1. Supporting Our Customers’ Journey to the Private Cloud
EMC EMEA TC Conference 2010
Supporting Our Customers’ Journey to the Private Cloud
BRS Solutions for VMware

2. Image vs Guest Level Backup
Guest level backup: traditional backup type by using backup software agent inside VM to read and transfer data just like on physical system.
Image level backup: backup is performed from ESX host by freezing VM and backing up its image.
Image
Guest
Backup application compatibility
Limited, but increasing
Requires only qualification
VM system compatibility
Limited to specific guest OS types and disk formats
Transparent
VM application compatibility
Limited
Transparent, standard backup application modules can be used.
Performance
High to very high
Low to medium
Resource usage
High

3. Application vs Crash Consistency
Typical image backup provides so-called crash-consistent backup.
In case of restore, VM is restored to a state equal of unplanned shutdown.
It does not provide application-awareness
To provide application-consistent backup, application itself must be informed of backup
Possible on Microsoft platform via VSS framework
Generally up to backup software vendor to provide VSS integration
Limited VSS integration provided by VMware starting with vSphere 4.1
Supported only for VMs running Windows 2008
Supported for limited set of applications
With VSS integration, backup level reached is application-consistent, but not application-integrated
For full application-integration and advanced capabilities, must use in-guest backups with appropriate application module.

4. VCB: VMware Consolidated Backup
Introduced with VMware ESX server 3.0 and still present in vSphere 4.0
Leverages VMFS snapshot technology
Not stable before VCB 1.5 introduced in ESX 3.5
Latest version is VCB 1.5 Update 2 from March 2010
VMware discontinued development of VCB and existing customers are encouraged to upgrade to VADP based solution
VCB is no longer present on vSphere 4.1
VCB is still supported for restore purposes even on latest vSphere versions
VCB requires a separate HW proxy host
VCB requires presence of VMware vCenter Converter (vConverter)
vConverter version must match supported version from backup application.

5. VADP: VMware Storage APIs for Data Protection
Introduced with VMware vSphere 4.0
Leverages VMFS snapshot technology
Backup flow is based on more integrated API
Supports VMs based on VMware vStorage VMFS
VADP cannot be used to protect pass-through disks (RDM: raw device mapped disks in physical compatibility mode)
VADP cannot be used to protect network mounts (CIFS or NFS) within guest
Backup solution can optionally have deeper integrated with storage arrays via VAAI: VMware vStorage APIs for Array Integration
This offloads VM snapshot creation from ESX host to array itself
Introduces limited application-awareness starting with vSphere 4.1
Proxy host is a VM itself.
Need a separate VM proxy for each OS type (Linux or Windows)

6. VADP vs VCB Quick Compare
VADP
VCB
Requires additional download & install
No, built into the data protection software
Yes
Full virtual machine image backup
Yes, single step copy – source to target
Yes, with two step copy – source to VCB proxy and VCB proxy to the target
Incremental virtual machine image backup
Yes – using change block tracking No
File level backup
Yes, both Windows and Linux
Yes, Windows only
Full virtual machine image restore
Yes, by using VMware Converter
Incremental virtual machine image restore
File level restore
Yes, using restore agents
CLI for image backup
CLI for file backup
Unlike VCB, which requires customers to download and install a separate

7. CBT: VMware VADP Change Block Tracking
VADP supports optional usage of CBT
CBT is disabled by default and must be enabled per VM
CBT requires that VM version is 7 or higher.
Environments upgrading from ESX 3.x to ESX 4.x need to upgrade each VM
CBT does introduce small performance penalty on production system
Not recommended for VMs with very high change rate

8. EMC BRS Solutions for VMware
NetWorker
Avamar
DataDomain

9. NetWorker and VMware Protection
IN-GUEST
Support for vSphere (VCB support in all current versions)
Deduplication support
Granular and application consistent guest level backup
Off-host snapshot-based backup
Granular and full image recovery with single image backup
Incremental and differential file backups based on full image
Licensed per physical host. Not per VM.
VDAP support coming in NW 7.6 SP2
OFF-HOST

10. VMware Auto-Discovery and Visualization
Automatically discover VMs
Notification of unprotected VMs
Visualization
Visual map of the environment
Interactive controls to filter display
Displays relationships between NetWorker and virtual environments
Helps determine load balancing
Configure VM backups from map— easy, right-click-to-launch wizard

11. NetWorker with Data Domain
FILE SYSTEMS AND APPLICATIONS
Use with existing disk-based or VTL capabilities
Use with DD Boost
Improved performance
Clone-controlled replication
Automated configuration
Monitoring and reporting
NetWorker
Data Domain
Replication
WAN
Primary data center
Remote site

12. Benefits of Data Domain Boost
Deduplication distributed to backup servers
Increases backup speed
Reduces network traffic
Clone-controlled replication
Schedules replication
Catalog awareness of replicated copies
Ease of use
Automated configuration
Monitoring and reporting
DD Boost
DD Boost
NetWorker
Data Domain

13. FILE SYSTEMS AND APPLICATIONS
NetWorker with Avamar
FILE SYSTEMS AND APPLICATIONS
Supports file systems and applications
Physical and virtual
Manage traditional and deduplication backup
Single client or application module
Common administration
Full indexing and browse
Common recovery
NetWorker
Avamar
Replication
WAN
Primary data center
Remote site

14. Avamar VMware Guest Backup
No-cost Avamar agents assure application consistency
Avamar Agents
Agent resides in each virtual machine
Deduplicates within and across virtual machines – as if they were physical servers
Reduces resource contention and speeds backups
Provides file-level restore for Windows, Linux and Solaris
VMware ESX

15. Avamar VMware Image Backup
Avamar integration with VMware vStorage API
Resource Pool
VMware Virtualization Layer
x86 Architecture
Physical server
Virtual Machines
SAN
storage
Avamar
server
Mount
= Avamar Software Agent
Deduplication within and across VMDK files
Load-balancing across proxy virtual machines
Change-block-tracking minimizes recovery time
File level recovery from image backup
Replication provides DR for backed up VMDKs

16. Proxy Server Load Balancing
Avamar efficiently uses available resources
ESX SERVER CLUSTER
Storage
LUNs
Virtual
Machines
Proxy
Servers Pool
Avamar
DRS
VMware
How does this work?
Avamar automatically assigns VMs backup jobs to available proxy servers using a round robin protocol
Backups are distributed evenly across available virtual proxy servers
Benefits
Automatic and transparent
More efficient backups
Better use of available resources
Simplifies the management of virtual proxy servers
Applied either globally or in groups

17. Use Cases Clear Channel
Protecting ~90TBs/1200+ VMs using Avamar and VADP&CBT image backups
Backup time range 3 min to 1 hour/VM
Without CBT some very large VMs (750GB in size) take upwards of 6-7 hours to backup.
Bank of America
Protecting up 350TBs+/6000 VMs using guest backup
Average backup time 6 min/VM
GSK
Protecting ~50TBs/1000 VMs using guest backups
USAA
Protecting ~75TBs/1300 VMs using guest backups
Backup time range from 2 minutes to 1 hour

18. Q & A