Docstoc

VMware Backup and Recovery Veeam Backup _ Replication vs

Document Sample
VMware Backup and Recovery Veeam Backup _ Replication vs Powered By Docstoc
					                                                                   Customer Value




                         openBench Labs




                         PERFORMANCE
                         Analysis: VMware Backup and Recovery
Data Center Management




                                          Veeam Backup & Replication v5
                                                       vs.
                                          Symantec Backup Exec 2010 R2




                                                                Commissioned by
PERFORMANCE
Analysis: VMware Backup and Recovery
                              Veeam Backup & Replication v5
                                           vs.
                              Symantec Backup Exec 2010 R2

                                                      Author: Jack Fegreus, Ph.D.
                                                               Managing Director
                                                                 openBench Labs
                                                      http://www.openBench.com
                                                                   April 21, 2011




            Jack Fegreus is Managing Director of openBench Labs and consults through
         Ridgetop Research. He also contributes to InfoStor, Virtual Strategy Magazine,
         and Open Magazine, and serves as CTO of Strategic Communications.
         Previously he was Editor in Chief of Open Magazine, Data Storage, BackOffice
         CTO, Client/Server Today, and Digital Review. Jack also served as a consultant
         to Demax Software and was IT Director at Riley Stoker Corp. Jack holds a Ph.D.
         in Mathematics and worked on the application of computers to symbolic logic.
                                                                        Table of Contents




Table of Contents

        Test Brief                                                 04
           Real Issues With Virtual Machine Data Protection        04
           Recovery-Centric Test Plan                              05


        Infrastructure Capabilities                                08
           Performance Foundation                                  08
           Isolating I/O Bottlenecks                               08


        Backup Performance                                         10
           Test 1: Agentless Backup                                13
           Test 2: Backup File Reduction                           15
           Test 3: Single Execution of All Options                 17


        Recovery Performance                                       21
           Test 4:   Direct VM Recovery From a Backup File         22
           Test 5:   Automated Recovery Verification               26
           Test 6:   Multi-OS File-Level Recovery                  29
           Test 7:   Application-Independent Item-Level Recovery   30
           Test 8:   Point-in-Time VM Replication                  32

        Test Summary                                               34




                                                                                            03
                                                                                                           Test Configuration




Test Brief
                          he gulf between IT’s expectations of the benefits that can be derived
                   “T     from a virtual infrastructure and the reality of the lagging data
                   protection measures put into place highlights the fact that a highly flexible
                   host infrastructure does not solve the knotty issues IT faces trying to
                   protect the applications and data running on VMs.”

                        REAL ISSUES WITH VIRTUAL MACHINE DATA PROTECTION
                                                                          In a 2010 Symantec datacenter
  U  NDER ESTT      : VM D           -P
                                  ATA ROTECTION EATURES  F            survey, IT sites without a virtual
                                                                      infrastructure project planned or in
             Veeam Backup & Replication v5 Software                   progress represented just 18% of the
                    Symantec Net Backup 2010 R2                       1,780 sites surveyed. On the other
1) Agent-less Backup Configuration: Test basic backup performance and hand, roughly half of the sites with a
   functionality along with any dependencies on the need to license,  virtual operating environment were
   manually deploy, or manage agents on either VMs or vSphere hosts.
                                                                      planning to expand the use of virtual
2) Image File Reduction via Data Compression and Deduplication: Both  machines (VMs) by running mission-
   data compression and data deduplication can be applied to image
                                                                      critical database-driven applications.
   backups to reduce backup file requirements.
3) Single Execution for Multiple Backup and Recovery Options: Easy-
                                                                                 Nonetheless, Symantec’s 2010
   to-implement backup and recovery operations with all recovery options,
                                                                             Disaster Recovery (DR) Plan survey
   including the whole VM, guest VM files and VM application items,
   available from a single backup.                                           indicates that IT regularly backs up
                                                                             only 56% of the applications and data
4) Direct VM Recovery from a Backup File: Instantly start VM recovery
   from a backup file without rehydrating data, and complete the process     running on VMs. What’s more, DR
   with Storage vMotion, VM cloning, or Veeam’s VM Copy wizard, which        plans typically exclude 60% of virtual
   uses Veeam’s FastSCP.                                                     servers at a site. As for data and
5) Automated Recovery Verification: Perform a test restore for every         applications backed up under the
   backup file as a standard backup validation test.                         umbrella of a DR plan, those backup
6) File-Level Recovery: VM image-level backups allow any VM to be            files fail to comply with either
   recovered in full or as a collection of guest OS data files.              Recovery Time Objectives (RTOs) or
7) Application-Item-level Recovery: Quick recovery of individual objects     Recovery Point Objectives (RPOs) on
   from any virtualized application, such as an Oracle Database, Microsoft   40% of IT’s tests to recover critical
   Exchange Server, or Microsoft SharePoint.                                 data and applications.
8) Point-in-Time VM Replication: Replicate and fail over VMs using low-
   impact synthetic backups for near continuous data protection (CDP) that Despite what seems to be a rather
   minimizes RPO for any VM.                                           lax concern for VM data protection,
                                                                       CIOs and Line of Business Executives
                  alike cite the strength of a virtual environment as a business continuity solution. When
                  asked to cite key reasons for adoption of virtual infrastructure, IT decision makers list
                  the ability to rapidly restart, non-disruptive move, and spawn new instances of VMs.
                  With high availability, disaster recovery and data protection core components of any


                                                                                                                                04
                                                                                                               Test Configuration




                  business continuity strategy, CIOs view virtual infrastructure as the best way to assuage
                  down-time fears of corporate executives within budget constraints that preclude
                  implementing costly (DR) components, such as fault-tolerant servers, redundant
                  hardware resources, and additional software licenses.

                                                                                   The gulf between IT’s expectations of
 P   RINCIPAL   VM D         ATA ROTECTION HALLENGES the benefits that can be derived from a
                                P                 C                            virtual infrastructure and the reality of
1) Faster Data Recovery: In surveys of IT sites by both Symantec and           the lagging data protection measures put
   Veeam, the top data protection challenge was the time necessary for         into place highlights the fact that a
   restoration, which was cited with roughly 10% greater frequency than        highly flexible host infrastructure does
   the time to run a backup process.
                                                                               not solve the knotty issues IT faces
2) IT Budget Resources Required to Test DR VM Restoration: When                trying to protect the applications and
   asked about more frequent testing of restore operations, 60% of the
                                                                               data running on VMs. More
   sites in the Symantec DR survey listed budgetary constraints on
                                                                               importantly, when surveyed about the
   resource provisioning as the biggest impediment.
                                                                               problems related to protecting VM data,
3) Employee Disruption Staging DR VM Tests: In a virtual dead heat
                                                                               a plurality of the top issues cited by IT
   with resource provisioning issues, 59% of datacenters reported the
   disruption to employees as limiting their ability to test DR restoration of were related to the recovery of data
   backup files.                                                               rather than the backing up of data. In
4) Fine Grained Restoration of VM Data: Entwined with the need for             particular the two reasons most often
   restore processes in the Symantec survey was the need for more              cited to explain why IT organizations
   granular data restoration in the forms of VM data files and application     infrequently test DR plans centered on
   items, such as individual databases.                                        the costs associated with provisioning
                                                                               the resources necessary to stage a
                    recovery test, and the disruption that staging such a test would cause for staff.

                  RECOVERY-CENTRIC TEST PLAN
                      To reflect growing concerns for data recovery within the overall data protection process,
                  openBench Labs set up an eight point test plan with five key tests focused on data recovery
                  issues. We applied this test plan to five VM workflows. These workflows represented:

                      1) A corporate email scenario, with Exchange Server 2010 and a Domain Controller,
                      2) A 64-bit database-driven business process, with SQL Server 2008 R2, and a
                           Windows level 2008 Domain Controller,
                      3) A 32-bit database-driven business process, with SQL Server 2005, and a
                           Windows level 2003 Domain Controller, and a Windows 7 workstation,
                      4) A standalone Linux server,
                      5) A standalone Windows workstation running Windows 7 Enterprise.

                     We tested the ability to validate backup files, including the ability to verify that a
                  backup file is recoverable. We then extended this line of testing to assess the time and
                  resources required to fully restore a VM from any backup file. In addition, we focused on
                  the ability to quickly perform fine-grained restore processes from a single backup file of
                  a VM. In these tests, we examined the ability to easily recover guest files and application-
                  level items from VMs running multiple versions of Windows- and Linux-based guest
                  operating systems.

                                                                                                                                    05
                                                                       Test Configuration




                       HOW WE TESTED KEY VM DATA PROTECTION FEATURES
BACKUP SERVER:
Dell PowerEdge 1900
 • Quad core CPU
 • 4GB RAM
 • QLogic QLE2462 4Gbps HBA
 • Quantum DLT-S4 Tape Drive
 • Windows 2008 Server R2
    • Veeam Backup & Replication v5
    • Symantec Backup Exec 2010 R2
    • vCenter Server 4.1
    • up.time 5
    • Iometer Benchmark

VSPHERE   4.1 HOSTS:
Dell PowerEdge 1900
 • Quad core CPU
 • 8GB RAM
 • QLogic QLE2462 4Gbps HBA
 • VMware ESX 4.1
HP ProLiant DL580
 • Quad processor CPU
 • 8GB RAM
 • QLogic 2462 4Gbps HBA
 • VMware ESX 4.1

SAN INFRASTRUCTURER:
QLogic SANbox 9002 FC Switch
Xiotech Emprise 5000 ISE
 • (2) Balanced 4.2TB DataPacs

VM WORKFLOWS:
Windows Server 2008 R2 VM
 • Active Directory, DNS, DHCP
Windows Server 2008 R2 VM
 • Exchange Server 2010
   • 500 mailboxes (400MB per mailbox)

Windows Server 2003 R2 VM
 • Active Directory, DNS, DHCP
Windows Server 2003 R2 VM
 • SQL Server 2005
Windows Server 2008 R2 VM
 • SQL Server 2008 2

SUSE Linux Enterprise Server 11
 • oblDisk Benchmark

Windows 7 VM
 • MS Office 2010
 • Iometer Benchmark




                                                                                            06
                                                                               Test Configuration




   On front-end backup processes, we concentrated our tests on functions to reduce the
time needed to backup a workflow and the volume of storage that a workflow would
consume. To minimize storage requirements, we tested the ability to invoke data
compression and data deduplication. To minimize backup window time, we tested
support for incremental backups and the ability to generate full-featured synthetic
backups for use in any restore process.

    We concluded our tests with an examination of VM replication. In particular, we
tested the ability to apply backup optimization techniques to achieve near continuous
data protection (near-CDP) for VMs that can meet aggressive RTO and RPO demands.




                                                                                                    07
                                                                                                           Infrastructure Capabilities




Infrastructure Capabilities
                          sing Iometer to benchmark I/O throughput for our backup server,
                   “U     we supported two simultaneous I/O streams: one read and one
                   write that ranged from 450MB to 475MB per second each using large
                   128KB blocks similar to backup applications.”
                  PERFORMANCE FOUNDATION
                     Before starting our evaluation of Veeam Backup & Replication v5 with Backup Exec
                  2010 R2, we first ran hardware benchmarks on our test configuration to determine all
                  hardware limitations that could affect our data protection testing. We used two servers
                  running the VMware vSphere ESX hypervisor to host our vSphere 4.1 test scenarios. All
                  backup and restore tests using Veeam Backup & Replication v5 and Symantec Backup
                  Exec 2010 R2 were performed from a Dell PowerEdge 1900 Server with a Quad-core,
                  4GB RAM, and a dual-port 4Gbps QLogic QLE 2462 FC HBA.

                                                         We provisioned logical disks on our backup server, to
SIMULATED BACKUP THROUGHPUT
                                                     provide storage for both Veeam Backup & Replication and
                                                     Backup Exec image files, as well as datastores for our vSphere
                                                     hosts on a Xiotech Emprise 5000 ISE. To facilitate server and
                                                     storage monitoring during our backup and restore testing, we
                                                     installed up.time 5 service level monitoring on our backup
                                                     server. The up.time 5 software is able to monitor and report
                                                     on all virtual and physical servers, and any other resources
                                                     with an SNMP interface. As a result, we would be able to
                                                     compare process loads on all systems during a backup, which
                                                     is a growing concern at IT sites.

                                                         To frame the maximum disk throughput that our
                                                     infrastructure was capable of delivering in a backup process,
                                                     we ran Iometer on our Dell PowerEdge 1900 backup server.
                                                     To simulate a backup process, we streamed large-block
                                                     (128KB) reads and writes simultaneously to two logical
                                                     drives from the Emprise 5000. We measured total read and
                                                     write throughput at 950 MB per second. These results pegged
  Using Iometer, two simultaneous I/O streams, one
reading and one writing data , each sustained        our ability to support a straight-through end-to-end backup
450MB to 475MB per second using 128KB data           process without data compression or data deduplication at
blocks, similar to backup applications.              around 450MB per second.

                  ISOLATING I/O BOTTLENECKS
                     As part of our virtual infrastructure configuration, we set up a test domain that
                  included two VMs. One VM took on the role of the domain controller and ran Windows
                  Server 2008 R2 with Active Directory (AD), DNS, and DHCP. The other VM played the


                                                                                                                                         08
                                                                                                            Infrastructure Capabilities




                  role of an email server running Exchange Server 2010 on Windows Server 2008 R2.

VM EMAIL TRANSACTION LOAD TEST
                                                    We configured this server with three additional logical disk
                                                 volumes to support 500 email accounts. To balance email
                                                 transactions, we used two 125GB logical volumes to distribute
                                                 our 500 mailboxes across two mailbox databases. Each database
                                                 contained 250 mail boxes, each of which held an average of
                                                 400MB of message data. The third volume was used to store
                                                 Exchange log files associated with mailbox database
                                                 transactions.

                                                     With 500 active mailboxes, our configuration was typical of a
                                                 single Exchange server at a small to medium enterprise (SME)
                                                 site or a distributed Exchange server used to scale up a large
                                                 enterprise site by distributing the load and improving resiliency.
                                                 Next, we configured the Jetstress benchmark to place a
                                                 transaction load on our Exchange Server to keep approximately
                                                 100% of our mailboxes busy processing 1 transaction per
                                                 second. When we measured actual performance with up.time 5,
                                                 Jetstress transactions were engaging all of our mailboxes at a rate
                                                 of 1.6 transactions per second.

   We set up Jetstress to generate an email     To put that level of performance in perspective, over an
transaction load that would keep all mailboxes
                                            8-hour business day, each mailbox would process over, 46,000
busy. With up.time 5, we measured the       transactions. The value of being able to support such a
Jetstress load as actually averaging 800 email
and 340 log transactions per second.        performance level rests in the ability to easily measure the
                                            overhead placed on a VM with direct recovery from a backup
                  file and the transition to a SAN-based datastore via vMotion.




                                                                                                                                          09
                                                                                                            Backup Performance




Backup Performance
                        he ability of Veeam Backup & Replication to implement data
                   “T    deduplication and compression with both full and incremental
                   backup files opens the door for IT to support extremely aggressive
                   RTO and RPO goals in an SLA for business continuity.”
                  BACKUP SOFTWARE ARCHITECTURE DIFFERENCES
                      We installed both Veeam Backup & Replication 5 and Symantec Backup Exec 2010 R2
                  on the same Dell PowerEdge server. A central issue in comparing the use of Backup Exec
                  2010 R2 with Veeam Backup & Replication v5 in a vSphere environment is the scope of
                  the two products. Veeam Backup & Replication is designed explicitly for a VMware
                  environment. Symantec Backup Exec, on the other hand, is designed to support an entire
                  site, with both physical and virtual servers. As a result, most Backup Exec 2010 R2
                  modules apply to both physical and virtual servers, which complicate a comparison of
                  Symantec’s Backup Exec 2010 Agent for VMware Virtual Infrastructure with Veeam
                  Backup & replication v5.

                                                                                     Comparing the functionality of
            VM BACKUP PERFORMANCE TESTS:                                         Veeam Backup & Replication v5
1) Agentless VM Backup: Test basic backup performance and functionality          with Backup Exec 2010 R2’s Agent
   along with any dependencies on the need to license, manually deploy, or       for VMware Virtual Infrastructure
   manage agents on either VMs or vSphere hosts.                                 is dependent on the modules that
2) Image File Reduction via Data Compression and Deduplication: Both             are installed in the base Backup
   data compression and data deduplication can be applied to image backups       Exec 2010 R2 package. Many
   to reduce backup file requirements.                                           cross-architecture modules,
3) Single Execution for Multiple Backup and Recovery Options: Easy-to-           including a Shared Storage Option
   implement backup operations for both full and incremental backups with all    for a SAN and a Deduplication
   recovery options, including the whole VM, guest VM files and VM application   Option, played important roles in
   items, available for any backup.                                              our vSphere environment and are
                                                                                 required to match the functionality
                  provided by Veeam Backup & Replication v5.

                     These cross-architecture modules, however, significantly drive up the total cost of a
                  Backup Exec 2010 R2 installation. What’s more, the need for all Backup Exec 2010 R2
                  modules to work in a physical server environment frequently adds overhead to a vSphere
                  environment. For example, Backup Exec 2010 R2 optimizes integration with multiple
                  physical and virtual tape libraries. As a result, Backup Exec 2010 R2 implements an
                  ersatz tape library structure to perform disk-to-disk (D2D) backups.

                     Implementation of an enterprise-class data deduplication solution complicates
                  Backup Exec 2010 R2’s use of a simulated tape library structure for D2D backups. In a
                  generic enterprise-class deduplication scheme, backup files that feature deduplicateed,


                                                                                                                                 10
                                                                                    Backup Performance




single-instance data are not self-contained. These files contain pointers to a repository of
single-instance data representations. In turn, that necessitates the creation of a special
library within Backup Exec 2010 R2 to handle the media used in D2D backups with data
deduplication.

   For our tests, creating two distinct D2D devices for backups with and without data
deduplication meant that we had to create two distinct devices: a Backup-to-Disk folder
and a Deduplication Storage folder. To simplify device management, we assigned a
distinct virtual volume to each of these folders. Backup Exec then created media files in
both of these directories and wrote backup data into the respective media files.

ALONG THE DATA DEDUPLICATION DIVIDE
   For D2D backups, the dual-device structure of Backup Exec 2010 R2 aligned with a
major backup distinction between Veeam Backup & Replication v5 and Backup Exec
2010 R2 with respect to compression and deduplication. While Veeam Backup &
Replication v5 allows all data reduction techniques, including data deduplication, data
compression, and incremental backup, to be used in a single job, Backup Exec 2010 R2,
must apply data deduplication exclusively and only to a full backup.

                                               f a company has standardized on Symantec
    Veeam Backup & Replication v5
implements a simple data
deduplication scheme that compares
                                         “I     Backup Exec for physical servers, it can
                                         leverage this capability to compound the benefits
only the data contained within an        from using Veeam for VMware virtualized servers.”
active job stream and makes each
deduplicateed backup file completely
self-contained. Since a Veeam backup file contains all of the information needed for
rehydration, any backup file can be restored from any server running Veeam Backup &
Replication v5.

   For a VM containing multiple versions of data files and multiple structures such as
database tables, Veeam’s active stream deduplication often provided data reduction on
the order of 40% to 50%. Moreover, with self-contained backup files, Veeam allows IT
administrators to combine data deduplication with other data reduction techniques,
including data compression. With both techniques in play, we typically experienced total
data reduction rates between 15-to-1 and 20-to-1.

   What’s more, if a company has standardized on Symantec Backup Exec for physical
servers, it can leverage this capability to compound the benefits of using Veeam for
VMware virtualized servers. The self-contained structure of Veeam’s backup files
provides IT with an option to add tape archiving to Veeam Backup & Replication v5 via
the backup of its host server. In this way, Backup Exec can be used to meet any off site
requirements for backups of VMs.

   On the other hand, the PureDisk service, which handles all data deduplication for
Backup Exec 2010 R2, takes a holistic time-centric perspective to VM data, which is
typical of most enterprise-level data-deduplication schemes designed to deduplicate data


                                                                                                         11
                                                                                    Backup Performance




from all sorts of generic sources. The goal of these deduplication schemes is to discover
data segments that are backed up repeatedly over time and replace them with pointers to
a single-instance of the data. To achieve this goal each enterprise-class data deduplication
scheme develops arcane algorithms to scan and break a data stream it into multiple
segments in a way that improves the likelihood of making as many matches as possible in
a way that is as efficient as possible.

   In addition to the algorithms used to identify redundant data, a fundamental
construct of any deduplication scheme is how the pointers work. Inline data
deduplication schemes, such as PureDisk, use backwards referencing which to replace
redundant data in the current backup with a pointer to a previous instance of that data
while the backup process is running. Comparing data blocks and substituting matching
blocks with pointers adds very significant overhead to the backup process and even
changes the characteristics of I/O operations.

    In the PureDisk scheme, a Backup Exec 2010 R2 media server maintains a catalog of
hash-coded data fingerprints that belong to unique segments of data discovered during
full backups over time. This makes storage reduction for a current backup job dependent
on the rate of cache hits for the job’s data segments with respect to fingerprints in the
media server’s catalog. What’s more, the caching of backup segment fingerprints creates
an affinity between a VM backup processes and a physical media server. The segment
catalog belonging to the media server that last backed up a VM is very likely to provide
the highest number of cache hits on the next backup of that VM.

   As a media server’s segment fingerprint catalog grows over time, cache hits increase
and the sizes of backup files decrease; however, growing the amount of data in the
segment fingerprint catalog also increases the number of potential comparisons that can
be made during a backup and the time needed to complete the process. That makes it
important for PureDisk to grow segment catalogs in a way that increases cache hits
without burdening search time.

    As a result, Backup Exec 2010 R2 prohibits the use of software compression, which
alters the structure of data segments, with deduplication, and data deduplication cannot
be used with either incremental or differential backups, which by definition copy only
new data segments. On the other hand, the ability of Veeam Backup & Replication to
implement data deduplication and compression with both full and incremental backup
files opens the door for IT to support extremely aggressive RTO and RPO goals in an
SLA for business continuity.




                                                                                                         12
                                                                                                                       Test 1: Agentless Backup




Test 1: Agentless VM Backup
                                                         needed to install and maintain a Backup Exec
                                               “WeRemotewhich we intended to restore individual2010 R2
                                               or physical—for
                                                               Agent on any Windows-based system—virtual
                                                                                                      files or
                                               item-level data.”
                   AGENT SYNCHRONIZATION
                       We began our assessment by examining functionality with respect to dependencies on
                   licensing, deploying, or managing agents on either individual VMs or vSphere hosts. In
                   addition, we also tested basic backup performance as a baseline for all testing.

BACKUP EXEC AGENT                                                                                 With Veeam Backup &
                                                                                              Replication v5, we were able to
                                                                                              perform all backup operations
                                                                                              on any VM—whether Linux-
                                                                                              or Windows-based—without
                                                                                              first installing an agent. We
                                                                                              needed to install and maintain
                                                                                              a Backup Exec 2010 R2 Remote
                                                                                              Agent on any Windows-based
                                                                                              system—virtual or physical—
                                                                                              for which we intended to
                                                                                              restore individual files or item-
                                                                                              level data.

                                                                                                  For IT, the installation of
                                                                                              multiple Remote Backup Exec
                                                                                              2010 R2 Agents on backup-
                                                                                              clients can be easily pushed
                                                                                              down from a media server
                                                                                              using a wizard. Nonetheless,
                                                                                              updating clients is typically
                                                                                              necessary after every update of
                                                                                              a media server t. Client
                                                                                              software must be updated to
    Using Backup Exec 2010 R2, remote agent software—available only for Windows-based         leverage fixes and functionality
 clients—was required to restore file-level data from a VM backup. We were also able to
 restore item-level data from a VM running either Active Directory, Exchange Server, or SQL   changes to the media server.
 Server with Granular Recovery Technology enabled. While a wizard on the media server
                                                                                  What’s more, with no agent
 made it possible to update multiple clients with a single push process, we often found it
 necessary to reboot clients individually after some updates.                  software available for a client
                                                                               running a Linux OS, we could
                   not perform file-based restores directly from a backup of our VM running SUSE Linux
                   Enterprise v11. In order to restore user files using Backup Exec 2010 R2, we needed to
                   run a separate Windows-network-based backup of directories exposed using Samba on
                   our Linux-based VM.



                                                                                                                                              13
                                                                                                                Test 1: Agentless Backup




BACKUP SERVER CPU &DISK LOAD
                                                                          VM Server Backup Performance
                                                                       Full backup, No Data Deduplication or Compression
                                                                                        Backup    Active    Backup      Backup Window
                                                             VM Parameters                         Data
                                                                                       Software               File        (hh:mm:ss)

                                                     Applications: Active Directory,    Veeam     11.9GB     11.5GB    0:02:09
                                                     DNS Server, DHCPServer                                            0:05:09
                                                                                       Backup
                                                     OS: Windows Server 2008 R2                   11.9GB     12.1GB
                                                                                        Exec                           0:07:07 with verify
                                                                                        Veeam     20.8GB     19.3GB    0:03:29
                                                     Application: SQL Server 2008 R2
                                                     OS: Windows Server 2008 R2        Backup                          0:04:36
                                                                                                  20.8GB     20.3GB
                                                                                        Exec                           0:07:00 with verify

                                                     Applications: Jetstress,           Veeam     228.8GB   229.0GB    0:20:41
                                                     Exchange Server 2010
                                                                                       Backup                          0:49:05
                                                     OS: Windows Server 2008 R2                   228.8GB   234.7GB
                                                                                        Exec                           1:06:38 with verify

                                                        In our initial tests, all backups were performed without
                                                     data deduplication or data compression. We measured the
                                                     elapsed process time of the backup window and the size of
                                                     the resulting backup file. In addition we examined the CPU
                                                     process load and the disk throughput load imposed on the
                                                     backup server during the backup window via up.time 5.

                                                        Not only were results similar across VMs, the pattern
                                                     established continued with more sophisticated processing
                                                     options. Veeam consistently leveraged the highest level of
                                                     available CPU resources to complete backup processes as
                                                     quickly as possible. As a result, Veeam Backup & Replication
                                                     v5 wrote data faster and completed jobs faster than Backup
                                                     Exec 2010 R2.

                                                        More importantly, Veeam Backup & Replication v5
                                                     removes backup verification from the backup window. By
                                                     focusing only on data protection for VMs, Veeam has been
  Backing up a primary domain controller VM, Veeam
Backup & Replication v5 used up to 85% of a          able to introduce new technologies that redefine all
processor on a quad-core server, while Backup Exec   traditional IT notions of system recovery.
2010 R2 peaked at 75%. Writing the backup files,
Veeam reached 215MB per second, while Backup      For our VM acting as a primary domain controller with
Exec peaked at 185MB per second. Backup Exec
                                               11.9 GB of active data, the backup process took just over 2
also kept the backup window open to verify backup
                                               minutes with Veeam Backup & Replication and 5 minutes
data by reading the backup file (265MB per second)
and calculating a checksum.                    Backup Exec 2010 R2. To verify the backup data, the full
                                               backup window took just over 7 minutes. Similarly, backing
                  up our VM running Exchange Server 2010 took nearly 21 minutes with Veeam Backup &
                  Replication v5 and just over 49 minutes with Backup Exec 2010 R2, which required over
                  an hour and 6 minutes in completing the entire process.


                                                                                                                                       14
                                                                                                             Test 2: Backup File Reduction




Test 2: Backup File Reduction
                                                                configured for data reduction took up to
                                                “Full backups longer to complete with Backup Exec 2010 R2,
                                                     nine times
                                                compared to Veeam Backup & Replication v5.”
                   THE DATA DEDUPLICATION DIVIDE
                      With backup files for our VM running Exchange Server consuming approximately
                   230GB with either Veeam Backup & Replication or Backup Exec 2010 R2, the need to
                   reduce backup-file size is undisputable. In our second set of backup tests, we examined
                   the ability to apply multiple data reduction techniques to backup files.

BACKUP FILE REDUCTION                                     While there is a strong consensus that the technologies
                                                      needed for backup file reduction are data deduplication and
                                                      compression, there are wide differences in the application of
                                                      these technologies. In fact, some of the biggest performance
                                                      differences between Veeam Backup & Replication v5 and
                                                      Backup Exec 2010 R2 arise from differences in the way that
                                                      each package approaches data deduplication.

                                                         Veeam Backup & Replication v5 does not store or compare
                                                      data beyond the context of a running job. As a result, a VM
                                                      backup can utilize both data deduplication and compression.
                                                      Moreover, since a Veeam backup file is self-contained, the file
                                                      has no dependencies on physical servers or support files. That
                                                      means a Veeam backup file can be backed up to tape as a
                                                      Windows Server file, trasnported to any Windows Server
                                                      running Veeam Backup & Replication v5 to recover the VM.

                                                          On the other hand, Backup Exec 2010 R2 uses an inline
                                                      enterprise-class data deduplication scheme that employs a
                                                      catalog of hash-codes—often dubbed ‘fingerprints’—of single
                                                      instance data segments. The catalog is used to simplify the use
                                                      of backwards-referencing pointers to unique instances of
                                                      previously encountered data segments. When a data segment
                                                      in the current backup is discovered to match an existing data
                                                      segment, the segment in the backup file is replaced by a copy
   While backing up a 20.8GB VM running Windows       of the pointer in the catalog.
 Server 2008 R2 and SQL Server 2008 R2, we
 applied both data compression and data                  This method creates interesting dependencies on time and
 deduplication with Veeam Backup & Replication
 v5. Veeam completed the backup in less than 6        place. Frequent backups of a VM on a server will populate
 minutes and reduced the backup file to 8.5 GB.       that server’s catalog with the most accurate up-to-date
 Using Backup Express 2010 R2, a backup with          collection of data segment fingerprints to boost the dtat
 software compression took nearly 21 minutes and      deduplication cache hit rate. When we repeated a backup of a
 created an 11.4GB backup file. On the other hand,
                                                      VM on a media server without changing any user data, the
 a backup with data deduplication, took close to 18
 minutes and created a backup file with just a        data deduplication rate jumped from 76% to 90%.
 4.2GB footprint.                                     Nonetheless, when we repeated that backup process a third


                                                                                                                                     15
                                                                                                             Test 2: Backup File Reduction




                  time after defragmenting the VM’s logical disk, the deduplication rate fell back to
                  81%.percent.

                      Inline data deduplication requires significant CPU and memeory resources, especially
                  if data reduction rates of around 90% or higher are to be reached. In terms of leveraging
                  available CPU resources, Veeam Backup & Replication v5, which implements a relatively
                  simple data depuplication scheme, typically utilized all available CPU cycles on our
                  quad-core server to minimize backup widows.

                                                                                               In contrast, Backup
                      VM Server Backup Performance                                          Exec 2010 R2, which
             Full backup: Data Deduplication/Compression and Verification                   runs a far more
                                   Backup    Active   Backup       Backup Window            sophisticated
        VM Parameters                         Data
                                  Software              File         (hh:mm:ss)             deduplication service,
                                                                                            typically utilized only
Applications: Active Directory,    Veeam     11.9GB    4.5GB     0:03:07
                                                                                            two processor cores. As a
DNS Server, DHCPServer                                           0:16:30                    result, backups
                                  Backup               6.3GB                Compression
OS: Windows Server 2008 R2                   11.9GB
                                   Exec                1.2GB     0:14:05    Deduplication   configured for data
                                                                                            reduction took up to
                                   Veeam     20.8GB    8.5GB     0:05:40                    nine times longer to
Application: SQL Server 2008 R2
OS: Windows Server 2008 R2        Backup              12.2GB     0:20:45 Compression        complete using Backup
                                             20.8GB                                         Exec 2010 R2, when
                                   Exec                4.0GB     0:17:58 Deduplication
                                                                                            compared to Veeam
Applications: Active Directory, Veeam        32.7GB   10.2GB     0:09:23                    Backup & Replication v5.
DNS Server, DHCPServer
SQL Server 2008 R2              Backup                19.2GB     0:38:14 Compression
                                             32.7GB                                 Even with data
OS: (2)Windows Server 2008 R2 Exec                     2.6GB     0:32:06 Deduplication
                                                                                 deduplication combined
Applications: Jetstress,         Veeam 228.8GB 13.5GB 0:19:59                    with data compression,
Exchange Server 2010                                                             Veeam Backup &
                                Backup              21.0GB 1:53:57 Compression   Replication v5 often
OS: Windows Server 2008 R2               228.8GB
                                  Exec               8.4GB 3:02:17 Deduplication provided around a 5-to-1
                                                                                 advantage in wall clock
                  time for a backup with respect to Backup Exec 2010 R2. What’s more, Veeam also created
                  consistently smaller back files compared to using software compression with Backup
                  Exec 2010 R2. These advantages were increased by packaging multiple servers in a single
                  backup, which increased the ability for Veeam to apply data deduplication. In particular,
                  by backing up our SQL Server 2008 R2 and a domain controller VMs as a workflow with
                  Veeam, we cut the backup file foot print by approximately 30% and still retained all
                  recovery options for each server.




                                                                                                                                     16
                                                                                                                 Test 3: Single Execution for All Options




                                                  ith the ability to apply any backup or restore
Test 3: Single Execution for All Options                      “W
                                                  option to an incremental backup, even IT at a
                                         small SMB shop can leverage just the local backup
                                         capabilities of Veeam Backup and Replication v5 to
support a business continuity SLA with RPO and RTO requirements of less than two minutes.”
                   INCREMENTAL EQUALITY
 INCREMENTAL BACKUP: VEEAM BACKUP & REPLICATION V5                                                      In our third series of
                                                                                                    tests, we examined the
                                                                                                    ability of each package to
                                                                                                    simplify operations for IT
                                                                                                    administrators. In
                                                                                                    particular, we focused on
                                                                                                    the ability to implement
                                                                                                    all backup options,
                                                                                                    including full and
                                                                                                    incremental, from a single
                                                                                                    GUI command. We also
                                                                                                    examined the ability to
                                                                                                    apply all recovery options,
                                                                                                    including VM guest OS
                                                                                                    files and data items, to
                                                                                                    each backup file. While
                                                                                                    virtualization’s reason
                                                                                                    d’être is simplification of
                                                                                                    resource management,
                                                                                                    data center managers
                                                                                                    continue struggling with
                                                                                                    the complexity of
                                                                                                    meeting RTO and RPO
                                                                                                    data protection targets in
                                                                                                    a virtual environment.

                                                                                                        We were able to run
                                                                                                    incremental and full
                                                                                                    backups interchangeably
                                                                                                    using Veeam Backup &
                                                                                                    Replication v5, which by
                                                                                                    default uses an initial full
                                                                                                    backup followed by
                                                                                                    incremental backups. To
   We set the default backup mode for our PDC VM running Active Directory to run reversed           make the most recent
 incremental backups continuously. To reduce the size of backup files we applied both data          backup the fastest to
 deduplication and compression . As a result, an incremental backup of our VM with 12GB of active
                                                                                                    restore, we used reversed
 data took about 90 seconds and generated a 25MB rollback file. More importantly, we were able
 to leverage all backup and recovery features:


                                                                                                                                                  17
                                                                                                         Test 3: Single Execution for All Options




                incremental backups: The incremental backup file is used to create a new synthetic full
                backup from the previous full backup and a rollback file generated to recreate the
                previous full backup to maintain that restore point. What’s more, we leveraged the short
                time to run an incremental backup and the small size of the rollback file to schedule
                continuous incremental backups—as a backup completed, a new backup started—and
                thereby maintain an RPO of less than two minutes.

                                                                                                   In addition to
INCREMENTAL BACKUP: BACKUP EXEC 2010 R2
                                                                                               applying all of the
                                                                                               options available for a
                                                                                               full backup, while
                                                                                               running an
                                                                                               incremental backup,
                                                                                               we were able to run
                                                                                               every restore option
                                                                                               with each incremental
                                                                                               backup file, whether
                                                                                               the backup file was a
                                                                                               rollup or rollback file.
                                                                                               Using a wizard, we
                                                                                               were able to pick any
                                                                                               recovery point
                                                                                               associated with either
                                                                                               a full or incremental
                                                                                               backup and run all of
                                                                                               the restore options.

                                                                                                       In particular, we
                                                                                                   were able to utilize
                                                                                                   our incremental
                                                                                                   backup file as a
                                                                                                   restore point with the
                                                                                                   Veeam Instant Restore
                                                                                                   feature, which allows a
                                                                                                   VM to run directly
                                                                                                   from a backup file and
                                                                                                   enables IT to comply
                                                                                                   with an RTO of less
                                                                                                   than two minutes.
  Using Backup Exec 2010 R2, we had to create a special policy to run an incremental backup. In    With the ability to
addition, we were not able to implement data deduplication or Granular Recovery Technology with an apply any backup or
incremental backup. As a result, restore wizard allowed us to recover the vSphere vmdk files       restore option to an
associated with a VM backed up with an incremental backup; however, the wizard did not make any of
the local Exchange Server 2010 files on our VM available from an incremental backup.
                                                                                                   incremental backup,
                                                                                                   even IT at a small
                   SMB shop can leverage just the local backup capabilities of Veeam Backup and
                   Replication v5 to support a business continuity SLA with RPO and RTO requirements of


                                                                                                                                          18
                                                                            Test 3: Single Execution for All Options




less than two minutes. For an IT administrator, the difference between an incremental
and a full backup are measured in time and storage volume.

   On the other hand, Backup Exec 2010 R2, with its reliance on agents, the
incompatibilities of differing D2D backups, and the overhead of an inline deduplication
scheme that uses a disk segment cache, is not able to provide all restore options to every
standard backup of a VM. In particular, IT administrators can perform a file-level restore
only on a full backup of a VM that runs Windows and has a Backup Exec agent installed.
Moreover, incremental and differential backups for VMs require a special backup policy
in order to execute and cannot utilize data deduplication.

INLINE BLOCK POINTING GAMBIT
    In a vSphere environment, there is a bigger question concerning the need for an
inline enterprise-class data deduplication scheme. Can data segments repeated over time
be discovered and removed from a VM backup file with significantly less overhead? The
answer can be found in the vStorage APIs for Data Protection (VADP) and Changed
Block Tracking (CBT).

    When scanning image backup data, an enterprise-class data deduplication scheme
targets the discovery of ordered sequences of physical data blocks that have been found
in a previous backups. In essence, the software looks for sequences of blocks that have
not changed over time. That’s why defragmentation of a logical volume absent explicit
changes to data will degrade the cache hit rate of a backup that uses backwards
referencing pointers. On the other hand, excluding data blocks that have not changed
from the last backup of a vSphere VM is a trivial process using CBT in conjunction with
an incremental backup.

    To test our ability to maximize segment caching, we ran two successive full backups
of our VM running Exchange Server 2010 using Backup Exec 2010 R2 with the PureDisk
deduplication service. On the second run, the deduplication rate was 98%, which was
manifested in an 8.4GB backup file. Nonetheless, the backup window required a full 3
hours and 2 minutes.

   Next we applied an incremental backup with Veeam Backup & Replication v5. With
both data deduplication and compression turned on, the incremental backup file
generated with vStorage and CBT started at 926.4MB. Modest internal deduplication and
a great deal of compression reduced the size of that backup file to 260.6MB. More
importantly the entire process took just 1minute and 52 seconds.




                                                                                                             19
                                                                                                              Recovery Performance




Recovery Performance
                        key vPower technology is the ability to launch a VM directly from
                   “A    a backup file: This capability entirely changes the construct of VM
                   recovery for IT operations.”
                   VPOWER TO MEET RECOVERY-CENTRIC SLAS
                       For IT, backup has long been a necessary daily activity centered on backing up data,
                   applications, and OS files in a minimal amount of time, which is dubbed the backup
                   window. From the perspective of a Line of Business (LoB) executive, however, the value
                   of IT data-protection operations rests entirely in recovery processes. That’s why data-
                   protection Service Level Agreements (SLAs) between IT and LoB units focus on RPO
                   and RTO targets: Backup is simply a means to provide a recovery point.

                                                                                With the introduction of new vPower
       VM RECOVERY PERFORMANCE TESTS:                                       technology, Veeam Backup &
4) Direct VM Recovery from a Backup File: Instantly start VM                Replication v5 revolutionizes IT’s ability
   recovery from a backup file without rehydrating data, and complete       to perform fast VM backup operations,
   the process with Storage vMotion, VM cloning, or Veeam’s VM Copy         test the recoverability of 100% of
   wizard, which uses Veeam’s FastSCP.                                      backups outside of the backup window,
5) Automated Recovery Verification: Perform a test restore for every        and meet strict RPO and RTO
   backup file as a standard backup validation test.                        requirements. With traditional backup
6) Multi-OS VM File-Level Recovery: VM image-level backups allow            software, backup validation consists of
   any VM to be recovered in full or as as a collection of logical guest    checking that the bits in the backup file
   OS data files.                                                           match the bits in the original VM. This
7) Application-Independent Item-level Recovery: Quick recovery of           amounts to rereading all of the data and
   individual objects from any virtualized application, such as an Oracle   calculating a checksum.
   Database, Microsoft Exchange Server, or Microsoft Sharepoint.
8) Point-in-Time VM Replication: Replicate and fail over VMs using      Traditional checksum validation
   low-impact synthetic backups for near continuous data protection  extends the time needed for a backup
   (CDP) that minimizes RPO for any VM.                              and only ensures that the VM and the
                                                                     VM backup are duplicates. This
                   validation method cannot check if the original VM has not been corrupted to the point
                   that it is no longer capable of being rebooted. To verify that a backed system will actually
                   run, Veeam Backup & Replication v5 has introduces a number of key technologies under
                   the banner of vPower.

                       A key vPower technology is the ability to launch a VM directly from a backup file:
                   This capability entirely changes the construct of VM recovery for IT operations. From a
                   process perspective, booting a VM directly from a backup file begins with placing
                   pointers to the files contained within the backup file inside a special directory on the
                   Veeam Backup & Replication v5 server. That directory is exported to the vSphere host
                   via NFS as a network attached datastore with read-only files.


                                                                                                                                     20
                                                                                       Recovery Performance




    With all of the VM virtual disks represented as read-only files via pointers, writing
new data is handled through cache files that Veeam adds to the vPower NFS datastore by
default. To improve write performance, new data can be redirected to a different
datastore. If this option is implemented, Veeam Instant Recovery triggers a snapshot of
the VM and redirects the snapshot and CBT files to a VeeamIR directory in the
designated datastore. In this case the vSphere snapshot handles the new data and cache
files are not created.
                                                               eeam Backup & Replication v5
    While a VM running from a backup file can
sustain a distinctly higher IOPS load with data
                                                      “V   extends the construct of file-level
                                                   data restore for any guest OS to object-level
redirection, there is an operational drawback
when consolidating the original and new data       data for any application on any guest OS.”
on a production datastore. If data redirection
has not been utilized, vMotion can be used to consolidate that data on a production
datastore while the VM remains running online. On the other hand, if data redirection
has been used to put new data in a snapshot on a second datastore, vMotion cannot be
utilized. An IT administrator will need to hot-clone the VM, power down the VM, and
power on the cloned copy.

   Another vPower construct is a Virtual Lab, which creates an isolated environment,
into which administrators can boot and test backed-up VMs. In addition to providing a
wizard to easily configure a virtual lab, Veeam provides test scripts to run on VMs to
ensure service roles on domain controllers, database servers, and email servers are
running properly. In a matter of minutes, test scripts can verify that a VM as backed up
with no configuration changes boots properly and its key applications run correctly.
What’s more these tests are run outside of the backup window while the original VM
continues to run in the production environment.

    Nonetheless, the lion’s share of restore operations for IT remain focused on retrieving
individual files inadvertently lost or corrupted in day-to-day use. In a virtual infrastructure,
this translates into the need to easily restore user files under the VM’s guest OS. To this
end, Veeam Backup & Replication v5 provides a wizard that works directly with
depuplicated and compressed backup files to restore any file associated with any guest OS.
What’s more, Veeam Backup & Replication v5 extends the construct of file-level data
restore for any guest OS to object-level data for any application on any guest OS.




                                                                                                              21
                                                                                              Test 4: Direct VM Recovery from a Backup File




Test 4: Direct VM Recovery from a Backup File
                                                                     eeam takes VM backup
                                                               “Vsimpleboot, internal VMverification from
                                                               backup files
                                                                            byte comparisons to validating VM
                                                                                            applications work,
                                                               and external function correctly.”
               RECONCILING RTO WITH REALITY
                   For LoB executives, RTO represents the maximum amount of time before an
               organization is negatively impacted by the interruption of a core business process. As a
               result, an SLA that targets business continuity must be driven by the needs of the
               business unit. As such, a business continuity SLA needs to satisfy a worst possible time
               for an interruption to occur. More importantly, the SLA should not degenerate into a
               reflection of IT capabilities.

                                                                                           For IT administrators,
                Traditional VM Restore Performance                                      recovering a VM to a
        Full Restoration with Rehydration of Deduplicated/Compressed Data               working state that
                             Backup Restored       Backup       Restore Window          corresponds to a previous
     VM Parameters                    Data                                              point in time often
                            Software                 File         (hh:mm:ss)
                                                                                        requires several hours of
                           Veeam       235.4GB     13.0GB     1:28:35                   work. Symantec’s 2010
Applications: Jetstress,
                                                                                        DR survey pegs the total
Exchange Server 2010
                           Backup                  22.1GB     2:26:00   Compression     amount of time spent in
OS: Windows Server 2008 R2             235.4GB
                            Exec                    8.8GB     2:43:35   Deduplication   recovering a system to
                                                                                        average about five hours.

                  We began recovery testing by assessing the time to do a traditional restore or our VM
               running Exchange Server. In particular, we measured the time period needed to extract
               and rehydrate VM data files from a backup file and then write the data to a vSphere host
               and register the VM. This time period did not include any storage provisioning activities
               before instituting the restore process or any post-process testing of VM functionality. Just
               the restore process for our VM running Exchange Server 2010 took 2hours, 43 minutes,
               and 35 seconds, when we used Backup Exec 2010 R2 with its data deduplication option.
               Even our best traditional restore time ran 1 hour, 28 minutes, and 35 seconds with
               Veeam Backup & Replication v5.

                  With traditional system restore techniques measured in hours, RTO issues have
               become serious problems for CIOs as more LoB executives link computer downtime to
               more than lost sales revenue. Many LoB executives have upped the ante by equating
               computer outages with potential losses in customer confidence and market share. As a
               result, senior LoB executives expect IT to meet a recovery time objective (RTO) that is
               measured in hours and in some cases even minutes. The challenge for many IT decision
               makers is how to assuage the business continuity fears of corporate executives within
               budget constraints that exclude costly components, such as fault-tolerant servers,
               redundant hardware and software, and standby network bandwidth.



                                                                                                                                     22
                                                                                                            Test 4: Direct VM Recovery from a Backup File




                     Unique to Veeam Backup & Replication v5 is the ability to start and run a VM
                  directly from a backup file without first going through provisioning and full restore
                  processes. In just 22 seconds we were able to boot and publish a VM running Exchange
                  Server into our vSphere production environment. The tradeoff for blazing recovery
                  speed comes with lower sustained IOPS rates. Nonetheless, it is possible to bring a VM
                  running from a backup file back to full performance levels with less than 30 seconds of
                  total server down time.

INSTANT RECOVERY START UP




   We used the Instant Recovery wizard to start our VM running Exchange Server 2010 directly from a backup file. Within 5 seconds, a
 Veeam server directory was populated with pointers to the contents of the VM backup file and exported to the vSphere server as a
 vPower NFS datastore. By default, Veeam added cache files to handle new data written to each of the VM’s logical disks. When we
 chose to redirect new data updates for Instant Recovery, Veeam triggered a VM snapshot and redirected the snapshot and CBT files to
 a directory dubbed VeeamIR on the datastore of our choice. With the snapshot now handling data updates, there was no need for
 special cache files.




                                                                                                                                                  23
                                                                                                           Test 4: Direct VM Recovery from a Backup File




                      We ran a number of tests with the Veeam Instant Restore feature. In these tests we
                  concentrated on RTO and performance requirements for SLAs. In particular, we ran
                  Jetstress with all data directed to the vPower NFS datastore and with updates redirected
                  to another datastore using a redirected snapshot. In addition we tested IOPS rates while
                  consolidating data for both cases.

                      In our initial test, we did not redirect data updates from the vPower NFS datastore. As
                  a result, writes were captured in local cache files and we were able to leverage vMotion.
INSTANT RECOVERY WITH VMOTION




  Using Veeam Instant Recovery, our VM running Exchange Server was published in vSphere within 22 seconds from an incremental
backup file. Within another 67 seconds we were able to log into the VM and launch Jetstress. At the same time, we started a vMotion
migration of the VM from the vPower NFS database to a SAN-based datastore. The vMotion process took 2 hours and 50 minutes. The
incremental Veeam backup and the Veeam Instant Recovery process took a total of just 2 minutes. That put the total time to backup and
fully recover our VM at 2 hours and 52 minutes with VM downtime less than 30 seconds.

                                                                                                                                                 24
                                                                                                      Test 4: Direct VM Recovery from a Backup File




                                                                              By redirecting update data for the logical
INSTANT RECOVERY IOPS PERFORMANCE
                                                                          disks to another datastore, we were able to
                                                                          double the level of Jetstress transactions that
                                                                          we could sustain. What’s more, this relative
                                                                          difference was carried over to the
                                                                          consolidation processes for these Instant
                                                                          Recovery scenarios. During the hot-clone
                                                                          process with the backup VM running with
                                                                          data redirection, we sustained an IOPS load
                                                                          very similar to the IOPS load that we had
                                                                          sustained by the default Instant Recovery
                                                                          configuration, which did not use data
                                                                          redirection.

                                                                              In particular, we sustained approximately
                                                                          150 email and 50 log transactions per second
                                                                          while consolidating data by hot-cloning the
                                                                          backup VM with data redirection. In
                                                                          comparison, without data redirection we were
                                                                          able to sustain roughly 60 email transactions
                                                                          and 25 log transactions per second while
                                                                          implementing vMotion to consolidate data for
                                                                          our backup VM. That IOPS level represents a
                                                                          fairly typical transaction processing load for
                                                                          many mission critical applications. In
                                                                          particular, it equates to 3,456 email
                                                                          transactions—reads, writes, and deletes—per
  With the Exchange Server running from a backup file with data           user mailbox over an 8-hour work period,
redirection, we sustained significantly more email transactions running
the Jetstress benchmark. With data updates redirected via a snapshot,
                                                               Consolidation with hot cloning took
we averaged 290 email and 105 log transactions per second. Without
                                                            roughly 12% more wall clock time. While the
redirection, we averaged 140 email and 38 log transactions per second.
                                                            vMotion process completed in 2 hours and 50
                   minutes, hot cloning took 3 hours and 10 minutes to complete. We then needed to shut
                   down the backup VM and start the cloned VM manually. In addition, the consolidation
                   process can be performed by invoking the VM Copy wizard , whch uses Veeam FastSCP.

                       In both cases we had the option to start consolidating the recovered VM at any point
                   in time. We could easily wait to run vMotion or hot-cloning during an off-peak
                   processing period. More importantly, using Veeam Backup & Replication v5, we were
                   able to perform an incremental backup and then recover our VM running Exchange
                   Server 2010 with Veeam Backup & Replication v5 in less time than it took just to run a
                   backup using data deduplication with Backup Exec 2010 R2.




                                                                                                                                            25
                                                                                                          Test 5: Automated Recovery Verification




Test 5: Automated Recovery Verification
                                                                              takes VM backup verification from simple
                                                                “Veeamcomparisons to validating thatand external
                                                                        byte
                                                                files boot, internal VM applications work,
                                                                                                            VM backup

                                                                dependencies on other VMs function correctly.”
                    FULL RECOVERY VALIDATION
 TRADITIONAL BACKUP VALIDATION                            Using Backup Exec, backup validation consists of checking
                                                          that the bytes in a backup file match the bytes in the VM. This
                                                          amounts to rereading the data in the backup file, calculating a
                                                          checksum, and then comparing that checksum against a
                                                          checkuum calculated while backing up the original VM.

                                                              This method significantly extends the backup window
                                                          and does not ensure that the backed up version actually
                                                          works. If the VM has has had critical OS files or application
                                                          files corrupted but not identified, the backup file will be an
                                                          exact duplicate of the original problem. Depending on the
                                                          severity of the problem, if the origial VM is shut down,
                                                          neither the original nor the backed-up VM may be bootable.

                                                             To verify that a backed-up VM and its applications will
                                                          run correctly, Veeam Backup & Replication v5 introduced a
                                                          new feature, dubbed SureBackup Recovery Verification,
                                                          which non disruptively verifies the full recovery of a VM.
                                                          Using the vPower NFS datastore construct utilized with
                                                          Instant Recovery, SureBackup starts a backed-up VM
                                                          associated with a recovery point directly from its backup file.
   The default backup scenario with Backup Exec           SureBackup Recovery Verificaton, however, does not publish
 2010 R2 includes the verification of backup data         the backed-up VM to the production environment.
 immediately after writing a backup file. In our tests,
 the time to reread the backup file was dependent on
 the data reduction method used in the backup. While In contrast to Instant Recovery, SureBackup creates a
 data compression consistently added more time toprotected Virtual Lab environment, in which backups of
 backup processes, data deduplication consistently
                                                 production VMs can run while the original VMs continue to
 added more time to verification processes.
                                                 operate. IT administrators create virtual lab environments
                    using a wizard that configures a private network, a vSwitch, and a gateway appliance that
                    masquerades recovered VMs with dynamic IP addresses outside the production network.
                    As a result, administrators can test VMs recovered from backup files using the VM’s
                    original IP address and node name without creating conflicts with production VMs.

                       An IT administrator can also statically configure the appliance to masquerade a
                    specific private-network address with a specific production-network address. Using this
                    technique, we discovered and monitored VMs in the virtual lab with up.time 5. Another
                    configuration option for each virtual lab is the choice of a datastore for redo logs, which
                    are automatically assigned to recovered VMs running within the lab environment.
                    Unlike Instant Recovery, which uses cache files or redirects data with a snapshot, updates

                                                                                                                                          26
                                                                                                                     Test 5: Automated Recovery Verification




                  to virtual disks are handled by redo logs.

SUREBACKUP RECOVERY VERIFICATION




   We tested Veeam’s SureBackup Recovery Verification feature by testing the recoverability of a backup of a VM acting as a primary
domain controller. We started our backed up VM directly from a backup file using the vPower NFS datastore and updates to the virtual
disks files of the VM were handled by redo logs. Once the virtual lab and virtual lab network were started, SureBackup published the VM
in the lab network and tested that the VM was running. Finally, scripts were run to test the VM’s roles as an Active Directory domain
controller, a global catalog server, and a DNS server. The entire process took 9 minutes and 13 seconds.


                     Beyond validating a backup file of a single VM, SureBackup Recovery Verification
                  supports the construct of an application group, which corresponds to an LoB workflow.
                  Wihin a group, VMs are placed in an ordered boot-sequence based on role and
                  application dependencies. Then each VM is assigned a series of tests to verify that all key
                  roles are functioning properly. As a result, Veeam takes VM backup verification from
                  simple byte comparisons to validating that VM backup files boot, internal VM
                  applications work, and external dependencies on other VMs function correctly.

                     Another important aspect of SureBackup is the ability to leave a virtual lab
                  environment running after verification tests complete. In addition, an IT administrator
                  can statically configure the appliance to masquerade a specific private-network address


                                                                                                                                                     27
                                                                           Test 5: Automated Recovery Verification




with a specific adress in the production network. Using this technique, we used up.time 5
to discover and monitor backed-up VMs running in a virtual lab. We also ran RDP
sessions on production systems that connected to the backed-up VM.

   By initiating a session with the backed-up VM from its corresponding production
VM, we were able to restore object-level data using application tools. Using this
technique, we successfully leveraged a SureBackup virtual lab environment with the most
current versions of Microsoft server infrastructure, including Exchange Server 2010 and
SQL Server 2008 R2, to access application items captured in backup files. As a result,
there is no need to wait for a backup software upgrade when a new version of a guest
VM’s OS or application is introduced.




                                                                                                           28
                                                                                                                    Test 6: File-Level Recovery




Test 6: Multi-OS VM File-Level Recovery
                                                                he        File Level Recovery
                                                           “TOS,Veeam can be Linux, Unix, (FLR) appliance”
                                                           VM’s
                                                                and restore wizard work independently of the
                                                                   which                      or the Mac OS.

                  RESTORATION EX MACHINA
                     Using Backup Exec 2010 R2, we were not able to implement a file-level recovery on
                  any backup file of VM that did not run Windows and that did not have a Backup Exec
                  2010 R2 agent installed. In contrast, any backup file created with Veeam Backup &
                  Replication v5 can be restored on a logical, file-level basis for any VM OS.

                                                                                             Using the Veeam Backup
 FILE LEVEL RECOVERY
                                                                                         & Replication v5 restore
                                                                                         wizard, we were able to
                                                                                         recover files from a backup
                                                                                         file of a VM running SUSE
                                                                                         Linux Enterprise v11. In this
                                                                                         process, Veeam Backup &
                                                                                         Replication leveraged the
                                                                                         vPower NFS datastore
                                                                                         construct used with Instant
                                                                                         Recovery and SureBackup to
                                                                                         launch a File Level Recovery
                                                                                         (FLR). appliance that
                                                                                         presented the files in the
                                                                                         target backup file.

                                                                                                  The restore wizard uses
                                                                                              the FLR appliance, which
                                                                                              runs on the vPower NFS
                                                                                              datastore, to present a logical
                                                                                              VM file-level view of the
                                                                                              contents of the target backup
                                                                                              file. The Veeam FLR
                                                                                              appliance and restore wizard
    We were able to perform a file level restore on a VM running SUSE Linux Enterprise Server work independently of the
  11 with Veeam Backup & Replication. In particular, we used a wizard, which launched an      VM’s OS, which can be
  FLR appliance on a vSphere host in order to present the contents of a backup file that was
  made available via a vPower NFS datastore.                                                  Linux, Unix, or the Mac OS.
                                                                                              As a result, IT administrators
                    can easily drill down on the directory structure of a logical VM in order to restore any
                    file.




                                                                                                                                            29
                                                                                                            Test 7: Item-Level Recovery




Test 7: Application-Independent Item-Level Recovery
                                                                                                      can use an
                                                                         “Since IT administratorsneedrecover for
                                                                               application’s own tools to
                                                                         item-level data, there is no     to wait
                                                  an upgrade to Veeam Backup &
Replication, when new versions of a guest VM’s OS or application software are introduced.”
                 OBJECT FOCUS
 SQL SERVER GRANULAR RECOVERY                                                     With the sophistication of VM
                                                                              applications continuing to
                                                                              increase, there is also a growing
                                                                              need for solutions to handle fine-
                                                                              grained problems associated with
                                                                              individual objects from VM
                                                                              applications, such as an Oracle
                                                                              Database, Microsoft Exchange
                                                                              Server, or Microsoft SharePoint.
                                                                              Restoring object-level data from
                                                                              applications is a much more
                                                                              complicated task than file-level
                                                                              restoration for a guest OS. While
                                                                              some object-level data restoration
                                                                              tasks can be orchestrated by
                                                                              exploiting explicit file structures
                                                                              within the guest OS,
                                                                              comprehensive restoration of
                                                                              object-level data often requires the
                                                                              ability to run one or more utility
                                                                              programs related to the associated
                                                                              application.

                                                                                    The need to leverage running
                                                                                 applications to restore object-level
                                                                                 data aligns precisely with the
                                                                                 capabilities of the Veeam’s
                                                                                 SureBackup feature. As a result,
                                                                                 Veeam’s vPower technology, which
                                                                                 provides the ability to run a VM
                                                                                 directly from a backup file, along
                                                                                 with the SureBackup virtual Lab
    Backup Exec 2010 R2 provides a Granular Recovery Technology option for full  construct, which provides a secure
  backups of VMs with a Remote Agent installed and running Active Directory,     environment to run a backup VM
  Exchange Server, or SQL Server. For our VM running SQL Server 2008 R2, we were
  able to restore any full database to our VM.                                   in parallel with the original
                                                                                 production VM are at the
                    foundation of Veeam’s Universal Application-Item Recovery (U-AIR).


                                                                                                                                   30
                                                                                                                            Test 7: Item-Level Recovery




ITEM-LEVEL RECOVERY WITH SUREBACKUP




    Item-level restoration with Veeam Backup & Replication v5 can be invoked with the Restore Wizard, which calls SureBackup or it can
 be started directly within SureBackup. Using item-level recovery with our VM running SQL Server 2008 R2, we were presented with a
 richer set of options than we had with Backup Exec 2010 R2. In particular, we were able to restore database items, such as individual
 tables, views, and stored procedures, to any VM running SQL Server. Furthermore, we could tailor a unique restore operation with a
 direct SQL query to any database on the backed up VM.


                     More importantly, there are no restrictions on IT when it comes to invoking
                  application tools to repair and restore item-level objects in a virtual lab. We were able to
                  masquerade the backed up VM on the production environment with a static production
                  address via the virtual lab appliance. As a result, we were able to use the Remote Desktop
                  Connection to set up a session on the backed up VM to run any native application from
                  any other VM. Since IT administrators can use the application’s own tools to recover
                  item-level data, there is no need to wait for an upgrade to Veeam Backup & Replication,
                  when new versions of a guest VM’s OS or application software are introduced.




                                                                                                                                                   31
                                                                                                                Test 8: Point-in-Time VM Replication




                                                                    or large sites that need to replicate mission-critcal
Test 8: Point-in-Time VM Replication                          “F     VMs to an off-site location, Veeam provides a built-
                                                              in solution that overcomes the need to restore data at the
                                                              DR site. ”
                    INCREMENTAL RPO
                       Enterprise-class data replication solutions attempt to meet lossless RPO requirements,
                    and introduce a level of high availability (HA) for DR support. To accomplish these twin
                    goals, replication solutions for virtual environments maintain multiple copies of VMs.

                       At the highest level of functionality and cost, VMs are kept in lockstep via synchronous
                    data transfers to all related VMs at the same time, using atomic data writes that must be
                    confirmed by all devices before they are committed, zero data loss among VMs can be
                    ensured. To lower complexity and trim costs, many replication schemes replace
                    synchronous with asynchronous updates, which can approach a near-lossless RPO
                    depending on network and device latencies.

                       For sites that define RPO requirements in minutes rather than milliseconds, point-in-
                    time replication offers a very easy way to implement a solution that provides all of the
                    HA benefits and meets the RPO granularity that the site requires to maintain business
                    continuity. In particular, Veeam Backup & Replication v5 is able to provide IT with a
                    very cost-effective alternative to zero-data-loss, synchronous, replication solutions
                    through the use of periodic reversed incremental backups.

                                                                                    Veeam’s Replication feature essentially
VM REPLICATION TOPOLOGY
                                                                                 provides an HA alternative to the vPower
                                                                                 Instant Recovery feature. With Instant
                                                                                 Recovery, the Veeam Server becomes a
                                                                                 single point of failure, unless Veeam
                                                                                 Backup & Replication v5 is installed on
                                                                                 multiple servers and the backup files are
                                                                                 shared or duplicated, Also direct access to
                                                                                 the second Veeam Backup server is
                                                                                 required to run Instant Recovery. On the
                                                                                 other hand, Veeam Replication creates an
                                                                                 operationally independent VM replica
  We set up a replica of our VM running Exchange Server on a separate            within a distributed vSphere
vSphere host. We then used automated incremental backups of the original         environment.
VM to keep the replica current. Operationally, the replica has all of the data
need to start at any time within its own datastore directory.
                                                                       The replica is created as a fully-
                    populated VM with the name of the original VM extended with the suffix _replica. Like
                    a standard backup, the replica assumes the logical network identity of the original VM
                    once it is started. What’s more, periodic incremental backups are stored with the replica’s
                    VMFS files to keep the replica up to date with the original VM.



                                                                                                                                             32
                                                                                                                Test 8: Point-in-Time VM Replication




                    Typically an IT administrator creates an automated schedule of incremental backup
                 updates to reflect the site’s RPO goal. Veeam supports a continuous update feature, which
                 launches new backup when an existing backup completes. To help conserve space, when
                 tight RPO constraints require frequent backups, the total number of backups stored can
                 be set to a fixed number, which creates a FIFO (First In First Out) queue for backup files,
                 which represent restore points.

                                                                                                 An important aspect of
VM REPLICATION PERFORMANCE
                                                                                             a replica is that it is
                                                                                             designed to remain
                                                                                             synchronized with the
                                                                                             original VM. As a result,
                                                                                             running in failover mode
                                                                                             is an aberration, since
                                                                                             saving any data changes
                                                                                             would break the ability of
                                                                                             the original VM to
                                                                                             synchronize data states
                                                                                             with the replica. As a
                                                                                             result, a replica is similar
                                                                                             to a VM running directly
                                                                                             from a backup file, in that
                                                                                             a special mechanism is
                                                                                             needed to store data
                                                                                             changes.

                                                                                                      Veeam Backup &
                                                                                                  Replication v5 uses a VM
                                                                                                  snapshot to capture data
                                                                                                  changes to a replica in
                                                                                                  failover mode. From an
                                                                                                  I/O viewpoint, this makes
                                                                                                  a replica similar to Instant
                                                                                                  Recovery with data
   We ran Jetstress on the Exchange Server replica in failover mode and measured performance      redirection. When we ran
 similar to Instant Recovery with data redirection, which also uses a snapshot to capture data
                                                                                                  Jetstress on a replica of
 changes. In particular, we sustained 270 email transactions plus 80 log transactions per second.
                                                                                                  our Exchange Server VM,
                    email and log transaction activity levels were nearly identical to the levels sustained when
                    we ran a backup of the VM with Instant Recovery and data redirection.

                    For large sites that need to replicate mission-critical VMs to an off-site location,
                 Veeam provides a built-in solution that overcomes the need to restore data at the DR site:
                 Only the original VMs need to be restored to enable resynchronization. On the other
                 hand, sites can still garner all of the RPO, RTO, and performance advantages of
                 replication locally using Veeam’s incremental backups and Instant Recovery


                                                                                                                                             33
                                                                                                                  Test Summary




Test Summary
                         eeam Backup & Replication v5 is able to support IT in providing
                   “V    the VMs in a vSphere environment with near lossless RPO and
                   aggressive RTO goals measured in minutes. ”
                   REWRITING THE RULES OF BUSINESS CONTINUITY
                      Driving the next wave of virtualization projects are the growing concerns expressed
                   by Line of Business (LoB) executives over business continuity. In a competitive 24x7
                   economic environment, computer downtime represents more than lost revenue to sales
                   and marketing executives. These executives equate lengthy computer outages with
                   potential losses in customer confidence and market share. As a result, senior LoB
                   executives expect IT to meet an RTO that is measured in hours rather than days and an
                   RPO that is close to lossless. With more mission critical applications moving into virtual
                   environments, Veeam Backup & Replication’s advanced features are essential for meeting
                   tight data protection constraints.

                                                                                             With respect to meeting
  VEEAM BACKUP & REPLICATION V5 FEATURE BENEFITS                                          RPO and RTO goals, Veeam
                                                                                          Backup & Replication v5 was
1) Agentless Backup for any VM: IT administrators do not install agents on VMs
                                                                                          designed explicitly to leverage
   or hosts, which allows all backup and restore operations, including file and data-
   item recovery, to work with any VM running any guest OS.
                                                                                          the advanced technology
                                                                                          found in a vSphere
2) Restart VMs from Backup Files for Near-Instantaneous RTO: Instant VM
   Recovery allows a VM to be started and run directly from a backup file with data
                                                                                          environment. As a result,
   redirection until the VM is fully restored online using vMotion, hot-cloning, or .     Veeam Backup & Replication
   Veeam’s FastSCP VM copy option..                                                       v5 is able to support IT in
3) Test and Authenticate Every Backup Job for Recoverability: SureBackup                  providing the VMs in a
   Recovery Verification starts VMs from backup files and runs application test scripts   vSphere environment with
   on the VMs in an isolated virtual lab environment to validate that applications are    near lossless RPO and
   running correctly.                                                                     aggressive RTO goals
4) Compress and Deduplicate Data Inline on any Backup Process: Veeam                      measured in minutes.
   Backup & Replication v5 includes compression and inline data deduplication that
   can be combined with incremental VM backups to provide the equivalent space                To provide this level of
   savingings of enterprise-class data deduplication systems while dramatically           data protection support,
   reducing the backup window.                                                            Veeam Backup and
5) Automate incremental Backups For Near-Lossless RPO: With data                          Replication v5 introduces
   deduplication and compression applied to incremental backups, which can be             vPower technology, which
   used with any recovery process as a restore point, low-impact incremental              allows a VM to be started and
   backups can be automated to run continuously.
                                                                                          run from a backup file. The
6) Restore or Repair Application Items: Run VMs from backup files in a virtual lab        key is a vPower NFS datastore
   to recover application-related objects using Veeam provided wizards or VM-
                                                                                          which is created on the Veeam
   resident application tools.
                                                                                          backup server, populated with
                                                                                          pointers to the contents of the


                                                                                                                                 34
                                                                                 Customer Value




backup file, and exported to the vSphere host server as read-only files. Depending on the
recovery scenario, Veeam institutes a number of optimal solutions, such as cache files,
redo logs, and VM snapshots, for capturing data updates to the VM’s logical volumes. IT
administrators can complete the restoration task by consolidating new and previous data
at any time using vMotion or hot cloning.

    Another key aspect of Veeam Backup and recovery is the use of data deduplication
and compression that focuses solely on the current backup process. This enables Veeam
to employ these technologies to any backup including incremental backups. This process
is very light weight when compared to deduplication schemes that cache and compare
fingerprints of all distinct strings of blocks encountered during backup processes. While
this scheme provides dramatic data reduction rates, the combination of the vSphere CBT
mechanism, incremental backup, and local data deduplication results in similar sized
data file in a fraction of the wall clock time required for the backup process.

   Moreover, IT can double down on the advantages garnered in incremental backup
processing to utilize very frequent—even continuous—automated incremental backups
to provide minimally spaced recovery points for mission critical systems. For the savvy
CIO, Veeam Backup & Replication is able to provide capabilities that go well beyond
what can be accomplished within a physical server environment. As a result, these
dedicated functions will not be found in any general purpose legacy product.




                                                                                                  35

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:65
posted:11/8/2011
language:English
pages:35