[cisco-voip] Backup and restore procedure in VMware environment?

[Ki Wi]

Hi Wes,
Manual intervention is ok as long we can save the time from installing the whole OS again which typically takes hours.

Sent from my iPhone
Pls pardon my fat fingers.

On 20 Apr, 2012, at 8:41 PM, Wes Sisk <wsisk at cisco.com> wrote:

> The wording is subtle but it does not accomplish what you want.  you cannot copy each node in the cluster one at a time and use those copies as a backup. database replication between the copies will not come up without manual intervention.
> 
> On Apr 19, 2012, at 11:32 PM, Ki Wi wrote:
> 
> Hi Scott and list members, 
> 
> I found this info from cisco's wiki for UC app. Looks like it is supported now. 
> 
> Copy Virtual Machine
> 
> NOTE: support varies by app and version. Before reading the best practices below, verify support at Supported Editions and Features of VMware vSphere ESXi, VMware vCenter and VMware vSphere Client.
> 
> Copying a Virtual Machine (VM) copies both the virtual server configuration and the workload (UC OS and application) running on that virtual server to a file on networked shared storage. This allows VMs to be copied, then subsequently modified or shut down. This feature effectively provides a method to do full system backup/restore, take system images or revert changes to software versions, user data and configuration changes.
> 
>         Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).
>         If uploading a VM copy as a “whole system restore”, clustered UC applications such as CUCM will probably require their replication to be manually “fixed” via a CLI command. 
> 
> 
> 
> 
> 
> 
> On Fri, Apr 20, 2012 at 3:20 AM, Scott Voll <svoll.voip at gmail.com> wrote:
> I don't know about newer versions.... but previously a back and restore was your only supported option.
> 
> and if you did have a snapshot / clone / etc and you used a backup to restore after.... the subs would all be off on there DB so you would have to rebuild each of them.  
> 
> I don't know if that has changed so take it for what it's worth.
> 
> YMMV
> 
> Scott
> 
> On Mon, Apr 16, 2012 at 10:56 AM, Ki Wi <kiwi.voice at gmail.com> wrote:
> Hey guys, 
> I'm wondering for cisco UCS, what you all have done for backup and restore procedure for quickest restoration?
> 
> Here's what i will do, correct me if I'm wrong. I only have CUCM/CUC/UCCX/CUPS in the cust UCS environment. 
> 
> For Publisher ( CUCM/ CUC / UCCX/ CUPS) , i suppose after initial setup is done. I can copy the VM and store the copy somewhere else such as another datastore or copy it off the esxi using SFTP.
> 
> When the publisher failed, I just need to restore the VM and restore the latest DRS backup into this publisher and reset all the sub synchronization.
> 
> For subscribers, will the steps above for publisher works? I guess I would have to store their individual copies (such as 3 sub i will need 3 VM copies) to avoid any IP address conflicts. 
> 
> _______________________________________________
> 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
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120421/6b05e04a/attachment.html>