[cisco-voip] DB Replication Status

[Jonathan Charles]

Well, you can follow the replication recovery procedure...

First shut down the Publisher.

Boot up the Publisher.

Once the Publisher is back up, wait 15 minutes and reboot each
subscriber in sequence, at 15 minute intervals (only one, then do that
one)...

This kicks off a full DB replication and repair...



Jonathan

On Wed, Sep 2, 2009 at 9:30 PM, Matthew
Loraditch<MLoraditch at heliontechnologies.com> wrote:
> In RTMT i get a good for both of servers replication status and equal
> numbers of replicates, but if I run a DB status report in Unified Reporting,
> each server says it can't access the other??? Anyone seen this, is this an
> error in the reporting mechanism or an actual problem and time to open a TAC
> case
> Version is 7.0.2.21010
>
> Thanks!
>
>
> Matthew Loraditch
> 1965 Greenspring Drive
>
> Timonium, MD 21093
> support at heliontechnologies.com
> (p) (410) 252-8830
> (F) (443) 541-1593
>
> Visit us at www.heliontechnologies.com
> Support Issue? Email support at heliontechnologies.com for fast assistance!
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>