Using Veeam Backup and Replication™ Software with an ExaGrid Systemgo.veeam.com/rs/veeam/images/Best_Practices_and... · · 2018-04-04Software with an ExaGrid System PN: 210-0317-04

Using Veeam® Backup and Replication™Software with an ExaGrid System

PN: 210-0317-04

Copyright

No part of this document may be reproduced or transmitted in any form or by any means without the express written permission of ExaGrid Systems, Inc.

© 2003-2014 ExaGrid Systems, Inc. All rights reserved. Printed in USA.

This document, the associated software, and the associated online documentation are the property of ExaGrid Systems, Inc. or its licensors, as applicable, and are loaned to the user under the terms of the ExaGrid Systems, Inc. End User License Agreement. Unauthorized copying or use of the software or any associated materials is contrary to the property rights of ExaGrid Systems and is a violation of state and federal law.

Trademarks

ExaGrid is a registered trademark of ExaGrid Systems, Inc. ExaGrid Systems (Logo), InstantDR, InfiniteFiler, GRIDdisk and Intelligent Disk-based Data Protection are all trademarks of ExaGrid Systems, Inc. All third-party trademarks are the property of their respective owners.

License Agreement

This document, the associated software and the associated online documentation are the property of ExaGrid Systems, Inc. or its licensors, as applicable. The use of these materials and the software is strictly limited to those users who have signed the ExaGrid Systems, Inc. End User License Agreement.

For any software acquired directly or indirectly on behalf of a unit or agency of the United States Government, whether for civilian agencies or for units of the Department of Defense, the software is a commercial item or commercial computer software (and documentation), and pursuant to Section 12.212 of the Federal Acquisition Regulations (FAR) or DoD FAR Supplement Section 227.7202, is provided under restricted rights as enumerated in the End User License Agreement.

Using Veeam Backup and Replication™ Software With an ExaGrid System iii

Preface

This guide provides instructions on how to use the Veeam Backup and Replication Software backup product with the ExaGrid System. This guide assumes the reader is experienced with Veeam and the ExaGrid System.

Veeam provides a number of ways to backup data. This guide provides basic backup examples. More experienced users will be able to use the information provided in this guide and build more complex backup schemes.

PurposeThe purpose of this guide is to suggest configurations, processes and procedures that will optimize the use of Veeam with the ExaGrid System.

iv ExaGrid Systems

Related Documentation

Contacting ExaGrid Technical SupportIf you have technical questions about this product that are not answered in this document contact ExaGrid Support:

■ Email: [email protected]■ Phone: 800-868-6985 and at the prompt, press 2.

Title Part Number

ExaGrid Administrator’s Guide 210-0165-xx

ExaGrid Release Notes 210-0174-xx

Contents v

Contents

1. Veeam and ExaGrid’s Disk-Based Backup System 1

Deduplication Ratios 2

Using the Veeam Deduplication Report PowerShell Script 2

ExaGrid’s Landing Space and Veeam 4

Instant VM Recovery from an ExaGrid System 4

Backup Copy 4

Tape Copy 5

Instant File-Level Recovery 5

2. Using Veeam With an ExaGrid System 6

3. ExaGrid Veeam Shares 8

ExaGrid Share Considerations 8

How to Create an ExaGrid Veeam Share 9

4. Recommended Veeam Settings 11

5. Using Server Message Block (SMB) Signing 14

6. Veeam Step-by-Step 16

Creating a Veeam Repository 16

Creating a Veeam Backup Job 21

vi ExaGrid Systems

7. Backup Copy 26

Making Local Copies 26

Making Remote Copies 28

8. Tape Job 30

9. Recovering From the ExaGrid Source Share 31

10. Disaster Recovery 32

1

Veeam and ExaGrid’s Disk-Based Backup System

The combination of ExaGrid’s and Veeam’s industry-leading VMware and HyperV data protection solutions allows customers to take advantage of Veeam Backup & Replication in VMware virtual environments on ExaGrid’s disk-based backup system. This combination provides fast backups and efficient data storage as well as replication to an off site location for disaster recovery.

The ExaGrid system fully leverages Veeam Backup & Replication’s built-in backup to disk capabilities and ExaGrid’s zone-level data deduplication for additional data reduction (and cost reduction) over standard disk solutions.

Customers can use Veeam Backup & Replication’s built-in source-side deduplication in concert with ExaGrid’s disk-based backup system with zone-level deduplication to further shrink backups.

In addition, customers can replicate backups to off site storage for disaster recovery purposes without sacrificing performance of critical backup and recovery features.

By combining the power and performance of Veeam-based VMware virtual machine backups and the ExaGrid System, customers can meet backup and disaster recovery goals quickly and easily.

2 ExaGrid Systems

Deduplication RatiosExaGrid Systems recommends configuring Veeam to deduplicate data within a job. Typically Veeam will achieve a 2:1 deduplication ratio.

Once the deduplicated Veeam backup data has landed, the ExaGrid System will further deduplicate the Veeam data anywhere from 3:1 to 5:1.

The ExaGrid System will report how well it deduplicated the Veeam backup data. The ExaGrid System will not report how well Veeam deduplicated the data.

To calculate the overall deduplication ratio achieved by both Veeam and your ExaGrid System; multiply the typical Veeam deduplication ratio of 2:1 by the deduplication ratio reported by your ExaGrid System. For example:

Veeam 2:1 x ExaGrid 4:1 = 8:1

To determine the exact deduplication achieved by your Veeam/ExaGrid System solution, use the Veeam Deduplication Report PowerShell Script.

Using the Veeam Deduplication Report PowerShell ScriptThe Veeam PowerShell Script generates a report that details the deduplication ratios achieved by your Veeam server. The ratios in the PowerShell report will calculate the overall deduplication ratios achieved by your ExaGrid/Veeam backup solution.

To use the Veeam PowerShell Script

■ Ensure that Veeam’s PowerShell Snapin is installed on your Veeam Server. The PowerShell Snapin is installed via the Veeam Backup & Replication Installer as described in: http://www.veeam.com/kb1489#/kb1489

■ Download the script to your Veeam server:

1. From the ExaGrid main menu, click Help.

2. From the drop down menu, click the Online Library. The on line library is displayed.

3. Open the Named VM Backup Applications section.

4. Right click on the Veeam Deduplication Report PowerShell script

5. Select the menu option to save the script as VeeamDedupReport.ps1 to your Veeam server.

Using Veeam Backup® and Replication™ Software With an ExaGrid System 3

■ Open a Veeam PowerShell window from the Veeam user interface on your Veeam server:

■ Run the script:

1. Via the PowerShell window navigate to the script’s location.

2. At the prompt, enter:

.\VeeamDedupReport.ps1 -egridDedup <ExaGrid Ratio>

For example, if your ExaGrid System is reporting 4:1 deduplication ratios for your Veeam backups, then:

Note – Only enter the antecedent portion of the ExaGrid deduplication ratio i.e. 4 not 4:1. The -egridDedup argument is optional; if omitted, the default value of 4 is used.

.\VeeamDedupReport.ps1 -egridDedup 4

4 ExaGrid Systems

■ Interpret the Results:

The PowerShell Script report is organized by Veeam repository and includes:

Job name, Combined Veeam and ExaGrid deduplication ratio (antecedent only), Veeam only deduplication ratio (antecedent only), number of backups, compression setting, whether deduplication enabled.

The Combined ratio is calculated using the ExaGrid deduplication ratio multiplied by the Veeam deduplication ratio.

The Veeam deduplication ratio is calculated by dividing the Total Backup Size by the Total Data Size.

Imported and deleted jobs are not included in this report.

Jobs that were deleted without deleting their restore points are still displayed but without compression and deduplication results.

ExaGrid’s Landing Space and VeeamExaGrid’s unique landing space architecture lends itself to Veeam’s VMware and HyperV data protection features. The ExaGrid landing space is a high-speed cache that retains the most recent backups in complete form.

The following Veeam features take full advantage of ExaGrid’s landing space.

Instant VM Recovery from an ExaGrid System In the event of a primary storage outage or to prove your backups are recoverable, Veeam can instantly recover a virtual machine and run it directly from an ExaGrid Server’s landing space. You then have the option to migrate the running VM to your production storage

Backup CopyThe combination of Veeam’s Backup Copy and WAN Accelerator with ExaGrid landing space architecture allows you to take full advantage of Veeam’s vPower features at both local and remote ExaGrid Sites.


Note – Do not confuse Veeam’s Backup Copy feature with Veeam’s VM replication feature or ExaGrid’s replication feature.

Copying a backup from a local ExaGrid Server’s landing space to a remote ExaGrid Server’s landing space provides:

■ A Veeam catalog that is “aware” of what is on the local and remote ExaGrid Sites■ Instant recovery operations from the landing space on either the local or remote

ExaGrid Site■ Different retention definitions for the backups stored on the local and remote

ExaGrid Sites

In addition, you may use Backup Copy to create daily, weekly, monthly, quarterly and yearly copies of your backups to your local or remote ExaGrid Sites.

For details on how to use Backup Copy with an ExaGrid System, see “Backup Copy” on page 26

Tape CopyWith the introduction of Veeam 7 you may now create Veeam backups that first write to an ExaGrid System, then automatically copy the backup from the ExaGrid landing space off to tape.

This feature is especially useful to those ExaGrid customers who:

■ Due to compliance and regulatory requirements, must maintain a removable copy of backed up data.

■ Only have one ExaGrid Site and want to maintain a disaster recovery copy of their backups.

For details on how to use Veeam’s Tape Copy with an ExaGrid System, see “Tape Job” on page 30.

Instant File-Level Recovery Quickly recover an entire VM or an individual file from an image-level backup. Veeam instant file-level recovery enables you to quickly restore individual files from your backups and replicas.

6 ExaGrid Systems

Using Veeam With an ExaGrid System

This section provides basic examples of how to use Veeam to backup to an ExaGrid Share.

Experienced Veeam users will be able to use the information provided in this guide and build more complex backup schemes.

The ExaGrid System supplements Veeam’s backup capabilities, providing improved data protection management, fast and reliable online data restores, enhanced security, and rapid data recovery from system or site disasters.


The ExaGrid System architecture is described in detail in the ExaGrid Administrator’s Guide and ExaGrid online help. The following architectural information may be of particular interest to Veeam users:

Data flows into an ExaGrid Share:

■ Backup application writes to an ExaGrid share.■ When the backup is complete, the ExaGrid deduplication engine will deduplicate

the backed up data.

Note – As more and more backups land, retained and deduplicated, deduplication ratios will improve.

■ A full copy of the most recent backup is maintained in the Landing Space.■ The deduplicated versions are kept in the Retention Space.■ In multi-site ExaGrid Systems, you can specify whether or not to maintain a copy

of a share on a second ExaGrid Site.

When a backup application requests a restore:

■ Since most restores are done from the most recent backup, the ExaGrid system keeps the most recent backup in its entirety. This ensures extremely fast restores.

■ Restores from an older backup are done by re-assembling the backup from backup versions.

Hub or Spoke Site

ExaGrid System

Hub or Spoke Site

Landing Space

Retention Space Retention Space

Landing Space

8 ExaGrid Systems

ExaGrid Veeam Shares

Before you can use Veeam to backup to an ExaGrid System, you must first create an ExaGrid Share. You will then use Veeam to write to the ExaGrid Share.

ExaGrid Share ConsiderationsHow many shares to create, which ExaGrid Server(s) will host which shares and what data will be backed up to a share must be part of your overall backup strategy. As part of your strategy, consider:

■ For systems with multiple ExaGrid Servers, creating shares on ExaGrid Servers in such a way that the backup load is evenly distributed across ExaGrid Servers.

■ Creating no more than 20 shares per ExaGrid Server but no more than 80 shares per ExaGrid Site.

■ Using unique share names across your ExaGrid System. You must use unique share names on each ExaGrid Server. In addition, ExaGrid recommends using unique share names across your ExaGrid System. Doing so will:

■ Make ExaGrid reports easier to interpret

■ Avoid share name conflicts in disaster recovery scenarios

■ Avoid share name conflicts if you decide to migrate a share to another ExaGrid Server

■ Creating multiple shares. Doing so allows you to:

■ More easily manage and identify data contained in a share.■ Group data that needs to be copied and protected to a second site. This will

ensure that only the data that needs to reside on the second site is copied over your network, thereby keeping network traffic to a minimum.

■ More efficiently migrate shares to a new ExaGrid Server. The more data a share contains, the longer it will take to migrate. When creating shares and their associated backups, consider future growth of your system and which data you may want to move (migrate) to a ExaGrid Server in an expanded system.


■ How many NICs are available on the ExaGrid Server being written to. Systems with multiple NICs allow you to write backup data from multiple sources to multiple shares.

■ Grouping Veeam backup jobs with similar VM guest machines (platform, software, etc.) to common shares. Doing so will enhance deduplication ratios.

How to Create an ExaGrid Veeam ShareThis section provides a very high-level description of how to create an ExaGrid Share. Detailed instructions on how to create an ExaGrid Share can be found in the ExaGrid Administrator’s Guide and the ExaGrid online help.

To create an ExaGrid Share:

1. In the ExaGrid Manager’s navigation tree, click the ExaGrid Server’s name on which you want to create the share.

2. In the ExaGrid main menu, click Manage.

3. From the drop down menu, click Shares.

4. In the Task area click New. The Create New Share page is displayed.

5. From the drop down list select Veeam.

6. In the space provided, enter a name for the share. You must use unique share names on each ExaGrid Server. In addition, ExaGrid recommends using unique share names across your ExaGrid System. Doing so will:

■ Make ExaGrid reports easier to interpret

■ Avoid share name conflicts in disaster recovery scenarios

■ Avoid share name conflicts if you decide to migrate a share to another ExaGrid Server.

7. For multi-site systems, select whether or not you want to replicate (copy) the share to a second site. Putting a copy onto another site provides an additional layer of protection for your data.

For example, you can create a share dedicated to full backups and keep a copy of those backups on another site. At the same time you can create a share dedicated to incremental backups and not copy the share to the second site.

10 ExaGrid Systems

8. If the share is to be copied to another site, from the drop down menu, select the site.

9. Enter the IP address and subnet mask for the device(s) that will write to the share.

Note – Some devices may use more than one IP address. You must include all IPs/names of all devises (physical or virtual) that will write to the share.

10. Click Done.


Recommended Veeam Settings

The following is a list of the settings required to use Veeam to backup to an ExaGrid System.

■ Update registry key

Before a Windows-based backup application server writes to an ExaGrid Share, update its time out registry key. ExaGrid provides a registry key script that will update the time out key. A copy of this key can be obtained via the ExaGrid user interface:

1.From the ExaGrid main menu, click Help.

2. From the drop down menu, click the Online Library. The online library is displayed.

3. Open the ExaGrid Documentation section.

4. Right click on the ExaGrid Registry Key Script link and select the menu option to save the script as a file.

5. In the dialog box, choose a location and filename. Be sure to use a ".reg" extension.

6. Run the script on your backup application server and the time out key will be updated.

■ Jobs■ Distribute the number of VMs per job as needed. The more jobs used, the

higher the concurrency rate.■ Most customer will only require a few jobs, however there is a maximum of

twenty per ExaGrid Server. ■ Organizing backup jobs so VMs of the same type (operating system, database,

etc.) are backed up to the same ExaGrid Share will maximize deduplication.

12 ExaGrid Systems

■ Repositories■ Create a separate repository for each Veeam job. ■ Enable and limit maximum concurrent tasks to one (1). Veeam’s default is four

(4).■ When creating a repository, keep in mind that your ExaGrid Server has more

than one network interface. When specifying a path for a repositories, spread the load across several network interfaces; doing so will maximize performance.

■ To maximize deduplication, point multiple repositories to a single ExaGrid Share. The ExaGrid System will deduplicate the entire contents of the share.

■ Scheduling Veeam backups

Customers backing up to ExaGrid Systems running versions of ExaGrid software prior to ExaGrid 4.6, when scheduling Veeam backups, ensure, under Automatic retry, that the Wait before each retry attempt option is set no more than fifteen (15) minutes.

■ Storage dialog box’s Advanced settings

Backup tab:

■ Ensure Reversed Incrementals is unchecked■ Ensure Transform previous backups... is unchecked■ Set other options as needed

Storage tab:

■ Check Enable inline data deduplication.■ For Veeam version 6.5 and later, set Compression level to Dedupe-friendly.■ For Veeam versions prior to 6.5, set Compression level to None.■ Set Optimize for to LAN Target.■ Set other options as needed

Notifications tab, set as needed.

vSphere tab, set as needed.

Advanced tab:

■ Ensure that Enable automatic backup integrity checks is checked.■ Set other options as needed

Storage integration tab, set as needed.

■ Synthetic backups

Synthetic backups are written to the ExaGrid Server that hosts the Veeam Share. To minimize the impact on system performance, ExaGrid recommends running synthetic backups according to Veeam’s recommended recipe of: After the initial full backup, run daily incrementals and weekly synthetics.


■ Parallel Processing - Global setting for all repositories

This option must be enabled for all repositories writing to an ExaGrid Share. It works in tandem with the Limit maximum concurrent tasks set to one (1) option to maximize performance.

■ Instant Recovery, Sure Backup and Application Item Recover

These Veeam features may only be used from an ExaGrid Source Share. Do not use them with an ExaGrid InstantDR Share at a remote site.

Note – Though you may not do an Instant Recovery from an InstantDR Share you may use Veeam to do a full VM restore from an InstantDR Share.

■ Guest File Level Recovery

May be used from either an ExaGrid Source Share or an ExaGrid InstantDR Share.

■ Import

Veeam’s Import function allows you to access Veeam backups on an InstantDR Share. Once imported, you can browse to and restore VM and individual files from an ExaGrid InstantDR Share.

Note – You may not use Veeam’s InstantRecovery feature on a backup imported from an InstantDR Share.

14 ExaGrid Systems

Using Server Message Block (SMB) Signing

SMB Signing is a feature that allows communications to be digitally signed at the packet level. Digitally signing the packets enables the recipient of the packets to confirm their point of origination and their authenticity. This security mechanism in the SMB protocol helps avoid issues like tampering of packets and “man in the middle” attacks. SMB signing does not encrypt data.

In addition, SMB signing augments the ExaGrid Share whitelist to control who and what has access to the backup data on ExaGrid Shares.

To use SMB signing with your ExaGrid System you must:

■ Enable SMB signing on your Microsoft® Windows® backup servers through either:

■ Enabling the Local Security Policy for the Microsoft network client: Digitally signed communications (always).

■ Setting up a security policy that includes the enabled Microsoft network client: Digitally signed communications (always) on a Windows domain through the use of Group Policy Objects (GPO), and applying it to the backup server.

To ensure these changes are fully in place, restart your backup server.

Caution – Backups must not be running while you are enabling SMB signing.

Caution – Once SMB signing is enabled, you must specify credentials on your backup application and on the ExaGrid System. Not doing so will cause your backups to fail.

■ Determine which local windows account (NOT the local system account) or domain account credentials you will specify in your backup application and on the ExaGrid System.


■ Enable and define security credentials on your ExaGrid System:

1. In the navigation tree, click ExaGrid

2. From the main menu, click Manage

3. From the drop down menu select Security Credentials and the Security Credentials Configuration page is displayed.

4. Click the online help link in the upper right-hand corner of the Security Credentials Configuration page for instructions on how to configure credentials.

The credentials you specify on the ExaGrid System must match an existing local or domain user account. Domain accounts must be entered without the domain information.

5. Define security credentials for Veeam’s Shared folder (CIFS) Repositories that write to your ExaGrid System:

Credentials must match a set of credentials defined on the ExaGrid System.

16 ExaGrid Systems

Veeam Step-by-Step

This section provides step-by-step instructions on how to configure Veeam with ExaGrid’s “Recommended Veeam Settings” on page 11.

Creating a Veeam RepositoryA Repository defines where a backup will be written and is created separately from the actual backup job. This allows a single backup destination definition to be used by multiple backup jobs.

To create a Repository:


1. In the Veeam left-hand backup navigation, click Add Repository and the New Backup Repository wizard will begin:

2. In the Spaces provided, enter a name for and a description of the repository.

3. Click Next and you will be prompted to select the type of repository:

4. Select Shared folder (CIFS).

5. Click Next and you will be prompted for the share information:

18 ExaGrid Systems

6. In the space provided, enter the UNC path to the ExaGrid Veeam Share.

7. If you have enabled SMB signing on your ExaGrid System check This share requires access credentials.

a. Click Add and the Credentials dialog box is displayed:

b. In the spaces provided, enter credentials that match a set of credentials defined on your ExaGrid System.

c. Click OK and the Credentials dialog box closes and the Share dialog box is redisplayed.

8. Under Proxying server select Automatic selection.

9. Click Next and you will be prompted for repository information:

10. Click Populate and Veeam will determine the capacity of the repository.

11. Set Limit maximum concurrent jobs count to: 1 (one).

12. Click Advanced and the Deduplication Storage Compatibility dialog box is displayed:

13. Uncheck Align backup file data blocks. ExaGrid is a byte-level deduplication appliance and this option will not improve deduplication


14. For the Decompress backup data blocks before storing option, see “Recommended Veeam Settings” on page 11

15. Click OK and the Repository information dialog box is re-displayed:

16. Click Next and you will be prompted for vPower NFS information:

17. Make vPower settings as needed.

18. Click Next and you will be prompted to review your settings:

19. Click Previous to go back and make changes as needed

20 ExaGrid Systems

20. Click Next and the Apply window will display repository settings:

21. When the settings are complete, the Finish button is activated.

22. Click Finish and the repository is ready to be used by backup jobs.


Creating a Veeam Backup JobTo create a Veeam backup job with the recommended settings:

1. In the Veeam main menu, click Backup job, and the backup wizard will begin:

2. In the Name and Description dialog box, enter a name and description for the backup job.

22 ExaGrid Systems

3. Click Next and you will be prompted to select VMs to backup:

4. Click Add and you will be prompted to add objects to be backed up:

5. Select the VMs to backup.

6. Click Add and your selected VMs will be displayed in the Virtual Machines dialog box:


7. When you have selected all VMs to be backed up, click Next and you will be prompted to select a repository:

8. Next to the Backup proxy entry, click Choose and choose a backup proxy as needed.

9. From the drop down menu, select the ExaGrid specific repository created for this job. To maximize performance, each Veeam job must use a separate repository.

10. Set the retention policy as needed.

11. If, when the job completes, you want a copy of the backup written to tape directly from the ExaGrid landing space, check Configure secondary destination for this job.

12. Click Advanced and you will be prompted to make advanced backup settings:

13. In the Backup tab:■ Ensure Reversed Incrementals is unchecked■ Ensure Transform previous backups... is unchecked■ Set other options as needed.

14. In the Storage tab:■ Check Enable inline data deduplication.

24 ExaGrid Systems

■ For Veeam version 6.5 and later, set Compression level to Dedupe-friendly.■ For Veeam versions prior to 6.5, set Compression level to None.■ Set Optimize for to LAN Target.■ Set other options as needed.

15. In the Notifications tab, set as needed.

16. vSphere tab, set as needed.

17. In the Advanced tab:■ Ensure that Enable automatic backup integrity checks is checked.■ Set other options as needed.

18. In the Storage integration tab, set as needed.

19. Click OK and the Advanced settings will be applied and the Advanced dialog box will close.

20. Click Next and you will be prompted for Guest processing:

21. Make selections as needed.


22. Click Next and you will be prompted to schedule the backup:

23. Set the schedule as needed.

24. Under Automatic retry, do not set Wait before each retry attempt to greater than fifteen (15) minutes.

25. Click Next and you will be prompted to review your settings:

26. Click Finish and the job will run according to your settings.

26 ExaGrid Systems

Backup Copy

This section provides a high-level description of using Veeam’s Backup Copy feature with an ExaGrid System. Consult Veeam’s documentation for detailed instructions and best practices for using the Backup Copy feature.

You can use Veeam’s Backup Copy feature to

■ Create weekly, monthly, quarterly and yearly copies of your backups to your local or remote ExaGrid Sites.

■ Copy backups from the landing space of an ExaGrid Server in one ExaGrid Site to the landing space of another ExaGrid Server in a remote ExaGrid Site.

Note – Do not confuse Veeam’s Backup Copy feature with Veeam’s VM replication feature or ExaGrid’s replication feature.

Making Local CopiesVeeam’s Backup Copy feature may be used to make a copy of a backup to the same site from which the source backup originates.

This is particularly useful if you need local copies of archived restore points.

When making local copies for archival purposes, you will get the best possible deduplication if you copy the backup into the same ExaGrid Share that hosts the source backup. This ensures that both the source and copy are deduplicated against each other.

To copy a source share’s backups back into itself you will need:

■ An ExaGrid Share on the local ExaGrid Site. When creating the share, enable ExaGrid replication as needed.


■ One repository that points to the share you created on the local ExaGrid Site. This repository will be used by both the backup job and the Backup Copy job.

■ Two jobs:

1. A source backup job that uses the repository that points to the ExaGrid Share on the local ExaGrid Site. For details, see “Creating a Veeam Backup Job” on page 21.

Note – You may have to first configure the backup job without defining a secondary target (Backup Copy job).

2. A Backup Copy job that:

■ Selects the source backup from either Infrastructure, Backup or Jobs

■ Uses the same repository as the source backup job.

In addition to the restore points created by a backup job, a Copy Backup job can create a separate set of restore points. The separate restore points are typically used for archiving versions of backups.

28 ExaGrid Systems

Making Remote CopiesWith Backup Copy, backups may be copied from the landing space of an ExaGrid Server in a local ExaGrid Site and copied to the landing space of another ExaGrid Server in a remote ExaGrid Site.

Copying a backup from a local ExaGrid Server’s landing space to a remote ExaGrid Server’s landing space provides:

■ A Veeam catalog that is “aware” of what is on the local and remote ExaGrid Sites. This Ensures recovery from disaster scenarios are as fast and efficient as possible.

■ Allows you to perform vPower operations, including Instant VM Recovery operations on both the local source backup and the copy at the remote ExaGrid Site.

■ Different retention definitions for the backups stored on the local and remote ExaGrid Sites

To use Veeam’s Backup Copy feature to copy to a remote ExaGrid Site you will need:

■ Two ExaGrid Shares:

1. One on the local ExaGrid Site. This share will be used as the backup job’s repository. When creating the share, enabling ExaGrid replication is not necessary because its contents will be copied by Veeam another ExaGrid Site.

2. One on the remote ExaGrid Site. This share will be used by the Backup Copy job’s repository. When creating the share, enabling ExaGrid replication is not necessary because its contents will be data copied from another ExaGrid Site.

■ Two repositories:

1. One repository will point to the share you created on the local ExaGrid Site. This repository will be used by the backup job.

2. One repository will point to the share you created on the remote ExaGrid Site. This repository will be used by the Backup Copy job.

■ Two jobs:

1. A backup job that uses the repository that points to the ExaGrid Share on the local ExaGrid Site. For details, see “Creating a Veeam Backup Job” on page 21.

Note – You may have to first configure the backup job without defining a secondary target (Backup Copy job).

2. A Backup Copy job that:


■ Selects the source backup from either Infrastructure, Backup or Jobs

■ Uses a repository separate from the source’s repository.

Note – The Copy Backup retention period may be set differently than that of the backup job.

30 ExaGrid Systems

Tape Job

ExaGrid’s unique landing space architecture allows you to take advantage of Veeam’s Tape Job feature. With Tape Jobs you can you can write backups to an ExaGrid System, then write those backups directly from the ExaGrid landing space off to tape.

This section provides a high-level description of using Veeam’s Tape Job feature with an ExaGrid System. Consult Veeam’s documentation for detailed instructions and best practices for using the Tape Job feature.

To use Veeam’s Tape Job feature with an existing Veeam backup job:

1. Via Veeam’s user interface, create a tape job that uses the existing backup job that points to an ExaGrid Share.

2. Configure the tape job to run as soon as the backup job completes.

3. Follow Veeam’s the best practices for creating tape jobs.


Recovering From the ExaGrid Source Share

Recovers are done from the Veeam user interface. Consult the Veeam documentation for details.

32 ExaGrid Systems

Disaster Recovery

In the event of a disaster, you may recover Veeam backups that your ExaGrid System has replicated to an ExaGrid InstantDR Share at a remote location.

To recover a Veeam backup from an ExaGrid InstantDR Share:

1. Create a Veeam repository that points to the ExaGrid InstantDR Share.

2. Right click on the newly created repository and click Rescan repository:

3. When the Rescan completes, in Veeam’s left-hand navigation frame click Backup & Replication.

4. In the Backup & Replication tree, under Backups, click Imported.


5. Right click on the imported (rescanned) backup and perform the restore operation needed:

Note – You may not use Veeam’s Instant recovery on a backup imported from an InstantDR Share.

In case of a disaster, if a Veeam Share is replicated to another ExaGrid Site, the Veeam share can be recovered to the ExaGrid Site that hosts the replicated share. The recovered ExaGrid Share can then become the source share. In this case, because the recovered share is now the source share, you may take advantage of:

■ InstantRecovery■ SureBackup■ U-AIR

34 ExaGrid Systems

Using Veeam Backup and Replication™ Software with an ExaGrid System

Part Number: 210-0317-04

© 2003-2014 ExaGrid Systems

Printed in the U.S.A. All rights reserved.

No part of this document may be reproducedor transmitted in any form or by any means without

prior written permission of ExaGrid Systems

.All rights reserved. Printed in U.S.A

Documents

Using Veeam Backup and Replication™ Software with an ExaGrid Systemgo.veeam.com/rs/veeam/images/Best_Practices_and... · · 2018-04-04Software with an ExaGrid System PN: 210-0317-04