NAS Backup Repositories need to be sized differently than standard repositories due to the fact that the backup file format is different, there are two levels of primary retention (short term and short term copy) and an archival retention.
Regarding the archival retention, only older file versions or deleted data are eligible to be moved to the Archive Repository as they age out and, as you can image, this constraint introduces a few challenges when sizing a NAS Backup Repository.
Also, compared to a standard Backup Repository a NAS Backup Repository consumes more RAM.
NAS Backup does not use VBK/VIB file format for storing data into the Backup Repository. A new file format has been developed specifically for this purpose and to properly treat the multitude of files to be protected. Its structure can be compared to an object storage, where data is divided into chunks and arranged into groups of files. The extension of those files is .vblob and their size is limited to 64 MB. The backup mode is always incremental forever.
The Short Term Backup Repository will always hold a copy of all source file, pulled from the network share.
NAS devices and file servers usually have a daily change rate between 1% and 3%. Please note that the percentage itself can vary a lot depending on the total capacity of the NAS: smaller units can have higher change rate with the change of only a minor subset of data, while larger devices may have a very small percentage with a huge amount of data is changed daily.
The achievable compression on NAS data depends on many factors. The data type is the most important, affecting how much compression is effective (eg: plain text or office data are very easy to compress, binary files are more difficult); some kinds of data (like PDFs) are compressed by default, as are most media files and, along with files protected by encryption, will give very bad to zero compression ratios. In average, total compression varies between 20% and 50% of the source size.
Given the information above, to size the Short Term repository you can refer to the following formula. Calculate first the initial backup (A) and then the increments size (B)
A = ((100 - data reduction) / 100) * source size B = ((change rate / 100) * source size) * retention
Then sum up the two values:
Data size = A + B
Metadata and free “workspace” need to be taken into account as well. Add 5% for each:
Grand total = Data size * 1.1
No additional sizing is required here as this is a complete mirror of the primary repository.
The Short Term Backup Repository should have half the proxy cores and 6GB of memory per-core.
For better performance for NAS backups, a fast (SSD) repository should be used for the metadata. That requires a Scale-Out-Repository (SOBR) where metadata is stored on the meta extent. An additional copy of the metadata is stored on data extent(s) for metadata redundancy.
To configure the placement of the NAS backup metadata and data you have to use PowerShell:
Set-VBRRepositoryExtent –Extent "NAME_Of_SSD_EXTENT" –Metadata
Set-VBRRepositoryExtent –Extent "NAME_Of_DEDUPLICATION_EXTENT" –Data
If you have multiple extents in your Scale-Out Backup Repository, make sure they are all configured correctly. To check the settings for all the Scale-Out Backup Repository Extents you can do this with PowerShell as well:
Get-VBRRepositoryExtent -Repository “NAME_OF_SOBR”
- NAS Backup
- NAS Backup Repositories support
- Scale-Out Repository with Extents in Metadata and Data Roles