Veeam Backup Repositories
Veeam Plug-ins store backup files in repositories added to the Veeam Backup & Replication infrastructure. In this section, you can find the list of supported backup repositories and limitations for Veeam Plug-in backups.
Veeam Plug-in for SAP on Oracle supports integration with the following types of repositories added to the Veeam Backup & Replication infrastructure:
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.
Make sure the repository is configured as described in the ExaGrid section of the Veeam Backup & Replication User Guide.
You can also use scale-out backup repositories that contain repositories supported by Veeam Backup & Replication.
- 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.
<PluginParameters repositoryFreeSpacePercentWarning="10" />
- The plug-in configuration wizard will not show repositories where the Encrypt backups stored in this repository option is enabled. To learn how to disable the encryption option, see Access and Encryption Settings on 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.
- Veeam extract utility cannot extract Veeam Plug-in backup files.
If you want to store Veeam Plug-in backups on scale-out backup repositories, consider the following:
- You cannot rename a scale-out backup repository with Veeam Plug-in backups stored on this repository.
- For Veeam Plug-in backups and backup copies, the Performance policy of a scale-out repository functions differently:
- Veeam Backup & Replication checks if there are extents without warning on free space insufficiency.
If there is no extents without the warning, Veeam Backup & Replication uses an extent with the largest amount of free space that has a free task slot.
- For the 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.
- For 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 several extents has the same least amount of used tasks, Veeam Backup & Replication uses 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 of the Veeam Backup & Replication guide.
- If a scale-out repository is configured in the Data locality policy, each time BR*Tools starts a new channel for transferring backup files, Veeam Plug-in checks the free space in the extents and selects a scale-out backup repository extent that has the largest amount of free space.
If there are two extents with only one task slot on each extent, the backup is performed using two parallel streams (one stream per extent).
- If you want to add a backup repository which contains Veeam Plug-in backups as an extent to a scale-out backup repository, you must do the following:
On the Veeam Backup & Replication console side
- Select Veeam Plug-in backup files that reside in this backup repository and remove them from configuration.
To learn more, see the Removing Backups from Configuration section in the Veeam Backup & Replication User Guide.
- Delete the Veeam Plug-in backup job.
To learn more, see the Disabling and Deleting Jobs section in the Veeam Backup & Replication User Guide.
- Add the repository as an extent to the scale-out repository.
To learn more, see the Extending Scale-Out Repositories section in the Veeam Backup & Replication User Guide.
- Rescan the scale-out repository.
To learn more, see the Rescanning Scale-Out Repositories section in the Veeam Backup & Replication User Guide.
Before importing your backup to the scale-out backup repository, consider that the names of all backup files (.VAB, .VASM, .VACM) and paths to these files contain only the following allowed characters:
If your backup was initially created on a standalone backup server, the default name of the backup metadata file (.VACM) contains forbidden characters. Before importing, you must delete forbidden characters from the file name or replace them with the allowed characters.
On the Veeam Plug-in side
- On the Veeam Plug-in server, set the scale-out repository as the target for backups using the following command:
- Map the imported backups using the following command:
You can configure Veeam Backup & Replication to transfer Veeam Plug-in backup files to a 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.
- Capacity tier does not track dependencies of full and incremental Veeam Plug-in backup files. Thus, consider the following:
- [For the Move policy] When backup files are transferred to the capacity tier, Veeam Backup & Replication takes into account only the creation time of backup files. Make sure that the operational restore window is not longer than the whole backup chain cycle period. Otherwise, you may encounter the scenario when full backup files are transferred to the capacity tier and their increment backup files still remain in the performance tier.
- The capacity tier immutability expiration date does not have the additional block generation period. The immutability expiration date is based only on the number of days specified in settings of the object storage backup repository.
- 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.
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 SAP on Oracle 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).
- After reaching one of the VAB file reuse limits, the count of the immutability period begins. 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 not extended for the active backup 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. For more information, see Restore from Hardened Repository.