Scale-Out Repository as NAS Backup Repository

In this article

    If you use a scale-out backup repository as a backup repository for storing NAS backups, by default Veeam Backup & Replication evenly distributes backup data among all the performance extents added to this repository. The NAS backup data is accompanied by the metadata files. To provide an opportunity to restore data written to extents remaining available in case one or two of other extents are unavailable, Veeam Backup & Replication triplicates metadata when writing it to extents. Thus, every extent keeps metadata for data stored on this extent (in folder meta) and replica of metadata for data stored on adjacent extents (in folder metabackup). Even if two of three adjacent extents are lost, you can restore NAS backup data stored on the third extent.

    Note

    Mind the following when storing NAS backups on a scale-out backup repository:

    • The metadata redundancy approach protects against two extents out of three being completely lost.
    • The metadata redundancy approach allows protecting metadata, not data.
    • The backup file placement policy set for the scale-out backup repository, as described in Backup File Placement, is ignored.

    Scale-Out Repository as NAS Backup Repository 

    You can configure performance extents in a scale-out backup repository to act as data extents or as metadata extents. To do that, use the Set-VBRRepositoryExtent cmdlet, as described in the Veeam PowerShell Reference. As a result, NAS backup data will be written to the data extent, metadata will be written to the metadata extent.

    Note

    Mind that even if the extent is intended for storing only backup data, replica of metadata for data stored on other extents will be copied to this extent.

    I want to report a typo

    There is a misspelling right here:

     

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