Virtual TapeServer 8.2 Configuration Guide
Table Of Contents
- Virtual TapeServer for NonStop Servers Configuration Guide
- Preface
- Introduction
- Overview of Tasks
- Reconfiguring Vaults
- Enabling Licensed Features
- Configuring Ports
- Creating and Managing VTLs and VTDs
- Enabling and Performing Tape-to-tape Exports
- Enabling and Performing Stacked Exports
- Enabling and Configuring Data Replication
- Enabling and Configuring Role Swapping
- Configuring EMS Communication
- Enabling and Configuring Data Encryption
- Creating and Managing Virtual Media
- Enabling and Configuring Scan/Cleanup
- Configuring User Accounts
- Configuring Web Interface Preferences
- Managing the VTS Server
- Troubleshooting
- Maintaining GFS for VTS
- Reinstalling and Restoring VTS
- Attaching External Devices after Initial Deployment
- TCP/IP Ports and Protocols
- Index
Creating and Managing Virtual Media | 77
Automatically migrating virtual tapes to physical tapes using
VTSPolicy
After BMA integration is configured, which enables a backup management application server
to read and write files to and from VTS, you can use VTSPolicy to initiate migration by having
the NonStop server send an EMS message to the VTS server. The VTS server then uses the
VTSPolicy command to invoke the backup management application to complete the desired
operation. VTS waits for the return code from the backup management application. If a
successful return code is received, VTS marks the virtual tape as migrated to physical tape. If
the return code indicates a failure, VTS does not mark the virtual tape as migrated and notes
this in the log file.
If the NonStop server requests a virtual tape that was migrated, VTS checks the size of the
requested virtual tape. If using IBM Tivoli Storage Manager and the size is 0, the virtual tape
was erased and VTS attempts to retrieve the data and recreate the virtual tape from physical
tape. To accomplish this, VTS references the metadata within the virtual tape and generates
a request to the backup management application to restore the data. After the data is
restored, the virtual tape is mounted. The NonStop server can then recognize the virtual tape
online and begin to restore it.
You can automate migration by issuing the VTSPolicy command using the FUP utility or by
adding the command to a TACL script.
Note If BMA integration is not enabled and configured, contact HP Global NonStop
Solution Center (GNSC) for support.
To configure the VTSPolicy command for IBM Tivoli Storage Manager
Here is the syntax of the VTSPolicy command for use with IBM Tivoli Storage Manager. Note
that all parameters specified for the command are case-sensitive.
VTSPolicy TSM 'backup_type /VAULTxx/pool/cartridge [keyword=value ...]'
where
backup_type
Specifies the type of backup. You can specify one of the following values: archive or
selective. The most commonly used type is archive, though you may want to contact
your Tivoli administrator for more information.
/VAULTxx/pool/cartridge
Specifies the pool and cartridge on which to operate. If you want to migrate an entire
pool, specify /VAULTxx/pool only.
keyword=value
Specifies a valid combination of keywords and their values. Supported keywords
include the following:
source or s
Specifies the fully-qualified hostname of the VTS system on which the
specified pool resides. In a VTS cluster, this keyword specifies the VTS server
that will execute the command. This keyword is required in a VTS cluster.
optfile or o
Specifies a UNIX absolute path to the TSM optfile file, which is required for
archive operations. This keyword is required.
empty Enables VTS to migrate empty cartridges. Set this keyword to YES or NO.
This keyword is not required and defaults to NO.