Source devices in Object Copy/Replication

When using Object Copy or Replication in Data Protector it is important to ensure the right Media Agent is reading the source data. This ensures the data stream is either kept locally on a specific Media Agent or is using the right path through the network.

You could either use a static re-mapping of Source devices within each Copy Spec or use Device Policies globally.

Static re-mapping of Source devices

This could be a very time consuming task in a configuration with dozens of devices and multiple Copy specs. This is commonly seen in larger StoreOnce Catalyst, Data Domain Boost or File Library implementations.

You need to select every possible Source device that should not be used during the operation and Change it to a different Source device. In this example only the device JETDCM01_B2D_jetdcm01 should replace all other devices.

Please note: B2D Source side devices should never be used during Object Copy/Replication. They must be replaced accordingly. Replacing a Source device with a device from a different library will cause Mount Requests.

Use Device Policies to control Source devices

The benefit of using Device Policies is that this is a one-time operation. All devices within a specific device (B2D, File Library, Tape Library) use the same Device Tag. Then assign the Copy Policy to control which Media Agent should be used during Object Copy/Replication. This is possible as a group operation on multiple Devices. Even B2D Source side devices are supported for this operation.

Please note: B2D Source side device should never be used during Object Copy/Replication. They must be replaced accordingly. The configuration options of Device Policies on Source side devices has been removed in Data Protector A.10.01 (QCCR2A75017). This should be fixed in QCCR2A75018 soon.

If the Device Policies are configured no further manual modification in the Copy spec is required.

Related global options

A few recommended global options relevant for Object Copy using either Device Policies and/or Static re-mapping.