1 / 15

veeam/blog Twitter : @ RickVanover @ Veeam

Physical vs. Virtual Backups. Rick Vanover. MCITP vExpert VCP Veeam Software. http://www.veeam.com/blog Twitter : @ RickVanover @ Veeam. About the Speaker. Contributor to industry publications. Agenda. How backups for physical systems work How backups for virtual machines work

romney
Download Presentation

veeam/blog Twitter : @ RickVanover @ Veeam

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Physical vs. Virtual Backups Rick Vanover • MCITP vExpert VCP • Veeam Software http://www.veeam.com/blog Twitter: @RickVanover @Veeam

  2. About the Speaker Contributor to industry publications

  3. Agenda • How backups for physical systems work • How backups for virtual machines work • What frameworks are available for backups • How restore situations are impacted • Service catalogs and virtualization’s impact • Opportunities by platform • Considerations for licensing, management • and administration

  4. How backups for physical systems work • Generally independent of server model • Software installed within operating system (Agent) PROs and CONs of Physical Backups PROs • Easily backup physical systems • Agentsavailablemanyapplications • Granular control and administration at each layer of backup infrastructure • Canbeinstalledinvirtualmachine CONs • May miss out on additional frameworks and APIs • May not work correctly if agent is not running • Additional management burden and permission configuration • Not necessarily optimized for virtual machines

  5. How backups for virtual systems work • Leverage platform features: Hyper-V and vSphere APIs • Commands usually sent to a parent object: host, cluster, management server, etc. PROs and CONs of Physical Backups PROs • Easily backup virtual systems • Can move data very fast • Can be agentless-based backups • Can be very easy to manage CONs • Agentless backups may miss granular recovery or application consistency • Early generation virtual backups may only take crash-consistent backups • Recovery may be complex

  6. Key technology for both backups Degrees of backup consistency • Crash consistent • File system consistent • Application consistent • Best option for recoverability • VSS shown below for Windows systems Operating system, storage array or system provider SQL, Exchange, Active Directory, Oracle, SharePoint Backup software Writers Volume Shadow Copy Service Requestor Provider Disk volume

  7. More options with virtualization platforms • Framework such as APIs make • vStorage APIs for data protection • Web Services • PowerShell • Windows Management Instrumentation

  8. Many technologies for technology today • Impacts every area of datacenter • Stakeholders need to be informed and satisfied • Business discussions need to happen as well

  9. Mix of technologies • The fact is, many environments will have both virtual machines and physical systems • Mainstream platforms • Different platforms, specialty systems • Multiple tools may be required for each platform to deliver the best results Restore Virtual Machines Physical Machines

  10. Common restore scenarios Important • File restores • Most common restore situation • Operating system type, file system, and permissions are important • Application data restores • Structured data constructs • Items • Wildcard restores • Don’t know what is needed, but not a whole system restore • Full restores

  11. Full restores are different for each platform • Physical machines • Bare metal recovery options available • Like hardware requirements may exist • Base operating system and agent • Virtual machines • Image-based can inject back into hypervisor • Physical restore systems may work on virtual machines • Abstracted restore destination inherently possible

  12. Service catalogs and virtualization Virtualization is impactful to existing procedures Scale Regulation Compliance Expectations Technologies Requirements Abilities Funding Current state

  13. Considerations for backups and data protection • Licensing • Scaling, purchasing, organic growth • Some amount of virtualization likely • Administration and operations • Updates • Data durability • Management • Ensuring proper visibility • Accommodate organic growth

  14. What We Covered • How backups for physical systems work • How backups for virtual machines work • What frameworks are available for backups • How restore situations are impacted • Service catalogs and virtualization’s impact • Opportunities by platform • Considerations for licensing, management and administration

  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

More Related