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 Oracle RMAN supports integration with the following types of repositories added to the Veeam Backup & Replication infrastructure:

    • ExaGrid
    • HPE StoreOnce. If you plan to use HPE StoreOnce as a backup repository for Veeam Plug-in for Oracle RMAN, the total number of stored files (data and metadata) must not exceed 1,000,000 per storage system.

    You can also use scale-out backup repositories that contain supported repository types.

    Backup Repositories Limitations

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

    <PluginParameters repositoryFreeSpacePercentWarning="10" />

    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.

    • If you use Veeam Plug-in version 9.5 Update 4, Veeam backup copy jobs are not able to process and copy the backups created by the plug-in.
    • Veeam extract utility cannot extract Veeam Plug-in backup files. By design of Oracle RMAN, these files cannot be imported “as files” to RMAN as they contain additional metadata bound to the used SBT device.

    Veeam Scale-Out Backup Repositories

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

    • If you want to migrate backup repositories to a scale-out backup repository and Veeam Plug-in backups are present on the repository, you must do the following:
    1. Transfer the folders that include backups to an existing scale-out backup repository extent.
    2. Rescan the scale-out backup repository.
    3. Set the scale-out backup repository as a target in the Veeam Plug-in settings.
    4. Rescan the repository that you want to add.
    5. Migrate the repository to the scale-out backup repository.
    • 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 will send 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.

    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, repository extents will be selected according to the amount of free space for each Oracle RMAN connection. If there are two extents with 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 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 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 Set-VBRScaleOutBackupRepository PowerShell command with the -EnablePluginBackupOffload parameter to offload backup files to the capacity tier.

    I want to report a typo

    There is a misspelling right here:


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