General Requirements and Limitations

The following limitations apply to all storage systems supported by Veeam Backup & Replication.

Infrastructure

Backup infrastructure for storage snapshots has the following requirements and limitations:

IPv6 Support

IPv6 is supported for the following storage systems:

If only management IPv6 connection is supported for a storage system, you can add this storage system to backup infrastructure using IPv6 address. However, all data traffic will be transferred over IPv4.

Note

Temporary IPv6 addresses are not supported for backup infrastructure components and backed-up machines. For more information about using temporary addresses, see this RFC section.

To use IPv6 addresses and resolve names using IPv6, configure IPv6 communication as described in the IPv6 Support section in the Veeam Backup & Replication User Guide.

[VMware Integration] Backup from Storage Snapshots

Backup from Storage Snapshots has the following requirements and 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.
  • To back up VM templates.
  • To back up encrypted VMs.
  • 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:
    • VMs that you plan to back up or replicate must not have VMware vSphere snapshots. VMs with snapshots are processed during regular backup job.
    • If you enable the Enable VMware tools quiescence option in the job settings, Veeam Backup & Replication will not use Backup from Storage Snapshots to process running Microsoft Windows VMs that have VMware Tools installed.
    • Backup from Storage Snapshots is not supported for SLES operating systems working over IPv6.
  • [For backup from secondary storage arrays] 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 the description of the storage system wizard.

[VMware Integration] Snapshot Orchestration and Backup from Snapshots with Snapshot Retention

Snapshot jobs (snapshot-only jobs and backup jobs with storage snapshot retention) have the following requirements and limitations:

  • The following applies to backup jobs with storage snapshot retention:
  • You must configure the backup infrastructure in the following way:
    • 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.
    • Add to the backup infrastructure vCenter Server or ESXi hosts with VMs whose disks are hosted on the storage system.
    • Add the storage system to the backup infrastructure. If you plan to perform backup from snapshots on secondary storage arrays, also add the secondary storage array to the backup infrastructure.
  • You must install a license for Veeam Backup & Replication Enterprise Plus edition on the backup server.
  • [For backup from secondary storage arrays] 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 the description of the storage system wizard.

[VMware Integration] Data Recovery from Storage Snapshots

Data recovery from storage snapshots has the following requirements and limitations:

FAT, NTFS or ReFS Restore from Storage Snapshots

Before you restore VM guest OS files from Microsoft Windows file systems, check the following requirements:

  • If you plan to restore VM guest OS files to their original location, you must make sure that VMware tools are installed on the target VM.
  • If you plan to restore guest OS files from a VM running Microsoft Windows ReFS, the Veeam Backup & Replication console must be installed on a machine running Microsoft Windows Server 2012 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 deduplication must be enabled on this machine.
  • 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.

Linux, Unix and Other File Systems Restore from Storage Snapshots

Before you restore VM guest OS files from Linux, Unix or other file systems, check the following requirements:

  • If you plan to restore VM guest OS files to their original location, make sure that VMware Tools are 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 arch and uname are installed on the VM guest OS.
  • 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 through VIX API/vSphere Web Services, you must use a root account for a target VM, otherwise the restore process will fail.
  • You cannot restore files directly to the original location from backups of BSD, Mac and Solaris VMs. You cannot restore files directly to the original location from NSS filesystems. Use the Copy to option instead.
  • 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.
  • For Linux target VM, consider the following:
    • 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.
    • SELinux must be disabled on the target VM.
    • 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.

Page updated 6/5/2024

Page content applies to build 12.1.2.172