- Special Scenarios Based on Vendor Own Guidelines + Backup Job With Active Full or Synthetic Full Backup:
The above vendor best practices and design guides mention situations where a deduplication storage can be used as primary backup target. Depending on the guidelines, select the incremental backup mode with active or synthetic full backup.
When Exagrid is used as a primary backup target, it is recommended to enable GFS processing with it. Please see Best Practices for ExaGrid
Disable inline deduplication setting when writing into deduplication storages.
However for deduplication devices that have a non deduplicated landing zone (Like ExaGrid) and backup only VMs, you can save some space: to do this, enable inline deduplication
By default, the Veeam source DataMover (Veeam Proxy or Agent) compression level is set to “optimal” to reduce data that needs to be transported over the network. The repository or the gateway server uncompress the data before storing the data to the deduplication device.
For backup copy jobs, set the compression level to “Auto” to leave the data in the way it was stored originally on the primary backup target.
The general best practices are:
Veeam can use different block sizes to store backups on the target. The block size is defined in the backup job settings and will be kept across all copies.
Block size changes are only activated by an active full and will only be used for the new backup chains (the data stored already are not touched).
Only 2 of the block size settings are recommended for deduplication storage usage at VM backups:
- Storage optimization: Local target (large blocks)
Use this option for any general deduplication storage / HPE StoreOnce Catalyst / Dell EMC DataDomain DDboost / Quantum DXi.
- Storage optimization: Local target
Use this option for ExaGrid.
By default, this advanced repository setting is disabled. Enable it for deduplication storages that work with fixed block length deduplication (e.g. NetApp ONTAP deduplication) or in situations where you can use ReFS/XFS Fast Cloning.
Encryption will create random data at the backup targets; as a result, the deduplication storages will not work effectively. It is recommended not to use encryption with deduplication storages.
Health check reads all data from the last restore point and across the backup chain. When used with deduplication storages, this data is rehydrated from the storage which may cause slow process. It is recommended to enable health check on the primary backup job before data is transported by backup copy job to a deduplication storage.
Veeam Defragmentation And Compact Settings
If you followed the above described guidelines, you do not need these settings. It is recommended that you disable them.