Non-Disruptive Backup of VMware Environments Using Veritas ...

More documents

Recommendations

Info

Technique 2: Backup the VMware VMDK (and VMX) FilesThree ways of backing these up:2) Shutdown VM – create snapshot – restart VM – backup VMDK filesUtilized snapshot + redo capability built into ESX 2.xRequires some scriptingVM is unavailable for only a short timeReboot is required with this techniqueAfter reboot, all writes are directed to a VMware Redo LogVMDK files are backed up using NBU RHEL client onService Console
Technique 2: Backup the VMware VMDK (and VMX) FilesThree ways of backing these up:3) Create snapshot – backup VMDK filesCreates a "Crash Consistent" version of VMware image(including apps)"Crash Consistent" does not sound very good…..No guarantee of data integrityNot recommended by NetBackupRaw Device Mapping (RDM) is"Crash Consistent" as well
Page 1 and 2: Non-Disruptive Backup of VMwareEnvi
Page 3: AgendaVMware ESX Architecture Overv
Page 6: Virtual Machine Backup IssuesAll VM
Page 9 and 10: Technique 1: Backup the VM as a NBU
Page 11 and 12: Technique 1: Backup the VM as a NBU
Page 13: Technique 2: Backup the VMware VMDK
Page 17 and 18: AgendaVMware ESX Architecture Overv
Page 19 and 20: CPU Utilization Before Virtualizati
Page 21 and 22: CPU Utilization After Virtualizatio
Page 23 and 24: VMware Consolidated Backup Componen
Page 25 and 26: VMware Consolidated Backup ProcessN
Page 27 and 28: VMware Consolidated Backup Processv
Page 29 and 30: Consolidate Backup Demo Environment
Page 31 and 32: Some Points To Keep In Mind Regardi
Page 33 and 34: Other ConfigurationsNot all possibl
Page 37 and 38: Planned Off-host Backup of VMware E
Page 41 and 42: Some Final Thoughts……..For more
Page 43: Presentation DownloadPlease remembe

Non-Disruptive Backup of VMware Environments Using Veritas ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?