<html><head></head><body bgcolor="#FFFFFF"><div>Hi Wes,</div><div>Manual intervention is ok as long we can save the time from installing the whole OS again which typically takes hours.<br><br>Sent from my iPhone<div>Pls pardon my fat fingers.</div></div><div><br>On 20 Apr, 2012, at 8:41 PM, Wes Sisk <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>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.<div><br><div><div>On Apr 19, 2012, at 11:32 PM, Ki Wi wrote:</div><br class="Apple-interchange-newline">Hi Scott and list members, <br><br>I found this info from cisco's wiki for UC app. Looks like it is supported now. <br><br>Copy Virtual Machine<br><br>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.<br>
<br>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.<br>
<br> Prior to copying, the VM must first be shutdown (which will shut down the virtual server, the UC OS and the UC application).<br> 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. <br>
<br><br><br><br><br><br><div class="gmail_quote">On Fri, Apr 20, 2012 at 3:20 AM, Scott Voll <span dir="ltr"><<a href="mailto:svoll.voip@gmail.com">svoll.voip@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't know about newer versions.... but previously a back and restore was your only supported option.<div><br></div><div>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. </div>
<div><br></div><div>I don't know if that has changed so take it for what it's worth.</div><div><br></div><div>YMMV</div><div><br></div><div>Scott<br><br><div class="gmail_quote"><div><div class="h5">On Mon, Apr 16, 2012 at 10:56 AM, Ki Wi <span dir="ltr"><<a href="mailto:kiwi.voice@gmail.com" target="_blank">kiwi.voice@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Hey guys, <br>I'm wondering for cisco UCS, what you all have done for backup and restore procedure for quickest restoration?<br>
<br>Here's what i will do, correct me if I'm wrong. I only have CUCM/CUC/UCCX/CUPS in the cust UCS environment. <br>
<br>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.<br><br>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.<br>
<br>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. <br>
<br></div></div>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></div><br></div></div></blockquote></body></html>