Limitations for Scale-Out Backup Repositories

Scale-out backup repositories have the following limitations:

  • The scale-out backup repository functionality is available in the Enterprise and Enterprise Plus editions of Veeam Backup & Replication.

If you configure a scale-out backup repository and then downgrade to the Standard license, you will not be able to run jobs targeted at the scale-out backup repository. However, you will be able to perform restore from the scale-out backup repository.

For each scale-out backup repository, you can add 1 object storage repository as a capacity extent and 4 standard backup repositories as performance extents: 3 active, and 1 inactive (that is put to the Maintenance mode). You can add inactive extents, for example, if any of active extents has no free space, and you want to evacuate backup data from it.

If you add 4 performance extents and do not put any of them to the Maintenance mode, the jobs targeted at the scale-out backup repository will fail.

Enterprise Plus edition has no limitations on the number of scale-out backup repositories or performance extents.

Names of VBM file and paths to VBM files must not contain spaces.

If a name of a VBM file or a path to a VBM file contains prohibited characters, Veeam Backup & Replication will fail to import such backup during rescan of the scale-out backup repository. To import such backup, you can replace prohibited characters with the underscore character, for example: C:\My Repository\Backup_Job\Backup_Job.vbm. You do not need to rename backup files themselves.

I want to report a typo

There is a misspelling right here:


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