The information below is direct from Veeam Backup & Replication Version 12 User Guide for VMware vSphere
You can disable the TLS connection with a registry value for the deduplicating storage appliances that do not support the TLS connection. For more information, see Veeam article kb4429 Quantum DXi Storage With Firmware 3.x Does Not Work with Veeam Backup & Replication 12
This is because Veeam Backup & Replication reads blocks of 4 MB, encrypts them, adds 16 KB metadata to each data block and then aligns data blocks.
This results in that each 4 MB data block on the source becomes a 5 MB block on the target.
Data processing (the Storage optimization setting). It is recommended that you use optimized job settings. Large data blocks produce a smaller metadata table that requires less memory and CPU resources to process.
For more information about storage optimization, see Data Compression and Deduplication
To overcome this limitation, schedule full backups (active or synthetic) to split the backup chain into shorter series. For example, to perform backups at 15-minute intervals 24 hours a day, you must schedule synthetic fulls every day. In this scenario, intervals immediately after midnight may be skipped due to duration of synthetic processing. For more information, see How Synthetic Full Backup Works
As a gateway server, you must use a Microsoft Windows server that is added to the backup infrastructure and has access to the Dell Data Domain backup repository over Fibre Channel.
If the hard stream limit is exceeded when Veeam Backup & Replication runs tasks against the backup repository, Veeam Backup & Replication fail to create new I/O streams.
If the hard stream limit is exceeded when Veeam Backup & Replication runs tasks against the backup repository, Veeam Backup & Replication will fail to create new I/O streams.
Below is general Veeam Backup & Replication configuration advice to be used when backing up to deduplicated storage.
From Veeam article kb1745, all Vendor-documented and Vendor-specific advice supersedes the advice below.
Advanced Settings
Below are the general recommendations for the Advanced Settings (Storage > Advanced):
Backup Tab
In general, deduplication devices have the lowest performance during read operations. As such, to maximize performance, the backup jobs should be write-only. Configure the backup job to use (Forward) Incremental with weekly Active full backups to achieve this.
Backup Mode
(Forward) Incremental
Enabled and set to weekly.
Weekly Full restore points ensure that during a restore, as few restore points must be read from as possible.
Maintenance Tab
Perform backup files health check
Disabled
While enabling this feature with deduplication storage is possible, it requires many read operations, which will take a long time to complete. With larger backup files on deduplicated storage, this feature could cause a backup job to spend days performing the health check, causing the job to not create new restore points.
Defragment and compact full backup file
Disabled
There is no need for this option when Active Fulls are being created.
Storage Tab
Disabled
Disabling deduplication in Veeam Backup & Replication cause the restore points to appear larger, but because Veeam does not deduplicate them, it allows the storage's deduplication function to be more effective.
Optimal or Dedupe-friendly
The Repository settings section of this article advises enabling a function that will cause all restore points to be decompressed before being written. As such, the compression set at the job level will only impact data compression while backup data is being transferred across the network. To reduce network congestion, either Optimal or Dedupe-friendly compression may be used. The latter will slightly reduce the effort needed to decompress before writing. Compression at the job level should rarely be completely disabled as it will significantly increase the amount of data that must be transferred over the network to the machine writing the data to the backup repository.
Storage optimization (Block Size)
4 MB
This block size, formerly called "Local target (large blocks)," will help improve performance when storing backup files on deduplication storage as it reduces the size of the backup file's internal metadata table.
Disabled
Data encryption has a negative effect on the deduplication ratio if you use a deduplicating storage appliance as a target. Veeam Backup & Replication uses different encryption keys for every job session. For this reason, encrypted data blocks sent to the deduplicating storage appliances appear different, even though they may contain duplicate data. If you want to achieve a higher deduplication ratio, you can disable data encryption. If you still want to use encryption, you can enable the encryption feature on the deduplicating storage appliance itself.
Figure 1: Enable the encryption feature on the deduplicating storage appliance
Figure 2: Set Maintenance Settings for Storage-level and Full backup
Figure 3: Set Data reduction, Compression level, and Storage optimization
When targeting deduplicated storage, the backup copy job should be configured as follows to force the backup copy job to perform primarily write-only operations:
Keep certain full backups longer for archival purposes
Enabled and set to have at least 1 weekly
Enabling this option forces the backup copy job to enforce retention using the forward-incremental retention policy, which prevents the job from using the non-GFS retention method that involves merging the oldest increment into the full (a retention method known as Forever Forward Incremental ). Forever Forward Incremental retention method is suboptimal for deduplication storage as it involves many small read and write operations to enforce retention.
Read the entire restore point from source backup instead of synthesizing it from increments
Enabled*
Enabling this option for local-to-local backup copy jobs being written to deduplication storage that does not support block cloning forces the job to perform strictly write-only operations to create the GFS full. Thereby avoiding unnecessarily taxing synthetic GFS full creation processing that involves creating the GFS full restore point by reading from previous restore points stored on the deduplication storage.
*This option should be disabled if:
The backup copy job is transferring backups across a low-speed connection. Specifically, a link so slow that transferring the entire full to the destination would be slower than the job creating a full synthetically using data already present on the deduplication storage.
Some offsite connections may be fast enough to perform the full transfer faster than the synthetic creation process. It will come down to comparing the network throughput vs. the read+write speed of the dedupe storage. For example, if the connection used to reach the backup copy destination is 100 Mbps (12.5 MB/s), and the deduplication storage can create a synthetic full at 40 MB/s, the option should be disabled. However, if the connection is 500 Mbps (62.5 MB/s), that is faster than the deduplication storage in this example, so reading the entire restore point across the network would be quicker.
The target deduplication appliance backup repository uses block cloning functionality.
Block cloning is available with integrated deduplication appliances (HPE StoreOnce Catalyst, Exagrid, Data Domain DDboost, and Quantum DXi)
Figure 4: Specifiy the target backup repository, recent restore points, and retention policy
Figure 5: Remove option to read the entire restore point from source backup
Advanced Settings
Below are the general recommendations for the Advanced Settings (Target > Advanced):
Maintenance Tab
Perform backup files health check
Disabled
While enabling this feature with dedupe storage is possible, it requires many read operations, which will take a very long time to complete. With larger backup files on deduplicated storage, this feature could cause a backup job to spend days performing the health check, causing the job to not create new restore points.
Defragment and compact full backup file
Disabled
There is no need for this option when Active Fulls are being created.
Storage Tab
Disabled
Disabling deduplication in Veeam Backup & Replication will cause the restore points to appear larger, but because Veeam does not deduplicate them, it will allow the storage's deduplication function to be more effective.
Auto
The Repository settings section of this article advises enabling a function that will cause all restore points to be decompressed before being written. As such, the compression set at the job level will only impact data compression while backup data is being transferred across the network.
Disabled
Data encryption has a negative effect on the deduplication ratio if you use a deduplicating storage appliance as a target. Veeam Backup & Replication uses different encryption keys for every job session. For this reason, encrypted data blocks sent to the deduplicating storage appliances appear as different though they may contain duplicate data. If you want to achieve a higher deduplication ratio, you can disable data encryption. If you still want to use encryption, you can enable the encryption feature on the deduplicating storage appliance itself.
Figure 6: Set Maintenance Settings for Target Storage-level and Full backup
Figure 7: Set Target Data reduction, Compression level, and Storage optimization
From Veeam article kb1745, all Vendor-documented and Vendor-specific advice supersedes the advice below.
When creating a new Backup Repository using one of the built-in Deduplication Storage Appliance options, the settings for the repository will be automatically configured to that vendor's optimized defaults and should not be changed.
The settings below are general advice for dedupe storage.
Below are the general recommendations for the Storage Compatibility Settings (Repository > Advanced):
Align backup file data blocks
Enabled for dedupe storage that uses fixed block length deduplication or dedupe storage capable of block cloning.
Disabled for dedupe storage that uses variable length deduplication.
Decompress backup file data blocks before storing
Enabled for all dedupe storage that does not have a non-dedupe landing zone.
Writing backup files to the dedupe storage that are uncompressed and undeduplicated by Veeam will allow the deduplication mechanisms within the storage to operate efficiently.
This repository is backed by rotated drives
Disabled
Use per-machine backup files
Enabled
Data Domain Boost Veeam All Simple Support Matrix
Data Domain Backup Software Veeam All Simple Support Matrix
Dell Data Domain Supported Features
The DD Boost technology offers a set of features for advanced data processing. Veeam Backup & Replication supports the following features:
Figure 8: Workflow of how Accelerated Restore works
Backup Proxy for Accelerated Restore
Veeam Backup & Replication restores all disks of a VM through one backup proxy. If you instruct Veeam Backup & Replication to select a backup proxy for the restore task automatically, it picks the least loaded backup proxy in the backup infrastructure. If you assign a backup proxy explicitly, Veeam Backup & Replication uses the selected backup proxy. For every VM disk, Veeam Backup & Replication starts a separate Veeam Data Mover on the backup proxy. For example, if you restore a VM with 10 disks, Veeam Backup & Replication starts 10 Veeam Data Movers on the backup proxy. The backup proxy assigned for the entire VM restore task must have enough RAM resources to be able to restore VM disks in parallel. For every VM disk, 200 MB of RAM is required. The total amount of required RAM resources is calculated by the following formula: Total amount of RAM = Number of VM disks * 200 MB Before starting the restore process, Veeam Backup & Replication checks the amount of RAM resources on the backup proxy. If the backup proxy does not have enough RAM resources, Veeam Backup & Replication displays a warning in the job session details and automatically fails over to a regular VM disks processing mode (data of VM disks is read at random and VM disks are restored sequentially).
Limitations for Accelerated Restore
The accelerated restore of entire VM has the following limitations:
Storage Appliances and Tapes
Storage appliances that are used to store backup data in filer (CIFS/NFS) or block device mode (iSCSI/FC/SAS) are not supported if the backup data is offloaded to tapes and is no longer stored directly on the filer/block device (Hierarchical Storage Management with Tape tier). To offload data to tapes, make sure that: • All of the backup data is stored on the appliance altogether (that is, all of the backup chains are stored on the appliance as a whole and not scattered across multiple devices) and only copies are stored on tapes. • These appliances emulate a tape system (VTL) as an access protocol for.
Dell Data Domain
Step 1. Launch New Backup Repository Wizard
To launch the New Backup Repository wizard, do the following:
Figure 9: Launch new backup repository Wizard
Step 2. Specify Backup Repository Name and Description
At the Name step of the wizard, specify a name and description for the backup repository:
Figure 10: Specify backup repository name and description
Step 3. Specify Server Settings
Options that you can specify at the Server step of the wizard depend on the type of backup repository you are adding.
Dell Data Domain
To configure settings for Dell Data Domain:
Figure 11: Using Fibre channel
Preconfigured Advanced Settings
Depending on the type of deduplicating storage appliance you use, Veeam Backup & Replication automatically sets advanced settings to the following ones:
Dell Data Domain
Limitations for Performance Tier
Consider the following limitations for performance tier:
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 120 points in this scale-out backup repository.
Ports
On backup infrastructure components, Veeam Backup & Replication automatically creates firewall rules for the required ports. These rules allow communication between the components.
Figure 12: Automated firewall rules for TCP111
Figure 13: Automated firewall rules for TCPport2049 and 2052
Additional knowledge based articles for Veeam:
Data Domain articles for using ifgroups for ddboost: