1

Backup og De-dup i et VmWare miljøEMC Avamar

Frank SimonsenSystems Engineer

2

Intelligent Archiving

EmailXtender, DiskXtender,

Backup and Recovery

NetWorkerAvamar

HomeBase

Active ArchiveCentera

Backup to DiskDisk Library

AnalyticsBackup Advisor

Assessment, ImplementationFile Server Assessment, Exchange Server Assessment,

Backup Assessment

HardwareHardware

SoftwareSoftware

ServicesServices

EMC Backup, Recovery and Archive SolutionsEMC Backup, Recovery and Archive Solutions

TapeLibraries

ClassificationInfoscape

EMC Next Generation Backup and Archive

3

De-duplication Process Overview

1. Client agent walks the file system 2. Client agent breaks

modified files into variable-size objects

3. Only unique objects are backed up

Avamar Server

4

A B C D

De-duplication Server (stored backup data)

Only unique data segments are backed up

E

EA

BC

D

Data already backed up, so only unique IDs stored (20 byte pointers)

New data segment identified and backed up

Global De-duplication: PowerPoint Example

Remote Site 1

� Duplicate Instance

A B

C D

Company_Overview.ppt

Remote Site 2� Modified Instance

A B

C D

Company_Overview.ppt

� First Instance

A B

C D

Company_Overview.ppt

Data Center

5

Backup De-duplication

Avamar

Avamar makes backup to disk more economical

Traditional Backup vs. EMC AvamarTotal Cumulative Storage - 10TB MS Office file data

(Traditional = weekly fulls + daily incrementals; EMC Avam ar = daily fulls)

16

32

48

64

80

96

112

128

144

160

176

192

8

1624

3240

4856

6472

8088

96

5.55.35.14.94.74.44.24.03.83.63.43.20

20

40

60

80

100

120

140

160

180

200

1 2 3 4 5 6 7 8 9 10 11 12Weeks

Cum

ulat

ive

TB

Traditional BackupTraditional Backup with Compression (2:1)EMC Avamar

Traditional Backup

Traditional Backup w/Compression (2:1)

EMC Avamar

Total Cumulative Storage - 10TB MS Office file data(Traditional = weekly fulls + daily incrementals; E MC Avamar = daily fulls)

Traditional Backup v. EMC AvamarCumulative Media Required

4 weeks 8 weeks

6

Unique Value PropositionVMware Environments LAN-attached File Servers

� Unable to complete full backups in available windows?

� Production data or moving test/dev to production?

� Desire to drive further consolidation hindered by backup bottlenecks?

� Guest, VCB or console backup?

� Backup up both files and virtual disks (*.vmdk)?

Yes? Yes?

� Unable to complete full backups in available windows?

� Desire to replicate across WAN to DR site?

� Desire to reduce spend and risk associated with tape backup infrastructures?

� Desire to slow growth of secondary storage?

� 1 to 15 TB of primary data to protect

� VMware guests up to 1.5 TB each

� Databases up to 500 GB, daily change rate < 5%

� VM, VCB or Console backup

� Windows or UNIX

� 1 to 15 TB of primary data to protect

� Maximum file count per file server < 5,000,000 files

� Up to 1.5 TB per file server

� Avoid x-rays, movies, sound files, analog files

� Windows or UNIX

Remote/Branch Office

Yes?

� Need to improve data protection for business continuity and compliance?

� Unable to backup using existing WAN bandwidth?

� Desire to reduce time, spend and risk with local tape mgmt and transport?

� Desire to slow growth of secondary storage?

� 1 to 15 TB of primary data to protect

� 5 to 500 sites

� Agent-only option if possible, if RTO acceptable over WAN or if RTO acceptable to restore at and ship systems from data center

� (Follow guidelines for file servers, databases and VMware)

*Recommended initial deployment guidelines, not limits.

7

Deployment Flexibility Avamar Software AgentA

WAN

(ENCRYPTED)

Small Remote Site

Avamar agent onlyon primary systems

A

(ENCRYPTED)

Large Remote Site

Primary systems

A

Avamarserver

Data Center

Primary systems

A

Avamarserver

(ENCRYPTED)

Remote Recovery Site

Primary systems

A

TapeVault

Avamarserver

(ENCRYPTED)

8

Innovative Architecture

� Redundant Array of Independent Nodes (RAIN) architecture

– Each server node with internal disk storage and CPU

– Grid architecture for online scalability and performance

– Provides server node failover and fault tolerance

� Daily integrity checks

� RAID protection from disk failures

� Available for Avamar software and Avamar Data Store

Avamar Server

Parity across storage nodes

Verified checkpoint

Utility andspare node

9

Avamar Data Store

� Complete EMC backup and recovery solution– Avamar de-duplication software– EMC-certified hardware, fully configured and delivered

� Built-in high availability– Avamar RAIN technology– Spare node, RAID– Redundant power

� Simplifies– Purchase (single vendor, certified hardware)– Deployment (minimizes onsite setup)– Service (single vendor support)

Prepackaged, Preconfigured Deployment Option for Av amar

10

� Avamar Data Store– Individual Avamar Data Store scales to equivalent

of up to 486 TB of traditional backup storage*– Backup media requirement reduced 20–30 times– Each two-node expansion adds the equivalent of

70 TB of traditional backup storage*

� Avamar Data Store, single node– Supports equivalent of up to 37 TB of traditional

backup storage*– Designed for easy deployment at remote offices– Offers fast, local recovery without dependence on

a WAN connection

*Note: Equivalent traditional backup capacity assumptions: 100 percent MS Office file data, weekly full and daily incremental backups, no compression, 10 percent daily change rate, 90-day retention

Avamar Data StoreFlexible Deployment Options

11

Avamar Virtual Edition for VMware

� Industry’s first de-duplication virtual server for backup and disaster recovery

– No other backup/recovery application can encapsulate backup and disaster recovery

� Leverages shared server and storage infrastructure

– Can utilize any storage (SAN, NAS, or DAS)

� Replication (of application and storage) eliminates shipping tapes

– Replicate between Avamar virtual machines, or from Avamar virtual machines to Avamar Data Store or standard Avamar servers

� Facilitates rapid, cost-effective deployment and return on investment

Avamar Server Software Deployed in VMware Virtual M achine (VM)

Hardware

ESX Server

Application

Operating System

Avamar VM1 TB

Operating System

DiskNICMemoryCPU

Avamar VM1 TB

Operating System

12

Data Center

Global De-duplication, Centralized Backup, and Disa ster RecoveryAvamar VMs Can Replicate to Avamar Data Store

Remote Office

Hardware

ESX Server

Application

Operating System

Avamar

Operating System

DiskNICMemoryCPU

Remote Office

Hardware

ESX Server

Application

Operating System

Avamar

Operating System

DiskNICMemoryCPU

Remote Office

Hardware

ESX Server

Application

Operating System

Avamar

Operating System

DiskNICMemoryCPU

Remote Office

Hardware

ESX Server

Application

Operating System

Avamar

Operating System

DiskNICMemoryCPU

AvamarData Store

13

Avamar Data Store Capacity

16 TB10 TB4 TB1 TBDe-duplicated data capacity

NoYes, 2-node increments

Yes, 2-node incrementsNoUpgradeable

24TB15 TB6 TB1.5 TBAvamar Server capacity

111NASwitch (24 port GBE NCS)

YesYesYesNoRack (40u Titan)

111NoSpare Node

111NoUtility Node

YesYesYesNoRAIN

Datacenter, Back office

Datacenter, Back Office

Datacenter, Back Office

Remote Office or Small Data Center

Customer Environment

18-Node12-Node6-NodeSingle NodeAvamar Data Store Models

14

Supported Client Platforms and Applications

10.4.xMac OS X (PowerPC and Intel)

8.2IBM UDB DB2

DART 5.5Data ONTAP 6.3, 6.4, 6.5, 7.0.4, 7.0.5, 7.0.6

NDMP for EMC Celerra and NetApp Filers

9i, 10g, 10gR2Oracle

7.0, 2000Microsoft SQL Server

5.5, 2000, 2003Microsoft Exchange

8, 9SUSE Linux Enterprise Server

8.0, 9.0Red Hat Linux

2.1, 3.0, 4.0Red Hat Enterprise Linux

11.0, 11iV2, 11iV2HP-UX

5.1, 5.2, 5.3AIX

2.6, 7, 8, 9, 10Sun Solaris

XP, NT 4.0, 2000, 2003Microsoft Windows

All versions for supported guests; VMware ESX Server 2.5.3, 3.0.1; VMware Consolidated Backup

VMware

VersionsPlatform

15

Network De-duplication

7,831 GB

9,583 GB

3,265 GB

5,097 GB

3,573 GB

Amount of Primary Data

104.2 GB

80.0 GB

24.2 GB

11.7 GB

6.1 GB

Amount Moved Daily

75:1

120:1

135:1

436:1

586:1

Daily De-dupe Ratio

Mix of Linux file systems and databases

Mix of 20% databases, 80% file systems (Windows and UNIX)

Engineering files on NAS Filers (NDMP backups)

Mix of Windows, Linux, and UNIX file systems

Windows file systems

Data Type

Mileage may vary: customer ratios vs. full backups

16

Remote Office Backup Via WAN

Challenges�WAN blockage�Poor reliability�Decentralized�Untrained IT staff

Central Data Center

WANDe-dupeServerWAN

Data De-dupe

Data De-dupe

Data De-dupe

Advantages�Automated�Encrypted�Centralized �Outstanding ROI

Without Avamar Clients With Avamar Clients

�Target approach requires hardware at every site

17

Traditional Backup vs. EMC Avamar Backup for VMware

� VMware virtualization delivers a new paradigm

� Backup must evolve to keep up

� Traditional backup software– Not optimized for virtualized environments– Lots of redundant data– Long backup windows

� Avamar’s de-duplication software– Efficient daily full backups to meet short backup windows– Optimizes consolidation capabilities– Support for Guest-level, VCB and console backups

18

Traditional Backup Solution Challenges

Backup Server

Disk / Tape

~200% weekly per virtual machine

~200% weekly per virtual machine

Traditional backup moves ~200% of primary data per week!

• Traditional backup is very inefficient – does nothing to eliminate redundant data.

• Redundant data along with weekly full and daily incrementals = up to 200% of primary data is backed up per week!

• Does nothing to solve network, backup server, or disk bottlenecks…

19

Avamar Backup Solution Benefits

Avamar backup only moves ~2% of primary data per week!

• Up to 10X faster backups

• Up to 300:1 less network bandwidth

• All backups stored as “virtual full images”

Only 2% weekly per virtual machine

Avamar Agents

20

Avamar Deployment Options in VMware environments

� Guest Level backup - Avamar agent is installed inside the Virtual Machine

� VMware Consolidated Backup (VCB) - Avamar agent is installed on the VCB proxy

� ESX Service Console backup - Avamar agent is installed on the ESX Service Console

21

Guest (or VM) level backup

� Avamar Agent installed inside each Virtual Machine.

� Most common deployment method; many advantages

� Avamar configuration same as for physical servers

� No advanced scripting or configuration needed.

� Supports Windows, Linux, HP-UX, AIX, Solaris, specific database agents, etc.

Avamar Server

ESX Service Console

Avamar Agents

22

EMC Avamar efficiently protects VM’s:

� Up to 95% reduction in data moved

� Up to 90% reduction in backup times

� Up to 50% reduction in disk impact

� Up to 95% reduction in NIC usage

� Up to 80% reduction in CPU usage

� Up to 50% reduction in memory usage

� All backups stored as “virtual full backups,” ready for immediate restore

– No application of full and incrementals

~2 to 7% weekly

Avamar – Efficient Daily Full Backups

~ 200% weekly

Traditional Backup (Full + Incrementals)

Avamar Benefits for Guest-level Backups

Maintain effective consolidation ratios without over taxing CPU utilization

23

Guest (or VM) level backup (continued)

� Requirements– Virtual Machine Operating System must have a supported Avamar

Agent.

� Advantages– Highest Level of efficiency (Data De-duplication)– Application Backup – SQL, Exchange, Oracle– Allows for partial or file level restores– Easily fits into most existing backup schemes– Requires no advanced scripting or VMware knowledge– Day to day procedures for backing up do not change

� Considerations– Although file level restores are one step, a two-step restore is required

for full system recovery

24

Guest Level Restore� File Level Restore

– Performed as a normal file level restore

– Select the file or files and restore

� Full System Restore

– Requires an OS with an Agent installed.

– Deploy a new Virtual Machine from “Golden Image”

– Power on the Virtual Machine and register it with the Avamar Server

– Perform a redirected restore to the new Virtual Machine

Full System Restore

25

� What is it?– New Backup Solution from VMware– Off-loads CPU workload to a proxy

server

� Consolidated Backup Benefits– Mount VMs across SAN– File system mount for Windows– .vmdk backup only for everything else– Offload CPU, memory, NIC footprint– Reduce backup agents

� Great for the Right Applications

CentralizedData Mover

Centralized file level backup enables easy & reliable data protection

VMware Consolidated Backup (VCB)

26

EMC Avamar & VMware Consolidated Backup

Avamar Supports VCB � Avamar de-duplicates at VCB proxy

server

� Windows: Avamar can backup at the file level through VCB

� All OS: Avamar can de-duplicate .vmdk files both for storage and replication for DR

� Up to 10X faster backups

VCB Proxy Server w/Avamar agent

EMC CLARiiON Arrays

Backup streamSAN

Backup streamAvamar Server

27

VCB and AVIM (Avamar VCB Interoperability Module)

� VMware Consolidated Backup with Avamar– Consolidated Backup utilities and scripts work in conjunction with

Avamar Agent software and AVIM (Avamar VCB Interoperability Module) scripts.

– Avamar Agent, interoperability module, and Consolidated Backup run on the VCB proxy, a physical machine that has Microsoft Windows 2003 installed.

� How AVIM Works– Set of scripts that leverage VCB scripts to snap/mount and un mount

running virtual machines. – Scripts are called before and after the backup process. – Scripts exist for full VM backup and for file level backup (for Windows

Virtual Machines only).

28

VMware Consolidated Backup (Continued)

� VCB Requirements– ESX 3.0.1– Shared storage over a fibre channel SAN– VCB proxy system running Microsoft Windows 2003 SP1. – The VCB proxy needs to be connected to the VirtualCenter

Server (or to a single ESX Server system if you are not using VirtualCenter)

� Avamar Requirements– Avamar Windows 2003 Agent Installed and Configured

29

� Advantages– Backup resources are offloaded to the VCB Proxy – Full image backups of running virtual machines– File level backups for Windows Virtual Machines– Image Virtual Disks are compressed– Consolidation ratios for VMware are optimized

� Considerations– Restore is a multi-step process

– VCB does not support iSCSI or NAS/NFS

– VCB cannot backup Virtual Machines with disk images stored on a storage device that the proxy cannot access

– VCB cannot backup Virtual Disks that are RDM in physical compatibility mode

– VCB cannot backup Virtual Machines that do not have an IP address or a domain name server (DNS) name associated with them

– VCB cannot perform File Level backup of Virtual Machines running Operating Systems other than Microsoft Windows NT 4.0, Windows 2000, Windows XP, Windows XP Professional, or Windows 2003.

VMware Consolidated Backup (Continued)

30

VCB AVIM Restore Process

� Restoring a Virtual Machine Image1. Restore the .vmdk to the proxy server

Copy the .vmdk file to the ESX serverRun an import command

2. Restore the .vmdk to the ESX ServerRun an import command� Note: This requires an Avamar Agent installed on the ESX Server

� Restoring from a File Level backup (windows only)1. Select files for restore on the Avamar server

Restore to the VCB ProxyCopy to the target virtual machine

2. Install an Avamar agent on the target virtual machinePerform a redirected restore directly from the Avamar server to the target virtual machine

31

ESX Console Backup

� Avamar Agent installed on the Console OS (COS).

� Requires advanced configuration to ensure that backups will not impact critical resources

� How ESX Service Console Backup Works

� 2 methods – Use vcbMount to

create a snapshot of the a running virtual machine for backup

– Suspend a Virtual Machine and back it up directly

Avamar Server

ESX Service Console

32

ESX Console Backup (Continued)

� Requirements– Avamar Linux Agent installed and configured– Additional disk space for virtual machine snapshots

� Advantages– Virtual Machine Image Level backups without VCB– No Proxy or SAN required

� Considerations– No file level backup– Restoring is a two-step process– Advanced Configuration: without proper scheduling and setup, backup

jobs can impact system resources and running virtual machines

Method 2 only– Virtual Machine must be powered off or suspended before backup starts– Virtual Disk Images are not compressed (empty space is processed)

33

ESX Console Restore

� Method 1 - Snapshot– Restore the Virtual Machine to the ESX Server– Use vcbRestore to restore the Virtual Machine to the ESX Server

� Method 2 - Suspend– Restore the Virtual Machine to the ESX Server– Register the Virtual Machine

34

Spørgsmål ?