Backup og De-dup i et VmWare miljø EMC Avamar. Frank Simonsen Systems Engineer

Transcription

1 Backup og De-dup i et VmWare miljø EMC Avamar Frank Simonsen Systems Engineer 1

2 EMC Next Generation Backup and Archive EMC Backup, Recovery and Archive Solutions Services Assessment, Implementation File Server Assessment, Exchange Server Assessment, Backup Assessment Software Intelligent Archiving Xtender, DiskXtender, Backup and Recovery NetWorker Avamar HomeBase Analytics Backup Advisor Classification Infoscape Hardware Active Archive Centera Backup to Disk Disk Library Tape Libraries 2

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 3

4 Global De-duplication: PowerPoint Example ❶ First Instance Data Center Remote Site 1 ❷ Duplicate Instance Remote Site 2 ❸ Modified Instance Company_Overview.ppt Company_Overview.ppt Company_Overview.ppt A B A B A B C D C D C D A Only unique data segments are backed up B C D Data already backed up, so only unique IDs stored (20 byte pointers) E New data segment identified and backed up A B C D E De-duplication Server (stored backup data) 4

5 Backup De-duplication Cumulative TB Traditional Backup v. EMC Avamar Traditional Backup vs. EMC Avamar Total Storage - 10TB MS Office file data (Traditional Cumulative = weekly fulls + daily Media incrementals; Required EMC Avamar = daily fulls) weeks 8 weeks Weeks Avamar Avamar makes backup to disk more economical Traditional Backup Traditional 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; EMC Avamar = daily fulls) 5

6 Unique Value Proposition Remote/Branch Office 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? VMware Environments 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)? LAN-attached File Servers 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? Yes? Yes? Yes? 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. 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 6

7 Deployment Flexibility A Avamar Software Agent Large Remote Site A Small Remote Site Primary systems Avamar server (ENCRYPTED) (ENCRYPTED) A Avamar agent only on primary systems A Data Center WAN Remote Recovery Site A Primary systems Primary systems (ENCRYPTED) (ENCRYPTED) Avamar server Avamar server Tape Vault 7

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 Parity across storage nodes Utility and spare node Avamar Server Verified checkpoint 8

9 Avamar Data Store Prepackaged, Preconfigured Deployment Option for Avamar 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) 9

10 Avamar Data Store Flexible Deployment Options Avamar Data Store Individual Avamar Data Store scales to equivalent of up to 486 TB of traditional backup storage* Backup media requirement reduced 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 10

11 Avamar Virtual Edition for VMware Avamar Server Software Deployed in VMware Virtual Machine (VM) 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 Application Operating System CPU Memory ESX Server Hardware Avamar VM 1 TB Operating System Avamar VM 1 TB Operating System NIC Disk 11

12 Avamar VMs Can Replicate to Avamar Data Store Global De-duplication, Centralized Backup, and Disaster Recovery Remote Office Application Avamar Operating System Operating System Data Center Remote Office Application Avamar Operating System Operating System ESX Server Hardware ESX Server Hardware CPU Memory NIC Disk CPU Memory NIC Disk Remote Office Remote Office Application Avamar Application Avamar Operating System Operating System Operating System Operating System ESX Server Hardware ESX Server Hardware CPU Memory NIC Disk Avamar Data Store CPU Memory NIC Disk 12

13 Avamar Data Store Capacity Avamar Data Store Models Single Node 6-Node 12-Node 18-Node Customer Environment Remote Office or Small Data Center Datacenter, Back Office Datacenter, Back Office Datacenter, Back office RAIN No Yes Yes Yes Utility Node No Spare Node No Rack (40u Titan) No Yes Yes Yes Switch (24 port GBE NCS) NA Upgradeable No Yes, 2-node increments Yes, 2-node increments No De-duplicated data capacity 1 TB 4 TB 10 TB 16 TB Avamar Server capacity 1.5 TB 6 TB 15 TB 24TB 13

14 Supported Client Platforms and Applications Platform Microsoft Windows Microsoft Exchange Microsoft SQL Server Oracle NDMP for EMC Celerra and NetApp Filers Sun Solaris AIX HP-UX Red Hat Enterprise Linux Red Hat Linux Mac OS X (PowerPC and Intel) SUSE Linux Enterprise Server VMware IBM UDB DB2 Versions XP, NT 4.0, 2000, , 2000, , i, 10g, 10gR2 DART 5.5 Data ONTAP 6.3, 6.4, 6.5, 7.0.4, 7.0.5, , 7, 8, 9, , 5.2, , 11iV2, 11iV2 2.1, 3.0, , x 8, 9 All versions for supported guests; VMware ESX Server 2.5.3, 3.0.1; VMware Consolidated Backup

15 Network De-duplication Mileage may vary: customer ratios vs. full backups Data Type Amount of Primary Data Amount Moved Daily Daily Dedupe Ratio Windows file systems 3,573 GB 6.1 GB 586:1 Mix of Windows, Linux, and UNIX file systems 5,097 GB 11.7 GB 436:1 Engineering files on NAS Filers (NDMP backups) 3,265 GB 24.2 GB 135:1 Mix of 20% databases, 80% file systems (Windows and UNIX) 9,583 GB 80.0 GB 120:1 Mix of Linux file systems and databases 7,831 GB GB 75:1 15

16 Remote Office Backup Via WAN Without Avamar Clients With Avamar Clients Data De-dupe Central Data Center WAN Data De-dupe WAN De-dupe Server Challenges WAN blockage Poor reliability Decentralized Untrained IT staff Target approach requires hardware at every site Data De-dupe Advantages Automated Encrypted Centralized Outstanding ROI 16

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 17

18 Traditional Backup Solution Challenges ~200% weekly per virtual machine Backup Server ~200% weekly per virtual machine Disk / Tape 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 18

19 Avamar Backup Solution Benefits Avamar Agents Only 2% weekly per virtual machine 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 19

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 20

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 Agents ESX Service Console Avamar Server 21

22 Avamar Benefits for Guest-level Backups 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 Maintain effective consolidation ratios without All backups over taxing stored CPU as virtual utilization full backups, ready for immediate restore No application of full and incrementals Traditional Backup (Full + Incrementals) ~ 200% weekly Avamar Efficient Daily Full Backups ~2 to 7% weekly 22

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 23

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 24

25 VMware Consolidated Backup (VCB) Centralized Data Mover 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 Centralized file level backup enables easy & reliable data protection 25

26 EMC Avamar & VMware Consolidated Backup VCB Proxy Server w/ Avamar agent SAN EMC CLARiiON Arrays Backup stream Backup stream 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 Avamar Server 26

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). 27

28 VMware Consolidated Backup (Continued) VCB Requirements ESX 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 28

29 VMware Consolidated Backup (Continued) 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

30 VCB AVIM Restore Process Restoring a Virtual Machine Image 1. Restore the.vmdk to the proxy server Copy the.vmdk file to the ESX server Run an import command 2. Restore the.vmdk to the ESX Server Run 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 Proxy Copy to the target virtual machine 2. Install an Avamar agent on the target virtual machine Perform a redirected restore directly from the Avamar server to the target virtual machine 30

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 ESX Service Console Avamar Server 31

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) 32

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 33

34 Spørgsmål? 34