[cisco-voip] 3rd Party backup tools

Tue Oct 27 08:56:58 EDT 2015

Not sure if mentioned in this thread, but something to consider is to have a VM with the base CUCM installed for each of your pubs and subs. That way, if you have to restore, you just spin up the base install and restore from DRS. 

That would save some significant time. 

--- 
Lelio Fulgenzi, B.A. 
Senior Analyst, Network Infrastructure 
Computing and Communications Services (CCS) 
University of Guelph 

519‐824‐4120 Ext 56354 
lelio at uoguelph.ca 
www.uoguelph.ca/ccs 
Room 037, Animal Science and Nutrition Building 
Guelph, Ontario, N1G 2W1 

----- Original Message -----

From: "Rob Dawson" <rdawson at force3.com> 
Cc: cisco-voip at puck.nether.net 
Sent: Tuesday, October 27, 2015 8:53:04 AM 
Subject: Re: [cisco-voip] 3rd Party backup tools 

I have cloned nodes for lab testing with no issue, but during a window when I could shut them down first. 

On the flip side, I have seen nodes get built erroneously on servers that were being backed up by Veeam and a stuck snapshot from a backup job cause call processing errors and node restarts. 

Rob 		

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nathan Reeves 
Sent: Tuesday, October 27, 2015 12:42 AM 
To: Ryan Huff 
Cc: cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] 3rd Party backup tools 

We've always had DRS backups in place given thats the officially supported path for restore. Do keep some Veeam backups in place but tend to run them infrequently when we're looking to do work on the cluster and want a quick fallback position. I would tend to power down and backup to ensure consistency as I'm not sure how well informix works with running machine snapshots on restore. 

Nathan 

On Tue, Oct 27, 2015 at 1:02 AM, Ryan Huff < ryanhuff at outlook.com > wrote: 

While it is more than NOT supported; I have had success with cloning ucos vm's (while powered off). Then powering on the clones with the parents turned off. Again, clearly not supported but I have not noticed any behavior differences. 

For kick's and curiosity's sake I have vmotioned a lab cluster (with sip pstn) before while powered on ... caused cpu spikes and the trunks had to be reset. 

However, in practice I'd not wonder outside the bounds of the DocWiki for backup purposes. 

Sent from my T-Mobile 4G LTE Device 

-------- Original message -------- 
From: Anthony Holloway 
Date:10/26/2015 12:20 PM (GMT-05:00) 
To: "Heim, Dennis" 
Cc: cisco-voip at puck.nether.net 
Subject: Re: [cisco-voip] 3rd Party backup tools 

As a Cisco partner, I will be sticking to the book on this one (DRS). 

http://docwiki.cisco.com/wiki/Ongoing_Virtualization_Operations_and_Maintenance#Backup.2C_Restore.2C_and_Server_Recovery 

However, I am very curious to know what else works, and how well it works. 

On Sun, Oct 25, 2015 at 11:12 PM, Heim, Dennis < Dennis.Heim at wwt.com > wrote: 

Whats the current thought process around 3 rd party backup tools to quickly restore a CUCM? I’ve played with Veeam in the past. If the VM is shutdown, would that be kosher? 

Dennis Heim | Emerging Technology Architect (Collaboration) 

World Wide Technology, Inc. | +1 314-212-1814 

“There is a fine line between Wrong and Visionary. Unfortunately, you have to be a visionary to see it." – Sheldon Cooper 

“The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it.” -- Michelangelo Buonarroti 

“We should tansform the way we work” -- RowanTrollope 

Click here to join me in my Collaboration Meeting Room 

_______________________________________________ 
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 

_______________________________________________ 
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/20151027/91a9c33a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.gif
Type: image/gif
Size: 4226 bytes
Desc: image006.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151027/91a9c33a/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.gif
Type: image/gif
Size: 2017 bytes
Desc: image007.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151027/91a9c33a/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.gif
Type: image/gif
Size: 2014 bytes
Desc: image008.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151027/91a9c33a/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.gif
Type: image/gif
Size: 1939 bytes
Desc: image009.gif
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20151027/91a9c33a/attachment-0003.gif>