[cisco-voip] Restoring 4.1(3)sr5d Publisher?

[Lelio Fulgenzi]

Your process is what I would do. Get it running to the version you have now offline and then once you have restored everything from backup shut down the publisher, plug it in and then restart it. once it is restarted, you will have to restart the TFTP server and other subscribers. 

Hopefully you don't have to republish the databases. But if you do, you can use the dbhelper tool to do that. 

Hopefully others will help. 

P.S. If your TAC engineer is not familiar with 4.1, then I would ask to have the case escalated to someone who has 4.1 experience. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
"Bad grammar makes me [sic]" - Tshirt 


----- Original Message ----- 
From: "Dane" <dane at pktloss.net> 
To: cisco-voip at puck.nether.net 
Sent: Wednesday, September 30, 2009 11:21:46 AM GMT -05:00 US/Canada Eastern 
Subject: [cisco-voip] Restoring 4.1(3)sr5d Publisher? 

We had a drive fail on our publisher and had someone swap it out last 
night. Well it seems they made a couple of mistakes and left me no 
option but having to rebuild and restore now. 

Were running 4.1(3)sr5d and have a current BARS backup. 

Problem is all the media we have is some what old so I am having to 
install and upgrade and upgrade and upgrade to get back to where we 
were. 

My concern centers around the fact that this is the publisher that is 
down and having to be rebuilt using older media and then upgrading to 
get back to the point we were. Is there a risk in corrupting or 
interrupting the subscriber that is currently operational and running 
everything? I am afraid of the publisher coming back online too early 
during the process and somehow overwriting information on the 
subscriber before the publisher is fully built. 

My TAC engineer isn't familiar with the 4.1 release and windows side 
of things. Currently the plan he suggests based on the media we have 
available is to install 4.0.2 (from media) offline (unplug cable), 
then upgrade it to 4.1(3), then upgrade to 4.1(3)sr5d, then install 
BARS from that version of CM and do the restore of the BARS backup 
data. 

Does this sound right to others? 
_______________________________________________ 
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/20090930/f98dde5c/attachment.html>