Installation Guide HP Virtual TapeServer for NonStop Servers Part Number: 528654-008 Product Version: 6.03.42 19333 Vallco Parkway Cupertino, CA 95014 © 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCSI converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . External storage or the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
Typographical conventions This guide uses the following typographical conventions: Convention Description Bold Used for file names, field names, URLs that are not hyperlinked, interface elements that are clicked/selected, and information that must be used literally. Bold Italic Represents variables within file names, command syntax, or other literal text. Italics Used for emphasis, book titles, and variables.
• A detailed description of the problem you are having with the equipment • Your name, telephone number, fax number, email address, and company address Preface | ix
x | Preface
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. Disk-based backup can significantly improve performance, contribute to improved operations, and enable an increasingly automated backup strategy.
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 RAID that are configured according to user needs. Most frequently, vaults include the entire RAID, though defining several vaults is a convenient way to separate data for different applications or users.
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 (BMAs), including IBM Tiv
System Status page The System Status page provides a view of VTS services that are currently running, virtual tape connections, and vault and pool free space. Only users that are assigned the View System Status access right can view this page. Click System Status on the navigation pane to view this page: The following sections are provided on this page: SERVER_NAME Provides the VTS system name, the current software version and date created, and the current date and time.
Free Space Optional section that is shown by default. When enabled (by setting the free_space_status parameter in the VTS configuration file), this section provides the following information: Vault/Pool: Displays all vaults and, after you click a vault, all pools in the vault Size: Displays the total size of the vault Available: Displays the remaining space in a vault Connections Displays all current virtual tape connections.
Start TapeServer (under Processes). You must have the Stop and Start TapeServer access right to start VTS. The table lists the host devices, pools, and virtual tapes configured on the VTS server. (This information is not listed if VTS is not running.) The host devices are the virtual tape drives that are displayed on the System Overview page (click View Configurations to view this page). The virtual tape devices correspond to vaults that were configured before VTS shipped.
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. For example, when you select cartridge maintenance from the window menu, the Virtual Media - Cartridge Maintenance page is displayed: Each Virtual Media page provides an area below the page title devoted to messages generated by VTS as a result of actions you perform on the pages. These messages generally confirm an operation or report an error.
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 One of the following VTS server modules is installed: • Model VT5900-A is built on the HP ProLiant DL585 G1 server: • Model VT5900-E or VT5900-G, which are built on an HP ProLiant DL385 G2 server: Two Fibre Channel cards (for supporting VTDs) are installed in model VT5900-G; two SCSI cards are installed in model VT5900-E. SCSI converters Each SCSI converter converts high-voltage differential (HVD) Ultra160/SCSI-3 to low-voltage differential (LVD) Ultra-2 SCSI.
External disk storage The following hardware may be purchased for external disk storage: • VT5915, which is built on the StorageWorks Modular SAN Array (MSA) 1500. It provides one controller shelf and one MSA 20 disk shelf, and it includes dual controllers. • VT5916, which is an MSA 20 add-on enclosure and is available if additional storage is needed after purchasing and installing the VT5915. You can install up to three of these storage arrays per VT5915.
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.
9. 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 43 for more information. 10. If Instant DR or AutoCopy is licensed, configure VTS to send EMS messages to the NonStop server.
Cabling and Connecting VTS A critical part of installing Virtual TapeServer (VTS) is establishing the physical connection between the NonStop 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 a summary of each model’s base configuration: VTS Model Height # of SCSI Ports # of FC Ports Optical or Magnetic Drives VT5900-A 4U 12 4 CD VT5900-E 2U 4 2* (for SAN connection only) DVD/CD VT5900-G 2U 0 6 (2 for SAN connection, 4 for VTDs) DVD/CD * Four SCSI ports (in slots 4 and 5) and two 4Gb Fibre Channel (FC) ports (in slot 2) are provided in the base configuration.
Connections from third 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 bus 8 (PCI-X slot 4A) on VTS server To bus 9 (PCI-X slot 4B) on VTS server To bus 10 (PCI-X slot 3A) on VTS server To bus 11 (PCI-X slot 3B) on VTS server Here is an illustration of the bus numbers on the back of the VT5900-A (DL585): Here is an illustration of the HVD and LVD ports on the back of th
Also, note that you do not have to use all of the SCSI buses (nor converter ports) for VTDs. You can use the ports as initiators for legacy SCSI tape drives. Here is an illustration of the slots on the back of the base model VT5900-E (DL385 G2). If the P800 card is installed, it is placed in slot 3 (below slot 4).
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 SCSI ports supported by VTS are Ultra160-LVD SCSI, with very high density connector interface (VHDCI) connectors. High-voltage differential (HVD) SCSI is supported through the SCSI converter. Connectors are labeled by bus number. Devices connected to different buses can have the same SCSI ID. The Fibre Channel ports on VTS support 4Gb Fibre Channel using LC-type connectors. Connectors are labeled by port number. Devices connected to different ports can have the same port ID.
chained subject to the maximum SCSI limitation of 82 foot total cable length. An HVD terminator is required on the last drive in the daisy chain. Connecting to the LAN, SAN, and power The following sections describe how to connect VTS to the network and power. Connecting to a LAN VTS is equipped with two standard 10Mbps/100Mbps/1Gbps Ethernet ports. Connect Ethernet port 1 for normal connectivity and port 2 for Instant DR and AutoCopy functionality.
Configuring Network Settings Virtual TapeServer (VTS) ships with the following default network configuration: IP address: 192.168.2.150 Netmask: 255.255.255.0 Gateway: 192.168.2.1 Hostname: tapeserver.tapelabs.com Before making any changes, obtain a new IP address, netmask, gateway, and hostname that are appropriate for your site from the network administrator. To change the network configuration, you must connect a monitor, keyboard, and mouse to VTS before powering it on.
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.
Adding Vaults for External Storage If you want to add a vault for external storage, you can connect a Linux system to Virtual TapeServer (VTS) over Fibre Channel and then complete the steps in this chapter. These steps require that you format the Linux file system and create disks, which are referred to as vaults in VTS. To add a vault to VTS 1. Attach the Linux system that will serve as the external storage. See Cabling to external resources on page 25 for more information. 2.
each device. For example, look at the /dev/sda line, which provides information about the /dev/sda device, the following information is listed: Host number = 12 Bus = 0 SCSI ID= 0 LUN = 1 SCSI type = 0 4. Configure the disk partitions by completing the following steps: a. Starting with the first recognized disk (sda), create the partition by entering the following command: fdisk /dev/sda The fdisk command displays a : prompt. The next commands are entered at this prompt. b.
7. Update the file-system table to reflect the new disks. Using a text editor, add the following lines to the /etc/fstab file for each vault created above: LABEL=/VAULT01 /VAULT01 ext3 defaults 1 2 Repeat this command for each vault. 8. Mount the newly created disks by entering the following command: mount /VAULT01 Repeat this command for each vault. 9. Assign access rights to the newly created disks by completing the following steps: a.
34 | Adding Vaults for External Storage
Reconfiguring and Validating Virtual Tape Connections Virtual TapeServer (VTS) is preconfigured with virtual tape connections. Edit the virtual tape connections, if necessary, to reflect exact 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.
The first four properties are collectively referred to as the BTLI of the virtual tape drive. The BTLI enables the host server to precisely identify the virtual tape drive; it provides an exact address of the virtual tape drive’s location on the bus. Remember that the host is connected to VTS by a single cable. The BTLI thereby enables you to multiplex the cable to identify multiple virtual tapes over a single cable.
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.
c. Select the connection you want to delete and click Delete Tape Connection. You can verify that the connection was deleted on the following pages: • Virtual Media — Click Virtual Media in the navigation pane and confirm that the virtual tape device is no longer listed in the table on the Virtual Media Operation page.
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.
i. 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 j. Do not select RAID, which is provided for Manufacturing’s purposes only. 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.
Validating backups from the NonStop server to the VTS server To validate that the NonStop server can back up to configured virtual tape drives in VTS, you must configure the NonStop server to add the virtual tape drive. Then, you can start the virtual tape drive from the NonStop server.
If unsuccessful, messages similar to the following are displayed: SCF - T9082G02 - (06JAN06) (31OCT05) - 01/19/2007 09:09:06 System \DEV3 (C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P. STORAGE E00002 START TAPE \DEV3.$TAPE30 rejected, file system error: 190 STOPPED: 0,63 CPU time: 0:00:00.
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. By default, VTS is an open system, which means that all users can access all functions. Access control enables you to establish rights for specific users or classes of users. You can fine tune control of VTS system resources on a group-by-group basis.
3. Under Defaults and Undo, click the Restore CLOSED Defaults button, which restores all default users, groups, and rights. 4. Click OK on the pop-up dialog box to confirm that you want to restore closed defaults. Below are closed system defaults: • • Users — The following users are defined.
Rights VTS/Linux Configuration Backup VTS/Linux Configuration Restore Administration Group X Supervisor Group X X View log files X View/Manage Configuration X Virtual Tape Operations Operations Group X X X X Scan and Cleanup Control Panel X X Virtual Tape Cartridge Maintenance X X Delete Cartridges X X Virtual Tape Import and Export X X Virtual Tape Instant DR X X Virtual Tape Mounts and Locks X X Virtual Tape Pool Maintenance X X Erase Cartridges X X HSM Migration X
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 44. 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.
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.
c. Add the following parameters at the bottom of the file that is displayed: Parameter Description Values Required ems_enable Enables EMS. Specifically, this parameter defines whether to run the processes for monitoring EMS messages. YES or NO Yes List of hostnames separated by spaces or commas Yes Default value: NO ems_hostnames Identifies the NonStop servers for which a Telnet session will be established. Each specified hostname can then have other parameters associated with it.
Parameter Description Values Required ems_username_ NSserver Specifies the user ID for the Telnet session. Username Yes ems_password_ NSserver The password for the specified user ID for the Telnet session. After you set this parameter, the value is displayed as ****** in the configuration file. Password Yes ems_notify_enable Enables EMS messages to be generated for notifications.
Parameter Description Values Required ems_notify_wait_ timeout Specifies the number of seconds to allow the host to process commands before VTS expects to prompt for another command. Typically, this should be 2-3 seconds but it causes no harm to allow more time for the host. Integer No Integer No YES or NO No Integer No Integer No Default value: 20 ems_notify_logout_ timeout Specifies the number of seconds to wait after issuing the LOGOUT command and before closing the socket connection.
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 Yes 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.
Parameter Description Values Required ems_service_ answer_type Specifies the service response. Expression No Expression No 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. Default value: logon (set for _TYPE:SAFEGUARD) ems_login_ userprompt_type Defines the user prompt during the login process.
Parameter Description Values Required ems_login_ passprompt_type Defines the password prompt during the login process. See ems_service_answer_type for an explanation of type. Expression No Expression No Expression or null No Default values: • for _TYPE:TACL: /Password:\s*$/i • for _TYPE:TACLS: /Password:\s*$/i • for _TYPE:XYGATE: /Password:\s*$/i • for _TYPE:SAFEGUARD: /Password:\s*$/i ems_login_ passanswer_type Defines the password response shown during the login process.
Parameter Description Values Required ems_vaults_ NSserver Restricts access to vaults from any hosts. List of vaults separated by spaces or commas No ANYSYS is not valid here. This list of permitted vaults should be specified as a space-delimited list. For any host, if there are no vaults specified here then all vaults are accessible. Leading slashes in the vault list are optional. ems_mount_delay Specifies the minimum number of seconds that must elapse after VTS receives a mount request.
ems_hostaddr_DEV2='192.168.50.66' ems_hostdevs_DEV2='$TAPE25' ems_virtdevs_DEV2='VTAPE25' ems_username_DEV2='super.
d. Click SAVE to save all changes. 3. Click RESTART on the Virtual Media - Mounts and Locks page to restart the EMS service. Or, click Start EMS Service on the Supervisory Functions page. You must start or restart the service to enable VTS to reread the configuration file. The following table lists the messages that are generated by VTS. Here is an explanation of the information for each EMS message: • The message text.
Message Text Severity Recommended Action Error: $jobname ENDED $jobnumber to $backupSystem Canceled by operator Warning Error: $jobname ENDED $jobnumber to $backupSystem Unable to create temporary link Critical Check the Virtual Media - Mounts and Locks page to ensure that the virtual tape exists on the system and that another process has not locked the virtual tape.
Message Text Severity Recommended Action Error: Can't get lock for $cart_request. Critical Check the Virtual Media - Mounts and Locks page to ensure that the virtual tape exists on the system and that another process has not locked the virtual tape. Error: Can't verify lock for $cart_request. Critical Check the Virtual Media - Mounts and Locks page to ensure that the virtual tape exists on the system and that another process has not locked the virtual tape.
Message Text Severity Recommended Action Error: TSM command failure for $cart_request. Warning The tsm_version parameter is not configured properly in the VTS configuration file, which is available on the Supervisory Functions page. Error: Unrecognized product specification; $hsm for $cart_request. Critical The hsm_product parameter is incorrect. Repair and resubmit the request. Error: Unrecognized product specification; $hsm for $cart_request. Critical The hsm_product parameter is incorrect.
Message Text Severity Non-zero return-code ($rc) from NetBackup bprestore Warning Restored $count file(s) Inform Restored $count file(s), rc=$rc Inform vtape_ems.php cancel processing Inform vtape_ems.php processing mount of $tape Inform Warning: hsm_opt_$pool is not defined. Critical The hsm_opt_pool parameter is required but missing from the VTS configuration file, which is available on the Supervisory Functions page.
Enabling SecureVTS SecureVTS is an optional Virtual TapeServer (VTS) software module that enables VTS to encrypt data that is stored on virtual tape. SecureVTS encrypts data when storing it on a virtual tape. Here is how SecureVTS affects tape operations: • When an encrypted tape is mounted, the data that is written to the tape is encrypted. You can also instruct SecureVTS to encrypt data that is already stored on a virtual tape if the tape is not encrypted.
A virtual tape can be encrypted in several ways: • It can be encrypted when it is created. • It can be manually encrypted after it is created. • It can be automatically encrypted when it is added to a pool that is designated as encrypted. • It can be encrypted if the pool in which it resides is designated as encrypted. Similarly, a virtual tape can be decrypted manually or when its pool is decrypted.
Installing the VPD file If VTS was upgraded to 6.03.42, obtain an encrypted Vital Product Data (VPD) file (vpd.enc). This file contains a tricryption ID, which enables VTS to communicate with the key server. You must obtain a VPD file for each system on which SecureVTS will be enabled. Note If you are using a 6.03.42 system, skip this procedure and go to Entering the license key on page 78 to install your license key for the SecureVTS feature. To install the VPD file 1. Obtain the vpd.
Entering the license key The license key is generated based on the hardware ID of the VTS server. Obtain a license key for each system on which SecureVTS will be enabled. Requires Administration group membership To enter a license key 1. On the VTS web interface, click SecureVTS Setup on the navigation pane. 2. If necessary, log in using an account that is a member of the Administration group. Click the Log In button at the top of the page and enter a username and password.
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.
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: • The VTS server provides two Ethernet ports (eth0 and eth1). These ports correspond to ports 1 and 2 on the back of the server. Under normal circumstances, eth0 is used for local IP traffic to access the user interface for the VTS operating system and for mounting communication between VTS and hosts.
The following steps use two sites as an example of enabling Instant DR or AutoCopy between two sites, New York and Los Angeles, connected by a wide area network (WAN): To configure network settings 1. Open a shell on the VTS system. 2. Set up the network interface on each VTS server on which you wish to enable Instant DR. a. Log in as root. b. Enter the root password. See Credentials on page 151 for a list of the default accounts provided on the server. c. At the [root@site default]# prompt, enter Startx.
i. Provide the IP address, subnet mask, and default gateway. In this example, the newyork VTS server is configured with IP address 10.10.2.145, subnet mask 255.255.255.0, and default gateway 10.10.2.1. Note j. eth1 must have a different IP subnet address then eth0. Click OK. k. Select eth1. l. Select Deactivate and then select Activate for the changes to take effect. 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: newyork.tapelabs.com • Aliases: newyork 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.
j. At the [root@site default]# prompt, enter service network restart. The network interfaces are reset: k. Test connectivity by pinging the network connections. At the prompt, enter ping hostname. For example, to ping the New York server, enter ping newyork. Output similar to the following is displayed: 64 bytes from time=0.053 ms 64 bytes from time=0.053 ms 64 bytes from time=0.053 ms 64 bytes from time=0.053 ms newyork (141.36.136.31): icmp_seq=0 ttl=64 newyork (141.36.136.
f. Add the name of all other VTS servers in this file. For example, on the Los Angeles VTS server, enter newyork. 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 ssh-keygen -t rsa. c. Press ENTER to save the file in the default location. This step creates the /home/bill/ .ssh/ directory. d.
7. Check the SSH connection, if you configured SSH. At the command prompt, enter ssh server uptime. For example, on the New York server, enter ssh newyork uptime. The first time you enter an ssh command, a message similar to the following is displayed: 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. 8. Repeat these steps on each VTS server.
• iptables -A INPUT -p tcp -m state --state RELATED -j ACCEPT Only allows connections that are of a related state. A related connection is a new connection that is associated with an existing connection. • iptables -A INPUT -p icmp -j ACCEPT Allows ICMP traffic through (ping and traceroute). This is not required but is helpful when troubleshooting network issues. • iptables -A INPUT -i eth1 -j REJECT Rejects all traffic with the exception of the preceding rules.
88 | Enabling Instant DR and AutoCopy
Enabling Enterprise Integration and Migration Enterprise integration enables a backup management application (BMA) 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 BMA client on the VTS server and configure the VTSPolicy command in conjunction with the Event Management Service (EMS) on VTS.
The BMA client must be installed on the VTS server, which is based on the Linux operating system. The BMA treats VTS as a UNIX host on the enterprise network. Virtual tapes are then migrated to the tape library managed by the BMA server according to policies set by the BMA administrator. The BMA server can migrate virtual tapes using the following methods: • The BMA administrator creates a backup job on the BMA server and schedules it to run on the BMA 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.
Configuring migration Be sure that the BMA client is installed and configured on the VTS server. Refer to the BMA product documentation for more information. Then, modify the VTS configuration file to configure migration, which entails configuring the hsm_ parameters as defined below. Note A default configuration file is defined for each VTS server. To override the default settings, you must define settings as described below.
Parameter Description Values Req’d? hsm_backup_pools For Backup Express only: Pool names, separated by spaces Yes checksum, EOJ, or retention Yes checksum, EOJ, or retention Yes No Specifies the restore device. Name of the restore device. For Tivoli Storage Manager only: Path Yes Path No Policy Yes Schedule Yes YES or NO No Integer, from 0-999 No Specifies the pool names where the virtual tapes to be migrated reside.
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 BMA should search its catalog for the file to be restored.
• Tivoli Storage Manager: hsm_enable="YES" hsm_product="TSM" hsm_optfile="dsm.opt" hsm_optfile_E1_HAL_10YEARS='/usr/opt/dsm.vts10.opt' ems_hsm_backup_notification="YES" • 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.
98 | 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).
If error 224 occurs on the SCF, perform the following: • Verify that the virtual tape is 519X or 5257 definition. • Confirm emulation by checking debug.log for a [filter] entry. • 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, perform the following: • Check the System Overview page to find the virtual tape device in question. • Erase expired virtual tapes to clear disk space.
File system Verify the following: • Has anything changed? • Is performance slow? • Is GFS or NFS 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 database (halt VTS before issuing these commands): • /etc/init.d/httpd stop • /etc/init.d/httpd start • /etc/init.
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.
If EMS auto-mounting is not functioning, perform the following: • Check the TACL user ID for access privileges. • Check the Ethernet cable. • Check Ethernet connectivity and activity LEDs. • Click RESTART on Mount Maintenance. • Verify that the virtual tape drives are available and that the virtual tape exists and is not in use. The requested virtual tape may be in an autoloader that is currently in use.
Event log file VTS provides many log files for troubleshooting issues with various functions of the system. For example, the EMS log contains all messages (dependant on filters) received from the NonStop server and the responses sent from VTS. VTS adds text that describes successful or unsuccessful mounts, VTSPolicy commands that were interpreted, and so on. This file enables you to diagnose the EMS configuration to and from the NonStop.
-rw-rw-r--rw-rw-r--rw-rw-r-- 1 1148 Aug 1 1038 Aug 1 4521 Aug 2 04:02 ../log/event.log.2.gz 4 04:02 ../log/event.log.1.gz 4 12:41 ../log/event.log System event log format Each message entry in the file follows the same format, as shown in the following example: 2006-08-28 16:25:18|WARNING|440002|5900-E| 127.0.0.
Message Attributes Character limit Message ID 6 Machine ID 6+ IP address 7-15 Server Name 1-255 User 1-255 Message Text 1-255 Message severity The severity attribute indicates the potential impact of the event or condition that the message reports. The following table lists the severity levels for log messages, starting from the lowest level of impact to the highest. Severity ID Severity Level Description 2 INFO A normal operation.
User auditing example Access control can be configured to generate log messages and audit events when a user changes the configuration or invokes management operations on any resource within VTS. For example, if a user deletes a pool or edits the VTS configuration file, access control would write a message to the log file. Each action/event would have a message ID assigned to it.
Severity ID Subsystem ID Event ID 2 20 2 Subsystem Message text 004 EMS mount Read-Only ems telnet ems mount of TAPE by HOST as read-only 20 005 EMS unmount ems telnet ems dismount of TAPE by HOST 4 20 006 EMS cancel mount ems telnet cancel mount of TAPE 6 20 007 EMS cancel mount ems telnet cancel mount of TAPE failed 8 20 007 EMS Mount ems telnet mount of TAPE failed: Tape missing 4 20 008 EMS Mount Read-Write ems telnet ems mount of TAPE by HOST as read-write 8 20 008
Severity ID Subsystem ID Event ID 2 20 2 Subsystem Message text 040 EMS Policy BEX ems telnet BEX POLICY 20 041 EMS Policy BEX ems telnet BEX completes, rc=0 8 20 042 EMS Policy BEX ems telnet BEX completes, rc=RC 2 20 050 EMS Policy TSM ems telnet TSM POLICY 2 20 051 EMS Policy TSM ems telnet TSM2 completes, rc=0 8 20 052 EMS Policy TSM ems telnet TSM2 completes, rc=RC 2 20 060 EMS Policy NetBackup ems telnet NBP POLICY 2 20 061 EMS Policy NetBackup ems telnet NB
Severity ID Subsystem ID Event ID Subsystem Message text 2 20 103 EMS Autocopy ems telnet AutoCopy accepts mount of PATH on HOST 2 20 104 EMS TMF ems telnet TMF accepts mount of PATH on HOST 2 20 133 EMS Policy Migrate Cartridge PATH un-migrated 6 20 133 EMS Policy Migrate Cartridge PATH un-migrate failed path in use rc=RC 8 20 133 EMS Policy Migrate Cartridge PATH un-migrate failed rc=RC 8 20 202 EMS Policy Mount ems mount request for TAPE from HOST failed to queue 8 20
Severity ID Subsystem ID Event ID Subsystem Message text Cartridge maintenance 2 21 010 Cartridge created Cartridge TAPE created in Pool POOL 4 21 010 Cartridge created Cartridge TAPE not created in Pool POOL 2 21 011 Cartridge deleted Cartridge TAPE deleted in Pool POOL 4 21 011 Cartridge deleted Cartridge TAPE not deleted in Pool POOL 6 21 011 Cartridge deleted Cartridge TAPE not deleted in Pool POOL because it is locked.
Severity ID Subsystem ID Event ID 2 22 2 2 Subsystem Message text 009 Set Pool to Autoloader vtape_pool libApply change autoload PATH from PATH to PATH 22 010 Set Pool to Autoloader vtape_pool libApply set autoload PATH 22 011 Remove retention vtape_pool libApply remove retention PATH 2 23 001 Canceled lock ems cancel lock PATH 2 23 002 Canceled mounts/locks page ems cancel mount NNNN 6 23 002 Canceled mounts/locks page ems cancel mount NNNN failed 2 24 001 Job Started m
Severity ID Subsystem ID Event ID Subsystem Message text 6 25 004 Job Retried AutoCopy (retry NN) of TAPE started 2 25 010 EMS AutoCopy ems telnet start autocopy of TAPE for HOST 4 26 001 Scan/Cleanup ScanCleanup cart TAPE in pool POOL is being scheduled for erasure 2 26 003 Scan/Cleanup erase by list submitted 2 26 007 Scan/Cleanup ScanCleanup completes 4 26 007 Scan/Cleanup ScanCleanup file system: SYS exceeds threshold 2 27 001 Job Started vtexport Import from /dev/
Supervisor functions Subsystem ID Event ID 2 33 4 Severity ID Subsystem Message text 000 Unblock TapeServer Startup perform UNBLOCK 33 001 Block TapeServer Startup perform BLOCK 4 33 002 Disable Compression perform COMPRESSION_OFF 2 33 003 Enable Compression perform COMPRESSION_ON 4 33 004 Edit VTS Configuration File edit vts.conf 8 33 005 Halt The System system being halted 8 33 006 Reboot The System system being rebooted 2 33 007 View Defaults view vts_default.
Severity ID Subsystem ID Event ID Subsystem Message text 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 accessed factory setting accessed 4 40 002 Factory Setup Access Control RESTORE OPEN defaults have been restored 4 40 003 Factory Setup Access Control RESTORE CLOSED defaults have been restored 4 40 014 Factory Setup Access Control RESTORE PASSWD defaults have been
Severity Subsystem ID Event ID Subsystem Message Text 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 Opened 4 61 002 Restore Open defaults Access Control RESTORE OPEN defaults 4 61 003 Restore Closed defaults Access Control RESTORE CLOSED defaults 4 61 004 Restore CUSTOM defaults Access Control RESTORE CUSTOM defaults 2 61 005 Undo last us
Subsystem ID Event ID 2 64 2 2 Severity ID Subsystem Message Text 001 Rights changed/ altered Access Control Save Rights 64 002 Save rights as CUSTOM Access Control Save Custom Rights 64 004 Change Group Access Control CHANGE USER GROUP for UUUU to GGGG Subsystem ID Event ID Subsystem Message Text 2 71 001 Erase by List EraseByList start 2 71 002 Erase by List EraseByList complete 4 71 002 Erase by List erase-by-list-cron 8 71 003 Erase by List EraseByList command X
Severity ID Subsystem ID Event ID Subsystem Message Text 2 90 004 XML Mount xml_socket id=50 safely mounted VOL 2 90 005 XML Mount xml_socket id=50 no space check mount VOL System Status 8 91 003 Space check chk_space MSG 8 91 004 Space check system_status WARN Troubleshooting | 119
120 | Troubleshooting
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-A, on the HP ProLiant DL585 • VT5900-E, on the HP ProLiant DL385 G2 Requires the View/Manage Configuration and Factory Setup Activities access rights To replace SCSI cards with FC cards and reconfigure VTS 1. Switch all buses to Physical (Tape) mode and block startup. a.
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. There should be no vaults mounted. d. From the terminal window on VTS, open the /etc/fstab file.
f. Remove SCSI cards from the server as follows: Note This order must be followed or the upgrade will not work. Every HP ProLiant DL585 server has SCSI and Fibre Channel cards in the same physical slots. A Fibre Channel card is always in slots 5 and 6. You will see slot numbers on the chassis above each slot. These numbers are visible on the inside and outside of the chassis. The following order of SCSI card removal must be followed: 1.
Here is a snapshot of the SCSI card after it is removed: g. 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. Then, re-install the shipping bracket and make sure the pull tab is secure. h. Place the top cover back in place and secure it. Slide the HP DL585 ProLiant server back into the rack and secure the two quick-disconnect screws on the front panel. i.
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. 2. Remove the SCSI card in slot 4 and install the second Fibre Channel card in slot 4, if necessary. Here is a snapshot of the SCSI card after it is removed: g.
e. For the SCSI buses, set the buses to Virtual or Physical according to the settings that were recorded in step 1e. f. Click Set Limits. 7. 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 device, 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.
PCI Slot Bus Number Card Type Virtual Tape Name 4B 9 SCSI $VTAPE09 5A 14 2G Fibre Fibre 5B 15 2G Fibre Fibre 6A 12 2G Fibre Fibre 6B 13 2G Fibre Fibre 7A 2 SCSI $VTAPE02 7B 3 SCSI $VTAPE03 8A 0 SCSI $VTAPE00 8B 1 SCSI $VTAPE01 As a reminder, here are the slot-to-bus relationships on the VT5900-E (HP ProLiant DL385 G2): f.
Refer to the steps documented in Modifying virtual tape connections on page 35. When changing the properties, change the TARGET from 5 to 0 from the drop-down box. Repeat the steps for each virtual tape connection that needs to be updated. 10. When the startup process is complete, open a terminal window on VTS and log in as root. Using a text editor, remove the lines that were commented out in step 2d on page 122 (remove the # sign in front of each vault, such as #LABEL=/VAULT01 becomes LABEL=/ VAULT01).
Adding Virtual Tape Drives If an additional virtual tape drive is purchased after the initial installation, you can add a virtual tape drive to your Virtual TapeServer (VTS) environment. You must purchase a license for an additional virtual tape device before you can add it to VTS. Requires the View/Manage Configuration and Factory Setup Activities access rights To add a virtual tape drive 1. Make note of the values assigned to the highest numbered physical tape drive: a. Click View Configurations.
c. Click Manage Tape Connections. d. Click Add a new physical tape. The Add Physical Tape page is displayed. e. From the bus drop-down list, select the value that is assigned to all other physical tapes on VTS. In the example above, this value is 2. f. From the target drop-down list, select the value above the target noted in step 1b. In the example, the target value was 1 so you would select 2 here. g. Leave the lun drop-down list set to 0. h. Leave the initiator drop-down list set to 7. i.
4. Add a new virtual 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 virtual tape. The Add A New Virtual Tape page is displayed. c. From the bus drop-down list, select the bus ID to which the host you are currently configuring is connected. For more information, see 2d on page 38. d. From the target drop-down list, select the SCSI ID on which the virtual tape will respond. See 2e on page 38. e.
5. Add a new tape connection, as follows: a. Click Setup Tapes at the bottom of the page to display the Manage Tape Connections page. b. Click Add a tape connection. The Add A Tape Connection page is displayed. c. Select the new virtual tape from the Virtual Tapes section of the page. d. Select the new logical and physical drives from the Logical Tapes section of the page. e. Click Add Tape Connection.
Hardware Information for Legacy Installations This chapter describes the hardware that was shipped for the Virtual TapeServer (VTS) 6.03.39 and 6.03.41 installations. It also provides cabling and Fibre Channel upgrade procedures for the old hardware. Hardware overview For VTS installations that are upgrading to 6.03.42, the following hardware may be installed.
• VTS model VT5902 was built on the HP ProLiant ML530 G2 server: 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 was purchased, additional internal storage may have been purchased for storing virtual tapes, or external storage could have been used.
External disk storage If VTS model VT5900-A or VT5900-C is installed, the following hardware may have been installed for external disk storage. Both models provide 14 hard disk bays, and each hard disk provides 146GB of storage. • VT5905, which was built on the StorageWorks Modular SAN Array (MSA) 1000 and provides a 2TB storage array. Up to four VT5905 may have been installed with VTS depending on the VTS model.
Cabling and connecting VTS Cabling for the various VTS models is described in the following sections.
HVD Bus A HVD Bus B HVD Bus C HVD Bus D LVD Bus A LVD Bus B LVD Bus C LVD Bus D To bus 4 (PCI-X slot 1A) on VTS server To bus 5 (PCI-X slot 1B) on VTS server To bus 6 (PCI-X slot 2A) on VTS server To bus 7 (PCI-X slot 2B) on VTS server Connections from third 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 bus 8 (PCI-X slot 4A) on VTS server To bus 9 (PCI-X slot
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. Optional six SCSI disks (146GB or 300GB) are available to give this unit internal storage. The six SCSI disks replace the two 36GB drives.
Connecting the HP ProLiant DL380 G3 (VT5901) The VT5901 are built on a 2U (3.5 inch) chassis and provides an internal 72GB DAT72 tape drive and four SCSI buses (limited to two virtual tape drives numbered 1 and 2). This system does not include a Fibre Channel adapter and does not support connection to external storage. In addition, there are five 300GB SCSI drives for storage. Two of the SCSI buses are for connecting external tape drives, if desired. Two of them are for virtual tape drives.
Connecting the HP ProLiant ML530 G2 (VT5902) The VT5902 is a 7U (12.25 inch) chassis and provides eight SCSI bus assignments numbered 3, 4, 5, 6, 9, 10, 11, and 12. A dual-channel Fibre Channel card for connection to external storage is included.
DL380 G4 (VT5900-B, VT5900-C) DL380 G3 (VT5901) ML530 G2 (VT5902) PCI-X Slot Bus # PCI-X Slot PCI-X Slot Bus # 1A 4 4A 6 1B 5 4B 7 5A 8 5B 9 6A 10 6B 11 7 Gb network interface card Bus # Upgrading a SCSI Adapter to a Fibre Channel Adapter SCSI-to-Fibre Channel Adapter Upgrade on page 121 provides instructions to replace one or more SCSI cards with the same number of VTS-supported Fibre Channel (FC) cards. Instructions for the 6.03.
6. Remove SCSI cards from the server as follows: Note This order must be followed or the upgrade will not work. Every HP ProLiant DL585 server has SCSI and Fibre Channel cards in the same physical slots. A Fibre Channel card is always in slots 5 and 6. You will see slot numbers on the chassis above each slot. These numbers are visible on the inside and outside of the chassis. The following order of SCSI card removal must be followed: a.
e. Remove the SCSI card in slot 7 and install the fifth Fibre Channel card in slot 7, if necessary. f. Remove the SCSI card in slot 8 and install the sixth Fibre Channel card in slot 8, 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. Then, re-install the shipping bracket and make sure the pull tab is secure. 8.
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 blue quick-release pull tabs that you need to open. Once loose, grasp the PCI Riser cage and pull up to remove it from the DL380 chassis. Refer to the diagrams on top of the PCI Riser cage if you have any questions about its removal.
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.
On the HP ProLiant DL380 G3 (VT5901) After completing step 2 on page 122, 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.
On the HP ProLiant ML530 G2 (VT5902) The HP ProLiant ML530 has SCSI and Fibre Channel cards in the same physical slots. Slots 2-5 can contain SCSI or Fibre Channel cards. After completing step 2 on page 122, remove the SCSI card(s) and install the Fibre Channel card(s), as follows: 1. From the rear of the HP ProLiant ML530 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.
7. Place the top cover back in place and secure it. Slide the HP ML530 ProLiant server back into the rack and secure the two quick-disconnect screws on the front panel. 8. From the rear of the HP ProLiant ML530 server, reconnect any remaining SCSI cables to the same ports where they were originally connected, if necessary. Because you removed one or more SCSI cards, you will have extra, unused SCSI cables. Reconnect the power cords. Now, continue with step 5 on page 125 and step 6 on page page 125.
150 | Hardware Information for Legacy Installations
Credentials This appendix provides a list of the default usernames and passwords that are configured on the VTS server. It is highly recommended that you change the password for all default user accounts.
152 | Credentials
Specifications The following outlines the physical and environmental specifications of the ProLiant servers on which Virtual TapeServer is shipped: Component Specifications Electrical VT5900-A: • • • • Rated Input Voltage: 100 to 120 VAC/200 to 240 VAC Rated Input Frequency: 50 to 60 Hz Input Power: 1135W @ 110 VAC/1125W @ 220 VAC Rated Input Current: 12A (100 VAC), 9.8A (120 VAC), 4.
Component Specifications Electrical VT5902: • • • • • • Physical Dimensions Rated Input Voltage: 100-127 VAC, 200-240 VAC Rated Input Current: 10A (100 VAC), 4.8A (200 VAC) Rated Input Frequency: 47 to 63 Hz Rated Input Power: 1000W (100 VAC), 960W (200 VAC) Rated Steady-State Power (Output): 600W Maximum Peak Power: 600W VT5900-A: • • • • • Form factor: standard 4U RETMA rack mount chassis Height: 6.94 in. (17.6 cm) Width: 19 in. (48.3 cm) Depth: 26.5 in. (67.3 cm) Weight: 66 lb (29.
Component Specifications Operating Environment VT5900-A: • • • • • • Operating Temperature: 50° to 95° F (10° to 35° C) Non-operating Temperature: -20° to 140° F (-29° to 60° C) Shipping Temperature: -22° to 122° F (-30° to 50° C) Maximum Wet Bulb Temperature: 101.7° F (38.
156 | Specifications
Index Numerics 256-bit AES-CBC encryption 75 A access control overview 43 saving and restoring custom defaults 59 Access Control page, overview 11 access rights, See rights adding physical tape drive 91 vaults for external storage 31 virtual tape drives 129 assigning groups to a user 52 rights to a group 55 attaching physical tape drives to VTS 91 audience vii AutoCopy configuring network settings 80 TCP/IP security 86 enabling 79 automating mounts 61 B backup management applications, See BMAs BMAs integr
D database, troubleshooting 101 default groups 44 users 44 deleting users 53 deployment, overview 17 diagnostic commands 101 tools 99 documentation viii E EMS configuring 61 messages 70 parameters in configuration file 62 troubleshooting 103 ems_enable parameter 62 ems_hostaddr_NSserver parameter 62 ems_hostdevs_NSserver parameter 62 ems_hostnames parameter 62 ems_hostport_NSserver parameter 64 ems_hsm_backup_notification parameter 96 ems_InterSystemCommunication_hosts parameter 68 ems_keep_alive parameter
hsm_policy parameter 95 hsm_pool parameter 94 hsm_product parameter 94 hsm_restore_device parameter 95 hsm_restore_period parameter 96 hsm_schedule parameter 95 hsm_server parameter 94 hsm_summary_limit parameter 96 hsm_username parameter 94 I initiator, description 39 installation checklist 18 overview 17 Instant DR configuring network settings 80 TCP/IP security 86 enabling 79 internal storage for legacy hardware 134 overview 14 Intraserver Communication Service (ISC) 4 introduction 1 L license key for
SecureVTS (cont.) page 11 VPD file 77 SecureVTS.
