Using optimized duplication to copy deduplicated data between OpenStorage devices or deduplication disk storage devices

Last published : Apr 02, 2026
Backup Exec supports optimized duplication, which enables deduplicated data to be copied directly from one OpenStorage device to another OpenStorage device from the same vendor. Both devices must be attached to a single Backup Exec server. For example, you can copy data from one Veritas PureDisk device to another Veritas PureDisk device. Because the data is deduplicated, only unique data is copied between the devices.
To copy data between OpenStorage devices or deduplication disk storage devices, you must create a job to duplicate backup sets. The destination device for the duplicate job must be the same type of device from the same vendor as the device that was used in the source backup job. No additional settings are required; optimized duplication occurs automatically when you set up a duplicate backup job between appropriate devices. You can restore data from either device.
Optimized duplication can be performed on backup sets that were enabled for Granular Recovery Technology (GRT). However, only deduplication disk storage devices and PureDisk devices support optimized duplication for GRT-enabled backup sets.
You can find a list of compatible types of storage devices in Backup Exec's Hardware Compatibility List:
http://www.veritas.com/docs/000017788
Note: The OpenStorage devices must be from the same vendor. You cannot perform optimized duplication between OpenStorage devices from different vendors. If you attempt to copy deduplicated data between OpenStorage devices from different vendors, regular duplication is performed instead of optimized duplication.
Using optimized duplication with the Central Admin Server feature
If you use the Central Admin Server feature (CAS), the functionality of optimized duplication is expanded to let you do the following:
  • Copy data from a deduplication disk storage device on one Backup Exec server to a deduplication disk storage device on another Backup Exec server.
  • Copy data from an OpenStorage device that is attached to a Backup Exec server to another OpenStorage device that is attached to a different Backup Exec server.
To use optimized duplication with CAS, the following requirements must be met:
  • You must have a license for the Enterprise Server feature. CAS is installed as part of the Enterprise Server feature.
  • All Backup Exec servers that you use with CAS as either a central administration server or as managed Backup Exec servers must use the 64-bit version of Windows.
  • You must have a central administration server and at least one managed Backup Exec server in your CAS environment.
  • For client-side deduplication and Backup Exec server-side deduplication, you must configure one deduplication disk storage on the Backup Exec server from which you want to copy the deduplicated data. You must also configure one deduplication disk storage on the Backup Exec server to which you want to copy the deduplicated data.
  • For appliance deduplication, the Backup Exec server from which you want to copy deduplicated data must have the appropriate plug-in for the OpenStorage device and a properly configured OpenStorage device. In addition, the Backup Exec server to which you want to copy the deduplication data must have the appropriate plug-in for the OpenStorage device and a properly configured OpenStorage device.
  • You must share deduplication devices between the Backup Exec servers.
  • You must inventory and catalog the media on the destination server before you recover any files from the duplicated backup set. You must do this regardless of how the catalog sharing option is configured for CAS.
Using optimized duplication to transfer backup data to a remote location
You can use optimized duplication to transfer backup data to a remote location over a WAN connection. You should prepopulate the destination deduplication disk storage device with a full backup of the servers. This prepopulation task is also known as seeding the destination deduplication disk storage device. Seeding helps avoid the time-consuming and bandwidth-intensive process of transmitting large amounts of backup data over the low bandwidth WAN connection.
To seed a device, you can store a full backup to an external storage device such as a USB drive. You can then transport the USB drive to the remote location where the Backup Exec server and the destination deduplication disk storage device are kept, and duplicate the backup data to the deduplication disk storage device.
How to set up optimized duplication
Set up a duplicate backup job to perform optimized duplication.

Table: How to set up optimized duplication

Step For more information
If you are using CAS, do the following\: See Configuring an OpenStorage device .
- Verify that you have one central administration server and at least one managed Backup Exec server. See Creating or importing deduplication disk storage .
- Verify that the Backup Exec server from which you want to copy the deduplicated data has a deduplication disk storage device (for client-side or Backup Exec server-side deduplication) or an OpenStorage device (for appliance deduplication). Also verify that the Backup Exec server to which you want to copy the deduplicated data has a deduplication disk storage device (for client or Backup Exec server-side deduplication) or an OpenStorage device (for appliance deduplication).
- Verify that the Backup Exec servers are enabled for sharing.
Note: This information applies only to CAS. If you do not have CAS, skip this step.
Create a backup job that uses an OpenStorage device or a deduplication disk storage device as the destination. See Backing up data .
Create a job to duplicate backup sets and select the appropriate OpenStorage device or deduplication disk storage as the destination. See Duplicating backup sets or a job history manually .
Note: The destination device for the duplicate job must be the same type of device from the same vendor as the device that was used in the source backup job.
See Sharing a deduplication device between multiple Backup Exec servers.