[cisco-voip] Publisher - Subscriber syncing

[Wes Sisk]

it depends, but most likely not.  even though you don't change anything 
there are still automated changes happening in the backend.  'utils 
dbreplication reset' will get you and going if replication has stopped.  
Scott's post is accurate on how to check replication state. You can also 
use the CLI command 'utils dbreplication status'

admin:utils dbreplication ?
      utils dbreplication clusterreset
      utils dbreplication dropadmindb
      utils dbreplication repair
      utils dbreplication reset
      utils dbreplication setrepltimeout
      utils dbreplication status
      utils dbreplication stop

admin:help utils dbreplication reset

utils dbreplication reset help:
usage: utils dbreplication reset [nodename]|all
Reset tears down and rebuilds replication. Use when replication setup 
has failed after install/upgrade
You must execute "utils dbreplication stop" before using this command. 
If reset all, stop replication on all nodes first.
If using reset <nodename>, stop replication on that node first.

/Wes

On 9/22/2008 8:18 AM, Anthony Kouloglou wrote:
> Hi, i have a 6.1(2) CUCM cluster.
> For some reasons, subscriber was out of the network for a couple of 
> days (but none change occured to it).
> We changed some things in the publisher : added some phones, edited 
> some others.
> As soon as i plugged in the subscriber in the network will it sync 
> with the publisher and get the latest changes?
> How can i monitor the process and know it has finished?
>
> Chears,
> Anthony
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080923/410ba68c/attachment.html>