Veeam Backup Repositories

Veeam Plug-ins store backup files in repositories added to the Veeam Backup & Replication infrastructure. This section lists supported types of backup repositories and limitations for Veeam Plug-in for Microsoft SQL Server backups.

Before you start performing operations on backup repositories within the Veeam Backup & Replication infrastructure, consider that you need to set the access permissions for each repository. For details, see Access and Encryption Settings on Backup Repositories.

Supported Backup Repositories

You can use the following types of repositories added to the Veeam Backup & Replication infrastructure to store backups created with Veeam Plug-in for Microsoft SQL Server:

• Windows Server
• Linux Server

• SMB (CIFS) Share

• NFS Share

• Dell Data Domain with Data Domain Boost (DDBoost)
• HPE StoreOnce

If you plan to use HPE StoreOnce as a backup repository for Veeam Plug-in backups, the total number of stored files (data and metadata) must not exceed 3,000,000 per Catalyst store. If necessary, multiple Catalyst stores may be created on the same StoreOnce system.

• Quantum DXi

• ExaGrid

Make sure the repository is configured as described in the ExaGrid section in the Veeam Backup & Replication User Guide.

• Hardened Repository

• Scale-Out Backup Repository

Make sure that the performance extents of the scale-out backup repository contain repositories supported by Veeam Plug-in for Microsoft SQL Server. For example, you cannot use object storage repositories as performance extents to keep backups created with Veeam Plug-ins.

Backup Repository Limitations

• For Veeam Plug-in backups, the warning which indicates that free space on a storage device has reached a specified threshold is configured in the veeam_config.xml file of Veeam Plug-in. The warning settings in the Veeam Backup & Replication console does not affect this setting.

To configure the warning settings, add the following parameter in the veeam_config.xml file:

Keep in mind that you must add the parameter to the existing line in the veeam_config.xml file. If you create a new line with the same name as the existing line, Veeam Plug-in will consider parameters only in the first detected line. Other parameters will be ignored.

• The plug-in configuration wizard will not show repositories where the Encrypt standalone application backups stored in this repository option is enabled. To learn how to disable the encryption option, see Access and Encryption Settings on Backup Repositories.

If you want to use the same backup target with the repository-based encryption and Veeam Plug-ins, create a second repository in the subfolder for Veeam Plug-in backups.

Alternatively, you can use transparent data encryption (TDE) provided by Microsoft. Using TDE, you can encrypt database data with an encryption key, back up encrypted data with Veeam Plug-in, then restore data and decrypt using the same encryption key. To learn more about TDE encryption, see this Microsoft article.

• Veeam extract utility cannot extract Veeam Plug-in backup files. By design of Microsoft SQL Server, these files cannot be imported “as files” as they contain additional metadata bound to the used SBT device.

• Veeam Plug-ins do not support backup operations targeted directly to object storage repositories.

To learn more about object storage repositories, see the Object Storage Repositories section in the Veeam Backup & Replication User Guide.

• Veeam Plug-ins do not support backup operations to object storage added as a performance extent of a scale-out backup repository.

Veeam Scale-Out Backup Repositories

If you want to store Veeam Plug-in backups in scale-out backup repositories, consider the following:

• You cannot rename a scale-out backup repository with Veeam Plug-in backups stored on this repository.

• If you want to add a backup repository as an extent to a scale-out backup repository and Veeam Plug-in backups are present on this backup repository, you must do the following:

1. In the Veeam Backup & Replication console, select Veeam Plug-in backup files that reside in this backup repository and remove them from configuration. For details, see Removing Backups from Configuration. Note that this action does not delete the backups from the repository.
2. In the Veeam Backup & Replication console, delete the Veeam Plug-in backup job. For details, see Deleting Jobs.
3. Add the repository as an extent to the scale-out repository. For details, see Extending Scale-Out Repositories.
4. Rescan the scale-out repository. For details, see Rescanning Scale-Out Repositories.

5. On the Veeam Plug-in server, launch the Configure Plug-in wizard and set the scale-out repository as the target for backups:

Alternatively, you can use the following command in the command line interface:

6. At the Backup Repository step of the wizard:

1. From the Backup repository drop-down list, select the scale-out repository.
2. Click Map backups to map the imported backups stored in the backup repository.

• For Veeam Plug-in backups and backup copies, the Performance policy of a scale-out repository functions differently:

1. Veeam Backup & Replication checks if there are extents without warning on free space insufficiency. If all extents have the warning, Veeam Backup & Replication uses an extent with the largest amount of free space that has a free task slot.
2. If there are extents without the warning, Veeam Backup & Replication checks if there are incremental extents with free task slots. If there are no incremental extents with free task slots, Veeam Backup & Replication uses a full extent with the least amount of used task slots.
3. If there are incremental extents with free task slots, Veeam Backup & Replication sends backup files to an incremental extent with the least amount of used task slots. If the amount of used tasks is the same, an extent with the largest amount of free space.

To learn more about file placement policies of scale-out repositories, see Backup File Placement section in the Veeam Backup & Replication guide.

• If a scale-out repository is configured in the Data locality policy, repository extents will be selected according to the largest amount of free space for each Microsoft SQL Server connection. If the selected extent does not have free task slots, Veeam Backup & Replication uses the extent with the next largest amount of free space. If there are two extents with only one slot on each extent, the backup will be launched on two streams (one on each extent).

Capacity Tier

You can configure Veeam Backup & Replication to transfer Veeam Plug-in backup files to the capacity tier. Both policies (Move policy, Copy policy) are supported for Veeam Plug-in backups with the following limitations:

• For Veeam Plug-in backup files, capacity tier does not verify whether data that is being moved is unique and has not been offloaded earlier. Thus, it is highly recommended to check the pricing plans of your cloud storage provider to avoid additional costs for offloading and downloading backup data.

• To offload Veeam Plug-in backup files to the capacity tier, Veeam Backup & Replication splits data into 1 MB objects and compresses the resulting objects. The default object size will be a compressed 1 MB block, resulting in objects of around 512 KB in size.

• [For the Move policy] For Veeam Plug-in for Microsoft SQL Server backups, capacity tier tracks dependencies of full and differential backup files. Thus, Veeam Backup & Replication tracks inactive backup chains and moves them to the capacity tier. No limitations apply to the operational restore window.

• Veeam Backup & Replication offloads Veeam Plug-in for Microsoft SQL Server backup files to the capacity tier with the Copy and Move policies in different ways. With the Copy policy, Veeam Backup & Replication checks backup files every 1 hour and runs an offload job only if new backup files exist. With the Move policy, Veeam Backup & Replication checks backup files every 4 hours and runs an offload job, even if there are no new files.

• Veeam Plug-in supports encryption of offloaded data to the capacity tier. The Encrypt data uploaded to object storage option in the Capacity Tier settings of the scale-out backup repository ensures that the entire collection of blocks along with the metadata will be encrypted while being offloaded. To learn more about capacity tier encryption, see the Encryption for Capacity Tier section in the Veeam Backup & Replication User Guide.

• In case a disaster strikes the scale-out repository and you have a Veeam Plug-in backup file on the capacity tier, you must re-create the scale-out repository before you restore from this backup file. You must connect the capacity tier with the Veeam Plug-in backup file to another backup server with Veeam Backup & Replication and a scale-out repository. After that, you can import the backup files to Veeam Backup & Replication and then perform data recovery operations.

• If you use a capacity tier that has been created in Veeam Backup & Replication version 10, you cannot transfer Veeam Plug-in backup files to a capacity tier. However, if you want to transfer them manually, do the following:

1. If the backup files are created by Veeam Plug-in version 10, upgrade the metadata of backup files as described in the Upgrading Backup Files section.
2. Run the Set-VBRScaleOutBackupRepository cmdlet with the EnablePluginBackupOffload parameter to offload backup files to the capacity tier.

Hardened Repository

You can configure Veeam Backup & Replication to transfer Veeam Plug-in backup files to a hardened repository. The hardened repository helps to protect Veeam Plug-in backup files from loss as a result of malware activity or unplanned actions. Backup files in the hardened repository become immutable for the time period specified in the backup repository settings. During this period, backup files stored in the repository cannot be modified or deleted.

For Veeam Plug-in for Microsoft SQL Server backups, immutability works according to the following rules:

• Immutability is applied to backup (.VAB) files and backup metadata (.VASM) files. Backup job metadata (.VACM) files are not immutable.

• Backup files become immutable for the configured time period (minimum 7 days, maximum 9999 days).

• Backup files become immutable after 24 hours have passed since each file was created. The immutability service runs in the background at every hour. This service detects and sets immutability flags for any backup file that can no longer be reused.

• The immutability period is automatically extended for backup files that contain restore points of the active chain.

Data Restore from Hardened Repository

As a result of malware activity or unplanned actions, backup job metadata (.VACM) files may become unavailable in the hardened repository. In this case, to restore data from the hardened repository, you must re-create the .VACM file. To do this, complete the following steps:

1. Run a Veeam Plug-in backup job to create a new Veeam Plug-in backup in a Veeam backup repository. The backup will consist of the .VAB, .VASM and .VACM files.
2. In the backup repository folder, replace the .VAB and .VASM files created at the step 1 with the .VAB and .VASM files from the hardened repository.
3. In the Veeam backup console, run the backup repair operation. Veeam Backup & Replication will generate a new .VACM file using information from the .VASM files. For details, see Repairing Backup.

Once the backup job metadata file is re-created, you can use Veeam Plug-in to restore your data.