About Duplicating Images To A Remote Netbackup Master Server - Symantec NetBackup Manual

About duplicating images to a remote NetBackup master server

Reduced workload on the NetBackup media servers. More backups can be
performed.
Faster duplication. Duplication can occur in the background, simultaneously
with ongoing backup jobs.
Reduced bandwidth. If the appliance supports deduplication, the copy process
may send only changed blocks.
The requirements and limitations of optimized duplication with the same domain
are as follows:
Optimized duplication
requirements
Optimized duplication
limitations
See Configuring OpenStorage optimized duplication within the same domain"
on page 98.
Duplication to a remote master server is a new feature in NetBackup 7.1. With
this feature, you can duplicate backup images to a different master server domain.
About OpenStorage optimized duplication methods
The vendor must expose the off-host data movement
capability in their plug-in.
Both the source and the destination disk pools must be
the same OpenStorage vendor type.
One or more NetBackup media servers must connect to
the source appliance and the destination appliance.
If the optimized duplication fails, the job is not retried.
To configure NetBackup to do normal duplication if the
optimized job fails, add the following entry to the
bp.conf file on the NetBackup master server:
RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE
The copy operation uses the maximum fragment size of
the source storage unit, not the setting for the
destination storage unit. The optimized duplication
copies the image fragments as is. For greater efficiency,
the duplication does not resize and reshuffle the images
into a different set of fragments on the destination
storage unit.
To confirm the image copy, a media server must have
connectivity to the destination appliance.
A storage unit group cannot be a destination for
optimized duplication. The destination must be a storage
unit that represents an OpenStorage appliance of the
same type as the source appliance.
Planning your deployment 65