HP Virtual Tape for NonStop Servers Crossroads® SurePath™ Virtual TapeServer Installation Guide Version .
Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii Typographical conventions . . . . . . . . . . . . . . . . . . .
6 Reconfiguring and Validating Virtual Tape Connections . . . . . . . . . . . . . . . . . . . . . . . . . .33 Modifying virtual tape connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Validating backups from the NonStop server to the VTS server . . . . . . . . . . . . . . . . . . . . . . 40 7 Configuring Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Enabling a closed system .
Message severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User auditing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
Appendix C, Adding Virtual Tape Drives — Describes how to add a virtual tape drive after installation. Appendix D, Credentials — Provides a list of the default usernames and passwords that are configured on the VTS server. Appendix E, Safety and Regulatory Guidelines — Provides safety information and instructions as well as regulatory statements. Appendix F, Specifications — Describes hardware and environmental specifications for 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. It is available on the documentation CD. • Virtual TapeServer Release Notes, which provides information about system support, known issues, and other information about the current release.
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 the following Backup Management Applications (BMAs): •
Overview of the VTS web interface VTS is managed through a standard web browser interface. Links on the navigation pane on the left side of the page enable you to navigate through VTS functions. The View Configurations, Manage Connections, Supervisor Functions, and Factory Setup links provide setup and management options. The System Status page provides operation status information, most of which is also available on the Virtual Media - Operation page.
VTS — Virtual TapeServer, which refers to the Virtual TapeServer engine and provides the core of VTS functionality. XML — Extensible Markup Language, which is the communication interface that can be used instead of EMS. Connections Displays all current virtual tape connections.
If VTS is not running, this page displays the following message: “TapeServer is not running!” To start VTS, click Supervisor Functions on the navigation pane and then click 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.
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. Various action buttons are available when you select an option on a page. They are automatically highlighted for use when appropriate.
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.
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.
10 | Introduction
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.
• External disk storage You can purchase the following hardware for external disk storage. Both models provide 14 hard disk bays, and each hard disk provides 146GB of storage. • VT5905, which is built on the StorageWorks Modular SAN Array (MSA) 1000 and provides a 2TB storage array. • VT5905-B, which is also built on the MSA 1000 and provides a 4TB storage array. • VT5906, which is an MSA 1000 add-on enclosure and is available if you need additional storage after purchasing and installing the VT5905.
• Fibre Channel upgrade card (VT5900-FCU) To replace a SCSI card with a Fibre Channel (FC) card on a ProLiant server, you can purchase the VT5900-FCU: This FC upgrade card is the HP StorageWorks A6826-60001 network adapter. It is a 2Gb/ sec, dual-port, PCI-X-to-Fibre Channel host bus adapter (HBA). See SCSI-to-Fibre Channel Adapter Upgrade on page 119 for instructions on how to install the card.
• SCSI converter — Allow 1U for the SCSI converter. • External storage — Allow 4U for the VT5905, and allow 3U for the VT5906. Also, the location should be spacious enough to provide good airflow around the unit. 4. Connect the VTS components, and connect VTS to external resources, if necessary. You must connect the NonStop server to VTS or to the SCSI converter. Then you can connect VTS to external disk and tape resources. For precise instructions, see Cabling and Connecting VTS on page 17. 5.
Installation checklist To facilitate an efficient installation, complete these preparations before service personnel arrive on location: • Identify available processor multifunction (PMF), input/output multifunction (IOMF), and ServerNet device adapter SCSI or FCSA Fibre Channel connection locations. • Obtain cables that are long enough to reach between the NonStop server and VTS. Host cables are not included with VTS. • Provide sufficient 110 volt (220/240 volt outside the USA) power outlets.
16 | Installation Summary and Checklist
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. 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.75 inch) VTS SCSI converters.
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. The terminators are required for PMF units through the S72000 models and early S74000 models. To determine if the PMF requires an external terminator, note the PMF model number. Any PMF labeled with a model earlier than 1970-A requires the terminator.
Cable connection order Here is a summary of the VTS server configuration: VTS Model Height # of SCSI Buses # of FC Buses Optical or Magnetic Drives VT5900-E 2U 0, 2, or 4 2, 4, or 6 DVD/CD Four SCSI ports (in slots 4 and 5) and two 4Gb Fibre Channel (FC) ports (in slot 3) are provided in the base hardware configuration. Optionally, one or both of the dual-port SCSI cards in slots 4 and 5 can be replaced with dual-port 2Gb FC cards.
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 119, and you set any of the FC ports to target mode (to connect the port to a virtual device), bus numbering will change. After you replace the SCSI card(s) and reboot VTS, refer to the Manage system limits page in the VTS web interface to see how the buses were renumbered.
SCSI If external SCSI-based storage is used to supplement a VTS server module’s internal storage, the connection is via SCSI cable. Depending on the type of SCSI storage used, different connectivity schemes and cables are required. To connect VTS to SCSI-based external storage that uses a VHDCI connector, use a cable with a male VHDCI connector on the VTS side and the appropriate (male or female) VHDCI connector on the SCSI storage side.
the total cable length must remain under 25 meters (82 feet). For connector specifics and termination requirements, refer to the storage manufacturer's user manual. Cabling to external tape resources The VTS server module is available with six usable I/O ports. Depending on the VTS model and the NonStop server type, these can be SCSI, Fibre Channel, or a combination. These I/O ports can be used for a combination of host or peripheral ports (or both) up to the limits of VTS licensing.
for a single tape drive is limited to 25 meters (82 feet). If multiple devices are daisy-chained on the bus, add the internal and external cable lengths between each device. HVD SCSI An HVD SCSI tape drive connection must be routed through a VTS SCSI converter to convert the LVD SCSI signal to HVD SCSI. A 6-foot male MD68 to male 68 VHDCI SCSI cable connects the VTS server module to the VTS SCSI converter. Use a male MD68 to male MD68 cable to connect the SCSI converter to the HVD tape drive.
Powering up and down Plug the power cords into grounded electrical outlets; it is recommended that the cables be routed to separate power sources for redundancy. Note Power up the SCSI converter before the VTS server module. Power down the SCSI converter before powering down the VTS server module. To power up 1. Power up the VTS SCSI converter using the power switch on the rear panel. 2. Press the power button located on the front panel of the VTS server module.
26 | Cabling and Connecting VTS
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 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 disk resources on page 21 for more information. 2.
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. Add a new partition by entering the following command: n c. Choose the primary partition by entering the following command: p d. Select the first partition by entering the following command: 1 e.
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. Change the ownership of the vault by entering the following command: chown bill.bill /VAULT* b.
32 | 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 NonStop server(s) in the environment can back up data to all virtual tape drives configured in VTS.
Requires the View/Manage Configuration access right To modify the properties of a virtual tape connection 1. Separate the virtual tape drive from its logical and physical counterparts. You cannot reconfigure a virtual tape drive while it is connected to logical and physical drives.
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.
b. Click Delete a tape connection. The Delete A Tape Connection page is displayed: 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.
c. Select the virtual tape drive to edit (the one for which you deleted the connection) and click Edit. The Edit Virtual Tape page is displayed: d. From the bus drop-down list, select the bus ID to which the NonStop host is connected. To determine the bus ID, you must find the PCI slot number on the back of the VTS server module where the SCSI or Fibre Channel cable connects from the card to the target. Labels indicate the bus number for each port. e.
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. You can select 4 as the target ID but you must configure the NonStop S server by specifying “DEVICEID 4” with the SCF ADD TAPE command.
j. 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. This property also specifies the icon selected for the virtual tape on the interface pages. k. In the serial_number field, specify the serial number of your virtual tape. Or, specify a 10-character string that is meaningful to you.
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.
42 | Reconfiguring and Validating Virtual Tape Connections
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.
Below are closed system defaults: • • Users — The following users are defined. Username Group admin Administration operator Operations tapelabs Supervisor Groups — The following rights are assigned to the groups: Note You cannot create new groups but you can modify permissions on the existing groups, and users can be added and removed from the groups. Also, the rights are organized in categories.
Rights Virtual Tape Operations Administration Group X Operations Group X Supervisor Group 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 X Mount Cartridges X X Unmount Cartridges X X View System Status X X X Change Refresh Rate X Stop and Start TapeS
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.
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 Delete Cartridges Description 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 - Instant DR page Virtual Tape Mounts and Locks Grants access to the Virtual Media - Mounts and Locks page Virtual Tape Pool Maintenance Grants access to the Virtual Media - Pool Maintenance page
Saving and restoring custom defaults After configuring users and group rights, you can save all settings as a custom configuration. Later, you can restore these settings by simply clicking the Restore CUSTOM Defaults button in the Defaults and Undo section of the page. This button becomes available after you save a custom configuration. These procedures require the System Access Controls access right To save custom default settings 1. Click the Save as CUSTOM button above the access rights table. 2.
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.
60 | 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.
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 ems_hostnames Identifies the NonStop servers for which a Telnet session will be established. List of hostnames Yes Each specified hostname can then have other parameters associated with it.
Parameter Description Values Required 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. YES or NO No ems_notification_ enable Enables VTS to send notification messages back to the NonStop host from EMS messages.
Parameter Description Values Required ems_notify_logout_ timeout Specifies the number of seconds to wait after issuing the LOGOUT command and before closing the socket connection. Integer No ems_keep_alive Enables VTS to send periodic EMS messages to the host so that the Telnet session does not time out. When enabled, EMS filtering on the host can be increased because VTS stays alive.
Parameter Description Values Required ems_service_select_ type Specifies the service. See ems_service_prompt_type for an explanation of type. Expression Yes ems_login_ command_NSserver Initiates the EMS Distributor on the NonStop server.
Parameter Description Values Required ems_login_ successful_type Defines a command string to send after successful login. Specify this in accordance with the syntax shown in ems_service_prompt_type. Expression or null No ems_vaults_ NSserver Restricts access to vaults from any hosts. List of vaults 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.
Parameter Description Values Required ems_resetdevs_ NSserver Specifies the list of tape names as known to the host system for which we will issue a reset before each mount. The ems_mount_reset parameter is a global override for this and must be enabled for the ems_resetdevs parameter to take effect. You can also specify ALL instead of a list of tapes. If ANYSYS is specified for NSserver, only ALL is recognized.
ems_login_passanswer_TYPE:TACL='%password%' ems_login_successful_TYPE:TACL='/Last Logon:/' ems_login_userprompt_TYPE:TACLS='/login:\s*$/i' ems_login_useranswer_TYPE:TACLS='%username%' ems_login_passprompt_TYPE:TACLS='/Password:\s*$/i' ems_login_passanswer_TYPE:TACLS='%password%' ems_login_successful_TYPE:TACLS='/Last Logon:/' ems_login_userprompt_TYPE:XYGATE='/TACL 1>\s*$/' ems_login_useranswer_TYPE:XYGATE='logon %username%' ems_login_passprompt_TYPE:XYGATE='/Password:\s*$/i' ems_login_passanswer_TYPE:XYGAT
• 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 Recommended Action Error: LEG/BEX/NBP/TSM command failure for $cart_request Critical The EMS Policy for HSM failed. Check the command syntax and context. Repair and resubmit. Error: LEG/BEX/NBP/TSM command failure for $cart_request Critical Error: Non-zero return-code ($rc) from dsmc (try this url … for $cart_request. Critical Error: Non-zero return-code ($rc) from NetBackup for $cart_request.
Message Text Severity Info: $host $code $policy Inform Info: $host $hsm $policy processed # file(s) for $cart_request.
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.
• VTS is based on the HP ProLiant hardware platform, which 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. When Instant DR is configured, eth1 is configured with a routable address to communicate with additional VTS servers at remote locations.
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 127 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-idr 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.
• Aliases: newyork-idr 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. 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.
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-idr. 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-idr (141.36.136.31): icmp_seq=0 ttl=64 newyork-idr (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-idr. 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-idr 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.
82 | 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.
If VTS deletes or erases a virtual tape, the BMA administrator must restore the virtual tape, when necessary. If the NonStop server requests access to a virtual tape that was erased or deleted, the mount request is queued on VTS until the data is recovered by the BMA server from physical tape. • VTS can request that the BMA server perform a backup or restore. This request is generated when you manually initiate a migration. This request is issued using the BMA command-line interface.
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. To confirm that the physical tape device(s) was created and communicating in the operating system, go to the Linux text console and enter the following command: mt -f path_to_drive status Note This step is applicable for physical tape drives only, not libraries. For example, you could enter mt -f /dev/st0 status. Here is a sample of the output from this command: SCSI File Tape Soft 2 tape drive: number=-1, block number=-1, partition=0. block size 0 bytes. Density code 0x0 (default).
3. Add the following parameters at the bottom of the file that is displayed: Parameter Description Values Req’d? hsm_enable Enables migration. YES or NO Yes hsm_product Identifies the BMA: BEX, NBP, TSM, or LEG Yes Hostname Yes Pool name Yes Username Yes Password Yes 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.
Parameter Description Values Req’d? hsm_optfile_pool For Tivoli Storage Manager only: Path No Policy Yes Schedule Yes Specifies the path to the optfile file for a specific pool. This parameter overrides the hsm_optfile parameter for the pool. hsm_policy For NetBackup only: Specifies the backup policy. hsm_schedule For NetBackup only: Specifies the backup schedule. hsm_erase_after_ backup Enables VTS to automatically erase a virtual tape after it is successfully migrated.
Here are sample configurations for each BMA: • Backup Express: hsm_enable="YES" hsm_product="BEX" hsm_server="lab-bex" hsm_username="sysadmin" hsm_password="tapelabs" hsm_backup_pools="MEDIAPOOL DLT DEVICEPOOL" hsm_backup_options="CHECKSUM Y; EOJ_ACTION U; RETENTION 999;" hsm_backup_options_LABELED="CHECKSUM Y; EOJ_ACTION U; RETENTION 999;" hsm_backup_options_CADE="CHECKSUM Y; EOJ_ACTION U; RETENTION 999;" ems_hsm_backup_notification="YES" hsm_restore_period="90d" • NetBackup: hsm_enable="YES" hsm_produc
Configuring and Maintaining GFS for Virtual TapeServer 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.
Configuring GFS To configure GFS, contact your authorized service and support representative to request assistance. No configuration is required on the VTS servers other than configuring the ems_InterSystemCommunication_hosts parameter in the VTS configuration file. See page 66 for a description of this parameter. An Ethernet connection is required between each Linux server (VTS servers and external disk resources). All servers must be connected by Fibre Channel to a disk array.
Shutting down GFS Complete the following steps to shut down GFS, which you must do before rebooting VTS: 1. Unmount GFS /Vaults. umount /VAULT10 Repeat this step until all vaults are unmounted. 2. Stop the Cluster Configuration System process. service ccsd stop 3. Remove GFS locks and shut down the GFS process. gulm_tool shutdown localhost 4. Reboot VTS. If no errors are displayed, it is safe to reboot VTS now that the GFS Cluster is shut down. After reboot, you may need to manually rejoin the cluster.
2. Confirm the Fibre Channel port is available and confirm that the Linux operating system sees the LUN defined for the file system by the storage array. This command will list all SCSI devices.
Adding a vault to a GFS cluster Complete the following steps to create a vault in a GFS cluster: 1. Launch a command prompt on a VTS server in the cluster and log in as root. 2. Choose the partition to use. You can view the /etc/fstab file to see the partitions that are already in use.
7. Determine the name of your cluster by entering the following command: ccs_read file cluster.ccs Here is an example of output from this command. In this example, the cluster name is “Tapeserver.” cluster { name = "Tapeserver" lock_gulm { servers = ["LosAngeles_vts1.crossroads.com", "LosAngeles_vts2.crossroads.com", "LosAngeles_vts3.crossroads.com"] } } 8.
g. To confirm that the partition was successfully mounted and now available, enter the following command: df -h The new vault should now be visible from all VTS servers. To confirm that the new vault is available, display the Virtual Media - Operations page on the VTS web interface and identify all pools.
98 | Configuring and Maintaining GFS for Virtual TapeServer
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. 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-- 1 1038 Aug 1 4521 Aug 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.
Field limits Messages are up to 255 characters in length; each message field has a character limit. The message attributes that have a fixed length (timestamp, message ID, machine ID, IP address) are placed at the front of the message. The attributes that have a variable length are automatically compressed to the available space.
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 Subsystem Message text 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 by HOST as read-only 4 20 008 EMS Mount Read-Write ems telnet ems mount of TAPE by HOST as read-write 2 20 005 EMS unmount ems cancel TAPE for HOST 2 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 telne
Severity ID Subsystem ID Event ID 2 20 6 Subsystem Message text 033 EMS Policy Migrate Cartridge PATH migrated 20 033 EMS Policy Migrate Cartridge PATH migrate failed, path in use, rc=RC 8 29 033 EMS Policy Migrate Cartridge PATH migrate failed, rc=RC 2 20 040 EMS Policy BEX ems telnet BEX POLICY 2 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 P
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 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 Cartridge mainte
Severity ID Subsystem ID Event ID 4 21 4 21 Subsystem Message text 013 Cartridge erased manually Cartridge XXXXX erased in Pool XXXXX 014 Cartridge erased by policy ems telnet Erase by list XXXXX Pool maintenance 2 22 001 Pool created vtape_pool libCreate VAULTXX 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 tix
Severity ID Subsystem ID Event ID 2 24 2 Subsystem Message text 001 Job Started manually IDR start NNNN as MMM 24 002 Job Started by policy Instant Disaster Recovery job XXXXX has been started via policy XXXXX 2 24 003 Job successful Instant Disaster Recovery job XXXXX completed successfully 8 24 004 Job Failed Instant Disaster Recovery job XXXXX failed 4 24 005 Job deleted Instant Disaster Recovery job deleted 4 24 006 Job Completed Instant Disaster Recovery job Completed
Severity ID Subsystem ID Event ID Subsystem Message text 2 26 007 Scan/Cleanup ScanCleanup completes 4 26 007 Scan/Cleanup ScanCleanup file system: SYS exceeds threshold 2 26 003 Erase by list submitted erase by list submitted 2 27 001 Job Started vtexport Import from /dev/stN 2 27 002 Job Successful vtexport Import complete for PATH unloading TAPE 8 27 003 Job Failed vtexport Import WHY for PATH 2 28 001 Job Started vtexport Export to /dev/stN 2 28 002 Job success
Severity ID Subsystem ID Event ID 2 29 8 29 Subsystem Message text 008 Backup Express policy job completed Cartridge XXXXX migrate job to XXXXX completed successfully via Backup Express 009 Backup Express policy job failed Cartridge XXXXX migrate job to XXXXX failed via Backup Express Transaction Management Facility (TMF) Copy 2 30 001 EMS start TMF copy ems telnet start TMFcopy of TAPE to TAPE for HOST Supervisor functions Subsystem ID Event ID 2 33 2 Severity ID Subsystem Messag
Severity ID Subsystem ID Event ID Subsystem Message text 2 35 004 EMS Started perform EMSCONTROL_START 2 35 005 EMS stopped perform EMSCONTROL_STOP 2 35 007 XML Started perform XMLSART 2 35 008 XML stopped perform XMLSTOP 2 35 010 ICS Started perform VTSISC_START 2 35 011 ICS stopped perform VTSISC_STOP Severity ID Subsystem ID Event ID Subsystem Message Text 4 40 001 Factory Setup accessed factory setting accessed 4 40 002 /access/ rebuild.
Subsystem ID Event ID Subsystem Message Text 2 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 Opened 4 61 002 Restore Open defaults Access Control RESTORE OPEN defaults 4 61 00
Severity ID Subsystem ID Event ID 2 62 4 2 Subsystem Message Text 004 Change user group User changed group from XXXXX to XXXXX 64 001 Rights changed/ altered Access Control rights have been altered 64 002 Save rights as CUSTOM Access Control settings have been saved as CUSTOM Rights Miscellaneous features Subsystem ID Event ID Subsystem Message Text 2 71 001 Erase by List Erasebylist start 2 71 002 Erase by List Erasebylist complete 6 71 003 Erase by List Erasebylist c
SCSI-to-Fibre Channel Adapter Upgrade This appendix provides instructions to replace one or more SCSI cards with the same number of VTS-supported 2Gb Fibre Channel (FC) cards on the VT5900-E. 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. On the VTS web interface, click Factory Setup on the navigation pane. b.
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.
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 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. The Manage system limits page is displayed.
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 37. d. From the target drop-down list, select the SCSI ID on which the virtual tape will respond. See 2e on page 37. 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.
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.
128 | Credentials
Safety and Regulatory Guidelines This section contains three types of required safety and compliance statements: • Regulatory Compliance • Waste Electrical and Electronic Equipment (WEEE) • Important Safety Information Regulatory compliance statements The following regulatory compliance statements apply to the products documented by this manual. FCC compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.
Korea MIC compliance Taiwan (BSMI) compliance Japan (VCCI) compliance This is a Class A product based on the standard or the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case the user may be required to take corrective actions.
Compliance with these directives implies conformity to the following European Norms (the equivalent international standards are in parenthesis): • EN55022 (CISPR 22) - Electromagnetic Interference • EN55024 (IEC61000-4-2, 3, 4, 5, 6, 8, 11) - Electromagnetic Immunity • EN61000-3-2 (IEC61000-3-2) - Power Line Harmonics • EN61000-3-3 (IEC61000-3-3) - Power Line Flicker • EN60950-1 (IEC60950-1) - Product Safety Laser compliance This product may be provided with an optical storage device (that is, CD
Not for external use CAUTION: NOT FOR EXTERNAL USE. ALL RECEPTACLES ARE FOR INTERNAL USE ONLY. ATTENTION: NE PAS UTILISER A L'EXTERIEUR DE L'EQUIPEMENT IMPORTANT: TOUS LES RECIPIENTS SONT DESTINES UNIQUEMENT A UN USAGE INTERNE. VORSICHT: ALLE STECKDOSEN DIENEN NUR DEM INTERNEN GEBRAUCH. High leakage current To reduce the risk of electric shock due to high leakage currents, a reliable grounded (earthed) connection should be checked before servicing the power distribution unit (PDU).
Specifications The following outlines the physical and environmental specifications of the ProLiant servers on which Virtual TapeServer is shipped: Component Specifications Electrical Input Power • Rated Line Voltage: 100 VAC, 120 VAC, 200-240 VAC • Rated Input Current: 10A (at 100 VAC), 9A (at 120 VAC), 6.
134 | Specifications
Index A access control overview 43 saving and restoring custom defaults 58 Access Control page, overview 9 access rights, See rights adding physical tape drive 85 vault to GFS cluster 95 vaults for external storage 29 virtual tape drives 123 assigning a group to a user 51 attaching physical tape drives to VTS 85 audience viii AutoCopy configuring network settings 74 configuring TCP/IP security 80 enabling 73 automating mounts 61 B backup management applications, See BMAs BMAs integration 83 supported by VT
ems_hostport_NSserver parameter 64 ems_hsm_backup_notification parameter 89 ems_InterSystemCommunication_hosts parameter 66 ems_keep_alive parameter 64 ems_login_command_NSserver parameter 65 ems_login_passanswer_type parameter 65 ems_login_passprompt_type parameter 65 ems_login_successful_type parameter 66 ems_login_useranswer_type parameter 65 ems_login_userprompt_type parameter 65 ems_mount_delay parameter 66 ems_notification_enable parameter 63 ems_notification_level parameter 63 ems_notify_enable param
M Manage Connections page 8 Manage system limits page 86 migration configuration parameters 88 overview 83 mounting automating 61 N network settings for the VTS server 27 NonStop server troubleshooting 99 validating backups to VTS 40 O open (access) system 43 Operation page 6 overview installation 13 VTS 1 VTS models 11 web interface 4 P passwords, modifying any user’s 49 yours 50 physical tape drive, adding 85 pools definition 2 powering VTS up and down 25 product overview 1 ProLiant server, troubleshoo
virtual tape drives adding 123 definition 2 virtual tapes definition 2 operations, troubleshooting 104 VT5900-E 11 VT5900-FCU 13 VT5905 12 VT5905-B 12 VT5906 12 VT5906-B 12 VT5915 12 VT5916 12 VTS overview 1 overview of models 11 server module, troubleshooting 100 W web interface overview 4 troubleshooting 101 X XML service 5 138 | Index
