3 Intended Audience This document will discuss best practices of protecting your virtual machines in VMware vsphere environments using Veeam Backup and Replication solution. This Tintri Best Practices Guide for backup and recovery will assist individuals who are responsible for the design and deployment of data protection and disaster recovery solutions for VMs deployed on Tintri VMstore appliances. This document will discuss the use of VADP (vstorage APIs for Data Protection) for backups and Tintri s CloneVM and ReplicateVM technologies for data protection and disaster recovery (DR) of virtual machines in a VMware environment. Introduction Tintri VMstores are purpose-built storage for virtual machines. IT administrators with working knowledge of virtualization can easily deploy Tintri storage. When deploying Tintri storage, there are no prerequisite operations such as LUN provisioning, HBA compatibility checks, or FC LUN zoning operations. From a VMware administrator point of view, the entire Tintri VMstore is presented as a single datastore. Tintri VMstore delivers extreme performance, VM density, and a wide variety of powerful data management features, which are seamlessly integrated with vsphere. These examples of data management functionality include snapshots, clones, instant bottleneck visualization, and automatic virtual disk alignment. Tintri VMstore extends and simplifies the management of virtual machines (VMs) through intrinsic VM-awareness that reaches from the top of the computing stack, all the way down into the storage system. This best practice guide highlights the following when using Veeam Backup and Replication to protect VMs on a Tintri VMstore: Architectural overview of a VMware environment with Tintri VMstore and Veeam components. Veeam backup server configuration settings when protecting VMs on Tintri VMstore. The simplicity of protecting VMs and application-specific VMs such as Microsoft Exchange 2013 DAG and Microsoft SQL servers with Veeam on Tintri VMstore. Using Veeam Backup and Replication Instant VM Recovery with Tintri VMstore. Using Veeam Backup and Replication SureBackup with Microsoft applications such as Microsoft Exchange 2013 DAG hosted on Tintri VMstores. Using Universal Application Item Recovery (U-AIR) for Microsoft Exchange DAG servers on Tintri VMstores. Using U-AIR for Microsoft SQL servers on Tintri VMstores. 1

4 Consolidated List of Practices The table below includes the recommended practices in this document. Click the text in the Recommendation column or see the section later in the document that corresponds to each recommendation for additional information. Tags Backup Veeam Backup Server Veeam Backup Server Veeam Backup Server Backup Proxy Server Backup Proxy Server Backup Proxy Server Backup Repository Server Backup Repository Server Backup Repository Server Configuring Backups Configuring Backups Configuring Backups Virtual Lab Virtual Lab Recommendations DO: It is a Tintri recommendation to deploy Veeam Backup Server, Backup Proxy Server and Backup Repository Server virtual machines with thin provisioning on Tintri VMstores. DO: Connect to a management IP with ample bandwidth allocated for backups. Management-only interfaces are often configured for 1GB only, intended to be dedicated to management activity. DO: Consider adding an additional vmkernel port dedicated to backups with sufficient bandwidth, such as a 10 Gb connection. DO: Deploy separate backup proxy servers so that the Veeam workload is distributed across available backup proxies on multiple hosts in a large deployment. DO: It is recommended to configure multiple proxy hosts with 2 vcpus instead of fewer proxies with higher CPU counts. DO: Use Network transport mode for critical VMs. With HotAdd transport for backups, connections to critical VMs may experience long pauses, which could disrupt the availability of the VMs to users. It is recommended to use backup proxy servers with Network transport mode for critical VMs in this case. DO: Ensure that each of the backup proxy servers has a minimum of one CPU core for each task. DO: When configuring a backup repository, use the Limit maximum concurrent tasks to: checkbox to control the number of concurrent jobs to the storage. DO: It is recommended that the backup repository is a Windows-based server. DO: Unselect decompress backup data blocks before storing to backup repository server virtual machines on Tintri VMstores. Initials backup of a guest virtual machine may take a little longer but with VMware s CBT, subsequent Veeam backup jobs will only backup changed data blocks and will improve backup performance in the long run. DO: When configuring backup jobs, it is recommended to enable deduplication and changed block tracking in the Veeam backup job Advanced Settings Window. DO: Check Enable application-aware image processing and configure Guest OS Credentials for protecting Microsoft enterprise applications. DO: Enable guest file system indexing if you require the use of the Veeam Backup Enterprise Manager and the Veeam Search Server to perform file search on virtual machines. It is recommended to uncheck guest file system indexing for most Veeam backup jobs, as it will affect backup performance on virtual machines with larger file systems. DO: Host Veeam virtual labs on Tintri VMstores to take advantage of Tintri s VM-level monitoring and data management functionalities. DO: The use of a proxy appliance in a Veeam virtual lab is recommended. 2

5 Tags Virtual Lab Virtual Lab Veeam Sure Backup Veeam Sure Backup Veeam Sure Backup Replication Replication Replication Replication VM Copy and Backup Copy Recommendations DO: The use of the Advanced single-host or Advanced multi-host option is recommended when there are different networks for the virtual machines. If distributed virtual switch (DVS) is available, multi-host option is recommended to evenly distribute lab and recovery VMs across multiple hosts, especially if the VMs are large and resource intensive, or there are many VMs required in the application group(s). DO: Test the virtual lab(s) with the application groups to ensure that SureBackup, U-AIR or SandBox processing are functional before making the services available to Veeam Backup Enterprise Manager requests. DO: When creating a SureBackup job, the Keep the application group running once the job completes option allows the SureBackup job to stay active after the backup validation. DO: For each VM within the SureBackup job, verify that the correct role has been defined in the Application Group. DO: Skip the validation for application group for U-AIR requests because the CRC checks could take time to complete when there are multiple VMs within a SureBackup Job. DO: For VMs that host Microsoft applications, enable Veeam Replication s builtin functionality to process applications and truncate application transaction logs as necessary. DO: A Veeam replication job can be configured to execute after a successful Veeam backup of a Microsoft application virtual machine. If the transaction logs are necessary in the backups to minimize data loss and a backup has not been performed before a Veeam replication job, it is recommended to use Do not truncate logs on the Veeam replication job. DO NOT: If you are using Tintri s CloneVM functionality for doing recovery operations, do not select Customization option i.e., select None for customization option. DO: With any VMs that host Microsoft applications, remember to include all the dependencies when replicating VMs using Tintri ReplicateVM feature. This will ensure that the virtual machines that have Microsoft applications can be powered on and brought online successfully at the DR site. DO: Import using the Veeam.vbm backup metadata file as it provides better performance. If there is no corresponding.vbm file, import using the.vbk file. 3

6 Backup Environment In this document, the referenced VMware vcenter architecture manages 3 ESXi hosts that have been configured with standard networks and distributed port groups. Veeam components are deployed on Windows 2012 R2 virtual machines on a Tintri VMstore. The Veeam Backup Server and the Veeam Backup Enterprise Manager is deployed on a single Windows 2012 R2 virtual machine. The virtual machines must meet the system requirements for the Veeam software installations. Veeam Component Veeam Backup Server Backup Proxy Server Backup Repository Server Minimum CPU And RAM Requirements CPU x86-64 processor with a minimum of 4 GB RAM plus 500MB RAM for each concurrent job CPU x86 with a minimum of 2 cores and 2 GB RAM plus 200MB for each concurrent task CPU x86 (x86-64 is recommended) with a minimum of 4 GB RAM plus 2GB RAM for each concurrent job For additional information, review Veeam Backup and Replication version 7.x User Guide for VMware Environments for detailed system requirements. DO: It is a Tintri recommendation to deploy Veeam Backup Server, Backup Proxy Server and Backup Repository Server virtual machines with thin provisioning on Tintri VMstores. Veeam Backup Server When configuring a Veeam Backup Server to protect VMs, a management vmkernel IP of the ESX/ESXi hosts must be accessible on required ports. See Veeam KB article 1518 for port requirements if hosts are firewalled. If multiple management IPs exist for your hosts, consider using HOSTS entries on your Veeam Backup Server and Veeam Proxies to choose which IP to connect to and backup from. From the Veeam backup server log, if the ESX/ESXi host is not accessible, a backup attempt could fail with an error message similar to the following: NBD_ClientOpen: Couldn t connect to <ESXi Host>:902 Failed to connect to server <ESXi Host>:902\n. DO: Connect to a management IP with ample bandwidth allocated for backups. Management-only interfaces are often configured for 1GB only, intended to be dedicated to management activity. DO: Consider adding an additional vmkernel port dedicated to backups with sufficient bandwidth, such as a 10 Gb connection. In this white paper, backup proxy servers are deployed as virtual machines on a Tintri VMstore to allow Veeam Backup and Replication jobs to take advantage of HotAdd transport. 4

7 Although a Veeam backup server can be deployed as a backup proxy, it is recommended to deploy separate backup proxy servers so that the Veeam workload can be offloaded and distributed across available backup proxies in a large environment. DO: Deploy separate backup proxy servers so that the Veeam workload is distributed across available backup proxies on multiple hosts in a large deployment. When there are remote sites that require data protection, the use of multiple backup proxy hosts is more efficient and also ensures that the best routes are available for backup and replication traffic. Backup Proxy Server When configuring a new VMware backup proxy server, be aware that the following error message could appear Network path was not found if the network path to the proxy host is not accessible. In order to install Veeam s Installer Service and Veeam Transport components on the backup proxy host, the credentials for the backup proxy host/server must have access to the ADMIN$ share of the proxy host. DO: It is recommended to configure multiple proxy hosts with 2 vcpus instead of fewer proxies with higher CPU counts. This allows the proxies to be moved between hosts and is less impactful. In addition, when HotAdd transport mode is used, multiple backup proxy hosts allow for multi-processing of virtual machines (VMs) and VMDKs, rather than having a single proxy server processing one VMDK (from the same VM) at a time. For HotAdd transport mode, the backup proxy server must have access to the ESX/ESXi host of the VM guest OS that will be backed up. Veeam jobs using the backup proxy host that is configured to use HotAdd transport exclusively, will fail the backup jobs if the proxy host for HotAdd cannot access the ESX/ESXi hosts. Veeam jobs will fail with the following error message in the job detail: If a backup proxy server is migrated between ESXi hosts, enable the Failover to network mode if primary transport modes fail or are unavailable on the backup proxy server properties. Veeam jobs that 5

8 use that backup proxy server will automatically attempt with NBD when HotAdd transport mode is not available. This method ensures that your backups for all VMs within that backup job will run and complete successfully. It is not necessary to manually select Network transport mode on the backup proxy server in this case. Manually switching the transport mode affects all backup jobs to the backup proxy host. Veeam Backup and Replication will also select the best transport mode to use if the Automatic selection is configured for the proxy host. If encryption over the wire is required for backup I/O, NBDSSL transport mode is configured when NetWork transport mode and Encrypt LAN traffic in network mode (SSL) is selected in the Veeam backup proxy server properties. Veeam jobs to that particular backup proxy server that uses NBDSSL transport mode will experience slower performance in comparison to Virtual Appliance (HotAdd) transport mode or Network (NBD) transport mode. For additional information on VADP backup transport modes, refer to the Tintri Backup and Recovery Best Practices with Tintri VMstore paper for generic backup and recovery solutions that are common with backup software applications. Note: With HotAdd transport mode, a VM can encounter lower IOPS during a VMware VADP snapshot removal phase of a backup due to the locks placed on the storage. This could lead to the VM being unresponsive or lost connections to the VM during backups using HotAdd transport mode. The following VMware KB article provides additional detail: A snapshot removal can stop a virtual machine for long time ( ). Additional information is also available from Veeam s KB: If a virtual machine connection is affected during a backup with HotAdd transport, NBD transport is recommended for the virtual machine for Veeam jobs. It is recommended to use Network transport mode for critical VMs. DO: Use Network transport mode for critical VMs. With HotAdd transport for backups, connections to critical VMs may experience long pauses, which could disrupt the availability of the VMs to users. It is recommended to use backup proxy servers with Network transport mode for critical VMs in this case. 6

9 Initial backup of a VM using NBD transport may take a little longer when compared to HotAdd transport. However, since Veeam utilizes VMware s Changed Block Tracking (CBT), subsequent backups of VMs with CBT enabled with NBD transport are comparable to HotAdd transport. With Veeam Backup and Replication version 7.x, parallel processing is enabled by default. However, in order to use the parallel processing capability, the proxy servers must have the minimum system requirements of a single CPU core for each task. DO: Ensure that each of the backup proxy servers has a minimum of one CPU core for each task. Backup Repository Server It is recommended to deploy additional hosts as backup repositories in large-scale virtual environments to reduce the workload on the Veeam Backup Server. Backup repositories can be created on the backup proxy server. Follow Veeam s user guide on system requirements for configuring a backup repository server. DO: When configuring a backup repository, use the Limit maximum concurrent tasks to: checkbox to control the number of concurrent jobs to the storage. 7

10 DO: It is recommended that the backup repository is a Windows-based server. A Windows-based backup repository can perform the role of the Veeam vpower NFS server and take advantage of Veeam s vpower technology to perform multi-os file-level restore, Instant VM Recovery, SureBackup, and Universal Application Item Recovery (U-AIR) requests. If a backup repository is deployed on a backup proxy server, HotAdd transport is efficient as the backup I/O does not need to use the storage network to write to a separate backup repository server. On the new backup repository server, it is also recommended to select the Align backup file data blocks using the Advanced setting button of the New Backup Repository Window. Backups to a backup repository server hosted on a Tintri VMstore allow your backups to take advantage of Tintri s deduplication technology for increased savings. DO: Unselect decompress backup data blocks before storing to backup repository server virtual machines on Tintri VMstores. Initials backup of a guest virtual machine may take a little longer but with VMware s CBT, subsequent Veeam backup jobs will only backup changed data blocks and will improve backup performance in the long run. Using the Tintri UI to monitor resource utilization Tintri dashboard and the VM view provide a VMware Administrator the features to monitor resource utilization of VMs and the Veeam servers. The Performance Reserve Changers in the Tintri dashboard is very useful when troubleshooting resource usage of virtual machines with applications and backup servers. For example, DC-W (a Windows Exchange 2013 server) in the virtual environment shows Host CPU % utilization greater than 78% for a long duration (see screenshot). The VM Administrator noticed that this particular VM has been consuming resources on the ESX/ESXi host for a week from the Tintri Virtual Machines tab. Tintri s intrinsic VM-level monitoring simplifies troubleshooting and monitoring of resource utilization of application virtual machines and backup virtual machine servers. This allows a VM administrator to manage VMs and a backup administrator to manage data protection rather than spending hours tracking down the issue. 8

11 A review of the Windows Task Manager on DC-W shows that the Microsoft SharePoint Search Component on the Windows Exchange 2013 server is consuming resources on the virtual machine. The ease to narrow down and focus on a particular VM when troubleshooting issues or a backup directly from the storage system is an unparalleled advantage of Tintri VMstore systems. Configuring Backups DO: When configuring backup jobs, it is recommended to enable deduplication and changed block tracking in the Veeam backup job Advanced Settings Window. If writing to deduplicating storage appliances or using Tintri VMstores to host Veeam backup repository server virtual machines, it is recommended to use traditional incremental backups with periodic fulls. For virtual machines that host Microsoft applications such as Microsoft Exchange in Database Availability Group (DAG) configuration, Microsoft SQL Server in AlwaysOn Availability Groups (AO AG), and Microsoft SharePoint, ensure that the Guest Processing in the backup jobs has Enable application-aware image 9

12 processing and Guest OS Credentials configured. Failure to provide the correct Guest OS credentials will result in failed application-aware image processing. DO: Check Enable application-aware image processing and configure Guest OS Credentials for protecting Microsoft enterprise applications. DO: Enable guest file system indexing if you require the use of the Veeam Backup Enterprise Manager and the Veeam Search Server to perform file search on virtual machines. It is recommended to uncheck guest file system indexing for most Veeam backup jobs, as it will affect backup performance on virtual machines with larger file systems. In the customize guest processing options for individual VMs, select the Require successful application processing and Truncate logs on successful backup only for VMs with Microsoft applications. Veeam Backup and Replication will stop the backup of the VM(s) with Microsoft applications if any VSS error occurs if Require successful application processing is enabled. When Truncate logs on successful backup only is selected, Microsoft application transaction logs are truncated only after a backup job completes successfully. If the transaction logs cannot be truncated for some reason, the Microsoft application transaction logs will remain untouched in the VM guest OS until the next runtime process. A Veeam backup administrator and the Microsoft application administrator can use this method to troubleshoot any backup issues earlier to ensure successful log truncation for subsequent backups of the virtual machines with Microsoft applications. In the Indexing tab, select Index everything except: option, the default option will index everything on the VM except for system folders if Enable guest file system indexing is enabled in the Guest Processing step of the Backup Job wizard. Indexing of a VM also enables restore of files with a single click. In addition, enabling indexing allows for fast and accurate search for VM guest OS files when using the Veeam Backup Enterprise Manager Files search feature. If the Enable guest file system indexing is not checked in the Guest Processing of the Backup Job properties, indexing will not occur even if an indexing option is selected in the Processing Settings Window. 10

13 With the application-aware image processing option enabled and the right Domain\user credentials that has read and write permissions to files configured, Veeam Backup Server will successfully backup any guest VMs with Microsoft applications installed. The following is a successful backup of two Microsoft Exchange 2013 (configured with Exchange DAG) servers running on a Tintri VMstore. Note: Backups using proxy host virtual machines and backup repository virtual machines on Tintri VMstores will temporarily affect storage latency and flash hit ratios during the backup process. Application Group Veeam s application group is used to verify VMs that have dependencies with other services and components in a virtual environment. For example, Exchange 2013 DAG consists of a minimum of two Exchange servers, a witness server, the domain controller, and the DNS virtual machines. To use an application group for Microsoft applications, the process requires: 1. Configuring application groups for Microsoft Applications. 2. Configuring virtual labs. 3. Configuring SureBackup jobs that will use the applications groups to be deployed in virtual labs for validating backups, fulfilling U-AIR requests, fulfilling Veeam Explorer requests, etc. A Veeam application group creates a system of interconnecting and interacting parts that an application depends on for verification. Along with the boot priority, the role and tests of each VM must be specified within the application group. On the Veeam Backup Server, an Exchange Application Group was created with the following virtual machines: Dom A domain controller and DNS server DC-W An Exchange 2013 server DC-W2012-6Wit An Exchange 2013 witness machine DC-W An Exchange 2013 server DC-DAG The Exchange 2013 DAG server exists as an entry in the DNS server in the domain 11

14 Here s another example of a SQL application group with the following virtual machines: Dom A domain controller and DNS server DC-W20127-SQL A Microsoft SQL 2012 server Veeam application groups can be used for SureBackup verification jobs and Virtual Labs, in addition to fulfilling requests such as Exchange Application Item Recovery or SQL Server Application Item Recovery that are submitted to the Veeam Backup Enterprise Manager. Virtual Lab A Veeam virtual lab is an isolated fenced off lab environment for verifying VMs with SureBackup. It is also used for fulfilling Veeam U-AIR requests and On-Demand Sandbox processing. DO: Host Veeam virtual labs on Tintri VMstores to take advantage of Tintri s VM-level monitoring and data management functionalities. DO: The use of a proxy appliance in a Veeam virtual lab is recommended. The proxy appliance facilitates the communication between the production environment and the isolated networks in the virtual lab. In addition to the use of a proxy appliance, Veeam version 7.x also provides advanced networking properties for deploying virtual labs when there are multiple production networks in the environment. This is very useful when production virtual machines within the application group are located on different networks. 12

15 DO: The use of the Advanced single-host or Advanced multi-host option is recommended when there are different networks for the virtual machines. If distributed virtual switch (DVS) is available, multi-host option is recommended to evenly distribute lab and recovery VMs across multiple hosts, especially if the VMs are large and resource intensive, or there are many VMs required in the application group(s). Note: Running a Virtual Lab, SureBackup job, or U-Air Recovery will lock all dependent Veeam files while running, which will prevent backups and replications that need to alter those files. This applies when a job is configured to use Reverse-incremental (with synthetic rollups being applied each backup), or during periods when synthetic rollups are used to convert.vib incremental files into.vbk (Base) and then into.vrb (rollback) files. To minimize this affect, consider using incremental jobs that rollup weekly during the weekend. In this case, a virtual lab can t be running through the weekend, but is available throughout the week. These advanced options ensure that the VMware Administrator and the Veeam Backup Administrator can create virtual labs to meet the requirements of a single-host or multi-hosts configurations. If a virtual lab is configured incorrectly, errors such as the following can occur when attempting a SureBackup validation. Here is another example of a virtual lab with an application initialization error of a SQL 2012 server in a SureBackup job. In this case, the Microsoft SQL server dependencies were not included in the application group and the user stopped the virtual lab job due to the application initialization failure. DO: Test the virtual lab(s) with the application groups to ensure that SureBackup, U-AIR or SandBox processing are functional before making the services available to Veeam Backup Enterprise Manager requests. 13

16 In a VMware environment with multiple networks and DMZs, use the Networking and the Isolated Networks options to correctly map the networks and VLANs to ensure a virtual lab can be deployed successfully. Tintri VMstore is designed specifically for VMs and uses FlashFirst architecture to provide consistent latencies; so spinning up VMs in virtual labs is very quick for fulfilling Veeam SureBackup or Veeam U-AIR requests and eliminating latencies. Use the Tintri vsphere Web Client plug-in or the Tintri VMstore UI to monitor datastore and resource performance. Note: Veeam backup restore points that have been stored for a long time on the backup repository host could temporarily affect latency and flash hit ratio because data that has been inactive is retrieved from non-flash storage. Veeam SureBackup A Veeam SureBackup job is a VM backup recovery verification job. SureBackup takes advantage of Veeam vpower NFS service to mount a backup file as if it was a regular VMDK file. Veeam SureBackup validates consistency of virtual machine backup files without impacting a production infrastructure. A Veeam SureBackup job is also used for Universal Application-Item Recovery. DO: When creating a SureBackup job, the Keep the application group running once the job completes option allows the SureBackup job to stay active after the backup validation. The SureBackup job can be used to fulfill Veeam Backup Enterprise Manager requests such as U-AIR for Exchange or U-AIR for SQL Server. DO: For each VM within the SureBackup job, verify that the correct role has been defined in the Application Group. 14

17 Based on the defined role for each VM, you can use the default Veeam test scripts to validate the application installed on the VM is working correctly. In the Settings section of the SureBackup job properties, the Validate consistency of virtual machines backup files will run CRC checks on the backup files of the VMs to ensure that the file is not corrupted. DO: Skip the validation for application group for U-AIR requests because the CRC checks could take time to complete when there are multiple VMs within a SureBackup Job. Note: The Keep the application group running once the job completes option in the Application Group step of the SureBackup Job wizard will automatically enable Skip validation for application group. The option is checked and also greyed out to prevent Skip validation from being disabled in this case. A Veeam SureBackup job depends on the virtual lab being deployed successfully with the network mappings in a multi-network VMware environment. This ensures all VMs within the application group can be powered on and successfully validated. It is also dependent on the application group being setup with the correct virtual machine dependencies to be successful. Here are side-by-side examples of successful SureBackup jobs for Exchange 2013 DAG servers and SQL 2012 servers on a Tintri VMstore. Replication Replication can be achieved using Native Veeam replication option or Tintri s ReplicateVM feature. There are benefits to using Tintri ReplicateVM instead, such as not locking a VM during replication, which would prevent a backup job from completing, which puts all VMs in that backup job at risk of missing SLA targets. Tintri ReplicateVM is WAN-efficient because only changed blocks are sent after compression and deduplication. Veeam replication copies a VM from its primary location to a destination location for keeping redundant copies of backup for DR purposes. The copy at the destination is an exact replica of the VM and registers the VM on the target ESX/ESXi host and syncs it with the original VM. When configuring a Veeam replication job, the DR site information must be provided. For example, if there is low bandwidth 15

18 connection between the source and destination sites, the Low connection bandwidth checkbox must be selected to allow seeding. Another example is if there are separate virtual networks at the DR site, the Separate virtual networks checkbox must be selected to enable network remapping for the VMs that are to be replicated to the DR site. If the network remapping is enabled, the virtual machines defined in the replication job will be mapped to the correct virtual networks at the DR site so that the systems can be powered on and brought online. DO: For VMs that host Microsoft applications, enable Veeam Replication s built-in functionality to process applications and truncate application transaction logs as necessary. Veeam Replication feature is useful for application-aware image processing of VMs that require copies at DR sites. DO: A Veeam replication job can be configured to execute after a successful Veeam backup of a Microsoft application virtual machine. If the transaction logs are necessary in the backups to minimize data loss and a backup has not been performed before a Veeam replication job, it is recommended to use Do not truncate logs on the Veeam replication job. In the Seeding step of the replication job configuration wizard, Veeam allows the initial seed to be selected from any backup repository in the DR site that contains a backup copy of the VM. Veeam replication uses VADP transport modes to access the source VM image to copy the VM data to the DR site. When a successful replica copy is created at the DR site, Veeam transport service retrieves only changed data blocks for all subsequent replication jobs for that VM. By ensuring that the right backup repository is selected for seeding and a replica mapping is selected at the DR site, Veeam replication jobs will be more efficient. Replication and recovery with Tintri ReplicateVM Tintri SnapVM, CloneVM, and ReplicateVM features complement Veeam Replication feature. SnapVM 16

19 can be used to protect VMs locally. SnapVM, CloneVM, and ReplicateVM features can be accessed from the vsphere Web Client UI (Tintri vsphere Web Client plug-in must be installed) directly. Right-click on the virtual machine that needs to be protected. Click All Tintri Actions and select any of the Tintri features to protect your VM on-site or off-site. If a VM was replicated using Veeam s Replication feature, we recommend making a Tintri clone of the VM if there is a requirement to power on and test the VM at the DR site. Using Tintri s Clone feature will ensure that subsequent Veeam replications of the VM are not interrupted. This will ensure that SLAs for Veeam backups and Veeam replication are not breached. DO NOT: If you are using Tintri s CloneVM functionality for doing recovery operations, do not select Customization option i.e., select None for customization option. Tintri s CloneVM and ReplicateVM solutions are also very useful when you want to protect a Veeam backup repository server. An advantage that Veeam Backup and Replication solution has over other enterprise backup solutions is that a valid backup image can be recovered from any Veeam Backup Server that has read access to the backup repository. There are no additional Veeam application specific pre-requisites that need to be completed other than a simple import of the backup restore point from the backup repository. 17

20 Therefore, a Veeam backup repository server can also be protected using Tintri s ReplicateVM feature. However, be aware that the initial Tintri s replication of the backup repository server may need to catch up to create a replica virtual machine at the DR site. Tintri s ReplicateVM feature is very useful as it also complements Veeam s Backup Copy feature. When using Tintri s protect functionality to protect a backup repository server or a critical VM, select the appropriate snapshot schedule that meets your protection requirements and protect by replicating snapshots to another Tintri VMstore for your critical VMs. In addition, the local retention period and remote retention period are independent of each other. For DR purposes, this means that the snapshot of a critical virtual machine or a backup repository server can be retained for a longer period offsite. For most VMs, it is recommended to keep the number of Tintri s snapshots per VM to a minimum. Veeam creates a lot of data change between backups if using reverse incrementals. Each snapshot could grow very large. It is recommended to keep 1 day for most virtual machines as each snap contains all the Veeam generations of change within. Use Tintri s ReplicateVM feature to protect critical VMs on Tintri VMstores. ReplicateVM send only blocklevel changes after deduplication and compression reducing WAN utilization by up to 95 percent for efficient creation of DR copies. For example, Tintri VMstore 2 contains VM B that has 2 of the 3 data blocks to create a replica of VM A from source Tintri VMstore 1. ReplicateVM only sends required unique changed blocks after compression to create VM A replica on destination Tintri VMstore 2. To restore VM A replica on destination Tintri VMstore 2, it is as easy as: 1. Selecting the replica VM from the Tintri VMstore UI at the DR site 2. Clone from the replica VM with Customization set to None to ensure VM SID is not modified 18

vpower What s New in Veeam Backup & Replication v5 Veeam Backup & Replication v5 is a major new release of Veeam s industry-leading data protection and disaster recovery solution for VMware vsphere that

This document shows you how to use a Drobo iscsi SAN Storage array with Veeam Backup & Replication version 5 in a VMware environment. Veeam provides fast disk-based backup and recovery of virtual machines

Veeam Backup & Replication for VMware Version 8.0 Evaluator s Guide May, 2015 2015 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication

Veeam Backup & Replication Version 6.5 User Guide VMware Environments November, 2012 2012 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this

Veeam Backup & Replication and Iomega Easy to use backup storage with StorCenter PX Presenter Name / Event Name What are the challenges? Managing VMware-centric environments requires a new way of thinking

Backing Up the CTERA Portal Using Veeam Backup & Replication CTERA Portal Datacenter Edition May 2014 Version 4.0 Copyright 2009-2014 CTERA Networks Ltd. All rights reserved. No part of this document may

Veeam Backup Enterprise Manager Version 7.0 User Guide August, 2013 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may

PN: 210-0317-04 Using Veeam Backup and Replication Software with an ExaGrid System Copyright No part of this document may be reproduced or transmitted in any form or by any means without the express written

Veeam Backup & Replication What s new in v6 GOLD AWARD NEW TECHNOLOGY Veeam Backup & Replication v6 won Best New Technology at VMworld 2011. This is the second year in a row Veeam Backup was selected as

ArCycle vmbackup for VMware/Hyper-V User Guide 2 Copyright Copyright ArCycle Software, Ltd., 2011-2014. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,

VS Why Vembu is Better TECHNOLOGIES www.vembu.com Copyright Information Information in this document is subject to change without notice. The entire risk of the use or the results of the use of this document

This document shows you how to use a Drobo iscsi array with Veeam Backup & Replication version 6.5 in a VMware environment. Veeam provides fast disk-based backup and recovery of virtual machines (VMs),

Administrator's Guide EN-000193-00 You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product

EMC VIPR SRM: VAPP BACKUP AND RESTORE USING EMC NETWORKER ABSTRACT This white paper provides a working example of how to back up and restore an EMC ViPR SRM vapp using EMC NetWorker. October 2015 WHITE

Virtual Appliance Setup Guide 2015 Bomgar Corporation. All rights reserved worldwide. BOMGAR and the BOMGAR logo are trademarks of Bomgar Corporation; other trademarks shown are the property of their respective

Veeam Backup & Replication v5 with vpower and Drobo SAN Storage for Business What Are the Challenges? Managing Vmware-centric environments requires a new way of thinking Attempting to manage virtual environments

VMware vcloud Air - Disaster Recovery User's Guide vcloud Air This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition.

BDR TM for VMware VMware BACKUP WITH VEMBU VEMBU TECHNOLOGIES www.vembu.com Copyright Information Information in this document is subject to change without notice. The entire risk of the use or the results

Installing and Configuring vcenter Support Assistant vcenter Support Assistant 5.5 This document supports the version of each product listed and supports all subsequent versions until the document is replaced

NovaBACKUP Virtual Dashboard User Manual NovaStor / April 2015 2015 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications are subject to

Veeam Backup & Replication Version 8.0 February, 2016 2016 Veeam Software. All rights reserved. All trademarks are the property of their respective owners. No part of this publication may be reproduced,

To ensure the functioning of the site, we use cookies. We share information about your activities on the site with our partners and Google partners: social networks and companies engaged in advertising and web analytics. For more information, see the Privacy Policy and Google Privacy &amp Terms.
Your consent to our cookies if you continue to use this website.