vmware data recovery - wie konfiguriere ich meine...
TRANSCRIPT
© 2010 VMware Inc. All rights reserved
VMware Data Recovery- wie konfiguriere ich meine BackupRüdiger Melzer, Sr. Systems Engineer, VMware Deutschland
S-2
43% of companies experiencing disasters never re-open, and 29% close within two years
(McGladrey and Pullen)
93% of business that lost their data center for 10 dayswent bankrupt within one year
(National Archives & Records Administration)
40% of all companies that experience a major disasterwill go out of business if they cannot gain access
to their data within 24 hours(Gartner)
Top executives say 10 hours to recovery;IT managers say up to 30 hours
(Harris Interactive)
Disasters Happen. Do You Need Protection?
S-3
IntroductionBusiness Continuity and how could VMware help you
S-4
Business Continuity As An Infrastructure Service For All Apps
Resource Pool
vSphere vSphere vSphere
Local Site Failover Site
• vCenter Site Recovery Manager
• MetroClustering
• VMware High Availability (app-aware)• VMware Fault Tolerance
• VMotion
• VMware Data Recovery• vStorage APIs for Data Protection
Resource Pool
vSphere vSphere
Dev /Test
Dev /Test
Dev /Test
Disaster RecoveryLocal Availability
Data Protection
4
• Application and OS independent • Focus on simplicity, cost-efficiency
S-5
Local Availability Disaster Recovery
VMware Business Continuity Pillars
Data Protection
X
Reliable Platform
S-6
IntroductionConsiderations for Disaster Recovery (RPO vs RTO)
S-7
Disaster Recovery Concepts
SecsMinsHrsDaysWks Secs Mins Hrs Days Wks
Recovery Point Recovery Time
Recovery Point Objective (RPO)Point in time to which data must be recovered (i.e. how old can the data be?)
Recovery Time Objective (RTO)Time required to complete recovery of the application and it’s data
Disaster Strikes
S-8
Backup
SecsMinsHrsDaysWks Secs Mins Hrs Days Wks
Recovery Point Recovery Time
Recovery Point Objective (RPO)
Synchronous Replication
Periodic Replication
Asynchronous Replication
Disaster Strikes
S-9
Restore
SecsMinsHrsDaysWks Secs Mins Hrs Days Wks
Recovery Point Recovery Time
Recovery Time Objective (RTO)
Recovery Time includes: Fault detection
Recovering data
Bringing apps back online
Automated Migration Manual
Migration
vCenter Site Recovery Manager
Disaster Strikes
S-10
Remember why we do backups in the first place…
10
Restore requirements dictate backup methods RTO is impacted by the speed and ease with which you can recover the
system successfully AND consistently
Will the application be ready to run once restored or do you need to check consistency/replay transaction logs first? How long?
Backup to/restore from disk vs tape maybe required
Restore over SAN vs over LAN vs over WAN
Remote offices may use a Data Recovery Appliance locally, which can dedupethen replicate back to H/O more efficiently across the WAN to meet requirements of both offsite backup AND RTO
And so on…
S-11
What Data Protection Options do I Have in a Virtual World?
S-12
VM Data Protection Options
Method Description
Backup Application via LAN
• Backup agent in each Guest OS• LAN-based backups• Guest OS file-level backups• Same method as backing up physical servers
SAN-Based Backup/Replication• Back up via SAN storage array replication tool• Back up all VMs in entire VMFS datastore volume• VM-level backups
Backup Application integratedwith VMware vStorage API
• Single backup agent in proxy (consolidated backup)• LAN-based or LAN-free backups• Guest OS file-level backups or VM-level backups
VMware Data Recovery• VMware implementation of backup application integrated
with VMware vStorage API• Ideal for small/medium businesses
S-13
Backup Application via LAN
Traditional Backup/Restore Application• Backup agent inside Guest OS
• File-based backup and restore
• LAN-based
• Concurrent backups of VMs on same host can magnify load
Backup Agent
Backup Application Server
LAN
S-14
SAN-Based Backup/Replication
Storage Array-Based Tool• Takes snapshot of entire LUN
• Each LUN contains one or more VMFS datastores
• Each VMFS datastore contains one or many VMs
LUN LUN LUN LUN LUN
S-15
VMware vStorage API
VM Backup• Leverages VM snapshots for full and incremental backups
• No agent inside Guest OS
• Supports all storage architectures
Integration• Native integration with enterprise backup solutions
• Evolution of VCB
• Deployable on Windows or Linux
S-16
VMware vStorage API Integration Options
VMware vCenter ServerEnterprise Backup Application UI
VMware vStorage API for Data Protection
VMware vSphere
VMware Data RecoveryEnterprise Backup Applications
S-17
VMware Data RecoveryConcepts and Functions of a Game Changing Approach
S-18
Overview of VMware Data Recovery Functionality
18
Backups: Disk based backup, not file level (fast backup and quick restore) Any Guest OS can be backed up. A VM can be backed up even if it is suspended or powered off. Leverages VM snapshot technology and uses the SYNC driver or Microsoft VSS to
quiesce the Guest OS on a running VM. VMware Tools must be installed and running. Leverages VM Change Block Tracking (very efficient storage of backup) Uses an intuitive wizard driven workflow to create, configure and schedule backup
jobs
Restores: Can overwrite the current VM. Restore the VM if it no longer exists. Restore a ‘test’ VM which is identical to the original VM, but does not have networking
enabled – this is called a Restore Rehearsal. Multiple restore points for each VM are displayed to easily select a specific point in
time copy to restore
S-19
VMware Data Recovery
VMware Data Recovery (vDR) Virtual Appliance• Quick, simple and complete
data protection for VMs
• VM-level backups and restore
• Centralized management through vCenter Server
• Agent-less
• Cost effective storage management through data de-duplication
• Ideal for small/medium businesses
VirtualCenter
1. Backup
2. Restore
1. VM Guest OS files deleted (user error) resulting in loss of service
2. Select VM backups to recover
3. Fast restore of VM…downtime minimized
1. Schedule backups2. Snapshots taken3. Data de-duped and stored
vCenter
vCenter
X
De-duplicatedStorage
X
S-20
VMware Data Recovery Architecture
vSphere Client Data Recovery plug-in
vCenter Server
vDR Appliance
Backup Destination:
CIFS Network Share
Backup Destination: .vmdk in NFS
Datastore
Backup Destination:
.vmdk in VMFS Datastore
VM Source
vDR Windows/Linux CLI
S-21
VMware Data Recovery Components
vDR Appliance• Virtual appliance in OVF format
• Leverages VMware vStorage API to discover, back up, and restore VMs
• Works with vCenter Server
vSphere Client Plug-In• Used to interact with vDR appliance
• Integrates with vSphere Client UI Wizard-driven backup/restore job creation Automatically imports vCenter VM inventory
• Requires plug-in on each vSphere Client
vSphere Client Data Recovery plug-in
vCenter ServervDR Appliance
S-22
VMware Data Recovery Components
VM Source (for Backup)• Any VM in vCenter inventory Residing in VMFS or NFS-based datastore
• VM must be able to support VM snapshots
Supported Backup Destinations• Virtual disk attached to vDR appliance VMFS .vmdk or RDM in virtual compatibility mode NFS .vmdk
• SMB/CIFS shared storage mapped via vDR
• At least 10GB free space
• Backups stored in compressed and de-duped format
vDR Appliance
Backup Destination:
CIFS Network Share
Backup Destination: .vmdk in NFS
Datastore
Backup Destination:
.vmdk in VMFS Datastore
VMware ESX/ESXi
S-23
VMware Data Recovery Components
vDR Windows/Linux CLI• Use to restore individual files to a Guest OS
• Runs inside Guest OS
• Restores files from a backed-up VM
• Connects to vDR appliance
vDR Appliance
VMware ESX/ESXi
vDR Windows CLI
S-24
vDR Backup and Restore
VM Backup• Entire VM backed up, not file-level
• Uses VM snapshots, block-based cloning, and changed block tracking
• Virtual hardware 7 or 4 supported
• Any Guest OS supported Requires Windows and VMware Tools for quiescing
- SYNC driver for Windows and Microsoft VSS for applications
• VM can be in any state– even powered off or suspended
• First backup is full; subsequent are incremental
• Data de-duplication is standard and always performed
S-25
Data De-Duplication
Techniques• Scan for identical elements (blocks)
• Store identical elements only once
• Save pointers instead of multiple copies of data
• Duplication exists when: Taking multiple backups of same VM – save only changed blocks via incremental
backups Taking backups of VMs with same Guest OS – collapse identical blocks across VMs
Benefits• Consume less disk space required for backups
S-26
Data De-Duplication
Changed Block Tracking
All VMs running the same OS• Changed block tracking allows Data Recovery to back up only the changed blocks• De-duplication works across VMs• Helps with reduction in space consumption and storage I/O• Backs up common files once
Unique Blocks1st Full Backup – VM1
Data StreamVM1 yesterday
VM1 at 02:00
1st Full Backup – VM2VM2 yesterday
2nd Backup – VM1
VM2 at 03:00 2nd Backup – VM2
De-dupe store
S-27
Data De-Duplication
Virtual Hardware Dependencies• Virtual hardware 7 VMs Data Recovery accesses changed block tracking on ESX/ESXi 4.x hosts to determine
if block needs to be backed up or not
• Virtual hardware 4 (legacy) VMs Virtual disks are scanned every time to determine changed blocks
De-Duplication Details• OS and application agnostic
• Offline grooming of the de-dupe store Purge, reclaim space, defragmenting, consistency checks
S-28
Requirements
Supported Platforms• vSphere 4 (ESX/ESXi 4.0 U2, vCenter 4.x)
VMs• Virtual hardware version 4 or 7 (7 for Change Block Tracking capabilities)
• Must support VM snapshots
Backup Destination• At least 10GB free space
S-29
Limitations
vDR Appliance• Maximum 100 VMs backed up per appliance
• Maximum 2 de-duplication stores per appliance
• Up to 10 appliance per vCenter Server supported
• Cannot reside in vApp
• Multiple appliances are independent and do not interact
Storage• Disk only – no tape/media integration
• Maximum of 1TB per de-duplication store, in total 2 TB with two stores(this is the amount of de-duplicated storage)
Backups• Maximum 8 concurrent backup and 8 concurrent restore jobs (per Appliance)
• One backup per VM allowed every 24 hours
• Appliance vCPU usage must be under 80%
S-30
Comparing VM Backup Options
BackupApplication with
vStorage API
VMware DataRecovery (vDR)
SAN Backup/Replicat
ion
Guest OS Backup
Backup Type
• Full VM• Incremental• File-level
• Full VM (first)• Incremental
(subsequent)
• Full VM (entire VMFS)
• File-level• Full VM (all files by
file-level)• Incremental
Backup State
• Quiesced (Windows SYNC, application via VMware Tools)
• Crash-consistent
• Quiesced(Windows SYNC, application via VMware Tools)
• Crash-consistent
• Crash-consistent• Quiesced (some
are application consistent via VSS integration)
• Crash-consistent• Quiesced
(depends on application)
VM State • Powered on/off • Powered on/off • Powered on/off • Powered on only
Backup Agent • Single proxy agent • None • None • One per Guest OS
Performance Impact
• LAN-free orLAN-based
• LAN-free orLAN-based
• LAN-free • LAN-based
S-31
Comparing VM Backup Options
BackupApplication with
vStorage API
VMware DataRecovery (vDR)
SAN Backup/Replicat
ion
Guest OS Backup
Pros
• Option for LAN-free or LAN-based backups
• Single proxy backup agent (save money)
• Integrated with enterprise backup solution
• Simple backup virtual appliance
• Integrated with vCenter 4.0
• Data de-duplication for storage efficiency
• Quick backup• LAN-free backups• No backup agent• Ideal for Disaster
Recovery
• Same method as backing up physical machines
• Restore files directly into Guest OSes
Cons
• Cannot restore files directly into Guest OS without backup agent in Guest OS
• Cannot back up files inside Guest OS individually (only entire VM)
• Limit of 100 VMs per vDR
• Cannot back up files inside Guest OS individually
• Cannot restore files directly into Guest OS
• Granularity is LUN level on Storage
• Full VM backup takes time
• Magnified network/CPU load
• One agent per Guest OS
S-32
Where Can I Learn More?
VMware Data RecoveryProduct Page – www.vmware.com/products/data_recovery
Overview, datasheet, webinars, docs, community links
Free 60-day Evaluation – all you need to get started!
Business Continuity Solutions from VMware – www.vmware.com/solutions/continuity
VMbook on BC/DR – www.vmware.com/resources/techresources/1063
External Resources Administering VMware Site Recovery Manager book by Mike Laverick –http://www.lulu.com/content/4343147
© 2010 VMware Inc. All rights reserved
Thank You!
Questions & Answers