[cisco-voip] Disaster Recovery Procedure CUCM 5.1(2)

[Patrick Diener]

thanks a lot for all the good responses, you really helped a lot!!!

considering the new information I changed my step by step process to
the following:

Step 1: Gather necessary stuff
- contact cisco licensing to get new .lic files for the replacement publisher hw
- make sure the USB tokens needed to change the CTL File are accessible

Step 2: Install CUCM on replacement hw
- make sure to use same hostname, ip address and passwords as the
server you like to replace
- add .lic files acquired in Step 1
- check weather sufficient DLUs and node licenses are now available

Step 3: DRS
- recover the latest backup using the disaster recovery system

Step 4: Reinstall Subscribers
- a fresh install is necessary for all subscribers in the cluster
- after the reinstall use DRS to recovery lost data on the Sub. (I
assume activated services, enterprise parameters, etc.)

Step 5: Update CTL file and LSCs
- use CTL Client and USB tokens to update the CTL File with the new
Certificates of all CallManager nodes, the TFTP Servers and CAPF
- if used, update the LSCs (cause CAPF cert. has been changed(??))

=> as I see it telephony service will be interrupted during sub.
rebuild. if security is configured tel. service will not be back up
until step 5 is finished...

all this is also covered in the doc wes posted!

Regards
Patrick


On 10/19/07, Ruben Montes (Europe) <Ruben.Montes at eu.didata.com> wrote:
> Hello,
>
> I had to do a Publisher replacement from a MCS7825 to a MCS7835 last
> week. We had two additional subscribers. I followed step by step the
> guide Wes has mentioned and all went fine (the whole change took us 9
> hours).
>
> The main problem is that you MUST reinstall also all the subscribers
> from the cluster: this was confirmed by TAC and by the customer's SE
> cisco engineer.
>
> If you have any additional question about this just drop me an email...
>
> Regards,
>
> Ruben
>
> -----Mensaje original-----
> De: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] En nombre de Wes Sisk
> Enviado el: viernes, 19 de octubre de 2007 19:03
> Para: Patrick Diener
> CC: cisco-voip at puck.nether.net
> Asunto: Re: [cisco-voip] Disaster Recovery Procedure CUCM 5.1(2)
>
> Hi Patrick,
>
> Good stuff.  Most of this is finally covered in CM513 docs:
> http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_g
> uide09186a00808be1dc.html
>
>
>
> Patrick Diener wrote:
> > I'm trying to put together a rough step by step procedure to do a
> > disaster recovery for a cucm 5.1(2) cluster and there are some stuff I
> > can't figure out how it should/will work...
> >
> > I based the steps on the DRS Admin Guide for Version 5.0 (5.1 not out
> yet?!?)
> >
> > Important: I try to do a restore on a new server hw => new first node
> MAC
> >
> > Step 1:
> > perform fresh install of cucm sw
> > !! set same hostname as before !!
> >
> ws: same hostname, ip, and passwords
> > Step 2:
> > perform restore using DRS and restart server (worked like a charm in
> the lab...)
> >
> > form now on I'm stuck...
> >
> ws: you restored the pub only, correct? and rebooted?  after you
> reinstall sub will need to DRS restore it as well.
> > Step 3:
> > Licensing?!?
> > all activated services will not start cause the .lic files are not
> > valid for the new server hw (at least thats what happened in the
> > lab..)
> > => will TAC send me a new .lic equal to the old one?
> > => do I need to contact licensing at cisco.com?
> > => any experience how long it will take to get the new .lic files?
> >
> ws: yep, new license files if replacing the pub. covered in the doc,
> licensing at cisco.com
> > Step 4:
> > move some phones to the restored publisher (assuming callmanager
> > service is running) and test all features needed
> > => will the phones register if security has been configured? I assume
> > the new callmanager, tftp and capf certificates will not match the
> > certificates stored in the phones ctl file (right?) how do I get out
> > of this mess without touching each and every phone to delete the ctl
> > file or perform a factory reset?
> >
> ws: this comes later actually. check the doc, you will create new CTL
> files using same USB token.
> > Step 5:
> > restore sub (or subs)
> >
> step5: reinstall subs, then restore subs, then perform post-replace
> checklist.
> >
> > all comments, experiences and remarks are appreciated!
> >
> > cheers
> > Patrick
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>