[cisco-voip] Publisher Recovery

[Matt Slaga (US)]

The database on the publisher should be the exact same as the last state
of the publisher.  What it sounds like was your BARS backups have been
failing :-(

 

TAC may be able to assist, but not likely.  It is extremely rare for TAC
to spend the time reworking subscribers, usually only in cases where the
issue was caused by BARS itself.

 

How many users and how far back would you have to go to get a good bars
backup?

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Michael L.
Windon
Sent: Tuesday, August 08, 2006 10:58 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Publisher Recovery

 

 

Issue: We have a Publisher and Single Subscriber Cluster. The Publisher
has crashed and will require a new install of OS, patches and CCM. I
would like to recover it to the Database still running on the
subscriber. Can I 

 

1.)     Promote the Subscriber to a Publisher and install the old
publisher as a subscriber?

2.)     Run BARS on the Subscriber and then recover the Publisher as a
Publisher but use the BARS to restore the database?

3.)     Change the replication process to replicate one way from the
subscriber to the publisher

4.)     Something Else

 

Thanks in Advance!

 

 

 




-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060808/6f60a242/attachment-0001.html