Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Restoring 7.0(1) Subscriber

Hi,

We are having a subscriber and a publisher. We have the backup taken of both the Publisher and Subscriber. We want to change the hard disk to higher capacity on the subscriber so we have to rebuild the subsciber with the exact version of the call manager that Publisher is running. All is fine. But after building the cal manager in the subscriber do i need to restore the Subsciber backup to this or it is not necessary to restore the subscibe backup as it Will  automatically take all the configs from the publisher ?

Thank you!

3 REPLIES

Re: Restoring 7.0(1) Subscriber

As long as the server is healthy after it is added back to the cluster, it will receive the DB info from the Publisher.

Hailey

Please rate helpful posts!

New Member

Re: Restoring 7.0(1) Subscriber

Thanks David,

Can you please explain in which scenario we will then restore the subscriber backup to the subscriber. And why do we take the backup of the subscriber?? if it gets the database from the publisher?

Re: Restoring 7.0(1) Subscriber

This answer can get pretty involved so I'll try to keep it short. Essentially DRS has a master agent (Publisher) and each cluster node has a local agent that gets automatically activated when you set up DRS.  The Pub can then do cluster-level backups and write data to a few .xml files that can be referenced to restore an entire cluster, if need be.  What I'd recommend is that you read this guide on DRS but focus on the restore scenarios:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/drs/7_0_1/DRS_CUCM/drsag701.html

What you'll find is that there is a scenario for restoring a Subscriber BUT it requires that you've also restored the Publisher.  So, if you had to do that anyway then you'd likely be doing a cluster-level recovery (i.e., major issue occurred).  If you have a single node that you want to restore, you can re-add it to the cluster and it will receive DB and other info as part of replication and etc.

Hailey

Please rate helpful posts!

191
Views
0
Helpful
3
Replies