HP Data Protector software interaction with deduplication enabled replication

4
HP Data Protector interaction with replication
The replication in both the VLS and D2D systems is mirroring the source cartridge to its matching
target cartridge so both cartridges have the same barcode, the same tape contents, and so on.
This represents a perfect mechanism to increase backup data resilience in terms of availability
and backup data protection. By using two different Data Protector Cell Manager hosts, backup
data resides at different locations and is available for further data handling. However as the
replicated cartridge represents an identical clone of the source cartridge it is a prerequisite to
import the replica into a different Data Protector cell. The source and the target libraries must
belong to their respective Data Protector cell.
Figure 1 Cell Manager assignment
Figure 1 shows the simplified architecture for such cartridge handling.
Note: With HP Data Protector, if you have a Cell Manager at each site that can share library
devices across sites through a MoM/CMMDB, you still need to ensure that each Cell Manager
only sees its local virtual library (that is, the source cell server must not be configured to see the
target virtual library and vice-versa)
In order to be able to use replicated cartridges on Cell Manager B, it needs to be “taught” about
what is on the replicated cartridges. Up to this point, Cell Manager B does not know about the:
• cartridge slot ID
• cartridge barcode
• catalog (content of a cartridge)
of the replicated cartridge.
A list of successfully replicated cartridges will be created on each target D2D or VLS device which
will then be imported into the Cell Manager B using scripts that run regularly on the Cell Manager
B system.