Vls Non-Deduplicated Replication - HP StorageWorks 12000 - Virtual Library System EVA Gateway Manual

Email Processing Example Script
The following section details an example script to process the "ISV Import" email report from the VLS
and convert it into a list of cartridges to be imported. The following steps show how this might be
done in the target site (this example uses a Linux server client):
• You will need an SMTP gateway server in the network (needed for the VLS SMTP emails).
• Allocate a client server to use for the import script (could be a separate server or the actual mas-
ter/cell server itself).
• Ensure the selected client is running an email messaging system (e.g,. sendmail).
• Create a user account on the client.
• Ensure the selected client has CLI access to the backup application.
• In the user account, create a filter that sequentially processes the incoming emails, and for the ISV
import emails it should send the message body (containing the list of replicated cartridges) to the
script that actually performs the tape import. One way of doing this is to create a .forward that
sends your incoming emails to procmail. For example:|/usr/bin/procmailand then add the
following lines to the .procmailrc that copy an ISV import email (containing the list of tapes to
import) to another script that runs the ISV-specific import commands:
:0 bc: # send VLS DP import files for processing* ^Subject:.*ISV| /home/importuser1/isv_im-
port/dpimport.sh
See Data Protector Import Example Script
scripts.
• On the target VLS device GUI, setup the SMTP Gateway address and then configure the "ISV Import"
email report using the selected email account.

VLS Non-deduplicated Replication

If you have not enabled Accelerated deduplication on your VLS device , non-deduplicated replication
can still provide a more reliable method of sending mission-critical data off-site compared to off-site
using physical tape (because there is no need to load/unload physical media and ship it to the off-site
location).
VLS-to-VLS non-deduplicated replication options:
• Using SAN-based Automigration
Automigration also supports using a VLS as a destination library, as a device-to-device replication
scheme over an extended SAN. To use a VLS as a destination library, designate one VLS as the
source and a second VLS as the destination. The destination VLS is presented over an extended
SAN so that it is visible to the source VLS. With Command View VLS, establishe an automigration
policy and echo copy pools in the same way you set up automigration with a physical destination
library. See
during your regular backup window. During the automigration window you defined, source virtual
cartridges automatically migrate to matching virtual cartridges on the destination VLS.
The VLS with the source library must support automigration; however, it is not necessary for the
destination VLS to do so. If you have an earlier generation VLS system and you purchase a
VLS6200, VLS6600, or VLS12000 Gateway, you can use the newer models to handle
automigration as the source device. Earlier generation VLS devices can be used as destinations.
192 Virtual Library Systems
Echo Copy Pools and Automigration
and NetBackup Import Example Script
Policy. The source VLS performs normal backups
for sample import