HP Data Protector software interaction with deduplication enabled replication

23
CLI summary of replication import scripts
The scripting solution has its own command line interface (CLI) completely separate from the
Data Protector CLI. The Data Protector CLI itself is not modified. The CLI Perl scripts can be called
without a parameter to get version and usage information.
Module CLI parameter
d2dHandler.pl
perl “d2dHandler.pl” --cfg “<CONFIGFILE>”
vlsHandler.pl
perl “vlsHandler.pl” --cfg “<CONFIGFILE>”
The files are retrieved from the configured e-mail server using POP3.
perl “vlsHandler.pl” –cfg “<CONFIGFILE>” [--
notificationfile “<NOTIFICATION_FILE>”]
• <NOTIFICATION_FILE>: Optional. When specified, this file (VLS
notification CSV file) is used to extract replicated slots. The file will
be deleted afterwards.
queueManager.pl
perl “queueManager.pl” --cfg “<CONFIGFILE>” { --add
“<task>” | --remove “<task>” | --list [“<library serial
number>”] }
– <task>: <lib>/<barcode>/<slot>
– <lib>: library name, used to import the tape
–
<barcode>: barcode of the tape to import
–
<slot>: slot number
executeImportTasks.pl
perl “executeImportTasks.pl” --cfg “<CONFIGFILE>”
verifyConfiguration.pl
perl “verifyConfiguration.pl” --cfg “<CONFIGFILE>”
D2D NAS Share Limitations
The following limitations apply to D2D NAS shares only.
• Only one File Library per share: There can only be one File Library using a D2D
NAS Share. Two libraries on the same share cannot be configured.
If the same share is used by two libraries, it is not possible to know from the replication
report to which library each slot belongs. Therefore, it is not possible to know to which
library each slot should be imported.
• Target File Library can have only one storage directory configured: To
import a media into the file library we need to know the storage directory in which the
media resides. In other words this is the D2D NAS target share as it is presented to the
target file library. If target library has many storage directories configured it is impossible
to know which one of them is the NAS share. Therefore it is impossible to run import.
• DFMF is not supported for File Library replication: Use of distributed file media
format (DFMF) is not supported for File Libraries.
• Replication must be suspended when import is running: This is because files
can temporarily disappear during replication. This would prevent successful import.