Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

NetBackup - VMware virtual machines

Created: 11 Oct 2012 • Updated: 19 Dec 2012 | 4 comments
mmeeggaann's picture
This issue has been solved. See solution.

Hi, 

 

I was wondering if it is possible to restore a VM with a new UUID and a different  display name, to the same location?
 
Let me explain... there are  6 VMs  (2 PROD, 2 DEV and 2 QA) running on  3-ESX servers configured as a cluster. I would like to use the NetBackup features (back up/ restore) to clone productive VMs and then update the non-productive environment (development o QA). To do so, I need the the UUID and display name are different. 
 
I'll appreciate your help. Regards!
 

 

Comments 4 CommentsJump to latest comment

CY's picture

I have not tried the way you asked, but I have a suggestion for your need (to refresh the Dev and QA from Production VM):

1. Assuming that you have the DB or release codes on different drives (for example, D:\) than of the boot drive (C:\), then you can configure the NBU backup policy to exclude the boot disk in "virtual disk selection" so only the data drives are backed up.  You can configure another NBU policy to back up the boot disk only (exclude the data disks) so you still can protect the whole VM.

2. Restore the data drives to the Dev and QA servers to refresh these non-production environments. Now you don't have to restore the whole VM and worry about changing the UUID, etc.

Yasuhisa Ishikawa's picture

You can restore VM with different UUID unless you check 'Restore BIOS UUID "xxxx" intead of creating a new UUID' at restore.
Of course, you can set different display name.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

captain jack sparrow's picture

Wondering why do you rely on NBU to clone your VMs when you have that feature in VMware / Hyper-V itself

 Cheers !!!

CJS

 

SOLUTION
mmeeggaann's picture

You're right Captain, at the end I wasn't able to test the NetBackup restore. The VMware administrator cloned the virtual machine and that was enough to resolve the issue.