Why Virtual MachineBackups Are DifferentDavid DavisTwitter: @davidmdavisBlog: www.VMwareVideos.com
About the speaker Previous VMware Customer, IT Manager, Server &  Network Admin with 18 years in IT Contributor to indust...
Agenda Hardware Independence Image Level vs. File Level Backups Change Block Tracking (CBT) New Possibilities With VM Back...
Hardware IndependenceTraditional architectureTotally different approach required for virtualization
Hardware IndependenceVirtualization architecture
Hardware Independence Abstracts OS from being tied to the hardware Guest OS now uses virtual hardware that works no  mat...
Image Level vs. File Level Backups  With virtualization, you can backup the entire “image” of  the server  No agent is req...
Change Block Tracking (CBT) With VMware ESX/ESXi 4.0 or later and virtual  machine HW version 7 or later, change block  t...
New Possibilities with VM Backups VM portability (HW independence) vMotion / svMotion / DRS / VMHA Fast backup (change ...
Traditional Backup Doesn’tUnderstand Virtualization You need backups of the VMDK (virtual machine disk)  as well as the V...
Traditional Backup Doesn’tUnderstand Virtualization The VMX contains the VM’s virtual hardware and  configuration
Traditional Backup Doesn’tUnderstand Virtualization Virtual machines move around thanks to vMotion and  Distributed Resou...
What is the Right Tool for the Job?
What We Covered Hardware Independence Image Level vs. File Level Backups Change Block Tracking (CBT) New Possibilities Wit...
Enjoy and share this material Feel free to promote this material Recommend your peers to pass certification Blog, Tweet...
Upcoming SlideShare
Loading in …5
×

Why virtual machine backups are different by David Davis

844 views

Published on

In this session we'll talk about hardware independence that's created by server virtualization. I'll cover the difference between image level versus file level backups. We'll touch on change block tracking, and then I'll cover some of the new features and possibilities that are made possible with virtualization backups, things like fast restore, replication, creating virtual labs and more. I'll cover why traditional backup software just doesn't understand virtualization, and then finally we'll end with what's the right tool for the job of backing up your virtual infrastructure. So with that, let's get started.

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
844
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
21
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

Why virtual machine backups are different by David Davis

  1. 1. Why Virtual MachineBackups Are DifferentDavid DavisTwitter: @davidmdavisBlog: www.VMwareVideos.com
  2. 2. About the speaker Previous VMware Customer, IT Manager, Server & Network Admin with 18 years in IT Contributor to industry publications
  3. 3. Agenda Hardware Independence Image Level vs. File Level Backups Change Block Tracking (CBT) New Possibilities With VM Backups – Fast Restore, Replication, Virtual Lab, and more Traditional Backup Doesn’t Understand Virtualization What is the Right Tool for the Job?
  4. 4. Hardware IndependenceTraditional architectureTotally different approach required for virtualization
  5. 5. Hardware IndependenceVirtualization architecture
  6. 6. Hardware Independence Abstracts OS from being tied to the hardware Guest OS now uses virtual hardware that works no matter the underlying server hardware Allows you to move VMs from server to server (within processor family) Hardware independence makes the benefits of virtualization possible Completely changes how you should look at backup
  7. 7. Image Level vs. File Level Backups With virtualization, you can backup the entire “image” of the server No agent is required in the guest OS No load is put on the guest OS No end users are affected when the backup occurs Backing up the image of the server is much faster and less disruptive than backing up the files in the guest OS Image level restores are much faster Backup Restore options and speed are critical Restore
  8. 8. Change Block Tracking (CBT) With VMware ESX/ESXi 4.0 or later and virtual machine HW version 7 or later, change block tracking is possible Virtual machine disk blocks that are changed are tracked outside of the guest OS CBT allows virtualization backup software to backup only the changed blocks (software that takes advantage of this feature) Allows backups to only process changed blocks
  9. 9. New Possibilities with VM Backups VM portability (HW independence) vMotion / svMotion / DRS / VMHA Fast backup (change block tracking) Fast restore (mount for backup repository & image level restore) Simplified disaster recovery Replication of only changed blocks to DR site Virtual Lab using backups of production VMs for test & development All made possible with use of virtualization
  10. 10. Traditional Backup Doesn’tUnderstand Virtualization You need backups of the VMDK (virtual machine disk) as well as the VMX (virtual machine configuration)
  11. 11. Traditional Backup Doesn’tUnderstand Virtualization The VMX contains the VM’s virtual hardware and configuration
  12. 12. Traditional Backup Doesn’tUnderstand Virtualization Virtual machines move around thanks to vMotion and Distributed Resource Scheduler (DRS)
  13. 13. What is the Right Tool for the Job?
  14. 14. What We Covered Hardware Independence Image Level vs. File Level Backups Change Block Tracking (CBT) New Possibilities With VM Backups – Fast Restore, Replication, Virtual Lab, and more Traditional Backup Doesn’t Understand Virtualization What is the Right Tool for the Job?
  15. 15. Enjoy and share this material Feel free to promote this material Recommend your peers to pass certification Blog, Tweet and share this material and your experience on Facebook You’re an Expert? We will be happy to have you as Backup Academy contributor. Apply here. Web: http://www.backupacademy.com E-mail: feedback@backupacademy.com Twitter: BckpAcademy Facebook: backup.academy

×