Veeam Backup Repositories

In this article

    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.

    Supported Backup Repositories

    Veeam Plug-in for SAP HANA supports integration with the following types of repositories added to the Veeam Backup & Replication infrastructure:

    • Follow the requirements in the ExaGrid section of the Veeam Backup & Replication User Guide.
    • In the global.ini of SAP HANA, set the max_recovery_backint_channels parameter value to a number lower than the repository task slots. ExaGrid recommends setting it to 1, and adjust gradually if needed.

    You can also use scale-out backup repositories that contain repositories supported by Veeam Backup & Replication.

    Backup Repositories Limitations

    To configure the warning settings, add the following parameter in the /opt/veeam/VeeamPluginforSAPHANA/veeam_config.xml file.

    <PluginParameters repositoryFreeSpacePercentWarning="10" />

    • Make sure Veeam backup repositories have enough free space to store database backups and transaction log backups. If required, you can use a scale-out backup repository.
    • If you use Veeam Plug-in for SAP HANA version 9.5 Update 4, Veeam Backup & Replication backup copy jobs does not process and copy the backups created by the plug-in.
    • Veeam extract utility cannot extract backup files created by Veeam Plug-in.
    • For security reasons, it is recommended to use separate repositories for different users and grant access to backup repositories only for required users.

    Scale-Out Backup Repositories

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

    • For Veeam Plug-in backups and backup copies, the Performance policy of a scale-out repository functions a little 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 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 least amount of used task slots. If the amount of used tasks is the same, an extent with the most amount of free space.
    • If a scale-out repository is configured in the Data locality policy, repository extents will be selected according to the amount of free space for each SAP HANA Backint connection. If there are two extents with one slot on each extent, the backup will be launched on two streams (one on each extent).
    • If you want to add repositories as extents to a scale-out backup repository, and Veeam Plug-in backups are present on the source repository, you must do the following:
    1. Copy the Veeam Plug-in job folder (the whole folder) to an existing scale-out backup repository extent.
    2. Delete the backups from the source repository.
    3. Rescan the source repository.
    4. Add the repository as an extent to the scale-out repository.
    5. Rescan the scale-out repository.
    6. Set the scale-out repository as target in the Veeam Plug-in settings.
    7. Map the imported backups using the following command:

    sudo SapBackintConfigTool --map-backup

    Capacity Tier

    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.
    • Capacity tier does not track dependencies of full and incremental Veeam Plug-in backup files. Thus, mind 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.
    • If a scale-out repository is down, you cannot restore from the Veeam Plug-in backup files stored on the capacity tier. In this case, you can only import the backup files manually and then perform the 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 Upgrading Metadata Files to New Format.
    2. Run the Start-VBROffloadBackupFile PowerShell command to send backup files to the capacity tier.

    • If you want to restore from backups stored on the capacity extent, at least one performance extent must be available or you must switch the catalog_backup_using_backint parameter to the False state in the global.ini file. Otherwise, at the end of the restore process, SAP Backint will not be able to back up the catalog and restore will fail.
    I want to report a typo

    There is a misspelling right here:


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