HP Data Protector software interaction with deduplication enabled replication

Note: Perl download and installation instructions can be found in the Addendum of this

document.

Tape import scripts

Theory of operation

The media on the target site can be imported to a different Data Protector Cell Manager after the

replication has finished and can be used there for restore and/or object copy tasks. Both D2D

backup devices and VLS devices have a notification mechanism that allows applications to find if

a media has been replicated successfully to the target device.

The HP VLS device provides an automatic notification mechanism that creates a report containing

all the replicated media that were created successfully since the execution of the last report. This

report can be scheduled and sent via e-mail attachment to any e-mail address.

The HP D2D device provides a web page containing the information about all replicated media in

an XML format that can be polled frequently. The XML page is available via an SSL-encrypted

connection by querying the following URL:

https://<D2D_hostname>/ReplicationStatus.xml

For example, for a D2D running on the host ‘myd2d.company.com’ the URL would be:

https://myd2d.company.com/ReplicationStatus.xml

The information received from a D2D device will be checked by the import script (D2D import

handler) against a previously recorded import history and if there is a change recognized in the

newly received status report the changes will be written into a queue file.

For a D2D NAS report, refer to:

https://myd2d.company.com/ReplicationNASStatus.xml

The VLS provides replication status information on a regular basis by e-mail. The e-mail contains

information about successfully replicated cartridges. The VLS import handler will parse the

provided information and will invoke the queue manager which updates the queue file with the

new information.

The queue file contains :

• library name

• barcode

• slot number

for each replicated cartridge.

The D2D/VLS import handler will automatically invoke the queue manager script to update the

queue file after a change has been recognized.

Finally an import task is scheduled, which invokes a Data Protector media import command that

uses the information from the queue file to import the successfully replicated cartridges.

Figure 2 shows a schematic overview of the script architecture.

All scripts use a single configuration file in which the following configuration details are specified:

• E-Mail notification details (VLS device)

• XML file location (URL to D2D devices)

• Cache file (XML History) location

• Queue file name and location

• Proxy Settings

• Log file name and location

• Log level and log file truncation period

• Library name/time window for import tasks/import tape drive