Performance tier of a scale-out backup repository is the level used for fast access to the data.
The performance tier of a scale-out backup repository can comprise one or more performance extents. A performance extent is a backup repository or an object storage repository added to the scale-out backup repository. The list of the performance extents is displayed at the Add Performance Extents step of the New Scale-out Backup Repository wizard.
After you add a backup repository or an object storage repository to the scale-out backup repository, they no longer exist as individual backup repositories.
When a backup repository or an object storage repository is added as a performance extent, some of its original settings are kept, and some are not. The following settings are kept, or inherited:
- Number of tasks that can be performed simultaneously
- Read and write data rate limit
- Data decompression settings
- Block alignment settings
- Connection mode (using gateway server or direct)
- Object storage consumption (for object storage repositories)
The following settings are not inherited:
- Rotated drive settings. Rotated drive settings are ignored and cannot be configured at the level of the scale-out backup repository.
- Per-machine backup file settings. Per-machine settings can be configured at the level of the scale-out backup repository.
Limitations for Backup Repositories
Consider the following limitations for backup repositories added as performance extents:
- The same limitations that are specific for certain types of backup repositories apply to the performance extents. For example, if you add Dell Data Domain as a performance extent to the scale-out backup repository, you will not be able to create a backup chain longer than 60 points in this scale-out backup repository.
- The performance extents of the scale-out backup repository should be located in the same site. Technically, you can add to the scale-out backup repository the performance extents that reside in different sites. However, in this case Veeam Backup & Replication will have to access VM backup files on storage devices in different locations, and the backup performance will degrade.
Limitations for Object Storage Repositories
Consider the following limitations for object storage repositories added as performance extents:
- You can add only one type of object storage repositories as performance extents of one scale-out backup repository. For example, if a first extent is an Amazon S3 object storage repository, the second extent must also be an Amazon S3 object storage repository. You cannot use the backup repository and the object storage repository for the same performance tier.
- Data located in object storage repositories is organized into a separate backup chain for every machine in a job.
In This Section