Design Considerations; Advanced Replication Job Control - HP 12000 Design Manual

The following screen shows an example of the job history on a target device but you can also view
the same information on the source device, and in the case of an active-active deployment you
can view both the outgoing and incoming jobs on a device that is both a source and a target:
On both the source and target devices there is also an option to view the "Job Summary" which
provides a summary of either all outgoing jobs (source) or all incoming (target) jobs. The summary
includes how many replication jobs were successful, how many jobs were rescheduled (for example,
due to cartridges being appended while they were actively replicating), and how many jobs failed.
For the incoming target jobs, the summary is shown for each source device. The job summary
provides a quick and easy overview of the replication activity on a VLS.

Design Considerations

Because every enterprise backup environment is different, there is no single answer for optimizing
replication. This section discusses replication design considerations to help you optimize replication
in your environment.

Advanced Replication Job Control

The replication windows in the echo copy pool policies and replication targets allow you to restrict
replication traffic to specific hours of the days or days or the week, but for the more complex
configurations there are additional ways to control the replication process at both the source and
destination devices.
If you have different classifications of backups at the source device, you may want to create multiple
echo copy pools with different policy priority settings so that high priority backups are replicated
before lower priority backups. You can still keep one replication target and configure the multiple
echo copy pools to have different slots ranges (and thus different sets of cartridges) within that
replication target. On the source device you could either have one source virtual library mapped
to the multiple echo copy pools or you could have a separate virtual library for each echo copy
pool. In either case you would divide your backup jobs so that the high priority jobs went to the
cartridge set or virtual library mapped to the echo copy pool with high priority set in the policies,
and the lower priority jobs would go to the other cartridges or other virtual library, etc.
Design Considerations 1 13