Veeam Backup & Replication 9.5 Update 4
User Guide for VMware vSphere
Related documents

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 NetApp] You must configure volume SnapMirror/Snapvault relationships between the primary and secondary storage arrays. For more information, see the NetApp documentation.

To configure a backup job:

  1. Open the Home view.
  2. Click Backup Job > VMware or vCloud on the ribbon. Veeam Backup & Replication will launch the New Backup Job wizard.
  3. At the Name step of the wizard, specify a name and description for the backup job.
  4. At the Virtual Machines step of the wizard, select VMs whose disks are hosted on the storage system.
  5. At the Storage step of the wizard, from the Backup repository list select a backup repository where you want to store backup files.
  6. In the Retention policy section, specify the number of backup restore points that you want to keep.
  7. Select the Configure secondary destinations for this job check box.

Configuring Backup Jobs with Storage Snapshot Retention 

  1. At the Secondary Target step of the wizard, click Add and select primary or secondary storage arrays to create snapshots.
  2. In the Number of snapshot copies to retain field, specify the number of storage snapshots that you want to maintain in the snapshot chain. When this number is exceeded, Veeam Backup & Replication will trigger the storage system to remove the earliest snapshot from the snapshot chain. Mind that the number of snapshots in the snapshot chain on the primary storage array cannot be fewer than 1.

Configuring Backup Jobs with Storage Snapshot Retention Note:

The Number of snapshot copies to retain option is not applicable to NetApp SnapMirror and HPE 3PAR Peer Persistence. On these secondary storage systems, Veeam Backup & Replication maintains the same number of storage snapshots as on primary storage systems.

If you use SnapMirror relationships between QTrees, you can define different retention policy settings for the primary NetApp storage system and NetApp SnapMirror. For example, you can configure the backup job to maintain 14 snapshots on the primary NetApp storage system and 10 snapshots of QTree directories on NetApp SnapMirror.

Configuring Backup Jobs with Storage Snapshot Retention 

  1. Specify other backup job settings as required.
  2. Click Next, then click Finish to save the job settings.

Configuring Backup Jobs with Storage Snapshot Retention 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 Protected by column.

Related Topics

Backup from Storage Snapshots with Snapshot Retention

This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VEnterprise Manager User GuideVeeam Cloud Connect GuideVeeam Agent Management GuideVeeam Explorers User GuideBackup and Restore of SQL Server DatabasesVeeam Plug-ins for Enterprise ApplicationsPowerShell ReferenceVeeam Explorers PowerShell ReferenceRESTful API ReferenceRequired Permissions ReferenceQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:


I want to let the Veeam Documentation Team know about that.