0% found this document useful (0 votes)

48 views184 pages

Veeam Backup 9 5 U3 Storage Integration User Guide

Uploaded by

Aitor Longarte

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

48 views184 pages

Veeam Backup 9 5 U3 Storage Integration User Guide

Uploaded by

Aitor Longarte

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 184

Veeam Backup &

Replication
Version 9.5
Integration with Storage Systems
September, 2018
© 2018 Veeam Software.

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language in any form by any means, without written permission from Veeam Software
(Veeam). The information contained in this document represents the current view of Veeam on the issue
discussed as of the date of publication and is subject to change without notice. Veeam shall not be liable for
technical or editorial errors or omissions contained herein. Veeam makes no warranties, express or implied, in
this document. Veeam may have patents, patent applications, trademark, copyright, or other intellectual property
rights covering the subject matter of this document. All other trademarks mentioned herein are the property of
their respective owners. Except as expressly provided in any written license agreement from Veeam, the
furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other
intellectual property.

NOTE:
Please read the End User Software License Agreement before using the accompanying software program(s).
Using any part of the software indicates that you accept the terms of the End User Software License
Agreement.

2 | Veeam Backup & Replication | Integration with Storage Systems |

Contents
CONTENTS ...........................................................................................................................................................3
CONTACTING VEEAM SOFTWARE ........................................................................................................................4
INTEGRATION WITH STORAGE SYSTEMS ............................................................................................................5
UNIVERSAL S TORAGE INTEGRATION API .................................................................................................................... 7
Installing Storage System Plug-Ins ......................................................................................................... 8
BACKUP INFRASTRUCTURE FOR STORAGE SNAPSHOTS ................................................................................................... 10
Adding VMware vSphere Server ........................................................................................................... 11
Configuring Backup Proxy ................................................................................................................... 12
Enabling HPE 3PAR Web Services API Server ......................................................................................... 14
Adding Storage Systems ..................................................................................................................... 15
Re-Scanning Storage Systems ............................................................................................................. 61
Removing Storage Systems ................................................................................................................. 64
BACKUP FROM STORAGE SNAPSHOTS ...................................................................................................................... 65
VM Data Processing ........................................................................................................................... 66
Backup from Primary Storage Arrays .................................................................................................... 68
Backup from Secondary Storage Arrays ................................................................................................ 72
Limitation on Number of VMs per Snapshot ........................................................................................... 80
BACKUP FROM CISCO HYPERF LEX SNAPSHOTS ........................................................................................................... 81
Integration Modes ............................................................................................................................. 82
How Backup from Cisco HyperFlex Snapshots Works .............................................................................. 84
Configuring Backup Proxies ................................................................................................................. 85
Configuring Backup from Cisco HyperFlex Snapshots .............................................................................. 87
Configuring Direct NFS Access on Cisco HyperFlex (Earlier Than 2.0) ........................................................ 89
SNAPSHOT JOBS ............................................................................................................................................. 90
Snapshot-Only Jobs ........................................................................................................................... 91
Storage Snapshots in Secondary Destination Jobs .................................................................................. 96
VEEAM EXPLORER FOR STORAGE SNAPSHOTS ............................................................................................................. 99
Traditional Restore vs. Restore from Storage Snapshots ........................................................................ 100
How Restore from Storage Snapshots Works ....................................................................................... 101
Creating and Deleting Snapshots ....................................................................................................... 102
Performing Instant VM Recovery........................................................................................................ 104
Restoring VM Guest OS Files (Microsoft Windows) ................................................................................ 114
Restoring VM Guest OS Files (Linux, Unix and Other)............................................................................ 123
Restoring Application Items from Microsoft Active Directory................................................................... 133
Restoring Application Items from Microsoft Exchange ........................................................................... 142
Restoring Application Items from Microsoft SharePoint.......................................................................... 150
Restoring Databases from Microsoft SQL Server ................................................................................... 151
Restoring Databases from Oracle ....................................................................................................... 159
ON-DEMAND SANDBOX FOR STORAGE SNAPSHOTS .................................................................................................... 167
REQUIREMENTS AND LIMITATIONS ....................................................................................................................... 169
General Limitations .......................................................................................................................... 170
Limitations for Cisco HyperFlex .......................................................................................................... 172
Limitations for Dell EMC VNX/VNXe .................................................................................................... 173
Requirements and Limitations for NetApp............................................................................................ 174

3 | Veeam Backup & Replication | Integration with Storage Systems |

Contacting Veeam Software
At Veeam Software we value the feedback from our customers. It is important not only to help you quickly with
your technical issues, but it is our mission to listen to your input, and build products that incorporate your
suggestions.

Customer Support
Should you have a technical concern, suggestion or question, please visit our Customer Center Portal at
www.veeam.com/support.html to open a case, search our knowledge base, reference documentation, manage
your license or obtain the latest product release.

Company Contacts
For the most up to date information about company contacts and offices location, please visit
www.veeam.com/contacts.html.

Online Support
If you have any questions about Veeam products, you can use the following resources:

 Full documentation set: www.veeam.com/documentation-guides-datasheets.html

 Community forum at forums.veeam.com

4 | Veeam Backup & Replication | Integration with Storage Systems |

Integration with Storage Systems
To build the data protection and disaster recovery strategy, you can use capabilities of native snapshots created
on production storage systems that host VM disks.

 Backup from Storage Snapshots. You can use storage snapshots to create backups and replicas of
VMware vSphere VMs hosted on storage systems. Backup from Storage Snapshots speeds up backup and
replication operations and reduces the impact of VMware vSphere snapshot removal on the production
environment.

 Veeam Explorer for Storage Snapshots. You can restore VM data directly from storage snapshots. Veeam
Explorer for Storage Snapshots automates the process of VM data recovery and reduces recovery time in
10 times or more.

 Snapshot jobs. You can configure backup jobs to periodically create storage snapshots on primary and/or
secondary storage arrays.

 On-Demand Sandbox for Storage Snapshots. You can start VMs whose disks are hosted on storage
systems in the On-Demand Sandbox. On-Demand Sandbox can be used for testing, training,
troubleshooting and so on.

To start working with storage systems, you must properly configure the backup infrastructure. For more
information, see Backup Infrastructure for Storage Snapshots. After that, you can use storage snapshots for data
protection and disaster recovery operations.

5 | Veeam Backup & Replication | Integration with Storage Systems |

Depending on the storage system type, you can perform the following operations:

NetApp
FAS/AFF,
IBM Universal
FlexArray
Dell EMC Spectrum Storage
Functionality/ HPE 3PAR HPE (V-Series) Cisco
VNX(e)/ Nimble Virtualize API
Storage type StoreServ StoreVirtual IBM HyperFlex
Unity Lenovo Integrated
N series
V-Series Systems
Lenovo
DM-Series

Backup from Storage Snapshots

Backup from ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
primary storage
arrays

Backup from ✕ ✓ ✕ ✓ ✓ ✕ ✓ ✕
secondary
storage arrays

Veeam Explorer from Storage Snapshots

Restore from ✓ ✓ ✓ ✓ ✓ ✕ ✓ ✓
primary storage
arrays

Restore from ✓ ✓ ✓ ✓ ✓ ✕ ✓ ✓
secondary
storage arrays

Snapshot Jobs

Snapshot-only ✕ ✓ ✕ ✓ ✓ ✕ ✓ ✓
job

Snapshot in ✕ ✓ ✕ ✓ ✓ ✕ ✓ ✓
secondary
destination job

Other Operations

Storage rescan ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
(infrastructu
re only)

Snapshot ✓ ✓ ✓ ✓ ✓ ✕ ✓ ✓
creation and
deletion
(manual)

6 | Veeam Backup & Replication | Integration with Storage Systems |

Universal Storage Integration API
Veeam Backup & Replication offers built-in integrations with storage systems to help decrease impact on the
production environment and significantly improve RPOs. Storage vendors, in turn, can leverage Veeam
Universal Storage API framework to integrate their storage solutions with Veeam Backup & Replication. With
this kind of integration Veeam Backup & Replication uses snapshots of Universal Storage API integrated systems
to perform backup and restore operations.

The following storage systems are supported:

 INFINIDAT InfiniBox

 Pure Storage FlashArray

 Huawei OceanStor

To start working with Universal Storage API integrated systems, you must perform the following steps:

1. Download the corresponding storage system plug-in from www.veeam.com/backup-replication-

download.html:

o INFINIDAT Plug-In for Veeam Backup & Replication

o Pure Storage Plug-In for Veeam Backup & Replication

o Huawei Plug-In for Veeam Backup & Replication

2. Run the setup wizard to install the plug-in.

3. Configure the backup infrastructure for storage snapshots.

After that, you can use Universal Storage API integrated storage snapshots for data protection and disaster
recovery operations.

7 | Veeam Backup & Replication | Integration with Storage Systems |

Installing Storage System Plug-Ins
Before you start working with Universal Storage API integrated systems, make sure you have installed the
Universal Storage API integrated system plug-in on the Veeam backup server.

NOTE:

If you connect to the backup server remotely with the Veeam Backup & Replication console, you must install
the Universal Storage API integrated system plug-in both on the backup server and the machine where you
run the console.

To install the plug-in, perform the following steps:

1. Run the plug-in installation file.

The latest version of the Universal Storage API integrated system plug-in is available at
https://www.veeam.com/backup-replication-vcp-download.html.

2. On the welcome screen of the setup wizard click the Next button to proceed to the configuration of the
installation.

8 | Veeam Backup & Replication | Integration with Storage Systems |

3. At the Terms of Usage step of the wizard, select I accept these terms.

4. At the Ready to Install the Program step of the wizard, click Install to begin installation.

5. When the installation process completes, click Finish to close the wizard.

After you install the plug-in, you must configure the backup infrastructure to be able to use storage system
snapshots for data protection. For more information, see Backup Infrastructure for Storage Snapshots.

9 | Veeam Backup & Replication | Integration with Storage Systems |

Backup Infrastructure for Storage
Snapshots
Before you start working with storage systems in Veeam Backup & Replication, you must properly configure the
backup infrastructure. As part of this process, you must perform the following actions:

1. Add VMware vSphere server. You must add to the backup infrastructure a VMware vCenter Server or
ESX(i) hosts with VMs whose disks are located on the storage system.

2. Configure a backup proxy. The backup proxy is required for storage systems rescan and Backup from
Storage Snapshots.

3. [For HPE 3PAR StoreServ] Enable HPE 3PAR Web Services API server. Veeam Backup & Replication uses
the HPE 3PAR Web Services API server to work with the HPE StoreServ storage system.

4. Add storage systems. You must add to the backup infrastructure the storage system(s) on which VM
disks are hosted. If you plan to work with secondary storage arrays, you must add them to the backup
infrastructure as well.

5. [For IBM Spectrum Virtualize with HyperSwap function] If you plan to select secondary storage volumes
as a data source for backup, use registry keys. For more information, contact Veeam Support Team.

NOTE:
You can work with storage systems in the Storage Infrastructure view of Veeam Backup & Replication.
Right after the installation, the Storage Infrastructure view is not displayed in the
Veeam Backup & Replication console. To display it, you must add at least one VMware vCenter Server or
ESX(i) host to the backup infrastructure.

10 | Veeam Backup & Replication | Integration with Storage Systems |

Adding VMware vSphere Server
Before you add a storage system and start using storage snapshots for backup and restore operations, you must
add a VMware vSphere server to the backup infrastructure. The VMware vSphere server is the VMware vCenter
Server or ESX(i) host with VMs whose disks are hosted on the storage system.

It is strongly recommended that you add a VMware vCenter Server or ESX(i) hosts to the backup infrastructure
before you add the storage system. When you add the storage system, Veeam Backup & Replication performs
the storage system rescan. As a part of this process, Veeam Backup & Replication maps storage volumes to
VMware vSphere datastores. This helps Veeam Backup & Replication understand what VMs host their disks on
storage volumes.

If you add the storage system to the backup infrastructure and do not add the VMware vCenter Server or ESX(i)
hosts, you will be able to perform only restore from storage snapshots. You will not be able to perform Backup
from Storage Snapshots.

TIP:
If you first add the storage system to the backup infrastructure and then add the VMware vCenter Server or
ESX(i) host, perform storage rescan to map storage volumes to VMware vSphere datastores.

11 | Veeam Backup & Replication | Integration with Storage Systems |

Configuring Backup Proxy
For some operations with storage snapshots, Veeam Backup & Replication requires a backup proxy. The backup
proxy is used for two purposes:

 Rescan of VMFS on storage volumes

 Backup from Storage Snapshot

When Veeam Backup & Replication performs rescan and backup operations, it needs to read the content on
storage volumes and snapshots. To do this, Veeam Backup & Replication uses a backup proxy as a helper.
Storage volumes and snapshots are mounted as new volumes to the backup proxy. As a result,
Veeam Backup & Replication can access mounted volumes and snapshots over the backup proxy and read VM
data from them.

To enable storage rescan and Backup from Storage Snapshots, you must configure a backup proxy in the backup
infrastructure. The backup proxy must meet the requirements listed below.

General Requirements
 The role of a backup proxy must be assigned to a Microsoft Windows machine. This can be a dedicated
machine or backup server performing the role of the default backup proxy.

 For Backup from Storage Snapshots, the transport mode for the backup proxy must be set to Automatic
selection or Direct storage access.

 [For HPE 3PAR] If storage LUNs reside in a virtual domain, the backup proxy to which LUNs are exported
must reside in the same virtual domain. If LUNs reside outside a virtual domain, the backup proxy must
also reside outside any available virtual domain.

iSCSI Protocol
 The backup proxy must have a Microsoft iSCSI Software initiator enabled.

 iSCSI traffic between the backup proxy and storage system must be allowed.

NOTE:
For storage rescan, Veeam Backup & Replication uses its own initiator. For this reason, a Microsoft iSCSI
Software initiator may not be enabled when you perform storage rescan. For Backup from Storage Snapshots,
however, a Microsoft iSCSI Software initiator must be enabled.

Fibre Channel Protocol

 The backup proxy must have a Fibre channel adapter installed and must have access to the storage
system over Fibre Channel fabric.

 To let Veeam Backup & Replication present snapshots of LUNs to the backup proxy, you must register
the backup proxy with a WWN ID on the storage system.

 Fibre Channel devices must be properly installed and shown in Device Manager on the backup proxy. The
WWN ID of the backup proxy must be properly zoned on the Fibre Channel switch.

12 | Veeam Backup & Replication | Integration with Storage Systems |

NFS Protocol
NFS traffic between the backup proxy and storage system must be allowed.

13 | Veeam Backup & Replication | Integration with Storage Systems |

Enabling HPE 3PAR Web Services API Server
This step must be performed if you plan to work with the HPE 3PAR StoreServ storage system.

Veeam Backup & Replication uses the HPE 3PAR Web Services API server to communicate with the HPE 3PAR
StoreServ storage system. When you add the HPE 3PAR StoreServ storage to the backup infrastructure,
Veeam Backup & Replication attempts to enable the server automatically. If Veeam Backup & Replication fails to
enable the server automatically, for example, Veeam Backup & Replication does not have enough privileges to do
this, you need to enable the server manually.

IMPORTANT!

The HPE 3PAR Web Services API is a part of the HPE 3PAR OS starting from version 3.1.2.
Veeam Backup & Replication does not support earlier versions of the HPE 3PAR OS.

To check if the HPE 3PAR Web Services API server is enabled and enable it if needed:

1. Log on to the Processor with administrator privileges:

#ssh <administrator account>@<SP IP Address>

2. View the current state of the Web Services API Server:

#showwsapi
-- -State- -HTTP_State-
HTTP_Port -HTTPS_State- HTTPS_Port -Version-
Enabled Active Enabled 8008
Enabled 8080 1.1

3. If the Web Services API Server is disabled, start it:

#startwsapi

4. If the HTTP or HTTPS state is disabled, enable one of them:

#setwsapi -http enable

#setwsapi -https enable

14 | Veeam Backup & Replication | Integration with Storage Systems |

Adding Storage Systems
To use storage snapshots for data protection and disaster recovery operations, you must add the storage system
to the backup infrastructure. If you plan to work with secondary storage arrays, you must add them to the
backup infrastructure as well.

When you add the storage system, Veeam Backup & Replication automatically rescans it. As part of the rescan
process, Veeam Backup & Replication performs the following operations:

1. Veeam Backup & Replication retrieves information about the storage system topology.

2. Veeam Backup & Replication retrieves information about VMware vSphere datastores from the VMware
vCenter Server and matches storage volumes to these datastores. Matching helps
Veeam Backup & Replication understand what VMs host their disks on storage volumes. It also helps
Veeam Backup & Replication get information about VMs on storage snapshots.
Veeam Backup & Replication assumes that disks of VMs located on storage volumes are also located on
storage snapshots.

3. Veeam Backup & Replication rescans storage snapshots. As a result of snapshot rescan,
Veeam Backup & Replication knows exactly what disks of what VMs are hosted on storage snapshots. If
for some reason Veeam Backup & Replication fails to rescan all storage snapshots, it rescans the last
storage snapshot in the hierarchy and propagates the retrieved information to other storage snapshots.

The topology of the storage system added to the backup infrastructure is displayed in the Storage
Infrastructure view in the Veeam Backup & Replication console. Storage snapshots are also displayed in the
inventory pane of the Home view, under the Storage snapshots node.

You can add the following storage systems to the backup infrastructure:

 Dell EMC VNX/VNXe

 IBM Spectrum Virtualize

 Universal Storage API Integrated Systems

 HPE StoreVirtual

 HPE 3PAR StoreServ

 NetApp

 Nimble

 Cisco HyperFlex

Adding Dell EMC VNX/VNXe

Before you add a storage system to the backup infrastructure, check prerequisites. Then use the New DELL
EMC Storage wizard to add the storage system.

Before You Begin

Before you add a storage system to the backup infrastructure, check the following prerequisites:

[For Dell EMC VNX Block] To take LUN snapshots, Veeam Backup & Replication uses the VNX snapshot
technology. Make sure that you have a license that covers this functionality. The SnapView snapshot technology
is not supported.

15 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch New Dell EMC Storage Wizard
To launch the New Dell EMC Storage wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click DELL EMC.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure
node and select Add Storage. In the displayed window, click DELL EMC.

 You can use this method if at least one Dell EMC storage system is added to the backup infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the DELL EMC node and
select Add storage. You can also select the DELL EMC node in the inventory pane, right-click
anywhere in the working area and select Add storage.

16 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select Storage Type
At the Storage Type step of the wizard, select the storage type.

 Select VNX (block) to add a Dell EMC VNX block storage system working over iSCSI or Fibre Channel.

 Select VNX (file) to add a Dell EMC VNX file storage system working over NFS.

 Select VNXe to add a Dell EMC VNXe storage system.

 Select Unity to add a Dell EMC Unity storage system.

17 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Specify Storage Name or Address
At the Name step of the wizard, specify the storage system name and description.

1. In the DNS name or IP address field, specify a DNS name or IP address of the storage system.

2. In the Description field, provide a description for future reference. The default description contains
information about the user who added the storage system, date and time when the storage system was
added.

Step 4. Specify Credentials

At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
storage system.

2. [For Dell EMC VNX block storage] Select the scope to which the user account belongs:

 Select Global if the user can administrate all VNX systems in the domain.

 Select Local if the user can administrate only a single VNX storage system in the domain.

 Select LDAP if the user can administrate all VNX systems that use the LDAP server for
authentication.

3. [For Dell EMC VNX file storage] When you add a storage system, Veeam Backup & Replication saves a
fingerprint of the SSH key of the management server to the configuration database. During every
subsequent connection to the server, Veeam Backup & Replication uses the saved fingerprint to verify
the server identity and avoid man-in-the-middle attacks.

18 | Veeam Backup & Replication | Integration with Storage Systems |

To let you identify the server, Veeam Backup & Replication displays the SSH key fingerprint.

 If you trust the server and want to connect to it, click Yes.

 If you do not trust the server, click No. Veeam Backup & Replication will display an error
message, and you will not be able to connect to the server.
If you update the SSH key on the server, you must acknowledge the new key in the server connection
settings. To do this, in the Storage Infrastructure view right-click the storage system, select Edit
storage, pass through the Edit Storage wizard and click Trust to acknowledge the new key.

Step 5. Specify Access Options

At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

2. If you plan to work with specific storage volumes, you can limit the storage rescan scope. In this case,
Veeam Backup & Replication will rescan only the volumes that you select. Limiting the rescan scope
reduces the amount of time required for the rescan operation.
To select volumes for rescan:

a. On the right of the Volumes to scan field, click Choose.

b. In the Choose Volumes window, select volumes that you want to rescan. To exclude volumes
from rescan, select All volumes except, click Add and select volumes from the list. To rescan
only specific volumes, select Only these volumes, click Add and select volumes from the list.
If you leave the Automatic detection option selected, Veeam Backup & Replication will
rescan all volumes in the storage hierarchy.
After you finish working with the wizard, you can change the rescan scope and start the rescan process

19 | Veeam Backup & Replication | Integration with Storage Systems |

manually at any time. For more information, see Re-Scanning Storage Systems.

3. Operations of storage rescan and Backup from Storage Snapshots are performed with the help of a
backup proxy. On the right of the Backup proxies to use field, click Choose and define backup
proxies that you want to use for these operations.

 Select Automatic selection to let Veeam Backup & Replication pick a backup proxy
automatically. Veeam Backup & Replication will check which backup proxies have access to the
storage system, and automatically assign an optimal backup proxy for rescan and Backup from
Storage Snapshots.

 Select Use the selected backup proxy servers only to explicitly select a backup proxy that
must be used for rescan and Backup from Storage Snapshots. It is recommended that you
select at least two backup proxies to ensure that rescan and Backup from Storage Snapshot are
performed if one of backup proxies fails or loses its connectivity to the storage system.

NOTE:
If you select backup proxies explicitly, you must make sure that you also select these proxies in settings of
backup and replication jobs for which you plan to use Backup from Storage Snapshots. If a backup proxy
selected for the job is not added to the list of backup proxies in the storage system connection settings and
the Failover to standard backup option is disabled in the job settings, the job will fail. For more
information, see Configuring Backup from Storage Snapshots.

20 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

Adding IBM Spectrum Virtualize Storage

To add an IBM Spectrum Virtualize storage system to the backup infrastructure, use the New IBM Spectrum
Virtualize Storage wizard.

Before You Begin

Before you add a storage system to the backup infrastructure, make sure that a license for the IBM Spectrum
Virtualize storage system supports IBM FlashCopy.

Step 1. Launch New IBM Spectrum Virtualize Storage Wizard

To launch the New IBM Spectrum Virtualize Storage wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click IBM Spectrum Virtualize.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure
node and select Add Storage. In the displayed window, click IBM Spectrum Virtualize.

 You can use this method if at least one IBM Spectrum Virtualize storage system is added to the backup
infrastructure.

21 | Veeam Backup & Replication | Integration with Storage Systems |

Open the Storage Infrastructure view. In the inventory pane, right-click the IBM Spectrum
Virtualize node under Storage Infrastructure and select Add storage. You can also select the IBM
Spectrum Virtualize node in the inventory pane, right-click anywhere in the working area and select
Add storage.

Step 2. Specify Storage Name or Address

At the Name step of the wizard, specify the storage system name and description.

1. In the DNS Name or IP address field, specify a DNS name or IP address of the storage system.

22 | Veeam Backup & Replication | Integration with Storage Systems |

23 | Veeam Backup & Replication | Integration with Storage Systems |
Step 3. Specify Credentials
At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
storage system.

NOTE:
User name and password values are case-sensitive.

2. The default port for communication with the storage system is 22. If necessary, you can change the port
number in storage system settings and specify the new port number in the Port field.

Step 4. Specify Access Options

At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

a. On the right of the Volumes to scan field, click Choose.

24 | Veeam Backup & Replication | Integration with Storage Systems |

IMPORTANT!

If you plan to use Backup from Storage Snapshots, you need to make sure that you include in the rescan
scope volumes on which VM disks reside.

25 | Veeam Backup & Replication | Integration with Storage Systems |

26 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

Adding Universal Storage API Integrated Systems

To add a Universal Storage API integrated system to the backup infrastructure, use the storage installation
wizard.

1. Launch the storage installation wizard

2. Specify the storage name or address

3. Specify credentials

4. Specify access options

5. Finish working with the wizard

Before You Begin

Before adding a storage system to the backup infrastructure, make sure that you have installed the storage
system plug-in. For more information, see Installing Storage System Plug-Ins.

27 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch Storage Installation Wizard
To launch the storage installation wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, select the storage system you plan to add.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure
node and select Add Storage. In the displayed window, select the storage system you plan to add.

 You can use this method if at least one storage system is added to the backup infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the storage system node
under Storage Infrastructure and select Add storage. You can also select the storage system node
in the inventory pane, right-click anywhere in the working area and select Add storage.

28 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Specify Storage Name or Address
At the Name step of the wizard, specify the storage system name and description.

1. In the DNS Name or IP address field, specify a DNS name or IP address of the storage system.

29 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Specify Credentials
At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
storage system.

NOTE:
User name and password values are case-sensitive.

2. The default port for communication with the storage system is 443. If necessary, you can change the
port number in storage system settings and specify the new port number in the Port field.

Step 4. Specify Access Options

At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

a. On the right of the Volumes to scan field, click Choose.

30 | Veeam Backup & Replication | Integration with Storage Systems |

IMPORTANT!

If you plan to use Backup from Storage Snapshots, you need to make sure that you include in the rescan
scope volumes on which VM disks reside.

31 | Veeam Backup & Replication | Integration with Storage Systems |

32 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

Adding HPE StoreVirtual Storage

To add an HPE StoreVirtual storage system to the backup infrastructure, use the New HPE StoreVirtual
Storage wizard.

33 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch New HPE StoreVirtual Storage Wizard
To launch the New HPE StoreVirtual Storage wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click Hewlett Packard Enterprise and select StoreVirtual.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure
node and select Add Storage. In the displayed window, click Hewlett Packard Enterprise and select
StoreVirtual.

 You can use this method if at least one HPE StoreVirtual storage system is added to the backup
infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the HPE StoreVirtual node
under Storage Infrastructure and select Add storage. You can also select the HPE StoreVirtual
node in the inventory pane, right-click anywhere in the working area and select Add storage.

34 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Specify Storage Name or Address
At the Name step of the wizard, specify the storage system name and description.

1. On the right of the Management server DNS name or IP address field, click Browse and select an
HPE storage management group.
You can also type a DNS name or IP address of the storage management server or storage cluster in the
Management server DNS name or IP address field.

2. In the Description field, provide a description for future reference. The default description contains
information about the user who added the management group, date and time when the HPE
management group was added.

Step 3. Specify Credentials

At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
management group.

1. From the Credentials list, select credentials to connect to the management group. If you have not set
up credentials beforehand, click the Manage accounts link or click Add on the right of the
Credentials field to add the credentials.

NOTE:
User name and password values are case-sensitive.

2. When you add a storage system, Veeam Backup & Replication saves a fingerprint of the SSH key of the
management server to the configuration database. During every subsequent connection to the server,
Veeam Backup & Replication uses the saved fingerprint to verify the server identity and avoid man-in-

35 | Veeam Backup & Replication | Integration with Storage Systems |

the-middle attacks.
To let you identify the server, Veeam Backup & Replication displays the SSH key fingerprint.

 If you trust the server and want to connect to it, click Yes.

 If you do not trust the server, click No. Veeam Backup & Replication will display an error
message, and you will not be able to connect to the server.
If you update the SSH key on the server, you must acknowledge the new key in the server connection
settings. To do this, in the Storage Infrastructure view right-click the storage system, select Edit
storage, pass through the Edit Server wizard and click Trust to acknowledge the new key.

Step 4. Specify Access Options

At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

a. On the right of the Volumes to scan field, click Choose.

36 | Veeam Backup & Replication | Integration with Storage Systems |

After you finish working with the wizard, you can change the rescan scope and start the rescan process
manually at any time. For more information, see Re-Scanning Storage Systems.

IMPORTANT!
If you plan to use Backup from Storage Snapshots, you need to make sure that you include in the rescan
scope volumes on which VM disks reside.

NOTE:

If you select backup proxies explicitly, you must make sure that you also select these proxies in settings of
backup and replication jobs for which you plan to use Backup from Storage Snapshots. If a backup proxy
selected for the job is not added to the list of backup proxies in the storage system connection settings and
the Failover to standard backup option is disabled in the job settings, the job will fail. For more
information, see Configuring Backup from Storage Snapshots.

37 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

Adding HPE 3PAR StoreServ Storage

Before you add an HPE 3PAR StoreServ storage system to the backup infrastructure, check prerequisites. Then
use the New HPE 3PAR StoreServ Storage wizard to add the storage system.

Before You Begin

Before you add a storage system to the backup infrastructure, check the following prerequisites:

1. The HPE 3PAR Web Services API server must be enabled. For more information, see Enabling HPE 3PAR
Web Services API Server.

2. A license for the HPE 3PAR StoreServ storage system must support HPE 3PAR Virtual Copy.

Step 1. Launch New HPE 3PAR StoreServ Storage Wizard

To launch the New HPE 3PAR StoreServ Storage wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click Hewlett Packard Enterprise and select 3PAR StoreServ.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure

38 | Veeam Backup & Replication | Integration with Storage Systems |

node and select Add Storage. In the displayed window, click Hewlett Packard Enterprise and select
3PAR StoreServ.

 You can use this method if at least one HPE 3PAR StoreServ storage system is added to the backup
infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the HPE 3PAR StoreServ
node under Storage Infrastructure and select Add storage. You can also select the HPE 3PAR
StoreServ node in the inventory pane, right-click anywhere in the working area and select Add
storage.

Step 2. Specify HPE 3PAR Web Services API Address

Veeam Backup & Replication uses the HPE 3PAR Web Services API to work with HPE 3PAR StoreServ storage
systems. The HPE 3PAR Web Services API delivers a programming interface for performing storage management
tasks.

At the Name step of the wizard, provide information about the HPE 3PAR Web Services API Server.

1. In the DNS name or IP address field, enter a full DNS name or IP address of the HPE 3PAR Web
Services API Server.

2. In the URL field, enter a URL of the HPE 3PAR Web Services API Server. By default,
Veeam Backup & Replication uses the following URL:
https://< websapiserver>:8080
where <websapiserver> is the name or IP address of the HPE 3PAR Web Services API Server.

3. In the Description field, provide a description for future reference. The default description contains
information about the user who added the server, date and time when the server was added.

39 | Veeam Backup & Replication | Integration with Storage Systems |

40 | Veeam Backup & Replication | Integration with Storage Systems |
Step 3. Specify Credentials
At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
HPE 3PAR Web Services API Server.

1. From the Credentials list, select credentials to connect to the HPE 3PAR Web Services API Server. If
you have not set up credentials beforehand, click the Manage accounts link or click Add on the right of
the Credentials field to add the necessary credentials.

IMPORTANT!
The user account must have the ‘edit’ user role on the HPE 3PAR Web Services API Server.

2. When you add a storage system, Veeam Backup & Replication saves a fingerprint of the SSH key of the
HPE 3PAR Web Services API Server to the configuration database. During every subsequent connection
to the server, Veeam Backup & Replication uses the saved fingerprint to verify the server identity and
avoid man-in-the-middle attacks.
To let you identify the server, Veeam Backup & Replication displays the SSH key fingerprint:

 If you trust the server and want to connect to it, click Yes.

 If you do not trust the server, click No. Veeam Backup & Replication will display an error
message, and you will not be able to connect to the server.
If you update the SSH key on the server, you must acknowledge the new key in the server connection
settings. To do this, in the Storage Infrastructure view right-click the storage system, select Edit
storage, pass through the Edit Server wizard and click Trust to acknowledge the new key.

41 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Specify Access Options
At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

a. On the right of the Volumes to scan field, click Choose.

IMPORTANT!

If you plan to use Backup from Storage Snapshots, you need to make sure that you include in the rescan
scope volumes on which VM disks reside.

42 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard

At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

43 | Veeam Backup & Replication | Integration with Storage Systems |

44 | Veeam Backup & Replication | Integration with Storage Systems |
Adding NetApp Storage System
To add a NetApp storage system to the backup infrastructure, use the New NetApp Storage wizard.

Step 1. Launch New NetApp Storage Wizard

To launch the New NetApp Storage wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click NetApp Data ONTAP.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure
node and select Add Storage. In the displayed window, click NetApp Data ONTAP.

 You can use this method if at least one NetApp storage system is added to the backup infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the NetApp node under
Storage Infrastructure and select Add Storage. You can also select the NetApp node in the
inventory pane, right-click anywhere in the working area and select Add storage.

45 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Specify NetApp Server Name or Address
At the Name step of the wizard, specify the storage system name and description.

1. In the Management server DNS name or IP address field, specify a DNS name or IP address of the
storage system.
You can browse for storage systems that exist in your environment:

a. On the right of the Management server DNS name or IP address field, click Browse.

b. In the NetApp Storage System Discovery window, enter an IP address of the storage
system or IP address of the subnet where the storage is located and click Discover.
Veeam Backup & Replication will search the whole subnet for storage systems. For example, if
you enter 172.16.1.12 as an IP address, Veeam Backup & Replication will search storage
systems in subnet 172.16.1.* and display a list of storage systems detected in this subnet.

c. In the list below, select a storage system that you want to add.

46 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Specify Credentials and Protocol Type
At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
storage system, and select the transport protocol.

2. From the Protocol list, select the type of protocol over which you want to communicate with the storage
system: HTTP or HTTPs.
The default transport protocol is HTTPs. However, you can configure the storage system to communicate
with Veeam Backup & Replication over the HTTP protocol if needed.

3. The default port for communication with the storage system is 443. If necessary, you can change the
port number in storage system settings and specify the new port number in the Port field.

47 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Specify Access Options
At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

2. [For NetApp storage system working over NFS] During storage rescan, backup and restore operations,
Veeam Backup & Replication automatically creates required NFS export rules on the storage system. If
you do not want Veeam Backup & Replication to create export rules, clear the Create required NFS
export rules automatically check box.

3. If you plan to work with specific storage volumes, you can limit the storage rescan scope. In this case,
Veeam Backup & Replication will rescan only the volumes that you select. Limiting the rescan scope
reduces the amount of time required for the rescan operation.
To select volumes for rescan:

a. On the right of the Volumes to scan field, click Choose.

IMPORTANT!
If you plan to use Backup from Storage Snapshots, you need to make sure that you include in the rescan
scope volumes on which VM disks reside.

4. Operations of storage rescan and Backup from Storage Snapshots are performed with the help of a
backup proxy. On the right of the Backup proxies to use field, click Choose and define backup
proxies that you want to use for these operations.

48 | Veeam Backup & Replication | Integration with Storage Systems |

49 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

Adding Nimble Storage System

To add a Nimble storage system to the backup infrastructure, use the New Nimble Storage wizard.

50 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch New Nimble Storage Wizard
To launch the New Nimble Storage wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click Hewlett Packard Enterprise and select Nimble.

 You can use this method if at least one Nimble storage system is added to the backup infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the Nimble node under
Storage Infrastructure and select Add Storage. You can also select the Nimble node in the
inventory pane, right-click anywhere in the working area and select Add storage.

51 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Specify Storage Name or Address
At the Name step of the wizard, specify the storage system name and description.

1. In the DNS name or IP address field, specify a DNS name or IP address of the storage system.

Step 3. Specify Credentials

At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
storage system.

1. From the Credentials list, select credentials to connect to the storage system. If you have not set up
credentials beforehand, click the Manage accounts link or click Add on the right of the Credentials
field to add the credentials.
The user account that you select must have Administrator or Power User permissions on the Nimble
storage system.

2. [For Nimble OS 2.3 and later] Veeam Backup & Replication uses Nimble RESTful API to communicate
with the storage system. By default, commands to the RESTful API server are sent over port 5392. If you
use another port for Nimble RESTful API, you can change the port number.

3. [For Nimble OS 2.3] When you add a storage system to the backup infrastructure,
Veeam Backup & Replication saves a fingerprint of the SSH key of the management server to the
configuration database. During every subsequent connection to the server, Veeam Backup & Replication
uses the saved fingerprint to verify the server identity and avoid man-in-the-middle attacks.
To let you identify the server, Veeam Backup & Replication displays the SSH key fingerprint:

52 | Veeam Backup & Replication | Integration with Storage Systems |

 If you trust the server and want to connect to it, click Yes.

 If you do not trust the server, click No. Veeam Backup & Replication will display an error
message, and you will not be able to connect to the server.
If you update the SSH key on the server, you must acknowledge the new key in the server connection
settings. To do this, in the Storage Infrastructure view right-click the storage system, select Edit
storage, pass through the Edit Server wizard and click Trust to acknowledge the new key.

Step 4. Specify Access Options

At the Access Options step of the wizard, specify options for accessing the storage system.

1. The Protocol to use list displays protocols over which the storage system can work. Select check boxes
next to protocols over which you want to work with the storage system.

a. On the right of the Volumes to scan field, click Choose.

53 | Veeam Backup & Replication | Integration with Storage Systems |

IMPORTANT!
If you plan to use Backup from Storage Snapshots, you need to make sure that you include in the rescan
scope volumes on which VM disks reside.

NOTE:
If you select backup proxies explicitly, you must make sure that you also select these proxies in settings of
backup and replication jobs for which you plan to use Backup from Storage Snapshots. If a backup proxy
selected in the job settings is not added to the list of backup proxies in the storage system connection
settings, Veeam Backup & Replication will fail over to the regular data processing mode. For more information,
see Configuring Backup from Storage Snapshots.

54 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

55 | Veeam Backup & Replication | Integration with Storage Systems |

Adding Cisco HyperFlex Storage System
To add a Cisco HyperFlex storage system to the backup infrastructure, use the New Cisco HyperFlex System
wizard.

Step 1. Launch New Cisco HyperFlex System Wizard

To launch the New Cisco HyperFlex System wizard, do one of the following:

 Open the Storage Infrastructure view. In the working area, click Add Storage. In the displayed
window, click Cisco HyperFlex.

 Open the Storage Infrastructure view. In the inventory pane, right-click the Storage Infrastructure
node and select Add Storage. In the displayed window, click Cisco HyperFlex.

 You can use this method if at least one Cisco HyperFlex storage system is added to the backup
infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the Cisco HyperFlex node
under Storage Infrastructure and select Add Storage. You can also select the Cisco HyperFlex
node in the inventory pane, right-click anywhere in the working area and select Add storage.

56 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Specify Storage Name or Address
At the Name step of the wizard, specify the storage system name and description.

1. In the DNS name or IP address field, enter a full DNS name or IP address of the Cisco HyperFlex
cluster management interface.

2. In the URL field, enter a URL of the Cisco HyperFlex RESTful API server. By default,
Veeam Backup & Replication uses the following URL:
https://<server>:8080
where <server> is the name or IP address of the Cisco HyperFlex RESTful API server, and 8080 is a
default port for communication with the Cisco HyperFlex RESTful API server.

3. In the Description field, provide a description for future reference. The default description contains
information about the user who added the storage system, date and time when the server was added.

57 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Specify Credentials
At the Credentials step of the wizard, specify credentials for a user account with administrator privileges on the
storage system.

From the Credentials list, select credentials to connect to the storage system. If you have not set up credentials
beforehand, click the Manage accounts link or click Add on the right of the Credentials field to add the
credentials. For more information, see the Credentials Manager section in Veeam Backup & Replication User
Guide.

58 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Specify Backup Proxy
At the Access Options step of the wizard, click Choose and select backup proxies that you plan to use for
backup and replication of VMs hosted on Cisco HyperFlex. Veeam Backup & Replication will check what data
retrieval methods are available for these backup proxies. For more information, see Methods of Data Retrieval.

 Select Automatic selection to let Veeam Backup & Replication check data retrieval methods for all
backup proxies in the backup infrastructure.

 Select Use the selected backup proxy servers only to explicitly define backup proxies that will be
used for VM data processing. In this case, Veeam Backup & Replication will check data retrieval methods
only for selected backup proxies.

59 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system and click Finish to start the
rescan process.

60 | Veeam Backup & Replication | Integration with Storage Systems |

Re-Scanning Storage Systems
You can rescan a storage system added to the backup infrastructure. Storage system rescan may be required, for
example, if you create or delete snapshots on the storage system. Storage system rescan will help you discover
these changes and update the storage system hierarchy in the Veeam Backup & Replication console.

Storage system rescan can be performed automatically or manually.

 Automatic storage rescan: Veeam Backup & Replication uses the following processes to rescan the
storage system:

o The Storage Monitor process runs in the background. The process detects new snapshots
and volumes, and performs their rescan with a time interval of 10 minutes.

o The Storage Discovery process starts every 7 days. The process performs rescan of the
whole storage system or selected volumes (if you limited the rescan scope for the storage
system).

 Manual storage rescan: if necessary, you can start the Storage Discovery process manually. Storage
discovery can be performed against any node in the storage system hierarchy: storage system, storage
volume and so on.

Before you start storage discovery, make sure that you have a properly configured backup proxy in the backup
infrastructure. Otherwise, Veeam Backup & Replication will not be able to match storage volumes to VMware
datastores and locate VMs on these storage volumes.

NOTE:

Veeam Backup & Replication does not perform rescan on VMs whose disks are located on VVol datastores.

To start storage discovery:

1. Open the Storage Infrastructure view.

2. In the inventory pane, expand the storage system tree.

3. Select a node in the storage system hierarchy: storage system, volume and so on.

4. Click Rescan on the ribbon or right-click the node in the hierarchy and select Rescan storage or
Rescan volume.

61 | Veeam Backup & Replication | Integration with Storage Systems |

IMPORTANT!
The rescan operation is performed only for volumes included in the rescan scope. To change the rescan
scope, open the storage system connection settings and navigate to the Access Options step of the wizard.
For details, see Adding Storage System.

62 | Veeam Backup & Replication | Integration with Storage Systems |

Limiting Rescan Scope
The storage system hierarchy can be very extensive, and the rescan process can take much time. To minimize
the rescan time, you can instruct Veeam Backup & Replication to rescan only specific volumes.

To limit the rescan scope:

1. Open the Storage Infrastructure view.

2. In the inventory pane, select the storage system type.

3. In the working area, right-click the root node of the storage system and click Choose volumes.

4. In the Choose Volumes window, select which volumes you want to rescan:

 To exclude volumes from rescan, select All volumes except, click Add and select volumes in
the list.

 To rescan only specific volumes, select Only these volumes, click Add and select volumes in
the list.
If you leave the Automatic detection option selected, Veeam Backup & Replication will rescan all
volumes in the storage system hierarchy.

5. Click OK.

6. Click Finish.

63 | Veeam Backup & Replication | Integration with Storage Systems |

Removing Storage Systems
You can remove a storage system from the backup infrastructure, for example, if you do not want to perform
Backup from Storage Snapshots or use Veeam Explorer from Storage Snapshots anymore.

Mind the following:

 When you remove a storage system from the backup infrastructure, Veeam Backup & Replication
attempts to find hosts with IQN starting with the 'VeeamAUX' prefix and remove such objects from the
storage hierarchy. Veeam Backup & Replication assumes that such hosts are created by
Veeam Backup & Replication itself and are used for service purposes.

 [For NetApp and Nimble storage] You cannot remove a storage system from the backup infrastructure if
you have a snapshot job configured for this storage system. You must delete the snapshot job first.

To remove a storage system:

1. Open the Storage Infrastructure view.

2. In the inventory pane or in the working area, right-click the storage system and select Remove
storage.

64 | Veeam Backup & Replication | Integration with Storage Systems |

Backup from Storage Snapshots
Backup from Storage Snapshots lets you speed up backup and replication for VMware vSphere VMs whose disks
are hosted on storage systems. When you perform Backup from Storage Snapshots, Veeam Backup & Replication
leverages storage snapshots for VM data processing. Backup from Storage Snapshots lets you reduce impact of
backup and replication activities on the production environment and improve RPOs.

65 | Veeam Backup & Replication | Integration with Storage Systems |

VM Data Processing
Backup from Storage Snapshots introduces a different mode of data processing for VMware vSphere VMs whose
disks are hosted on storage systems.

Regular VM Data Processing

In the regular processing course, Veeam Backup & Replication uses a VMware vSphere snapshot. The VMware
vSphere snapshot “freezes” the VM state and data at a specific point in time. This way, the VM data is brought to
a consistent state suitable for backup or replication.

During regular VM data processing, Veeam Backup & Replication performs the following actions:

1. Veeam Backup & Replication triggers a VMware vSphere snapshot for a VM. VM disks are put to the
read-only state, and every virtual disk of the VM receives a delta file named like vmname-00001.vmdk.

2. Veeam Backup & Replication copies VM data from read-only disks of the VM. All changes that the user
makes to the VM while backup or replication is performed are written to delta files.

3. When VM processing is finished, the VMware vSphere snapshot is committed. VM disks resume writes,
and data from delta files is merged to the VM disks. After data is merged, the VMware vSphere snapshot
is removed.

Regular VM data processing may take long. If backup or replication is performed for a VM running a highly
transactional application, the delta file may grow large. The snapshot commit process will take much time, and
the VM may hang up during this process. To overcome this situation, you can use Backup from Storage
Snapshots.

66 | Veeam Backup & Replication | Integration with Storage Systems |

Backup from Storage Snapshots
Backup from Storage Snapshots lets you speed up backup and replication operations. For Backup from Storage
Snapshots, Veeam Backup & Replication complements the VMware vSphere snapshot technology with the
storage snapshots technology, and uses storage snapshots as a source of data for backup and replication.

During Backup from Storage Snapshots, Veeam Backup & Replication performs the following actions:

1. Veeam Backup & Replication triggers a VMware vSphere snapshot for VMs whose disks are hosted on the
storage system.

2. Veeam Backup & Replication triggers a storage snapshot of the volume or LUN hosting the VM itself and
the created VMware vSphere snapshot.

3. The VMware vSphere snapshot on the original storage volume is deleted immediately after the storage
snapshot is created. Veeam Backup & Replication accesses the ‘cloned’ VMware vSphere snapshot on the
storage snapshot and copies VM data from it.

4. When VM processing is finished, the storage snapshot capturing the VMware vSphere snapshot is
removed.

As a result, the VMware vSphere snapshot exists for a very short time, namely several seconds. Delta files do not
grow large, and the time of VMware vSphere snapshot commit decreases.

67 | Veeam Backup & Replication | Integration with Storage Systems |

Backup from Primary Storage Arrays
To use Backup from Storage Snapshots, you must select the Enable backup from storage snapshots check
box in backup or replication job settings.

When you run a job with Backup from Storage Snapshots enabled, Veeam Backup & Replication performs the
following actions:

1. Veeam Backup & Replication analyzes which VMs in the job host their disks on the storage system, and
triggers VMware vCenter Server to create VMware vSphere snapshots for these VMs.

2. Veeam Backup & Replication instructs the storage system to create a snapshot of the storage volume or
LUN that hosts VM disks and VMware vSphere snapshots.

3. Veeam Backup & Replication gets Changed Block Tracking information for VMs hosted on the storage
system.

4. Veeam Backup & Replication instructs VMware vCenter Server to remove VMware vSphere snapshots on
the production storage system. The 'cloned' VMware vSphere snapshots remain on the created storage
snapshots.

5. Veeam Backup & Replication checks the backup infrastructure and detects if there is a backup proxy that
has a direct connection to the storage system. Veeam Backup & Replication mounts the storage snapshot
as a new volume to this backup proxy.

6. Veeam Backup & Replication reads and transports VM data blocks via the backup proxy to the backup
repository. For incremental backup or replication, Veeam Backup & Replication uses obtained CBT data to
retrieve only changed data blocks from the storage snapshot.

68 | Veeam Backup & Replication | Integration with Storage Systems |

7. When VM data processing is finished, Veeam Backup & Replication unmounts the storage snapshot from
the backup proxy and instructs the storage system to remove the storage snapshot.

Mixed Job Scenarios

Backup from Storage Snapshots is used only for those VMs whose disks are hosted on supported storage
systems. As backup and replication jobs typically process a number of VMs that may reside on different types of
storage, Veeam Backup & Replication processes VMs in mixed jobs in the following way:

 If a job processes a number of VMs whose disks are hosted on different types of storage,
Veeam Backup & Replication uses Backup from Storage Snapshots only for VMs whose disks are hosted
on supported storage systems. Other VMs are processed in a regular manner.

 If a VM has several disks, some hosted on supported storage systems and some hosted on another type
of storage, Veeam Backup & Replication does not use Backup from Storage Snapshots to such VM. All
disks of such VM are processed in a regular manner.

During a job, Veeam Backup & Replication processes VMs residing on different types of storage at different time:

1. Veeam Backup & Replication first triggers VMware vSphere snapshots and storage snapshots for VMs
hosted on supported storage systems.

2. After the storage snapshot is created, Veeam Backup & Replication triggers VMware vSphere snapshots
for other VMs. These VMs are processed in a regular manner further on, in parallel with VMs whose disks
are hosted on supported storage systems.

Configuring Backup from Storage Snapshots

You can instruct Veeam Backup & Replication to use Backup from Storage Snapshots for backup and replication.
During backup and replication jobs, Veeam Backup & Replication reads data of processed VMs from storage
snapshots, which speeds up backup and replication operations and improves RPOs.

Before you perform Backup from Storage Snapshots, check the following prerequisites:

 You must install a license for Veeam Backup & Replication Enterprise Plus Edition on the backup server.

 You must configure the backup infrastructure in a proper way:

o You must add to the backup infrastructure a backup proxy that will be used for backup or
replication, and properly configure this backup proxy. For more information, see
Configuring Backup Proxy.

o You must add to the backup infrastructure vCenter Server or ESX(i) host(s) with VMs

69 | Veeam Backup & Replication | Integration with Storage Systems |

whose disks are hosted on the storage system.

o You must add the storage system to the backup infrastructure.

 You must check limitations for Backup from Storage Snapshots. For more information, see Backup from
Storage Snapshots.

To back up and replicate VMs using Backup from Storage Snapshots:

1. Configure a backup or replication job. At the Storage step of the backup or replication job wizard, select
a backup proxy that will be used for data transport. You can assign the backup proxy explicitly or choose
the automatic mode of backup proxy selection.

NOTE:

A backup proxy that you select must be added to the list of backup proxies in storage system connection
settings. If the backup proxy is not added to the list in storage system connection settings,
Veeam Backup & Replication will fail over to the regular data processing mode. For more information, see
Adding Storage Systems.

2. At the Storage step of the wizard, click Advanced, then click the Integration tab. Make sure that the
Enable backup from storage snapshots check box is selected. By default, this option is enabled for
all newly created jobs.

3. If you add to the job many VMs whose disks are hosted on the same volume or LUN, select the Limit
processed VM count per storage snapshot to <N> check box and specify the number of VMs for
which 1 storage snapshot must be created. Veeam Backup & Replication will divide VMs into several
groups and trigger a separate storage snapshot for every VM group. As a result, the job performance will
increase. For more information, see Limitation on Number of VMs per Snapshot.

70 | Veeam Backup & Replication | Integration with Storage Systems |

4. If Veeam Backup & Replication fails to create a storage snapshot, VMs whose disks are hosted on the
storage system will not be processed by the job. To fail over to the regular data processing mode and
back up or replicate such VMs, select the Failover to standard backup check box.

71 | Veeam Backup & Replication | Integration with Storage Systems |

Backup from Secondary Storage Arrays
If the primary storage array is associated with a secondary storage array, you can use the secondary storage
array as a data source for backup. Backup from snapshots on secondary storage arrays reduces impact on the
production storage. During backup, operations on VM data reading are performed on the side of the secondary
storage array, and the primary storage array is not affected.

You can use backup from snapshots on secondary storage arrays if you have the following storage systems in the
production environment:

 HPE 3PAR Peer Persistence

 IBM Spectrum Virtualize with HyperSwap function

 NetApp SnapMirror and/or NetApp SnapVault

 Nimble arrays with replicated copies

To back up from snapshots on secondary storage arrays, you must configure the backup job to build a snapshot
chain on the secondary storage array and instruct Veeam Backup & Replication to use the created snapshots as a
data source.

72 | Veeam Backup & Replication | Integration with Storage Systems |

How Backup from Secondary Storage Systems Works
Backup from snapshots on secondary storage arrays is similar to Backup from Storage Snapshots on the primary
storage array.

1. Veeam Backup & Replication triggers a VMware vSphere snapshot for a VM whose disks are hosted on
the primary storage array.

2. Veeam Backup & Replication instructs the storage system to create an application-consistent storage
snapshot on the primary storage array. The created snapshots capture the VMware vSphere snapshot.
The VMware vSphere snapshot on the primary storage array is then deleted.

3. The storage snapshot is transported from the primary storage array to the secondary storage array.

4. Veeam Backup & Replication checks if there is a backup proxy that has a direct connection to the
secondary storage array. The transported storage snapshot is mounted to this backup proxy.

5. The backup job retrieves VM data from the mounted storage snapshot.

6. When the job finishes processing the VM, Veeam Backup & Replication instructs the storage system to
delete a snapshot on the primary storage array. The transported snapshot on the secondary storage
remains in the snapshot chain until it is removed by the retention policy.

Mind the following:

 [For NetApp storage systems] Veeam Backup & Replication creates auxiliary snapshots on the primary
storage system. The number of storage snapshots in the snapshot chain cannot be fewer than 1.

 [For Nimble storage systems] On Nimble storage systems, snapshot transport is triggered as soon as you
create a new storage snapshot. For this reason, launch of snapshot transport and deletion of VMware
vSphere snapshots are performed in parallel.

73 | Veeam Backup & Replication | Integration with Storage Systems |

Failover to Backup from Snapshots on Primary Storage Arrays
In some cases, Veeam Backup & Replication may fail to back up VM data from storage snapshots on the
secondary storage array. This can happen, for example, if Veeam Backup & Replication fails to connect to the
secondary storage array or a license required for volume or LUN export is not installed (in case of NetApp
SnapMirror or SnapVault).

To overcome this situation, you can instruct the backup job to fail over to the Backup from Storage Snapshots on
the primary storage array. In this case, Veeam Backup & Replication will create a storage snapshot on the
primary storage array and attempt to transport it to the secondary storage array. If the transport process fails,
Veeam Backup & Replication will retrieve VM data from the created snapshot on the primary storage array.

To let Veeam Backup & Replication fail over to Backup from Storage Snapshots on the primary storage array, you
must enable the Failover to primary storage snapshot option in the backup job settings.

NOTE:
Failover to Backup from Storage Snapshots on the primary storage array is not supported for HPE 3PAR Peer
Persistence and IBM Spectrum Virtualize with HyperSwap function.

74 | Veeam Backup & Replication | Integration with Storage Systems |

Configuring Backup from Snapshots on Secondary Storage
Arrays
You can configure a backup job to perform Backup from Storage Snapshots on secondary storage arrays.

Before you perform Backup from Storage Snapshots, check the following prerequisites:

 You must configure a secondary storage array for the primary storage system where VMs that you plan
to back up are hosted.

 You must install a license for Veeam Backup & Replication Enterprise Plus edition on the backup server.

 You must configure the backup infrastructure in a proper way:

o [For NetApp] You must configure volume SnapMirror/Snapvault relationships between the
primary and secondary storage arrays. For more information, see NetApp documentation.

o [For Nimble] You must configure Volume Collection replication from the primary storage
array to the secondary storage array. For more information, see Nimble documentation.

o You must add to the backup infrastructure a backup proxy that will be used for backup, and
properly configure this backup proxy. For more information, see Configuring Backup Proxy.

o You must add to the backup infrastructure vCenter Server or ESX(i) host(s) with VMs
whose disks are hosted on the storage system.

o You must add the primary storage system and secondary storage array to the backup
infrastructure.
[For IBM Spectrum Virtualize with HyperSwap function] To perform Backup from Secondary
Storage Arrays, add IBM Spectrum Virtualize storage system to the backup infrastructure.
Select secondary storage volumes as a data source for backup using registry keys. For more
information, contact Veeam Support Team.

IMPORTANT!
When you add arrays to the backup infrastructure, you must add to the rescan scope volumes and LUNs on
which VM disks are located (both for primary and secondary storage arrays). For more information, see
Adding Storage Systems.

 You must check limitations for Backup from Storage Snapshots. For more information, see Backup from
Storage Snapshots.

 [For NetApp] You must install a license for storage snapshot export on NetApp SnapMirror or SnapVault.
For more information, see Required Licenses for NetApp.

To back up VMs from snapshots on secondary storage arrays:

1. Configure a backup job. At the Storage step of the backup job wizard, select a backup proxy that will be
used for data transport. You can assign the backup proxy explicitly or choose the automatic mode of
backup proxy selection.

75 | Veeam Backup & Replication | Integration with Storage Systems |

NOTE:
A backup proxy that you select must be added to the list of backup proxies in storage system connection
settings. If the backup proxy is not added to the list in storage system connection settings,
Veeam Backup & Replication will fail over to the regular data processing mode. For more information, see
Adding Storage Systems.

2. From the Backup repository list, select a backup repository where you want to store backup files.

3. In the Retention policy section, specify the number of backup restore points that you want to keep.

76 | Veeam Backup & Replication | Integration with Storage Systems |

4. Select the Configure secondary destinations for this job check box.

5. Click Advanced, then click the Integration tab. Make sure that the Enable backup from storage
snapshots check box is selected. By default, this option is enabled for all newly created jobs.

6. If you add to the job many VMs whose disks are located on the same volume or LUN, select the Limit
processed VM count per storage snapshot to <N> check box and specify the number of VMs for
which 1 storage snapshot must be created. Veeam Backup & Replication will divide VMs into several
groups and trigger a separate storage snapshot for every VM group. As a result, the job performance will
increase. For more information, see Limitation on Number of VMs per Snapshot.

7. If Veeam Backup & Replication fails to create a storage snapshot, VMs whose disks are located on the
storage system will not be processed by the job. To fail over to the regular data processing mode and
back up such VMs, select the Failover to standard backup check box.

77 | Veeam Backup & Replication | Integration with Storage Systems |

8. If Veeam Backup & Replication cannot create a storage snapshot on the secondary storage array, the job
will not back up VMs whose disks are located to the storage system. To fail over to Backup from Storage
Snapshots on the primary storage system, select the Failover to primary storage snapshot check
box. If Veeam Backup & Replication fails to create a storage snapshot on the secondary storage array, it
will trigger the storage snapshot on the primary storage system and use it as a source for backup. Note,
however, that Backup from Storage Snapshots on the primary storage system will produce additional
load on the production environment.

9. At the Secondary Target step of the wizard, click Add and select a secondary storage array. For
example, Nimble Snapshot Replicated Copy.

10. In the Number of snapshot copies to retain field, specify the number of storage snapshots that you
want to maintain in the snapshot chain on the secondary storage array. When this number is exceeded,
Veeam Backup & Replication will trigger the storage system to remove the earliest snapshot from the
chain.

78 | Veeam Backup & Replication | Integration with Storage Systems |

11. Select the Use as the data source check box.

12. Specify other backup job settings as required.

13. Click Next, then click Finish to save the job settings.

79 | Veeam Backup & Replication | Integration with Storage Systems |

Limitation on Number of VMs per Snapshot
By default, during Backup from Storage Snapshots Veeam Backup & Replication creates VMware vSphere
snapshots for all VMs that reside on the same volume or LUN, and then triggers a storage snapshot for this
volume or LUN. If the number of VMs on the volume or LUN is great, VM snapshot creation may take much time.
To speed up the backup or replication process, you can limit the number of VMs per storage snapshot.

To limit the number of storage snapshots, you must enable the Limit processed VM count per storage
snapshot to <N> option and specify the number of VMs per snapshot in the job settings.

With the limitation option enabled, Veeam Backup & Replication processes VMs in several cycles:

1. Veeam Backup & Replication divides VMs into several groups, as defined in the Limit processed VM
count per storage snapshot to <N> option.

2. Veeam Backup & Replication triggers VMware vSphere snapshots for VMs in the first group.

3. Veeam Backup & Replication triggers a storage snapshot for the volume or LUN on which VMs are
hosted.

4. Veeam Backup & Replication deletes VMware vSphere snapshots for VMs in the first group.

5. Veeam Backup & Replication copies data of VMs in the first group from the storage snapshot.

6. Veeam Backup & Replication removes the storage snapshot.

7. Steps 2-6 are repeated for every remaining group of VMs.

For example, you add to the job 15 VMs whose disks are hosted on the same volume and set the Limit
processed VM count per storage snapshot to <N> option to 10. Veeam Backup & Replication will divide all
VMs into 2 groups — a group of 10 VMs and group of 5 VMs. Veeam Backup & Replication will perform the data
processing cycle for the first group of VMs. When VM data processing is over, Veeam Backup & Replication will
start processing the second group of VMs.

80 | Veeam Backup & Replication | Integration with Storage Systems |

Backup from Cisco HyperFlex Snapshots
Veeam Backup & Replication integrates with Cisco HyperFlex and allows you to improve performance of backup
and replication of VMware vSphere VMs hosted on Cisco HyperFlex.

For backup and replication of VMs hosted on Cisco HyperFlex, Veeam Backup & Replication does not use VMware
vSphere snapshots to preserve VMs in a consistent state suitable for backup or replication. Instead, it relies on
native Cisco HyperFlex VM snapshots. Use of Cisco HyperFlex VM snapshots lets avoid the overhead produced by
VMware vSphere snapshots removal on the production environment.

To create HyperFlex VM snapshots, Cisco leverages VMware vSphere Storage APIs Array Integration (VAAI).
VAAI enables VMware vSphere ESX(i) hosts to communicate with storage devices and offload storage operations
such as snapshot creation and cloning to the storage array. As a result, Cisco HyperFlex can create space
efficient VM snapshots almost instantly. Veeam Backup & Replication, in its turn, can use HyperFlex snapshots for
VM data processing, which helps speed up backup and replication operations, reduce impact of backup and
replication activities on the production environment and improve RPOs.

Implementation of integration with Cisco HyperFlex is different from those provided for other supported storage
systems. When Veeam Backup & Replication processes VMs hosted on Cisco HyperFlex, it leverages snapshots
created at the VM level, not snapshots created at the storage volumes level. The results of the VM processing are
reported in job results: if a VM is processed with Cisco HyperFlex snapshots, Veeam Backup & Replication
displays the 'Creating VM native Cisco HX snapshot' message in job statistics.

81 | Veeam Backup & Replication | Integration with Storage Systems |

Integration Modes
Veeam Backup & Replication provides two types of integration for Cisco HyperFlex:

 Advanced integration with Cisco HyperFlex

 Standard data processing with Direct NFS enhancements

Advanced Integration with Cisco HyperFlex

In case of full integration with Cisco HyperFlex, Veeam Backup & Replication can leverage Cisco HyperFlex VM
snapshots for backup and replication, which improves VM data processing performance.

Veeam Backup & Replication fully integrates with Cisco HyperFlex if the production environment and backup
infrastructure meet the following requirements:

 VMs reside on the supported Cisco HyperFlex system. For more information, see System Requirements.

 Veeam Backup & Replication 9.5 Update 2 or newer is installed on the backup server.

 License for Veeam Backup & Replication Enterprise Plus Edition is installed on the backup server.

 Cisco HyperFlex system is added to the backup infrastructure. For more information, see Adding Cisco
HyperFlex Storage System.

 Backup proxy is properly configured in the backup infrastructure. For more information, see Configuring
Backup Proxies.

 The Enable backup from storage snapshots option is selected in the job settings (default setting).
For more information, see Configuring Backup of VMs on Cisco HyperFlex.

You can instruct Veeam Backup & Replication to read data from Cisco HyperFlex snapshots in the following
transport modes: Direct storage access, Virtual appliance or Network. The recommended mode is Direct storage
access working over NFS protocol. It provides the best performance and low overhead on ESX(i) hosts. In this
mode, Veeam Backup & Replication bypasses the ESX(i) host and reads/writes data directly from/to Cisco
HyperFlex NFS data network.

Standard Data Processing with Direct NFS Enhancements

Veeam Backup & Replication can use standard backup methods to process VMs hosted on Cisco HyperFlex. In
this case, Veeam Backup & Replication will leverage standard VMware vSphere VM snapshots, not Cisco
HyperFlex VM snapshots to preserve VMs in a consistent state suitable for backup or replication.

To allow Veeam Backup & Replication to access VM data directly over the HyperFlex Data network by NFS
protocol, Veeam has added some enhancements starting from Veeam Backup & Replication v9.0 Update 2.
Veeam Backup & Replication can use the Direct NFS access transport mode if the production environment and
backup infrastructure meet the following requirements:

 Direct NFS access is enabled on data platform controllers. For more information,
https://www.veeam.com/kb2300.

 VMs do not have Cisco HyperFlex snapshots (including the base snapshot) or VMware vSphere
snapshots.

 VMs meet requirements described in the Limitations for Direct NFS access section.

 Backup proxies assigned for jobs work in the Direct storage access or Automatic selection modes. For
more information, see the Adding VMware Backup Proxies section in Veeam Backup & Replication User
Guide.

82 | Veeam Backup & Replication | Integration with Storage Systems |

 Backup data read over NFS is processed by a single HyperFlex Controller that holds the HyperFlex
Controller Cluster IP.

If these requirements are not met, Veeam Backup & Replication can process VM data in the Virtual appliance or
Network transport mode.

The diagram below demonstrates how Veeam Backup & Replication picks transport modes for processing VMs
hosted on Cisco HyperFlex:

83 | Veeam Backup & Replication | Integration with Storage Systems |

How Backup from Cisco HyperFlex Snapshots
Works
When you perform backup or replication from Cisco HyperFlex snapshots, Veeam Backup & Replication performs
the following actions:

1. Veeam Backup & Replication analyses which VMs in the job are hosted on Cisco HyperFlex.

2. If application-aware processing is enabled, Veeam Backup & Replication quiesces data and applications
on VMs guest OSes.

3. Veeam Backup & Replication triggers Cisco HyperFlex VM snapshots through VAAI individually for every
processed VM.

4. If application-aware processing is enabled, Veeam Backup & Replication resumes quiesced I/O activities
on VMs guest OSes.

5. Veeam Backup & Replication reads new virtual disk data blocks (for full job session) or changed virtual
disk data blocks with CBT (for incremental job sessions) from Cisco HyperFlex NFS stores and transports
them to the backup repository or target datastore.

6. After VM data processing is finished, Veeam Backup & Replication triggers removal of the Cisco
HyperFlex VM snapshots.

NOTE:
After the backup job completes, the HyperFlex Sentinel snapshot (base snapshot) remains for the VM and is
visible in the VMware Snapshot Manager. This is done to improve the processing performance and reduce
storage load. For more information, see the Cisco HyperFlex documentation.

84 | Veeam Backup & Replication | Integration with Storage Systems |

Configuring Backup Proxies
To enable backup and replication from Cisco HyperFlex snapshots, you must configure one or more backup
proxies in the backup infrastructure. Backup proxies must meet the following requirements:

 The role of a backup proxy must be assigned to a Microsoft Windows machine. This can be a dedicated
machine or backup server performing the role of the default backup proxy.

 The backup proxy that you plan to use must have NFS access to the network handling traffic between
Cisco HyperFlex and ESXi hosts where the backed up or replicated VMs reside.

Methods of Data Retrieving

Backup proxies that process data of VMs hosted on Cisco HyperFlex can read VM data from NFS stores over the
NFS HyperFlex data network. Depending on the backup infrastructure configuration, backup proxies can read
data over the following data paths:

 Backup from Storage Snapshots over IO Visor on ESX(i) hosts. The IO Visor is a Cisco HyperFlex
software module that runs on every ESXi host that is a part of the Cisco HyperFlex cluster. It presents
HyperFlex NFS datastores to the ESX(i) hosts and optimizes the data paths in the HyperFlex cluster.
The backup over IO Visor is the preferred method. It provides the high speed of VM data reading and
balances the load across the HyperFlex cluster. To read VM data over IO Visor, backup proxies must be
connected to the same HyperFlex data network as the processed VMs. You must also configure a firewall
rule on the ESXi hosts to allow Veeam Backup & Replication to interact with the IO Visor. For more
information, see Configuring Firewall Rules for Cisco HyperFlex IOVisor Processing.
If the firewall rules are not configured, Veeam Backup & Replication will fail over to Backup from Storage
Snapshot over the HyperFlex Controller Cluster IP by default.

 Backup from Storage Snapshots over HyperFlex Controller Cluster IP. In this processing mode,
all traffic is handled by a single HX controller that holds the HyperFlex Controller Cluster IP.
To read VM data over HyperFlex Controller Cluster IP, backup proxies must be connected to the same
HyperFlex data network as the processed VMs. Veeam Backup & Replication will configure all necessary
firewall settings within the HyperFlex Controllers automatically during the storage discovery process.
Veeam Backup & Replication automatically detects new HyperFlex controllers and applies firewall
changes.

Configuring Firewall Rules for Cisco HyperFlex IO Visor

Processing
The Cisco HyperFlex IO Visor is a software component that runs on all ESXi hosts within a Cisco HyperFlex
cluster. It works as a NFS server for Veeam traffic.

You need to allow NFS traffic from the backup proxies to ESXi hosts. As Cisco IO Visor based NFS communication
uses dynamic ports, you need to create an ESXi firewall rule with inbound ports 0-65535 and the backup proxy IP
addresses as allowed IP addresses.

You can do this in 3 ways:

 Create a VMware ESXi host extension VIB file that creates the firewall rule, install/enable it on all hosts
and set the backup proxy IP addresses as allowed ones. For more information, see
https://www.veeam.com/kb2291.

 Use a predefined VMware ESXi host extension VIB file from the Veeam Community GitHUB project. For
more information, see https://www.veeam.com/kb2298.

85 | Veeam Backup & Replication | Integration with Storage Systems |

 Use ESXi command line interface to create a temporary firewall rule (until the next ESXi host reboot). For
more information, see https://www.veeam.com/kb2299.

Configuring Backup Proxies for Backup from Storage Snapshot

with Virtual Appliance or Network mode
If you plan to use the Virtual Appliance or Network mode to process VMs hosted on Cisco HyperFlex, you must
configure the backup infrastructure in the following way:

1. You must add Cisco HyperFlex to the backup infrastructure to allow Veeam Backup & Replication to
create HyperFlex snapshots.

2. You must configure the backup proxies to work in the Virtual Appliance or Network transport mode. For
more information, see the Virtual Appliance and Network Mode sections in Veeam Backup & Replication
User Guide.

3. If you plan to use the Virtual Appliance mode, it is recommended that you enable an optimization for NFS
datastores in Veeam Backup & Replication to avoid VM stuns as described in
http://kb.vmware.com/kb/2010953. To do this:

a. Create a backup proxy on every host in the VMware vSphere cluster where VMs that you plan
to back up or replicate reside.

b. On the machine where the Veeam Backup & Replication console is installed, open Registry
Editor.

c. Navigate to the key: HKLM\Software\Veeam\Veeam Backup and Replication\.

d. Create a new DWORD with name EnableSameHostHotaddMode, and set its value to 2.

If a backup proxy on the same host as a processed VM is unavailable,

Veeam Backup & Replication will use an available backup proxy on a different host, but force it
to use the Network transport mode, so that no stun occurs.

86 | Veeam Backup & Replication | Integration with Storage Systems |

Configuring Backup from Cisco HyperFlex
Snapshots
You can instruct Veeam Backup & Replication to perform backup and replication from Cisco HyperFlex snapshots.
During a backup and replication job, Veeam Backup & Replication will use native Cisco HyperFlex VM snapshots
instead of VMware vSphere snapshots, which will speed up backup and replication operations and improve RPOs.

Before you configure backup and replication jobs, make sure that the production environment and backup
infrastructure meet requirements for full integration with Cisco HyperFlex. For more information, see Integration
Modes.

To back up and replicate from Cisco HyperFlex snapshots:

87 | Veeam Backup & Replication | Integration with Storage Systems |

3. If Veeam Backup & Replication fails to process VMs in the full integration mode, VMs hosted on Cisco
HyperFlex will not be backed up or replicated. To fail over to the regular data processing mode, select
the Failover to standard backup check box.

88 | Veeam Backup & Replication | Integration with Storage Systems |

Configuring Direct NFS Access on Cisco
HyperFlex (Earlier Than 2.0)
VMware vSphere VMs hosted on Cisco HyperFlex access the storage with the help of special Cisco HyperFlex HX
Data Platform controllers. The controllers are dedicated VMs deployed on the same VMware ESX host that hosts
the VMs.

By default, the controllers are configured to receive traffic only from the ESX(i) host where they are located. To
provide communication between Veeam Backup & Replication and the Cisco HyperFlex storage system, you need
to manually enable the Direct NFS access mode between the backup proxy and controllers.

For more information about configuring Direct NFS Access on Cisco HyperFlex earlier than 2.0, see
https://www.veeam.com/kb2300.

89 | Veeam Backup & Replication | Integration with Storage Systems |

Snapshot Jobs
During Backup from Storage Snapshots, Veeam Backup & Replication instructs the storage system to create
temporary storage snapshots. Veeam Backup & Replication uses these snapshots as a data source for VM data
processing. Temporary storage snapshots are application-consistent: they hold VM data in a consistent state and
guarantee proper restore of application and services.

You can use snapshots created with Veeam Backup & Replication to build a snapshot chain on the primary or
secondary storage array.

NOTE:

[For IBM Spectrum Virtualize] When you add IBM Spectrum Virtualize storage systems with HyperSwap
function to the backup infrastructure, Veeam Backup and Replication, by default, works with primary storage
volumes. If you want to select secondary storage volumes as a data source for backup, use registry keys. For
more information, contact Veeam Support Team.

To create application-consistent snapshots on storage arrays, you must configure a backup job of the necessary
type. Veeam Backup & Replication lets you configure two types of jobs:

 Snapshot-only jobs

 Jobs creating snapshots in secondary destinations

90 | Veeam Backup & Replication | Integration with Storage Systems |

Snapshot-Only Jobs
The snapshot-only job is similar to scheduling automatic snapshot creation in the storage management console.
A snapshot-only job does not create Veeam backup files on the backup repository. It creates only storage
snapshots on the storage system by schedule defined in the job settings.

You can use snapshot-only jobs to create a snapshot chain on the primary storage array where disks of VMs
processed by the job are hosted. In addition to it, you can instruct the snapshot-only job to create a snapshot
chain on secondary storage arrays.

Depending on the backup job settings, the created snapshots can be application-consistent or crash-consistent.

Configuring Snapshot-Only Jobs

You can use snapshot-only jobs to create a chain of storage snapshots on the primary storage array and,
optionally, on the secondary storage array.

To configure a snapshot-only backup job:

1. Open the Home view.

2. Click Backup Job > VMware or vCloud on the ribbon. Veeam Backup & Replication will launch the
New Backup Job wizard.

3. At the Name step of the wizard, specify a name and description for the backup job.

4. At the Virtual Machines step of the wizard, click Add and select VMs whose disks are hosted on the
storage system.

5. At the Storage step of the wizard, select the primary storage array from the Backup repository list.

6. In the Retention policy section, specify the number of storage snapshots that you want to maintain in
the snapshot chain on the primary storage array. When this number is exceeded,
Veeam Backup & Replication will trigger the storage system to remove the earliest snapshot from the
snapshot chain.

91 | Veeam Backup & Replication | Integration with Storage Systems |

NOTE:
The number of snapshots in the snapshot chain on the primary storage array cannot be fewer than 1. Even if
you set the Number of snapshot copies to retain value to 0, Veeam Backup & Replication will keep 1
snapshot in the snapshot chain.

7. If you want to additionally create storage snapshots on the secondary storage array, select the
Configure secondary destinations for this job check box.

8. If you have enabled a secondary destination for the job, at the Secondary Target step of the wizard,
click Add and select the secondary storage array for a secondary location.

92 | Veeam Backup & Replication | Integration with Storage Systems |

9. [For secondary storage arrays] In the Number of snapshot copies to retain field, specify the number
of storage snapshots that you want to maintain in the snapshot chain on the secondary storage array.
When this number is exceeded, Veeam Backup & Replication will trigger the storage system to remove
the earliest snapshot from the chain.
This option is not applicable to HPE 3PAR Peer Persistence and NetApp SnapMirror. On these secondary
storage systems, Veeam Backup & Replication maintains the same number of storage snapshots as on
the primary storage systems.
If you use SnapMirror relationships between QTrees, you can define different retention policy settings for
the primary NetApp storage system and NetApp SnapMirror. For example, you can configure the backup
job to maintain 14 snapshots on the primary NetApp storage system and 10 snapshots of QTree
directories on NetApp SnapMirror.

93 | Veeam Backup & Replication | Integration with Storage Systems |

10. To create application-consistent storage snapshots, you can enable VMware Tools quiescence or
application-aware processing. If you do not enable either of these options, Veeam Backup & Replication
will produce a crash-consistent storage snapshot.

 To enable VMware Tools quiescence, in the advanced settings of the backup job select the
Enable VMware Tools quiescence check box. Veeam Backup & Replication will use VMware
Tools to create VMware vSphere snapshots for VMs whose disks are hosted on the storage
system. After VMware vSphere snapshots are created, Veeam Backup & Replication will trigger
a storage snapshot. For more information, see the VMware Tools Quiescence section in
Veeam Backup & Replication User Guide.

94 | Veeam Backup & Replication | Integration with Storage Systems |

 To enable application-aware processing, at the Guest Processing step of the wizard select the
Enable application-aware processing check box and specify necessary settings for
application-aware image processing.
During the backup job session, Veeam Backup & Replication will quiesce applications running
inside VMs using application-aware processing. After applications inside the VM are quiesced,
Veeam Backup & Replication will trigger a storage snapshot. For more information, see the
Application-Aware Processing section in Veeam Backup & Replication User Guide.

11. At the Schedule step of the wizard, select the Run the job automatically check box and specify the
schedule by which storage snapshots must be created.

12. Click Next, then click Finish to save the backup job settings.

95 | Veeam Backup & Replication | Integration with Storage Systems |

Storage Snapshots in Secondary Destination Jobs
You can configure a backup job to create regular backup files on the backup repository and, additionally,
maintain a snapshot chain on the storage system. Veeam Backup & Replication lets you create storage snapshots
in the following destinations:

 Primary storage array where VM disks are hosted

 Secondary storage arrays

NOTE:
[For IBM Spectrum Virtualize] When you add IBM Spectrum Virtualize storage systems with HyperSwap
function to the backup infrastructure, Veeam Backup and Replication, by default, works with primary storage
volumes. If you want to select secondary storage volumes as a data source for backup, use registry keys. For
more information, contact Veeam Support Team.

Depending on the backup job settings, the created storage snapshots can be application-consistent or crash-
consistent.

The backup job of this type is performed in the following way:

1. Veeam Backup & Replication triggers VMware vCenter Server to create a VMware vSphere snapshot for a
VM.

2. Veeam Backup & Replication instructs the storage system to create a temporary snapshot of a volume or
LUN capturing VM disks and VMware vSphere snapshot. The VMware vSphere snapshot on the primary
storage array is deleted.

3. Veeam Backup & Replication uses the temporary storage snapshot as a data source for backup and
replication.

4. After the backup or replication job is finished, the temporary volume snapshot is copied to the storage
system and published as a new snapshot in the snapshot chain.

5. After snapshot transport, Veeam Backup & Replication performs cleanup operations and removes the
temporary snapshot on the primary storage array.

96 | Veeam Backup & Replication | Integration with Storage Systems |

Configuring Jobs Creating Snapshots in Secondary Destination
You can configure a backup job to create backup files and a chain of storage snapshots on the primary storage
array and/or secondary storage arrays.

Before you perform a backup job, configure the backup infrastructure in a proper way:

• [For NetApp] You must configure volume SnapMirror/Snapvault relationships between the primary and
secondary storage arrays. For more information, see NetApp documentation.

• [For Nimble] You must configure Volume Collection replication from the primary storage array to the
secondary storage array. For more information, see Nimble documentation.

To configure a backup job:

1. Open the Home view.

2. Click Backup Job > VMware or vCloud on the ribbon. Veeam Backup & Replication will launch the
New Backup Job wizard.

3. At the Name step of the wizard, specify a name and description for the backup job.

4. At the Virtual Machines step of the wizard, select VMs whose disks are hosted on the storage system.

5. At the Storage step of the wizard, from the Backup repository list select a backup repository where
you want to store backup files.

6. In the Retention policy section, specify the number of backup restore points that you want to keep.

7. Select the Configure secondary destinations for this job check box.

8. At the Secondary Target step of the wizard, click Add and select primary or secondary storage arrays
to create snapshots.

97 | Veeam Backup & Replication | Integration with Storage Systems |

9. In the Number of snapshot copies to retain field, specify the number of storage snapshots that you
want to maintain in the snapshot chain. When this number is exceeded, Veeam Backup & Replication will
trigger the storage system to remove the earliest snapshot from the snapshot chain.

NOTE:
The number of snapshots in the snapshot chain on the primary storage array cannot be fewer than 1.

This option is not applicable to NetApp SnapMirror and HPE 3PAR StoreServ Peer Persistence. On these
secondary storage systems, Veeam Backup & Replication maintains the same number of storage
snapshots as on primary storage arrays.
If you use SnapMirror relationships between QTrees, you can define different retention policy settings for
the primary NetApp storage system and NetApp SnapMirror. For example, you can configure the backup
job to maintain 14 snapshots on the primary NetApp storage system and 10 snapshots of QTree
directories on NetApp SnapMirror.

10. Specify other backup job settings as required.

11. Click Next, then click Finish to save the job settings.

98 | Veeam Backup & Replication | Integration with Storage Systems |

Veeam Explorer for Storage Snapshots
Veeam Explorer for Storage Snapshots is a technology in Veeam Backup & Replication that lets you restore
VMware VM data directly from native storage snapshots. Veeam Explorer for Storage Snapshots automates the
process of data recovery for VMs hosted on storage systems, eliminates intermediate restore and manual
operations. As a result, you can restore necessary VM data from storage snapshots in seconds.

You can use Veeam Explorer for Storage Snapshots to perform the following restore operations:

 Instant VM Recovery

 VM guest OS files restore (Microsoft Windows and multi-OS restore)

 Restore of Microsoft Active Directory objects

 Restore of Microsoft Exchange objects

 Restore of Microsoft SharePoint objects

 Restore of Microsoft SQL Server databases

 Restore of Oracle databases

99 | Veeam Backup & Replication | Integration with Storage Systems |

Traditional Restore vs. Restore from Storage
Snapshots
Many organizations use storage snapshots for data protection. Storage snapshots allow for very low RPO: they
have minimal impact on storage performance and can be created in seconds. Administrators can schedule
snapshots to be created several times a day or even every hour.

In virtual environments, restore from storage snapshots can be difficult. Storage snapshots are created per-
volume, and a volume typically hosts disks of several VMs. For this reason, restore from storage snapshots is not
a simple rollback operation — it is a multi-task process. When an administrator restores a VM from the storage
snapshot manually, he/she needs to perform the following actions:

1. Present a storage snapshot to an ESX(i) host.

2. Perform an HBA rescan.

3. Mount the storage snapshot to an ESX(i) host.

4. Browse the storage snapshot to locate VM files.

5. Add the VM to the inventory or copy VM files to another VMFS datastore.

6. Power on the VM.

7. Perform restore operations.

8. Perform cleanup operations after VM data restore is complete.

As a result, the restore process takes much time. If you need to restore guest OS files and application objects
from a VM on the storage snapshot, the procedure will be even more complicated.

Veeam Explorer for Storage Snapshots fully automates operations of mounting storage snapshots to ESX(i) hosts.
You only need to select an ESX(i) host to which the storage snapshot will be mounted, and Veeam Explorer for
Storage Snapshots will perform all other operations automatically.

Veeam Explorer for Storage Snapshots does not convert storage snapshots into backups. It uses them “as is” and
lets you restore VM data directly from native storage system snapshots. You do not have to install any agents or
perform additional configuration actions.

100 | Veeam Backup & Replication | Integration with Storage Systems |

How Restore from Storage Snapshots Works
For restore operations, Veeam Backup & Replication uses a copy of the volume snapshot, not the volume
snapshot itself.

The volume snapshot copy is a read-write clone of the volume snapshot. The volume snapshot copy protects the
VMFS volume metadata integrity on the volume snapshot. During file-level restore and Instant VM Recovery, the
ESX(i) host to which the volume snapshot is mounted updates VMFS metadata on the volume snapshot. Use of
the volume snapshot copy helps protect the volume snapshot from these changes.

When you restore VM data from storage snapshots, Veeam Backup & Replication performs the following actions:

1. The user starts the restore process for some VM on the storage snapshot.

2. Veeam Backup & Replication triggers the storage system to create a copy or a clone of this storage
snapshot.

 If you restore several VMs from one storage snapshot, Veeam Backup & Replication does not
create several snapshot copies. Instead, it uses one snapshot copy for restore.

 If you start several restore operations (for example, Instant VM Recovery and VM guest OS
restore) for the same VM from the storage snapshot, Veeam Backup & Replication creates
several snapshot copies and works with them during restore.

3. The user selects an ESX(i) host in the virtual environment, and the created snapshot copy is presented to
this ESX(i) host as a new volume. The ESX(i) host is added to the list of Allowed Servers for the snapshot
copy. As a result, the ESX(i) host has access to the snapshot copy and can read and write data to/from
it.

4. Veeam Backup & Replication makes sure that the IP address of the storage system is in the list of static
targets on the ESX(i) host.

5. The storage system issues an HBA re-scan command to the vCenter Server. Once rescan is finished, the
snapshot copy appears in the discovered targets list on the ESX(i) host. After that, the storage system
performs re-signature for storage volumes.

6. The user performs necessary restore operations in the Veeam Backup & Replication console.

7. After restore is completed, Veeam Backup & Replication issues a command to the storage system. The
storage system deletes the snapshot copy from the ESX(i) host and performs cleanup operations.

101 | Veeam Backup & Replication | Integration with Storage Systems |

Creating and Deleting Snapshots
You can create and delete storage snapshots in the Veeam Backup & Replication console. The create/delete
snapshot operations do not differ from the create/delete snapshot operations that you perform in the
management console of the storage system.

To create a volume snapshot:

1. Open the Storage Infrastructure view.

2. In the inventory pane, expand the storage system tree.

3. Right-click the necessary volume and select Create Snapshot.

4. In the New Storage Snapshot window, specify a name for the created snapshot and provide a
description for the snapshot (if the snapshot description field is available).

5. [For HPE StoreVirtual] To quiesce VMs on the volume, select the Create application-managed
snapshot check box. The storage system will trigger a command to VMware vCenter Server to quiesce
VMs with VMware Tools. VM quiescence will bring VM data to a consistent state before the snapshot is
taken. If the Create application-managed snapshot option is not enabled,
Veeam Backup & Replication will trigger a point-in-time snapshot.

NOTE:
To create application-managed snapshots on HPE StoreVirtual, make sure that Application Aware Snapshot
Manager is properly installed and configured. If the Application Aware Snapshot Manager is not installed,
Veeam Backup & Replication will report an error, and the snapshot will not be created. For more information,
see HPE StoreVirtual Application-Aware Snapshot Manager Deployment Guide at
https://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=4118659&docId=emr_na-
c03983695&docLocale=en_US.

To delete a volume snapshot:

102 | Veeam Backup & Replication | Integration with Storage Systems |

1. Open the Storage Infrastructure view.

2. In the inventory pane, expand the storage system tree.

3. Right-click the necessary snapshot and select Delete snapshot.

103 | Veeam Backup & Replication | Integration with Storage Systems |

Performing Instant VM Recovery
You can instantly recover a VM from a storage snapshot without prior de-staging and intermediate restores.
Instant VM Recovery accelerates VM restore, improves RTOs and decreases downtime of production VMs.

Before performing Instant VM Recovery, check prerequisites. Then use the Instant Recovery wizard to restore
a VM from a storage snapshot.

Before You Begin

Before you perform Instant VM Recovery, check the following prerequisites:

 If you are recovering a VM to the production network, make sure that the original VM is powered off to
avoid conflicts.

 You must add the storage system to the backup infrastructure.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 [For storage systems working over Fibre Channel] To let Veeam Backup & Replication present snapshots
of LUNs to an ESX(i) host, you must register the ESX(i) host with a WWN ID on the storage system.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses
on the storage system.

104 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch Instant Recovery Wizard
To launch the Instant Recovery wizard, do one of the following:

 On the Home tab, click Restore and select VMware vSphere backup. In the Restore from backup
section, select Instant VM recovery.

 Open the Storage Infrastructure view. In the inventory pane, expand the storage system tree and
select the necessary volume snapshot. In the working area, select a VM that you want to restore and
click Instant VM Recovery on the ribbon. You can also right-click a VM and select Instant VM
recovery. In this case, you will pass immediately to the Recovery Mode step of the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM that you want to restore and click Instant VM Recovery on the
ribbon. You can also right-click a VM and select Instant VM recovery. In this case, you will pass
immediately to the Restore Point step of the wizard.

To quickly find a VM, you can use the search field at the top of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

105 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, select a VM that you want to restore.

1. In the VM to recover list, expand the necessary volume snapshot.

2. Select the VM.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

106 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point for the VM. Every storage snapshot acts as an
independent restore point.

107 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Select Recovery Mode
At the Recovery Mode step of the wizard, choose the restore mode:

 Select Restore to the original location if you want to restore the VM with its initial settings to its
original location. If you select this option, you will pass directly to the Restore Reason step of the wizard.

 Select Restore to a new location, or with different settings if you want to restore the VM to a
different location and/or with different settings. If you select this option, the Instant Recovery wizard
will include additional steps for customizing VM settings.

108 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Select Destination for Recovered VM
The Destination step of the wizard is available if you have chosen to change a location and settings of the
recovered VM.

Select a destination for the recovered VM:

1. In the Host field, specify a host on which the VM must run. Veeam Backup & Replication will create a
clone/virtual copy of the storage snapshot, mount it to the selected ESX(i) host and start the VM on this
ESX(i) host.

2. In the VM folder field, select a folder to which you want to place the recovered VM.

3. In the Restored VM name field, enter a name under which the recovered VM must be registered. By
default, Veeam Backup & Replication uses the original name of the VM. If you are restoring the VM to
the same ESX(i) host or same datacenter where the original VM is registered, and the original VM still
resides there, it is recommended that you change the VM name to avoid conflicts.

4. In the Resource pool list, select a resource pool to which you want to place the recovered VM.

109 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Specify Restore Reason
At the Restore Reason step of the wizard, enter a reason for performing Instant VM Recovery. The information
you provide will be saved in the session history, and you will be able to view it later.

110 | Veeam Backup & Replication | Integration with Storage Systems |

Step 7. Verify Instant VM Recovery Settings
At the Ready to Apply step of the wizard, specify additional settings for Instant VM Recovery:

1. If you are recovering a production VM that has failed and want to connect the recovered VM to a
network upon restore, select the Connect VM to network check box. If you are recovering a VM for
testing disaster recovery and the original VM is still running, leave this check box not selected. Before
you power on the VM, you will have to manually change VM network configuration: disconnect it from
the production network and connect it to an isolated non-production network to avoid conflicts.

2. To start the VM immediately after recovery, select the Power on VM automatically check box. If you
are recovering the VM to the production network, make sure that the original VM is powered off to avoid
conflicts.

3. Check Instant VM Recovery settings and click Next. Veeam Backup & Replication will restore the VM on
the selected ESX(i) host.

111 | Veeam Backup & Replication | Integration with Storage Systems |

Step 8. Finalize Instant VM Recovery
All currently running Instant VM Recovery sessions are displayed in the Home view, under the Restore >
Instant Recovery node.

To check the progress of an Instant VM Recovery session and view session details:

1. Open the Home view.

2. In the inventory pane, select Instant Recovery.

3. In the working area, right-click the session and select Properties. You can also double-click the session
in the working area.

After the VM is successfully recovered, you can finalize Instant VM Recovery in two ways:

 Migrate the restored VM to the production environment

 Unpublish the recovered VM

Migrating Instantly Restored VMs

To migrate the recovered VM to the production environment:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

3. In the working area, right-click the Instant VM Recovery session and select Migrate to production.
Veeam Backup & Replication will launch the Quick Migration wizard. During migration,
Veeam Backup & Replication will restore the VM from the storage snapshot and then additionally move
changes that were made while the VM was running in the Instant Recovery mode.

112 | Veeam Backup & Replication | Integration with Storage Systems |

Unpublishing Instantly Restored VMs
To unpublish the recovered VM:

1. Open the Home view.

2. In the inventory pane, select the Instant Recovery node.

3. In the working area, right-click the session and select Stop publishing.

You can also unpublish the VM using the History view:

1. Open the History view.

2. In the inventory pane, Instant VM recovery node under Restore.

3. In the working area, right-click the session and select Stop session.

113 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring VM Guest OS Files (Microsoft
Windows)
You can restore VM guest OS files from a storage snapshot. Veeam Backup & Replication supports file-level
restore for the following Microsoft Windows file systems:

 FAT

 NTFS

 ReFS

When you perform guest OS file restore, you select an ESX(i) host in the virtual environment.
Veeam Backup & Replication creates a clone/virtual copy of the storage snapshot on which the VM disks are
hosted, and mounts the clone/virtual copy to the selected ESX(i) host as a new LUN/volume.

Veeam Backup & Replication accesses the configuration file of the VM (VMX) on the mounted clone/virtual copy
and uses this configuration file to register a temporary VM on the ESX(i) host. Disks of the restored VM are
mounted to this temporary VM. After disks are mounted, you can copy VM guest OS files and folders to their
original location, local machine drive or save them in a network shared folder.

Before you start file-level restore, check prerequisites. Then use the File Level Restore wizard to restore VM
guest OS files and folders.

Before You Begin

Before you restore VM guest OS files from storage snapshots, check the following prerequisites:

 You must add the storage system to the backup infrastructure.

 If you plan to restore VM guest OS files to their original location, you must make sure that VMware Tools
are installed on the target VM.

 If you plan to restore guest OS files from a VM running Microsoft Windows ReFS, the
Veeam Backup & Replication console must be installed on a machine running Microsoft Windows Server
2012 and later.

 If you plan to restore files from a VM running Microsoft Windows Server 2012 R2 and later, and Data
Deduplication is enabled for some VM volumes, the Veeam Backup & Replication console must be
installed on a machine running Microsoft Windows Server 2012 and later. Data Deduplication must be
enabled on this machine.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 [For storage systems working over Fibre Channel] To let Veeam Backup & Replication present snapshots
of LUNs to the ESX(i) host, you must register the ESX(i) host with a WWN ID on the storage system.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses
on the storage system.

114 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch File Level Restore Wizard
To launch the File Level Restore wizard, do one of the following:

 On the Home tab, click Restore and select VMware vSphere backup. In the Restore from backup
section, select Guest files (Windows).

 Open the Storage Infrastructure view. In the inventory pane, select the necessary volume snapshot.
In the working area, select a VM whose guest OS files you want to restore and click Guest Files >
Microsoft Windows on the ribbon. You can also right-click a VM and select Restore guest files >
Microsoft Windows. In this case, you will pass immediately to the Location step of the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM whose guest OS files you want to restore and click Guest Files >
Microsoft Windows on the ribbon. You can also right-click a VM and select Restore guest files >
Microsoft Windows. In this case, you will pass immediately to the Restore Point step of the wizard.

To quickly find the necessary VM, you can use the search field at the top of the window. Enter a VM name or a
part of it and click the Start search button on the right or press [ENTER].

115 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, select a VM whose guest OS files you want to restore.

1. In the VM to recover list, expand the necessary volume snapshot.

2. Select the VM.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

116 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point for the VM. Every storage snapshot acts as an
independent restore point.

117 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Select ESX(i) Host for Snapshot Mounting
At the Location step of the wizard, select an ESX(i) host to which the clone/virtual copy of the storage snapshot
will be mounted. On the selected ESX(i) host, Veeam Backup & Replication will create a temporary VM and
mount disks of the restored VM to this temporary VM.

To specify destination for a snapshot clone/virtual copy and temporary VM:

1. At the Location step of the wizard, click Customize.

2. Next to the Host field, click Choose and select an ESX(i) host to which the snapshot clone/virtual copy
must be mounted and on which the temporary VM must be created.

3. Next to the Resource pool field, click Choose and select a resource pool to which you want to place
the temporary VM.

4. Next to the VM folder field, click Choose and select a folder to which you want to place the temporary
VM.

5. Click OK.

118 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Specify Restore Reason
At the Reason step of the wizard, enter a reason for performing VM guest OS files restore. The information you
provide will be saved in the session history, and you will be able to view it later.

TIP:

If you do not want to display the Reason step of the wizard in future, select the Do not show me this
page again check box.

Step 6. Save Restored Files

At the Summary step of the wizard, click Finish to start the restore process.

After the restore process is complete, Veeam Backup & Replication will open the Veeam Backup browser
displaying the file system tree of the restored VM. Note that names of the restored VM hard disks may differ from
the original ones.

You can perform the following operations with VM guest OS files in the Veeam Backup browser:

 Restore files and folders to the original location

 Save files and folders to a folder on the backup server or in network shared folder

 Launch Veeam Explorers for application item restore

 Open files in Microsoft Windows Explorer

After the restore process is complete, close the Veeam Backup browser.

119 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Files to Original Location
To restore files or folders to their original location, in the Veeam Backup browser right-click a file or folder and
select one of the following commands:

 To overwrite the original file on the VM guest OS with the file restored from the backup, select Restore
> Overwrite.

 To save the file restored from the backup next to the original file, select Restore > Keep.
Veeam Backup & Replication will add the RESTORED- prefix to the original file name and save the
restored file in the same location where the original file resides.

120 | Veeam Backup & Replication | Integration with Storage Systems |

Saving Files to New Location
To save restored files or folders to a folder on the backup server or in a network shared folder, in the Veeam
Backup browser right-click a file or folder and select Copy To and select a location to which the file or folder must
be copied.

When restoring file objects, you can choose to preserve original NTFS permissions:

 Select the Preserve permissions and ownership check box to keep original ownership and security
permissions for restored objects. Veeam Backup & Replication will copy files and folders with associated
Access Control Lists and preserve granular access settings.

 Leave the Preserve permissions and ownership check box not selected if you do not want to
preserve original ownership and access settings for restored objects. Veeam Backup & Replication will
change security settings: the user who launched the Veeam Backup & Replication console will be set as
the owner of restored objects. Access permissions will be inherited from a folder to which restored
objects are saved.

121 | Veeam Backup & Replication | Integration with Storage Systems |

Launching Veeam Explorers
If you are restoring VM guest OS files of the virtualized Microsoft Active Directory Server, Microsoft Exchange
Server, Microsoft SharePoint Server, Microsoft SQL Server, you can launch Veeam Explorer for the necessary
application directly from the Veeam Backup browser.

 To start Veeam Explorer for Microsoft Active Directory, browse to the Microsoft Active Directory database
file (DIT) in the Veeam Backup browser, select it and click Application Items > Active Directory
Items on the Home tab or double-click the DIT file.

 To start Veeam Explorer for Microsoft Exchange, browse to the Microsoft Exchange database file (EDB) in
the Veeam Backup browser, select it and click Application Items > Exchange Items on the Home
tab or double-click the EDB file.

 To start Veeam Explorer for Microsoft SharePoint, browse to the Microsoft SharePoint content database
(MDF) in the Veeam Backup browser, select it and click Application Items > SharePoint Items on
the Home tab or double-click the MDF file.

 To start Veeam Explorer for Microsoft SQL Server, browse to the Microsoft SQL Server database file in
the Veeam Backup browser, select it and click Application Items > SQL Server Databases on the
Home tab or double-click the Microsoft SQL Server database file. For more information, see
http://technet.microsoft.com/en-us/library/ms143547.aspx.

Working with Windows Explorer

You can use Microsoft Windows Explorer to work with restored files and folders.

To open Microsoft Windows Explorer:

1. In the Veeam Backup browser, click Explore on the ribbon or right-click the necessary folder and select
Explore.

2. Veeam Backup & Replication will launch Microsoft Windows Explorer. Browse to the necessary VM guest
OS files.

You can also start Microsoft Windows Explorer from the Start menu of Microsoft Windows and browse to the
necessary VM guest OS files. VM disks are mounted under the C:\veeamflr\<vmname>\<volume n> folder
on the backup server.

Closing Veeam Backup Browser

You can browse restored files and folders only while the Veeam Backup browser is open. After the Veeam Backup
browser is closed, Veeam Backup & Replication unmounts VM disks from the temporary VM.

It is recommended that you close the Veeam Backup browser after you finish restoring files and folders.

Veeam Backup & Replication checks if there is any activity in the Veeam Backup browser every 5 minutes. If the
user or Veeam Backup & Replication components and services do not perform any actions for 30 minutes,
Veeam Backup & Replication displays a warning notifying that the Veeam Backup browser will be closed in 5
minutes.

After the warning is displayed, you can perform one of the following actions:

 You can close the Veeam Backup browser manually.

 You can click Cancel to postpone the close operation. The Veeam Backup browser will remain open for 5
minutes. After this period expires, Veeam Backup & Replication will display the warning again.

 You can perform no action. The Veeam Backup browser will be automatically closed in 5 minutes.

122 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring VM Guest OS Files (Linux, Unix and
Other)
You can restore VM guest OS files from a storage snapshot. Veeam Backup & Replication supports file-level
restore for the most commonly used file systems on Linux, Solaris, BSD, Unix and Micro Focus OES.

When you perform VM guest OS file restore, you select an ESX(i) host in your virtual environment.
Veeam Backup & Replication creates a clone/virtual copy of the storage snapshot on which the VM disks are
hosted, and mounts the clone/virtual copy to the selected ESX(i) host as a new LUN/volume.

Veeam Backup & Replication copies an ISO of the proxy appliance, a helper VM, to the mounted clone/virtual
copy. The proxy appliance is rather small, around 50 MB. It requires 1024 MB RAM and takes 10-20 seconds to
boot. Veeam Backup & Replication automatically starts the proxy appliance on the ESX(i) host and mounts disks
of the restored VM to the proxy appliance as virtual hard drives. VMDK files are mounted directly from storage
snapshots. After disks are mounted, you can copy necessary VM guest OS files and folders to their initial location,
local machine drive or save them in a network shared folder.

Before you start file-level restore, check prerequisites. Then use the File Level Restore wizard to restore VM
guest OS files and folders.

Before You Begin

Before you restore VM guest OS files from storage snapshots, check the following prerequisites:

 You must add the storage system to the backup infrastructure.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 If you plan to restore VM guest OS files to their original location, make sure that VMware Tools must be
installed on the target VM.

 Veeam Backup & Replication restores ACL for recovered VM guest OS files. To let
Veeam Backup & Replication detect the target Linux system architecture and kernel version, make sure
that the following utilities are installed on the VM guest OS: arch and uname.

 Veeam Backup & Replication must have access to the guest OS of the target VM to be able to deploy a
coordination process. The coordination process performs a number of administrative actions on the
target VM guest OS, for example, collects information about mount points.

 [For Linux/Unix-based target VM] Veeam Backup & Replication uses the SSH protocol to communicate
with the target Linux/Unix VM and requires the SCP utility on the target VM. Make sure that the SSH
daemon is properly configured and SCP utility is available on the target VM.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses
on the storage system.

123 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch File Level Restore Wizard
To launch the File Level Restore wizard, do one of the following:

 On the Home tab, click Restore and select VMware vSphere backup. In the Restore from backup
section, select Guest files (other OS).

 Open the Storage Infrastructure view. In the inventory pane, select the necessary volume snapshot.
In the working area, select a VM whose guest OS files you want to restore and click Guest Files >
Linux and other on the ribbon. You can also right-click a VM and select Restore guest files > Linux
and other. In this case, you will pass immediately to the Restore Point step of the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM whose guest OS files you want to restore and click Guest Files >
Linux and other on the ribbon. You can also right-click a VM and select Restore guest files > Linux
and other. In this case, you will pass immediately to the Restore Point step of the wizard.

To quickly find a VM, you can use the search field at the top of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

124 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, select a VM whose guest OS files you want to restore.

1. In the Virtual machine list, expand the necessary volume snapshot.

2. Select the VM.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

125 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point for the VM. Every storage snapshot acts as an
independent restore point.

126 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Specify Restore Reason
At the Reason step of the wizard, enter a reason for performing VM guest OS files restore. The information you
provide will be saved in the session history, and you will be able to view it later.

Step 5. Select Location for Proxy Appliance

At the Ready step of the wizard, select an ESX(i) host to which the clone/virtual copy of the storage snapshot
will be mounted. On the selected ESX(i) host, Veeam Backup & Replication will also place a proxy appliance and
mount disks of the restored VM to this proxy appliance.

To specify a destination for the snapshot clone/virtual copy and proxy appliance:

1. Click the Customize link at the bottom of the window.

2. In the FLR Appliance Configuration window, select an ESX(i) host to which the snapshot clone must
be mounted and on which the proxy appliance must be registered.

3. In the Resource pool field, specify a resource pool to which you want to place the proxy appliance.

4. In the Network section, specify an IP address and other network settings for the proxy appliance. The
proxy appliance must be placed in the same network where the backup server resides.

5. To enable FTP access to the restored file system, select the Enable FTP server on appliance check
box. As a result, your users will be able to access the proxy appliance via FTP, browse the file system of
the restored VM and download files on their own.

6. If you are restoring a VM with the Novell Storage Services file system, select the Restore from Novell
Storage Services (NSS) file system check box. Veeam Backup & Replication will deploy a specific
proxy appliance that supports the Novell Storage Services file system.

127 | Veeam Backup & Replication | Integration with Storage Systems |

7. Click OK.

IMPORTANT!
When choosing an ESX(i) host for the proxy appliance used for file-level restore from the Novell Storage
Services file system, make sure that it allows running VMs with 64-bit guest OSes.

128 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Start Restore Process
At the Restore step of the wizard, check the progress of the restore process. The file-level restore appliance
may take about 10-20 seconds to boot.

Step 7. Save Restored Files

When the restore process is complete, Veeam Backup & Replication opens the Veeam Backup browser displaying
the file system tree of the restored VM.

You can restore files and folders to their original location, new location or access files on FTP.

NOTE:
You can browse to the VM guest OS files and access restored files on the FTP only while the Veeam Backup
browser is open. After the Veeam Backup browser is closed, Veeam Backup & Replication will unmount VM
disks from the proxy appliance, remove the proxy appliance and unmount the storage snapshot from the
ESX(i) host (unless this storage snapshot is used by other restore operations).

129 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Files to Original Location
To restore files and folders to the original location, in the Veeam Backup browser right-click a file or folder and
select one of the following commands:

 To overwrite the original file on the VM guest OS with the file restored from the backup, select Restore
> Overwrite.

To access the target VM guest OS and restore files to the original location, Veeam Backup & Replication uses an
account specified in the backup job settings. If this account does not have sufficient rights to access the target
VM guest OS, you will be prompted to enter credentials. In the Credentials window, specify a user account to
access the destination location (server or shared folder). You can use the account under which you are currently
logged on or a different account.

In some cases, you may remove the original VM and restore it from the backup by the time of file-level restore.
If you then attempt to restore VM guest OS files to the original location, Veeam Backup & Replication will not be
able to find the original VM by its reference ID, and display a warning. Click OK and browse to the target VM in
the virtual infrastructure to which you want to restore VM guest OS files.

130 | Veeam Backup & Replication | Integration with Storage Systems |

Saving Files to New Location
To save files and folders to a new location:

1. In the Veeam Backup browser, right-click the necessary file or folder and select Copy to.

2. In the Select Destination window, select a destination server (local or remote) from the list or provide
a path to a shared folder.

 If you are recovering files to a Linux server, you can select the destination server from the list
or add the destination server ad-hoc. To add a destination server ad-hoc, scroll down the list of
servers and choose Specify a different host at the end of the list. Follow the steps of the
wizard to add a Linux server that will be used as the destination server.
The server you add ad-hoc will not appear in the list of managed hosts in
Veeam Backup & Replication: its purpose is to host files that you recover. The added server will
only remain visible in the Veeam Backup browser until all currently active file-level restore
sessions are completed.

 If you are recovering files to a shared folder, specify a path to the destination folder.

3. If you want to preserve original permissions and ownership for recovered files, select the Preserve
permissions and ownership check box.

4. After you click Restore, you may need to specify credentials to access the destination location. If
prompted, in the Credentials window specify the user account to access the target server or shared
folder. You can use the account under which you are currently logged on or a different account.

IMPORTANT!
If you plan to keep original permissions and ownership settings of restored files and folders, the account you
specify must have privileges to change the owner on the target server or in the shared folder.

131 | Veeam Backup & Replication | Integration with Storage Systems |

Accessing Files over FTP
If you have chosen to enable an FTP server on the FLR appliance, the restored file system will also be available
over FTP at ftp://<FLR_appliance_IP_address>. Users in the same network can access the FLR appliance and
restore files they need on their own.

132 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Application Items from Microsoft Active
Directory
Veeam Backup & Replication integrates with Veeam Explorer for Microsoft Active Directory. Veeam Explorer for
Microsoft Active Directory lets you browse Microsoft Active Directory databases in VMs located on storage
snapshots and restore Microsoft Active Directory items (objects and containers) and their attributes back to the
production Microsoft Active Directory database.

Before you start working with Veeam Explorer for Microsoft Active Directory, you need to extract a Microsoft
Active Directory database from the storage snapshot. You can do it in two ways:

 You can use the Microsoft Active Directory Object Restore wizard. In this case,
Veeam Backup & Replication will automatically extract a Microsoft Active Directory database from the
storage snapshot and open it in Veeam Explorer for Microsoft Active Directory. For more information, see
Using Microsoft Active Directory Object Restore Wizard.

 You can restore VM guest OS files from a backup of a virtualized Microsoft Active Directory server,
manually locate a Microsoft Active Directory database and open it in Veeam Explorer for Microsoft Active
Directory. For more information, see Opening Microsoft Active Directory Database Manually.

Using Microsoft Active Directory Object Restore Wizard

When you run the Microsoft Active Directory Object Restore wizard, Veeam Backup & Replication
automatically extracts the Microsoft Active Directory database from the storage snapshot and opens it in Veeam
Explorer for Microsoft Active Directory.

As part of this procedure, Veeam Backup & Replication performs the following actions:

1. Veeam Backup & Replication creates a clone/virtual copy of the storage snapshot and mounts the
clone/virtual copy to an ESX(i) host.

2. Veeam Backup & Replication accesses the configuration file of the virtualized Microsoft Active Directory
server (VMX) on the snapshot clone/virtual copy and uses this configuration file to register a temporary
VM on the ESX(i) host.

3. Veeam Backup & Replication mounts disks of the Microsoft Active Directory server to the temporary VM.

4. Veeam Backup & Replication locates the Microsoft Active Directory database and opens it in Veeam
Explorer for Microsoft Active Directory.

133 | Veeam Backup & Replication | Integration with Storage Systems |

Before You Begin
Before you restore application items from storage snapshots, check the following prerequisites:

 You must add the storage system to the backup infrastructure.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses
on the storage system.

134 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch Microsoft Active Directory Object Restore Wizard
To launch the Microsoft Active Directory Restore wizard, do one of the following:

 On the Home tab, click Restore and select VMware vSphere backup. In the Restore from backup
section, select Application items and click Next. At the Select Application step of the wizard, select
Microsoft Active Directory.

 Open the Storage Infrastructure view. In the inventory pane, select the necessary volume snapshot.
In the working area, select a VM running Microsoft Active Directory and click Application Items >
Microsoft Active Directory on the ribbon. You can also right-click the VM and select Restore
application items > Microsoft Active Directory objects. In this case, you will pass immediately to
the Location step of the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM running Microsoft Active Directory and click Application Items >
Microsoft Active Directory on the ribbon. You can also right-click the VM and select Restore
application items > Microsoft Active Directory objects. In this case, you will pass immediately to
the Restore Point step of the wizard.

To quickly find a VM, you can use the search field at the top of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

135 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, Veeam Backup & Replication displays all Microsoft Active Directory
VMs whose disks are located on the storage system. Select the necessary VM from the list. If the necessary VM is
not displayed in the list, select the Show all VMs check box. Veeam Backup & Replication will display all VMs
whose disks are located on the storage system.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

136 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point from which you want to restore a Microsoft
Active Directory database. Every storage snapshot acts as an independent restore point.

137 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Select ESX(i) Host for Snapshot Mounting
At the Location step of the wizard, select an ESX(i) host to which the clone/virtual copy of the storage snapshot
must be mounted. On the selected ESX(i) host, Veeam Backup & Replication will create a temporary VM and
mount disks of the virtualized Microsoft Active Directory to this temporary VM.

To specify a destination for the snapshot clone/virtual copy and temporary VM:

1. At the Location step of the wizard, click Customize.

2. Next to the Host field, click Choose and select an ESX(i) host to which the snapshot clone/virtual copy
must be mounted and on which the temporary VM must be created.

3. Next to the Resource pool field, click Choose and select a resource pool to which you want to place
the temporary VM.

4. Next to the Folder field, click Choose and select a folder to which you want to place the temporary VM.

5. Click OK.

138 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Specify Restore Reason
At the Reason step of the wizard, enter a reason for restoring a Microsoft Active Directory database. The
information you provide will be saved in the session history, and you will be able to view it later.

TIP:

If you do not want to display the Reason step of the wizard in future, select the Do not show me this
page again check box.

139 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Open Database in Veeam Explorer for Microsoft Active Directory
At the Summary step of the wizard, click Finish to start the restore process.

Veeam Backup & Replication will automatically locate a Microsoft Active Directory database and open it in Veeam
Explorer for Microsoft Active Directory. You can browse the database and restore items that you need.

Detailed information about Veeam Explorer for Microsoft Active Directory is provided in documentation for Veeam
Explorer for Microsoft Active Directory. To access the documentation, do one of the following:

 Open Veeam Explorer for Microsoft Active Directory and press [F1].

 From the main menu of Veeam Explorer for Microsoft Active Directory, select Help > Online Help.

Opening Microsoft Active Directory Database Manually

If Veeam Backup & Replication fails to locate a Microsoft Active Directory database automatically for some
reason, you can use the file-level restore functionality to restore a Microsoft Active Directory database from the
storage snapshot. You can then open the database in Veeam Explorer for Microsoft Active Directory.

To restore application items from Microsoft Active Directory:

1. Restore VM guest OS files from a backup of a virtualized Microsoft Active Directory server. For more
information, see Restoring VM Guest OS Files (Microsoft Windows).

2. In the Veeam Backup browser, locate a Microsoft Active Directory database file (NTDS.dit) and double-
click it or select the NTDS.dit file and click Application Items > Active Directory Items on the
ribbon.

Veeam Backup & Replication will open the database in Veeam Explorer for Microsoft Active Directory. After that,
you can browse the database and restore Microsoft Active Directory objects.

140 | Veeam Backup & Replication | Integration with Storage Systems |

 Open Veeam Explorer for Microsoft Active Directory and press [F1].

 Open Veeam Explorer for Microsoft Active Directory. From the main menu of Veeam Explorer for
Microsoft Active Directory, select Help > Online Help.

141 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Application Items from Microsoft
Exchange
Veeam Backup & Replication integrates with Veeam Explorer for Microsoft Exchange. Veeam Explorer for
Microsoft Exchange lets you browse Microsoft Exchange mailbox stores in VMs located on storage snapshots and
restore Microsoft Exchange items that you need.

Before you start working with Veeam Explorer for Microsoft Exchange, you need to extract a Microsoft Exchange
database (EDB file) from the storage snapshot. You can do it in two ways:

 You can use the Microsoft Exchange Item Level Restore wizard. In this case,
Veeam Backup & Replication will automatically extract a Microsoft Exchange database from the storage
snapshot and open it in Veeam Explorer for Microsoft Exchange. For more information, see Using the
Microsoft Exchange Item Level Restore Wizard.

 You can restore VM guest OS files from a backup of a virtualized Microsoft Exchange server, manually
locate a Microsoft Exchange database and open it in Veeam Explorer for Microsoft Exchange. For more
information, see Opening Microsoft Exchange Database Manually.

Using the Microsoft Exchange Item Level Restore Wizard

When you run the Microsoft Exchange Item Level Restore wizard, Veeam Backup & Replication
automatically extracts a Microsoft Exchange database (EDB file) from the storage snapshot and opens it in
Veeam Explorer for Microsoft Exchange.

As part of this procedure, Veeam Backup & Replication performs the following steps:

1. Veeam Backup & Replication creates a clone/virtual copy of the storage snapshot and mounts the
clone/virtual copy to an ESX(i) host.

2. Veeam Backup & Replication accesses the configuration file of the virtualized Microsoft Exchange server
(VMX) on the snapshot clone/virtual copy and uses this configuration file to register a temporary VM on
the ESX(i) host.

3. Veeam Backup & Replication mounts disks of the Microsoft Exchange server to the temporary VM.

4. Veeam Backup & Replication scans the Microsoft Exchange Event log to locate the EDB file and ese.dll
file on mounted disks. The ese.dll file is required for configuring Veeam Explorer for Microsoft
Exchange.

5. Veeam Backup & Replication opens the EDB file in Veeam Explorer for Microsoft Exchange, and you can
browse it to find necessary items.

Before You Begin

Before you restore application items from storage snapshots, check the following prerequisites:

 You must add the storage system to the backup infrastructure.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses

142 | Veeam Backup & Replication | Integration with Storage Systems |

on the storage system.

Step 1. Launch Microsoft Exchange Item Level Restore Wizard

To launch the Microsoft Exchange Item Level Restore wizard, do one of the following:

 Open the Storage Infrastructure view. In the inventory pane, select the necessary volume snapshot.
In the working area, select a VM running Microsoft Exchange and click Application Items > Microsoft
Exchange on the ribbon. You can also right-click the VM and select Restore application items >
Microsoft Exchange mailbox items. In this case, you will pass immediately to the Location step of
the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM running Microsoft Exchange and click Application Items >
Microsoft Exchange on the ribbon. You can also right-click the VM and select Restore application
items > Microsoft Exchange mailbox items. In this case, you will pass immediately to the Restore
Point step of the wizard.

To quickly find the necessary VM, you can use the search field at the top of the window. Enter a VM name or a
part of it and click the Start search button on the right or press [ENTER].

143 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, Veeam Backup & Replication displays all Microsoft Exchange VMs
with disks whose disks are located on the storage system. Select the necessary VM in the list. If the necessary
VM is not displayed in the list, select the Show all VMs check box. Veeam Backup & Replication will display all
VMs whose disks are located on the storage system.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

144 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point from which you want to recover a Microsoft
Exchange database. Every storage snapshot acts as an independent restore point.

145 | Veeam Backup & Replication | Integration with Storage Systems |

To specify a destination for the snapshot clone/virtual copy and temporary VM:

1. At the Location step of the wizard, click Customize.

2. Next to the Host field, click Choose and select an ESX(i) host to which the snapshot clone must be
mounted and on which the temporary VM must be created.

3. Next to the Resource pool field, click Choose and select a resource pool to which you want to place
the temporary VM.

4. Next to the Folder field, click Choose and select a folder to which you want to place the temporary VM.

5. Click OK.

146 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Specify Restore Reason
At the Reason step of the wizard, enter a reason for restoring data from Microsoft Exchange. The information
you provide will be saved in the session history, and you will be able to view it later.

TIP:

If you do not want to display the Reason step of the wizard in future, select the Do not show me this
page again check box.

147 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Open EDB File in Veeam Explorer for Exchange
At the Summary step of the wizard, click Finish to start the restore process.

Veeam Backup & Replication will automatically locate a Microsoft Exchange database and open it in Veeam
Explorer for Microsoft Exchange. You can browse the database and restore items that you need.

Detailed information about Veeam Explorer for Microsoft Exchange is provided in documentation for Veeam
Explorer for Microsoft Exchange. To access the documentation, do one of the following:

 Open Veeam Explorer for Microsoft Exchange and press [F1].

 From the main menu of Veeam Explorer for Microsoft Exchange, select Help > Online Help.

148 | Veeam Backup & Replication | Integration with Storage Systems |

Opening Microsoft Exchange Database Manually
If Veeam Backup & Replication fails to locate a Microsoft Exchange database automatically for some reason, you
can use the file-level restore functionality to restore a Microsoft Exchange database from the storage snapshot.
You can then open the database in Veeam Explorer for Microsoft Exchange.

To restore application items from Microsoft Exchange:

1. Restore VM guest OS files from a backup of a virtualized Microsoft Exchange server. For more
information, see Restoring VM Guest OS Files (Microsoft Windows).

2. In the Veeam Backup browser, locate an EDB file and double-click it or select the EDB file and click
Application Items > Exchange Items on the ribbon.

Veeam Backup & Replication will open the selected database in Veeam Explorer for Microsoft Exchange. After
that, you can browse the database and restore items that you need.

Detailed information about Veeam Explorer for Microsoft Exchange is provided in documentation for Veeam
Explorer for Microsoft Exchange. To access the documentation, do one of the following:

 Open Veeam Explorer for Microsoft Exchange and press [F1].

 Open Veeam Explorer for Microsoft Exchange. From the main menu of Veeam Explorer for Microsoft
Exchange, select Help > Online Help.

149 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Application Items from Microsoft
SharePoint
Veeam Backup & Replication integrates with Veeam Explorer for Microsoft SharePoint. Veeam Explorer for
Microsoft SharePoint lets you browse Microsoft SharePoint content databases in VMs located on storage
snapshots and restore documents, items and document libraries that you need.

Before you start working with Veeam Explorer for Microsoft SharePoint, you need to extract a Microsoft
SharePoint content database (MDF file) from the storage snapshot. To do this, you need to restore VM guest OS
files from a backup of the virtualized Microsoft SharePoint server, manually locate the content database and open
it in Veeam Explorer for Microsoft SharePoint.

To restore application items from Microsoft SharePoint:

1. Restore VM guest OS files from a backup of a virtualized Microsoft SharePoint server. For more
information, see Restoring VM Guest OS Files (Microsoft Windows).

2. In the Veeam Backup browser, locate the MDF file and double-click it or select the file and click
Application Items > SharePoint Items on the ribbon.

Veeam Backup & Replication will attach the content database to the Microsoft SQL Server on which the
Veeam Backup & Replication configuration database is deployed and open the database in Veeam Explorer for
Microsoft SharePoint. After that, you can browse the database and restore items that you need.

Detailed information about Veeam Explorer for Microsoft SharePoint is provided in documentation for Veeam
Explorer for Microsoft SharePoint. To open access the documentation, do one of the following:

 Open Veeam Explorer for Microsoft SharePoint and press [F1].

 From the main menu of Veeam Explorer for Microsoft SharePoint, select Help > Online Help.

150 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Databases from Microsoft SQL Server
Veeam Backup & Replication integrates with Veeam Explorer for Microsoft SQL Server. Veeam Explorer for
Microsoft SQL Server lets you browse Microsoft SQL Server databases in VMs located on storage snapshots and
restore Microsoft SQL Server databases.

Before you start working with Veeam Explorer for Microsoft SQL Server, you need to extract the Microsoft SQL
Server database from the storage snapshot. You can do it in two ways:

 You can use the Microsoft SQL Server Database Restore wizard. In this case,
Veeam Backup & Replication will automatically extract a Microsoft SQL Server database from the storage
snapshot and open it in Veeam Explorer for Microsoft SQL. For more information, see Using the Microsoft
SQL Server Database Restore Wizard.

 You can restore VM guest OS files from a backup of a virtualized Microsoft SQL Server, manually locate a
Microsoft SQL Server database and open it in Veeam Explorer for Microsoft SQL Server. For more
information, see Opening Microsoft SQL Server Database Manually.

Using the Microsoft SQL Server Database Restore Wizard

When you run the Microsoft SQL Server Database Restore wizard, Veeam Backup & Replication
automatically extracts a Microsoft SQL Server database from the storage snapshot and opens it in Veeam
Explorer for Microsoft SQL Server.

As part of this procedure, Veeam Backup & Replication performs the following actions:

1. Veeam Backup & Replication creates a clone/virtual copy of the storage snapshot and mounts the
clone/virtual copy to an ESX(i) host.

2. Veeam Backup & Replication accesses the configuration file of the virtualized Microsoft SQL Server (VMX)
on the snapshot clone/virtual copy and uses this configuration file to register a temporary VM on the
ESX(i) host.

3. Veeam Backup & Replication mounts disks of the Microsoft SQL Server to the temporary VM.

4. Veeam Backup & Replication locates a Microsoft SQL Server database and attaches the content database
to a staging Microsoft SQL Server. As a staging server, Veeam Backup & Replication uses the Microsoft
SQL Server on which the Veeam Backup & Replication configuration database is deployed.

5. Veeam Backup & Replication opens the database in Veeam Explorer for Microsoft SQL Server.

Before You Begin

Before you restore application items from storage snapshots, check the following prerequisites:

 You must add the storage system to the backup infrastructure.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses
on the storage system.

151 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch Microsoft SQL Server Database Restore Wizard
To launch the Microsoft SQL Server Database Restore wizard, do one of the following:

 Open the Storage Infrastructure view. In the inventory pane, select the necessary volume snapshot.
In the working area, select a VM running Microsoft SQL Server and click Application Items >
Microsoft SQL Server on the ribbon. You can also right-click the VM and select Restore application
items > Microsoft SQL Server databases. In this case, you will pass immediately to the Location
step of the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM running Microsoft SQL Server and click Application Items >
Microsoft SQL Server on the ribbon. You can also right-click the VM and select Restore application
items > Microsoft SQL Server databases. In this case, you will pass immediately to the Restore
Point step of the wizard.

To quickly find the necessary VM, you can use the search field at the top of the window. Enter a VM name or a
part of it and click the Start search button on the right or press [ENTER].

152 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, Veeam Backup & Replication displays all Microsoft SQL Server VMs
whose disks are located on the storage system. Select the necessary VM in the list. If the necessary VM is not
displayed in the list, select the Show all VMs check box. Veeam Backup & Replication will display all VMs whose
disks are located on the storage system.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

153 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point from which you want to restore a Microsoft SQL
Server database. Every storage snapshot acts as an independent restore point.

 Select Restore from the latest available backup if you want to restore a database from the latest
restore point in the backup chain.

 Select Restore from this restore point if you want to restore a database from a specific restore point.

154 | Veeam Backup & Replication | Integration with Storage Systems |

To specify a destination for the snapshot clone/virtual copy and temporary VM:

1. At the Location step of the wizard, click Customize.

2. Next to the Host field, click Choose and select an ESX(i) host to which the snapshot clone/virtual copy
must be mounted and on which the temporary VM must be created.

3. Next to the Resource pool field, click Choose and select a resource pool to which you want to place
the temporary VM.

4. Next to the Folder field, click Choose and select a folder to which you want to place the temporary VM.

5. Click OK.

155 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Specify Restore Reason
At the Reason step of the wizard, enter a reason for restoring a database from the Microsoft SQL Server VM.
The information you provide will be saved in the session history, and you will be able to view it later.

TIP:

If you do not want to display the Reason step of the wizard in future, select the Do not show me this
page again check box.

156 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Open Database in Veeam Explorer for Microsoft SQL Server
At the Summary step of the wizard, click Finish to start the restore process.

Veeam Backup & Replication will automatically locate a Microsoft SQL Server database and attach the content
database to a staging Microsoft SQL Server. After that, Veeam Backup & Replication will open the Veeam
Explorer for Microsoft SQL Server and add the restored database to it.

Detailed information about Veeam Explorer for Microsoft SQL is provided in documentation for Veeam Explorer
for Microsoft SQL. To access the documentation, do one of the following:

 Open Veeam Explorer for Microsoft SQL Server and press [F1].

 Open Veeam Explorer for Microsoft SQL Server. From the main menu of Veeam Explorer for Microsoft
SQL Server, select Help > Online Help.

157 | Veeam Backup & Replication | Integration with Storage Systems |

Opening Microsoft SQL Server Database Manually
If Veeam Backup & Replication fails to locate a Microsoft SQL Server database automatically for some reason,
you can use the file-level restore functionality to restore a Microsoft SQL Server database from the storage
snapshot. You can then open the database in Veeam Explorer for Microsoft SQL Server.

To restore a Microsoft SQL Server database:

1. Restore VM guest OS files from a backup of a virtualized Microsoft SQL Server. For more information, see
Restoring VM Guest OS Files (Microsoft Windows).

2. In the Veeam Backup browser, locate the MDF file and double-click it or select the file and click
Application Items > SQL Server Databases on the ribbon.

Veeam Backup & Replication will attach the restored database to the Microsoft SQL Server on which the
Veeam Backup & Replication configuration database is deployed and open the database in Veeam Explorer for
Microsoft SQL Server. After that, you can restore the database to the necessary Microsoft SQL Server.

Detailed information about Veeam Explorer for Microsoft SQL is provided in documentation for Veeam Explorer
for Microsoft SQL. To access the documentation, do one of the following:

 Open Veeam Explorer for Microsoft SQL Server and press [F1].

 Open Veeam Explorer for Microsoft SQL Server. From the main menu of Veeam Explorer for Microsoft
SQL Server, select Help > Online Help.

158 | Veeam Backup & Replication | Integration with Storage Systems |

Restoring Databases from Oracle
Veeam Backup & Replication integrates with Veeam Explorer for Oracle — a tool that lets you browse Oracle
databases in VMs located on storage snapshots and restore Oracle databases.

Before you start working with Veeam Explorer for Oracle, you need to extract an Oracle database from the
storage snapshot. You can do it in two ways:

 You can use the Oracle Database Restore wizard. In this case, Veeam Backup & Replication will
automatically extract an Oracle database from the storage snapshot and open it in Veeam Explorer for
Oracle. For more information, see Using the Oracle Database Restore Wizard.

 You can restore VM guest OS files from a backup of a virtualized Oracle server, manually locate an
Oracle database and open it in Veeam Explorer for Oracle. For more information, see Opening Oracle
Database Manually.

Using the Oracle Restore Wizard

When you run the Oracle Database Restore wizard, Veeam Backup & Replication automatically extracts an
Oracle database from the storage snapshot and opens it in Veeam Explorer for Oracle.

As part of this procedure, Veeam Backup & Replication performs the following actions:

1. Veeam Backup & Replication creates a clone/virtual copy of the storage snapshot and mounts the
clone/virtual copy to an ESX(i) host.

2. Veeam Backup & Replication accesses the configuration file of the virtualized Oracle server (VMX) on the
snapshot clone/virtual copy and uses this configuration file to register a temporary VM on the ESX(i)
host.

3. Veeam Backup & Replication mounts disks of the Oracle server to the temporary VM.

4. Veeam Backup & Replication locates the Oracle database and attaches the database to a staging Oracle
server.

5. Veeam Backup & Replication opens the database in Veeam Explorer for Oracle.

Before You Begin

Before you restore application items from storage snapshots, check the following prerequisites:

 You must add the storage system to the backup infrastructure.

 You must check limitations for Veeam Explorer for Storage Snapshots. For more information, see Veeam
Explorer for Storage Snapshots.

 [For NetApp storage systems] Depending on the storage type, you may need to install additional licenses
on the storage system.

159 | Veeam Backup & Replication | Integration with Storage Systems |

Step 1. Launch Oracle Database Restore Wizard
To launch the Oracle Database Restore wizard, do one of the following:

 Open the Storage Infrastructure view. In the inventory pane, select the necessary volume snapshot.
In the working area, select a VM running Oracle and click Application Items > Oracle on the ribbon.
You can also right-click the VM and select Restore application items > Oracle databases. In this
case, you will pass immediately to the Location step of the wizard.

 Open the Home view. In the inventory pane, select Storage snapshots. In the working area, expand
the necessary volume, select a VM running Oracle and click Application Items > Oracle on the ribbon.
You can also right-click the VM and select Restore application items > Oracle databases. In this
case, you will pass immediately to the Restore Point step of the wizard.

To quickly find a VM, you can use the search field at the top of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

160 | Veeam Backup & Replication | Integration with Storage Systems |

Step 2. Select VM
At the Virtual Machine step of the wizard, Veeam Backup & Replication displays all Oracle VMs whose disks are
located on the storage system. Select the necessary VM in the list. If the necessary VM is not displayed in the list,
select the Show all VMs check box. Veeam Backup & Replication will display all VMs whose disks are located on
the storage system.

To quickly find a VM, you can use the search field at the bottom of the window. Enter the VM name or a part of it
and click the Start search button on the right or press [ENTER].

161 | Veeam Backup & Replication | Integration with Storage Systems |

Step 3. Select Restore Point
At the Restore Point step of the wizard, select a restore point from which you want to restore an Oracle
database. Every storage snapshot acts as an independent restore point.

 Select Restore from the latest available backup if you want to restore a database from the latest
restore point in the backup chain.

 Select Restore from this restore point if you want to restore a database from a specific restore point.

162 | Veeam Backup & Replication | Integration with Storage Systems |

Step 4. Select ESX(i) Host for Snapshot Mounting
At the Location step of the wizard, select an ESX(i) host to which the clone/virtual copy of the storage snapshot
must be mounted. On the selected ESX(i) host, Veeam Backup & Replication will create a temporary VM and
mount the disks of the virtualized Oracle server to this temporary VM.

To specify a destination for the snapshot clone/virtual copy and temporary VM:

1. At the Location step of the wizard, click Customize.

2. Next to the Host field, click Choose and select an ESX(i) host to which the snapshot clone/virtual copy
must be mounted and on which the temporary VM must be created.

3. Next to the Resource pool field, click Choose and select a resource pool to which you want to place
the temporary VM.

4. Next to the Folder field, click Choose and select a folder to which you want to place the temporary VM.

5. Click OK.

163 | Veeam Backup & Replication | Integration with Storage Systems |

Step 5. Specify Restore Reason
At the Reason step of the wizard, enter a reason for restoring a database from the Oracle VM if necessary. The
information you provide will be saved in the session history, and you will be able to view it later.

TIP:

If you do not want to display the Reason step of the wizard in future, select the Do not show me this
page again check box.

164 | Veeam Backup & Replication | Integration with Storage Systems |

Step 6. Open Database in Veeam Explorer for Oracle
At the Summary step of the wizard, click Finish to start the restore process.

Veeam Backup & Replication will automatically locate an Oracle database and attach the content database to the
staging server. After that, Veeam Backup & Replication will open the Veeam Explorer for Oracle and add the
database to it.

Detailed information about Veeam Explorer for Oracle is provided in documentation for Veeam Explorer for
Oracle. To access the documentation, do one of the following:

 Open Veeam Explorer for Oracle and press [F1].

 Open Veeam Explorer for Oracle. From the main menu of Veeam Explorer for Oracle, select Help >
Online Help.

165 | Veeam Backup & Replication | Integration with Storage Systems |

Opening Oracle Database Manually
If Veeam Backup & Replication fails to locate an Oracle database automatically for some reason, you can use the
file-level restore functionality to restore an Oracle database from the storage snapshot. You can then open the
database in Veeam Explorer for Oracle.

To restore an Oracle database:

1. Restore VM guest OS files from a backup of a virtualized Oracle server. For more information, see
Restoring VM Guest OS Files (Microsoft Windows).

2. In the Veeam Backup browser, locate the database file and double-click it or select the file and click
Application Items > Oracle databases on the ribbon.

Veeam Backup & Replication will attach the restored database to a staging server and open the database in
Veeam Explorer for Oracle. After that, you can restore the database to the necessary Oracle server.

Detailed information about Veeam Explorer for Oracle is provided in documentation for Veeam Explorer for
Oracle. To access the documentation, do one of the following:

 Open Veeam Explorer for Oracle and press [F1].

 Open Veeam Explorer for Oracle. From the main menu of Veeam Explorer for Oracle, select Help >
Online Help.

166 | Veeam Backup & Replication | Integration with Storage Systems |

On-Demand Sandbox for Storage
Snapshots
In the On-Demand Sandbox, you can start VMs from snapshots existing on the production storage array. You can
use the On-Demand Sandbox to test VMs, troubleshoot issues, perform training and so on.

Veeam Backup & Replication offers the On-Demand Sandbox functionality for the following storage systems:

 Dell EMC VNX(e)

 HPE 3PAR StoreServ, including secondary HPE 3PAR volumes — HPE 3PAR Peer Persistence

 HPE StoreVirtual P4000 series and HPE StoreVirtual VSA (Virtual Storage Appliance)

 IBM Spectrum Virtualize, including secondary IBM volumes — IBM Spectrum Virtualize HyperSwap

 NetApp, including secondary NetApp arrays — NetApp SnapMirror and NetApp SnapVault

 Nimble storage, including secondary Nimble arrays — Nimble Snapshot Replicated Copy

Configuration of the On-Demand Sandbox in which VMs from storage snapshots are started is similar to
configuration of the regular On-Demand Sandbox. To start a VM from the storage snapshot in the isolated
environment, you must configure the following objects:

 Virtual lab. The virtual lab must mirror the networking scheme of the production environment. You can
configure a new virtual lab or use an existing virtual lab. Any type of the virtual lab configuration is
supported: basic single-host, advanced single-host or advanced multi-host. For more information, see
Veeam Backup & Replication User Guide for VMware vSphere.

 Application group. The application group must contain one or several VMs that you want to start in the
On-Demand Sandbox. You can select VMs from volumes or LUNs on the storage system. During the
SureBackup job, Veeam Backup & Replication will detect the latest snapshot for this volume or LUN and
start the VM from this snapshot. For more information, see Veeam Backup & Replication User Guide for
VMware vSphere.

 SureBackup job. You must link the application group with VMs and virtual lab to the SureBackup job.
For more information, see Veeam Backup & Replication User Guide for VMware vSphere.

How On-Demand Sandbox for Storage Snapshots Works

To start a VM from the storage snapshot in the On-Demand Sandbox, Veeam Backup & Replication needs to
present this storage snapshot to an ESX(i) host as a datastore. To do this, Veeam Backup & Replication performs
the following actions:

1. Veeam Backup & Replication detects the latest storage snapshot for the VM whose disks are located on
the storage system.

2. Veeam Backup & Replication triggers the storage system to create a copy of the storage snapshot. The
snapshot copy helps protect the storage snapshot from changes.
To create a snapshot copy, Veeam Backup & Replication uses the same technology as for Veeam
Explorer from Storage Snapshots. The technology choice depends on licenses installed on the storage
system. For more information, see Veeam Explorer for Storage Snapshots.

3. The snapshot copy is presented as a new datastore to the ESX(i) host on which the virtual lab is
registered.

4. Veeam Backup & Replication performs regular operations required for On-Demand Sandbox: reconfigures
the VMX file, starts the VM, performs necessary tests for it and so on.

167 | Veeam Backup & Replication | Integration with Storage Systems |

5. After you finish working with VMs and power off the On-Demand Sandbox, Veeam Backup & Replication
performs cleanup operations: powers off the VM and the proxy appliance in the virtual lab, unmounts the
datastore from the ESX(i) host and triggers the storage system to remove the snapshot copy.

Number of Mounted NFS Datastores

You can add to the application group several VMs that reside on different storage snapshots. In this case,
Veeam Backup & Replication will trigger several snapshot copies (one per each storage snapshot) and present
the equal number of datastores to the ESX(i) host.

The number of NFS datastores that can be mounted to the ESX(i) host is limited by VMware vSphere. If number
of snapshot copies is great, Veeam Backup & Replication may fail to present all of them as datastores to the
ESX(i) host. In this case, VMs in the application group will not be started and the SureBackup job will fail. For
more information about limitations, see
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2239.

To overcome this situation, Veeam Backup & Replication offers the mechanism of the snapshot copy re-
mounting:

1. If Veeam Backup & Replication detects that there are not enough resources to mount a datastore, it
displays a warning and offers you to free up resources on the ESX(i) host.

2. During the next 20 minutes, Veeam Backup & Replication attempts to mount the datastore with the time
interval of 2 minutes.

3. If resources are freed and Veeam Backup & Replication manages to mount the datastore, VMs in the
application group are started and the SureBackup job continues to run. If resources on the ESX(i) hosts
are not freed within 20 minutes, the SureBackup job fails.

Limitations for On-Demand Sandbox for Storage Snapshots

On-Demand Sandbox for storage snapshots has the following limitation:

 You cannot add to the On-Demand Sandbox a VM whose disks are hosted on a VMware datastore that
comprises several LUNs.

 If a VM has several disks that are located on different VMware vSphere datastores,
Veeam Backup & Replication will register a temporary VM only with those disks that are located on the
storage snapshot from which you added the VM. Other VM disks will be excluded from the VMX
configuration file of the temporary VM.

168 | Veeam Backup & Replication | Integration with Storage Systems |

Requirements and Limitations
Backup from Storage Snapshots and Veeam Explorer for Storage Snapshots have a set of limitations and
requirements to storage systems:

 General Limitations

 Cisco HyperFlex

 EMC VNX/VNXe

 NetApp

169 | Veeam Backup & Replication | Integration with Storage Systems |

General Limitations
The following limitations apply to all storage systems supported by Veeam Backup & Replication:

Backup Infrastructure
 Veeam Backup & Replication does not display volumes with the 'VeeamAUX' prefix in the storage
hierarchy. Such volumes are used for service purposes and are filtered out.

 [For iSCSI connectivity] CHAP authentication is not supported.

 SAS connections are not supported.

Backup from Storage Snapshots

Backup from Storage Snapshots has the following limitations:

 Backup from Storage Snapshots does not support vRDM disks. vRDM disks are skipped from processing.

 Backup from Storage Snapshots cannot be used for VMs whose disks are located on VVol datastores.

 Backup from Storage Snapshots cannot be used to back up VM templates.

 [For storage systems working over NFS] VMs that you plan to back up or replicate must not have
VMware vSphere snapshots. VMs with snapshots are skipped from processing.

 [For storage systems working over NFS] If you enable the Enable VMware tools quiescence option in
the job settings, Veeam Backup & Replication will not use Backup from Storage Snapshots to process
running Microsoft Windows VMs that have VMware Tools installed.

Veeam Explorer for Storage Snapshots

Veeam Explorer for Storage Snapshots has the following limitations:

 You cannot perform any kind of restore operation (Instant VM Recovery, VM guest OS files restore and
application items restore) when a VMware datastore comprises several LUNs.

 Veeam Explorer for Storage Snapshots does not support VMs whose disks are located on VVol
datastores.

 If a VM has several disks that are located on different VMware vSphere datastores,
Veeam Backup & Replication will restore the following data:

o [Instant VM Recovery] The restored VM will have only those VM disks that are hosted on
the same datastore as the VMX file.

o [VM guest OS files restore] You will be able to restore VM guest OS files only from those
VM disks that are hosted on the same datastore as the VMX file.

o [Application items restore] You will be able to restore application items only from those VM
disks that are hosted on the same datastore as the VMX file.

 [Multi-OS file-level restore] You cannot restore files directly to the original location from backups of BSD,
Mac and Solaris VMs. You cannot restore files directly to the original location from NSS filesystems. Use
the Copy to option instead.

 [For secondary storage arrays] You cannot perform Instant VM Recovery and restore VM guest OS files
to the original location from snapshots on secondary storage arrays — NetApp SnapMirror, SnapVault

170 | Veeam Backup & Replication | Integration with Storage Systems |

and Nimble Snapshot Replicated Copy. Secondary storage arrays are not mapped to original VMs and
datastores.
The file-level restore limitation applies both to Microsoft Windows and other file systems. Use the Copy
to option instead.

 Multi-OS file-level restore for encrypted VMs is not supported.

 If the original VM is removed from vSphere infrastructure or migrated to another datastore, you won`t
be able to perform the following operations:

o Perform instant VM Recovery to the original location

o Perform VM guest OS files restore to the original location

o Restore the VM disks that contain the absolute path in the VMX file

Snapshot-Only Jobs
 If a VM added to the job has several disks that reside on the same volume, you cannot exclude specific
VM disks from the backup as Veeam Backup & Replication creates snapshots at the volume level.

 Veeam Backup & Replication does not support the following guest processing options for snapshot-only
jobs: Microsoft SQL Server and Oracle log backup and guest file indexing.

 If you remove and re-add a SAN array that is already associated with a snapshot-only job,
Veeam Backup & Replication will restart the retention cycle. You will need to manually remove old
snapshots that are no longer needed.

171 | Veeam Backup & Replication | Integration with Storage Systems |

Limitations for Cisco HyperFlex
If you plan to perform backup and replication from Cisco HyperFlex storage snapshots, consider the following
limitations:

 VMs must be hosted on the supported Cisco HyperFlex system. For more information, see System
Requirements.

 Veeam Backup & Replication 9.5 Update 2 must be installed on the backup server. For more information,
see Integration Modes.

 Currently Veeam Backup & Replication does not support scenarios where several Cisco HyperFlex
systems are registered under different VMware vCenter Servers. It is recommended to back up VMs of
each VMware vCenter Server instance using a separate Veeam backup server.

 VMs must not have VMware vSphere snapshots. VMs with VMware vSphere snapshots are skipped during
backup or replication. You can instruct Veeam Backup & Replication to process these VMs in the regular
data processing mode. To do this, enable the Failover to standard backup option in job settings.

 Disks of a processed VM must be located on the same Cisco HyperFlex NFS store. If some VM disks are
located on an NFS store other than the store hosting the VM configuration file, such VM will be processed
in the regular backup mode.

 The Limit processed VM count per storage snapshots to N option is not applicable to Cisco
HyperFlex since snapshots for VMs hosted on Cisco HyperFlex are created at the VM level, not volume
level.

172 | Veeam Backup & Replication | Integration with Storage Systems |

Limitations for Dell EMC VNX/VNXe
If you plan to perform backup and restore from Dell EMC VNX/VNXe storage snapshots, consider the following
limitations:

Dell EMC VNX Block

 Veeam Backup & Replication supports LUNs that reside on Storage Pools.

 To take LUN snapshots, Veeam Backup & Replication uses the VNX snapshot technology. Make sure that
you have a license that covers this technology. The SnapView snapshot technology is not supported.

Dell EMC VNX File

 A read-only checkpoint can have only 1 writable snapshot. If a read-only checkpoint already has a
writable snapshot, Veeam Backup & Replication uses this writable snapshot for restore.

 Writable snapshots are not detected by the storage rescan process and are not displayed in the storage
system hierarchy.

Dell EMC VNXe

In EMC VNXe, you cannot export more than 1 storage snapshot for a LUN or LUN group concurrently. For this
reason, Veeam Backup & Replication can perform only one task that uses storage snapshots at the same time.

In Veeam Backup & Replication, tasks have the following priority levels (starting with the highest priority):
restore task > backup job > rescan task. If you start several jobs or tasks that use storage snapshots,
Veeam Backup & Replication will check what priority tasks have and perform the following actions:

 If a LUN snapshot is exported for storage rescan and you start a backup job or restore task at the same
time, the rescan process will fail.

 If a LUN snapshot is exported for a backup job and you start another backup job at the same time, the
second backup job will be waiting until the first backup job is finished.

 If a LUN snapshot is exported for a restore task and you start a backup job at the same time, the backup
job will fail (or failover to the regular processing mode if corresponding settings are enabled in the
backup job).

 If a LUN snapshot is exported for a backup job and you start a restore task at the same time, the restore
task will be waiting until the backup job is finished.

Dell EMC VNX(e) Working over NFS

 VMs that you plan to back up or replicate must not have VMware vSphere snapshots. VMs with VMware
vSphere snapshots will be skipped from Backup from Storage Snapshots.

 If you enable the Enable VMware tools quiescence option in the backup job settings,
Veeam Backup & Replication will not use Backup from Storage Snapshots to process running Microsoft
Windows VMs that have VMware Tools installed.

173 | Veeam Backup & Replication | Integration with Storage Systems |

Requirements and Limitations for NetApp
Depending on the protocol type and operating mode of the NetApp storage system, Veeam Backup & Replication
uses different technologies to perform the following operations:

 Storage system rescan

 Backup from Storage Snapshots

 Restore from storage snapshots

You may need to install additional NetApp licenses. You need to install one license, even if several technologies
can be used for snapshot clone creation.

Rescan of NetApp Storage System

cDot
Storage Type FlexClone SnapRestore No License

Primary Storage System

iSCSI/FC Possible (preferred) Possible Not possible

NFS Possible Possible Possible

Secondary Storage System: NetApp SnapMirror and SnapVault

iSCSI/FC Possible Not possible Not possible

NFS Possible Possible Possible

NOTE:
During storage rescan, Veeam Backup & Replication adds its export rules for the storage. New rules are added
at the beginning of the list, shifting existing rules down in the list.

Backup from Storage Snapshots

7-Mode
Traditional LUN Cloning (no
Storage Type FlexClone
license)

FC/iSCSI Possible Recommended

NFS Not needed Not needed

174 | Veeam Backup & Replication | Integration with Storage Systems |

cDot
Storage Type FlexClone SnapRestore No License

Primary Storage System

iSCSI/FC Possible (preferred) Possible Not possible

NFS Possible Possible Possible

Secondary Storage System: NetApp SnapMirror and SnapVault

iSCSI/FC Possible (mandatory) Not possible Not possible

NFS Possible Possible Possible

NOTE:
During backup from storage snapshots, Veeam Backup & Replication adds its export rules for the storage.
New rules are added at the beginning of the list, shifting existing rules down in the list.

Traditional LUN Cloning

For NetApp storage systems that do not have a FlexClone license installed, Veeam Backup & Replication uses the
NetApp traditional LUN cloning technology.

Traditional LUN clones are created with the help of a backing snapshot.

1. Veeam Backup & Replication creates a backing snapshot for a LUN holding VM data. The backing
snapshot is a snapshot of a volume where the LUN is located. The backing snapshot acts as a helper, or
medium, for the LUN clone. It contains a momentarily image of the LUN and captures the exact state of
the LUN at the necessary point in time.

2. After that, Veeam Backup & Replication creates a LUN clone.

The LUN clone bases on the backing snapshot and shares its data with the backing snapshot.
Veeam Backup & Replication cannot delete the backing snapshot before the LUN clone is removed. Deletion of
the backing snapshot will corrupt the LUN clone.

In case of traditional LUN cloning, backing snapshots created by Veeam Backup & Replication may be locked and
may fail to be deleted automatically with cleanup operations. This can happen, for example, if you schedule the
NetApp storage system to create daily volume snapshots, and the scheduled operation begins before
Veeam Backup & Replication deletes the backing snapshot that was used for backup or replication.

175 | Veeam Backup & Replication | Integration with Storage Systems |

In this situation, the created backing snapshot will become a part of the snapshot chain. The scheduled snapshot
and all subsequent snapshots will reference this snapshot, and Veeam Backup & Replication will be unable to
remove it. As a result, your retention policy for scheduled snapshots may be disrupted.

To avoid this situation, it is recommended that you install a FlexClone license on the NetApp storage system. In
this case, Veeam Backup & Replication will use the FlexClone technology for LUN cloning.

FlexClone
The FlexClone technology lets you create a transparent, space-efficient copy of a LUN. FlexClones are created in
seconds and require little space on the storage. Unlike traditional LUN clones, FlexClones are independent and do
not cause any problems with volume snapshot deletion.

For Backup from Storage Snapshots, Veeam Backup & Replication creates a FlexClone in the following way:

1. Veeam Backup & Replication creates a temporary snapshot of a volume hosting a LUN to capture the
momentary state of this LUN.

2. After that, Veeam Backup & Replication creates a LUN clone.

This temporary volume snapshot is used as a base for a FlexClone. However, the base snapshot is not tied to the
FlexClone, as a backing snapshot in traditional LUN cloning. Veeam Backup & Replication can delete it without
any impact for the FlexClone at any time.

SnapRestore
For NetApp storage systems that work in the cDot operating mode and have a SnapRestore license installed,
Veeam Backup & Replication can use the NetApp SnapRestore technology for Backup from Storage Snapshots.

Veeam Backup & Replication creates a storage snapshot in the following way:

1. Veeam Backup & Replication creates a snapshot of a volume holding VM data.

2. Veeam Backup & Replication creates a LUN clone via SnapRestore.

176 | Veeam Backup & Replication | Integration with Storage Systems |

NFS Protocol
If the NetApp storage system operates over NFS, you do not have to install any additional licenses to use Backup
from Storage Snapshots.

For Backup from Storage Snapshots, Veeam Backup & Replication creates a snapshot of a volume on which the
NFS share with VM data resides. The created volume snapshot is used as a source of data.
Veeam Backup & Replication starts its native NFS agent on the backup proxy and uses this agent to read data
from the cloned NFS share on the volume snapshot.

177 | Veeam Backup & Replication | Integration with Storage Systems |

Restore from Storage Snapshots

7-Mode
Traditional LUN
Storage Type Cloning FlexClone SnapRestore NDMP
(No License)

Only one license is required

FC/iSCSI Possible Recommended Not possible Not possible

NFS Not possible Recommended Limited usage. Limited usage.

Veeam Backup & Repli Veeam Backup & Repli
cation transports all cation transports all
data before Instant VM data before Instant VM
Recovery, file-level Recovery, file-level
restore or application restore or application
item restore starts.*** item restore starts.***

FC/iSCSI SnapMirror Not used Mandatory Not possible Not possible

FC/iSCSI SnapVault Used for restore Mandatory (used for Not possible Not possible
rescan*)

NFS SnapMirror Not possible Recommended Limited usage. Limited usage.

Several licenses are used

NFS SnapVault Not possible For file-level restore Limited usage. Limited usage.
and application item Veeam Backup & Repli Veeam Backup & Repli
restore, cation transports all cation transports all
Veeam Backup & Repli data before Instant VM data before Instant VM
cation can use Recovery, file-level Recovery, file-level
FlexClone**. For VM restore or application restore or application
restore, item restore starts.*** item restore starts.***
Veeam Backup & Repli
cation can use
SnapRestore or NDMP
(check columns on the
right).

* Not used for restore operations due to NetApp SnapVault limitations.

** Can be used only for file-level restore. To enable restore, you can use registry keys. For more information,
contact Veeam Support Team.

*** Veeam Backup & Replication copies VM files from the /vol/volname/VMFolder/ folder from the snapshot to
the /vol/vvolname/Veeam_Restore_VMname/VMFolder/ folder, and restore wizards work with copied files.

178 | Veeam Backup & Replication | Integration with Storage Systems |

cDot
Storage Type FlexClone SnapRestore No License

Primary Storage System

iSCSI/FC Possible (preferred) Possible Not possible

NFS Possible Possible Not possible

Secondary Storage System: NetApp SnapMirror and SnapVault

iSCSI/FC Possible (mandatory) Not possible Not possible

NFS Possible (mandatory) Not possible Not possible

Traditional LUN Cloning

For NetApp storage systems that do not have the FlexClone license installed, Veeam Backup & Replication uses
the NetApp traditional LUN cloning technology.

During restore from storage snapshots, Veeam Backup & Replication creates a LUN clone. The storage snapshot
from which you want to restore data is used as a backing copy. The LUN clone is then mounted to an ESXi host,
and you can restore VM data from it.

179 | Veeam Backup & Replication | Integration with Storage Systems |

FlexClone
For NetApp storage systems that have a FlexClone license installed, Veeam Backup & Replication uses the
NetApp FlexClone technology for restore from storage snapshots.

During restore from storage snapshots, Veeam Backup & Replication creates a FlexClone of a LUN. The storage
snapshot from which you want to restore data is used as a base copy. The FlexClone is then mounted to an ESXi
host, and you can restore the necessary VM data from it.

SnapRestore
For NetApp storage systems that have a SnapRestore license installed, Veeam Backup & Replication uses the
NetApp SnapRestore technology for restore from storage snapshots.

When you restore data from storage snapshot, Veeam Backup & Replication triggers NetApp to create a clone of
a LUN via SnapRestore. To do this, NetApp restores LUN data to a new location on the volume where the original
LUN is located. As a result, you have a read-write copy of the LUN holding VM data, and can use this copy for
restore operations.

NFS Protocol
When you perform restore from storage snapshot on NetApp storage systems working over the NFS protocol,
Veeam Backup & Replication triggers NetApp to clone an NFS share that holds VM data. NetApp creates a copy of
the NFS share and places this copy on the same volume where the original NFS share is located. This copy is
used as a data source for restore operations.

After a copy of the NFS share is created, Veeam Backup & Replication mounts the NFS share copy to an ESX(i)
host as a new datastore, and you can restore VM data from the mounted NFS share copy.

If you have several VMs that reside on the same storage snapshot, Veeam Backup & Replication will create only
one NFS datastore per snapshot. During restore, VMs from the same snapshot are copied to the same folder on
the volume where the original NFS share is located. When you start the restore process for the first VM on the
storage snapshot, the folder is presented as a datastore to an ESX(i) host. After you finish the restore process for
the last VM on the storage snapshot, the folder is unmounted from the ESX(i) host.

180 | Veeam Backup & Replication | Integration with Storage Systems |

Depending on the operation mode of the NetApp storage system, Veeam Backup & Replication uses different
technologies to create a clone of an NFS share.

7-mode

If the NetApp storage system operates in the 7-mode, you must have a FlexClone or SnapRestore license
installed, or the NDMP protocol enabled.

Veeam Backup & Replication uses the following technologies for LUN clone creation:

 If you have a FlexClone license installed, Veeam Backup & Replication uses the FlexClone technology.

 If you have a SnapRestore license installed, Veeam Backup & Replication uses the SnapRestore
technology.

If neither FlexClone nor SnapRestore license is installed, Veeam Backup & Replication uses the NDMP protocol. If
the NDMP protocol is not enabled, VM data restore will fail.

IMPORTANT!
[For Instant VM Recovery] Veeam Backup & Replication performs actual Instant VM Recovery only if a
FlexClone license is installed. If the SnapRestore license is installed or the NDMP protocol is enabled,
Veeam Backup & Replication performs entire VM restore instead of Instant VM Recovery. As a result, the
restore process takes more time.

C-mode

If the NetApp storage system operates in the C-mode, you must have a FlexClone or SnapRestore license
installed.

 If you have a FlexClone license installed, Veeam Backup & Replication uses the FlexClone technology.

 If you have a SnapRestore license installed, Veeam Backup & Replication uses the SnapRestore
technology.

If neither FlexClone nor SnapRestore license is installed, VM data restore will fail.

181 | Veeam Backup & Replication | Integration with Storage Systems |

Restore from SnapVault
7-mode

If the NetApp storage system operates in the 7-mode, you must have a FlexClone or SnapRestore license
installed, or the NDMP protocol enabled.

 If you have a SnapRestore license installed, Veeam Backup & Replication uses the SnapRestore
technology.

 If a SnapRestore license is not installed, Veeam Backup & Replication uses the NDMP protocol. If the
NDMP protocol is not enabled, VM data restore will fail.

IMPORTANT!

[For Instant VM Recovery] If you restore data from NetApp SnapVault, Veeam Backup & Replication performs
entire VM restore instead of Instant VM Recovery. As a result, the restore process takes more time.

C-mode

If the NetApp storage system operates in the C-mode, you must have a FlexClone license installed. In the
opposite case, VM data restore will fail.

User Permissions
A user account that you plan to use for work with the NetApp storage system must have the following
permissions:

7-Mode
 login-http-admin

 api-system-*

 api-license-* (api-license-list-info)

 api-volume-*

 api-net-*

 api-options-*

 api-vfiler-*

 api-qtree-*

 api-nfs-*

 api-snapshot-*

 api-lun-*

 api-iscsi-*

182 | Veeam Backup & Replication | Integration with Storage Systems |

 api-feature-*

 api-registry-*

 cli-options

 api-fcp-*

 api-file-*

 api-igroup-*

 api-clone-*

 api-snapvault-*

 api-snapmirror-*

 api-cf-*

cDot
Command/Directory Access/Query Level

DEFAULT readonly

cluster readonly

metrocluster readonly

fcp readonly

file readonly

igroup readonly

iscsi all

network readonly

node readonly

security readonly

security login readonly

set readonly

snapmirror all

system readonly

version readonly

183 | Veeam Backup & Replication | Integration with Storage Systems |

qtree readonly

lun all

nfs all

snapshot all

volume all

vserver all

184 | Veeam Backup & Replication | Integration with Storage Systems |

Veeam Backup 9 5 U4 Storage Integration User Guide
No ratings yet
Veeam Backup 9 5 U4 Storage Integration User Guide
194 pages
Veeam Backup & Replication: Integration With Storage Systems Guide
No ratings yet
Veeam Backup & Replication: Integration With Storage Systems Guide
271 pages
Veeam Backup 11 0 Storage Integration User Guide
No ratings yet
Veeam Backup 11 0 Storage Integration User Guide
259 pages
Veeam Backup 11 0 Storage Integration User Guide
No ratings yet
Veeam Backup 11 0 Storage Integration User Guide
254 pages
Veeam Backup & Replication: User Guide Vmware Environments
No ratings yet
Veeam Backup & Replication: User Guide Vmware Environments
218 pages
Backup 5.0.2 User Guide
No ratings yet
Backup 5.0.2 User Guide
177 pages
Veeam Backup 12 Storage Integration User Guide
No ratings yet
Veeam Backup 12 Storage Integration User Guide
244 pages
Veeam 9.5 User Guide
No ratings yet
Veeam 9.5 User Guide
1,121 pages
Veeam Backup 8 Userguide Vmware
No ratings yet
Veeam Backup 8 Userguide Vmware
841 pages
Veeam Backup 9 0 User Guide Vsphere en
No ratings yet
Veeam Backup 9 0 User Guide Vsphere en
1,173 pages
VeeamBackup&Replication 12.0 Sample
100% (1)
VeeamBackup&Replication 12.0 Sample
23 pages
Veeam Backup 9 5 User Guide Vsphere PDF
No ratings yet
Veeam Backup 9 5 User Guide Vsphere PDF
1,040 pages
Veeam Backup 9 0 User Guide Vsphere en
No ratings yet
Veeam Backup 9 0 User Guide Vsphere en
1,068 pages
Veeam Backup 8 Userguide Vmware
100% (2)
Veeam Backup 8 Userguide Vmware
783 pages
Veeam Backup 11 0 User Guide Vsphere
No ratings yet
Veeam Backup 11 0 User Guide Vsphere
1,857 pages
Veeam Backup 11 0 User Guide Vsphere
No ratings yet
Veeam Backup 11 0 User Guide Vsphere
1,904 pages
Veeam Backup 11 0 User Guide Vsphere
No ratings yet
Veeam Backup 11 0 User Guide Vsphere
2,022 pages
Veeam Backup 9 5 User Guide Vsphere en
No ratings yet
Veeam Backup 9 5 User Guide Vsphere en
996 pages
Veeam Backup 9 5 User Guide Hyperv
No ratings yet
Veeam Backup 9 5 User Guide Hyperv
936 pages
Veeam Backup & Replication - User Guide For VMware Vsphere - Version 11
No ratings yet
Veeam Backup & Replication - User Guide For VMware Vsphere - Version 11
1,999 pages
Veeam Backup 11.0 User Guide Vsphere
100% (1)
Veeam Backup 11.0 User Guide Vsphere
1,927 pages
Veeam Im Huawei Universum Jan Maue
No ratings yet
Veeam Im Huawei Universum Jan Maue
34 pages
Veeam Backup & Replication - User Guide For Hyper-V Environments
No ratings yet
Veeam Backup & Replication - User Guide For Hyper-V Environments
249 pages
Backup and Replication
No ratings yet
Backup and Replication
173 pages
Veeam Backup 7 Userguide
No ratings yet
Veeam Backup 7 Userguide
457 pages
Veeam Backup 12 Quick Start Guide Vsphere
No ratings yet
Veeam Backup 12 Quick Start Guide Vsphere
125 pages
Veeam Backup 11 0 Aws Integration User Guide
No ratings yet
Veeam Backup 11 0 Aws Integration User Guide
157 pages
Veeam Backup 9 0 Permissions
0% (1)
Veeam Backup 9 0 Permissions
19 pages
Veeam Backup 9 5 U4 User Guide Vsphere
No ratings yet
Veeam Backup 9 5 U4 User Guide Vsphere
1,246 pages
Veeam Backup 11.0 User Guide Hyper-V
No ratings yet
Veeam Backup 11.0 User Guide Hyper-V
1,576 pages
Veeam 12 Preview Slides
No ratings yet
Veeam 12 Preview Slides
57 pages
#1 Cloud Data Management: Veeam Backup & Replication
No ratings yet
#1 Cloud Data Management: Veeam Backup & Replication
2 pages
Veeam Backup 11 0 Quick Start Guide Vsphere
No ratings yet
Veeam Backup 11 0 Quick Start Guide Vsphere
127 pages
Veeam Backup 9 5 User Guide Hyperv en
No ratings yet
Veeam Backup 9 5 User Guide Hyperv en
910 pages
Veeam Backup 12 Quick Start Guide Vsphere
No ratings yet
Veeam Backup 12 Quick Start Guide Vsphere
129 pages
Veeam Certified Engineer Training Program: Textbook
No ratings yet
Veeam Certified Engineer Training Program: Textbook
203 pages
Veeam Backup 12 User Guide Vsphere
100% (1)
Veeam Backup 12 User Guide Vsphere
2,695 pages
Veeam Presentation
No ratings yet
Veeam Presentation
25 pages
VMCEv9 Textbook 20160718
No ratings yet
VMCEv9 Textbook 20160718
199 pages
VMCEv9 Textbook
No ratings yet
VMCEv9 Textbook
199 pages
Veeam Backup 7 Userguide Vmware
No ratings yet
Veeam Backup 7 Userguide Vmware
575 pages
VBR UserGuide
No ratings yet
VBR UserGuide
77 pages
Veeam Backup 11 0 User Guide Hyperv
No ratings yet
Veeam Backup 11 0 User Guide Hyperv
1,659 pages
Veeam Backup 10 0 Quick Start Guide Vsphere
No ratings yet
Veeam Backup 10 0 Quick Start Guide Vsphere
118 pages
Veeam Backup 10 0 User Guide Hyperv
No ratings yet
Veeam Backup 10 0 User Guide Hyperv
1,410 pages
Veeam Backup Replication Best Practices
100% (1)
Veeam Backup Replication Best Practices
249 pages
VMCE9 Textbook 20161024 PDF
No ratings yet
VMCE9 Textbook 20161024 PDF
211 pages
Veeam Backup Replication v8 Designing Planning Backup Repository Performance
100% (1)
Veeam Backup Replication v8 Designing Planning Backup Repository Performance
28 pages
Vmware Site Recovery Technical Overview
No ratings yet
Vmware Site Recovery Technical Overview
26 pages
Smartfabric Os10 Virtual Link Trunking Ra
No ratings yet
Smartfabric Os10 Virtual Link Trunking Ra
33 pages
VMware-iSCSI Design Deploy
No ratings yet
VMware-iSCSI Design Deploy
26 pages
Windows MPIO Setup for VNXe3200
No ratings yet
Windows MPIO Setup for VNXe3200
15 pages
2021.Q2 Goehring & Rozencwajg Market Commentary
No ratings yet
2021.Q2 Goehring & Rozencwajg Market Commentary
26 pages
Sunilkumar VCS
No ratings yet
Sunilkumar VCS
3 pages
Gartner Reprint - Object Storageoct21
No ratings yet
Gartner Reprint - Object Storageoct21
20 pages
Netapp Backup Snapcreator
No ratings yet
Netapp Backup Snapcreator
68 pages
Eternus Ab Series
No ratings yet
Eternus Ab Series
107 pages
AltaVault Deployment Guide Updated PDF
No ratings yet
AltaVault Deployment Guide Updated PDF
58 pages
Cloud Stack
No ratings yet
Cloud Stack
127 pages
How Oracle Saved A Billion Dollars - The IT Story
100% (1)
How Oracle Saved A Billion Dollars - The IT Story
44 pages
FAS Series Data Sheet
No ratings yet
FAS Series Data Sheet
5 pages
Qs Ds XN22 (En)
No ratings yet
Qs Ds XN22 (En)
7 pages
Netapp Storage Deployment Guide: Smart Business Architecture Data Center
No ratings yet
Netapp Storage Deployment Guide: Smart Business Architecture Data Center
27 pages
Snapshot Management For NAS Devices Integration Guide
No ratings yet
Snapshot Management For NAS Devices Integration Guide
104 pages
NEtApp ASA C250 en
No ratings yet
NEtApp ASA C250 en
6 pages
L2 Requirements Example
No ratings yet
L2 Requirements Example
4 pages
Huawei Storage Sales Training Guide
No ratings yet
Huawei Storage Sales Training Guide
41 pages
Case NETAPP AND THE CHALLENGE OF GLOBAL LEADERSHIP PDF
No ratings yet
Case NETAPP AND THE CHALLENGE OF GLOBAL LEADERSHIP PDF
18 pages
Case Studies - Chapter 3.3
100% (1)
Case Studies - Chapter 3.3
30 pages
SAP HANA Developer Quick Start Guide en
No ratings yet
SAP HANA Developer Quick Start Guide en
57 pages
Cloning Oracle E Business Suite Release 12.2 RAC Enabled Systems With Rapid Clone (Doc ID 1679270.1)
No ratings yet
Cloning Oracle E Business Suite Release 12.2 RAC Enabled Systems With Rapid Clone (Doc ID 1679270.1)
20 pages
10 Crowdsourced Analyst Firms' Alternatives
No ratings yet
10 Crowdsourced Analyst Firms' Alternatives
3 pages
CR-3-536 Clustered Data ONTAP Network Infrastructure
No ratings yet
CR-3-536 Clustered Data ONTAP Network Infrastructure
52 pages
Veeam Backup Tool
No ratings yet
Veeam Backup Tool
18 pages
NetApp Command Cheat Sheet
No ratings yet
NetApp Command Cheat Sheet
2 pages
Pawan Patidar
No ratings yet
Pawan Patidar
5 pages
Top IT Service Providers Guide
No ratings yet
Top IT Service Providers Guide
55 pages
RS25866 - 18600 - DC Brochure Design-Update - RZ
No ratings yet
RS25866 - 18600 - DC Brochure Design-Update - RZ
24 pages
Session Slides
No ratings yet
Session Slides
20 pages
Senior SAN Storage Engineer Resume
No ratings yet
Senior SAN Storage Engineer Resume
5 pages
DS 2932 ONTAP System Manager Datasheet
No ratings yet
DS 2932 ONTAP System Manager Datasheet
2 pages
Data ONTAP® 7.3 Commands - Manual Page Reference, Volume 1
No ratings yet
Data ONTAP® 7.3 Commands - Manual Page Reference, Volume 1
648 pages
STRSW ILT D8CADM REV03 - LabSetupGuide
No ratings yet
STRSW ILT D8CADM REV03 - LabSetupGuide
8 pages