Physical vs. Virtual Backups Rick Vanover MCITP vExpert VCP Veeam Software

About the Speaker Contributor to industry publications

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

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  Agents available many applications  Granular control and administration at each layer of backup infrastructure  Can be installed in virtual machine 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

PROs and CONs of Physical Backups 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  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

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 Disk volume Volume Shadow Copy Service Provider Requestor Writers

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

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

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 Virtual Machines Physical Machines

Common restore scenarios  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 Important

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

Service catalogs and virtualization Virtualization is impactful to existing procedures

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

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

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.here Web: Twitter: BckpAcademyBckpAcademy Facebook: backup.academybackup.academy