Configuration Guide:Best Practices with HP Storageand VeeamModern Data ProtectionBuilt for VirtualizationNovember, 2013

Configuration Guide: Best Practices with HP Storage and VeeamContentsIntended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Veeam Backup & Replication overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Veeam VMware integration with HP StoreVirtual and HP StoreServ . . . . . . 5Veeam Explorer for Storage Snapshots . . . . . . . . . . . . . . . . . . . . . . . . 5Backup from Storage Snapshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Moving backups for longer retention - Backup Copy jobs. . . . . . . . . . . . . . . 7Achieving best practices: VM backup and recovery . . . . . . . . . . . . . . . . . . . . 7Adding Veeam to your virtual infrastructure . . . . . . . . . . . . . . . . . . . 8Configuring storage infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . 11Configuring backup jobs using DAS- and SAN-basedbackup repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Configuring backup jobs when using the HP StoreOnce BackupSystem as a backup repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Configuring Veeam backup servers and backup proxies. . . . . . . . . 19Summary of Veeam Backup & Replication Editions and Features. . . . . . . . 22Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23About Veeam Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Configuration Guide: Best Practices with HP Storage and VeeamIntended audienceThis guide is intended for those involved in the design, acquisition andimplementation of data protection solutions for vSphere and Hyper-V virtualmachines (VMs) on shared SAN storage and/or NAS. It was written for ITgeneralists and specialists alike, whether they need to back up a dozenor hundreds of VMs. The audience includes but is not limited to: SystemsAdministrators responsible for servers, hypervisors, storage, and backup;Sales Engineers; Systems Engineers; Solution Architects; Professional ServicesEngineers; and Consultants. The technical information contained herein isintended as a starting point for designing and implementing a VM dataprotection solution. This backup and replication solution has been tested andcertified jointly by HP and Veeam .Veeam Backup & ReplicationoverviewVeeam Backup & Replication is one of the most powerful solutions for VMbackup, replication and recovery in VMware vSphere and Microsoft Hyper-Venvironments. With Veeam Backup & Replication, VMs can be backed up todisk, archived to low-cost storage and replicated from one host to another.Recovery of VMs can occur in a matter of minutes using Veeam’s patentedtechnology integrated with HP Storage.The major components of Veeam Backup & Replication consist of amanagement server, proxy servers, backup repository servers and disk-basedbackup repositories. The backup proxy servers are Windows-based installations.The backup repositories can be Windows or Linux based, network attachedstorage systems or tape. These resources can be virtual or physical dependingupon the storage and network topology, desired throughput of backup andrecovery data streams, as well as the available server resources.3

Configuration Guide: Best Practices with HP Storage and VeeamVeeam backup architectureThe following diagram represents a typical example of the Veeam replicationarchitecture with distributed backup proxies at the source (production)and target (recovery) locations. VM-level replication occurs from one ESXor Hyper-V host to another of the same type. It does not require identicalhardware from source to target nor does it require additional Veeam licensingon the target. Veeam VM replication is covered in detail in the Veeam Backup &Replication User’s Guides for VMware and Hyper-V.Veeam replication architecture4

Configuration Guide: Best Practices with HP Storage and VeeamVeeam VMware integration with HPStoreVirtual and HP StoreServVeeam Explorer for Storage SnapshotsVeeam integrated HP StoreServ Virtual Copy (SAN snapshot) & HP StoreVirtualsnapshot technology to create Veeam Explorer for Storage Snapshots and Backupfrom Storage Snapshots. This integration enables a VM Recovery Point Objective(RPO) of 30 minutes or less, automated recovery in minutes and superior backupperformance which is non-disruptive to production VM workloads.Veeam Explorer for Storage Snapshots integrates Veeam fast recovery with theefficiency of HP StoreServ Virtual Copy and HP StoreVirtual snapshots. Oncea SAN snapshot of a vSphere VMFS volume is created on the primary storagesystem, it becomes visible in the Veeam console. In a restore scenario, VeeamExplorer for Storage Snapshots mounts VMFS volumes from the arrays and usesthe Veeam recovery engine for restore tasks.Veeam Explorer for Storage Snapshots provides fast recovery of VMs, Windowsor Linux guest files, SharePoint and Exchange items (messages, meetings, etc.)from the snapshots on primary storage. SAN snapshots can enable VM RPOs ofas little as 5 minutes with HP StoreServ Virtual Copies and 30 minutes with HPStoreVirtual snapshots.vSphereVeeam Explorer for Storage Snapshots5

Configuration Guide: Best Practices with HP Storage and VeeamNOTE: HP 3PAR StoreServ storage systems require a Virtual Copy license toenable storage snapshot functionality.Backup from Storage SnapshotsVeeam Backup from Storage Snapshots can reduce backup windows byhours – utilizing HP StoreVirtual snapshots and HP StoreServ Virtual Copiesas the source for creating full and incremental backup images. Without theuse of storage snapshots, VM backup images must be created using VMwaresnapshots alone. When VMware snapshots are used to backup heavily utilizedVMs, performance of the hosts, storage system, VM and application can beseriously impacted. With Backup from Storage Snapshots, the hypervisorsnapshot is used briefly to create an application-consistent state for the storagesnapshot. The hypervisor snapshot is then released after the storage snapshotis taken. This hardware-level storage snapshot then becomes the source of theVM backup, independent of the production VM.The storage snapshot is read by a Veeam proxy as the backup source. TheVM’s CBT map is queried for fast incremental backup of quiesced VMs fromthe snapshot clone to disk without mounting the storage snapshot to thehypervisor or registering the VM with the host. The use of CBT for storagesnapshot backup sources is unique to the industry and is responsible for thedramatic reduction in backup windows when deploying HP Storage and Veeam.6

Configuration Guide: Best Practices with HP Storage and VeeamNOTE: Veeam Backup from Storage Snapshots is part of the all-inclusiveEnterprise Plus Edition of Veeam Backup & Replication. HP 3PAR StoreServstorage systems require a Virtual Copy license to enable storage snapshotfunctionality.Moving backups for longer retention Backup Copy jobsBackup images can be copied to different types of storage to achieve differentobjectives. A backup might first be written to fast storage (DAS or SAN-based)then moved to less expensive, higher capacity storage after a specific period oftime. This data movement can be automated via Veeam job settings includingBackup Copy job. A job can be automated to back up VMs to a specific locationwith a predetermined number of restore points based on the job’s retentionpolicy before the backup is moved to longer-term storage.Achieving best practices: VM backupand recoveryVeeam Backup & Replication can be architected for multiple tiers of data protection.A VM backup image file is written to disk to create the first copy of a virtualmachine. VM replicas are used to create a second copy of a VM off premises.Recovery of VMs, guest files as well as SharePoint and Exchange items from HP7

Configuration Guide: Best Practices with HP Storage and VeeamStoreVirtual and HP StoreServ SAN snapshots can be achieved directly fromproduction storage with a hardware snapshot copy as well. For longer retentionperiods, backup image files can be copied off premises using tape and to cloudproviders based on OpenStack or other object-based storage services.Tradeoffs occur with different classes of backup storage. Deduplication appliancesprovide the highest level of data reduction and the longest retention periods at theexpense of longer VM Recovery Time Objectives (RTOs). The performance of keyVeeam Backup & Replication vPower features, such as Instant VM Recovery andSureBackup can also be impacted. Primary storage systems provide a balance ofscalability and fast recovery performance (low RTO) versus a more capacity-efficientdeduplication appliance.Administrators can avoid the classic backup and recovery tradeoff that occursbetween efficient storage with long retention capability and fast VM recovery inone of two ways. With HP StoreServ and HP StoreVirtual storage, fast recoveryfrom production storage snapshots may be achieved with Veeam Explorer forStorage Snapshots and achieve the high-efficiency and long retention that ispossible with HP StoreOnce Backup Systems. If Veeam Explorer for StorageSnapshots is not an option, a backup can be written to fast backup storage(DAS or SAN) to satisfy a short-term retention and recovery schedule prior tobeing written to longer-term storage such as a deduplication appliance, tapeor cloud storage. This tiered backup approach can be easily automated in theVeeam backup job settings.Adding Veeam to your virtual infrastructureNOTE: For detailed instructions on installation and configuration best practicesdownload the Veeam Backup and Replication user guides for Hyper-V orVMware and Veeam Best Practices Guide for VMware.Configuring backup infrastructureInstall Veeam Backup & Replication on a Windows system. The user guideoutlines the system requirements, but both physical system and VMinstallations are supported. Download the latest version of Veeam Backup &Replication from: default installation creates a backup folder (c:\Backup) and installs theVMware backup proxy role by default so that VMware VMs can be backedup to this Windows server or VM. The VM backup infrastructure is scaled byadding additional virtual and physical Windows proxy servers to move data,disk-based backup storage resources in the form of CIFS shares, LUNs andLinux paths as backup repositories.8

Configuration Guide: Best Practices with HP Storage and VeeamNOTE: The Veeam Management Server should have a minimumconfiguration of one modern 64-bit capable processer (minimum fourcores) and 4 GB of RAM when running the supplied SQL Express instance(standalone SQL servers can be used).Add vCenter, SCVMM or host informationServers and VMs used for proxies and backup repositories must first be addedto Managed Servers via the Add Server wizard. To add a backup proxy to thebackup infrastructure, a Windows server already added to the list of managedservers should be assigned to the role.NOTE: Proxy and repository servers should be configured with at least onemodern x86/x64 processor (minimum two cores); 2 GB RAM; 200 MB disk space.Adding backup repositoriesYou can assign the role of a backup repository to any Windows or Linux serveradded to the list of managed servers in Veeam Backup & Replication, or to anyshared CIFS folder, to which the backup server has access.9

Configuration Guide: Best Practices with HP Storage and VeeamDetecting tape librariesVeeam Backup & Replication will automatically import tape resourceswith device-specific OEM Windows drivers which are visible to the Veeammanagement server via Windows Device Manager.NOTE: It is important for both the changer devices and the tape drive(s) tobe visible in Windows Device Manager.10

Configuration Guide: Best Practices with HP Storage and VeeamTape libraries and media will automatically be displayed in the BackupInfrastructure view.Configuring storage infrastructureAdding HP production storage for hardware-assisted backup and recoveryof VMware VMsWhen using HP StoreVirtual and HP StoreServ storage, SAN snapshots can beused for hardware-assisted backup and recovery of VMs and guest files, as wellas Microsoft SharePoint and Exchange items. Add the management consoleaddress and credentials for automatic importation of VMFS volumes, snapshotsand associated VMs. To utilize hardware-assisted backup with storage snapshots,the Veeam Backup Proxy must have, at minimum, read access to vSphere VMFSvolumes on the SAN. This is not a requirement for hardware-assisted recovery.11

Configuration Guide: Best Practices with HP Storage and VeeamNOTE: For support of Veeam Explorer for Storage Snapshots with HPStoreVirtual storage, the minimum version of LeftHand OS (previously SAN/iQ) is 9.5.01.Configuring backup jobs to use HP storage for hardware-assisted backupof vSphere VMsBy default, Veeam Backup & Replication jobs are set to use storage snapshotsas the method of retrieving vSphere VM data. However, it is possible to enableor disable this capability manually by right clicking on a backup or replicationjob and clicking Edit, followed by Storage, and choosing the Advanced button.You will see a tab labeled Storage Integration.Configuring backup jobs using DAS- and SANbased backup repositoriesPrimary storage arrays and direct-attached storage in servers offer goodrandom I/O performance characteristics which is required for recovering VMsfast with object-level granularity. The trade-off with an online primary storagearray versus a nearline backup appliance with deduplication is fast recoveryand granular restoration at the expense of lower storage efficiency and shorterretention periods. Backup appliances are purpose-built to offer a lot of bulkstorage for longer retention and overall lower cost per GB at the expense oflonger recovery times when compared to general-purpose primary disk arrays.12

Configuration Guide: Best Practices with HP Storage and VeeamThe mode of incremental backup, source-side deduplication and compressioncan all be configured by clicking the Advanced button in the Storage stepof the New Backup Job or Edit Backup Job wizards. Deduplication is alwaysrecommended regardless of the choice of backup target device to minimizethe backup image size and reduce network traffic. The settings in the dropdown lists under the Backup and Storage tabs display detailed descriptions forparticular use cases when selected.Reversed incremental backup modeSetting compression for backup jobs using SAN and DASThe Edit Backup Jobs wizard Storage tab provides the configuration settingsfor compression. The following example shows compression enabled, whichis the recommendation for backing up to primary disk arrays. The setting inthis example is for optimal compression, which strikes a balance betweencompression (which reduces network traffic during backup) and the CPU loadon the backup proxy. A compression setting of “best” yields the smallest backupimage and uses less network bandwidth. However, the wizard recommends asix-core processor in the backup proxy.Setting block size for backup jobs using SAN and DASThe Storage tab optimizations, configured for a local target in this example,determine the block size used for backup and deduplication. The block sizescan be: 256 KB for a backup target over a WAN; 512 KB for backup over a LAN;or 1024 KB for backup targets located directly on the backup server. For DASand SAN storage the local target setting is recommended.13

Configuration Guide: Best Practices with HP Storage and VeeamNote: To launch the Advanced Settings dialog, click on the Advanced buttonin the Edit Backup Jobs wizard. then open the Storage tab in the AdvancedSettings dialog to see the configuration options. When you select an optionfrom the drop-down list, a detailed description of the appropriate use caseis displayed, ensuring a simple and successful deployment experience.Best practices for maximizing VM recovery with HP Storage primarystorage subsystems:Design your disk array for fast random read I/O profiles to better enable Veeam’sInstant VM Recovery. Mounting NFS exports on a Linux server can improve RTOsup to 25% in many cases. Enable deduplication and compression with VeeamBackup & Replication in order to reduce backup traffic on the network and toachieve maximum space savings of the backup images.Recommended Backup Mode Reversed Incremental14

Configuration Guide: Best Practices with HP Storage and VeeamConfiguring backup jobs when using the HPStoreOnce Backup System as a backup repositorySetting compression for backup jobsThe settings for compression are selected from the Advanced tab of the New/Edit Backup Jobs wizard’s Storage screen. A compression setting of Optimalbalances the CPU load on the proxy server vs. the backup size and the amountof network bandwidth used. In this example, Compression is set to None, whichoptimizes the HP StoreOnce deduplication ratio at the expense of increasednetwork traffic during backup. The following section explains how to reducenetwork traffic while optimizing deduplication.Setting block size for backup jobsFor HP StoreOnce Backup Systems presenting CIFS shares (or NFS Exports), usethe LAN target setting under Advanced Settings.15

Configuration Guide: Best Practices with HP Storage and VeeamBest practices for maximizing VM backup capacity and retention with HPStoreOnce:Enable deduplication for both Veeam Backup & Replication and the applianceto achieve maximum network throughput.Set your backup repository to decompress backup images before they arewritten to disk or disable compression for the backup job. Compressing VMimages prior to backing them up to a deduplication appliance reduces backuptraffic on the network; however, it will negatively impact the appliance’s abilityto deduplicate the backup image on disk. This is not a bad thing: while dedupehas already taken place, HP StoreOnce Backup Systems will not report theconsolidated ratio between Veeam and the appliance.Recommended Backup Mode Forward incrementalThe type of incremental backup as well as source-side deduplication andcompression can be configured in the backup job wizard (click the Advancedbutton). Deduplication is always recommended regardless of the choice ofbackup target device. Select a setting from the drop-down list (Storage tab) todisplay a detailed description for particular use cases. The following exampleshows the recommendation for disabling compression on a backup/dedupeappliance. There is a low compresssion (10 -15%) setting called DedupeFriendly which can be used. The disclaimer that no two data sets are alike mustbe heeded. Always test alternate settings where possible.16

Configuration Guide: Best Practices with HP Storage and VeeamThe selection for the type of incremental backup mode is made in the Backuptab of the Advanced Settings dialog box. Incremental backup mode is therecommended configuration when backing up to an HP StoreOnce BackupSystem as shown below.Incremental backup mode, also known as forward incremental, can beconfigured for forever-incremental backup using synthetic full backups or youcan elect to run periodic full backups. A synthetic backup is simply a seriesof incremental backups rolled into a previous full backup to create a currentsynthetic “full” backup.Data block decompression and data block alignment settings for HPStoreOnce Backup SystemsThis section describes how to enable source-side compression to reduce networktraffic and then decompress prior to writing the backup image to the target. Thedecompression and alignment settings are found in the New Backup Repositorywizard (click the Advanced button on the Edit Backup Repository wizard). For HPStoreOnce Backup Systems, select the checkbox for Decompress backup data blocksbefore storing. Leave the Align backup file data blocks checkbox unselected, asStoreOnce deduplication uses a variable block size.17

Configuration Guide: Best Practices with HP Storage and VeeamBest practices for maximizing capacity and retention with HP StoreOncewith fast VM recovery:Fast recovery of a VM is predicated on a backup target’s ability to handlerandom I/O, whether or not “rehydration” of deduplicated data is required. Ifcritical VMs need quick and granular recovery capability, consider backing up toa physical backup proxy server with locally attached disks or a primary storagearray to complement the appliance. Low-cost storage in a proxy or a diskarray can provide a low-cost repository with a much lower RTO than a backupappliance. Once the desired retention period is met to accommodate fastrecovery the backup can then be moved via the Backup Copy job function tolonger-term storage. Fast recovery can also be automated using HP StoreVirtualsnapshots and HP StoreServ Virtual Copies of production VMFS volumes withVeeam Explorer for Storage Snapshots.18

Configuration Guide: Best Practices with HP Storage and VeeamConfiguring Veeam backup servers and backupproxiesIn order to achieve the fastest possible backup (e.g. the shortest backupwindow) and the fastest possible recovery (e.g. the shortest RTO), the backupinfrastructure resources must be taken into consideration. Three factors directlyaffect the performance and effectiveness of this infrastructure: production(e.g. source) storage performance; backup (e.g. target) performance; and theperformance of the backup management and proxy servers.For maximum performance in a direct SAN environment, physical hardwareproxies with direct FC or iSCSI connectivity are ideal. Virtual hardware canachieve acceptable performance in most environments and can actually be thebest option in some cases. There are several advantages and disadvantages toconsider when deciding between physical and virtual servers.Physical server proxyPros Provides best throughput, especiallywhen using direct SAN access for FCand iSCSI storageCons Requires investment in additionalhardware Multi-core processors can run moresimultaneous jobs meaning less proxiesto manage Requires more complex storage setupfor direct SAN access and ongoingconfiguration as storage environmentevolves No added multipathing or CPU load onvirtual infrastructure Provides limited advantages for NFSenvironments Easier and more robust recovery fromcatastrophic failures involving failedvirtual infrastructure Target storage can be attached directlyto physical servers19

Configuration Guide: Best Practices with HP Storage and VeeamVirtual server proxyPros Can use existing virtual machines Leverages existing infrastructure Requires no additional hardware Generally the highest-performanceoption for NAS and DAS datastores Simpler setup and configurationCons Virtual proxies are limited by vCPUresources Multiple proxies in the infrastructure canhave significant impact on host resources Generally requires more proxies to achievethe same throughput as physical Target storage typically must be accessedvia network which can be a potentialbottleneckThe following recommendations are provided as starting points; significantvariation can occur based on environmental factors. We assume typicalenvironments with average change rates of 2-5% daily and an eight-hourbackup window. Virtual proxy – one (1) four-vCPU VM for every 100 VMs or 10TB of data.This assumes two jobs each producing approximately 50MB/s each for fullbackups. Physical proxy – one 16 core physical system for every 400 VMs or 40TB ofdata. This assumes physical SAN connectivity and eight concurrent jobs eachproducing 100MB/s each for full backups.NOTE: You must have sufficient network bandwidth available to the physicalserver to achieve this level of performance. High-speed interconnects suchas 8Gb Fibre Channel and 10Gb Ethernet are highly recommended.Deploying test proxies and running jobs to measure throughput is essentialto determine more accurate numbers for the specific environment. For physical proxies, use SAN Access mode. Remember, SAN Access moderequires the physical server to be provisioned with access to the storagesubsystem, either via Fibre Channel or iSCSI. For virtual proxies, use Hot-Add transport mode. Remember, Hot-Add moderequires the proxy server be located on a VM in the same cluster/host as theVM you are backing up. Use Network transport mode only when other modes are not available.20

Configuration Guide: Best Practices with HP Storage and VeeamIf a datastore cannot be accessed by Direct SAN or Hot-Add mode by anyproxy, then the system will use Network mode to retrieve the VM disks via theESXi management interface. When using Network mode, Veeam Backup &Replication attempts to locate a proxy that is on the same subnet as the ESXimanagement interface to reduce the risk of crossing slow, layer-3 networks. Inthis mode, the VM data is transferred over the IP management network so it isimportant that this network has the ability to handle sustained high-speed datatransfer without interfering with normal management traffic.NOTE: If you plan to deploy proxy server(s) on existing VM(s), and a virtualproxy is set-up to backup or replicate itself, be aware that CBT will bedisabled and the job will automatically failover to Network mode. This canhave a noticeable impact on backup performance.Proxy servers are the real workhorse of Veeam Backup & Replication as suchthey consume considerable CPU resources. In general, assuming defaultcompression options, it is recommended that one CPU be available for everyactive job: One (1) core for every job (physical servers) and one (1) vCPUs for everyactive job (virtual servers). At least four (4) vCPUs allocated for virtual proxies to leave resourcesavailable for other server functions.For memory sizing, assume the proxy server’s data mover agent will use themaximum memory (1.7GB), leaving additional headroom to be safe. Therefore,the requirement is 2GB of RAM per concurrent process as a minimum.Best practices for increased backup repository performance:Use the fastest possible disk and mirrored RAID levels. Fast VM recoverywill necessitate a disk backup target with good random read capability suchas a disk array (i.e. P2000 MSA, HP StoreVirtual, EVA, HP StoreServ, etc.) orDirect-Attached Storage (i.e. SMART Array P421/BBWC and D2600 JBODenclosures). Fast backup targets can be deployed using existing DAS orSAN resources provided they’re adequately sized (RAM; multi-core CPUs;number of HDDs and RPM speed; Gb speed networking).21

Configuration Guide: Best Practices with HP Storage and VeeamSummary of Veeam Backup &Replication Editions and Features:VeeamBackup &ReplicationStandardEditionVeeam Explorer for StorageSnapshots Snapshot-assisted recovery VeeamBackup &ReplicationEnterpriseEdition Backup from Storage Snapshots Exchange 2010/2013 messagelevel recovery Veeam Explorer for MicrosoftExchange Direct recovery to mailbox1Veeam Explorer for MicrosoftSharePoint2Native tape support3 Snapshot-assisted backupVeeam Explorer for MicrosoftExchangeVeeamBackup &ReplicationEnterprisePlus Edition U-AIR (Universal ApplicationItem Recovery) Exchange 2003/2007 messagelevel recovery SQL and Active Directory objectlevel recovery1. Veeam Backup & Replication Enterprise Plus Edition also supports dissimilar mailbox restore targets (e.g. foreignmail domain, Office 365, etc.).2. All editions support restore via save, send and export. Enterprise and Enterprise Plus editions also supportrestore to original location.3. All editions support copying Windows, Linux and VM backup files to tape. Enterprise and Enterprise Plus editionsadd tight integration with backup jobs and support full tracking of VMs and restore points on tape.22

Configuration Guide: Best Practices with HP Storage and VeeamResourcesVeeam Backup and Replication User Guide for Hyper-V or VMwareVeeam Community Forums – Backup and ReplicationHP Storage Landing PageHP-VEEAM Landing Page on Veeam.comHP Business Support CenterVeeam SupportVeeam Community Forums23

Configuration Guide: Best Practices with HP Storage and VeeamAbout Veeam SoftwareVeeam is Modern Data Protection - providing powerful, easy-to-use andaffordable solutions that are Built for Virtualization and the Cloud. VeeamBackup & Replication delivers VMware backup, Hyper-V backup, recovery andreplication. This #1 VM Backup solution helps organizations meet RPOs andRTOs, save time, eliminate risks and dramatically reduce capital and operationalcosts. Veeam Backup Management Suite combines Veeam Backup &Replication and Veeam ONE into a single integrated solution to protectvirtualization investments, increase administrator productivity and help mitigatedaily management risks. Veeam Management Pack (MP) extends enterprisemonitoring to VMware through Microsoft System Center. Veeam also providesfree tools for the virtualization community.Founded in 2006, Veeam is privately-owned and has been profitable since 2009.Veeam currently has over 20,000 ProPartners and 80,000 customers worldwide.Veeam’s global headquarters are located in Baar, Switzerland and has officesthroughout the world. To learn more, visit

Configuration Guide: Best Practices with HP Storage and VeeamModern Data ProtectionBuilt for VirtualizationPowerfulEasy-to-UseVeeam Backup & Replication#1 VM Backup for

backup, replication and recovery in VMware vSphere and Microsoft Hyper-V environments . With Veeam Backup & Replication, VMs can be backed up to disk, archived to low-cost storage and replicated from one host to another . Recovery of VMs can occur in a matter of minutes using