The CLI utils dbreplication reset all was run on a Cisco Unified Communications Manager.
However, replication failed to restart. Which course of action should be taken to resolve this issue?

A.
Restart the replication from the Cisco Unified Communications Manager RTMT tool.

B.
Issue the CLI command utils dbreplication runtimestate

C.
Issue the CLI command utils dbreplication reset

D.
Issue the CLI command utils dbreplication clusterreset

E.
Issue the CLI command utils dbreplication clusterreset all

Explanation:
I’ve found only this post:
Database Replication Does Not Occur When Connectivity Is Restored on Lost Node
Symptom Database replication does not occur when connectivity is restored on lost node
recovery. You can verify the state of replication by using the methods given in the topic Replication
Fails Between the Publisher and the Subscriber. Only use the following procedure if you have
already tried to reset replication on the node, and have been unsuccessful.

Possible Cause: The CDR check remains stuck in a loop, due to a delete on device table.
Recommended Action
Step1 Run utils dbreplication stop on the affected subscribers. You can run them all at once.
Step2 Wait until Step1completes, then, run utils dbreplication stop on the affected publisher
server.
Step3 Run utils dbreplication clusterreset from the affected publisher server. When you run the
command, the log name gets listed in the log file. Watch this file to monitor the process status. The
path to the follows:/var/log/active/cm/trace/dbl/sdi
Step4 From the affected publisher, runutils dbreplication reset all.
Step5 Stop and restart all the services on all the subscriber servers [or restart/reboot all the
systems(subscriber servers)] in the cluster to get the service changes. Do this only afterutils
dbreplication status shows Status 2.
Link-http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/trouble/7_0_1/tbsystem.html