Hewlett-Packard StorageWorks 12000 - Virtual Library System EVA Gateway Manual
Download Manual of HP 6000 - Officejet Wireless Color Inkjet Printer Power Supply, Storage for Free or View it Online on All-Guides.com.
Brand: HP
Category: Power Supply , Storage
Type: Manual
Model: HP 6000 - Officejet Wireless Color Inkjet Printer , HP StorageWorks 12000 - Virtual Library System EVA Gateway , HP StorageWorks 9000 Virtual Libr
Pages: 218 (10.09 Mb)
Download HP 6000 - Officejet Wireless Color Inkjet Printer Manual
ferent pools with different retention times for fulls vs. incrementals), but this means that the incre-
mental backups will not be fully deduplicated because their backup jobs names will not match the
full backup job names. To address this, the VLS firmware version 3.3.0 includes a new GUI option
called “Edit Data Protector Configuration” (in the System Maintenance screen). This option allows
you to enter suffixes that will be stripped off the end of the Data Protector backup jobs names
when they are deduplicated. For example, if you have a full backup called BACKUP1_F and an
incremental backup of the same data called BACKUP1_I, you can enter _F and _I in the Edit
Data Protector Configuration and the incremental backups will deduplicate against the full backups.
Data Protector Import Example Script
The following section details an example script to perform the tape import commands for HP Data
Protector. The input to the script is the ISV Import email report (containing a list of cartridges by
/barcode/library/slot that were successfully replicated and thus are ready for import).
This example uses a Linux server client which contains the email processing script (above) and has
CLI access to the Data Protector CLI. The virtual library on the VLS target device has been presented
to Data Protector over Fibre Channel and configured in Data Protector as a tape library with tape
drives (each tape drive will have its own Data Protector drive name). A recommended configuration
would be to reserve a subset of the drives in the library just for use by tape import (i.e., do not use
these drives for any other jobs) and the remaining drives can be used for restore jobs or copy to
physical tape etc. This is because the import script needs to define the Data Protector drive names
that it can use for import jobs and it would make the script more complex to handle drives that might
be in use for other jobs when you want to run an import. One way of defining the Data Protector
drive names would be to create a lookup file that defines the library serial number and the Data
Protector drive name (or names) that can be used for import. For example, a “libmap_file” containing:
DEC06150U7~DP_cell2_lib03_drv1~DP_cell2_lib03_drv2
The actual script would process the cartridge list from stdin (identified by the “ISV” tag at the beginning
of the line) and use the Data Protector CLI to trigger a tape import on the specified drive(s). For
example:
#!/bin/bash
#read from stdin
CARTLIST=`grep ISV~ /dev/stdin`
DRVBSY=( 0 0 0 0 )
for CART in $CARTLIST
do
BARCODE=`echo $CART | awk -F"~" '{print $2}'`
LIBSERIAL=`echo $CART | awk -F"~" '{print $3}'`
BCSLOT=`echo $CART | awk -F"~" '{print $4}'`
DRVNAME[0]=`grep $LIBSERIAL $LIBMAP | awk -F"~" '{print $2}'`
DRVNAME[1]=`grep $LIBSERIAL $LIBMAP | awk -F"~" '{print $3}'`
DRVNAME[2]=`grep $LIBSERIAL $LIBMAP | awk -F"~" '{print $4}'`
DRVNAME[3]=`grep $LIBSERIAL $LIBMAP | awk -F"~" '{print $5}'`
if [ -z ${DRVNAME[0]} ]
then
DRVBSY[0]=1
fi
if [ -z ${DRVNAME[1]} ]
then
DRVBSY[1]=1
fi
if [ -z ${DRVNAME[2]} ]
then
DRVBSY[2]=1
fi
if [ -z ${DRVNAME[3]} ]
then
DRVBSY[3]=1
fi
#find a drive to use
Virtual Library Systems196