Installation Guide HP Virtual TapeServer for NonStop Servers Part Number: 514105-001 Product Version: 6.04 © 2004 - 2008 Hewlett-Packard All rights reserved No part of this document may be copied in any form or by any means without prior written consent of HP. All drawings, schematics and artwork used in the manufacture of the products described herein are copyrighted.
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Typographical conventions . . . . . . . . . . . . . . . . . . .
Cabling to external tape resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCSI LVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HVD SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hard drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCSI controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi | Contents
Preface Welcome to the Virtual TapeServer Installation Guide. This guide provides installation and configuration information for Virtual TapeServer (VTS). VTS enables host systems to read from and write to an embedded or attached redundant array of independent disks (RAID). The virtual tape drive emulates the type of tape drive specified during the initial installation and setup process. About this guide The Virtual TapeServer Installation Guide is designed to help you attach and configure VTS.
Related documentation In addition to this installation guide, the following documentation is provided: • Virtual TapeServer Operations and Administration Guide, which describes how to use the VTS web interface to manage VTS. • Virtual TapeServer Release Notes, which provides information about system support, known issues, and other information about the current release.
Introduction Tape remains the most practical solution for removable storage, and it is often required by regulatory agencies to be archived and stored offsite. However, as the cost of commodity disk storage has decreased, many enterprises view disk-based backup solutions as a feasible alternative to tape-based backup.
hardware and tape media, automate backup and restore operations, and increase flexibility in managing backed-up data. The virtual environment The basic building blocks of VTS are vaults, pools, virtual tape drives, and virtual tapes. VTS can support multiple virtual tape drives that respond to tape commands just as a physical tape drive would. Virtual pools are organized into vaults, which correspond to areas of the file system that are configured according to user needs.
Overview of features The following VTS features enable you to simplify and streamline tape operations, reduce costs for storage, automate backup and restore operations, and increase flexibility in managing backed-up data: • Flexible and extendable, enabling you to create any number of virtual tape pools that “contain” any number of virtual tapes • Compatibility with Backup, Restore, and TMF • Compatibility with Mediacom and DSM/TC • Support for backup management applications, including IBM Tivoli Sto
• SecureVTS — Encrypts and decrypts backup data written on disk from one or more host servers. Compliance regulations and organizations highly recommend the encryption of valuable data; SecureVTS provides a robust encryption solution that deploys on existing hardware. Industry-standard 256-bit AES symmetric key encryption is used. Overview of the VTS web interface VTS is managed through a standard web browser interface.
EMS — Event Management Service, which starts the EMS distributor on the NonStop server by issuing a Tandem Advanced Command Language (TACL) command. The distributor notifies the VTS EMS service when an EMS message is posted on the NonStop server. VTS — Virtual TapeServer, which refers to the Virtual TapeServer engine and provides the core of VTS functionality. SecureVTS If SecureVTS is enabled, this section displays its status. Free Space Optional section that is shown by default.
• Imports and exports from and to physical drives • Instant DR operations The Virtual Media - Operation page is the homepage, though you can click Virtual Media on the navigation pane to display the Virtual Media - Operation page again. The refresh button at the top of the page enables you to update the information displayed on the Virtual Media page.
contents of the pool. Click the - symbol to collapse the pool. The colors have the following meaning: • Orange — Locked (mounted, Instant DR, migration, AutoCopy, export, or import) • Purple — Autoloading enabled • Red — Remotely addressed • Black — Available If you select an option from the window drop-down list, additional pages are available. You must have the corresponding right(s) to view the pages.
System Overview page When you click View Configurations on the navigation pane, the following page is displayed. The View/Manage Configuration access right is required to view this page. This page lists the virtual-to-physical mappings for the VTS system. It also lists the virtual, logical, and physical tapes that are available to be mapped.
Manage Tape Connections page This page enables you to access other pages to manage virtual tape connections, logical tapes, virtual tapes, and tape definitions. Click Manage Connections on the navigation pane to display this page. The View/Manage Configuration access right is required to view this page.
Supervisory Functions page Click Supervisor Functions on the navigation pane to display this page. The options displayed on this page are based on your access rights; at a minimum, the Supervisory Functions access right is required. Clicking a link on the Supervisory Functions page enables you to perform administrative operations, such as applying updates, editing the configuration file, rebooting the system, downloading files, starting and stopping processes, and examining log files.
Access Control page When you click Access Control on the navigation pane, the Access Control page is displayed. The System Access Controls or User Access Controls access right is required to view this page. If you have the System Access Controls right, this page enables you to grant or limit access to specific VTS functions by managing users and groups. Otherwise, this page enables you to change your password.
Factory Setup page If the Factory Setup option is available, you can click it to display the Factory Setup page: This page enables you to configure VTS and perform administrative functions, such as adding virtual tapes or backing up files. You must have authorized credentials to access this page.
Installation Summary and Checklist This chapter describes the hardware needed by Virtual TapeServer (VTS), the installation process, and the information you should prepare before beginning. Refer to subsequent chapters for details about each step. Hardware overview Before beginning the installation, it is important to identify the hardware involved in setting up the VTS system and the role that each component plays.
Servers Models VT5900-E and VT5900-G are built on an HP ProLiant DL385 G2 server; models VT5900-H and VT5900-J are built on an HP ProLiant DL385 G5: Two Fibre Channel cards are installed (for supporting VTDs) in model VT5900-G and VT5900-J. Two SCSI cards are installed in model VT5900-E and VT5900-H. Internal disk storage The VT5900-E, VT5900-G, VT5900-H, and VT5900-J models support optional internal storage (model VT5904-E) that can be used for storing backup data.
• VT5916, which is an MSA 20 add-on enclosure and is available if additional storage is needed after 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. • VT5905 or VT5905-B, which are built on the StorageWorks MSA 1000 and provide a builtin 8-port FC switch. The VT5905 provides 14 hard disk bays, and each hard disk provides 146GB of storage at 10,000rpm. Each hard drive in the VT5905-B provides 300GB disks.
Cables The following is a list of HP cables and their part numbers, which are provided by HP for VTS installations. Note These cables are provided if listed in the CPSA description for the PID. Cable Part Number S-series SCSI cable, 3 m (10 ft) 518-010W S-series SCSI cable, 7.6 m (25 ft) 518-025W S-series SCSI cable, 15.2 m (50 ft) 518-050W S-series SCSI cable, 22.
Overview of the VTS deployment To install and configure Virtual TapeServer (VTS), perform the following steps. You may want to review the Installation checklist on page 18 before beginning. Also, you should be familiar with the following concepts and tasks before installing VTS: • Know how to add, configure, and use tape devices in NonStop server environments with compression set to OFF. • Know how to add users in NonStop server operating system environments.
connections. See Configuring and Validating Virtual Tape Drives on page 47 for instructions. 10. Configure access control. It is recommended that you enable a closed system, which requires users to authenticate to access resources. You can also configure the default groups to set privileges for users assigned to the groups. See Configuring Access Control on page 59 for more information. 11. If Instant DR or AutoCopy is licensed, configure VTS to send EMS messages to the host server.
Cabling and Connecting VTS A critical part of installing Virtual TapeServer (VTS) is establishing the physical connection between the host server and VTS. Cabling and termination issues are the single largest contributor to an unsuccessful or delayed installation. Preparing and planning in advance for the right cables, lengths of cables, connectors, and terminators dramatically increases the chances of successful installation and simplifies any subsequent troubleshooting.
Cabling from NonStop S-series servers NonStop S-series servers use HVD SCSI to connect to disk and tape peripherals. The NonStop S-series server I/O controller uses a 68-pin high-density connector. Note See Cables on page 16 for a description of cables that may be provided by HP. VTS uses low voltage differential (LVD) SCSI, so conversion of the NonStop S-series HVD signal to LVD is required. To accomplish this task, VTS for NonStop S-series servers includes one or more 1U (1.
Checking SCSI termination All VTS SCSI ports are internally terminated. Check that appropriate termination is installed at the opposite end of the SCSI bus for all NonStop S-series servers and external SCSI storage devices. Note that some older NonStop servers, such as the S7000, require an in-line SCSI terminator. This pass-through device sits between the external SCSI connector of the PMF board on the NonStop and the cable that connects to the SCSI converter.
Cable connection order Cabling for the various VTS models is described in the following sections.
Here is an illustration of the slots on the back of the base model. If the P800 card is installed, it is placed in slot 3 (below slot 4). Here is an illustration of the HVD and LVD ports on the back of the SCSI converter: Note If you replace one or both of the SCSI cards with the 2Gb FC card(s), as described in SCSI-to-Fibre Channel Adapter Upgrade on page 141, and you set any of the FC ports to target mode (to connect the port to a virtual tape drive), bus numbering will change.
Cabling to external disk resources VTS supports optional connectivity to a wide variety of external SCSI or Fibre Channel (FC) storage solutions using any port that has not been reserved for a virtual tape drive. For FC-attached external resources, identify the connector type for the device end. Source FC cables with LC fiber connector for the VTS end and the necessary connector for the device end. Define a storage space on the disk array for use with the Linux operating system.
requirements, refer to the storage manufacturer's user manual for the SCSI-based external storage devices. To connect VTS to a SCSI-based external storage that uses an MD68 connector, use a cable with a male VHDCI connector on the VTS side and the appropriate (male or female) MD68 connector on the SCSI storage side. For connector specifics and termination requirements, refer to the user manual for the SCSI-based external storage devices.
The Device Mapper Multipath Enablement Kit (dm-multipath and devicemapper RPMs) is installed by default on the VTS server. You must download the latest version of the multipath.conf file, which is available here: http://h20000.www2.hp.com/bizsupport/TechSupport/ SoftwareIndex.
SCSI LVD LVD tape drives can be connected to any SCSI port on the VTS server module that has not been reserved for use as a virtual tape drive. The VTS server module uses a female VHDCI connector, so a cable with a male VHDCI is required. Depending on the type of tape drive, that end of the cable probably uses a male MD68 connector. Two drives can be daisy chained, and an LVD external terminator is required on the last drive in the chain.
Connecting to a SAN When defining LUNs on a storage array, start at LUN 0. Otherwise, the Fibre Channel interface in VTS might not recognize them correctly. Connecting power Plug the power cords into grounded electrical outlets; it is recommended that the cables be routed to separate power sources for redundancy. Powering up and down To power up 1. Press the power button located on the front panel of the VTS server module.
3. Execute the halt command by clicking Supervisor Tools on the navigation pane of the user interface and then clicking Halt the System. Allow the VTS server to completely shut down before proceeding. The VTS server’s console will indicate “System Halted”. 4. Press the power button located on the front panel of the VTS server module. The button light changes from green to yellow.
30 | Cabling and Connecting VTS
Configuring Network Settings By default, Virtual TapeServer (VTS) is configured to use Dynamic Host Configuration Protocol (DHCP). To change the network configuration, you must connect a monitor, keyboard, and mouse to VTS before powering it on. To change the default settings, use a console window and complete the following steps. Before making any changes, obtain a new IP address, netmask, gateway, and hostname that are appropriate for your site from the network administrator. 1. Log in as root.
4. Select the network device to modify (default is eth0) by double-clicking eth0 or eth1. Eth0 corresponds to port 1 on the back of the VTS server, and Eth1 corresponds to port 2. The Ethernet Device window is displayed: 5. Change the static IP settings, or select DHCP to apply the IP address. Then click OK to return to the Network Configuration window. 6. Click the DNS tab and enter the host name you want to assign to VTS, the IP address of your DNS server(s), and the domain. 7.
Installing GFS The Global File System (GFS) is an advanced feature that allows Linux servers to simultaneously read and write files on a single shared file system on a SAN. VTS is based on Linux, and GFS enables multiple VTS servers to access a shared set of pools and virtual tapes. The Event Management Service (EMS) can then automatically mount virtual tapes from the GFS pools as if they were separately mounted.
switch). Or, you can configure HP Integrated Lights-Out (iLO) to handle fencing. Refer to the following for more information about fencing: • Fencing overview — http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/ html/Cluster_Suite_Overview/s2-fencing-overview-CSO.html • Configuring fencing devices with Conga (luci and ricci) — http://www.redhat.com/docs/enUS/Red_Hat_Enterprise_Linux/5.2/html/Cluster_Administration/s1-config-fence-devicesconga-CA.
Complete the next four steps (steps 8-11) on only one server (node) that will be included in the cluster. It is recommended that you shutdown all nodes in the cluster other than the one used in these steps. If you are creating multiple vaults, you must also complete steps 8-11 for each GFS file system to be used for vault storage. 8. Choose your device(s) to be used for GFS. In the commands and output below, /dev/sde is used as an example device.
b. Create the volume group by entering the following: vgcreate gfsvg1 /dev/sde1 c. Create the logical volume by entering the following command. The -l 100%FREE argument creates a logical volume using the entire volume group. lvcreate -l 100%FREE -n lv1 gfsvg1 d. Enter the following command to confirm the physical volume: pvscan Here is an example of the output: 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 e.
Act PV VG Size PE Size Total PE Alloc PE / Size Free PE / Size VG UUID 1 17.14 GB 4.00 MB 4388 4388 / 17.14 GB 0 / 0 lm4cH7-4wgq-s1VR-VNwc-pFC6-i54u-h5tKxk h. Enter the following command to view details about the logical volume: lvdisplay Here is an example of the output: --- 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.
11. Start ricci and luci. For more information about these GFS services, refer to http://www.redhat.com/docs/ manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/s1-startluci-ricci-conga-CA.html. These services must be configured in the cluster before you can mount the newly created GFS volume. Complete the following steps to start the services. a. Make sure that the luci system has a proper /etc/hosts file.
• Enter each cluster member's name and root password, and click Submit. • Click the Cluster tab at top of the page. • Click Create a New Cluster. • Enter the same cluster name specified in step 10a. • Enter each system's fully qualified domain name and root password. • Select Use locally installed packages. • Make sure Enable Shared Storage Support is selected. • Click Submit. Although the interface states that the systems are rebooted, they are not. 12. Configure fencing: a.
14. Complete the following steps on each cluster node to verify that all cluster nodes can access the 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. Enter the following commands on the console of the node: mkdir /VAULT10 chown bill.root /VAULT10 chmod 755 /VAULT10 mount /dev/gfsvg1/lv1 /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 .
15. 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. If you 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.
b. 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 c. Using the luci web interface, ensure that nodes are not fenced. d.
Quorum: 1 Active subsystems: 7 Flags: 2node Ports Bound: 0 11 Node name: 192.168.80.2 Node ID: 2 Multicast addresses: 239.192.2.201 Node addresses: 192.168.80.
44 | Installing GFS
Configuring Licensing Before you can use VTS, you must enable virtual tape drive (VTD) licensing. You can also enable licensing for optional features — SecureVTS, Instant DR, and AutoCopy (Instant DR and AutoCopy are licensed together). To obtain license keys, log in to https:// partners.crossroads.com, click Tools, and follow the instructions on the site. License keys are generated based on the hardware ID of the VTS server. Obtain a set of license keys for each VTS server in your environment.
4. If SecureVTS is licensed, type the license key in the Secure VTS Key field. 5. If Instant DR and Autocopy are licensed, type the license key in the IDR Key field. 6. In the VTD Key field, type the license key. 7. Click SUBMIT. 8. On the pop-up dialog, click OK to confirm that you want to add the key. 9. Restart the TapeServer service. Click Supervisor Functions on the navigation pane. On the Supervisory Functions page, click Stop TapeServer and then click Start TapeServer.
Configuring and Validating Virtual Tape Drives After Virtual TapeServer (VTS) is deployed, you must create virtual tape drives (often referred to as VTDs). Up to 32 virtual tape drives are supported per VTS server. Then, you must configure the virtual tape connections in VTS, which define connections between the hosts and virtual tape drives in your environment. You can then validate that the host server(s) in the environment can back up data to all virtual tape drives configured in VTS.
Presented to Host? Property Description Host type The type of host (NonStop S-series, NonStop Integrity, NonStop BladeSystem, or UNIX server). No Serial number The serial number or other string describing the virtual tape drive. Only alphanumeric characters should be used. Yes The first four properties are collectively referred to as the BTLI of the virtual tape drive.
i. Specify a name for the virtual tape drive in the name field. If you are creating multiple virtual tape drives, increment the number that is appended to the physical tape drive noted in step 5c. j. Select RAID from the type drop-down list. k. Click Add Physical Tape. 2. Add a new logical tape, as follows: a. Click Setup Tapes at the bottom of the page to display the Manage Tape Connections page. b. Click Add a new logical tape. The Add A New Logical Tape page is displayed. c.
target IDs on a bus must be identical, and you cannot assign a LUN value more than once per bus. The appropriate ID value depends on the host server: • For NonStop S-series servers IDs 4 and 5 are reserved for tape devices, while other IDs are reserved for other device types. NonStop S servers default to target ID 5 for tape drives, therefore it is recommended that you select 5 from the target drop-down list.
h. Select the media format from the tape_type drop-down list. This property defines the type of tape that the virtual tape emulates. This property also specifies the icon selected for the logical drive on user interface pages. Note Do not select RAID; this option is provided for physical tapes only. i. Specify the host, or initiator, type by choosing an option from the host_type dropdown list. This property is for reference only; it is not presented to the host.
b. Note the bus, target, LUN, and initiator (BTLI) numbers for the highest numbered physical tape drive to which the RAID type is assigned. In the snapshot provided in the previous step, the highest BTLI is 30 1 0 7. c. Note the name of this physical tape drive. In the snapshot, the physical tape drive is named PTAPE01. d. Note the name of the associated logical tape. The example logical tape is named LTAPE01. It is recommended that you back up the VTS database after modifying the VTS configuration.
For example, the $VTAPE01 virtual tape drive is associated with the LTAPE01 logical drive and the PTAPE01 physical hard drive: The following steps describe how to disassociate the virtual tape drive ($VTAPE01 in this example) from its logical and physical drives (LTAPE01 and PTAPE01): a. In the navigation pane, click Manage Connections. The Manage Tape Connections page is displayed. b. Click Delete a tape connection. The Delete A Tape Connection page is displayed: c.
c. On the Choose A Virtual Tape To Edit page, select the virtual tape drive to edit (the one for which you deleted the connection) and click Edit. This page is then displayed: d. Change the values of the virtual tape as needed. See step 3 on page 49 for a description of the properties. e. Click Edit Virtual Tape to save your settings. 3. Re-associate the virtual tape drive with the logical and physical drives: a. Click Manage Connections in the navigation pane.
b. Click Add a tape connection. The Add A Tape Connection page is displayed: c. Select the virtual tape drive you want to reconnect from the Virtual Tapes section of the page. d. Select the logical and physical drives to which you want to reconnect the virtual tape drive from the Logical Tapes section of the page. e. Click Add Tape Connection. If successful, the connection is added at the bottom of the virtual-logical-physical associations on the System Overview page.
sg2 3 tape CPQNSD 5257 #VFHP02 slot 1, port 1 VFHP02 VT36 sg3 3 tape CPQNSD 5257 #VFHP03 slot 1, port 1 VFHP03 VT36 sg5 3 tape CPQNSD 5257 #VFHP04 slot 1, port 1 VFHP04 VT36 4. If you do not see devices, issue the following command to scan the devices and detect new devices: CLIMCMD clim_name lunmgr -s 5. If the devices are not listed again, issue the following command, which enables you to set LUNs: CLIMCMD clim_name lunmgr -a, VERBOSE 6.
On NonStop S-series servers, issue the following command: SCF ADD TAPE $VTD, BACKUPCPU #, COMPRESSION OFF, DENSITY 6250, DEVICEID #, HIGHPIN ON, LOCATION (x,y,z), LUN 0, MAXOPENS 4, PRIMARYCPU #, PROGRAM $SYSTEM.SYSTEM.OTPPROCP, RECSIZE 2048, SAC #, SENDTO STORAGE, STARTSTATE STARTED This command should return messages similar to the following if successful: SCF - T9082G02 - (06JAN06) (31OCT05) - 01/19/2007 08:42:02 System \DEV3 (C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
58 | Configuring and Validating Virtual Tape Drives
Configuring Access Control If you have system administrator privileges, you can configure access control to grant or limit access to specific VTS functions. Each login ID belongs to a group and each group has a unique set of privileges. Note VTS provides a user that has administrator privileges. You can log in as admin if no other administrative user is created on the system. The default password for this user is virtual.
Enabling a closed system You can enable a closed system to require authentication. The user can access only the resources assigned to a particular group. You can enable or disable individual rights to resources. Requires the System Access Controls access right To enable a closed system 1. Click Access Control on the navigation pane. 2. When prompted, log in. After logging in, the Access Control page is displayed. 3.
subcategories are granted by default, though you can remove individual rights in the subcategories.
Rights Administration Group Operations Group Supervisor Group Virtual Tape Mounts and Locks X X Virtual Tape Pool Maintenance X X Erase Cartridges X X HSM Migration X X Mount Cartridges X X Unmount Cartridges X X View System Status X X X Change Refresh Rate X Stop and Start TapeServer X X X X X X X X X Vault Access Access to All Vaults X Note that, by default, the Factory Setup Activities access right is not assigned to any group.
Managing users You can add users to VTS or modify settings of an existing user. The following sections describe how to create, modify, and delete users. Note In the following procedures, if the Users and Groups and Rights sections of the Access Control page are not available, you must enable a closed system. These sections are not displayed if the system is configured as open access. Creating a user Requires the System Access Controls access right To create a user 1.
3. Click + to expand Users and Groups. 4. Click ADD. The name and password fields are displayed. 5. Type a username in the name field. Usernames cannot contain spaces and cannot duplicate existing usernames, group names, or reserved names. Also, they must be alphanumeric, though they can include an _ (underscore) character. 6. Type a password in the password field.
7. Click APPLY. The user is added and additional buttons are displayed. 8. To assign the user to a group, click CHANGE GROUP. The Group drop-down list is displayed. Note The user cannot perform functions until you assign the user to a group. 9. Select a group from the drop-down list and click APPLY.
Changing any user’s password It is highly recommended that you change the passwords of the default users. Requires the System Access Controls access right to change any user’s password To change a user’s password 1. Click Access Control on the navigation pane. 2. When prompted, log in. After logging in, the Access Control page is displayed.
3. Click + to expand Users and Groups. 4. Select the user from the Users drop-down list. 5. Click SET PASSWORD. The Password field is displayed. 6. Type a new password in the field. 7. Click APPLY.
Changing your password Requires the User Access Controls access right to change your password only To change your own password 1. Click Access Control on the navigation pane. 2. When prompted, log in. After logging in, the User Access Control page is displayed. 3. Type your current password in the Old password field. 4. Type a new password in the New Password field. 5. Type the new password again in the New Password (again) field. 6. Click APPLY.
Assigning a user to a group Requires the System Access Controls access right To assign a user to a group 1. Click Access Control on the navigation pane. 2. When prompted, log in. After logging in, the Access Control page is displayed. 3. Click + to expand Users and Groups.
4. Select the user from the Users drop-down list. The SET PASSWORD and CHANGE GROUP buttons are displayed. 5. To assign the user to a group, click CHANGE GROUP. 6. Select a group from the drop-down list and click APPLY. Deleting a user Requires the System Access Controls access right To delete a user 1. Click Access Control on the navigation pane. 2. When prompted, log in. After logging in, the Access Control page is displayed.
3. Click + to expand Users and Groups. 4. Select the user from the Users drop-down list. 5. Click REMOVE. 6. When prompted, click OK to confirm that you want to remove the selected user.
Configuring groups Groups define the access rights that are assigned to users. Three groups are provided: Administration, Operations, and Supervisor. For a list of the default rights assigned to these groups, see page 60. You can modify the access rights that are assigned to these groups. You can also save your changes as a set of custom defaults, which can be restored later if necessary.
3. Click + to expand Rights. 4. To modify access rights assigned to the Administration group, select the checkbox next to each access right in the Administration column. Note The rights are organized in categories. If you grant access to a category, all rights in the subcategories are granted by default, though you can remove individual rights in the subcategories.
Right User Access Controls Description Enables the user to change his or her password only within Access Control Block and Unblock TapeServer Displays the Block & Unblock TapeServer link on Supervisory Functions page, which enables the user to block and unblock VTS functions Database Download Enables the user to download the database from the Supervisory Functions page Database Upload Enables the user to upload a database from the Supervisory Functions page Edit VTS Configuration File Enables the u
Right Description Scan and Cleanup Control Panel Grants access to the Virtual Media - Scan/ Cleanup page Virtual Tape Cartridge Maintenance Grants access to the Virtual Media - Cartridge Maintenance page Delete Cartridges Enables the user to delete virtual tapes from the Virtual Media - Operation and Virtual Media - Cartridge Maintenance pages Virtual Tape Import and Export Grants access to the Virtual Media - Import/ Export page Virtual Tape Instant DR Grants access to the Virtual Media - Instan
5. To modify access rights assigned to the Operations group, select the checkbox next to each access right in the Operations column. See step 4 for a description of each right. 6. To modify access rights assigned to the Supervisor group, select the checkbox next to each access right in the Supervisor column. See step 4 for a description of each right. 7. Click APPLY above the table to save your changes.
2. When prompted, click OK to confirm that you want to save the settings as the custom defaults. The Restore CUSTOM Defaults button becomes available in the Defaults and Undo section of the page. To restore the custom default settings Click the Restore CUSTOM Defaults button to restore the custom configuration and discard changes made since the custom defaults were last saved.
78 | Configuring Access Control
Configuring EMS Communication To automate the process of mounting and dismounting virtual tapes, you must configure the Event Management System (EMS) on Virtual TapeServer (VTS). The EMS service starts the EMS distributor on the NonStop server by issuing a Tandem Advanced Command Language (TACL) command. The distributor notifies the VTS EMS service when an EMS message is posted on the NonStop server.
Parameter Description Values Required ems_notify_enable Enables EMS messages to be generated for notifications. YES or NO No YES or NO No ALL, INFO, WARNING, ERROR, CRITICAL, or NONE No List of hostnames or IP addresses separated by spaces No Default value: NO ems_notification_ enable Enables VTS to send notification messages back to the NonStop host from EMS messages.
Parameter Description Values Required ems_keep_alive Specifies the number of seconds between periodic EMS messages that are sent from VTS to the host so that the Telnet session does not time out. When set, EMS filtering on the host can be increased because the Telnet connection between the VTS server and the NonStop host stays alive. If omitted or set to 0, keep-alive messaging is disabled.
Parameter Description Values Required ems_response_ timeout Specifies the timeout value (in seconds) used to wait for each response during the EMS Telnet login process. Integer No Note that you can specify the ems_response_timeout_ NSserver instead of or in addition to this parameter. If ems_response_timeout_ NSserver is specified, its value overrides the value of this parameter for the specified host. See the next step for more information about ems_ response_timeout_NSserver.
Parameter Description Values Required ems_service_ prompt_type Specifies the service selection prompt to which the EMS login process responds and begins. Expression No Expression No Expression Yes Expression No type is the hostname of the NonStop server or TYPE:choice, where choice is the login service, such as TACL, TACLS, XYGATE, or SAFEGUARD. You can also specify _ANYSYS instead of _type.
Parameter Description Values Required ems_login_ useranswer_type Defines the user response shown during the login process. See ems_service_prompt _type for an explanation of type. Expression No Expression No Expression No Default values: • for _TYPE:TACL: logon %username% • for _TYPE:TACLS: %username% • for _TYPE:XYGATE: logon %username% • for _TYPE:SAFEGUARD: logon %username% ems_login_ passprompt_type Defines the password prompt during the login process.
Parameter Description Values Required ems_login_ successful_type Defines a command string to send after successful login. See ems_service_prompt_type for an explanation of type. Expression or null No Default values: • for _TYPE:TACL: /Last Logon:/ • for _TYPE:TACLS: /Last Logon:/ • for _TYPE:XYGATE: /Last Logon:/ • for _TYPE:SAFEGUARD: /Last Logon:/ d. For each hostname specified by ems_hostnames, you can add the following hostspecific EMS parameters at the bottom of the file that is displayed.
Parameter Description Values Required ems_virtdevs_ NSserver Specifies the list of virtual tape drives known to the NonStop server that correspond to the list specified by ems_hostdevs_NSserver. If this entry is omitted, VTS uses the same names listed for the host. If specified, there must be the same number of virtual tape names as host tape names. There is a one-to-one correspondence.
Parameter Description Values Required ems_login_ command_NSserver Initiates the EMS Distributor on the NonStop server. The name variable in the command ($VTMS1 in the following example) should be unique for every VTS server.
ems_hostdevs_DEV2='$TAPE25' ems_virtdevs_DEV2='VTAPE25' ems_service_select_DEV2='TACL' ems_login_command_DEV2='#SET #INFORMAT TACL |EMSDIST /CPU 0, PRI 100, NAME $VTMS1, TERM $ZHOME/ BACKUP 1, TYPE P, COLLECTOR $0, TEXTOUT [#MYTERM]' Here is an example of the parameters set in the default VTS configuration file: ems_enable='NO' ems_mount_delay='0' ems_notify_enable='NO' ems_notification_enable='NO' ems_notification_level='ERROR CRITICAL' ems_keep_alive='YES' ems_notify_hostnames='' ems_notify_wait_timeout='
3. Set the username and password for each EMS host: a. Click Supervisor Functions on the navigation pane. b. Click Manage Passwords. The following page is displayed: c. From the drop-down list, select the EMS host. Note If the EMS hostnames are not in the list, the ems_enable parameter may not be set to YES. d. In the Username field, type a username for that host. e. In the New Password field, type a password for the user. f. Retype the password in the New Password (again) field. g. Click Update. h.
• The recommended action to take. Message Text Severity Recommended Action (Error:) Non-zero return-code ($rc) from dsmc (try this url … for $cart_request. Critical An IBM Tivoli Storage Manager (TSM) failure occurred. Examine the return error code and correct the problem. AUTOCOPY FAILED: Request by: $requestor ($retry_number) cannot create directory $target (rc=$rc) Critical No action is required. The task will be retried.
Message Text Severity Recommended Action Error: BEX $policy $cart_request failed with result code $rc Critical See the HSM get or HSM put log files on the Supervisory Functions page for details about the HSM request. Error: BEX command failure! Critical A syntax error occurred in the BEX command. Repair the request and resubmit. Error: can not determine the proper command for this request. Critical HSM restore for TSM was unable to determine the proper restore or retrieve command.
Message Text Severity Error: Non-zero return-code ($rc) from NetBackup for $cart_request. Warning Error: Processing failed, no files processed for $cart_request Critical No files were successfully processed. See the HSM get or HSM put log files on the Supervisory Functions page for details about the HSM request. Error: Success message not found in NetBackup job output for $cart_request. Critical An HSM request failed to find or process the virtual tapes for the request.
Message Text Severity Recommended Action Info: $jobname ENDED to $backupSystem Inform Info: AUTOCOPY $requestor $source $target ($retry_number) Inform Info: AUTOCOPY Complete $requestor $source $target $retry Inform Info: autocopy from $source to $host:$destination Inform Info: cancel mount of $tape Inform Info: TMFcopy of $tape Inform Non-zero return-code ($rc) from NetBackup bprestore Warning Restored $count file(s) Inform Restored $count file(s), rc=$rc Inform vtape_ems.
94 | Configuring EMS Communication
Enabling Instant DR and AutoCopy Instant DR is an advanced software module (VT5907 or VT5907-A) that enables you to create and maintain identical copies of backup data on Virtual TapeServer (VTS) disk storage at one or more locations. In the event of a disaster, remote recovery operations can begin immediately using the backup data copy on a remote VTS site. VTS copies data to remote sites over a wide area network (WAN) TCP/IP connection.
Instant DR and AutoCopy features have distinct advantages that may be specific to individual sites or requirements. 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.
• SSH must be configured on all VTS servers involved in AutoCopy operations. You can also configure SSH if you want to secure data when copying data to remote locations (for Instant DR). SSH must be configured for Protocol 2 RSA or DSA encryption using Public Key Identification only. Public Key Identification requires that the sender’s Public Key be installed in the specific authorized_keys file on the receiver VTS system.
c. At the [root@site default]# prompt, enter startx. This starts the VTS operating system UI. d. From the operating system UI, click the Linux Start button at the bottom left-hand side of the window. e. Select System →Network Device Control from pop-up list. The Network Device Control window is displayed. f. Select eth1 and click Configure. The Network Configuration window is displayed: g. Double-click eth1. h. Select Activate device when computer starts. i. Select Statically set IP Addresses. j.
3. Set up the hosts file to configure aliases for each IP address of the VTS servers. a. Click the Hosts tab. b. Click New. c. Provide the IP address, hostname, and alias for the local VTS server. In this example, the following values are entered: • IP Address: 10.10.2.145 • Hostname: boston.mycompany.com • Aliases: boston d. Click OK.
e. Repeat these steps for each VTS site. In this example, after completing these steps for all VTS servers, the Hosts tab looks like this: f. Select File→Save. g. Click OK. h. Close the Network Configuration window. i. Select eth1. j. Click Deactivate. k. Click Activate. l. Select eth0. m. Click Deactivate. n. Click Activate. o. From the operating system GUI, select the Screen icon located at the bottom left-hand side of the window. A command prompt window is displayed.
p. At the [root@site default]# prompt, enter service network restart. The network interfaces are reset: q. Test connectivity by pinging the network connections. At the prompt, enter ping hostname. For example, to ping the Boston server, enter ping boston. Output similar to the following is displayed: 64 ms 64 ms 64 ms 64 ms bytes from boston (141.36.136.31): icmp_seq=0 ttl=64 time=0.053 bytes from boston (141.36.136.31): icmp_seq=1 ttl=64 time=0.053 bytes from boston (141.36.136.
f. Add the name of all other VTS servers in this file. For example, on the Los Angeles VTS server, enter boston. g. Save and exit the file. 5. Set up and authorize secure shell (SSH) if you are configuring VTS for AutoCopy or if you wish to secure communication for Instant DR. a. At the command prompt, change to the /home/bill directory. b. Enter the following command: ssh-copy-id –i /home/bill/.ssh/id_dsa.pub bill@boston c. When prompted, enter yes. d.
To configure TCP/IP security 1. On the VTS server, create the /etc/sysconfig/iptables file and open it for editing. 2.
• -A INPUT -i eth1 -j REJECT --reject-with icmp-port-unreachable Rejects all traffic with the exception of the preceding rules. • -A INPUT -p tcp -m state --state INVALID -j REJECT --reject-with icmp-port-unreachable Sends a rejected notification to the invalid sender. You can change REJECT to DROP to drop the traffic without a rejection notification. Note that this should be entered on one line. • COMMIT Causes the preceding commands to take effect. 3. Save and close the file. 4.
Enabling Enterprise Integration and Migration Enterprise integration enables a backup management application server to read and write files to and from Virtual TapeServer (VTS). You can enable VTS to migrate virtual tapes to physical tapes. To configure VTS to automatically migrate virtual tapes, you must install a backup management application client on the VTS server and configure the VTSPolicy command in conjunction with the Event Management Service (EMS) on VTS.
managed by the backup management application server according to policies set by the backup management application administrator. The backup management application server can migrate virtual tapes using the following methods: • The backup management application administrator creates a backup job on the backup management application server and schedules it to run on the backup management application client.
Adding a physical tape drive You can attach an external tape resource, such as a tape drive or robotic library, to VTS. You can then manually initiate migration of a virtual tape to physical tape, or you can rely on enterprise integration to automate migration of virtual tape data. Or, if you add a standalone tape drive or a simple cartridge autoloader, you can export a virtual tape.
c. Delete the virtual tape drive that uses the target bus. Click Manage Connections on the navigation pane, and then click Delete an existing virtual tape. The Choose A Virtual Tape To Delete page is displayed. d. Select the virtual tape that uses the target bus and click Delete. e. Change the system limits for the target bus. Click Factory Setup on the navigation pane. f. When prompted, enter factory as the username and the corresponding password.
4.
Requires the Edit VTS Configuration File access right To configure migration 1. Click Supervisor Functions on the navigation pane of the VTS interface. 2. Click Edit VTS Configuration File. 3. Add the following parameters at the bottom of the file that is displayed: Parameter Description Values Req’d? hsm_enable Enables migration.
Parameter Description Values Req’d? hsm_optfile For Tivoli Storage Manager only: Path Yes Path No Integer, from 1-30 No Policy Yes Schedule Yes YES or NO No Integer, from 0-999 No Specifies the path to the optfile file. Default value: dsm.opt hsm_optfile_pool For Tivoli Storage Manager only: Specifies the path to the optfile file for a specific pool. This parameter overrides the hsm_optfile parameter for the pool.
Parameter Description Values Req’d? hsm_summary_limit Specifies the number of lines retained in the log file, which records the command used to invoke each backup or restore job. This is a joint log that contains only the commands used, not the job output. Integer No Value No YES or NO No Default value: 1000 hsm_restore_period For Backup Express only: Specifies how far back in time the backup management application should search its catalog for the file to be restored.
• NetBackup: hsm_enable='YES' hsm_product='NBP' hsm_policy='POLICY' hsm_schedule='SCHEDULE' hsm_server='SERVER' ems_hsm_backup_notification='YES' • Networker: hsm_enable='YES' hsm_product='LEG' hsm_pool='POOL' hsm_server='SERVER' ems_hsm_backup_notification='YES' 4. Click SAVE. 5. Set the username and password for the backup management application. Note This step is required for Backup Express and NetBackup only. a. Click Supervisor Functions on the navigation pane. b. Click Manage Passwords.
114 | Enabling Enterprise Integration and Migration
Troubleshooting This appendix provides information to assist you in addressing problems you may encounter while installing and using Virtual TapeServer (VTS).
HP health monitoring utilities The VTS server provides the following: • HP Systems Insight Manager (HPSIM-Linux-C.05.02.02.00.bin) • HP System Health Application and the HP Insight Management Agents (hpasm-8.0.0173.rhel5.x86_64.rpm) • HP System Management Homepage (hpsmh-2.1.12-200.x86_64.rpm) • SNMP agent access to the HP iLO management controller (hp-ilo-8.1.0104.rhel5.x86_64.rpm) These utilities can be used for managing HP systems to maximize system uptime and health.
If error 224 occurs on the SCF, perform the following: • Verify that the virtual tape is using the 519X or 5257 definition. • Verify that the WWPN, SAC, and Module are correctly listed in SCF for the tape device. If an “end of media” message is displayed on the host, erase expired virtual tapes to clear disk space. If a tape drive stops responding from SCF, perform the following: • Check the system log for parity errors or other SCSI-related failures. • Check power indicators on the SCSI converter.
File system Verify the following: • Has anything changed? • Is performance slow? • Is GFS running on the system? • Is the problem occurring for a particular vault or all vaults? Is the problematic vault on internal or external disk storage? • What is the result of the last vault check on the external storage? You can check for FSCK messages in the system log, as well as the result of the last vault check.
The Apache web server is responsible for running the VTS web interface. To verify that Apache is running: /etc/init.d/httpd status A message similar to the following should be displayed: httpd (pid 25380 25015 25014 25013 25012 25011) is running... Use the following commands, respectively, to stop, start, or restart the web server (halt VTS before issuing these commands): • /etc/init.d/httpd stop • /etc/init.
To view log files, the following commands are useful: vi logfile To edit and search the file tail –f –n 35 logfile To list the file in real-time grep –ni string logfile To search for a specific string more logfile To search a file by paging through it SCSI converter During normal operation, the LEDs on the SCSI converter blink every 3-5 seconds. During backups, the activity LED is almost solidly lit.
Event Management System (EMS) Verify the following: • Has the EMS logon expired? • Is there network connectivity between VTS and the NonStop server? • Was the VTS operating system or the EMS template upgraded? • Is VTS up-to-date with the latest product enhancement code? • Is there a typographical error in the VTS configuration file? You can check the EMS log file for the last timestamp of messages.
• Check that the tape is in the drive. • Check the media write-protection. If you cannot access a virtual tape because it is locked, perform the following: • Check MEDIACOM for label in use. • Check other VTS systems for remotely mounted virtual tapes. • Reboot VTS to clear all local file locks. If an autoloading pool did not recycle, verify that Autoloading or Recycle is selected on the Pool Maintenance page.
• Erasing all virtual tapes in a pool on the Cartridge Maintenance page: A message similar to the following is displayed on the web interface: Erased 1 cartridge; Erasure of cartridge SH0002 in pool SHARE failed! • Setting the virtual tape size on the Pool Maintenance page: A message similar to the following is displayed on the web interface: Unable to set size limit on SHARE:SH0001, rc=2.
number and a new (blank) log begins with the default name. All rotated log files are compressed except for the first (more recent). Thirty versions of the file are kept. This file is renewed each day at 4 a.m. Previous log files are compressed using gzip. If more than seven log files must be maintained, the files must be backed up manually. Note Users must have Read access to the /user/local/tape/log directory.
Attribute Format Example Description User administrator The user ID under which the associated event was executed. Message text Access Control RESTORE OPEN defaults have been restored A description of the event or condition. (See Message text on page 126.) Field limits Messages are up to 255 characters in length; each message field has a character limit. The attributes that have a variable length are automatically compressed to the available space.
Severity ID Severity Level Description 6 Error A user error that the system or application can handle with no interruption and limited degradation of service. 8 Critical A system or service error from which the system can recover, although there might be a momentary loss or permanent degradation of service.
Severity ID Subsystem ID Event ID Subsystem Message text 6 20 001 Manual mount Cartridge XXX mount failed, rc=RC 8 20 001 Manual mount Cartridge XXX mount failed, rc=RC 2 20 002 Manual unmount Cartridge XXX has been manually unmounted 6 20 002 Manual unmount Cartridge XXX unmount failed, rc=RC 2 20 003 EMS mount ems mount TAPE for HOST as ACCESS completed 8 20 003 EMS Mount ems mount TAPE for HOST failed rc=RC 2 20 004 EMS mount Read-Only ems telnet ems mount of TAPE b
Severity ID Subsystem ID Event ID Subsystem Message text 8 20 031 EMS Delete Cartridge PATH delete in Pool POOL failed, rc=RC 4 20 032 EMS Policy IDR ems telnet IDR completes, rc=RC 8 20 032 EMS Policy IDR vtape-operation-erase-PATHfailed-rc=RC 2 20 033 EMS Policy Migrate Cartridge PATH migrated 6 20 033 EMS Policy Migrate Cartridge PATH migrate failed, path in use, rc=RC 8 20 033 EMS Policy Migrate Cartridge PATH migrate failed, rc=RC 2 20 040 EMS Policy BEX ems telne
Severity ID Subsystem ID Event ID 2 20 8 Subsystem Message text 096 EMS Policy HSMPUT hsmput XXXXXX for HOST completed 20 096 EMS Policy HSMPUT hsmput XXXXXX for HOST failed, error MSG, rc=RC 2 20 097 EMS Policy HSMGET hsmget XXXXXX for HOST completed 8 20 097 EMS Policy HSMGET hsmget XXXXXX for HOST failed, error MSG, rc=RC 2 20 098 EMS Policy HSMDELETE hsmdelete XXXXXX for HOST completed 8 20 098 EMS Policy HSMDELETE hsmdelete XXXXXX for HOST failed, error MSG, rc=RC 2
Severity ID Subsystem ID Event ID 8 20 8 Subsystem Message text 209 EMS Policy Mount ems reject TAPE for HOST no virtual drives available 20 210 EMS Policy ems reject TAPE for HOST immediate request not recognized 8 20 213 EMS Policy ems failure TAPE for HOST already locked 2 20 250 EMS Policy TSM ems_telnet TSM2 POLICY 2 20 251 EMS Policy TSM ems_telnet TSM2 completes rc=0 8 20 252 EMS Policy TSM ems_telnet TSM2 completes rc=RC Cartridge maintenance 2 21 010 Cartridge
Severity ID Subsystem ID Event ID Subsystem Message text 4 22 002 Pool deleted vtape_pool libDelete VAULTXX 4 22 003 Pool renamed vtape_pool libRename XXXXX VAULTYY/YYYY 4 22 004 Pool moved vtape_pool libMove XXXXX YYYYY 2 22 005 Size set vtape_pool libApply set tixe limit PATH from SIZE to SIZE 2 22 007 Retention set vtape_pool libApply set retention PATH RETAIN 2 22 008 Retention modified vtape_pool libApply vtmeta FILES from RETAIN to RETAIN 2 22 009 Set Pool to Auto
Severity ID Subsystem ID Event ID Subsystem Message text 2 24 006 Job Completed IDR job JOB completed rc=0 8 24 006 Job Completed IDR job JOB completed rc=RC 2 24 007 IDR Save IDR save JOB 6 24 007 IDR Save IDR no carts for TAPE 4 24 008 IDR Delete IDR delete JOB 4 24 010 IDR Stop IDR stop PID 2 25 001 Job Started AutoCopy of TAPE started 2 25 002 Job Successful AutoCopy of TAPE complete 8 25 003 Job Failed AutoCopy of TAPE failed 6 25 004 Job Retried Au
Severity ID Subsystem ID Event ID Subsystem Message text 2 28 002 Job successful vtexport Export complete for PATH unloading TAPE 8 28 003 Job Failed vtexport Export WHY for PATH Transaction Management Facility (TMF) Copy 2 30 001 EMS start TMF copy ems telnet start TMFcopy of TAPE to TAPE for HOST Subsystem Message text Supervisor functions Subsystem ID Event ID 2 33 000 Unblock TapeServer Startup perform UNBLOCK 4 33 001 Block TapeServer Startup perform BLOCK 4 33 002
Severity ID Subsystem ID Event ID Subsystem Message text 2 35 004 EMS Started perform EMSCONTROL_START 5 35 005 EMS stopped perform EMSCONTROL_STOP 2 35 007 XML Started perform XMLSART 4 35 008 XML stopped perform XMLSTOP 2 35 010 ICS Started perform VTSISC_START 4 35 011 ICS stopped perform VTSISC_STOP 2 35 015 TM Started perform TMSTART 4 35 016 TM stopped perform TMSTOP Severity ID Subsystem ID Event ID Subsystem Message Text 4 40 001 Factory Setup acc
Severity Subsystem ID Event ID 4 51 2 Subsystem Message Text 002 Delete a tape connection Tape connection XXXXX as YYYYYY deleted 52 001 Add Logical tape LXXXX added 2 52 002 Edit Logical tape LXXXX edited 4 52 003 Delete Logical tape LXXXX deleted 2 53 001 Add Virtual tape VXXXX added 2 53 002 Edit Virtual tape VXXXX edited 4 53 003 Delete Virtual tape VXXXX deleted Subsystem ID Event ID Subsystem Message Text 2 61 001 Access Control accessed Access Control O
Severity ID Subsystem ID Event ID 4 62 2 2 Subsystem Message Text 002 Delete/Remove user Access Control REMOVE USER UUUU 62 003 Set user password Access Control SET PASSWORD for UUUU 62 005 Change user group Access Control CHANGE PASSWORD for UUUU 2 63 001 Add Group Access Control ADD GROUP GGGG 4 63 002 Remove Group Access Control REMOVE GROUP GGGG 2 64 001 Rights changed/ altered Access Control Save Rights 2 64 002 Save rights as CUSTOM Access Control Save Custom Righ
Severity ID Subsystem ID Event ID Subsystem Message Text 6 71 005 Erase by List EraseByList failed 2 72 000 Delete by List DeleteByList start 2 72 002 Delete by List DeleteByList complete 8 72 003 Delete by List DeleteByList command XXXX not recognized 6 72 004 Delete by List DeleteByList vclear error on CART is RC 6 71 005 Delete by List DeleteByList failed 81 002 Erase by List erase-by-list-crumb 8 90 003 XML Mount xml_socket id=50 MSG 2 90 004 XML Mount xml
138 | Troubleshooting
Credentials Here is a list of the user accounts for the VTS operating system (Linux). Username Default Password root bbill bill bbill The first time you log in to the VTS operating system using one of these usernames, you are prompted to change the password. Acceptable passwords must be at least 8 characters in length and include uppercase and lowercase alphanumeric characters.
140 | Credentials
SCSI-to-Fibre Channel Adapter Upgrade This appendix provides instructions to replace one or more SCSI cards with the same number of VTS-supported Fibre Channel (FC) cards on the following VTS models: • VT5900-E, on the HP ProLiant DL385 G2 • VT5900-H, on the HP ProLiant DL385 G5 Refer to Upgrading a SCSI Adapter to a Fibre Channel Adapter on page 152 if you need to upgrade legacy hardware.
g. Click Supervisor Functions on the navigation pane. h. Click Block TapeServer Startup on the Supervisory Functions page. 2. Unmount all vaults, stop the PMF on the NonStop server, and shut down VTS. a. From a terminal window on VTS, log in as root. b. Use the umount /VAULTxx command (where xx is the vault number) to unmount all vaults. Repeat this command for each vault on the system until all vaults are unmounted. c. Verify that all vaults are unmounted by typing mount in the VTS terminal window.
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 sure the blue clips are firmly seated and locked in place on each slot. Then, re-install the PCI Riser 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.
6. Configure the new Fibre Channel bus(es) as virtual devices (targets). For each bus that you wish to configure for use as a virtual tape drive, complete these steps: a. Click Factory Setup on the navigation pane. b. When prompted, enter the login credentials. c. Click Factory Options and enter the login credentials again. d. Click Manage system limits. The Manage system limits page is displayed.
f. PCI Slot Bus Number Card Type Virtual Tape Name 5A 2 2G Fibre $VTAPE02 5B 3 2G Fibre $VTAPE03 Click Set Limits. 7. Reboot VTS. 8. Use the VTS web interface to reconfigure a virtual tape connection. After the Fibre Channel ports are configured as virtual devices, the final step in this process is to reconfigure the virtual tape connections. Virtual tape connections originally set up as SCSI need to be edited for use on a Fibre Channel bus.
146 | SCSI-to-Fibre Channel Adapter Upgrade
Hardware Information for Legacy Installations This chapter describes the hardware that was shipped for the Virtual TapeServer (VTS) 6.03.39, 6.03.41, and 6.03.42 installations and that is supported in an upgraded environment. It also provides cabling and Fibre Channel upgrade procedures for the old hardware. Hardware overview For VTS installations that are upgrading to 6.04, the following hardware may be installed. Note Models shipped with 6.03.42 are still shipped with 6.04.
SCSI converters Each SCSI converter converts high-voltage differential (HVD) Ultra160/SCSI-3 to low-voltage differential (LVD) Ultra-2 SCSI. It provides up to four converter circuits. Here is a picture of the back of the SCSI converter: Internal storage If the VT5900-C, VT5900-E, or VT5900-G was purchased, additional internal storage may have been purchased for storing virtual tapes.
Fibre Channel upgrade card To replace a SCSI card with a Fibre Channel (FC) card on an HP ProLiant server, the VT5900-FCU may have been purchased: This FC upgrade card is a 2 Gb/sec, dual port, 64-Bit/133 MHz, PCI-X-to-Fibre Channel host bus adapter (HBA). Cabling and connecting VTS Cabling for the various VTS models is described in the following sections.
Connecting the HP ProLiant DL585 G1 (VT5900-A) The VT5900-A is a 4U (7 inch) chassis and provides 12 SCSI bus assignments, numbered 112. This model includes two dual-channel Fibre Channel cards, providing up to four connections to external storage.
Here is an illustration of the bus 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 buses, numbered 0-3. The VT5900-C has a dual-channel Fibre Channel card but no DAT72 drive and is shipped with two (mirrored) 36GB SCSI drives, for use by the software only.
Here is an illustration of the HVD and LVD ports on the back of the SCSI converter: Modifying virtual tape connections When modifying a virtual tape connection in VTS, you must define a virtual tape’s properties. Refer to Configuring and Validating Virtual Tape Drives on page 47 for an explanation of the properties and instructions for modifying them. These following provides information needed when modifying the bus ID for virtual tape connections on 6.03.39 and 6.03.41 hardware.
On the HP ProLiant DL585 G1 (VT5900-A) After completing step 2 on page 142, remove the SCSI card(s) and install the Fibre Channel card(s), as follows: 1. From the rear of the HP ProLiant DL585 server, mark each SCSI cable with the port position to which 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 SCSI adapters for easier access to the adapter cards. 3.
The following order of SCSI card removal must be followed: 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, if necessary. c. Remove the SCSI card in slot 2 and install the third Fibre Channel card in slot 2, if necessary. d. Remove the SCSI card in slot 1 and install the fourth Fibre Channel card in slot 1, if necessary. e.
On the HP ProLiant DL380 G4 (VT5900-B and VT5900-C) After completing step 2 on page 142, remove the SCSI card(s) and install the Fibre Channel card(s), as follows: 1. From the rear of the HP ProLiant DL380 server, mark each SCSI cable with the port position to which 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 SCSI adapters for easier access to the adapter cards. 3.
The following order of SCSI card removal must be followed: 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, if necessary. Here is a snapshot of the SCSI card after it is removed: 7. After you install all of the Fibre Channel upgrade cards in the appropriate slots, make sure the blue clips are firmly seated and locked in place on each slot.
Specifications The following outlines the physical and environmental specifications of the ProLiant server on which Virtual TapeServer is shipped: Component Specifications Electrical • Rated Line Voltage: 100 VAC, 120 VAC, 200-240 VAC • Rated Input Current: 10A (at 100 VAC), 9A (at 120 VAC), 6.
158 | Specifications
Index A access control overview 59 saving and restoring custom defaults 76 Access Control page, overview 11 access rights, See rights adding physical tape drive 107 assigning groups to a user 69 rights to a group 72 attaching physical tape drives to VTS 107 audience vii AutoCopy configuring network settings 97 TCP/IP security 102 configuring SSH 102 enabling 95 licensing 45 automating mounts 79 B backup management applications, See BMAs BMAs integration 105 supported by VTS 105 BTLI 48 building blocks of V
D database, troubleshooting 118 debug information 115 default groups 60 users 60 deleting users 70 deployment, overview 17 diagnostic commands 118 tools 115 documentation viii E EMS configuring 79 messages 90 parameters in configuration file 79, 85 troubleshooting 121 user accounts 89 ems_enable parameter 79 ems_hostaddr_NSserver parameter 85 ems_hostdevs_NSserver parameter 85 ems_hostnames parameter 79 ems_hostport_NSserver parameter 85 ems_hsm_backup_notification parameter 112 ems_InterSystemCommunicatio
hsm_enable parameter 110 hsm_erase_after_backup parameter 111 hsm_joblog_maxnum parameter 111 hsm_optfile parameter 111 hsm_optfile_pool parameter 111 hsm_policy parameter 111 hsm_pool parameter 110 hsm_product parameter 110 hsm_put_batch_size 111 hsm_restore_device parameter 110 hsm_restore_period parameter 112 hsm_schedule parameter 111 hsm_server parameter 110 hsm_summary_limit parameter 112 I iLO 116 initiator, description 50 installation checklist 18 overview 17 installing GFS 33 Instant DR configurin
S SCSI controllers, troubleshooting 117 converter cabling to VTS 21 cabling from NonStop server 20 overview 15 converter, troubleshooting 120 termination 21 upgrading to Fibre Channel for legacy hardware 152 SCSI-to-Fibre Channel upgrade current models 141 SecureVTS licensing 45 page 11 SSH, configuring 102 Supervisory Functions page 10 Support viii system event log 123 System Overview page 8 System Status page 4 T target, description 49 troubleshooting database 118 diagnostic commands 118 diagnostic tools
W web interface overview 4 troubleshooting 118 Index | 163
