HI,

Nope.  Only the other way.  Only if a sub dies will it get the DB from the pub. 
 If the pub dies you have to reinstall the SW on the pub then restore from the 
backup file.  Keep a record of the IP address, hostname and probably IP 
addresses and passwords.

cr*p.  Forgot what to do with the subscribers.  I think they just 
re-synchronized.  I rebuit a 5.1 pub about 1.5 years ago and the sub wasn't in 
the same building but the phones registerd to it and dbsync looked good when I 
left (at 3:00am).  But Db sync issues developed a couple days later.  Not sure 
if they were just the usual 5.1 db bugs that were floating around or I should 
have re-did the subscriber too.

It's important to keep and check your disaster recovery backups and store them 
off the CCM box and possibly off-site.  Usually SFTP the backup file to a 
windows server where your enterprise backup software will put it on tape.

If you have a DR site, you can store the backup file on a server at the DR site.

You should be able to really simulate a pub failure by turning off the power to 
the VM.  One of the times you do it, it might not come back up and give a 
kernal panic message.  Make sure your pub is on a UPS with redundant power 
supply and keep people away from the power switch.  lol (ok, not funny.  3am)

________________________________
From: ccie_voice-boun...@onlinestudylist.com 
[ccie_voice-boun...@onlinestudylist.com] On Behalf Of S Maclean 
[sdmac...@hotmail.com]
Sent: Friday, May 01, 2009 11:59 AM
To: ccie_voice@onlinestudylist.com
Subject: [OSL | CCIE_Voice] PUB DR Simulation

Any thoughts..

I’m simulating a PUB failure in my VM lab with 6.1, does the DRS restore 
mechanism make it reach out to the existing subscribers during the restore? I 
have 1 PUB and 2 SUB in the scenario.

If it does reach out, can I do it isolated, ie just build the PUB on it’s own? 
What's the best way to do this?




________________________________
Share your photos with Windows Live Photos – Free. Try it 
Now!<http://clk.atdmt.com/UKM/go/134665338/direct/01/>

Reply via email to