Virtual TapeServer 8.3 Supplemental Installation Guideh20628. · iii Contents Preface v Supportedreleaseversionupdates v Typographicalconventions v Relateddocumentation v 1InstallingGFS

Virtual TapeServer for NonStop ServersSupplemental Installation Guide

HP Part Number: 702038-001Published: August 2012Edition: All J06 release version updates (RVUs), all H06 RVUs, and all G06 RVUs

- i -

© Copyright 2012 Hewlett-Packard Development Company, L.P.

Legal Notice

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data forCommercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

The information contained herein is subject to change without notice. The only warranties for HP products andservices are set forth in the express warranty statements accompanying such products and services. Nothing hereinshould be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors oromissions contained herein.

Export of the information contained in this publication may require authorization from the U.S. Department ofCommerce.

Microsoft, Windows, Internet Explorer, and all Windows-based trademarks are either trademarks or registeredtrademarks of Microsoft Corporation.

Mozilla and Firefox are registered trademarks of the Mozilla Corporation.

Linux is a registered trademark of Linus Torvalds.

Copyright (C) 2008 CentOSLicensed under the Creative Commons Attribution-Share Alike 3.0 Licensehttp://creativecommons.org/licenses/by-sa/3.0/legalcode

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc.

Other product and company names may be the trademarks of their respective owners.

http://creativecommons.org/licenses/by-sa/3.0/legalcode

http://creativecommons.org/licenses/by-sa/3.0/legalcode

iii

Contents

Preface v

Supported release version updates v

Typographical conventions v

Related documentation v

1 Installing GFS 1

Installing or reinstalling GFS 2

Troubleshooting 13

2 Enabling BMA Integration and Migration 15

3 Enabling and Configuring AutoCopy and Instant DR 25

Overview of Instant DR 26

Overview of AutoCopy 26

Using Instant DR or AutoCopy 27

Configuring network settings 28

Configuring AutoCopy 32

Configuring Instant DR 35

Manually replicating a virtual tape using Instant DR 35

Automatically replicating a virtual tape using Instant DR 39

4 SCSI-to-Fibre Channel Adapter Upgrade 41

5 Hardware Information for Legacy Installations 47

Hardware overview 47

Servers 47

SCSI converters 47

Internal storage 48

External disk storage 48

Fibre Channel upgrade card 49

Cabling and connecting VTS 49

Connecting the HP ProLiant DL585 G1 (VT5900-A) 50

Connecting the HP ProLiant DL380 G4 (VT5900-B and VT5900-C) 51

Connecting the HP ProLiant DL385 G2 (VT5900-E) 52

Connecting the HP ProLiant DL385 G2 (VT5900-G) 53

iv | Virtual TapeServer Supplemental Installation Guide

Connecting to the HP ProLiant DL385 G5 (VT5900-H) 54

Connecting to the HP ProLiant DL385 G5 (VT5900-J) 57

Connecting to the HP ProLiant DL185 G5 (VT5900-K) 59

Connecting to the HP ProLiant DL380 G6 (VT5900-L) 60

Connecting to the HP ProLiant DL185 G5 (VT5900-O) 60

Modifying virtual tape connections 62

Upgrading a SCSI Adapter to a Fibre Channel Adapter 63

On the HP ProLiant DL585 G1 (VT5900-A) 63

On the HP ProLiant DL380 G4 (VT5900-B and VT5900-C) 65

Index 69

v

Preface

Welcome to the Virtual TapeServer Supplemental Installation Guide. This guide provides additionalconfiguration information for Virtual TapeServer (VTS), which should be used after completing theprocedures in the Virtual TapeServer Quick Start Guide and Virtual TapeServer Configuration Guide. Thisguide is provided for HP personnel only.

Supported release version updatesThis guide supports all J06 release version updates (RVUs), all H06 RVUs, and all G06 RVUs, untilotherwise indicated in a replacement publication.

Typographical conventionsThis guide uses the following typographical conventions:

Convention Description

Bold Used for file names, field names, URLs, interface elementsthat are clicked/selected, and information that must beused literally.

Bold Italic Represents variables within file names, command syntax,URLs, or other literal text.

Italics Used for emphasis, book titles, and variables.

Monospace Used for text that is displayed on-screen, command namesand arguments (syntax), code, and command-line text.

Monospace Italic Represents variables within command syntax, code, orcommand-line text.

Blue Text Used for cross-references.

This icon notes the user who is responsible for performing the procedure that follows.

Related documentationThe following documentation is provided for VTS:

l Quick Start Guide, which provides instructions for installing the hardware and configuring VTSon the network.

vi | Virtual TapeServer Supplemental Installation Guide

l Configuration Guide, which describes how to configure VTS and how to use the VTS webinterface to manage VTS.

l Help, which provides detailed instructions for working with the web interface

l Release Notes, which provides information about system support, known issues, upgrade anddowngrade instructions, and other information about the current release.

All documentation is available on the About page of the web interface.

1

1Installing GFS

The Global File System (GFS) is an advanced feature that allows Linux servers to simultaneously readand write files on a single shared file system on a SAN. VTS is based on Linux, and GFS enablesmultiple VTS servers to access a shared set of pools and virtual tapes. The Event ManagementService (EMS) can then automatically mount virtual tapes from the GFS pools as if they wereseparately mounted.

With GFS, all VTS servers connect to each other over Fibre Channel to the same storage array, andGFS allows each VTS to access all vaults at the same time. If a server becomes unavailable, otherservers can still access the vaults.

This chapter describes how to install GFS in the VTS environment.

Note Additional information about managing GFS is provided in the Maintaining GFS for VTSappendix of the Virtual TapeServer Configuration Guide.

2 | Virtual TapeServer Supplemental Installation Guide

Installing or reinstalling GFSDuring the installation of GFS, you must configure a fencing method for the cluster. You can configureFibre Channel switch fencing if the external storage device is connected over Fibre Channel (forexample, if the HP StorageWorks Modular SAN Array provides a built-in Fibre Channel switch). Or,you can configure HP Integrated Lights-Out (iLO) to handle fencing. Refer to the following for moreinformation about fencing:

l Fencing overview — https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Suite_Overview/s2-fencing-overview-CSO.html

l Configuring fencing devices with Conga (luci and ricci) —https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/s1-config-fence-devices-conga-CA.html

Note When connecting to the Fibre Channel switch used for fencing, ensure that dual pathsare not created when zoning is configured.

l All other Red Hat documentation — https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/

The following topics are relevant: “Cluster Administration", "Cluster Suite Overview", and"Configuration Example - Fence Devices”.

Also, if you encounter problems while installing GFS, you may need to delete a cluster. TheURLs listed here provide this information as well.

Note If path failover is configured in the environment, be sure to reference the multipathed mapperdevice instead of the sd device in the following procedure. For example, reference/dev/mapper/mpathX instead of /dev/sdX.

The following steps assume that the physical cabling of the servers and storage is complete andconnectivity has been verified.

To install GFS1. Log in to the operating system of the VTS server.

2. Become root:

su -

3. Mount the GFS Install/Upgrade DVD. This example illustrates mounting the DVD on/media/cdrom:

mkdir -p /media/cdrom

mount /dev/cdrom /media/cdrom

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Suite_Overview/s2-fencing-overview-CSO.html










https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/s1-config-fence-devices-conga-CA.html











https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/




Installing GFS | 3

4. Install the GFS RPMs by entering the following command:

/media/cdrom/installGFS.bash

Ignore any warnings that may be displayed.

5. Unmount and eject the DVD:

umount /media/cdrom

eject

6. Enter the following commands to disable clustering services that are included with the GFSbut not used by VTS. Failure to disable these can cause the system to hang.

chkconfig openais off && service openais stop

chkconfig saslauthd off && service saslauthd stop

If any of these commands returns a failure, it is not an error. It indicates that the process wasnot running.

7. GFS RPMs inadvertently remove SCSI target mode support. To address this and maintaincorrectly functioning virtual tape drives (VTDs), run the following command:

/usr/local/tape/bin/mkinitrd.pl -f

The VTS server is rebooted after this completes.

8. Repeat these steps on each server (node) that will be included in the cluster.

Complete the next four steps (steps 9-12) on only one server (node) that will be included in thecluster. It is recommended that you shutdown all nodes in the cluster other than the one used inthese steps. If you are creating multiple vaults, you must also complete steps 9-12 for each GFS filesystem to be used for vault storage.

9. Choose your device(s) to be used for GFS. You can use the fdisk -l command to list devices andnote the partition information (/dev/sde, for example). If a partition is not listed, checkconnections to storage. Or, the storage may need to be configured; refer to the storagedocumentation for details.

In the commands and output below, /dev/sde is used as an example device.

VTS assumes an empty, unpartitioned disk, and further disk partitioning is not performed.Cluster members will mount devices based on LVM names, not SCSI device names, and theseGFS devices will not use disk labels.


If the vault will be less than 2TB in size, complete the following steps to partition the disk:

a. Enter the following command to partition the device.

fdisk /dev/sde

b. Enter n to add a new partition.

c. Enter p to specify the primary partition.

d. Enter 1 to specify the first partition.

e. Press ENTER to accept the defaults.

f. Enter w to save the configuration.

To confirm the configuration, enter the following command:

fdisk -l /dev/sde

Here is an example of the output:

Disk /dev/sde: 18.4 GB, 18413722112 bytes

255 heads, 63 sectors/track, 2238 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System

/dev/sde1 1 2238 17976703+ 83 Linux

If the vault will be 2-4TB in size, complete these steps to partition the disk:

a. Start the partition editor, which is an interactive program similar to fdisk:

parted /dev/sde

b. Create a GPT disk label, which is a GUID partition table:

mklabel gpt

c. Create a 4TB primary partition at the beginning of the disk:

mkpart primary 0 4000G

Note You can specify 100% instead of 4000G to create a partition that uses the entiredisk.

d. Quit parted.

quit

Installing GFS | 5

10. Perform LVM initialization of the device. /dev/sde1 is used as an example partition on the/dev/sde device.

a. If GFS was previously installed and you want to remove all volume data, enter thefollowing commands to remove the logical volume (lv1) and wipe labels from thephysical volume (sda1):

lvremove -f /dev/gfsvg1/lv1 gfsvg1

pvremove /dev/sda1 -ff

When prompted, enter y to confirm.

b. Create the physical volume by entering the following command:

pvcreate /dev/sde1

You may need to use the -ff option to force creation.

c. Create the volume group by entering the following (this example creates the gfsvg1group):

vgcreate gfsvg1 /dev/sde1

d. Create the logical volume by entering the following command. The -l 100%FREE optioncreates a logical volume using the entire volume group.

lvcreate -l 100%FREE -n lv1 gfsvg1

e. Enter the following command to confirm the physical volume:

pvscan


PV /dev/sde1 VG gfsvg1 lvm2 [17.14 GB / 0 free]

Total: 1 [17.14 GB] / in use: 1 [17.14 GB] / in no VG: 0 [0 ]

f. Enter the following command to confirm the volume group:

vgscan


Reading all physical volumes. This may take a while...

Found volume group "gfsvg1" using metadata type lvm2


g. Enter the following to display details about the physical volume:

pvdisplay


--- Physical volume ---

PV Name /dev/sde1

VG Name gfsvg1

PV Size 17.14 GB / not usable 3.37 MB

Allocatable yes (but full)

PE Size (KByte) 4096

Total PE 4388

Free PE 0

Allocated PE 4388

PV UUID tTHBFt-6pqc-ILIY-Uis5-L8Yn-bvBu-SCN3MV

h. Enter the following to view details about the volume group:

vgdisplay


--- Volume group ---

VG Name gfsvg1

System ID

Format lvm2

Metadata Areas 1

Metadata Sequence No 2

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 1

Open LV 1

Max PV 0

Cur PV 1

Act PV 1

VG Size 17.14 GB

PE Size 4.00 MB

Total PE 4388

Alloc PE / Size 4388 / 17.14 GB

Free PE / Size 0 / 0

VG UUID lm4cH7-4wgq-s1VR-VNwc-pFC6-i54u-h5tKxk

Installing GFS | 7

i. Enter the following command to view details about the logical volume:

lvdisplay


--- Logical volume ---

LV Name /dev/gfsvg1/lv1

VG Name gfsvg1

LV UUID VQUsmh-LI1E-rBIm-3tCe-9o6K-cjlp-ah8e4j

LV Write Access read/write

LV Status available# open 0

LV Size 17.14 GB

Current LE 4388

Segments 1

Allocation inherit

Read ahead sectors 0

Block device 253:0

11. Create the GFS file system:a. Enter the following command. Note that any data that may reside on the logical volume

(dev/gfsvg1/lv1 is used as an example) is destroyed.

gfs_mkfs -p lock_dlm -t cluster_name:gfs01 -j journals

/dev/gfsvg1/lv1

where

-p lock_dlm sets the lock manager to DLM

-t cluster_name specifies the cluster name; restrict the cluster name length to 15characters or less

-j journals specifies the number of journals to create, which should be the number ofnodes plus two

b. When prompted, enter y to proceed. Output similar to the following is displayed:

Device: /dev/gfsvg1/lv1

Blocksize: 4096

Filesystem Size: 4394620

Journals: 3

Resource Groups: 68

Locking Protocol: lock_dlm

Lock Table: cma:01


Syncing...

All Done

12. Start ricci and luci.

For more information about these GFS services, refer to chapters 3 and 4 of this guide:https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/index.html.

These services must be configured in the cluster before you can mount the newly created GFSvolume. Complete the following steps to start the services.

a. Make sure that the luci system has a proper /etc/hosts file. Here is an examplecommand to confirm the contents of the file:

cat /etc/hosts

Here is an example of the file:

# Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1 localhost.localdomain localhost

192.168.80.2 vtsdev27.commstor.crossroads.com vtsdev27

The file should list all cluster nodes. The localhost entry (including IP address and nodename) is for the system you are using and the other entries are for the cluster nodes.

b. On each node, start ricci:

chkconfig ricci on

service ricci start

To confirm that ricci is running, enter the following:

service ricci status

c. On one (and only one) of the cluster servers, configure and start the luci service. RedHat recommends configuring luci on a non-cluster node. It will function properly on acluster node, though web connectivity is lost while the system is rebooting. If the lucinode goes down, the cluster cannot be administered with luci.

luci_admin init

When prompted, enter a new password.

Then, restart the luci service:

service luci restart

https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/index.html






Installing GFS | 9

Note the URL given in the output; you will access it in the next step.

d. Configure the cluster using the luci web interface:a. Access the web interface by loading the URL given in the previous step in a web

browser.

b. When prompted, accept the certificate permanently.

c. Click OK if a certificate domain mismatch warning is displayed.

d. Log in by entering the luci admin username and password.

e. Click Add a System.

f. Enter the fully qualified domain name or IP address of the GFS system.

g. Enter the root password for that system.

h. Click Add another entry.

i. Enter each cluster member's name and root password, and click Submit.

j. Click the Cluster tab at top of the page.

k. Click Create a New Cluster.

l. Enter the same cluster name specified in step 11a.

m. Enter each system's fully qualified domain name or IP address and rootpassword.

n. Select Use locally installed packages.

o. Make sure Enable Shared Storage Support is selected.

p. Click Submit.

Although the interface states that the systems are rebooted, they are not.

13. Configure fencing:a. In the browser, under the cluster name in the left column, click Nodes.

b. For each node, click Manage Fencing for this Node.

c. Under Main Fencing Method, click Add a fence device to this level.

d. Select brocade fabric switch.

e. Enter the hostname of the Fibre Channel switch. Consult your SAN administrator for thisinformation.

f. Enter the IP address of the Fibre Channel switch. Consult your SAN administrator forthis information.

g. Enter the username for accessing the Fibre Channel switch. Consult your SANadministrator for this information.


h. Enter the corresponding password. Consult your SAN administrator for this information.

i. Enter the port of the Fibre Channel switch. Consult your SAN administrator for thisinformation.

j. Click Update.

Repeat these steps for each node in the cluster.

14. Add GFS storage to the cluster:a. In left-hand column of the web interface, under the cluster name, click Resources.

b. Click Add a resource.

c. Select GFS.

Note Do not select GFS2.

d. For the name, enter the vault name (for example, VAULT10).

e. For the mount point, enter the location where you want the vault to appear (forexample, /VAULT10).

f. For the device, enter the name of the device specified in step 11 (for example,/dev/gfsvg1/lv1).

g. Leave the options and filesystem ID blank.

h. Click Submit.

Because the LUN-to-device mapping can be different on each system, clvm logical volumenames are globally unique. You cannot create duplicates.

Repeat these steps for each GFS file system.

15. If GFS was previously installed, you may need to rediscover the previous GFS volume byrunning these commands:

pvscan

lvscan

vgscan

16. Complete the following steps on each cluster node to verify that all cluster nodes can accessthe GFS volumes, mount them, and access files written by other nodes. In the following steps,VAULT10 is used as the name of the vault.

a. Configure the /etc/fstab file to automatically mount the file system when VTS restarts.Add a line to the file that is similar to the following:

/dev/gfsvg1/lv1 /VAULT10 gfs defaults 0 0

Installing GFS | 11

b. Enter the following commands on the console of the node:

mkdir /VAULT10

mount -a -t gfs

chown bill.root /VAULT10

chmod 755 /VAULT10

ls -al /VAULT10

The following is an example of output for the ls command:

total 12

drwxr-xr-x 2 root root 3864 May 15 15:24 .

drwxr-xr-x 4 root root 4096 May 15 17:59 ..

c. Enter the following command to verify that there is free space on the mounted GFS filesystem.

df -H /VAULT10


Filesystem Size Used Avail Use% Mounted on

/dev/mapper/gfsvg1-lv1 17G 36K 17G 1% /VAULT10

d. Enter the following command to verify that you can write to the mounted GFS filesystem.

touch /VAULT10/`hostname`

e. Verify that files written by other VTS servers are visible by entering the followingcommand:

ls -al /VAULT10


total 28

drwxr-xr-x 2 root root 3864 May 16 11:32 .

drwxr-xr-x 4 root root 4096 May 15 17:59 ..

-rw-r--r-- 1 root root 0 May 16 11:32

vtsdev27.commstor.crossroads.com

After completing these steps on each node, this output lists each system's hostname inthe vault directory. Be sure to delete these files after completing this installationprocedure.


17. Verify fencing.

Note These steps verify Brocade Fibre Channel fencing only.

Before performing these steps, make sure you are not logged into the switch through Telnet. Ifyou are logged in, the brocade fencing script will fails with an error similar to the following:

/sbin/fence_brocade -a ip_addr -l username -n 2 -p password -o disable

pattern match read eof at ./fence_brocade line 138

# echo $?

255

where ip_addr, username, and password is that of the Fibre Channel switch. Consult your SANadministrator for this information.

To verify the fencing method, enter the following commands:

/sbin/fence_brocade -a ip_addr -l username -n 2 -p password -o disable

/sbin/fence_brocade -a ip_addr -l username -n 2 -p password -o enable

18. Complete the following steps to configure fencing from luci:a. From the luci web interface, select the node.

b. Select choose a task...

c. Select fence this node.

d. From the command line, enter the following:

tail -f /var/log/messages


May 15 19:06:19 VTS_svr fence_node[28881]: Fence of "VTS_svr2"

was successful

19. Test fencing. In a separate window, enter the following command to view for fencing messagesin the system log file:

tail -f /var/log/messages

Here is an example of the messages:

May 15 19:10:25 VTS_svr fenced[10804]: VTS_svr2 not a cluster member

after 0 sec post_fail_delay

May 15 19:10:25 VTS_svr fenced[10804]: fencing node "VTS_svr2"

May 15 19:10:26 VTS_svr fenced[10804]: fence "VTS_svr2" success

20. If EMS will be used, configure EMS as described in the EMS chapter of the Configuration Guide.

To power up a GFS cluster after installation, refer to the GFS appendix in the Configuration Guide.

Installing GFS | 13

TroubleshootingThis section describes how to verify the installation and troubleshoot any issues.

1. Verify that the appropriate services are enabled and started by entering the followingcommands:

chkconfig cman on && service cman restart

chkconfig clvmd on && service clvmd restart

chkconfig ricci on && service ricci restart

Note that these commands also restart fencing and deactivate the cluster.

2. Verify that logical volumes cannot be seen by attempting to mount a logical volume(/dev/gfsvg1/gfslv1 and VAULT10 are example values):

mount /dev/gfsvg1/gfslv1 /VAULT10

Here is an example of the output if the logical volume is not visible:

mount: special device /dev/gfsvg1/gfslv1 does not exist

3. Verify that the volume is active:

ls /VAULT10

4. Using the luci web interface, ensure that nodes are not fenced.

5. Enter the following command to activate all known volume groups in the system:

vgchange -ay


1 logical volume(s) in volume group "gfsvg1" now active

6. Mount the vault by entering this command:

mount /dev/gfsvg1/gfslv1 /VAULT10

7. If luci will not start or restart, enter the following:

service luci start

or

service luci restart


If luci can see a node but indicates that ricci is not running, but the node shows ricci isrunning, output to the similar is displayed:

luci[15356]: Unable to establish an SSL connection to

192.168.80.2:11111: ricci's certificate is not trusted

Enter the following commands to remove luci:

rpm -e luci

rm -rf /var/lib/luci

You may need to reinstall luci or re-import the cluster. The luci RPM is available on the GFSInstall/Upgrade DVD. If necessary, mount the DVD and enter the following command to installluci:

rpm -ivh /media/cdrom/vts-6.04-gfs-install/luci*.rpm

To review the cluster status, enter the following command:

cman_tool status


Version: 6.0.1Config Version: 5Cluster Name: cmaCluster Id: 711Cluster Member: YesCluster Generation: 64Membership state: Cluster-MemberNodes: 2Expected votes: 1Total votes: 2Quorum: 1Active subsystems: 7Flags: 2nodePorts Bound: 0 11Node name: 192.168.80.2Node ID: 2Multicast addresses: 239.192.2.201Node addresses: 192.168.80.2

15

2Enabling BMA Integration and Migration

Through integration with a backup management application server, you can read and write files toand from Virtual TapeServer (VTS). You can then enable VTS to export, or “migrate”, virtual tapes tophysical tapes using an attached external tape device. On upgraded servers, you can configure thehsm_ parameters in the configuration file to enable migration, which is described in this chapter.

Note You can also configure stacked export jobs if capacity is licensed, which is described in theConfiguration Guide.

To enable migration, you must install a backup management application (BMA) client on the VTSserver, which runs the Linux operating system. The BMA treats VTS as a UNIX host on the enterprisenetwork. Virtual tapes are then exported to the tape library managed by the BMA server accordingto policies set by the BMA administrator. Refer to BMA documentation for instructions and moreinformation.

After installing and configuring the BMA, you must configure the Event Management Service (EMS)on VTS. This is done using the VTS web interface. And you must configure the hsm_ parameters asdescribed in this chapter.

To automatically migrate tapes, you can configure the VTSPolicy command on the VTS server toautomatically export tapes. You can also manually initiate stacked exports by clicking the Migratebutton on the Virtual Media - Operation page. A BMA client must be installed and configured on theVTS server to enable manual migration. You can use an external tape device attached duringinstallation, or you can attach a device as described in the Configuration Guide.

The BMA server can migrate virtual tapes using the following methods:

l The BMA administrator creates a backup job on the BMA server and schedules it to run on theBMA client. The BMA server manages the entire process and maintains a database of thebackup files including a list of physical tapes to which the data was written. The BMA serveralso controls the tape library.

If VTS deletes or erases a virtual tape, the BMA administrator must restore the virtual tape,when necessary. If Tivoli Storage Manager is used, the mount request is queued on VTS untilthe data is recovered by the BMA server from physical tape if the server requests access to avirtual tape that was erased or deleted.

l VTS can request that the BMA server perform a backup or restore. This request is generatedwhen you manually initiate a migration. This request is issued using the BMA command-lineinterface. VTS generates the BMA command request, executing it on the VTS server. The BMA


client will request services from the BMA server, which may be located on the VTS server oron a remote server. The BMA server then identifies the tape to back up or restore andinstructs the tape library to perform the operation.

l A VTSPolicy command sent from the host server through EMS can initiate migration.VTSPolicy can initiate many of the commands that are available on the BMA server. Thecommand can be scheduled on the host server using NetBatch or appended to a TandemAdvanced Command Language (TACL) backup script.

Be sure that the BMA client is installed and configured on the VTS server. Refer to the BMAdocumentation for more information. Then, modify the VTS configuration file to configure migration,which entails configuring the hsm_ parameters, and then set the username and password.

Note A default configuration file is defined for each VTS server. To override the default settings, youmust define settings as described below.

To enable and configure migration

Requires the Edit VTS Configuration File access right

1. Click Configuration > System on the navigation pane of the VTS interface.

2. Click Edit Configuration File.

3. Add the following parameters at the bottom of the file that is displayed:

Parameter Description ValuesReq'-d?

hsm_enable Enables migration.

Default value: YES

YES or NO Yes

hsm_product Identifies the BMA:

l TSM for TivoliStorage Manager

l LEG for Networker

l BEX for BackupExpress

l NBP for NetBackup

l CMV forCommVault Galaxy

For automated migration,

TSM, LEG, BEX, NBP, orCMV

Yes

Enabling BMA Integration and Migration | 17


you can specify any ofthese values, whichdepends on the BMA.

Default value: TSM

hsm_server For Backup Express,NetBackup, Networker,and CommVault Galaxyonly:

Specifies the BMA serverhostname or IP address.

Hostname or IP addressof the VTS server

Yes

hsm_pool For Networker only:

Specifies the pool name.

Pool name Yes

hsm_backup_pools For Backup Express only:

Specifies the pool nameswhere the virtual tapesto be migrated reside.

Pool names, separatedby spaces

Yes

hsm_backup_options

For Backup Express only:

Specifies the backupoptions for all pools.

checksum, EOJ, orretention

Yes

hsm_backup_options_poolname

For Backup Express only:

Specifies the backupoptions for the poolspecified by poolname.

checksum, EOJ, orretention

Yes

hsm_restore_device For Backup Express only:

Specifies the restoredevice.

Name of the restoredevice.

No



hsm_optfile For Tivoli StorageManager only:

Specifies the path to theoptfile file.

Default value: dsm.opt

Path Yes

hsm_optfile_pool For Tivoli StorageManager only:

Specifies the path to theoptfile file for a specificVTS pool. This parameteroverrides the hsm_optfileparameter for the pool.

Path No

hsm_put_batch_size For Tivoli StorageManager only:

Specifies the maximumnumber of virtual tapesto lock and migrate at atime, thereby creatingbatches of tapes tomigrate. This parameteris optional and set to 0 bydefault, which causes VTSto lock all target virtualtapes until the migrationis complete.

Note: Using thisparameter may impactperformance, slowing themigration.

Integer, from 1-30 No

hsm_policy For NetBackup only: Policy Yes



Specifies the backuppolicy.

hsm_schedule For NetBackup only:

Specifies the backupschedule. (Typically, aUser schedule isspecified.)

The schedule name Yes

hsm_client For CommVault Galaxyonly:

Specifies the hostname orIP address of the VTSserver on which theCommVault client isinstalled.

Hostname or IP address Yes

hsm_backupset For CommVault Galaxyonly:

Specifies the name of thebackup set, which is thelogical grouping ofsubclients in CommVault.

Backup set name Yes

hsm_subclient For CommVault Galaxyonly:

Specifies the name of thesubclient policy, whichconsists of one or moreCommVault subclienttemplates. The templatescontain a commonconfiguration that youwant applied to target

Policy name Yes



subclients within aCommCell.

hsm_erase_after_backup Enables VTS toautomatically erase avirtual tape after it issuccessfully migrated.Only the tape data iserased; the metadataremains.

Default value: NO

YES or NO No

hsm_joblog_maxnum Specifies the maximumnumber of job log files tobe retained. These filescontain the output fromeach job. This valueapplies separately tobackup and restore jobs.If set to zero, no logs areretained.

Default value: 20

Integer, from 0-999 No

hsm_summary_limit Specifies the number oflines retained in the logfile, which records thecommand used to invokeeach backup or restorejob. This is a joint logthat contains only thecommands used, not thejob output.

Default value: 1000

Integer No



hsm_restore_period For Backup Express only:

Specifies how far back intime the BMA shouldsearch its catalog for thefile to be restored.Specify the restore periodin the nnU format where:

l nn is a numberbetween 1 and 99

l U is the unit;specify “d” fordays, “w” forweeks, or “y” foryears

Default value: 90d

Value No

ems_hsm_backup_notification

Sends notifications to theNonStop kernel (NSK)from the EMS Telnetpolicy process. Forexample, after a virtualtape is migrated, asuccessful or failedmessage is generated sothat the NSK candetermine if theoperation was successful.

Default value: YES

YES or NO No


Here are sample configurations for each BMA. When setting values for your environment, besure to use your hostname, paths, and so on.

l Tivoli Storage Manager:

hsm_enable='YES'

hsm_product='TSM'

hsm_optfile='dsm.opt'

hsm_optfile_E1_HAL_10YEARS='/usr/opt/dsm.server10.opt'

ems_hsm_backup_notification='YES'

l Networker:

hsm_enable='YES'

hsm_product='LEG'

hsm_pool='POOL'

hsm_server='SERVER'


l Backup Express:

hsm_enable='YES'

hsm_product='BEX'

hsm_server='lab-bex'

hsm_backup_pools='MEDIAPOOL DLT DEVICEPOOL'

hsm_backup_options='CHECKSUM Y; EOJ_ACTION U; RETENTION 999;'

hsm_backup_options_LABELED='CHECKSUM Y; EOJ_ACTION U; RETENTION

999;'

hsm_backup_options_CADE='CHECKSUM Y; EOJ_ACTION U; RETENTION

999;'

ems_hsm_backup_notification='YES'hsm_restore_period='90d'

l NetBackup:

hsm_enable='YES'

hsm_product='NBP'

hsm_policy='POLICY'

hsm_schedule='USER'

hsm_server='SERVER'


l CommVault Galaxy

hsm_enable='YES'

hsm_product='CMV'


hsm_server='stingray3'

hsm_client='server42'

hsm_backupset='server42_OnDemand'

hsm_subclient='default'

4. Click SAVE.

5. Set the username and password for the BMA.

Note This step is required for CommVault Galaxy, Backup Express, and NetBackup only.

a. Click Security > Passwords on the navigation pane.The following page is displayed:

b. Select hsm from the drop-down list and configure a password. Click Help for completeinstructions.

24 | Virtual TapeServerSupplemental Installation Guide

25

3Enabling and Configuring AutoCopy and Instant DR

Data Replication is a advanced software feature that enables you to back up data to remote VirtualTapeServer (VTS) servers. This feature was implemented as Instant DR and AutoCopy before thisrelease; Instant DR and AutoCopy are supported on upgraded systems.

To configure Instant DR and AutoCopy, you must configure network settings for all VTS locations.Adhere to the following requirements and guidelines when configuring these software modules:

l The VTS server provides two Ethernet ports (eth0 and eth1). Under normal circumstances,eth0 is used for local IP traffic to access the user interface for the VTS and for mountingcommunication between VTS and hosts. When Instant DR is configured, eth1 is configured witha routable address to communicate with additional VTS servers at remote locations.

l The Event Management Service (EMS) is responsible for monitoring mounts and dismountsrelevant to AutoCopy. Therefore, EMS must be configured and running on the VTS server asdescribed in the EMS chapter of the Virtual TapeServer Configuration Guide.

l SSH must be configured on all VTS servers if you want to secure data when copying data toremote locations (for Instant DR). Also, it must be configured on all VTS servers involved inAutoCopy operations. SSH must be configured for Protocol 2 RSA or DSA encryption usingPublic Key Identification. Public Key Identification requires that the sender’s Public Key beinstalled in the specific authorized_keys file on the receiver VTS system.

l It is very important that SSH communications flow though network connections from one VTSsystem to another. A single gigabit connection is used to handle the SSH data transfer andother communications between VTS systems. To prevent congestion, because of the highvolume of traffic that can flow over a connection used for Instant DR or Autocopy, it isrecommended that a completely separate gigabit subnet be used to connect VTS systems.Network speeds of less than a gigabit are not recommended. The ProLiant servers do notsupport speeds of greater than one gigabit.

l For AutoCopy, the source and target servers must have the same software version installed.

After completing the procedures in this chapter, refer to the Virtual TapeServer Configuration Guidefor instructions on using the Data Replication feature to import and export virtual tapes.


Overview of Instant DRInstant DR enables you to create and maintain identical copies of backup data on VTS disk storage atone or more locations. Virtual tapes are transmitted from one vault to another. The Instant DR jobsindicate the pools or virtual tapes to be transmitted. When a job is initiated, a copy of the virtualtape is transmitted over the network link. Be aware that the virtual tapes duplicated on a remotevault consume additional disk space, which is the same amount as the original virtual tape.

VTS servers cannot “see” each others’ pools and virtual tapes until the Instant DR jobs run. The poolsand virtual tapes in the primary operation page look identical if all virtual tapes are copied. Ifselected virtual tapes are copied using the Instant DR job, the virtual tape and pool lists aredifferent. Automatic Event Management Service (EMS) mounting chooses from pools as it would inday-to-day operations because the virtual tapes will be created in the new vault.

Note An Instant DR job will fail if the virtual tape already exists in another pool on the target.Virtual tape names must be unique across all vaults and pools.

If an encrypted virtual tape is stored on an Instant DR server and the Instant DR server attempts toperform an operation on the tape, Data Encryption must be enabled and the key server that was usedto encrypt the tape must be configured on the Instant DR server. If not, the tape operation will failand an error message is displayed on the Instant DR server indicating that the operation failed. Referto the Virtual TapeServer Configuration Guide for information about Data Encryption and anexplanation of the possible failures.

In general, Instant DR should be used if files do not change much from day to day. Data is transmittedin batches, one or more times per day, and only data differences are sent. Bandwidth is consumedwhen the data transmission is scheduled according to policy, usually during off-peak hours. Instant DRis supported across multiple sites, from one to many servers based on the configuration.

Instant DR performs well in environments where the backup data does not significantly change on adaily basis. Synchronizing transaction files, which can change constantly, is not necessary a good useof Instant DR. Poor performance may result when synchronizing transaction files because the processby which Instant DR computes file differences can take longer than copying an entire file. You mayalso rely on AutoCopy for synchronizing data. See "Overview of AutoCopy" below to determine ifAutoCopy is a better solution for your needs.

If Instant DR is licensed, you must enable licensing by entering the license key as described in theVirtual TapeServer Configuration Guide. Then, you can create new Instant DR backup schemes as wellas launch and monitor the remote synchronization processes. You can also automate Instant DRbackups using the VTSPolicy command, if EMS communication is configured (refer to the EMS chapterof the Configuration Guide). This chapter describes how to perform these tasks.

Overview of AutoCopyAutoCopy enables you to copy a virtual tape from one VTS server to another when the virtual tape ismounted, modified, and dismounted by the host server. Configure AutoCopy to set the following:

l The pools to be monitored for mount and dismount activity on the VTS system

l The VTS system that will be the recipient of copies of modified virtual tapes

l The pool name on the target and recipient VTS system

Enabling and Configuring AutoCopy and Instant DR | 27

AutoCopy is enabled at the pool level; all virtual tapes contained in the pool are monitored andcopied when necessary. If VTS fails to copy a virtual tape, it retries the AutoCopy operation everyfive minutes for a total of twelve attempts. If the operation fails altogether, a failure message is sentto the event log.

Note Autocopy will fail if the virtual tape already exists in another pool on the target. Virtual tapenames must be unique across all vaults and pools.

If an encrypted virtual tape is stored on an AutoCopy server and the AutoCopy server attempts toperform an operation on the tape, Data Encryption must be enabled and the key server that was usedto encrypt the tape must be configured on the AutoCopy server. If not, the tape operation will fail andan error message is displayed on the AutoCopy server indicating that the operation failed. Refer tothe Virtual TapeServer Configuration Guide for information about Data Encryption and an explanationof the possible failures.

In general, AutoCopy should be used if files change often throughout the day. VTS automaticallymonitors pools designated for AutoCopy. If a change is detected, data is transmitted when eachvirtual tape is unmounted. This means that bandwidth may be consumed throughout the day, whichmay coincide with user activity on the network. You may also rely on Instant DR for synchronizingdata. See "Overview of Instant DR" on page 26 to determine if Instant DR is a better solution for yourneeds.

Event Management System (EMS) and Secure Shell (SSH) are prerequisites for AutoCopy. EMS mustbe configured and running correctly as described in the EMS chapter of the Configuration Guide. TheEMS service is responsible for monitoring mounts and dismounts relevant to AutoCopy. SSH must beconfigured on the source VTS server (contact your authorized service and support representative ifyou need help configuring SSH). AutoCopy performs the copy operation from the source VTS systemto the target VTS system using an SSH transfer, which encrypts communication between the VTSsystems. The VTS systems that receive virtual tape copies do not have to be configured for EMS orAutoCopy.

AutoCopy assumes that a virtual tape mounted in Read/Write or With Ring mode will be modifiedupon dismount. NonStop mount requests that are designated No Ring are mounted as Read Only andare not automatically copied.

Using Instant DR or AutoCopyInstant DR and AutoCopy features have distinct advantages that may be specific to individual sites orrequirements. In general, Instant DR should be used if files do not change much from day to day.AutoCopy is best used if files change often throughout the day. Keep the following in mind whenenabling these features:

Instant DR AutoCopy

How often is data copied? In batches Individually, as each virtualtape is unmounted

When is data transmitted? Synchronized, once or moreper day

As each virtual tape isunmounted

How is the feature initiated? By policy scheduling or the Automatically, virtual tapes


Instant DR AutoCopy

Dispatch button on theInstant DR page in the VTSweb interface

in the pool are monitoredand copied when necessary

At what level are changesmade (implementationgranularity)?

Vault, pool, or virtual tape Pool only

How much data istransmitted?

Data difference only, whichmay reduce datatransmission

Bit-for-bit (1:1) copyoperation

When is bandwidthconsumed?

Per schedule, usually off-hours

Throughout the day, maycoincide with user activity

How many backup sites aresupported?

Multiple sites, from one siteto many based on setup

Single site, from one site toanother

Is tuning supported? Initiates multiple jobs toovercome delays

Single job only

You may use Autocopy and Instant DR separately or at the same time. However, if Autocopy andInstant DR are used simultaneously, it should be noted that they may not be run on the same virtualtapes. For example, you may run Autocopy on vtapeA in PoolXYZ while also running an Instant DR jobon vtapeB in PoolXYZ. However, you cannot run Autocopy on vtapeA in PoolXYZ and then immediatelyrun an Instant DR job for PoolXYZ in its entirety. This is because vtapeA will be in use and locked byAutocopy. In this case, the Instant DR job would fail.

Configuring network settingsYou must configure network settings for all VTS locations. To configure the primary (local) system,you must attach a monitor, keyboard, and mouse to the VTS server. To configure secondary (remote)systems, you must use a remote-access application to access those systems, or perform the steps ateach site. The IP address, which will differ for each VTS server, must be configured at the primaryand secondary sites. Consult your network administrator to determine the gateway and subnet maskto use for each system.

In addition, you should be familiar with networking concepts to complete the steps in this section.Obtain the following information before beginning this procedure:

l Root access to the VTS system; refer to the Configuration Guide for a list of the defaultaccounts provided on the server

l IP address, subnet mask, and gateway of each VTS server


The following steps use two sites as an example of enabling Data Replication between two sites,Server A and Server B, connected by a wide area network (WAN):

To configure network settings1. Verify that the hostname, IP address, and gateway are configured on each VTS server in the

environment. Refer to the Quick Start Guide for more information.

2. If DNS or DHCP is not configured in your environment and you want the servers tocommunicate using hostnames, set up the /etc/hosts file to configure aliases for each VTSserver in the environment. Perform this step on the secondary server for each primary VTSserver.

a. At the command prompt, log in.

b. Become root:

su -

c. Be sure the file contains the IP address, hostname, and alias for the primary VTS serverand the secondary server(s). Here is an example of the file on Server A:




10.10.2.144 server_a.domain.com server_a

10.10.2.145 server_b.domain.com server_b

Here is an example of the file on Server B:




10.10.2.145 server_b.domain.com server_b

10.10.2.144 server_a.domain.com server_a


3. Test connectivity by pinging the network connections. At the prompt, enter ping hostname.For example, to ping Server B, enter ping server_b. Output similar to the following isdisplayed:

64 bytes from server_b (10.10.2.145): icmp_seq=0 ttl=64 time=0.053 ms




Press CTRL-C to stop the ping process.

If you receive a timeout error, check cabling or contact a network administrator forassistance. If you receive an unknown host error, check the /etc/hosts file and make sureeverything is correct. Note that the hostnames in this file are case-sensitive.

4. Set up and authorize secure shell (SSH).a. At the command prompt, become bill:

su - bill

b. Generate an authorization key for SSH for the secondary server, to authorize remoteaccess for the bill user:

ssh-keygen -t rsa

c. Press ENTER to save the file in the default location. This step creates the/home/bill/.ssh/ directory.

d. Press ENTER to skip the pass phrase.

e. Press ENTER to verify skipping the pass phrase.

f. Copy the generated authorization key to the secondary server (Server B):

ssh-copy-id –i /home/bill/.ssh/id_rsa.pub bill@server_b

g. When prompted, enter yes.

h. Enter the password for the bill user at the secondary server.

Note If problems arise when using SSH with the secondary server, you can remove the/home/bill/.ssh/known_hosts and /home/bill/.ssh/authorized_keys files from thesecondary and primary servers and repeat the steps above.


5. If you configured SSH and access to the bill account is restricted on the VTS servers, you mustgrant SSH access to the bill user for each VTS server. To do this, become root (enter su -root) and then edit /etc/ssh/sshd_config to add this line:

AllowUsers vtsa bill@source_svr

where source_svr is the IP address or hostname of the VTS server where the remote export jobis originating. To specify multiple servers, use wildcard characters in the specified IP addressor hostname, or specify a list of servers separated by spaces.

Also, if the following line is listed in the file, be sure to remove it:

DenyUsers bill

6. Check the SSH connection, if you configured SSH.a. At the command prompt, log in.

b. Become bill:

su - bill

c. At the command prompt, enter ssh user@server uptime. For example, on Server B,enter ssh bill@server_b uptime.

The first time you enter an ssh command, a message similar to the following isdisplayed:

The authenticity of host 'server_name (IP_addr)' can't be

established.

RSA key fingerprint is

5f:10:3c:47:78:8f:e3:28:9d:ab:6b:34:ed:d1:e4:08.

Are you sure you want to continue connecting (yes/no)?

Enter yes.

d. Repeat these steps on each VTS server.

Note SSH can be setup for one direction or multiple directions. If multiple directions areconfigured, these steps should be executed from each direction.


Configuring AutoCopyNote A default configuration file is defined for each VTS server. To override the default settings, you

must define settings as described below.

To modify the VTS configuration file to configure AutoCopy

Requires the Edit Configuration File access right

1. Enable Data Replication licensing by entering the key on the Manage System Licenses page(click Configuration > System on the navigation pane and then click Manage SystemLicenses).

2. Click Configuration > Systemon the navigation pane.

3. Click Edit Configuration File.

4. Add the following parameters at the bottom of the file that is displayed:

Parameter Description Values

autocopy_enable Enables AutoCopy. This parameter isrequired.

Default value: NO

YES or NO

autocopy_pools Specifies the pools to monitor foractivity; virtual tapes in these poolsare copied after activity is detected.This parameter is required.

List of pool names,separated by spaces

autocopy_target_poolname

Specifies the target of the copyoperation for the pool specified bypoolname. Specify this parameter foreach pool listed by the autocopy_pools parameter.

You can set this parameter to atarget VTS system name; in this case,the pool is copied to the same pathon the target server. Ensure that anidentically named vault exists on thetarget system. The pool itself does

VTS system name, suchas server42

or, VTS system namefollowed by the path tothe pool, using a colonto separate them, as inserver42:/VAULT00/PO-OL1



not need to exist on the targetserver; it will be created, ifnecessary.

You can also set this parameter to avault and server, which defines thetarget path on the server.

You can set this parameter to a poolon a target VTS server; in this case,VTS determines the vault in whichthe pool resides on the targetsystem.

In all cases, ensure that no virtualtape name on the target systemmatches the name of any virtualtapes to be copied (they will beoverwritten). Also, the vaults on theoriginating and target VTS systemscannot reside in the same GFS filesystem, if GFS is used.

You can omit this parameter and setthe autocopy_target_ANYPOOLparameter to specify the target forall pools.

autocopy_target_ANYPOOL

Specifies the target of the copyoperation for all pools set byautocopy_pools. Specify thisparameter if you do not set theautocopy_target_poolnameparameter for each pool inautocopy_pools. See details abouthow to set this parameter in thedescription of autocopy_target_poolname.

VTS system name

or, vault on a VTSsystem, such as/VAULT00/server1

or, pool on a targetsystem, such asserver1:pool1



rep_enable Enables AutoCopy for virtual tapes inVTLs.

Default value: NO

YES or NO

rep_delay Specifies the time to wait (inseconds) before starting to copy data,for virtual tapes in VTLs. This is anoptional parameter that provides adelay to the host so that it can issuea mount for verification. When amount request is received, anyrunning AutoCopy operation for thevirtual tape is terminated and thepartially copied data is removedfrom the remote system.

0 - 86400

rep_bwlimit Specifies the maximum bandwidth (inthousands of bytes per second) to beused for each AutoCopy operation, forvirtual tapes in VTLs. If set togreater than 0, the approximatebandwidth used for the copy will belimited to the value specified.

Integer

Here is an example configuration:

autocopy_enable='YES'

rep_enable='YES'

autocopy_pools='VTS001 VTS003 VTS004'

autocopy_target_ANYPOOL='VTS-DR'

rep_delay='60'

rep_bwlimit='100'

Or:

autocopy_enable='YES'

rep_enable='YES'

autocopy_pools='DR1 DR2'


autocopy_target_DR1='SVR08'

autocopy_target_DR2='SVR08:/VAULT00/DR2_AU'

5. Click SAVE.

6. Restart the TapeServer process on the Manage System Tasks page.

Configuring Instant DRYou can manually replicate data using an Instant DR jobset, or you can automatically replicate datathrough the use of EMS.

Manually replicating a virtual tape using Instant DRTo manually replicate data using Instant DR, you must define a jobset. Each jobset can back up one ormore virtual tapes. Within each jobset, the synchronization tasks are serialized. This means that twotasks cannot run at the same time. However, you can dispatch separate jobsets, one right afteranother, to run multiple synchronization tasks simultaneously, though whether you can do thisdepends on the performance capabilities of your host server resources.

Each jobset contains entries that identify virtual tapes to process. A virtual tape is identified byvault, pool, and virtual tape name. The destination name of the virtual tape on the remote VTSserver can be the same as the source or different, and it is referred to as a target. In a simplescenario, you can synchronize virtual tapes to the same target names on the remote system. Also,each jobset can specify many targets, or you can have a separate jobset for each target.

On the Virtual Media - Instant DR page, a job history log is maintained. You can select an existingbackup set for execution or create a new backup set. You can also dispatch backup jobs.

Note Before beginning the following procedure, verify that the instant dr option is available fromthe window drop-down list on the Configure Tapes and Pools page. If this option is notavailable, the menu_InstantDR parameter must be set to YES in the VTS configuration file.Edit the configuration file by clicking Supervisor Functions on the navigation pane and thenclicking Edit Configuration File. Or, you may need to contact HP Global NonStop SolutionCenter (GNSC) if Instant DR is not enabled and configured.

To create an Instant DR jobset

Requires the Virtual Tape Instant DR access right

1. Click Administration > Virtual Tapes on the navigation pane.

2. Click the Advanced Media Actions link in the upper right corner of the page.


3. Select instant dr from the window drop-down list at the top of the page.

4. Click NEW in the Select Backup Set section of the page.

5. In the Enter new job name field, type the name of the jobset.

6. Click SUBMIT to continue. The following page is displayed:

7. In the Backup target system field, type the name or IP address of the system to receive thebackup.

8. In the Directory field, type the full path to the target vault (in UNIX notation). The path mustbegin with the vault where the backup will be made. The remainder of the string is specific toyour environment.


9. Select the Use Secure Transfer checkbox if SSH is configured on the VTS systems and youwant to encrypt the information being transmitted. This transfer method is not necessary ifthe connection between the VTS systems is secure or in a trusted environment. The encryptionprocess used in a secure transfer might cause some degradation in the data transfer rate.

10. Select the All Files checkbox if you want to send all files in the job to the remote system. Ifyou do not select this checkbox, only the newest virtual tape (determined by the filetimestamps) is transmitted.

Note All virtual tapes within the selected target must be available to be opened andtransmitted when the job is executed.

11. Enter the information for the jobset in the vault, pool, cartridge, and target name fields.Consider the following information when specifying these values:

l The vault, pool, and cartridge fields define the source of the backup. The target namefield specifies the name of the virtual tape on the target server.

l Specify the vault and pool names exactly as they are on your VTS system. The cartridge(virtual tape) and target names can be different. Example:/VAULT01/LIB01

l Specify a single = in any of the fields to specify the same value as the one directlyabove that value (previous line, same column). Specify == or * in the pool field toindicate the same pool as referenced in the source entry, such as /VAULT01/==. Youcan specify == for the target name, which indicates to use the same name as the virtualtape you are synchronizing.

l Instant DR is designed to connect to remote disaster recover sites over a connectionthat is much slower than the connection to your host server or the local area network.It is important to configure Instant DR in a way that maximizes your bandwidth. It isrecommended to use a wildcard for your virtual tape name, such as ARC*. The targetname is the target file name, such as ARCMASTR. Also, you can reduce the amount ofdata sent over the connection to the remote site by using a common target name for allvirtual tapes in a pool. Because backup data sets change little from day to day, onlychanges are sent to the remote site, thereby minimizing bandwidth.

l Keep the following in mind regarding the target name: If a new generation of a backupis done on consecutive days, you might rotate through a group of virtual tapes for eachbackup on each day and retain previous versions online for several days. The virtualtape you want to synchronize would be the one most recently created. Each of thesevirtual tapes has been generated from the same backup task such that some of the dataremains the same from day to day, and some have changed. If the virtual tapes involvedare named ABC001, ABC002, ABC003, you can use an arbitrary name such as ABCABC togive to the virtual tape on the remote site.


Do this by creating three lines in the jobset. If these virtual tapes are in the same pool,you only need to specify vault and pool once and use = for these items on the secondand third lines. On each line, specify the source virtual tape name. Specify ABCABC fortarget name on the first line and then specify = on the last two lines.

Alternately, you can use the wildcard shortcut by creating a one-line jobset with thevalue ABC* for the virtual tape name, assuming ABC* does not identify more virtualtapes than the ones you are working with. The asterisk is the only wildcard characteraccepted and can be used only in the cartridge field. It can appear anywhere in thename (before, after, or in the middle). It can also appear by itself to designate allvirtual tapes in the pool. If the All Files checkbox is not selected, VTS finds the virtualtape identified with a wildcard that has most recently been modified. In this case, itmakes sense to specifically identify the target virtual tape name instead of using ==.

If the All Files checkbox is selected, the opposite is true. It is unlikely that you wouldwant multiple asterisk-identified source files backed up to the same destination virtualtape name. In this case, use == in the target field.

Also, click DEL for any blank rows in the Job Set section of the page.

12. Click SAVE.

To manually backup data to the remote site

Requires the Virtual Tape Instant DR access right

1. Click Administration > Virtual Tapes on the navigation pane.

2. Click the Advanced Media Actions link in the upper right corner of the page.

3. Select instant dr from the window drop-down list at the top of the page.

4. Select the jobset to run.


5. Click DISPATCH at the bottom of the page to start the Instant DR process and to display themain Instant DR page.

You can monitor the process in the Job History box, which shows a one-line summary of the jobsetsthat are running and those that are complete. Click REFRESH until the Job History indicates finished.The virtual tape is available on the remote VTS server until it is needed or until the process runsagain and updates it. To display complete job log information on the process, click §.

Automatically replicating a virtual tape using Instant DRYou can initiate an Instant DR jobset by configuring the NonStop server to send an EMS message toVTS. This automates the Instant DR process. VTS parses the message and executes the specifiedInstant DR jobset. You can configure the NonStop server by defining a file utility program (FUP) callor by creating a TACL macro.

To use a file utility program (FUP) call

You can issue a simple FUP call to copy the contents of a text file to the $0 process. Complete thefollowing steps:

1. Create a text file named IDRTEXT1 on the NonStop server that contains the following line:

VTSPolicy IDR idrjobname1

where idrjobname1 is the name of the Instant DR job defined in VTS. Note that this text is casesensitive.

2. From Batchcom or within an existing backup script, run the following command:

FUP COPY IDRTEXT1, $0

This send the contents of the IDRTEXT1 file to the EMS collector.

To use a TACL macro in obey script

On the NonStop server, you can create an obey script that includes a TACL macro that communicateswith the VTS server through EMS. In the script file, add the commands specified below. To initiatethe script, run the script using the obey command, add the lines to the end of an existing script, orschedule the script to run from Batchcom.

#SET collector $0#SET evt_num number#SET action -1


#SET emphasis -1#SET evt_text VTSPolicy IDR idrjobname

Here is an explanation of the lines:

#SET collector $0 — Refers to the EMS collector to which to send the message. Change collector tothe name of the collector in the EMS configuration settings on VTS.

#SET evt_num number— Assigns a number to the event.

#SET action -1 — Refers to the way the message is displayed in an EMS viewer, such as ViewPoint. Inthis case, it is inverse text until acknowledged.

#SET emphasis -1 — Refers to the way the message is displayed in an EMS viewer, such asViewPoint. In this case, it is normal text.

#SET evt_text VTSPolicy IDR idrjobname— Specifies the message to be sent to the EMS collector.Replace idrjobname with the name of the Instant DR job in VTS.

Add these lines to the end of an existing obey script or schedule it from Batchcom.

When the script runs, the following is sent in the EMS message:

#PUSH evt_x evt_error req_error req_read req_prompt#PUSH action_id collector#LOAD /LOADED evt_x/ $system.zspidef.zemstacl#LOAD /LOADED evt_x/ $system.zspidef.zspitacl#LOAD /LOADED evt_x/ $system.zspidef.ztactacl#LOAD /LOADED evt_x/ $system.zspidef.ztaptacl#DEF evt_buf STRUCT BEGIN BYTE b(1:3000); END;#SET collector $0#SET action_id 0#SET evt_error [#REQUESTER /WAIT/ READ [collector] req_error req_read req_prompt]#PUSH evt_num action emphasis evt_text text_len#SET evt_num number#SET action -1#SET emphasis -1#SET evt_text VTSPolicy IDR idrjobname#SET text_len#SET evt_error [#EMSINIT evt_buf [ZEMS^VALÊXTERNAL^SSID] [evt_num]ZEMS^TKN^TEXT [#charcount evt_text] [evt_text]]#SET evt_error [#SSPUT evt_buf ZEMS^TKNÊMPHASIS [ZSPI^VAL^TRUE]]#SET evt_error [#SSPUT evt_buf ZEMS^TKNÂCTION^NEEDED [ZSPI^VAL^TRUE]]#APPENDV req_prompt evt_buf

41

4SCSI-to-Fibre Channel Adapter Upgrade

This chapter provides instructions to replace one or more SCSI cards with the same number of VTS-supported Fibre Channel cards on the following VTS models:

l VT5900-E, on the HP ProLiant DL385 G2

l VT5900-H, on the HP ProLiant DL385 G5

Refer to "Upgrading a SCSI Adapter to a Fibre Channel Adapter" on page 63 if you need to upgradelegacy hardware.

To replace SCSI cards with Fibre Channel cards and reconfigure VTS

Requires the View/Manage Configuration access right

1. Delete any VTDs or VTLs that use the ports that are being converted to Fibre Channel. See theonline help for instructions.

2. Switch all ports to Physical (Tape) mode and block startup.a. On the VTS web interface, click Configuration > Manage Virtual Devices on the

navigation pane.

b. When prompted, enter the login credentials.

c. Write down the current configuration.

d. Select physical for all ports and then click Submit. Confirm to reboot the server.

e. Click Administration > System Tasks on the navigation pane.

f. Click Block TapeServer Startup on the Manage System Tasks page.

3. Unmount all vaults, stop the Process Multi-Function (PMF) on the NonStop server, and shutdown VTS.

a. From a terminal window on VTS, log in.

b. Become root:

su -


c. Use the umount /VAULTxx command (where xx is the vault number) to unmount allvaults. Repeat this command for each vault on the system until all vaults areunmounted.

d. Verify that all vaults are unmounted by typing mount in the VTS terminal window.There should be no vaults mounted.

e. From the terminal window on VTS, open the /etc/fstab file. Use a text editor tocomment out all vaults in the /etc/fstab file by placing a # symbol before eachLABEL=/VAULT line (for example, #LABEL=/VAULT01). Repeat until all vaults arecommented out.

f. Save all changes and exit the editor.

g. From the NonStop server, stop all virtual tape drives using the SCF STOP PMFname

command.

h. Power down all VTS SCSI converters using the switch on the rear of each unit.

i. From a terminal window on VTS, enter shutdown now.

4. Remove the SCSI card(s) and install the Fibre Channel card(s).a. From the rear of the HP ProLiant DL385 G2 server, mark each SCSI cable with the port

position to which it is attached. This will make it easier to reattach them to the correctSCSI ports later.

b. Disconnect the ProLiant power cords as a precaution. Disconnect all SCSI cables fromthe SCSI adapters for easier access to the adapter cards.

c. If the HP ProLiant DL385 G2 is mounted in a rack, loosen the front pull tabs and slidethe server out so that you can open the top cover. Do not remove the server from therails. If there is a stabilizer foot, extend it so the enclosure does not tip forward.

d. Open the ProLiant DL385 G2 top cover, remove it, and set it aside.

e. Look inside the ProLiant DL385 G2 server to the back right-hand side where a pluggablemodule, called the PCI Riser cage, houses the SCSI and Fibre Channel adapters. You willsee a two round blue quick-release pull tabs that you need to open. Once loose, graspthe PCI Riser cage and pull up to remove it from the DL385 G2 chassis. Refer to thediagrams on top of the PCI Riser cage if you have any questions about its removal. Setthe PCI Riser cage on a flat surface that allows ample access to the side of the modulewhere the adapter cards can be accessed. Note the blue tabs or pull tabs that alloweach adapter to be removed from its slot.

f. Remove SCSI cards from the server; slots 5 and 4 contain SCSI cards.

The following order of SCSI card removal must be followed:

1. Remove the SCSI card in slot 5 and install the first Fibre Channel card in slot 5.

SCSI-to-Fibre Channel Adapter Upgrade | 43

2. Remove the SCSI card in slot 4 and install the second Fibre Channel card in slot 4, ifnecessary.

Here is a snapshot of the SCSI card after it is removed:

g. After you install the Fibre Channel upgrade cards in the appropriate slots, make surethe blue clips are firmly seated and locked in place on each slot. Then, re-install the PCIRiser cage in the DL385 G2 chassis. Once aligned, firmly press the module into place.Re-tighten the two blue pull tabs on the PCI Riser cage.

h. Place the top cover back in place and secure it. Slide the HP DL385 G2 ProLiant serverback into the rack and secure the two quick-disconnect screws on the front panel.

i. From the rear of the HP ProLiant DL385 G2 server, reconnect any remaining SCSIcables to the same ports where they were originally connected, if necessary. Becauseyou removed one or more SCSI cards, you will have extra, unused SCSI cables.Reconnect the power cords.

5. Restart VTS.a. Power on the ProLiant server by pushing the power button on the front panel. The

restart process begins and is complete when the screen displays a login prompt.


b. Power on all of the SCSI converters using the switch on the rear of each unit. Dependingon how many SCSI cards were removed from the ProLiant server, some converter portsor entire units may no longer be used.

6. Configure the remaining SCSI port(s) with the original settings.a. On the VTS web interface, click Configuration > Manage Virtual Devices on the

navigation pane.

b. If prompted, enter the login credentials.

c. For the SCSI ports, set the ports to virtual or physical according to the settings thatwere recorded in step 2c.

d. Click Submit.

7. Configure the new Fibre Channel port(s) as virtual devices (targets). For each port that youwish to configure for use as a virtual tape drive, complete these steps:

a. Click Configuration > Manage Virtual Devices on the navigation pane.

b. If prompted, enter the login credentials.

c. Starting at the highest numbered port, configure the Fibre Channel ports as virtualdevices by selecting virtual for the port(s).

You cannot skip a Fibre Channel port. For example, you cannot set ports 15, 14, and 12to virtual, leaving port 13 as physical (if the checkbox is not selected, it defaults tophysical).

As a reminder, here are the slot-to-port relationships on the VT5900-E (HP ProLiantDL385 G2) and VT5900-H (HP ProLiant DL385 G5):

PCI Slot Bus Number Card Type Virtual Tape Name

1 A N/A (P400 controller card)

1 B N/A (P400 controller card)

2 A 4 4G Fibre Fibre

2 B 5 4G Fibre Fibre

3 A N/A (left open for P800controller card)

3 B N/A (left open for P800

SCSI-to-Fibre Channel Adapter Upgrade | 45

PCI Slot Bus Number Card Type Virtual Tape Name

controller card)

4 A 0 2G Fibre $VTAPE00

4 B 1 2G Fibre $VTAPE01

5 A 2 2G Fibre $VTAPE02

5 B 3 2G Fibre $VTAPE03

d. Click Submit. Confirm to reboot the server.

8. Use the VTS web interface to reconfigure a VTD.

After the Fibre Channel ports are configured as virtual devices, the final step in this process isto reconfigure the VTDs. VTDs originally set up as SCSI need to be edited for use on a FibreChannel port.

Refer to the steps documented in the online help. When changing the properties, change theTarget from 5 to 0 from the drop-down box. Repeat the steps for each VTD that needs to beupdated.

9. When the startup process is complete, open a terminal window on VTS and log in. Then, entersu - to become root. Using a text editor, remove the lines that were commented out in step 3(remove the # sign in front of each vault, such as #LABEL=/VAULT01 becomesLABEL=/VAULT01). Do this for all vaults.

10. Save all changes and exit the editor.

11. Reboot VTS.

46 | Virtual TapeServerSupplemental Installation Guide

47

5Hardware Information for Legacy Installations

This chapter describes the hardware in older Virtual TapeServer (VTS) installations and that issupported in an upgraded environment. It also provides cabling and Fibre Channel upgradeprocedures for the old hardware.

Hardware overviewFor VTS installations that are upgrading to 8.0, the following hardware may be installed.

ServersOne of the following VTS server modules was installed:

l VT5900-A was built on the HP ProLiant DL585 G1 server

l VT5900-B and VT5900-C were built on the HP ProLiant DL380 G4 server

l VT5900-E and VT5900-G were built on an HP ProLiant DL385 G2 server

l VT5900-H was built on the HP ProLiant DL385 G5 server

l VT5900-J was built on the HP ProLiant DL385 G5 server

l VT5900-K and VT5900-O were built on the HP ProLiant DL185 G5 server

l VT5900-L was built on the HP ProLiant DL380 G6 server

If you purchased the VT5900-SA for use with the VT5900-K or VT5900-L, refer to the VirtualTapeServer SCSI-to-FC Adapter Quick Setup Guide and User Manual for installation and configurationinformation.

SCSI convertersEach SCSI converter converts high-voltage differential (HVD) Ultra160/SCSI-3 to low-voltagedifferential (LVD) Ultra-2 SCSI. It provides up to four converter circuits.


Internal storageIf the VT5900-C, VT5900-E, VT5900-G, VT5900-H, VT5900-J, VT5900-K, or VT5900-O was purchased,additional internal storage may have been purchased for storing virtual tapes. The followingadditional internal storage models were available:

l VT5904-A, which provided one internal disk drive of 146GB storage space

l VT5904, which provided six internal disk drives of 146GB each

l VT5904-B, which provided one internal disk drive of 300GB

l VT5904-E, which provided eight internal disk drives, each with 146GB of storage capacity

l VT5904-H, which provided eight 300GB internal disks for the VT5900-H

l VT5900-6TB, which provided six 1TB internal disks for the VT5900-K

l Six 2TB disks may have been added to the VT5900-O if six 1TB or six 2TB internal disks wereprovided

External disk storageIf VTS model VT5900-A, VT5900-C, VT5900-E, VT5900-G, or VT5900-H is installed, the followinghardware may have been installed for external disk storage.

l VT5915, which is built on the StorageWorks MSA 1500cs. It provides one controller shelf andone MSA 20 disk shelf, and it includes dual controllers, each of which provides a single FibreChannel port. The VT5915 also includes 12 750GB 7,200rpm SATA disk drives.

l VT5916, which is an MSA 20 add-on enclosure and is available if additional storage is neededafter purchasing and installing the VT5915. It includes 12 750GB 7,200rpm SATA disk drives.You can install up to three of these storage arrays per VT5915.

l VT5917, which is an MSA 2000 that provides 12TB. This is the controller and shipped with theVT5900-J.

l VT5918, which is an MSA 2000 that provides 12TB. Up to three of these may be installed withthe VT5917 and VT5900-J.

l VT5905 or VT5905-B, which are built on the StorageWorks MSA 1000 and provide a built-in 8-port Fibre Channel switch. The VT5905 provides 14 hard disk bays, and each hard diskprovides 146GB of storage at 10,000rpm. Each hard drive in the VT5905-B provides 300GBdisks.

l VT5906 or VT5906-B, which are built on the StorageWorks Modular 4314 and available ifadditional storage was needed after purchasing and installing the VT5905 or VT5905-B. Up totwo of these can be installed per VT5905 or VT5905-B. The VT5906 provides 14 hard disk bays,and each hard disk provides 146GB of storage. The VT5906-B provides 300GB disks.

Hardware Information for Legacy Installations | 49

l VT5930 controller, which is built on the P2000 MSA and has 12 2TB drives and up to threeVT5931 expansion chassis (P2000 MSA), each with 12 2TB drives; maximum capacity per P2000system is 96TB.

Fibre Channel upgrade cardTo replace a SCSI card with a Fibre Channel card on an HP ProLiant server, the VT5900-FCU mayhave been purchased:

This Fibre Channel upgrade card is a 2 Gbps, dual-port, 64-Bit/133 MHz, PCI-X-to-Fibre Channel hostbus adapter (HBA).

Cabling and connecting VTSCabling for the various VTS models is described in the following sections. Here is a summary of eachmodel’s configuration:

VTS Model Hardware Height # ofSCSI Ports

# of FCPorts

Optical orMagnetic Drives

VT5900-A DL585 G1 4U 12 4 CD

VT5900-B DL380 G4 2U 4(limited to 2for virtualdrives)

0 DVD/CD, DAT72

VT5900-C DL380 G4 2U 4 2 DVD/CD

VT5900-E DL385 G2 2U 4 2* (for SANconnectiononly)

DVD/CD

VT5900-G DL385 G2 2U 0 6 (2 forSANconnection,4 forVTDs)

DVD/CD


VTS Model Hardware Height # ofSCSI Ports

# of FCPorts

Optical orMagnetic Drives

VT5900-H DL385 G5 2U Up to 4 Up to 4 --

VT5900-J DL385 G5 2U 0 Up to 6 --

VT5900-K DL185 G5 2U 0 Up to 4 --

VT5900-L DL380 G6 2U 0 Up to 10 --

VT5900-O DL185 G5 2U 0 Up to 8 DVD/CD

Note For the most reliable service, use cables of the highest quality and shortest possible lengthbased on the location of the equipment in the data center.

Connecting the HP ProLiant DL585 G1 (VT5900-A)The VT5900-A is a 4U (7 inch) chassis and provides 12 SCSI port assignments, numbered 1-12. Thismodel includes two dual-channel Fibre Channel cards, providing up to four connections to externalstorage.

The recommended cable connection order for the SCSI converters attached to a VT5900-A is asfollows:

Connections from first SCSI converter

HVD Bus A HVD Bus B HVD Bus C HVD Bus D

To NonStop server To NonStop server To NonStop server To NonStop server

LVD Bus A LVD Bus B LVD Bus C LVD Bus D

To port 8A on VTSserver

To port 8B on VTSserver



Connections from second SCSI converter









Connections from third SCSI converter








Here is an illustration of the port numbers on the back of the VT5900-A (DL585 G1):

Here is an illustration of the HVD and LVD ports on the back of the SCSI converter:

Connecting the HP ProLiant DL380 G4 (VT5900-B and VT5900-C)The VT5900-B and VT5900-C were built on a 2U (3.5 inch) chassis and provides four SCSI ports,numbered 0-3. The VT5900-C has a dual-channel Fibre Channel card but no DAT72 drive and is shippedwith two (mirrored) 36GB SCSI drives, for use by the software only. Optional six SCSI disks (146GB or300GB) are available to give this unit internal storage. The six SCSI disks replace the two 36GBdrives. The VT5900-B model allows the use of all four SCSI ports for connecting virtual tape drives.The VT5900-C model allows the use of all four SCSI ports or the two Fibre Channel ports forconnecting virtual tape drives.

The recommended cable connection order for the SCSI converter attached to a VT5900-B and VT5900-C is as follows:


To NonStop server To NonStop server







Here is an illustration of the port numbers on the back of the DL380 G4:


Connecting the HP ProLiant DL385 G2 (VT5900-E)The VT5900-E is built on a 2U (3.5 inch) chassis and provides four SCSI ports, numbered 0-3. A dual-channel 4Gbps Fibre Channel card is also provided for connection to the SAN. This base model allowsthe use of all four SCSI ports for connecting virtual tape drives (no ports on the 4Gbps Fibre Channelcard can be used for virtual connections).

The recommended cable connection order for the SCSI converter attached to a base model of VT5900-E is as follows:








Note When attaching NonStop servers to the HVD ports, it is recommended that you attach to HVDport D then to HVD port C and then to HVD ports A and B if necessary. Also, note that you donot have to use all of the SCSI ports (or converter ports) for VTDs. You can use the ports asinitiators for legacy SCSI tape drives.


Here is an illustration of the slots on the back of the base model. If the P800 card is installed, it isplaced in slot 3 (below slot 4).


Note If you replace one or both of the SCSI cards with the 2Gbps Fibre Channel card(s), as describedin "SCSI-to-Fibre Channel Adapter Upgrade" on page 41, and you set any of the Fibre Channelports to target mode (to connect the port to a virtual tape drive), port numbering will change.After you replace the SCSI card(s) and reboot VTS, refer to the Manage Virtual Devices page inthe VTS web interface to see how the ports were renumbered. Contact your VTS service andsupport representative for help correlating port numbers to ports on the back of the VTSserver.

Connecting the HP ProLiant DL385 G2 (VT5900-G)The VT5900-G are built on a 2U (3.5 inch) chassis and provides up to four Fibre Channel ports,numbered 0-3. A dual-channel 4Gbps Fibre Channel card is also provided for connection to externalstorage (ports 4 and 5). This base model allows the use of four 2Gbps Fibre Channel ports forconnecting virtual tape drives (no ports on the 4Gbps Fibre Channel card can be used for virtualconnections).

Here is an illustration of the slots on the back of the base model. If the P800 card is installed, it isplaced in slot 3 (below slot 4).


Connecting to the HP ProLiant DL385 G5 (VT5900-H)Here is an illustration of the back of the VT5900-H (base model):

1. SCSI port (slot 4, port A)

2. SCSI port (slot 5, port A)

3. SCSI port (slot 5, port B)

4. SCSI port (slot 4, port B)

5. 4Gb FC port (slot 2, port A)

6. 4Gb FC port (slot 2, port B)

7. Power plugs

8. Ethernet port 2 (eth1)

9. Ethernet port 1 (eth0)

10. PS/2 port

11. PS/2 port

12. VGA port

13. USB ports

14. Serial port

15. iLO port

The SCSI card in slot 4 may be replaced by a dual-port 2Gb Fibre Channel card (VT5900-FCU).

If the host server requires an HVD SCSI connection, such as the NonStop S-series, you must connectthe VTS server to the SCSI converter, and then connect the SCSI converter to the host server. Here isan illustration of the HVD and LVD ports on the back of the SCSI converter:

For the best possible performance, use all 4Gb ports first and connect the external disk array orexternal tape device to a 4Gb port. Then, if necessary, connect external storage to the 2Gb ports,which may provide half the performance as the 4Gb ports.

To connect to host servers through the SCSI converter

Cable the host server to the SCSI converter and cable the SCSI converter to the VTS server:

1. Connect one end of an LVD cable to an LVD bus (port) on the SCSI converter. If cabling tomultiple host servers, the recommended cable connection order is as follows:

l HVD Bus A > To NonStop server

l HVD Bus B > To NonStop server

l HVD Bus C > To NonStop server


l HVD Bus D > To NonStop server

l LVD Bus A > To VTS slot 4A

l LVD Bus B > To VTS slot 4B

l LVD Bus C > To VTS slot 5A

l LVD Bus D > To VTS slot 5B

It is recommended that you attach to HVD bus D then to HVD bus C and then to HVD buses Aand B if necessary. Also, note that you do not have to use all of the SCSI buses (or converterports) for VTDs. You can use the ports as initiators for legacy SCSI tape drives.

2. Connect the other end of the LVD cable to the appropriate SCSI port on the VTS server.

3. Connect one end of an HVD cable to the appropriate HVD bus on the SCSI converter.

4. Connect the other end of the HVD cable to the host server.

5. If you are cabling multiple host servers to VTS, repeat these steps.

6. Note the port number used on the VTS server. Later, you will have to set this port to targetmode using the VTS web interface.

To connect to an external Fibre Channel disk array or tape device1. Connect one end of a Fibre optic cable to the Fibre Channel (FC) port on the VTS server.

2. Connect the other end of the cable to the external disk array or tape drive or library.

You may want to connect a second cable, to provide redundancy. You can connected to a separateSAN switch or RAID controllers on the server. See "Configure storage space and path failover" in theQuick Start Guide for more information.

To connect to external SCSI tape devices

If the drive or library requires an HVD SCSI connection, follow the steps in "To connect to hostservers through the SCSI converter" on page 54 to cable the drive or library to the SCSI converter.Then, follow these steps to cable the SCSI converter to the VTS server.

1. For a SCSI connection, connect one end of an LVD cable to a SCSI port on the VTS server. For aFibre Channel connection, connect one end of a Fibre optic cable to a Fibre Channel (FC) porton the VTS server.

2. Connect the other end of the cable to the external drive or library.

3. Repeat these steps for additional drives or libraries.

4. Note the port number(s) used on the VTS server. Later, you will have to set the port(s) tophysical mode using the VTS web interface.

To connect to the network

Connect one end of an Ethernet cable to Ethernet port 1, which is the port on the left (labeled in theserver diagram). Port 1 corresponds to eth0 in Linux, which is the VTS operating system. Connect the


other end of the cable to the LAN or WAN switch.

If Data Replication, AutoCopy, or Instant DR is licensed, you may also want to connect to Ethernetport 2, which is on the right (labeled in the server diagram). Port 2 corresponds to eth1.Performance on port 1 may be affected if you do not dedicate a port for replication traffic. Connectthe other end of the cable to the LAN or WAN switch. (You can also use port 2 for networkconfiguration, as described below.)

Note If a second subnet is not available, you cannot use Ethernet port 2 (eth1).

To connect the iLO port to the network1. Connect one end of an Ethernet cable to the iLO port.

2. Connect the other end of the cable to the LAN or WAN switch.

To connect to power1. Connect both power cords to the VTS server.

2. Plug each power cord into a grounded electrical outlet. It is recommended that the cords beconnected to separate electrical circuits for redundancy.

To connect for network configuration

To configure the server’s network settings, you can connect the VTS server to the network using oneof these options:

l Connect a computer to the server using a serial cable

l Connect a computer to the server using an Ethernet cable

l Connect to a monitor and keyboard

To connect using a serial cable:

1. Connect one end of a serial cable to one of the serial ports on the VTS server.

2. Connect the other end of the cable to a computer. (If the computer does not provide a serialport, you can use a serial-to-USB conversion cable.)

To connect using an Ethernet cable:

1. Connect one end of an Ethernet cable to port 2 (eth1).

2. Connect the other end of the cable to a computer.

3. Configure the Ethernet port on the computer to use 1.1.1.2 as its static IP address.

To connect to monitor and keyboard:

1. Connect one end of a VGA cable into the 15-pin VGA port on the VTS server.

2. Connect the other end of the cable into the monitor or computer with terminal emulation.

3. If using a keyboard, connect it to a PS/2 or USB port on the VTS server.


Connecting to the HP ProLiant DL385 G5 (VT5900-J)Here is an illustration of the back of the VT5900-J:

1. 2Gb FC port (slot 4, portA)


3. 2Gb FC port (slot 5, portB)




7. Power plugs

8. Ethernet port 2

9. Ethernet port 1

10. PS/2 port

11. PS/2 port

12. VGA port

13. USB ports

14. Serial port

15. iLO port

As a best practice, use all 4Gb ports first and connect the external disk array or tape device to a 4Gbport. Then, if necessary, connect external storage to the 2Gb ports, which may provide half theperformance as the 4Gb ports.

To connect to the host server1. Connect one end of a Fibre optic cable to a Fibre Channel (FC) port on the VTS server.

2. Connect the other end of the cable to the host server.

3. If you are cabling multiple host servers to VTS, repeat these steps for each host server.


To connect to an external disk array or tape device1. Connect one end of a Fibre optic cable to the Fibre Channel (FC) port on the VTS server.

2. Connect the other end of the cable to the external disk array.


You may want to connect a second cable, to provide redundancy. When using the VT5917, forexample, active/active failover can be configured.

To connect to external tape drives or libraries1. Connect one end of a Fibre optic cable to a Fibre Channel (FC) port on the VTS server.


3. Repeat these steps for additional drives or libraries.

4. Note the port number(s) used on the VTS server. Later, you will have to set the port(s) tophysical mode using the VTS web interface.


Connect one end of an Ethernet cable to Ethernet port 1. (Port 1 corresponds to eth0 in Linux.)Connect the other end of the cable to the LAN or WAN switch.

If Instant DR or AutoCopy is licensed, you may also want to connect to Ethernet port 2. (Port 2corresponds to eth1.) Performance on port 1 may be affected if you do not dedicate a port to InstantDR or AutoCopy.


2. Plug each power cord into a grounded electrical outlet. It is recommended that the cords berouted to separate power sources for redundancy.

To connect to monitor, keyboard, and mouse1. Connect one end of a VGA cable into the 15-pin VGA port on the VTS server.



4. If using a mouse, connect it to a PS/2 or USB port on the VTS server.

To connect the iLO port to the network1. Connect one end of an Ethernet cable to the iLO port.



Connecting to the HP ProLiant DL185 G5 (VT5900-K)Note The VT5900-O that ships with version 8.0 is also built on the DL185 G5. Refer to the 8.0 Quick

Start Guide for connection information for this server.

Here is an illustration of the back of the VT5900-K:

1. Power plugs

2. PS/2 port

3. PS/2 port

4. Serial port

5. FC port (slot 3, port A)

6. FC port (slot 3, port B)

7. Ethernet ports

8. USB ports

9. Mgmt port

10. VGA port

11. FC port (slot 2, port A)

12. FC port (slot 2, port B)

The second 4Gb FC card (VT5900-FC4) shown in slot 2 is optional and may not be installed.


Connecting to the HP ProLiant DL380 G6 (VT5900-L)Note The VT5900-P that ships with version 8.0 is also built on the DL380 G6. Refer to the 8.0 Quick

Start Guide for connection information for this server.

Here is an illustration of the back of the VT5900-L (base model):

1. 4Gb FC ports (slot 2)


3. Power plugs


5. Ethernet ports 4 and 3

6. iLO port

7. Serial port

8. PS/2 ports

9. Ethernet ports 2 and 1

10. VGA port

11. USB ports

An FC card (VT5900-FC4) may be installed in slot 5 (above slot 6). A FC card (VT5900-FC4) may alsobe installed in slot 1 (above the fan and power plug on the left), replacing the P800 card that isinstalled in the base model.

Connecting to the HP ProLiant DL185 G5 (VT5900-O)Here is an illustration of the back of the VT5900-O:

1. Power plugs

2. PS/2 port

3. PS/2 port

4. Serial port

5. Ethernet ports

6. USB ports

7. Mgmt port

8. VGA port

9. FC ports (slot 1)


The second FC card shown in slot 2 is optional and may not be installed. If installed, it may provideup to four ports instead of the two shown.

To connect to the host server

When connecting host servers over Fibre Channel to the VTS server, use one port per host server, ifpossible. If connecting more than one host server through a switch, ensure that the host servers areof the same type. Each Fibre Channel port on the VTS server is configured to emulate one host typeonly. Host servers of differing types must be connected to separate ports. Also, ensure proper zoningis configured.

1. Connect one end of a Fibre optic cable to a Fibre Channel (FC) port on the VTS server.

2. Connect the other end of the cable to the host server.


To connect to an external tape device1. Connect one end of a Fibre optic cable to a Fibre Channel (FC) port on the VTS server.


3. Note the port number used on the VTS server. Later, you will have to set the port to physicalmode using the VTS web interface.


Connect one end of an Ethernet cable to Ethernet port 1, which is the port on the left (labeled in theserver diagram). Port 1 corresponds to eth0 in Linux, which is the VTS operating system. Connect theother end of the cable to the LAN or WAN switch.

If Data Replication, AutoCopy, or Instant DR is licensed, you may also want to connect to Ethernetport 2, which is on the right (labeled in the server diagram). Port 2 corresponds to eth1.Performance on port 1 may be affected if you do not dedicate a port for replication traffic. Connectthe other end of the cable to the LAN or WAN switch. (You can also use port 2 for networkconfiguration, as described below.)

Note If a second subnet is not available, you cannot use Ethernet port 2 (eth1).

To connect to the management port for Lights-Out 100 support1. Connect one end of an Ethernet cable to the Mgmt port.



2. Plug each power cord into a grounded electrical outlet. It is recommended that the cords beconnected to separate electrical circuits for redundancy.


To connect for network configuration

To configure the server’s network settings, you can connect the VTS server to the network using oneof these options:

l Connect a computer to the server using a serial cable

l Connect a computer to the server using an Ethernet cable

l Connect to a monitor and keyboard

To connect using a serial cable:

1. Connect one end of a serial cable to one of the serial ports on the VTS server.

2. Connect the other end of the cable to a computer. (If the computer does not provide a serialport, you can use a serial-to-USB conversion cable.)

To connect using an Ethernet cable:

1. Connect one end of an Ethernet cable to port 2 (eth1).

2. Connect the other end of the cable to a computer.

3. Configure the Ethernet port on the computer to use 1.1.1.2 as its static IP address.

To connect to monitor and keyboard:

1. Connect one end of a VGA cable into the 15-pin VGA port on the VTS server.



To connect to the DVD/CD-ROM drive1. Connect one end of the USB cable to the DVD/CD-ROM drive.

2. Connect the other end of the cable to one of the USB ports on the back of the VTS server.

Modifying virtual tape connectionsWhen modifying a virtual tape connection in VTS, you must define a virtual tape’s properties. Referto the Virtual TapeServer Configuration Guide for an explanation of the properties and instructions formodifying them. The following provides information needed when modifying the port ID for virtualtape connections on 6.03.39 and 6.03.41 hardware.


To determine the port ID, you must find the PCI slot number on the back of the VTS server modulewhere the SCSI or Fibre Channel cable connects from the card to the target. Labels indicate the portnumber for each port. For legacy hardware, the port IDs are as follows:

DL380 G4 (VT5900-B, VT5900-C)

Port Bus #

3 A 0

3 B 1

2 A 2

2 B 3

1 A 4

1 B 5

Upgrading a SCSI Adapter to a Fibre Channel Adapter"SCSI-to-Fibre Channel Adapter Upgrade" on page 41 provides instructions to replace one or moreSCSI cards with the same number of VTS-supported Fibre Channel cards. Instructions for the 6.03.42models are included in that appendix; refer to it for the steps required to replace a SCSI card. Thissection describes the specific step needed for the following VTS models:

l VT5900-A, on the HP ProLiant DL585 G1

l VT5900-B and VT5900-C, on the HP ProLiant DL380 G4

On the HP ProLiant DL585 G1 (VT5900-A)After completing step 3 on 41, remove the SCSI card(s) and install the Fibre Channel card(s), asfollows:

1. From the rear of the HP ProLiant DL585 server, mark each SCSI cable with the port position towhich it is attached. This will make it easier to reattach them to the correct SCSI ports later.

2. Disconnect the ProLiant power cords as a precaution. Disconnect all SCSI cables from the SCSIadapters for easier access to the adapter cards.

3. If the HP ProLiant DL585 is mounted in a rack, loosen the front pull tabs and slide the serverout so that you can open the top cover. Do not remove the server from the rails. If there is astabilizer foot, extend it so the enclosure does not tip forward.

4. Open the ProLiant DL585 top cover, remove it, and set it aside.

5. Look inside the ProLiant DL585 server to the back where the SCSI and Fibre adapters arelocated. You will see a shipping bracket secured with a quick-disconnect pull tab that you need


to release to remove the shipping bracket. Once the shipping bracket is removed, you canaccess the blue tabs that lock and unlock the SCSI and Fibre Channel cards.

6. Remove SCSI cards from the server as follows:

Note This order must be followed or the upgrade will not work. Every HP ProLiant DL585server has SCSI and Fibre Channel cards in the same physical slots. A Fibre Channelcard is always in slots 5 and 6. You will see slot numbers on the chassis above eachslot. These numbers are visible on the inside and outside of the chassis.


a. Remove the SCSI card in slot 3 and install the first Fibre Channel card in slot 3.

b. Remove the SCSI card in slot 4 and install the second Fibre Channel card in slot 4, ifnecessary.

c. Remove the SCSI card in slot 2 and install the third Fibre Channel card in slot 2, ifnecessary.

d. Remove the SCSI card in slot 1 and install the fourth Fibre Channel card in slot 1, ifnecessary.

e. Remove the SCSI card in slot 7 and install the fifth Fibre Channel card in slot 7, ifnecessary.

f. Remove the SCSI card in slot 8 and install the sixth Fibre Channel card in slot 8, ifnecessary.



7. After you install all of the Fibre Channel upgrade cards in the appropriate slots, make sure theblue clips are firmly seated and locked in place on each slot. Then, re-install the shippingbracket and make sure the pull tab is secure.

8. Place the top cover back in place and secure it. Slide the HP DL585 ProLiant server back intothe rack and secure the two quick-disconnect screws on the front panel.

9. From the rear of the HP ProLiant DL585 server, reconnect any remaining SCSI cables to thesame ports where they were originally connected, if necessary. Because you removed one ormore SCSI cards, you will have several extra, unused SCSI cables. Reconnect the power cords.

Now, continue with step 5 on 43 and step 6 on page 44.

On the HP ProLiant DL380 G4 (VT5900-B and VT5900-C)After completing step 3 on 41, remove the SCSI card(s) and install the Fibre Channel card(s), asfollows:

1. From the rear of the HP ProLiant DL380 server, mark each SCSI cable with the port position towhich it is attached. This will make it easier to reattach them to the correct SCSI ports later.

2. Disconnect the ProLiant power cords as a precaution. Disconnect all SCSI cables from the SCSIadapters for easier access to the adapter cards.


3. If the HP ProLiant DL380 is mounted in a rack, loosen the front pull tabs and slide the serverout so that you can open the top cover. Do not remove the server from the rails. If there is astabilizer foot, extend it so the enclosure does not tip forward.

4. Open the ProLiant DL380 top cover, remove it, and set it aside.

5. Look inside the ProLiant DL380 server to the back right-hand side where a pluggable module,called the PCI Riser cage, houses the SCSI and Fibre adapters. You will see a two round bluequick-release pull tabs that you need to open. Once loose, grasp the PCI Riser cage and pull upto remove it from the DL380 chassis. Refer to the diagrams on top of the PCI Riser cage if youhave any questions about its removal. Set the PCI Riser cage on a flat surface that allowsample access to the side of the module where the adapter cards can be accessed. Note theblue tabs or pull tabs that allow each adapter to be removed from its slot.

6. Remove SCSI cards from the server as follows:

Note This order must be followed or the upgrade will not work. Every HP ProLiant DL380server has SCSI and Fibre Channel cards in the same physical slots.

A Fibre Channel card is always in slot 1, the bottom slot; there is no reason to remove thiscard. Slots 2 and 3 contain SCSI cards. A picture showing these slots follows:


a. Remove the SCSI card in slot 3 and install the first Fibre Channel card in slot 3.

b. Remove the SCSI card in slot 2 and install the second Fibre Channel card in slot 2, ifnecessary.



7. After you install all of the Fibre Channel upgrade cards in the appropriate slots, make sure theblue clips are firmly seated and locked in place on each slot. Then, re-install the PCI Riser cagein the DL380 chassis. Once aligned, firmly press the module into place. Re-tighten the two bluepull tabs on the PCI Riser cage.

8. Place the top cover back in place and secure it. Slide the HP DL380 ProLiant server back intothe rack and secure the two quick-disconnect screws on the front panel.

9. From the rear of the HP ProLiant DL380 server, reconnect any remaining SCSI cables to thesame ports where they were originally connected, if necessary. Because you removed one ormore SCSI cards, you will have extra, unused SCSI cables. Reconnect the power cords.

Now, continue with step 5 on 43 and step 6 on page 44.

For step 7c on 44, consider the following slot-to-port relationships on the HP ProLiant DL380 G4(VT5900-B and VT5900-C):

PCI-X Slot Bus Number Virtual Tape Name

3 A 0 $VTAPE00

3 B 1 $VTAPE01


PCI-X Slot Bus Number Virtual Tape Name

2 A 2 $VTAPE02

2 B 3 $VTAPE03

1 A 4 Fibre *

1 B 5 Fibre *

69

Index

A

addingSee also creating

AutoCopy

enabling 26

overview 26

parameters in configuration file 32

autocopy_enable parameter 32

autocopy_pools parameter 32

autocopy_target_anypool parameter 33

autocopy_target_poolname parameter 32

automating

Instant DR 39

B

backup management applications (BMAs),integration 15

backup schemes for Instant DR 35

C

cabling, connection order

VT5900-A 50

VT5900-B and VT5900-C 51

VT5900-E 52

VT5900-G 53

configuring

automated migration 16

enterprise integration 16

network and TCP/IP settings for roleswapping 28

SSH for remote export jobs 30

virtual tape connections for legacyhardware 62

connecting

VT5900-A 50

VT5900-B 51

VT5900-C 51

VT5900-E 52

VT5900-G 53

VT5900-H 52

VT5900-J 53

creatingSee also adding

backup scheme for Instant DR 35

E

ems_hsm_backup_notification parameter 21

enabling

AutoCopy 26, 32, 34

Instant DR 26, 35

external storage for legacy hardware 48

F

Fibre Channel upgrade

for legacy hardware 63

procedure 41

VT5900-A 63

VT5900-B and VT5900-C 65

VT5900-E 42


G

GFS

overview 1

GFS, installing 1

H

hardware overview, legacy models 47

hsm_backup_options parameter 17

hsm_backup_options_poolnameparameter 17

hsm_backup_pools parameter 17

hsm_backupset parameter 19

hsm_client parameter 19

hsm_enable parameter 16

hsm_erase_after_backup parameter 20

hsm_joblog_maxnum parameter 20

hsm_optfile parameter 18

hsm_optfile_pool parameter 18

hsm_policy parameter 18

hsm_pool parameter 17

hsm_product parameter 16

hsm_put_batch_size 18

hsm_restore_device parameter 17

hsm_restore_period parameter 21

hsm_schedule parameter 19

hsm_server parameter 17

hsm_subclient parameter 19

hsm_summary_limit parameter 20

I

installing GFS 1

Instant DR

automating 39

creating backup scheme 35

enabling 26

page 36

internal storage for legacy hardware 48

L

licensing

migration 23

M

menu_InstantDR parameter 35

migration 15

configuration parameters 16

licensing 23

MSA 1000 48

MSA 1500 48

O

overview

legacy hardware 47

R

rep_bwlimit parameter 34

rep_delay parameter 34

rep_enable parameter 34

role swapping

configuring network and TCP/IPsettings 28

S

SCSI-to-Fibre Channel upgrade, currentmodels 41

Index | 71

SCSI, upgrading to Fibre Channel for legacyhardware 63

SSH, configuring 30

T

typographical conventions v

V

Virtual Media

Instant DR page 36

virtual tape connections, configuring

for legacy hardware 62

VT5900-A, Fibre Channel upgrade 63

VT5900-B

Fibre Channel upgrade 65

overview 47

VT5900-C


overview 47

VT5900-E


overview 47

VT5900-G, overview 47

VT5900-H, overview 47

VT5900-J, overview 47

VT5905 48

VT5906 48

VT5915 48

VT5916 48

VTSPolicy

Instant DR 39


Documents

Virtual TapeServer 8.3 Supplemental Installation Guideh20628. · iii Contents Preface v Supportedreleaseversionupdates v Typographicalconventions v Relateddocumentation v 1InstallingGFS