Veeam Backup 11 0 Storage Integration User Guide

Veeam Backup & Replication
Version 11
Integration with Storage Systems Guide
November, 2021
© 2021 Veeam Software.
All rights reserved. All trademarks are the property of their respective owners.
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 intelle ctual
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
Read the End User Software License Agreement before using the accompanying software programs. Using
any part of the software indicates that you accept the terms of the End User Software License Agreement.
2 | V eeam Backup & Replication | Integration with Storage Systems Guide

Contents
CONTACTING VEEAM SOF TWARE ................................ ................................ ........................... 4
ABOUT THIS DOCUMENT ................................ ................................ ................................ ..... 5
INTEGRATION WITH STORAGE SYSTEMS ................................ ................................ ................... 6
VMware Integration .............................................................................................................................. 7
Backup from Storage Snapshots.................................................................................................. 11
Backup from Cisco HyperFlex Snapshots .................................................................................... 26
Snapshot Orchestration ............................................................................................................. 33
Backup from Storage Snapshots with Snapshot Retention ...........................................................40
Veeam Explorer for Storage Snapshots....................................................................................... 44
Creating and Deleting Snapshots ...............................................................................................117
NAS Integration ................................................................................................................................. 119
NAS File Share Back up from Storage Snapshots .........................................................................120
Veeam Agent Integration ................................................................................................................... 122
Backup Infrastructure for Storage Integration ..................................................................................... 123
Configuring Backup Proxy for Storage Integration ..................................................................... 124
Adding Storage Systems ........................................................................................................... 126
Rescanning Storage Systems .................................................................................................... 219
Removing Storage Systems ......................................................................................................223
Requirements and Limitations ........................................................................................................... 224
System Requirements ..............................................................................................................225
Required Permissions .............................................................................................................. 229
General Limitations ................................................................................................................. 236
Cisco HyperFlex Limitations ..................................................................................................... 239
Dell EMC VNXe, VNX, SC Limitations ........................................................................................ 240
NetApp Data ONTAP/Lenovo Thinksystem DM Limitations ........................................................ 242
Universal Storage API Integrated Systems ...........................................................................................253
Prerequisites for API Integrated Systems .................................................................................. 254
Installing Storage System Plug-Ins............................................................................................255
Update Notifications ................................................................................................................257
On-Demand Sandbox for Storage Snapshots ...................................................................................... 258

Contacting Veeam Software
At Veeam Software we value 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, visit the Veeam Customer Support Portal 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 office locations, visit the Veeam Contacts
Webpage.
Online Support
If you have any questions about Veeam products, you can use the following resources:
• Full documentation set: veeam.com/documentation-guides-datasheets.html
• Veeam R&D Forums: forums.veeam.com

About This Document
This user guide provides information about integration, main features, and use of Veeam Backup & Replication
with storage systems. The document applies to version 9.5 Update 4 and all subsequent versions until it is
replaced with a new edition.
Intended Audience
The user guide is intended for anyone who wants to build the data protection and disaster recovery strategy
using Veeam Backup & Replication and storage systems that host VM disks. It is primarily aimed at backup
administrators, consultants, analysts and any other IT professionals using the product.

Integration with Storage Systems
To build the data protection and disaster recovery strategy, you can use the capabilities of native snapshots
created on production storage systems.
Integration with storage systems in Veeam Backup & Replication offers the following options:
• VMware integration
• NAS integration
• Veeam Agent for Microsoft Windows integration

VMware Integration
To build the data protection and disaster recovery strategy, you can use the 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 Orchestration. You can configure backup jobs to periodically create storage snapshots on
primary and/or secondary storage arrays.
• Backup from Storage Snapshots with Snapshot Retention. You can configure backup jobs to create backup
files in the backup repository and, additionally, storage snapshots on the 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.
Depending on the storage system type, you can perform the following operations:
Op erati Dell HP E HP E HP E NetApp Cisco IBM Univers

on/ E MC 3P AR StoreVirtual/LeftHand/ Nimb FAS/AFF, Hy p erF FlashSyst al
Storage Unity StoreSe P 4000 series le FlexArray lex em Storage
Ty p e XT/Uni rv, HPE ( V- ( StorWiz AP I
ty , P rimera Series), e) , IBM Integrat
VNX(e) Fujitsu SVC, ed
E TE RNUS Lenovo Sy stem
HX/AX, Storage s
IBM N V Series
series,
Lenovo
ThinkSyst
em DM
Series
Ba ckup from Storage Snapshots
Backup
from
primary ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
storage
arrays

HX/AX, Storage s
IBM N V Series
series,
Lenovo
ThinkSyst
em DM
Series
Backup
from
seconda
✕ ✓1 ✕ ✓1 ✓1 ✕ ✓1 ✕
ry
storage
arrays
Veeam Explorer from Storage Snapshots
Restore
from
primary ✓ ✓ ✓ ✓ ✓ ✕ ✓ ✓
storage
arrays
Restore
from
seconda
✓ ✓ ✓ ✓ ✓ ✕ ✓ ✓3
ry
storage
arrays
Sna pshot Orchestration
Snapsh
ot-only
job for
✕ ✓ ✕ ✓ ✓ ✕ ✓ ✓
primary
storage
arrays

HX/AX, Storage s
IBM N V Series
series,
Lenovo
ThinkSyst
em DM
Series
Snapsh
ot-only
job for
seconda ✕ ✓1 ✕ ✓1 ✓1 ✕ ✓1 ✕
ry
storage
arrays
Ba ckup from Storage Snapshots with Snapshot Retention
Backup
job with
snapsho
t
retentio ✕ ✓ ✕ ✓ ✓ ✕ ✓ ✓
n on
primary
storage
arrays
Backup
job with
snapsho
t
retentio
✕ ✓1 ✕ ✓1 ✓1 ✕ ✓1 ✕
n on
seconda
ry
storage
arrays
Other Operations
Storage
✓ ✓ ✓ ✓ ✓ ✓2 ✓ ✓
rescan

HX/AX, Storage s
IBM N V Series
series,
Lenovo
ThinkSyst
em DM
Series
Snapsh
ot
creation
and ✓ ✓ ✓ ✓ ✓ ✕ ✓ ✓
deletion
(manual
)
1
Storage snapshot technology:
• HPE 3PAR StoreServ – periodic remote copy and snapshot creation on Peer Persistent target
• HPE Nimble – snapshot replication
• Net App FAS and AFF Series, FlexArray (V Series), Fujitsu ETERNUS HX/AX, IBM N series, and Lenovo ThinkSystem DM
Series – snapshot replication with SnapMirror/SnapVault
• IBM FlashSystem (StorWize), IBM SVC, Lenovo Storage V Series – snapshot creation on HyperSwap target
2
Infrastructure only
3
Contact vendor to check compatibility and storage system configuration

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.
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. 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. 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.

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.
Backup from Primary Storage Arrays

To use Backup from Storage Snapshots, you must select the E na ble 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. Analyzes which VMs in the job host their disks on the storage system. Checks the backup infrastructure
and detects if there is a backup proxy that has a direct connection to the storage system.
2. Triggers the vCenter Server to create VMware vSphere snapshots for these VMs.
3. Gets Changed Block Tracking information for VMs hosted on the storage system.
4. Instructs the storage system to create a snapshot of the storage volume or LUN that hosts VM disks and
VMware vSphere snapshots.
5. Instructs the vCenter Server to remove VMware vSphere snapshots on the production storage system. The
'cloned' VMware vSphere snapshots remain on the created storage snapshots.
6. Mounts the storage snapshot as a new volume to this backup proxy.
7. Reads and transports VM data blocks through 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.
8. 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 the regular data processing mode 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 RP Os.
Before you perform Backup from Storage Snapshots, check the following prerequisites:
• You must install the Enterprise Plus edition of Veeam Backup & Replication 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 ESXi hosts with VMs 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. Otherwise, Veeam Backup & Replication may fail over to the regular data processing
mode. To ensure failover to the regular data processing mode in case Veeam Backup & Replication does
not detect a backup proxy, at the Storage step of the backup or replication job wizard, click Ad vanced and
select the Fa ilover to standard backup check box.
The Fa ilover to standard backup option will also work if Veeam Backup & Replication fails to create
storage snapshots for the storage volumes. As a result, all VMs residing on the volumes will be processed
by regular data processing mode.
2. At the Storage step of the wizard, click Ad vanced, then click the Integration tab. Make sure that the
E na ble 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 multiple VMs whose disks are hosted on the same volume or LUN, select the Limit
p rocessed VM count per storage snapshot to <N> check box and specify the number of VMs for which one
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.
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 a rrays if you have the following storage systems in
the production environment:
• HPE Primera or HPE 3PAR with Remote Copy (Asynchronous) or Peer Persistence
Note: For Remote Copy, only asynchronous periodic replication mode is supported.
• IBM Spectrum Virtualize with HyperSwap
• Lenovo V Series with HyperSwap
• HPE Nimble arrays with replicated copies
• NetApp SnapMirror and/or NetApp SnapVault

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.
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 analyzes which VMs in the job host their disks on the storage system and
checks the backup infrastructure to detect if there is a backup proxy that has a direct connection to the
storage system.
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. The transported storage snapshot is mounted to the detected 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 HPE Nimble] On HPE 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.
• [For NetApp] 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.
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 Fa ilover 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.
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 run the backup job, 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 HPE Nimble] You must configure Volume Collection replication from the primary storage array to
the secondary storage array. For more information, see the HPE Nimble documentation.
o [For NetApp] You must configure volume SnapMirror/SnapVault relationships between the primary
and secondary storage arrays. MirrorAndVault Relationships will be identified by
Veeam Backup & Replication as SnapVault. For more information, see the NetApp 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 hosts or ESXi hosts 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] You must add IBM Spectrum Virtualize
storage system to the backup infrastructure, and select secondary storage volumes as a data source
for backup using registry keys. For more information, contact Veeam Customer Support.
IMP ORTANT
When you add storage 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, do the following:
a. 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 may fail over to the regular data processing mode. To
switch on the failover, at the Storage step of the backup or replication job wizard, click
Ad vanced and select the Fa ilover to standard backup check box.
For more information, see Adding Storage Systems.
b. From the Ba ckup repository list, select a backup repository where you want to store backup files.
c. In the Retention policy section, specify the number of backup restore points that you want to keep.

d. Select the Configure secondary destinations for this job check box.
e. Click Ad vanced, then click the Integration tab. Make sure that the E nable backup from storage
sna pshots check box is selected. By default, this option is enabled for all newly created jobs.
f. If you add to the job many VMs whose disks are located on the same volume or LUN, select the Limit
p rocessed 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.
g. 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 Fa ilover to standard backup check box.

h. 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 Fa ilover 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.
2. At the Secondary Target step of the wizard, click Ad d and select a secondary storage array. For example,
Nimb le Snapshot Replicated Copy.
a. In the Numb er 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 NetApp SnapMirror. On this secondary storage system,
Veeam Backup & Replication maintains the same number of storage snapshots as on primary storage
arrays.

b. Select the Use as the data source check box.
3. Specify other backup job settings as required.
4. Click Nex t, then click Finish to save the job settings.
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 p er 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
p er 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.

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 ESXi 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.

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 the System Requirements
section in Veeam Backup & Replication User Guide.
• Veeam Backup & Replication 9.5 Update 2 or later 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 E nable backup from storage snapshots option is selected in the job settings (default setting). For
more information, see Configuring Backup from Cisco HyperFlex Snapshots.
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 ESXi hosts. In this
mode, Veeam Backup & Replication bypasses the ESXi 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, see this Veeam KB
article.
• VMs do not have Cisco HyperFlex snapshots (including the base snapshot) or VMware vSphere snapshots.
• VMs meet requirements described in the Direct NFS Access section of the Veeam Backup & Replication
User Guide.

• 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 the Veeam Backup & Replication User
Guide.
• 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:
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.
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:
• Ba ckup from Storage Snapshots over IO Visor on ESXi 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 ESXi 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.

• Ba ckup 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 use one of the following ways for Cisco HyperFlex version below 3.0:
• 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 this Veeam KB article.
• Use a predefined VMware ESXi host extension VIB file from the Veeam Community GitHUB project. For
more information, see this Veeam KB article.
• Use ESXi command line interface to create a temporary firewall rule (until the next ESXi host reboot). For
more information, see this Veeam KB article.
For HyperFlex clusters running HX Data Platform 3.0 or later, use the procedure described in this Veeam KB
article.
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 of the
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 this VMware KB article. 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.
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:
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.
2. At the Storage step of the wizard, click Ad vanced, then click the Integration tab. Make sure that the
E na ble backup from storage snapshots check box is selected. By default, this option is enabled for all
newly created jobs.

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
Fa ilover to standard backup check box.
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 ESXi 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 this Veeam
KB article.

Snapshot Orchestration
Veeam Backup & Replication lets you perform Snapshot Orchestration — build a snapshot chain on primary
and/or secondary storage arrays. To create snapshots on storage arrays, you must run a snapshot -only job.
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 in the backup repository. It creates only storage
snapshots on the storage system by a schedule that is defined in the job settings.
Depending on the backup job settings, the created snapshots ca n 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.
Before you configure a snapshot-only job, check the licensing terms for storage arrays.
Snapshot-only jobs on the primary storage arrays are available on any license edition.
Licensing for snapshot-only jobs on the secondary storage arrays depends on the used storage system.
License NetApp NetApp HP E HP E Primera or IBM Lenovo V HP E

E d ition/ Sna pMirro Sna pVaul P rimera or HP E 3PAR with Sp ectrum Series with Nimb le
Storage r t HP E 3PAR Remote Copy Virtualize Hy p erSwa a rrays
Sy stem with P eer ( Asynchronous with p with
P ersistenc ) Hy p erSwa rep licate
e p d cop ies
E nterpris ✓ ✕ ✓ ✕ ✓ ✓ ✕
e

License NetApp NetApp HP E HP E Primera or IBM Lenovo V HP E
E d ition/ Sna pMirro Sna pVaul P rimera or HP E 3PAR with Sp ectrum Series with Nimb le
Storage r t HP E 3PAR Remote Copy Virtualize Hy p erSwa a rrays
Sy stem with P eer ( Asynchronous with p with
P ersistenc ) Hy p erSwa rep licate
e p d cop ies
E nterpris ✓ ✓ ✓ ✓ ✓ ✓ ✓
e P lus
To configure a snapshot-only job:
1. Open the Home view.
2. Click Ba ckup Job > VMware or vCloud on the ribbon. Veeam Backup & Replication will launch the New
Ba ckup Job wizard.
3. At the Na me step of the wizard, specify a name and description for the backup job.
4. At the Virtual Machines step of the wizard, click Ad d 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 Ba ckup repository list.
In the Retention policy field, 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 chain (if it does not contain any
restore points that fall under the retention period).
Mind that the number of snapshots in the snapshot chain on the primary storage array cannot be fewer
than 1. Even if you set the Retention policy value to 0, Veeam Backup & Replication will keep 1 snapshot in
the snapshot chain.

If you want to additionally create storage snapshots on the secondary storage array, select the Configure
secondary destinations for this job check box.
6. If you have enabled a secondary destination for the job, at the Secondary Target step of the wizard, click
Ad d and select the secondary storage array for a secondary location.
[For secondary storage arrays] In the Numb er 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 (if it does not contain any restore points that fall under the retention
period).
[For NetApp SnapMirror] The Numb er of snapshot copies to retain option is not applicable to NetApp
SnapMirror. On this secondary storage system, Veeam Backup & Replication maintains the same number of
storage snapshots as on primary storage systems. MirrorAndVault Relationships will be identified by
Veeam Backup & Replication as SnapVault.
[For NetApp 7-mode] 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.

[For HPE 3PAR] The number of snapshot copies to retain option is not applicable to HPE 3PAR Peer
Persistence.
7. 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 E na ble VMware
Tools quiescence check box.

Veeam Backup & Replication will 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 Specify Advanced Backup Settings section in
8. You can enable application-aware processing to create a transactionally consistent backup. To do so,
select the E na ble application-aware processing check box at the Guest Processing step of the wizard.
Specify necessary settings for application-aware image processing. For more information on settings, see
the Specify Guest Processing Settings section in Veeam Backup & Replication User Guide.
If you are going to process logs, set a repository for storing them. To do so, after you've selected the
E na ble application-aware processing check box, click Ap p lications. Select any VM and click E d it. In the
P rocessing Settings window, select SQL (for Microsoft SQL VMs) or Ora cle (for Oracle VMs). Select Ba ckup
log s periodically (for Microsoft SQL VMs) or Ba ckup logs every N minutes (for Oracle VMs). Ba ckup
rep ository field will appear. Choose the backup repository from the dropdown list.
Keep in mind that by doing this you are setting the backup repository for the whole job, not just for the
VM you've selected.

For more information on log settings, see the Microsoft SQL Server Transaction Log Settings (for Microsoft
SQL VMs) or Oracle Archived Log Settings (for Oracle VMs) sections in the Veeam Backup & Replication
User Guide.
9. During the backup job session, Veeam Backup & Replication will quiesce applications running inside VMs
using application-aware processing. For more information on how application-aware processing works, see
the Application-Aware Processing section in Veeam Backup & Replication User Guide.
Backup job session flow:
o Veeam Backup & Replication quiesces applications running inside VMs using application-aware
processing (performs VSS freeze).
o After applications inside the VM are quiesced, Veeam Backup & Replication creates a VMware
snapshot. This does not apply to freeze-only VMs.
A VM is freeze-only if it meets these conditions:
▪ The disks of this VM can be located on one or more storage volumes,
▪ These storage volumes only contain the disks of this VM. They do not contain the disks of any
other VM that are included in the same backup job.
o Then Veeam Backup & Replication triggers a storage snapshot.
The freeze-only VMs (those VMs for which a VMware snapshot was not created) are processed in
successive order after creating storage snapshots for the other VMs.

NOTE
[For Nimble and HPE 3PAR] Freeze-only processing is not supported if replication is switched on for
the volume. In this case, Veeam Backup & Replication will fail over to VMware Snapshot processing.
10. At the Schedule step of the wizard, select the Run the job a utomatically check box and specify the
schedule by which storage snapshots must be created. For more information, see the Define Job Schedule
section in the Veeam Backup & Replication User Guide.
11. At the Summary step of the wizard, review settings of the added storage system. Select the Run the job
when I click Finish check box if you want to start the job right after you finish working with the wizard.
Click Finish to save the backup job settings.
TIP
To learn which VMs were processed by a snapshot job (a snapshot-only job or a backup job with storage
snapshot retention) open the Storage Infrastructure view and navigate to the necessary storage snapshot.
If a VM was processed by a snapshot job, Veeam Backup & Replication displays the job name in the
P rotected by column.

Backup from Storage Snapshots with Snapshot
Retention
You can configure a backup job to create regular backup files in 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
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 the vCenter Server to create a VMware vSphere snapshot for a VM.
2. Veeam Backup & Replication instructs the storage system to create two snapshots of a volume or LUN
capturing VM disks:
o A new snapshot on the storage system. This snapshot remains in the snapshot chain until it is
removed by the retention policy.
o A temporary snapshot for backup or replication operations. This snapshot is removed after backup or
replication is complete.
3. Veeam Backup & Replication removes the created VMware vSphere snapshot from the VM snapshot list.
4. Veeam Backup & Replication uses the temporary storage snapshot as a data source for backup and
replication.
5. Veeam Backup & Replication performs cleanup operations and removes the temporary snapshot on the
storage array.

6. Veeam Backup & Replication checks the number of storage snapshots in the snapshot chain. If the number
exceeds the value defined in retention policy settings, Veeam Backup & Replication instructs the storage
system to remove the earliest snapshot from the snapshot chain.
Configuring Backup Jobs with Storage Snapshot Retention

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 backup, configure the backup infrastructure in a proper way:
• [For HPE Nimble] You must configure Volume Collection replication from the primary storage array to the
secondary storage array. For more information, see the HPE Nimble documentation.
• [For HPE 3PAR Peer Persistence and HPE 3PAR Remote Copy] You must create a Remote Copy Group
(RCG) with relevant type (Synchronous or Periodic).
• [For NetApp] You must configure volume SnapMirror/SnapVault relationships between the primary and
secondary storage arrays. MirrorAndVault Relationships will be identified by Veeam Backup & Replication
as SnapVault. For more information, see the NetApp documentation.
To configure a backup job:
2. Click Ba ckup Job > VMware or vCloud on the ribbon. Veeam Backup & Replication will launch the New
Ba ckup Job wizard.
3. At the Na me 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 Ba ckup repository list select a backup repository where you
want to store backup files.
6. In the Retention p olicy 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 Ad d and select primary or secondary storage arrays to
create snapshots.
9. In the Numb er 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 (if it does not contain any
restore points that fall under the retention period). Mind that the number of snapshots in the sna pshot
chain on the primary storage array cannot be fewer than 1.
[For NetApp SnapMirror] The Numb er of snapshot copies to retain option is not applicable to NetApp
SnapMirror. On this secondary storage system, Veeam Backup & Replication maintains the same number of
storage snapshots as on primary storage systems. MirrorAndVault Relationships will be identified by
Veeam Backup & Replication as SnapVault.
[For NetApp 7-mode] 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.

[For HPE 3PAR] The number of snapshot copies to retain option is not applicable to HPE 3PAR Peer
Persistence.
10. Specify other backup job settings as required.
11. Click Nex t, then click Finish to save the job settings.
TIP
To learn which VMs were processed by a snapshot job (a snapshot-only job or a backup job with storage
snapshot retention) open the Storage Infrastructure view and navigate to the necessary storage snapshot.
If a VM was processed by a snapshot job, Veeam Backup & Replication displays the job name in the
P rotected by column.

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 second s.
You can use Veeam Explorer for Storage Snapshots to perform the following restore operations:
• Instant Recovery
• Instant Disk 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
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. If restore from storage snapshots is performed manually,
an administrator must do the following:
1. Present a storage snapshot to an ESXi host.
2. Perform an HBA rescan.
3. Mount the storage snapshot to an ESXi 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 ESXi hosts.
You only need to select an ESXi 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.
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 Recovery,
the ESXi 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 a VM on the storage snapshot.
2. Veeam Backup & Replication triggers the storage system to create a copy or a clone of this storage
snapshot.
o 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.
o If you start several restore operations (for example, Instant 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 ESXi host in the virtual environment, and the created snapshot copy is presented to
this ESXi host as a new volume. The ESXi host is added to the list of Allowed Servers for the snapshot
copy. As a result, the ESXi host has access to the snapshot copy and can read and write d ata to/from it.
4. [For iSCSI protocol] Veeam Backup & Replication makes sure that the IP address of the storage system is in
the list of static targets on the ESXi host.
[For iSCSI and FC protocols] The storage system issues an HBA rescan command to the vCenter Server.
Once rescan is finished, the snapshot copy appears in the discovered targets list on the ESXi host. After
that, the storage system performs re-signature for storage volumes.
[For NFS protocol] The datastore gets registered on the ESXi host through the IP address or FQDN + share
name.
5. The user performs necessary restore operations in the Veeam Backup & Replication console.

6. After restore is completed, Veeam Backup & Replication issues a command to the storage system. The
storage system deletes the snapshot copy from the ESXi host and performs cleanup operations.
Performing Instant Recovery

You can instantly recover a VM from a storage snapshot without prior de-staging and intermediate restores.
Instant Recovery accelerates VM restore, improves RTOs and decreases downtime of production VMs.
Before you perform Instant Recovery, check prerequisites. Then use the Instant Recovery wizard to restore a VM
from a storage snapshot.
Before You Begin

Before you perform Instant 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 ESXi host, you must register the ESXi 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. For more information, see Required Licenses for NetApp.

Step 1. Launch Instant Recovery Wizard
To launch the Instant Recovery wizard, do one of the following:
• On the Home tab, click Restore > VMware vSphere > Restore from backup > Entire VM restore > Instant
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
recovery on the ribbon. You can also right-click a VM and select Instant recovery.
• Open the Home view. In the inventory pane, select Ba ckups > Snapshots. In the working area, expand the
necessary backup and do one of the following:
o Select the VM that you want to restore and click Instant recovery on the ribbon.
o Right-click the VM that you want to restore and select Instant recovery.
You can select multiple VMs. To do so, hold [Ctrl] or [Shift] key and select the necessary VMs in the working
area. After that, click Instant Recovery on the ribbon. You can also right-click the selected VMs and select
Instant Recovery.
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 Sta rt search button on the right or press [E NTER].

Step 2. Select VM
At the Ma chines step of the wizard, select one ore more VMs that you want to restore.
1. In the Ma chines to restore list, you can add or remove VMs. Click Ad d to add more VMs to restore. Click
From infrastructure to select VMs from your storage infrastructure, or By wildcard to select VMs using a
wildcard character. Click Remove to remove VMs from the list.
To quickly find a VM, you can use the search field. Enter the VM name or a part of it, and the relevant VM
will appear.
2. Click P oint to select a restore point from which you want to restore the VMs. Every storage snapshot acts
as an independent restore point.

Step 3. Select Restore Mode
At the Restore Mode step of the wizard, specify the destination settings for recovered VMs.
1. Choose the restore mode:
o Select Restore to the original location if you want to restore the VMs with their initial settings to its
original location. If you select this option, you will pass directly to the Restore Reason step of the
wizard.
o Select Restore to a new location, or with different settings if you want to restore the VMs to a
different location and/or with different settings. If you select this option, the Instant Recovery wizard
will include additional steps for customizing the VMs settings.
2. Select the Restore VM tags check box if you want to restore tags that were assigned to the original VM,
and assign them to the restored VM. Veeam Backup & Replication will restore the VM with original tags if
the following conditions are met:
o The VM is restored to its original location.
o The original VM tag is still available on the source vCenter Server.

Step 4. [For Multiple VMs] Select Host
Select a host to recover the VMs to.
1. Click Host and select one of the list. To quickly find a host or a cluster, you can use the search field at the
bottom of the window. From the drop-down list to the left of the field, choose Cluster or Host. Then enter
the cluster or host name or a part of it and click the Sta rt search button on the right or press [E NTER].
2. After that, click P ool to select the resource pool to recover the VMs to.
You can apply changes to each VM separately or to multiple VMs in bulk .

Step 5. [For Multiple VMs] Select Folder
Select a folder to recover the VMs to. To do it, select the necessary VM and click Folder. You can keep the folder
selected by default.
You can apply changes to each VM separately or to multiple VMs in bulk.

Step 6. [For Single VM] 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 single
recovered VM.
Select a destination for the recovered VM:
1. 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 ESXi 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.
2. 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 ESXi host and start the VM on this
ESXi host.
3. In the VM folder field, select a folder to which you want to place the recovered VM.
4. In the Resource p ool list, select a resource pool to which you want to place the recovered VM.
5. You can also customize the machine BIOS UUID. To do it, click Ad vanced and select either P reserve BIOS
UUID or Generate new BIOS UUID .

Step 7. Specify Restore Reason
At the Restore Reason step of the wizard, enter a reason for performing Instant Recovery. The information you
provide will be saved in the session history, and you will be able to view it later.
If you do not want to see this step in future, select the Do not show me this page again check box.

Step 8. Verify Instant Recovery Settings
At the Summary step of the wizard, specify additional settings for Instant 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 P ower on target VM after restoring 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 Recovery settings and click Finish. Veeam Backup & Replication will restore the VM on the
selected ESXi host.

Step 9. Finalize Instant Recovery
All currently running Instant Recovery sessions are displayed in the Home view, under the Instant Recovery
node.
To check the progress of an Instant Recovery session and view session details:
2. In the inventory pane, click the Instant Recovery node.
3. In the working area, right-click the VM and select P roperties.
Alternatively, you can open the History view, select the Instant Recovery node under Restore in the inventory
pane and double-click the instant VM restore session.
After the VM has been successfully recovered, you can finalize Instant Recovery in one of two ways:
• Migrate the restored VM to the production environment
• Unpublish the recovered VM
Migrating Instantly Restored VMs

To migrate a recovered VM to the production environment:
2. In the inventory pane, select the Instant Recovery node.
3. In the working area, right-click the VM and select Mig rate to production. Veeam Backup & Replication will
launch the Quick Migration wizard.
During migration, Veeam Backup & Replication will restore the VM from the backup file and additionally
move all changes that were made while the VM was running from the backup in the Instant Recovery
mode.
TIP
When you pass through the Quick Migration wizard, enable the Delete source VM files upon successful
mig ration option. Veeam Backup & Replication will restore the VM to production and automatically stop
the Instant VM recovery session. If you do not enable this option, the Instant VM recovery session will still
be running, and you will need to unpublish the recovered VM manually.
Unpublishing Instantly Restored VMs

If you have disabled the Delete source VM files upon successful migration option in the Quick Migration
settings, you must unpublish the VM manually. After you unpublish the VM, the Instant Recovery ses sion will
end and the recovered VM will be unmounted from the vPower NFS server. The migrated VM will remain on the
production environment.
To unpublish a recovered VM:
2. In the inventory pane, select the Instant Recovery node.
3. In the working area, right-click the VM and select Stop publishing.

TIP
After the VM has been published from the backup, you can open the VM console directly from
Veeam Backup & Replication. To do this, in the working area right-click the VM and select Op en VM
Console.
Performing Instant Disk Recovery

You can instantly recover a VM disk from a storage snapshot without prior de-staging and intermediate restores.
Instant Disk Recovery accelerates VM restore, improves RTOs and decreases downtime of production VMs.
NOTE
First Class Disks (FCD) are not supported for Instant Disk Recovery from storage snapshots.
To restore a VM disk from a storage snapshot, use the Instant Disk Recovery wizard.

Step 1. Launch Instant Disk Recovery Wizard
To launch the Instant Disk Recovery wizard, do one of the following:
• 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
Disk Recovery on the ribbon. You can also right-click a VM and select Instant disk recovery.
• Open the Home view. In the inventory pane, select Ba ckups > Snapshots. In the working area, expand the
necessary backup and do one of the following:
o Select the VM that you want to restore and click Instant disk recovery on the ribbon.
o Right-click the VM that you want to restore and select Instant disk recovery.

Step 2. Select VM
At the Virtual Machine step of the wizard, select a VM whose disks you want to restore.
To quickly find a VM, you can use the search field. Enter the VM name or a part of it, and the relevant VM will
appear in the list.

Step 3. Select Restore Point
At the Restore P oint step of the wizard, specify the restore point from which to restore the disk. Select from the
list of available restore points.

Step 4. Specify Mapping
At the Disk Mapping step of the wizard, select the target virtual machine. To do it, click Choose and select from
the list of available virtual machines.
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 Sta rt search button on the right or press [Enter].
If you wish to select a virtual device node where to map the disk, select a disk in the list and click Cha nge. Select
the virtual device node from the drop-down list.

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

Step 6. Verify Instant Disk Recovery Settings
At the Summary step of the wizard, check Instant Disk Recovery settings and click Finish.
Veeam Backup & Replication will restore the disk on the selected ESXi host.
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 ESXi host in the virtual environment.
Veeam Backup & Replication creates a clone of the storage snapshot on which the VM disks are hosted, and
mounts the clone to the selected ESXi host as a new datastore.
Veeam Backup & Replication accesses the configuration file of the VM (VMX) on the mounted clone and uses
this configuration file to register a temporary VM on the ESXi 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 loca tion,
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:
• If you plan to restore VM guest OS files to their original location, you must make sure that VMwa re 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 or later.
• If you plan to restore files from a VM running Microsoft Windows Server 2012 or 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 or later. Data Ded uplication must be enabled on this
machine.
of LUNs to the ESXi host, you must register the ESXi host with a WWN ID on the storage system.

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 > Restore from backup > Guest files restore >
Microsoft 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
W ind ows 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
W ind ows 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 Sta rt search button on the right or press [E NTER].

Step 2. Select VM
At the Ma chine 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.
it and click the Sta rt search button on the right or press [E NTER].

At the Restore P oint step of the wizard, select a restore point for the VM. Every storage snapshot acts as an
independent restore point.

Step 4. Select ESXi Host for Snapshot Mounting
At the Loca tion step of the wizard, select an ESXi host to which the clone/virtual copy of the storage snapshot
will be mounted. On the selected ESXi 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 Loca tion step of the wizard, click Customize.
2. Next to the Host field, click Choose and select an ESXi 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.

At the Rea son 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 6. Save Restored Files
At the Summary step of the wizard, click Browse 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.
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 store the
restored file in the same folder where the original file resides.
If the file with the RESTORED- prefix already exists in the original location, Veeam Backup & Replication
will name the restored file in the following format: RESTORED-<filename>__YYYYMMDD_HHMMSS.

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 P reserve 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 P reserve 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.
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 d atabase
file (DIT) in the Veeam Backup browser, select it and click Ap p lication 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 (E DB) in
the Veeam Backup browser, select it and click Ap p lication 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 Ap p lication 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 Ap p lication Items > SQL Server Databases on the Home tab or
double-click the Microsoft SQL Server database file. For more information, see Microsoft Docs.
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 E x plore on the ribbon or right-click the necessary folder and select
E x plore.
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 Sta rt 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 Ca ncel 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.
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. For the full
list of supported file systems, see the Platform Support section of the in the Veeam Backup & Replication User
Guide.
To restore files from VM guest OS, Veeam Backup & Replication uses a helper appliance. The helper appliance is
a helper VM running a stripped down Linux kernel that has a minimal set of components. The appliance is quite
small — around 50 MB. It requires 1024 MB RAM and takes around 10 –20 seconds to boot.
When you perform file-level restore, Veeam Backup & Replication does the following:
1. On an ESXi host in your virtual environment, Veeam Backup & Replication creates a clone/virtual copy of
the storage snapshot on which the VM disks are hosted. Veeam Backup & Replication mounts the
clone/virtual copy to the selected ESXi host as a new datastore.

2. Veeam Backup & Replication copies an ISO of the helper appliance to the datastore and starts the helper
appliance.
3. Veeam Backup & Replication mounts the restored VM disks to the helper appliance as virtual hard drives.
VMDK files are mounted directly from storage snapshots.
4. After disks are mounted, Veeam Backup & Replication launches the Veeam Backup browser where
mounted VM disks are displayed. In the browser, you can restore files and folders to their original location,
local machine drive or save them in a network shared folder.
5. When you restore files or folders, the mount server connects to the VM over network or VIX API/vSphere
Web Services if a connection over the network cannot be established.
6. When the restore process is finished, Veeam Backup & Replication deletes the datastore, unmounts the
clone/virtual copy from the ESXi host and then deletes this copy.
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:
• 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.
• The mount server, whether it is a helper host or a helper appliance, must have access over a network to a
VM whose files you restore or direct access to vCenter or ESXi host where the VM resides. If the mount
server is connected to a VM whose files you restore via VIX API/vSphere Web Services, you must use a root
account for a target VM, otherwise the restore process will fail.
• For Linux target VM, mind the following:
o If you want to restore files over network, make sure that the SSH daemon is configured and SCP utility
is available on the target VM.
o SELinux must be disabled on the target VM.
o A range of ports that are used for data transfer must be open on the target VM.
For more information on configuring connection settings for Linux servers, see the Specify Credentials
and SSH Settings step of the New Linux Server wizard in the Veeam Backup & Replication User Guide.
of LUNs to an ESXi host, you must register the ESXi host with a WWN ID on the storage s ystem.

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 > Restore from backup > Guest files restore >
Linux and other.
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 Ready step of the wizard.
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.

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.

At the Restore P oint step of the wizard, select a restore point for the VM. Every storage snapshot acts as an
independent restore point.

Step 4. Review Restore Settings
At the Rea dy step of the wizard, review the restore settings. Here you can select an ESXi host to which the
clone/virtual copy of the storage snapshot will be mounted. On the selected ESXi host,
Veeam Backup & Replication will also place a helper appliance and mount disks of the restored VM to this helper
appliance.
To specify a destination for the snapshot clone/virtual copy and helper appliance:
1. Click the Customize link at the bottom of the window.
2. In the Host field of the FLR Appliance Configuration window, select an ESXi host to which the snapshot
clone must be mounted and on which the helper appliance must be registered.
3. In the Resource p ool field, specify a resource pool to which you want to place the helper appliance.
4. Select a network for the helper appliance:
a. On the right of the Network field, click Choose.
b. In the Select Network window, Veeam Backup & Replication will display a list of networks to which
the specified host is connected.
Mind that the backup server and the mount server must have access to the helper appliance over the
network. The helper appliance must be placed in the same network where the backup server resides.
5. Specify IP addressing settings for the helper appliance:
o If you use a DHCP server in the network, leave the Ob tain an IP address automatically option selected.
o To manually assign the specific IP address to the helper appliance, select the Use the following IP
a d dress option and specify the IP address, subnet mask and default ga teway address.
5. To enable FTP access to the restored file system, select the E nable FTP server on appliance check box. As
a result, your users will be able to access the helper appliance through 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 helper
appliance that supports the Novell Storage Services file system.
7. Click OK.

IMP ORTANT
When choosing an ESXi host for the helper 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.

Step 5. Start Restore Process
When the restore process starts, Veeam Backup & Replication opens the Veeam Backup browser. Right-click the
job and select Sta tistics option to check the progress of the restore process. The file-level restore appliance may
take about 10-20 seconds to boot.

At the Rea son 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 la ter.

Step 7. Verify Restore Settings
At the Summary step of the wizard, review the restore settings and click Browse to open the Veeam Backup
browser.

Step 8. 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 helper appliance, remove the helper appliance and unmount the storage snapshot from the
ESXi host (unless this storage snapshot is used by other restore operations).
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 save the file restored from the backup next to the original file, select Restore > Keep.
Veeam Backup & Replication will add the .RESTORED-YYYYMMDDHHMMSS suffix to the original file name
and store the restored file in the same folder where the original file resides.
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.
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 Cop y 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.
o 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 Sp ecify 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.
o 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, sele ct the P reserve
p ermissions a nd 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.

IMP ORTANT
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.
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.
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 ESXi 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 ESXi 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.
Before you restore the Microsoft Active Directory database from a storage snapshot, check prerequisites. Then
use the Microsoft Active Directory Object Restore wizard to restore the Microsoft Active Directory database.
1. Launch the Microsoft Active Directory Object Restore wizard
2. Select a VM
3. Select a restore point
4. Select an ESXi host for snapshot mounting
5. Specify a restore reason
6. Open the database in Veeam Explorer for Microsoft Active Directory
Before You Begin

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

Step 1. Launch Microsoft Active Directory Object Restore Wizard
To launch the Microsoft Active Directory Object Restore wizard, do one of the following:
• On the Home tab, click Restore and select VMware vSphere > Restore from backup or Restore from replica
> Ap p lication items restore > Microsoft Active D irectory.
working area, select a VM running Microsoft Active Directory and click Ap p lication 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.
necessary volume, select a VM running Microsoft Active Directory and click Ap p lication 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.

Step 2. Select VM
At the Ma chines 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 a ll VMs check box. Veeam Backup & Replication will display all VMs whose
disks are located on the storage system.

At the Restore P oint 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.

must be mounted. On the selected ESXi 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:
temporary VM.
4. Next to the Fold er field, click Choose and select a folder to which you want to place the temporary VM.
5. Click OK.

At the Rea son 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.

Step 6. Open Database in Veeam Explorer for Microsoft Active Directory
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 Ap p lication Items > Microsoft Active Directory 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.
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].

• Open Veeam Explorer for Microsoft Active Directory. From the main menu of Veeam Explorer for Microsoft
Active Directory, select Help > Online Help.
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 (an 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 (an 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:
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 ESXi 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 restore Microsoft Exchange objects from a storage snapshot, check prerequisites. Then use the
Microsoft Exchange Item Level Restore wizard to restore the Microsoft Exchange database.
1. Launch the Microsoft Exchange Item Level Restore wizard
2. Select a VM
3. Select a restore point
4. Select an ESXi host for snapshot mounting
5. Specify a restore reason
6. Open the EDB file in Veeam Explorer for Exchange
Before You Begin

Step 1. Launch Microsoft Exchange Item Level Restore Wizard
To launch the Microsoft Exchange Item Level Restore wizard, do one of the following:
> Ap p lication items restore > Microsoft Exchange .
working area, select a VM running Microsoft Exchange and click Ap p lication Items > Microsoft Exchange
on the ribbon. You can also right-click the VM and select Restore application items > Microsoft Exchange
ma ilbox items. In this case, you will pass immediately to the Location step of the wizard.
necessary volume, select a VM running Microsoft Exchange and click Ap p lication Items > Microsoft
E x change on the ribbon. You can also right-click the VM and select Restore application items > Microsoft
E x change mailbox items. In this case, you will pass immediately to the Restore Point step of the wizard.

Step 2. Select VM
At the Ma chines 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 a ll VMs check box. Veeam Backup & Replication will display all VMs whose
disks are located on the storage system.

At the Restore P oint 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.

will be mounted. On the selected ESXi host, Veeam Backup & Replication will create a temporary VM and mount
disks of the virtualized Microsoft Exchange server to this temporary VM.
2. Next to the Host field, click Choose and select an ESXi host to which the snapshot clone must be mounted
and on which the temporary VM must be created.
temporary VM.
5. Click OK.

At the Rea son 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.

Step 6. Open EDB File in Veeam Explorer for Exchange
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.
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 stora ge 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
Ap p lication Items > Microsoft Exchange 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.
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 (an 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
Ap p lication Items > Microsoft SharePoint 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 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.
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.
1. [For snapshots created by a snapshot-only job with VSS]: Veeam Backup & Replication opens the database
in Veeam Explorer for Microsoft SQL Server.
3. 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 ESXi
host.
4. Veeam Backup & Replication mounts disks of the Microsoft SQL Server to the temporary VM.
5. 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.
6. [For snapshots created in other ways than by a snapshot-only job with VSS]: Veeam Backup & Replication
opens the database in Veeam Explorer for Microsoft SQL Server.
Before You Begin
of LUNs to an ESXi host, you must register the ESXi host with a WWN ID on the storage sy stem.
Step 1. Launch Microsoft SQL Server Database Restore Wizard
To launch the Microsoft SQL Server Database Restore wizard, do one of the following:
> Ap p lication items restore > Microsoft SQL Server.
working area, select a VM running Microsoft SQL Server and click Ap p lication Items > Microsoft SQL Server
on the ribbon. You can also right-click the VM and select Restore application items > Microsoft SQL Server
d a tabases. In this case, you will pass immediately to the Location step of the wizard.
necessary volume, select a VM running Microsoft SQL Server and click Ap p lication 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.
Step 2. Select VM
At the Ma chines 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 a ll VMs check box. Veeam Backup & Replication will display all VMs whose disks are
located on the storage system.
At the Restore P oint 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.
mount disks of the virtualized Microsoft SQL Server to this temporary VM.
temporary VM.
5. Click OK.
At the Rea son step of the wizard, enter a reason for restoring a database from the Microsoft SQL Server VM. The
Step 6. Open Database in Veeam Explorer for Microsoft SQL Server
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.
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
Ap p lication Items > Microsoft SQL Server 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.
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 Ora cle 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 Ora cle Database Restore wizard, Veeam Backup & Replication automatically extracts an
Oracle database from the storage snapshot and opens it in Veeam Explorer for Oracle.
1. [For snapshots created by a snapshot-only job with VSS]: Veeam Backup & Replication opens the database
in Veeam Explorer for Oracle.
3. 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 ESXi host.
4. Veeam Backup & Replication mounts disks of the Oracle server to the temporary VM.
5. Veeam Backup & Replication locates the Oracle database and attaches the database to a staging Oracle
server.
6. [For snapshots created in other ways than by a snapshot-only job with VSS]: 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 prere quisites:
Step 1. Launch Oracle Database Restore Wizard
To launch the Ora cle Database Restore wizard, do one of the following:
> Ap p lication items restore > Oracle Database.
working area, select a VM running Oracle and click Ap p lication 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.
necessary volume, select a VM running Oracle and click Ap p lication 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.
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.
At the Restore P oint 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.
mount the disks of the virtualized Oracle server to this temporary VM.
temporary VM.
5. Click OK.
At the Rea son step of the wizard, enter a reason for restoring a database from the Oracle VM if necessary. The
Step 6. Open Database in Veeam Explorer for Oracle
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.
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
Ap p lication Items > Oracle 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.
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 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/LeftHand/P4000 series] To quiesce VMs on the volume, select the Create
a p plication-managed snapshot check box. The storage system will trigger a command to the 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/LeftHand/P4000 series, 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.
To delete a volume snapshot:
2. In the inventory pane, expand the storage system tree.
3. Right-click the necessary snapshot and select Delete snapshot.
NAS Integration
Veeam Backup & Replication allows you to integrate your storage systems with NAS file shares residing on them
into your infrastructure. For more information, see the Adding Enterprise Storage System as NAS Filer section of
the Veeam Backup & Replication User Guide.
information, see Backup Infrastructure for Storage Integration. After that, you can use storage snapshots for
data protection and disaster recovery operations.
You can perform backup from storage snapshots and storage rescan for the following storage systems:
• Dell EMC Isilon/PowerScale
• Lenovo ThinkSystem DM Series
• NetApp ONTAP
NAS File Share Backup from Storage Snapshots
For backup from storage snapshots, Veeam Backup & Replication uses storage snapshots as a source of data for
backup.
During backup from storage snapshots, Veeam Backup & Replication triggers a storage snapshot of the volume
where the NAS file share is located.
Veeam Backup & Replication performs file share backup to the backup storage in the following way:
1. When a new backup job session starts, Veeam Backup & Replication triggers a storage snapshot.
2. Veeam Backup & Replication assigns a file proxy to process the file share data.
3. The file proxy enumerates files and folders on the file share and creates a cycl ic redundancy check (CRC)
tree.
4. The file proxy transfers the CRC tree to the cache repository.
5. The cache repository saves the CRC tree.
When the cache repository receives a new CRC tree structure from the proxy, it compares it with the CRC
tree created during the previous run of the backup session. If any files or folders of the file share have
changed since the previous backup session run, the cache repository instructs the file proxy to start
reading changed data from the source file share.
6. The file proxy reads new data from the file share.
7. The file proxy creates data packages and transfers them to the target backup repository.
Data packages comprise backup data files (each 64 Mb in size) and metadata files that contain names and
versions of backup files and allocation of data in backup files.
8. Veeam Backup & Replication checks file versions in the backup repository against retention settings and
moves backup data from the backup repository to the archive repository if necessary.
9. Veeam Backup & Replication deletes the storage snapshot.
For Dell EMC Isilon/PowerScale: File Change Tracking

You have an option to use the file change tracking technology provided by the NAS manufacturer. It lets you
speed up the backup operation. For information on the file change tracking technology setup, see the Specify
File Share Processing Settings step of the New File Share wizard in the Veeam Backup & Replication User Guide.
In this case, Veeam Backup & Replication performs file share backup to the backup storage in the following wa y:
1. When a new backup job session starts, Veeam Backup & Replication triggers a storage snapshot.
2. [For all job sessions after the first one] Veeam Backup & Replication requests Dell EMC Isilon/PowerScale
storage system to return the difference between current and previous snapshots.
3. Veeam Backup & Replication assigns a file proxy to process the file share data.
4. The file proxy enumerates files and folders on the file share and creates a cyclic redundancy check (CRC)
tree.
5. The file proxy transfers the CRC tree to the cache repository.
6. The cache repository saves the CRC tree.
When the cache repository receives a new CRC tree structure from the proxy, it compares it with the CRC
tree created during the previous run of the backup session. If any files or folders of the file share have
changed since the previous backup session run, the cache repository instructs the file proxy to start
reading changed data from the source file share.
7. The file proxy reads new data from the file share.
8. The file proxy creates data packages and transfers them to the target backup repository.
Data packages comprise backup data files (each 64 Mb in size) and metadata files that contain names and
versions of backup files and allocation of data in backup files.
9. Veeam Backup & Replication checks file versions in the backup repository against retention settings and
moves backup data from the backup repository to the archive repository if necessary.
10. [For all job sessions after the first one] Veeam Backup & Replication deletes the previous storage
snapshot, keeping the newest storage snapshot.
Veeam Agent Integration
Veeam Backup & Replication allows you to integrate your storage systems with Veeam Agent for Microsoft
Windows installed on computers in your infrastructure. For more information, see the Storage Snapshots
Support section in the Veeam Agent Management Guide.
information, see Backup Infrastructure for Storage Integration. After that, you can use storage snapshots for
data protection and disaster recovery operations.
For requirements and limitations for Veeam Agent integration, see Limitations and Considerations section in the
Veeam Agent Management Guide.
For information on how backups from storage snapshots are created, see the Storage Snapshots Support section
in the Veeam Agent Management Guide.
You can perform backup from storage snapshots and storage rescan for the following storage systems:
• Dell EMC Unity XT/Unity, VNX(e)
• Fujitsu ETERNUS HX/AX
• HPE 3PAR StoreServ
• HPE Nimble
• HPE Primera
• HPE StoreVirtual/LeftHand/P4000 series
• IBM N series
• IBM FlashSystem (StorWize), IBM SVC, Lenovo Storage V Series
• NetApp FAS/AFF, FlexArray (V-Series)
• Universal Storage API Integrated Systems
Backup Infrastructure for Storage
Integration
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. Configure a backup proxy. The backup proxy is required for storage systems rescan and backup from
storage snapshots.
2. Add storage systems. You must add the storage systems on which the backup data is hosted to the backup
infrastructure. If you plan to work with secondary storage arrays, you must add them to the backup
infrastructure as well.
Check the prerequisites for a specific storage systems before you add a storage system to your backup
infrastructure.
Configuring Backup Proxy for Storage
Integration
For some operations with storage snapshots, Veeam Backup & Replication requires a backup proxy. The backup
proxy is used for two purposes:
• Rescan (storage discovery) process on storage volumes
• Backup from storage snapshots
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 the
backup data from them.
General Requirements
• For VMware integration
o You must assign to a Microsoft Windows or a Linux machine the role of a backup proxy. This can be a
dedicated machine or backup server performing the role of the default backup proxy.
o For backup from storage snapshots, the transport mode for VMware backup proxy must be set to
Automatic selection or Direct storage access.
o For Linux backup proxy, to check compatibility with a storage system, see the system requirements
provided by the storage system vendor.
• [For VMware and Veeam Agent integration] 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 v irtual domain.
• [For Veeam Agent integration] You must assign the role of a backup proxy, type Agent, to a machine
running Microsoft Windows Server OS version. This can be a dedicated machine or backup server
performing the role of the default backup proxy, if it is running Microsoft Windows Server OS version.
• [For NAS integration] You must assign the role of a backup proxy, type Agent, to a Microsoft Windows
machine. This can be a dedicated machine or backup server performing the role of the default bac kup
proxy.
iSCSI Protocol
• [For Microsoft Windows] The backup proxy must have a Microsoft iSCSI Software initiator enabled.
• [For Linux] The backup proxy must have an Open-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 (Open-iSCSI) may not be enabled when you perform storage rescan. For Backup from
Storage Snapshots, however, a Microsoft iSCSI Software initiator (Open-iSCSI) must be enabled.
CIFS/SMB Protocol
• CIFS/SMB traffic between the backup proxy and storage system must be allowed.
• Backup proxy is not supported on Linux.
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.
NFS Protocol
• NFS traffic between the backup proxy and storage system must be allowed.
• Backup proxy is not supported on Linux.
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.
Before you add a storage system to Veeam Backup & Replication, make sure SAN initiator groups for production
ESXi hosts and for proxy hosts are isolated and snapshot clones will not be exported to production environment.
Otherwise, you may encounter production infrastructure issues such as doubling of the root
RGK4IT_VMware_Cluster_Boot Volume to ESXi.
If you want Veeam Backup & Replication to automatically rescan the storage system after you add it, select the
relevant check box at the last step of the wizard. For more information on the rescan process, see Rescan
(Storage Discovery) Process.
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.
NOTE
If only Veeam Agents backup processing is selected for a storage system, storage volumes and snapshots
of such storage system are not displayed under the Storage snapshots node. The storage system itself is
still displayed.
You can add the following storage systems to the backup infrastructure:
• Cisco HyperFlex
• Dell EMC Unity, VNXe, VNX
• HPE Nimble
• HPE 3PAR StoreServ and HPE Primera
• IBM Spectrum Virtualize
• NetApp Data ONTAP
Adding Cisco HyperFlex

Before you add a Cisco HyperFlex storage system to the backup infrastructure, check prerequisites. Then use the
New Cisco HyperFlex System wizard to add the storage system.
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 Ad d 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 Ad d 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 Ad d Storage. You can also select the Cisco HyperFlex node in the
inventory pane, right-click anywhere in the working area and select Ad d storage.
Step 2. Specify Storage Name or Address and Storage Role
At the Na me 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 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.
Only VMware backup jobs are allowed to access this storage system, so the VMwa re backup check box is
selected automatically in the Role field.
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 Ma nage accounts link or click Ad d on the right of the Credentials field to
add the credentials. For more information, see the Credentials Manager section in
2. When you add a storage system, Veeam Backup & Replication saves to the configuration database a
thumbprint of the TLS certificate installed on the Cisco HyperFlex RESTful API server. During every
subsequent connection to the server, Veeam Backup & Replication uses the saved thumbprint to verify the
server identity and avoid the man-in-the-middle attack.
If the certificate installed on the server is not trusted, Veeam Backup & Replication displays a warning.
o To view detailed information about the certificate, click View.
o If you trust the server, click Continue.
o If you do not trust the server, click Ca ncel.
Veeam Backup & Replication will display an error message, and you will not be able to connect to the
server.
If you update the certificate on the server, you must acknowledge the new certificate in the server
connection settings. To do this, in the Storage Infrastructure view right-click the storage system, select
E d it storage, pass through the E d it Server wizard and click Trust to acknowledge the new certificate.
Step 4. Specify VMware Access Options
At the VMwa re vSphere step of the wizard, 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.
• Leave Automatic selection to let Veeam Backup & Replication check data retrieval methods for all backup
proxies in the backup infrastructure.
• Click Choose and 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.
Step 5. Apply Settings
At the Ap p ly step of the wizard, wait for the storage system to be added to the backup infrastructure. After
that, click Nex t.
Step 6. Finish Working with Wizard
At the Summary step of the wizard, review settings of the added storage system.
Select the Run the storage infrastructure rescan when I click Finish check box if you want to start the rescan
right after you finish working with the wizard. For more information on the rescan process, see Rescan (Storage
Discovery) Process.
Click Finish to close the wizard.
Adding Dell EMC

Before you add a Dell EMC storage system to the backup infrastructure, check prerequisites. Then use the New
DE LL EMC Storage wizard to add the storage system.
Step 1. Launch New Dell EMC Storage Wizard
To launch the New Dell EMC Storage wizard, do one of the following:
click DE LL EMC.
and select Ad d Storage. In the displayed window, click DE LL E MC.
• 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 DE LL E MC node and select
Ad d storage. You can also select the DE LL E MC node in the inventory pane, right-click anywhere in the
working area and select Ad d storage.
Step 2. Select Dell EMC Storage Type
At the Storage Type step of the wizard, select one of the following storage types:
• Dell EMC SC series/Compellent
• Dell EMC Unity XT/Unity, VNXe, VNX
Adding Dell EMC Isilon

To add Dell EMC Isilon/PowerScale storage system to the backup infrastructure, do the following:
1. Specify storage name or address and storage role
2. Specify credentials
3. Specify NAS access options
4. Apply settings
5. Finish working with wizard
At the Na me 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.
information about the user who added the storage system, date and time when the storage system was
added.
Only NAS backup jobs are allowed to access this storage system, so the NAS filer check box is selected
automatically in the Role section.
storage system: from the Credentials drop-down list, select credentials to connect to the storage system. If you
have not set up credentials beforehand, click the Ma nage accounts link or click Ad d on the right of the
Credentials field to add the credentials. For more information, see the Credentials Manager section in
• To view detailed information about the certificate, click View.
• If you trust the server, click Continue.
• If you do not trust the server, click Ca ncel.

server.
In the RE ST API port dialog, select the necessary port.
Step 3. Specify NAS Access Options
At the NAS Filer step of the wizard, specify options for accessing the storage system.
1. In the P rotocol to use section, select check boxes next to protocols over which you want to work with the
storage system.
2. During storage rescan, backup and restore operations, Veeam Backup & Replication automatically creates
required SMB and NFS export rules on the storage system. If you do not
want Veeam Backup & Replication to create export rules, clear the Create required 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 to rescan, click Choose to the right of the Volumes to scan field. In the E d it Volumes
window, select volumes you want to rescan:
a. To exclude volumes from rescan, select All volumes except and click Ad d . Click From infrastructure to
select volumes from your storage infrastructure, or By wildcard to select volumes using a wildcard
character.
b. To rescan only specific volumes, select Only the following volumes and click Ad d . Click From
infrastructure to select volumes from your storage infrastructure, or By wildcard to select volumes
using a wildcard character.
c. If you leave All existing volumes check box 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
manually at any time. For more information, see Rescanning Storage Systems.
4. To rescan storage systems and perform Backup from Storage Snapshots, you must configure a backup
proxy. On the right of the Ba ckup proxies to use field, click Choose and define backup proxies that you
want to use for these operations.
o 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.
o 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 connection with the storage system.
that, click Nex t.
Discovery) Process.
Adding Dell EMC Unity XT/Unity, VNXe, VNX
To add Dell EMC Unity XT/Unity, VNXe, VNX storage system to the backup infrastructure, do the following:
1. Select storage type
4. Specify VMware access options
5. Specify Veeam Agent access options
6. Apply settings
7. Finish working with wizard
Step 1. Select Dell EMC Unity XT/Unity, VNXe, VNX Storage Type
At the Storage Type step of the wizard, select the storage type.
• Select Unity XT/Unity to add a Dell EMC Unity XT/Unity storage system.
• Select VNXe to add a Dell EMC VNXe storage system.
• 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.
At the Na me step of the wizard, specify the storage system name, description and storage role.
added.
3. In the Role section, select the types of backup jobs that are allowed to access this storage system:
a. Select the Block or file storage for VMware vSphere check box to allow VMware backup.
b. [for Unity XT/Unity, VNXe, VNX (block)] Select the Block storage for Microsoft Windows servers
check box to allow backup of Veeam Agents.
When you select any of these check boxes, additional steps of the wizard will appear.
If you do not select any check box, Veeam Backup & Replication displays an error. To proceed with the
wizard, select at least one check box.
storage system.
2. [For Dell EMC VNX block storage] Select the scope to which the user account belongs:
o Select Global if the user can administer all VNX systems in the domain.
o Select Loca l if the user can administer only a single VNX storage system in the domain.
o Select LDAP if the user can administer all VNX systems that use the LDAP server for authentication.
3. When you add a storage system, Veeam Backup & Replication saves to the configuration database the
following information:
o [For Dell EMC Unity XT/Unity, VNXe] A thumbprint of the TLS certificate installed on the
management server.
o [For Dell EMC VNX file storage] A fingerprint of the SSH key of the management server.
During every subsequent connection to the server, Veeam Backup & Replication uses the saved
information to verify the server identity and avoid man-in-the-middle attacks.
[For Dell EMC Unity XT/Unity, VNXe] If the certificate installed on the server is not trusted,
Veeam Backup & Replication displays a warning.
o If you do not trust the server, click Ca ncel. In this case, Veeam Backup & Replication will display an
error message, and you will not be able to connect to the server.
[For Dell EMC VNX file storage] To let you identify the server, Veeam Backup & Replication displays the
SSH key fingerprint. To accept the fingerprint and connect to the server, click Y es . If you click No,
server.
If you update the certificate or SSH key on the server, you must acknowledge the new certificate or SSH
key in the server connection settings. To do this, in the Storage Infrastructure view right-click the storage
system, select E d it storage, pass through the E d it Server wizard and click Trust.
At the VMwa re vSphere step of the wizard, specify options for accessing the storage system. You will see this
step if you have selected the Block or file storage for VMware vSphere check box at the Specify Storage Name
or Address and Storage Role step of the wizard.
storage system.
character.
IMP ORTANT
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.
3. To rescan storage systems and perform Backup from Storage Snapshots, you must configure a backup
backup proxies fails or loses connection to the storage system.
IMP ORTANT
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 Fa ilover to standard backup option is disabled in the job settings, the job
will fail. For more information, see Configuring Backup from Storage Snapshots.
4. From the Mount Server list, select a server that you want to use as a mount server for file-level and
application items restore, or click Ad d New to add a new one. For more information, see Mount Server
Step 5. Specify Veeam Agent Access Options
At the Server Storage step of the wizard, specify options for accessing the storage system. You will see this step
if you selected the Block storage for Microsoft Windows servers check box at the Specify Storage Name or
Address and Storage Role step of the wizard.
storage system.
o To exclude volumes from rescan, select All volumes except and click Ad d . Click From infrastructure to
character.
o To rescan only specific volumes, select Only the following volumes and click Ad d . Click From
o If you leave All existing volumes check box selected, Veeam Backup & Replication will rescan all
IMP ORTANT
rescan scope the volumes on which the protected machine disks reside.
3. To rescan storage systems and perform Backup from Storage Snapshots, you need to configure a backup
automatically assign an optimal backup proxy for rescan and Backup from Storag e Snapshots.
backup proxies fails or loses its connectivity to the storage system.
NOTE
will fail.
that, click Nex t.
Discovery) Process.
Adding Hewlett Packard Enterprise

Before you add a Hewlett Packard Enterprise storage system to the backup infrastructure, check prerequisites.
Then use the New HPE Storage wizard to add the storage system.
Step 1. Launch New HPE Storage Wizard
To launch the New HPE Storage wizard, do one of the following:
click Hewlett Packard Enterpsrise .
and select Ad d Storage. In the displayed window, click Hewlett Packard Enterpsrise.
• You can use this method if at least one HPE Nimble, 3PAR StoreServ or StoreVirtual/LeftHand/P4000
series storage system is added to the backup infrastructure.
Open the Storage Infrastructure view. In the inventory pane, right-click the Hewlett Packard Enterpsrise
node and select Ad d storage. You can also select the Hewlett Packard E nterpsrise node in the inventory
pane, right-click anywhere in the working area and select Ad d storage.
Step 2. Select HPE Storage Type
At the Storage Type step of the wizard, select one of the following storage types:
• HPE Nimble
• HPE 3PAR StoreServ and HPE Primera
Adding HPE Nimble

To add an HPE Nimble storage system to the backup infrastructure, do the following:
5. Apply settings
6. Finish working with the wizard
NOTE
Make sure that the Access setting is set to Volume Only for VMware hosts on all Nimble volumes that are
used as VMware datastores.
If the Access setting within the Nimble storage system is set to Volume & Snapshots for VMware hosts, the
VMware host detects all snapshots as volumes at volume rescan when Veeam Backup & Replication mounts
Nimble snapshots to a backup proxy. When Veeam Backup & Replication subsequently unmounts the
snapshots after the backup is complete, alerts and alarms may be triggered on the VMware host regarding
inaccessible storage. The VMware host can even become unresponsive as a result. Be aware, the VMware
hosts may require a reboot during a maintenance period for the new LUN access permissions to take effect.
added.
b. Select the Block storage for Microsoft Windows servers check box to allow backup of Veeam Agents.
storage system.
The user account that you select must have Administrator or Power User permissions on the HPE Nimble
storage system.
2. Veeam Backup & Replication uses HPE 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 HPE
Nimble RESTful API, you can change the port number.
3. When you add a storage system, Veeam Backup & Replication saves to the configuration database the
following information:
o [For Nimble OS 2.3 and later] A thumbprint of the TLS certificate installed on the management server.
o [For Nimble OS 2.3] A fingerprint of the SSH key of the management server.
During every subsequent connection to the server, Veeam Backup & Replication uses the saved
information to verify the server identity and avoid man-in-the-middle attacks.
[For Nimble OS 2.3 and later] If the certificate installed on the server is not trusted,
Veeam Backup & Replication displays a warning.
server.
[For Nimble OS 2.3] To let you identify the server, Veeam Backup & Replication displays the SSH key
fingerprint. To accept the fingerprint and connect to the server, click Y es . If you click No,
server.
storage system.
character.
IMP ORTANT
IMP ORTANT
storage system.
character.
IMP ORTANT
NOTE
will fail.
that, click Nex t.
Discovery) Process.
Adding HPE 3PAR StoreServ and HPE Primera
Before you add an HPE 3PAR StoreServ or HPE Primera storage system to the backup infrastructure, check
prerequisites. After that, do the following:
1. Enable HPE 3PAR Web Services API Server
2. Specify HPE 3PAR Web Services API address and storage role
5. Apply settings
Step 1. Enable HPE 3PAR Web Services API Server
Veeam Backup & Replication uses the HPE 3PAR Web Services API (WSAPI) server to communicate with HPE
Primera and HPE 3PAR StoreServ storage systems. When you add an HPE Primera or 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.
To check if the WSAPI server is enabled and enable it if needed:
1. Log on to the Processor with administrator privileges:
#ssh <administrator account>@<SP IP Address>
2. Run the following command to view the current state of the WSAPI server:
#showwsapi
-- -State- -HTTP_State-
HTTP_Port -HTTPS_State- HTTPS_Port -Version-
Enabled Active Enabled 8008
Enabled 8080 1.1
3. If the WSAPI server is not running, run the following command to start it:
#startwsapi
4. If the HTTP port is disabled, run the following command to enable it:
#setwsapi -http enable
If the HTTPS port is disabled, run the following command to enable it:
#setwsapi -https enable
Step 2. Specify HPE 3PAR Web Services API Address and Storage Role
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 Na me step of the wizard, provide information about the HPE 3PAR Web Services API Server, provide a
description and storage role.
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 or HPE Primera 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.
information about the user who added the server, date and time when the server was added.
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 Ma nage accounts link or click Ad d on the right of the
Credentials field to add the necessary credentials. For more information, see the Credentials Manager
IMP ORTANT
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 to the configuration database a TLS
certificate thumbprint and an SSH key fingerprint of the HPE 3PAR Web Services API Server. During every
subsequent connection to the server, Veeam Backup & Replication uses the saved information to verify the
server identity and avoid the man-in-the-middle attack.
server.
Veeam Backup & Replication will display the SSH key fingerprint. To accept the fingerprint and
connect to the server, click Y es .
step if you have selected the Block or file storage for VMware vSphere check box at the Specify HPE 3PAR Web
Services API Address and Storage Role step of the wizard.
storage system.
character.
IMP ORTANT
IMP ORTANT
if you selected the Block storage for Microsoft Windows servers check box at the Specify HPE 3PAR Web
Services API Address and Storage Role step of the wizard.
storage system.
character.
IMP ORTANT
NOTE
will fail.
that, click Nex t.
Discovery) Process.
Adding HPE StoreVirtual
To add an HPE StoreVirtual/LeftHand/P4000 series storage system to the backup infrastructure, do the
following:
5. Apply settings
1. On the right of the Ma nagement 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
Ma nagement server DNS name or IP address field.
information about the user who added the management group, date and time when the HPE management
group was added.
3. In the Role section, select the types of backup jobs that are allowed to a ccess this storage system:
management group.
1. From the Credentials list, select credentials to connect to the management group. If you have not set up
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-the-
middle attacks.
To let you identify the server, Veeam Backup & Replication displays the SSH key fingerprint.
o If you trust the server and want to connect to it, click Y es .
o 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 E d it storage,
pass through the E d it Server wizard and click Trust to acknowledge the new key.
storage system.
character.
After you finish working with the wizard, you can change the resca n scope and start the rescan process
IMP ORTANT
IMP ORTANT
storage system.
character.
IMP ORTANT
NOTE
will fail.
that, click Nex t.
Discovery) Process.
Adding IBM Spectrum Virtualize

Before you add a storage system to the backup infrastructure, check prerequisites. Then use the New IBM
Sp ectrum Virtualize Storage wizard.
Step 1. Launch New IBM Spectrum Virtualize Storage Wizard
To launch the New IBM Spectrum Virtualize Storage wizard, do one of the following:
click IBM Spectrum Virtualize.
and select Ad d 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.
Open the Storage Infrastructure view. In the inventory pane, right-click the IBM Spectrum Virtualize node
under Storage Infrastructure and select Ad d storage. You can also select the IBM Spectrum Virtualize node
in the inventory pane, right-click anywhere in the working area and select Ad d storage.
1. In the DNS Name or IP address field, specify a DNS name or IP address of the storage system.
added.
storage system.
credentials beforehand, click the Manage accounts link or click Add on the right of the Credentials field to
NOTE
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 P ort field.
storage system.
character.
IMP ORTANT
IMP ORTANT
At the Storage Server step of the wizard, specify options for accessing the storage system. You will see this step
storage system.
character.
IMP ORTANT
NOTE
will fail.
that, click Nex t.
Discovery) Process.
Adding Lenovo ThinkSystem DM Series

To add a Lenovo storage system to the backup infrastructure, use the New Lenovo ThinkSystem DM Series
Storage wizard.
Step 1. Launch New Lenovo ThinkSystem Storage Wizard
To launch the New Lenovo ThinkSystem Storage wizard, perform the following steps:
1. Open the Storage Infrastructure view and do one of the following:
o In the working area, click Ad d Storage.
o In the inventory pane, right-click the Storage Infrastructure node and select Ad d Storage.
2. In the displayed window, select Show more vendors > Lenovo > Lenovo ThinkSystem DM Series.
You can also use this method to launch the wizard if at least one Lenovo ThinkSystem DM Series storage system
or Netapp Data ONTAP storage system is added to the backup infrastructure:
2. In the inventory pane, right-click the ONTAP storage system and select Ad d Storage.
Alternatively, you can select the ONTAP storage system in the inventory pane, right-click anywhere in the
working area and select Ad d storage > Lenovo ThinkSystem DM Series.
Step 2. Specify Lenovo ThinkSystem Server Name or Address and Storage
Role
1. In the Ma nagement server D NS name or IP address field, specify a DNS name or IP address of the storage
system.
added.
c. Select the NAS filer check box to allow NAS backup jobs.
Step 3. Specify Credentials and Protocol Type
storage system, and select the transport protocol.
2. From the P rotocol 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.
When you add a storage system, Veeam Backup & Replication saves to the configuration database a thumbprint
of the TLS certificate installed on the management server. During every subsequent connection to the server,
Veeam Backup & Replication uses the saved thumbprint to verify the server identity and avoid the man-in-the-
middle attack.
server.
If you update the certificate on the server, you must acknowledge the new certificate in the server connection
settings. To do this, in the Storage Infrastructure view right-click the storage system, select E d it storage, pass
through the E d it Server wizard and click Trust to acknowledge the new certificate.
step if you have selected the Block or file storage for VMware vSphere check box at the Specify Lenovo
ThinkSystem Server Name or Address step of the wizard.
storage system.
2. [For Lenovo ThinkSystem storage system working over NFS] During storage resca n, 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
ex p ort rules automatically check box.
character.
IMP ORTANT
automatically assign an optimal backup proxy for rescan and Backup from Storage Snapshot s.
IMP ORTANT
if you selected the Block storage for Microsoft Windows servers check box at the Specify Lenovo ThinkSystem
Server Name or Address step of the wizard.
storage system.
character.
IMP ORTANT
NOTE
will fail.
At the NAS Filer step of the wizard, specify options for accessing the storage system. You will see this step if
you selected the NAS filer check box at the Specify Lenovo ThinkSystem Server Name or Address step of the
wizard.
storage system.
2. 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 export rules a utomatically check box.
character.
IMP ORTANT
rescan scope volumes on which file share disks reside.
Veeam Backup & Replication will check which backup proxies have access to the storage sy stem, and
IMP ORTANT
In order to back up file shares residing on this storage system, do not forget to do the following:
1. Run the storage infrastructure rescan to discover file shares. You can either select this option at the
last step of the wizard, as described in Finish Working with Wizard, or manually start the storage
discovery, as described in Rescanning Storage Systems.
2. Add the storage system or its part as a file share to the inventory of the virtual infrastructure, as
described in the Adding Enterprise Storage System as NAS Filer section of the
At the Ap p ly step of the wizard, wait until Veeam Backup & Replication adds the storage system to the backup
infrastructure. After that, click Nex t.
Discovery) Process.
Adding NetApp Data ONTAP

Before you add to the backup infrastructure a NetApp storage system running Data ONTAP, check prerequisites.
Then use the New NetApp Data ONTAP Storage wizard to add the storage system.
Step 1. Launch New NetApp Data ONTAP Storage Wizard
To launch the New NetApp Data ONTAP Storage wizard, perform the following steps.
2. In the displayed window, select NetApp > Da ta ONTAP.
You can use this method to launch the wizard if at least one NetApp Data ONTAP storage system or Lenovo
ThinkSystem DM Series storage system is added to the backup infrastructure:
2. In the inventory pane, right-click the ONTAP storage system and select Ad d Storage.
Alternatively, you can select the necessary NetApp storage system in the inventory pane, right-click
anywhere in the working area and select Ad d storage .
Step 2. Specify NetApp Server Name or Address and Storage Role
1. In the Ma nagement server DNS name or IP address field, specify a DNS name or IP address of the storage
system.
added.
c. Select the NAS filer check box to allow NAS backup.
Step 3. Specify Credentials and Protocol Type
storage system, and select the transport protocol.
2. From the P rotocol 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.
When you add a storage system, Veeam Backup & Replication saves to the configuration database a thumbprint
of the TLS certificate installed on the NetApp management server. During every subsequent connection to the
server, Veeam Backup & Replication uses the saved thumbprint to verify the server identity and avoid the man-
in-the-middle attack.

server.
If you update the certificate on the server, you must acknowledge the new certificate in the server connection
settings. To do this, in the Storage Infrastructure view right-click the storage system, select E d it storage, pass
through the E d it Server wizard and click Trust to acknowledge the new certificate.
step if you have selected the Block or file storage for VMware vSphere check box at the Specify NetApp Server
Name or Address and Storage Role step of the wizard.
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
a utomatically check box.
character.
NOTE
If you use NetApp MetroCluster, you will not be able to select volumes from infrastructure.
IMP ORTANT
IMP ORTANT
if you selected the Block storage for Microsoft Windows servers check box at the Specify NetApp Server Name
storage system.
character.
IMP ORTANT
NOTE
will fail.
At the NAS Filer step of the wizard, specify options for accessing the storage system. You will see this step if
you selected the NAS Filer check box at the Specify NetApp Server Name or Address and Storage Role step of
the wizard.
storage system.
2. [For NetApp Data ONTAP 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
ex p ort rules automatically check box.
character.
After you finish working with the wizard, you can change the rescan scope and start the r escan process
IMP ORTANT
rescan scope volumes on which file share disks reside.
Veeam Backup & Replication will check which backup proxies have access to the storage sy stem, and
IMP ORTANT
In order to back up file shares residing on this storage system, do not forget to do the following:
1. Run the storage infrastructure rescan to discover file shares. You can either select this option at the
last step of the wizard, as described in Finish Working with Wizard, or manually start the storage
discovery, as described in Rescanning Storage Systems.
2. Add the storage system or its part as a file share to the inventory of the virtual infrastructure, as
described in the Adding Enterprise Storage System as NAS Filer section of the
that, click Nex t.
Discovery) Process.
Adding Universal Storage API Integrated Systems

Before you add a Universal Storage API integrated system to the backup infrastructure, check prerequisites.
Then use the storage installation wizard.
1. Launch the storage installation wizard
6. Apply settings
Step 1. Launch Storage Installation Wizard
To launch a storage installation wizard for Universal Storage API integrated systems, perform the following
steps.
2. In the displayed window, click Show more vendors and select the storage system that you want to add.
To launch the installation wizard for NetApp SolidFire storage systems, in the displayed window selec t
NetApp > E lement.
To launch the installation wizard for DELL EMC SC Series/Compellent storage systems, in the displayed
window select Dell EMC > SC Series.
If at least one Universal Storage API integrated system is added to the backup infrastructure, you can use the
following method to launch the wizard:
2. In the inventory pane, right-click the necessary storage system and select Ad d Storage.
Alternatively, you can select the necessary storage system in the inventory pane, right-click anywhere in
the working area and select Ad d storage.
If the storage system that you want to add does not appear on the list, click Show more vendors to go to the
next page. If your storage system still doesn't appear, select Get plug-in for another storage to see available
plug-ins and download the one from your storage vendor. For more information, see Installing Storage
System Plug-Ins.
1. In the DNS Name or IP address field, specify a DNS name or IP address of the storage system.
added.
storage system.
NOTE
2. In the P ort field, specify a number of the port that you plan to use to connect to a server.
At the VMwa re vSphere step of the wizard, specify options for accessing the storage system. You will s ee this
storage system.
character.
c. If you leave All existing volumes checkbox selected, Veeam Backup & Replication will rescan all
IMP ORTANT
IMP ORTANT
storage system.
character.
IMP ORTANT
NOTE
will fail.
that, click Nex t.
Discovery) Process.
Rescanning Storage Systems
You can rescan a storage system added to the backup infrastructure. 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.
[For VMware integration] Storage system rescan may be required, for example, if you create or delete snapshots
For more information about the storage system rescan process, see Rescan (Storage Discovery) Process.
Before you start storage discovery, make sure that you have a properly configured backup proxy in the backup
infrastructure. [For VMware integration]: Otherwise, Veeam Backup & Replication will not be able to match
storage volumes to VMware datastores and locate VMs on these storage volumes.
NOTE
[For VMware integration]: Veeam Backup & Replication does not perform rescan on VMs whose disks are
located on VVol datastores.
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, open the storage system connection settings and navigate to the
VMwa re/NAS/Veeam Agent Access Options step of the wizard. Select the volumes you want to rescan.
For more information, see Sp ecify VMware/NAS/Veeam Agent Access Options step of the relevant Ad d Storage
wizard.
Rescan (Storage Discovery) Process

The Storage Discovery process performs rescan of the whole storage system or selected volumes. It can be
performed against the following nodes in the storage system hierarchy: vendor, storage system, storage
volume. In case you have limited rescan scope, storage discovery will be performed only for included volumes.
For details, see Limiting Rescan Scope.
NOTE
If only Veeam Agents backup processing is selected for a storage system, storage volumes are not
displayed and rescan of selected volumes is not available.
During the rescan, the Storage Discovery process gets and updates the necessary information regarding the
storage systems added to Veeam Backup & Replication. This is necessary for the backup and restore processes
using storage integration.
Stages of Rescan
1. [For VMware,NAS, Veeam Agent integration] General infrastructure
Receiving storage system information.
a. Defining the storage system data hierarchy (volumes, shares, LUNs, snapshots).
b. Getting the information about each volume added to rescan scope (name, ID, size, SCSI Unique ID for
LUNs, local paths for shares).
c. Defining basic information about storage snapshots (name, id, creation time).
d. Getting information about storage adapters (targets).
e. Receiving other relevant information.
2. [For VMware,NAS, Veeam Agent integration] Availability from backup proxies
Verifying the possibility of using proxies for backup/rescan/data transmission directly from the storage
systems.
a. Analyzing the selected proxies and checking iSCSI/NFS/CIFS servers availability from these proxies.
b. Matching proxies with available servers. The LUNs/share files available from these servers are
considered available from the relevant proxies.
Availability through Fibre Channel is not checked. If a proxy is added to a storage system list, the access is
considered set.
3. [For VMware integration] vCenter/ESXi rescan
a. Identifying the list of vCenter/ESXi datastores added to Veeam Backup & Replication.
b. Matching the vCenter/ESXi datastores with volumes (LUNs/share files) added to

Veeam Backup & Replication. Making the list of VMs located on datastores.
c. Creating/updating information files for the VMs in the snapshots of relevant volumes.
If the VMFS/NFS rescan has not been executed for a volume earlier, we assume that all the snapshots
of the volume are for those VMs that have been in the datastore at the moment of rescan.
If the VMFS/NFS rescan has been executed for a volume earlier, Veeam Backup & Replication skips the
next step (updating the VMware hosts information for each VM).
d. Updating the VMware hosts information for each VM.
4. [For VMware integration] VMFS/NFS rescan
Scanning the snapshot file system.
a. Identifying the snapshot file system type.
b. If the snapshot file system type corresponds with VMFS or NFS: searching for the .vmx files located in
the snapshots.
Thus the system identifies the VMs located in the snapshots. If this stage has not been performed for
these snapshots earlier, the snapshot content shown in Veeam Backup & Replication may be changed
on this stage: some VMs may be added or deleted.
c. Defining the VMs size.
How to Start Storage Discovery

The following actions and processes initiate the Storage Discovery process:
• Storage Monitor
The Storage Monitor process runs in the background. Every 10 minutes the process checks:
o Appearance or removal of snapshots in the supervised volumes,
o Changes in the snapshot names in the supervised volumes,
o Changes in the name of the supervised volume itself,
o Appearance or removal of volumes (including changes due to alteration in the rescan scope Volumes
to scan).
If changes are detected, the Storage Monitor initiates the rescan of the container entity, including all
rescan stages:
o Alteration in a snapshot starts rescan of the volume,
o Alteration in a volume starts rescan of the storage system.
If more than 30% of the volumes need to be rescanned, the Storage Monitor starts rescan of the whole
storage system.
• Automatic storage rescan
Rescan of all storage systems, including all rescan stages, starts once a week.
• Adding vCenter Server/ESXi
Rescan of all storage systems without VMFS/NFS Rescan.
• Adding a backup proxy
Rescan of all storage systems without vCenter/ESXi and VMFS/NFS Rescan.
• Starting Veeam Backup Service

Complete rescan of all storage systems.
• Adding a storage system as a NAS filer

Rescan of storage systems with NAS integration.
• Selecting Run the storage infrastructure rescan when I click Finish check box in a storage system adding
wizard
Rescan of the added storage system, all stages included.
• Manual storage rescan
If necessary, you can start the Storage Discovery process manually. Storage discovery can be performed
against the following nodes in the storage system hierarchy: vendor, storage system or storage volume.
To manually start storage discovery:
a. Open the Storage Infrastructure view.
b. In the inventory pane, expand the storage system tree.
c. Select a node in the storage system hierarchy: vendor, storage system or volume.
d. Click Rescan on the ribbon or right-click the node in the hierarchy and select Rescan storage or Rescan
volume.
IMP ORTANT
The rescan operation is performed only for volumes included in the rescan scope. For information how to
change the rescan scope, see Limiting Rescan Scope.
Removing Storage Systems
You can remove a storage system from the backup infrastructure.
Mind the following:
• When you remove a storage system from the backup infrastructure, Veeam Backup & Replication attempts
to find hosts with names 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 VMware integration]: 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:
2. In the inventory pane or in the working area, right-click the storage system and select Remove storage.
Requirements and Limitations
Backup from Storage Snapshots and Veeam Explorer for Storage Snapshots have a set of requirements and
limitations.
• System Requirements
• Required Permissions
• General Limitations
• Cisco HyperFlex Limitations
• Dell EMC VNXe, VNX, SC Limitations
• NetApp Data ONTAP/Lenovo Thinksystem DM Limitations
System Requirements
Veeam Backup & Replication offers integration with the the following storage systems:
Cisco HyperFlex HX-Series

• NFS connectivity only
• HyperFlex 4.0(2x) or later (Backup from Storage Snapshots, Full Integration mode)
• Basic authentication is not supported for SSO users in HyperFlex starting from version 3.0
Dell EMC Isilon/PowerScale (NAS Backup only)

• NFS or CIFS connectivity
• OneFS 8.1.2 to 9.1
Dell EMC VNX, VNX2, VNXe and Unity XT/Unity

• NFS, Fibre Channel (FC) or iSCSI connectivity
• Dell EMC VNX/VNX2 all OE versions are supported
• Dell EMC Unity XT/Unity, VNXe OE versions 3.x up to 5.1
HPE 3PAR StoreServ
• Fibre Channel (FC) or iSCSI connectivity
• 3PAR OS versions 3.2.2 up to 3.3.1 MU5
• WSAPI 1.5 and later
• iSCSI VLAN tags are supported
• Virtual Domains are supported
HPE Nimble Storage AF-Series, HF-Series and CS-Series

• Nimble OS 2.3 or later
• HPE Nimble synchronous replication is not supported
HPE Alletra 6000

• OS version 6.0
• Synchronous replication is not supported
HPE Primera
• Fibre Channel (FC) or iSCSI (starting from OS versions 4.3 or later) connectivity
• OS versions 4.x
HPE Alletra 9000

• OS version 9.3
HPE StoreVirtual/LeftHand/P4000 series and StoreVirtual VSA
• iSCSI connectivity only
• LeftHand OS versions 9.5 up to 12.8
• HPE SV3200 (LeftHand OS version 13) is not supported
IBM FlashSystem (StorWize), IBM SVC, Lenovo Storage V Series

• IBM Spectrum Virtualize OS 7.6 or later
NetApp FAS/AFF, FlexArray (V-Series), ONTAP Edge/Select/Cloud VSA and FAS

OEM (Fujitsu ETERNUS HX/AX, IBM N series and Lenovo DM series)
• NFS, Fibre Channel or iSCSI connectivity
• ONTAP 7-mode versions 8.2 up to 8.2.5
• ONTAP cluster-mode versions 8.3 to 9.8, and 9.91
• MetroCluster is supported
• ONTAP features application-aware data management and SVM-DR are not supported
• NetApp Synchronous SnapMirror is not supported
NOTE
To start working with the following storage systems, you must install storage system plug-in.
DataCore SANsymphony
• DataCore SANsymphony 10.0 PSP12 or later
Dell EMC PowerMax

• Dell EMC PowerMax/VMAX All Flash (PowerMax OS microcode family 5978 or later)
• Unisphere for PowerMax 9.2.1.6 or later
Dell EMC PowerStore
• Dell EMC PowerStore T and PowerStore X series (PowerStore OS 2.0 or later)
Dell EMC SC Series/Compellent
• Storage Center OS 7.4.2 or later
• FluidFS volumes and Live Volumes are not supported
Fujitsu ETERNUS AF/DX series

• ETERNUS AF series: AF250 S2, AF650 S2, AF150 S3, AF250 S3, AF650 S3
• ETERNUS DX series: DX60 S4, DX100 S4, DX200 S4, DX500 S4, DX600 S4, DX8900 S4, DX60 S5,
DX100 S5, DX200 S5, DX500 S5, DX600 S5, DX900 S5
• Storage firmware version:
o ETERNUS AF S2 and DX S4 series (except DX8900 S4): V10L88-1000 or later
o ETERNUS AF S3 and DX S5 series, DX8900 S4: V11L30-5000 or later
Hitachi VSP
• VSP E590, E790, E990 (93-03-01-60/00 or later)
• VSP F350, F370, F700, F900 (88-07-01-x0/00 or later)
• VSP G350, G370, G700, G900 (88-07-01-x0/00 or later)
• VSP 5000 series (90-05-01-00/00 or later)
HPE XP
• HPE XP8 (90-05-01-00/00 or later)
Huawei OceanStor
• Huawei OceanStor Dorado V3 Series with software version V300R001 or later
• Huawei OceanStor Dorado V6 Series with software version 6.0 or later
• Huawei OceanStor V3 and F V3 Series with software version V300R006 or later
• Huawei OceanStor V5 and F V5 Series with software version V500R007 or later
INFINIDAT Infinibox F-series
• InfiniBox 3.0 or later
NOTE
You must add to the backup infrastructure only one of the two InfiniBox storage arrays for which
Active/Active Replication is configured, or exclude the replicating volumes on one of these arrays from
rescan. For details on how to exclude volumes from rescan, see the Rescanning Storage Systems section in
the Veeam Backup & Replication User Guide.
NetApp SolidFire/HCI
• iSCSI connectivity
• NetApp SolidFire support requires Element OS 9.0 or later
• NetApp HCI support requires Element OS 10.0 or later
Pure Storage FlashArray
• Purity 4.10 or later
• Purity ActiveCluster is supported. Direct access to a single proxy server from both storage arrays in the
cluster is required.
• Replicated volume snapshots on the target array are supported. For details, see this Veeam KB article.
Tintri IntelliFlash/Western Digital IntelliFlash/Tegile

• Tintri IntelliFlash 3.9.2, 3.10.1 or later

1
This version is supported starting from Veeam Backup & Replication <%BLDVER%>.
Required Permissions
To perform data protection and disaster recovery operations with storage snapshots, the account used to
connect to a storage system must have necessary permissions.
In This Section
• NetApp Data ONTAP/Lenovo Thinksystem DM Permissions
• Universal Storage API Integrated Systems Permissions
NetApp Data ONTAP/Lenovo Thinksystem DM Permissions

The account used to connect to a NetApp Data ONTAP/Lenovo Thinksystem DM 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-*
• api-feature-*
• api-registry-*
• api-fcp-*
• api-file-*
• api-igroup-*
• api-clone-*
• api-snapvault-*
• api-snapmirror-*
• api-cf-*
• cli-options
• security-api-vfiler
CDOT (VMware Integration)
Command/Directory Access/Query Level
DEFAULT readonly
cluster readonly
metrocluster readonly
fcp readonly
file readonly
igroup all
iscsi all
network readonly
node readonly
security readonly
security login readonly
set readonly
snapmirror all
system readonly
version readonly
qtree readonly
lun all
nfs all
snapshot all
volume all
vserver all
Only as SVM (VMware Integration)
DEFAULT none
lun all
lun igroup all
network readonly
security readonly
snapmirror all
system readonly
version readonly
volume all
volume file readonly
volume qtree all
volume snapshot all
vserver all
vserver fcp all
vserver iscsi all
vserver nfs all
CDOT (NAS Backup Integration)
DEFAULT readonly
security readonly
volume snapshot all
vserver all
vserver nfs all
Only as SVM (NAS Backup Integration)
DEFAULT none
lun readonly
network readonly
security readonly
snapmirror readonly
version readonly
volume readonly
volume snapshot all
vserver all
CDOT (Veeam Agent Integration)
cluster readonly
lun all
metrocluster readonly
network readonly
system license readonly
system node readonly
version readonly
volume all
volume snapshot all
vserver all
Only as SVM (Veeam Agent Integration)
lun all
network readonly
version readonly
volume all
volume snapshot all
vserver all
Universal Storage API Integrated Systems Permissions

The account used to connect to a Universal Storage API integrated system must be assigned a necessary role in
the storage system console and/or have a set of necessary permissions.
• For Dell EMC PowerMax, the account must be assigned the Storage Administrator role.
• For Fujitsu ETERNUS, the account must be assigned the Software role.
• For NetApp SolidFire/HCI, the account must have the following permissions:
o Volumes
o Cluster Admins
• For Western Digital IntelliFlash, the account must be assigned the Veeam Admin Role.
• For DataCore, the account must have the following permissions:
o General
o Port
o Host
o Virtual disk
o Snapshot
o Physical disk
• For Hitachi VSP, the account must be assigned the following roles:
o Storage Administrator (View Only)
o Storage Administrator (Provisioning)
o Storage Administrator (Local Copy)
• For HPE XP, the account must be assigned the following roles:
o Storage Administrator (View Only)
o Storage Administrator (Provisioning)
o Storage Administrator (Local Copy)
• For Dell EMC PowerStore, the account must be assigned the following roles:
o Administrator
o Storage Administrator
o Storage Operator
General Limitations
The following limitations apply to all storage systems supported by Veeam Backup & Replication:
• Backup infrastructure
• Backup from Storage Snapshots
• Snapshot Orchestration and Backup from Storage Snapshots with Snapshot Retention
• Veeam Explorer for Storage Snapshots
Backup Infrastructure (VMware, Veeam Agent integration)

Backup infrastructure for storage snapshots has the following limitations:
• CHAP authentication is not supported for storage systems working over iSCSI.
• SAS connections are not supported.
• Veeam Backup & Replication does not display volumes and snapshots with the 'VeeamAUX' prefix in the
storage hierarchy. Such volumes are used for service purposes and are filtered out.
Backup from Storage Snapshots (VMware integration)

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 temp lates.
• Processing of VMs with VMware vSphere snapshots may take much longer to start compared to using the
Direct SAN Access transport mode with iSCSI/FC SAN. In case these delays are unacceptable, we
recommend to either delete the VMware vSphere snapshots or avoid using storage snapshots integration
to protect such VMs.
• For storage systems working over NFS:
o VMs that you plan to back up or replicate must not have VMware vSphere snapshots. VMs with
snapshots are processed during regular backup job.
o If you enable the E na ble 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.
Snapshot Orchestration and Backup from Storage Snapshots

with Snapshot Retention (VMware integration)
Snapshot jobs (snapshot-only jobs and backup jobs with storage snapshot retention) have the following
limitations:
• If you remove or re-add a storage array that is already associated with a snapshot job,
Veeam Backup & Replication will restart the retention cycle. You will need to manually remove old
snapshots that are no longer needed.
• You cannot configure a job to create storage snapshots on arrays of different storage vendors.
• For IBM Spectrum Virtualize:
o Before you add this storage system to the backup infrastructure, make sure that a license for the IBM
Spectrum Virtualize storage system supports IBM FlashCopy.
o When you add IBM Spectrum Virtualize storage systems with HyperSwap function to the backup
infrastructure, Veeam Backup & 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.
o You can use backup jobs to create a snapshot chain either on a primary or on a secondary storage
array, but you cannot configure snapshot creation on both storage arrays at the same time.
• For HPE 3PAR StoreServ:
o 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.
o A license for the HPE 3PAR StoreServ storage system must support HPE 3PAR Virtual Copy.
o You can use backup jobs to create a snapshot chain either on a primary or on a secondary storage
array, but you cannot configure snapshot creation on both storage arrays at the same time.
• For snapshot-only jobs:
o 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.
o Veeam Backup & Replication does not support guest file indexing for snapshot-only jobs.
o You cannot perform backup of VMs residing on a VMware datastore that comprises several LUNs.
Veeam Explorer for Storage Snapshots (VMware integration)

Veeam Explorer for Storage Snapshots has the following limitations:
• During restore of VM guest OS files from storage snapshots, data is transferred over LAN through the
Network Block Device protocol (NBD). Therefore, restore performance may not be optimal.
• 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.
• You can restore data of a VM whose disks are hosted on different VMware datastores (multi-home
restore). This is true for storage snapshots created both as snapshot-only jobs and backup jobs with
storage snapshot retention. However, if you restore from native storage snapshots or snapshots that were
created with earlier versions of Veeam Backup & Replication (up to version 9.5 Update 4), mind the
following:
o The restored VM will have only those VM disks that are hosted on the same datastore as the VMX file.
o You will be able to restore VM guest OS files or application items only from those VM disks that are
hosted on the same datastore as the VMX file.
o You will not be able to restore VM disks that contain the absolute path in the VMX file.
o [For HPE Nimble and NetApp] You will not be able to perform Instant Recovery and restore VM guest
OS files to the original location from snapshots on secondary storage arrays.
To overcome these limitations, you must restore from storage snapshots created with the current version
of Veeam Backup & Replication (starting from version 9.5 Update 4).
• If you remove or re-add a storage array to the backup infrastructure, you will be able to restore data only
from those VM disks that are hosted on the same datastore as the VMX file.
• You cannot restore data of a VM whose disks are hosted on storage systems of different storage vendors.
• Multi-OS file-level restore is not supported for encrypted VMs.
• Multi-OS file-level restore with Mount Host is not supported for storage snapshots.
• 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 Cop y to option instead.
• If the original VM is removed from vSphere infrastructure or migrated to another datastore, you will not
be able to perform VM guest OS files restore to the original location.
Cisco HyperFlex Limitations
[For VMware integration] 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 the System
Requirements section in the Veeam Backup & Replication User Guide.
• Currently Veeam Backup & Replication does not support scenarios where several Cisco HyperFlex systems
are registered under different vCenter Servers. It is recommended that you back up VMs of each vCenter
Server instance using a separate Veeam backup server.
• VMs must not have VMware vSphere snapshots.

During backup or replication, Veeam Backup & Replication fails to trigger Cisco HyperFlex snapshots on
VMs that already have VMware vSphere snapshots. You can instruct Veeam Backup & Replication to
process these VMs in the regular data processing mode. To do this, enable the Fa ilover to standard backup
option in job settings.
• Disks of a processed VM must be hosted on the same Cisco HyperFlex NFS store. If some VM disks are
hosted on an NFS store other than the store where the VM configuration file resides, 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.
• For working with REST API, use default route and default port: https://{hostname}:443.
Dell EMC VNXe, VNX, SC Limitations
If you plan to perform operations with Dell EMC storage snapshots, consider the following limitations:
• Dell EMC VNXe
• Dell EMC VNX Block
• Dell EMC VNX File
• Dell EMC SC
Dell EMC VNXe

The following limitations apply to Dell EMC VNXe storage systems:
• [For VMware, Veeam Agent integration] In Dell EMC VNXe, you cannot export more than one 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.
• [For VMware integration] 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:
o 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.
o 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.
o 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).
o 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.
This limitation does not apply to Dell EMC Unity storage systems.
Dell EMC VNX Block

[For VMware, Veeam Agent integration] The following limitations apply to Dell EMC VNX Block storage
systems:
• 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

[For VMware integration] The following limitations apply to Dell EMC VNX File storage systems:
• A read-only checkpoint can have only one 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 SC (formerly Compellent)

[For VMware, Veeam Agent integration] Make sure that multiple proxy servers are not part of a single Server
object.
NetApp Data ONTAP/Lenovo Thinksystem DM
Limitations
If you plan to perform operations with NetApp Data ONTAP/Lenovo Thinksystem DM storage snapshots,
consider the following limitations:
• [For VMware integration] Veeam Backup & Replication may fail to perform backup from secondary storage
arrays if SVM/volumes have identical names between primary and secondary storage arrays.
• [For VMware, Veeam Agent integration] When the storage is added as a specific SVM, and not as a whole
cluster, you must set up Aggregation List for vServer so that FlexClone Volume would work properly.
Otherwise, errors like this will arise: ‘Cannot create volume. Reason: aggregate aggr1 is not in aggr-list of
Vserver svm-dr-nfs.’
• [For NAS, Veeam Agent integration] Depending on the protocol type and operating mode of the storage
system, Veeam Backup & Replication uses different technologies to perform the following operations:
o [For VMware integration] Storage system rescan
o [For VMware, NAS, Veeam Agent integration] Backup from storage snapshots
o [For VMware integration] Restore from storage snapshots
You may need to install additional licenses. You need to install one license, even if several technologies
can be used for snapshot clone creation.
• [For VMware, NAS integration] NetApp FlexGroups are not supported for storage snapshot integration
scenarios (including NAS Backup).
• [For VMware integration] Backup jobs from storage snapshots with secondary target are not supported if
several SnapMirror/SnapVault relationships are configured for one source volume.
• [For VMware integration] Multi-home restore is not supported for NetApp 7-mode with NFS protocol (all
snapshots) and for SnapMirror Target Snapshots with NFS or iSCSI/FC protocol.
• [For VMware, NAS integration] The snapshot directory must be visible in the NFS or SMB shares. To learn
more about making the snapshot directory visible, see NFS and SMB (CIFS) Protocols.
Rescan of NetApp Storage Systems
7-Mode
Storage FlexClone Sna pRestore No license (Traditional LUN

Ty p e ( recommended) cloning)
P rimary Storage System
iSCSI/FC Possible Possible (not used) Possible
NFS Possible (not used) Possible (not used) Possible (not used)
Storage FlexClone Sna pRestore No license (Traditional LUN
Ty p e ( recommended) cloning)
Secondary Storage System: SnapMirror and SnapVault
iSCSI/FC Possible Possible (not used) for Possible for SnapVault

SnapVault
Not possible for SnapMirror
NFS Possible (not used) Possible (not used) Possible (not used)
cDot
Storage Type FlexClone (recommended) Sna pRestore No license (Traditional LUN cloning)
iSCSI/FC Possible Possible Not possible
NFS Possible (not used) Possible Possible
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.
7-Mode
Storage Type FlexClone (recommended) Sna pRestore No license

( Traditional
LUN
cloning)
iSCS/FC Possible Possible (not used) Possible
NFS Possible (not used) Possible (not used) Possible

(not used)
iSCS/FC Possible Possible (not used) for Possible

SnapVault for
SnapVault
Not
possible
for
SnapMirror

(not used)
cDot
Storage Type FlexClone Sna pRestore No license (Traditional

( recommended) LUN cloning)
Storage Type FlexClone Sna pRestore No license (Traditional
( recommended) LUN cloning)
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 VMware, Veeam Agent integration] 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 backup 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 momentary image of the LUN and captures the exact sta te 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.
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
[For VMware, Veeam Agent integration] 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 VMware, Veeam Agent integration] 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 backup data.
2. Veeam Backup & Replication creates a LUN clone using SnapRestore.
NFS and SMB (CIFS) Protocols
[For VMware, NAS integration] If the NetApp storage system operates over SMB (CIFS) (for NAS integration) or
over NFS (both for VMware and NAS integration), 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
file share with backup data resides. The created volume snapshot is used as a source of data.
Veeam Backup & Replication uses the client on the backup proxy and the proxy reads the data from the shared
folder storing the volume snapshot.
Requirements for NFS Protocol

Make sure that the following requirements are met:
• [For VMware, NAS integration] NFS access rules (SVM export policies) are created. VBR can create the NFS
access rules automatically. You can turn off this option, but in this case make sure the settings are correct.
• [For VMware integration] If you are using a secondary NetApp in backup process, its volumes are mounted
(have configured mount path).
• [For VMware, NAS integration] The snapshot directory (.snapshot) is visible in the NFS volumes. To ensure
that, login to your NetApp Ontap System Manager, select the NFS volume, click Sna pshot Copies –
Configuration Settings and select the box Ma k e Snapshot directory (.snapshot) visible.
Requirements for SMB (CIFS) Protocol

[For NAS integration] Make sure that the following requirements are met:
• SMB (CIFS) access rules (SVM export policies) are created. VBR can create the SMB access rules
automatically. You can turn off this option, but in this case make sure the settings are correct.
• Permissions for access to the SMB share are properly configured. To ensure that, login to your NetApp
Ontap System Manager, select the SMB share in Storage – Sha res, click E d it to open share settings, and
configure permissions in the P ermissions tab.
• The snapshot directory (~snapshot) is visible in the SMB share. To ensure that, login to your NetApp Ontap
System Manager, select the SMB share in Storage – Sha res, click E d it to open share settings, and select the
Show Snapshots check box in the Op tions tab.
Restore from Storage Snapshots
7-Mode
Storage Type FlexClone Sna pRestore No license NDMP

( recommended) ( Traditional LUN
cloning)
iSCS/FC Possible Possible (not used) Possible Not possible
NFS Possible Possible1 Not possible Possible
iSCS/FC Possible Possible for Possible for Not possible

SnapVault SnapVault
Not possible for Not possible for

SnapMirror SnapMirror
NFS Possible for Possible for Not possible Possible

SnapMirror SnapVault1
Not possible for Not possible for

SnapVault2 SnapMirror
1
Veeam Backup & Replication copies VM files from the /vol/volname/VMFolder/ folder from the snapshot to
the /vol/vvolname/Veeam_Restore_VMname/VMFolder/ folder. The restore wizards work with copied files.
2
Can be used only for file-level restore. To enable restore, you can use registry keys. For more information, contact Veeam
Support Team.
cDot
NFS Possible Possible Not possible
NFS Possible 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.
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 using 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 ESXi
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 ESXi host. After you finish the restore process for
the last VM on the storage snapshot, the folder is unmounted from the ESXi host.
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.
IMP ORTANT
[For Instant Recovery] Veeam Backup & Replication performs actual Instant 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 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.
technology.
If neither FlexClone nor SnapRestore license is installed, VM data restore will fail.
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.
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.
IMP ORTANT
[For Instant Recovery] If you restore data from NetApp SnapVault, Veeam Backup & Replication performs
entire VM restore instead of Instant 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.
Universal Storage API Integrated Systems
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 the Veeam
Universal Storage API framework to integrate their storage solutions with Veeam Backup & Replication. With
this kind of integration, you can use snapshots of Universal Storage API integrated systems to perform backup
and restore operations.
The following storage systems are supported:
• DataCore SANsymphony
• Dell EMC PowerMax
• Dell EMC PowerStore
• Dell EMC SC Series/Compellent
• Fujitsu ETERNUS DX/AF series
• Hitachi VSP
• HPE XP
• Huawei OceanStor
• INFINIDAT InfiniBox
• NetApp SolidFire/HCI
• Pure Storage FlashArray
• Tintri IntelliFlash/ Western Digital/Tegile
To start working with Universal Storage API integrated systems, you must perform the following steps:
1. Download the necessary storage system plug-in from the Veeam Download page.
2. Install the storage system plug-in.
3. Configure the backup infrastructure for storage integration.
Prerequisites for API Integrated Systems
[For VMware, Veeam Agent integration] Before you add storage systems to Veeam Backup & Replication, check
the following prerequisites:
• You must install the storage system plug-in. For more information, see Installing Storage System Plug-Ins.
• For Fujitsu ETERNUS storage systems, you must obtain and install the Veeam Storage Integration license
The Veeam Storage Integration license is free of charge. You can obtain the license from the Fujitsu
website.
• Fujitsu ETERNUS storage plug-in will not work with FIPS policy enabled on the
Veeam Backup & Replication server.
• For Tintri IntelliFlash/ Western Digital IntelliFlash/Tegile storage systems, make sure that multiple proxy
servers are not part of a single Initiator Group object.
• For DataCore storage plug-in, you must not use commas in the password for the account that you plan to
use to access the storage.
• For Huawei storage plug-in, adding the storage as a specific vStore is supported over NFS only.
To learn prerequisites for other API integrated systems, see the following Veeam KB articles:
• Veeam KB article 4200 on Dell PowerMax limitations
• Veeam KB article 4243 on Dell PowerStore limitations
• Veeam KB article 4191 on Hitachi VSP limitations
• Veeam KB article 4194 on HPE XP limitations
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.
To install a 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 the Veeam
Download page.
2. On the welcome screen of the setup wizard click the Nex t button to proceed to the configuration of the
installation.
3. At the Terms of Usage step of the wizard, select I a ccept these terms.
4. At the Rea dy 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 Integration.
Update Notifications
Veeam Backup & Replication uses update notifications to inform you about new versions of Universal Storage
API integrated system plug-ins. When a new version of a plug-in becomes available on the website,
Veeam Backup & Replication displays an icon in the system tray. An icon is displayed once a week.
To get a new version of a plug-in, double-click the Veeam Backup & Replication icon in the system tray.
Veeam Backup & Replication will open the Veeam Download page where you can download the plug-in.
To install the plug-in, follow the steps described in the Installing Storage System Plug-Ins section.
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), Unity XT/Unity
• HPE 3PAR StoreServ and Primera, including secondary volumes — HPE 3PAR Peer Persistence
• HPE StoreVirtual/LeftHand/P4000 series and HPE StoreVirtual VSA (Virtual Storage Appliance)
• IBM Spectrum Virtualize, including secondary IBM volumes — IBM Spectrum Virtualize HyperSwap
• NetApp, including secondary arrays — NetApp SnapMirror and NetApp SnapVault
• HPE Nimble storage, including secondary 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.
• Ap p lication 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 ESXi 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. F or
more information, see the Veeam Explorer for Storage Snapshots section in the
3. The snapshot copy is presented as a new datastore to the ESXi 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.
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 ESXi 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 ESXi host.
The number of NFS datastores that can be mounted to the ESXi 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 ESXi
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 this VMware KB article.
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 ESXi 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 ESXi hosts are
not freed within 20 minutes, the SureBackup job fails.
Limitations for On-Demand Sandbox for Storage Snapshots

Before you start using On-Demand Sandbox for storage snapshots, check limitations for Veeam Explorer for
Storage Snapshots. For more information, see the General Limitations section in the

Veeam Backup 11 0 Storage Integration User Guide

Uploaded by

Copyright:

Available Formats

Veeam Backup 11 0 Storage Integration User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Veeam Backup 11 0 Storage Integration User Guide

Uploaded by

Copyright:

Available Formats

Veeam Backup & Replication

2 | V eeam Backup & Replication | Integration with Storage Systems Guide

3 | V eeam Backup & Replication | Integration with Storage Systems Guide

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

• Veeam R&D Forums: forums.veeam.com

4 | V eeam Backup & Replication | Integration with Storage Systems Guide

5 | V eeam Backup & Replication | Integration with Storage Systems Guide

• Veeam Agent for Microsoft Windows integration

6 | V eeam Backup & Replication | Integration with Storage Systems Guide

Op erati Dell HP E HP E HP E NetApp Cisco IBM Univers

Ba ckup from Storage Snapshots

7 | V eeam Backup & Replication | Integration with Storage Systems Guide

Veeam Explorer from Storage Snapshots

Sna pshot Orchestration

8 | V eeam Backup & Replication | Integration with Storage Systems Guide

Ba ckup from Storage Snapshots with Snapshot Retention

9 | V eeam Backup & Replication | Integration with Storage Systems Guide

10 | V eeam Backup & Replication | Integration with Storage Systems Guide

Regular VM Data Processing

Backup from Storage Snapshots

11 | V eeam Backup & Replication | Integration with Storage Systems Guide

Backup from Primary Storage Arrays

12 | V eeam Backup & Replication | Integration with Storage Systems Guide

6. Mounts the storage snapshot as a new volume to this backup proxy.

Mixed Job Scenarios

13 | V eeam Backup & Replication | Integration with Storage Systems Guide

Configuring Backup from Storage Snapshots

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

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

14 | V eeam Backup & Replication | Integration with Storage Systems Guide

15 | V eeam Backup & Replication | Integration with Storage Systems Guide

Backup from Secondary Storage Arrays

• IBM Spectrum Virtualize with HyperSwap

• Lenovo V Series with HyperSwap

• HPE Nimble arrays with replicated copies

• NetApp SnapMirror and/or NetApp SnapVault

16 | V eeam Backup & Replication | Integration with Storage Systems Guide

How Backup from Secondary Storage Systems Works

4. The transported storage snapshot is mounted to the detected backup proxy.

17 | V eeam Backup & Replication | Integration with Storage Systems Guide

Failover to Backup from Snapshots on Primary Storage Arrays

18 | V eeam Backup & Replication | Integration with Storage Systems Guide

Configuring Backup from Snapshots on Secondary Storage Arrays

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

19 | V eeam Backup & Replication | Integration with Storage Systems Guide

To back up VMs from snapshots on secondary storage arrays:

20 | V eeam Backup & Replication | Integration with Storage Systems Guide

For more information, see Adding Storage Systems.

21 | V eeam Backup & Replication | Integration with Storage Systems Guide

22 | V eeam Backup & Replication | Integration with Storage Systems Guide

23 | V eeam Backup & Replication | Integration with Storage Systems Guide

3. Specify other backup job settings as required.

4. Click Nex t, then click Finish to save the job settings.

Limitation on Number of VMs per Snapshot

24 | V eeam Backup & Replication | Integration with Storage Systems Guide

6. Veeam Backup & Replication removes the storage snapshot.

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

25 | V eeam Backup & Replication | Integration with Storage Systems Guide

26 | V eeam Backup & Replication | Integration with Storage Systems Guide