Installation Guide - HPE Support Center

Installation Guide - HPE Support Center
Installation Guide
HP Virtual TapeServer for NonStop Servers
Part Number: 514105-001
Product Version: 6.04
© 2004 - 2008 Hewlett-Packard
All rights reserved
No part of this document may be copied in any form or by any means without prior written
consent of HP.
All drawings, schematics and artwork used in the manufacture of the products described
herein are copyrighted. Reproduction of said drawings, schematics and artwork or
manufacture of said products without written consent of HP is absolutely prohibited.
Document History
Part Number
Publish Date
514105-001
528654-008
528654-007
528654-006
528654-005
528654-004
528654-003
December 2008
March 2008
June 2007
September 2006
May 2006
January 2006
July 2005
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Typographical conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Supported release version updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viii
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
The virtual environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Overview of features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview of the VTS web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
System Status page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Virtual Media pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
System Overview page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Manage Tape Connections page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Supervisory Functions page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Access Control page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SecureVTS page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Factory Setup page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2
Installation Summary and Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
New installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Internal disk storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
External disk storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
SCSI converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Fibre Channel upgrade card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Upgraded installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Overview of the VTS deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3
Cabling and Connecting VTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Cabling from Integrity NonStop servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Cabling from NonStop S-series servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Cabling the NonStop S-series server to the SCSI converter . . . . . . . . . . . . . . . . . . . . . . . 20
Checking SCSI termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Cabling the SCSI converter to VTS server module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Cable connection order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connecting the VT5900-E or VT5900-H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connecting the VT5900-G or VT5900-J . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Cabling to external disk resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Path failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Contents | iii
Cabling to external tape resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI LVD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HVD SCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to the LAN, SAN, and power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to a LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to a SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Powering up and down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
26
27
27
27
27
28
28
28
4
Configuring Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
5
Installing GFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
6
Configuring Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
7
Configuring and Validating Virtual Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Adding a virtual tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Modifying virtual tape connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Configuring the NonStop BladeSystem Cluster I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Validating backups from the NonStop server to the VTS server . . . . . . . . . . . . . . . . . . . . . . 56
8
Configuring Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Enabling a closed system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Managing users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Creating a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Changing any user’s password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Changing your password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Assigning a user to a group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Deleting a user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Configuring groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Saving and restoring custom defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
9
Configuring EMS Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
10 Enabling Instant DR and AutoCopy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Configuring network settings on all VTS servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Configuring TCP/IP security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
11 Enabling Enterprise Integration and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Adding a physical tape drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Configuring migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
12 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Diagnostic techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
PuTTY (Telnet/SSH client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Virtual Network Computing remote control software . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
HP health monitoring utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
HP Integrated Lights-Out (iLO) and HP Integrated Lights-Out 2 (iLO 2) . . . . . . . . . . 116
Common issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
NonStop server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
VTS server module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
iv | Contents
Host server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hard drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Web interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
External storage or the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Management System (EMS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Virtual tape operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SecureVTS and failed tape operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Location, retention, and rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System event log format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Field limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User auditing example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
117
117
118
118
118
119
120
120
120
121
121
122
123
123
124
125
125
126
126
126
A
Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
B
SCSI-to-Fibre Channel Adapter Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
C
Hardware Information for Legacy Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Hardware overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
SCSI converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Internal storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
External disk storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Fibre Channel upgrade card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Cabling and connecting VTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Connecting the HP ProLiant DL585 G1 (VT5900-A) . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Connecting the HP ProLiant DL380 G4 (VT5900-B and VT5900-C) . . . . . . . . . . . . . . . 151
Modifying virtual tape connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Upgrading a SCSI Adapter to a Fibre Channel Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
On the HP ProLiant DL585 G1 (VT5900-A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
On the HP ProLiant DL380 G4 (VT5900-B and VT5900-C) . . . . . . . . . . . . . . . . . . . . . . 155
D Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
Contents | v
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.
This guide provides procedures for all tasks you must perform to start using VTS, including
cabling, hardware, configuration, licensing, and troubleshooting information.
Audience
VTS is designed for use by a storage area network (SAN) administrator or IT professional who
typically works with large data centers and is responsible for ensuring that data backups
occur in the organization. This document is designed for personnel who install or maintain
VTS. The audience should be familiar with configuring backup applications, Ethernet and
Fibre Channel networks, and tape libraries.
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.
Monospace
Used for output text, command names and arguments
(syntax), code, file content (such as parameters), and
command-line text.
Monospace Italic
Represents variables within command syntax, code, or
command-line text.
Blue Text
Used for cross-references and URLs that are hyperlinks.
This icon is used throughout the guide to note the access right(s) required to perform the
procedure that follows.
Preface | vii
Related documentation
In addition to this installation guide, the following documentation is provided:
•
Virtual TapeServer Operations and Administration Guide, which describes how to use the
VTS web interface to manage VTS.
•
Virtual TapeServer Release Notes, which provides information about system support,
known issues, and other information about the current release. Please see your Technical
Support representative for a copy of the release notes for this software release for any
updated information on the product.
Supported release version updates
This guide supports all J06 release version updates (RVUs), all H06 RVUs, and all G06 RVUs,
until otherwise indicated in a replacement publication.
Support
Call the HP Global Mission Critical Solution Center (GMCSC) for support. For the fastest
possible resolution, have the following information available:
•
Your company’s name
•
Virtual TapeServer model number
•
Serial number of your equipment
•
Hardware configuration
•
Software configuration
•
The “Software version” value, including the date created, from the System Status page on
the VTS web interface
•
A detailed description of the problem you are having with the equipment
•
Your name, telephone number, fax number, email address, and company address
viii | 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, or virtual tape storage, can
significantly improve performance, allows users to plan backup and archiving strategies, and
enables users to manage data retention and disaster recovery operations.
Virtual TapeServer (VTS) is a fully integrated virtual tape, hardware and software solution.
VTS allows host systems to read from and write to a local or SAN-attached file system. Data
is automatically migrated to a tape device based on policies or manually migrated to physical
tape for archival storage or disaster recovery, if long-term backup copies are required. The
integrated support for backup management application software provides policy-driven
mechanisms for writing to physical tape drives and libraries.
For every host connection to VTS, the host system “sees” a tape drive; the virtual tape drive
emulates the type of tape drive specified during the initial installation and setup process.
Virtual tape drives behave just like real tape drives without the problems generally
associated with real tape drives.
VTS delivers reliable, scalable, and high performance virtual tape for backup and restore,
Transaction Management Facility (TMF), and archive and data recovery operations. You can
deploy VTS to simplify and streamline traditional tape operations, reduce costs for storage
1
hardware and tape media, automate backup and restore operations, and increase flexibility in
managing backed-up data.
The virtual environment
The basic building blocks of VTS are vaults, pools, virtual tape drives, and virtual tapes. VTS
can support multiple virtual tape drives that respond to tape commands just as a physical
tape drive would.
Virtual pools are organized into vaults, which correspond to areas of the file system that are
configured according to user needs. Most frequently, vaults include the entire file system,
though defining several vaults is a convenient way to separate data for different applications
or users. As an analogy, think of a vault as a file system. Multiple RAIDs can be attached to
most VTS models, enabling you to define multiple vaults.
Virtual tapes are “stored” in pools, which are the equivalent to magazines of cartridges used
in tape drive libraries. A pool can contain as many virtual tapes as necessary for a given
application, which provides a great advantage over cartridge magazines that have physical
limits to the number of cartridges they can contain. A pool is synonymous with a directory on
a file system.
Note
The VTS web interface refers to virtual tapes as “cartridges.” Note that these terms
are synonymous in VTS.
Virtual tape drives respond to mount, write, rewind, read, and unload commands from
standard host applications. Virtual tape drives require virtual tape media, and VTS enables
you to create an unlimited number of virtual tapes. A virtual tape is the logical equivalent to
a physical tape. However, unlike physical tape media, virtual tapes can be created in any size
because the data is pooled on low-cost disk storage. A virtual tape contains only the data
written to it, with no wasted space. When a virtual tape is no longer needed, it can be
discarded just like a physical tape. A virtual tape is synonymous with a file in a directory.
2 | Introduction
Overview of features
The following VTS features enable you to simplify and streamline tape operations, reduce
costs for storage, automate backup and restore operations, and increase flexibility in
managing backed-up data:
•
Flexible and extendable, enabling you to create any number of virtual tape pools that
“contain” any number of virtual tapes
•
Compatibility with Backup, Restore, and TMF
•
Compatibility with Mediacom and DSM/TC
•
Support for backup management applications, including IBM Tivoli Storage Manager,
Symantec Veritas NetBackup, Syncsort Backup Express, and EMC Legato Networker
The heart of VTS is a middleware tape emulation engine that enables VTS to emulate tape
storage to host servers and provides backup storage for the data on industry standard, lowcost disk arrays. Data stored in VTS can later be copied to real tape media for archival storage
or disaster recovery if long-term backup copies are required. The advantages of this approach
include the following:
•
Access to data in VTS is almost immediate, and there is no tape to mount or rewind and
no searching through tape volumes for data files.
•
If additional tape storage is needed, you can create virtual tapes using the VTS web
interface without involving the host server. Tapes exported by VTS are identical to those
made by the application directly and can be read on any NonStop server, including sites
without VTS.
•
VTS allows multiple hosts to perform up to 32 simultaneous backups per VTS server. Up
to one virtual tape drive (VTD) is supported per SCSI bus, up to four VTDs are supported
per Fibre Channel port, and up to 32 VTDs are supported per VTS server.
•
Data compression — Allows VTS to compress files as they are written to disk storage
devices. Its use can double the available storage capacity and reduce the amount of
associated storage costs. This feature uses an “on-the-fly” compression algorithm that
creates little processor overhead and can increase performance and throughput by
decreasing the volume of data written to disk.
Optional features that further enhance the benefits of VTS include the following:
•
Global File System (GFS) support — Offers enhanced access to shared vaults and
eliminates single points of failure by deploying multiple VTS systems into a set of
clustered nodes. In the event of a failure, GFS enables any active VTS system in the
cluster to have access to the data, ensuring uninterrupted service to host systems.
•
AutoCopy and Instant DR — Enables the creation of a disaster recovery plan by
efficiently copying or synchronizing backup data between a local VTS server and one or
more remote VTS sites. These features allow for maintaining one or more copies of backup
data at a remote site. AutoCopy automatically copies a virtual tape from one VTS system
to another when the virtual tape is mounted, modified, and dismounted by the host
server. Instant DR uses a delta-difference engine to identify data on a virtual tape that
has changed from one backup to the next. After the initial backup is copied to one or more
remote locations, only that portion of the backup data that has changed since the last
backup is transmitted from the local site to the remote site.
Introduction | 3
•
SecureVTS — Encrypts and decrypts backup data written on disk from one or more host
servers. Compliance regulations and organizations highly recommend the encryption of
valuable data; SecureVTS provides a robust encryption solution that deploys on existing
hardware. Industry-standard 256-bit AES symmetric key encryption is used.
Overview of the VTS web interface
VTS is managed through a standard web browser interface. 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.
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. This section also lists any patches that are installed on the
server.
Services
Displays the current services that are enabled on the system and whether they are
running. The following services may be listed:
ISC — Interserver Communication Service, which enables communication between
VTS servers that have equal access to some or all virtual tapes. Servers in the ISC
ring notify the others whenever they satisfy a mount request.
4 | Introduction
EMS — Event Management Service, which starts the EMS distributor on the
NonStop server by issuing a Tandem Advanced Command Language (TACL)
command. The distributor notifies the VTS EMS service when an EMS message is
posted on the NonStop server.
VTS — Virtual TapeServer, which refers to the Virtual TapeServer engine and
provides the core of VTS functionality.
SecureVTS
If SecureVTS is enabled, this section displays its status.
Free Space
Optional section that is shown by default. 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. The following information is listed:
host — The name of the virtual tape drive
type — The type of drive that the virtual tape drive is emulating
command — The last command sent to the tape drive
status — The status of the last command executed by the tape drive
kb/sec — The amount of data that is being transferred to the tape drive per second
c/ratio — The compression ratio, if compression is enabled
Options
Buttons to change the system refresh rate. By default, the system automatically
refreshes the page every 15 seconds. The following buttons are available:
Refresh Now: Refreshes information on the page immediately.
Stop Refreshing: Stops refreshing the page and removes the Stop Refreshing and
Change Rate buttons. After you click this button, the Auto Refresh button is
displayed.
Auto Refresh: Instructs VTS to automatically refresh the page (according to the
refresh rate). After you click this button, the Stop Refreshing and Change Rate
buttons are displayed.
Change Rate: Sets a refresh rate.
Virtual Media pages
Most tasks are performed on the Virtual Media page, including managing the following:
•
Cartridges (virtual tapes)
•
Pools
•
Mounts and locks
Introduction | 5
•
Imports and exports from and to physical drives
•
Instant DR operations
The Virtual Media - Operation page is the homepage, though you can click Virtual Media on
the navigation pane to display the Virtual Media - Operation page again. The refresh button
at the top of the page enables you to update the information displayed on the Virtual Media
page.
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.) 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 drives correspond to vaults that were configured before VTS shipped.
You can sort the contents of the table by clicking a column heading; by default, the contents
are sorted by host device.
•
The size(MB) column indicates whether a tape is unlabeled (empty) or labeled (0). It also
indicates the data capacity that is used after a backup runs. (If a labeled tape is erased,
the value in this column returns to 0.) If you click the link, a pop-up dialog box is
displayed listing tape data.
•
The c/ratio column indicates the compression ratio, if compression is enabled for VTS.
•
If the limit column is displayed, it specifies the pool size limit next to all virtual tapes in a
pool. The limit is set on the Pool Maintenance page.
A red dot in the pool column indicates that the pool contains no virtual tapes. If SecureVTS is
enabled, is displayed in the pool column, indicating that the pool is encrypted. Otherwise,
is displayed. The + symbol indicates that the pool contains virtual tapes. Click + to display the
6 | Introduction
contents of the pool. Click the - symbol to collapse the pool. The colors have the following
meaning:
•
Orange — Locked (mounted, Instant DR, migration, AutoCopy, export, or import)
•
Purple — Autoloading enabled
•
Red — Remotely addressed
•
Black — Available
If you select an option from the window drop-down list, additional pages are available. You
must have the corresponding right(s) to view the pages. 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.
Various action buttons are available when you select an option on a page. They are
automatically highlighted for use when appropriate.
Introduction | 7
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.
8 | Introduction
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.
Introduction | 9
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.
10 | Introduction
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.
SecureVTS page
When you click the SecureVTS Setup option, a page similar to the following is displayed (if
licensing has been enabled and you are logged in):
SecureVTS is an optional Virtual TapeServer (VTS) software module that enables VTS to
encrypt data that is stored on virtual tape. Refer to the SecureVTS chapter for more
information about this feature.
Introduction | 11
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.
12 | 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. These sections provide a
description of each hardware component and how it fits into the VTS environment:
New installations
Here is an overview of the ProLiant hardware that may have been purchased for new
installations:
VTS Server
DL385 G2
(model VT5900-E)
plus one SCSI converter
DL385 G2
(model VT5900-G)
DL385 G5
(model VT5900-H)
plus one SCSI converter
DL385 G5
(model VT5900-J)
Additional
Internal Storage
Additional
External Storage
FC Upgrade
Card
Eight 146GB internal
disks (model VT5904-E)
• One or more
MSA 2000s
(models VT5917
and VT5918)
• One or more
MSA 1500s
(models VT5915
and VT5916)
• One or more
MSA 1000s
(models VT5905
and VT5906)
One 2Gb/sec,
dual-port, PCIX-to-Fibre
Channel host
bus adapter
(model
VT5900-FCU)
N/A
One 2Gb/sec,
dual-port, PCIX-to-Fibre
Channel host
bus adapter
(model
VT5900-FCU)
N/A
13
Servers
Models VT5900-E and VT5900-G are built on an HP ProLiant DL385 G2 server; models
VT5900-H and VT5900-J are built on an HP ProLiant DL385 G5:
Two Fibre Channel cards are installed (for supporting VTDs) in model VT5900-G and
VT5900-J. Two SCSI cards are installed in model VT5900-E and VT5900-H.
Internal disk storage
The VT5900-E, VT5900-G, VT5900-H, and VT5900-J models support optional internal storage
(model VT5904-E) that can be used for storing backup data. Each VT5904-E model provides
eight internal disk drives, each with 146GB of storage capacity.
External disk storage
Note
In addition to the following models, the HP StorageWorks Enterprise Virtual Array
(EVA) is a qualified storage solution for use with VTS. The EVA requires a path
failover connection through two ports on the VTS server to two ports on the EVA.
After cabling the EVA, refer to Path failover on page 25 for information about
configuring path failover.
The following hardware may be purchased for external disk storage.
•
VT5917, which is build on the StorageWorks Modular SAN Array (MSA) 2000fc. It houses
dual controllers, each of which provides two 4Gbps ports (4 in total) and uses 1GB of write
cache memory. The VT5917 also includes 12 1TB 7,200rpm SATA hard disk drives, which
provide 12TB of raw capacity (approximately 9TB when set up as RAID-5 and formatted).
•
VT5918, which is an MSA 2000fc add-on enclosure and is available if additional storage is
needed after purchasing and installing the VT5917. It includes 12 1TB 7,200rpm SATA
disk drives. You can install up to three of these storage arrays per VT5917.
•
VT5915, which is built on the StorageWorks MSA 1500cs. It provides one controller shelf
and one MSA 20 disk shelf, and it includes dual controllers, each of which provides a
single FC port. The VT5915 also includes 12 750GB 7,200rpm SATA disk drives.
14 | Installation Summary and Checklist
•
VT5916, which is an MSA 20 add-on enclosure and is available if additional storage is
needed after purchasing and installing the VT5915. It includes 12 750GB 7,200rpm SATA
disk drives. You can install up to three of these storage arrays per VT5915.
•
VT5905 or VT5905-B, which are built on the StorageWorks MSA 1000 and provide a builtin 8-port FC switch. The VT5905 provides 14 hard disk bays, and each hard disk provides
146GB of storage at 10,000rpm. Each hard drive in the VT5905-B provides 300GB disks.
•
VT5906 or VT5906-B, which are built on the StorageWorks Modular 4314 and available if
additional storage was needed after purchasing and installing the VT5905 or VT5905-B.
Up to two of these can be installed per VT5905 or VT5905-B. The VT5906 provides 14
hard disk bays, and each hard disk provides 146GB of storage. The VT5906-B provides
300GB disks.
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. One SCSI converter
is provided if you purchased the VT5900-E or VT5900-H. Here is a picture of the back of the
SCSI converter:
Installation Summary and Checklist | 15
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.9 m (75 ft)
518-075W
LC-LC, Multimode Fibre cable, 2 m
M8900-02
LC-LC, Multimode Fibre cable, 5 m
M8900-05
LC-LC, Multimode Fibre cable, 15 m
M8900-15
LC-LC, Multimode Fibre cable, 40 m
M8900-40
LC-LC, Multimode Fibre cable, 80 m
M8900-80
Fibre Channel upgrade card
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 a 2Gb/sec, dual-port, PCI-X-to-Fibre Channel host bus adapter
(HBA). See SCSI-to-Fibre Channel Adapter Upgrade on page 141 for instructions on how to
install the card.
Upgraded installations
For VTS installations that are upgrading from 6.03.39 or later, refer to Hardware Information
for Legacy Installations on page 147 for an overview of the hardware and configuration
information supported in previous versions of VTS.
16 | Installation Summary and Checklist
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.
•
If you want to use the Event Management Service (EMS) mounts feature, which
automates the process of mounting and dismounting virtual tapes, know how to configure
MEDIACOM on NonStop servers, including creating pools and tape volumes.
•
Know how to add tape devices to the NonStop BladeSystem Cluster I/O Module (CLIM) if
a CLIM is attached to the NonStop server and the VTS server will be attached through
the CLIM.
Here are the steps you must take to mount and configure the VTS environment:
1. Prepare the operating environment. VTS can operate in any clean, indoor location. Do not
store or place VTS outside of the environmental ranges listed in Specifications on page
157. Keep all enclosure ventilation openings unobstructed and avoid placing VTS in direct
sunlight, rain, or other sources of moisture.
2. Unpack VTS. Carefully unpack and inspect the VTS components. If any damage is
apparent, immediately notify the carrier and your vendor. Save the carton and packing
materials in case you need to return VTS.
3. Mount the VTS components in a 19-inch rack near the host server and close to a power
source:
•
VTS server module — Allow 2U (3.5 inches) for the server.
•
SCSI converter — Allow 1U for each SCSI converter.
•
External storage — Allow 4U for the VT5905 and VT5906, allow 4U for the VT5915
and 2U for the VT5916, and allow 2U for the VT5917 and VT5918.
4. Connect the VTS components, and connect VTS to external resources, if necessary. You
must connect the host server to VTS or to the SCSI converter. Then, connect VTS to
external disk and tape resources. (Part of this step includes configuring external storage
for path failover, if necessary.) For precise instructions, see Cabling and Connecting VTS
on page 19.
5. Connect VTS to the local area network (LAN) and storage area network (SAN), and plug
the power cords into grounded electrical outlets. Power on the VTS server and SCSI
converter(s), if provided. See Connecting to the LAN, SAN, and power on page 27 for
details.
6. Configure network settings as described in Configuring Network Settings on page 31.
7. If necessary, install the Global File System (GFS) as described in Installing GFS on page
33. GFS enables you to cluster VTS systems so that servers can access a shared set of
pools and virtual tapes.
8. Configure licensing as described in Configuring Licensing on page 45.
9. Edit the virtual tape connections to reflect exact connections between the hosts and
virtual tape drives in your environment. VTS is preconfigured with virtual tape
Installation Summary and Checklist | 17
connections. See Configuring and Validating Virtual Tape Drives on page 47 for
instructions.
10. Configure access control. It is recommended that you enable a closed system, which
requires users to authenticate to access resources. You can also configure the default
groups to set privileges for users assigned to the groups. See Configuring Access Control
on page 59 for more information.
11. If Instant DR or AutoCopy is licensed, configure VTS to send EMS messages to the host
server. VTS can process mount message requests, VTSPolicy commands, and Tandem
Advanced Command Language (TACL) heartbeat messages. VTS can send critical and
error event messages to the host server. Complete the procedures in Configuring EMS
Communication on page 79 to configure this communication.
12. If Instant DR or AutoCopy is licensed, configure and activate the feature(s) as described
in Enabling Instant DR and AutoCopy on page 95.
13. To enable VTS to migrate virtual tape to physical tape using a backup management
application, you must configure the backup management application on the VTS server
and then edit the VTS configuration file. See Enabling Enterprise Integration and
Migration on page 105 for more information.
14. If you want to use the HP System Health Application and Insight Management Agents to
monitor VTS, you must configure them. See HP health monitoring utilities on page 116
for more information.
After completing these steps, you can begin using VTS to store data on virtual tape. Refer to
the Virtual TapeServer Operations and Administration Guide for more information about
using VTS for day-to-day storage procedures.
Installation checklist
To facilitate an efficient installation, complete these preparations:
•
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 host server and VTS. Host cables
are not included with VTS.
•
Provide sufficient 110 or 220/240 volt power outlets. VTS uses redundant power supplies,
so consider independent power sources for high-availability operation. Additional power
outlets might be required for external tape drives or RAID storage devices.
•
Secure a monitor and keyboard for temporary use during installation. VTS does not
require a monitor or keyboard for normal operation. However, it is recommended that you
connect a monitor and keyboard when rebooting the system.
•
Obtain a CAT-5 Ethernet cable for connecting VTS to the network.
•
Identify TCP/IP information to assign to VTS:
•
•
Fully qualified domain name
•
IP address
•
Subnet mask
•
Default router (gateway)
•
DNS or DHCP addresses with VTS name entered (DHCP is not supported with GFS)
Identify a system that can be used to access the VTS web interface.
18 | Installation Summary and Checklist
Cabling and Connecting VTS
A critical part of installing Virtual TapeServer (VTS) is establishing the physical connection
between the host server and VTS. Cabling and termination issues are the single largest
contributor to an unsuccessful or delayed installation. Preparing and planning in advance for
the right cables, lengths of cables, connectors, and terminators dramatically increases the
chances of successful installation and simplifies any subsequent troubleshooting.
This section describes cabling between the host server, VTS, and any external disk or tape
storage devices.
Cabling from Integrity NonStop servers
Integrity NonStop servers use native Fibre Channel (FC) to connect to disk and tape
peripherals. The FC connection on the Integrity NonStop server I/O adapter uses a female
LC-type connector. You can connect Integrity NonStop servers directly to the I/O panel on
VTS using the appropriate length male LC-to-LC fiber optic cable.
Note
See Cables on page 16 for a description of cables that may be provided by HP.
Integrity NonStop servers can also be connected to the VTS SCSI converter by using a
NonStop S-series server I/O enclosure. The NonStop S-series IOAM enclosure with an FCSA
is used to bridge the Integrity NonStop server FC to high-voltage differential (HVD) SCSI.
19
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.75 inch) VTS SCSI converters.
The SCSI converter converts high-voltage differential (HVD) Ultra160/SCSI-3 to low-voltage
differential (LVD) Ultra-2 SCSI. It provides four pairs of 68-pin connectors (all female). Each
pair consists of one 68-pin HVD connection (top row) and one 68-pin LVD connection (bottom
row). Up to four SCSI HVD connections can be converted to LVD SCSI for VTS usage. Up to
three SCSI converters come prepackaged with VTS.
The VTS SCSI converter connects to a NonStop S-series server in the same way as a physical
tape device, using a SCSI cable connected to controllers in the NonStop S-series server.
Cabling the NonStop S-series server to the SCSI converter
Connections are made to the PMF, IOMF, and/or ServerNet/DA. These controllers use a
female MD68 connector. The SCSI cable used to connect to the NonStop S-series server must
have a male MD68 connector. The other end must also have a male MD68 connector to plug
into the top row of female MD68 connectors on the VTS SCSI converter. Cable length to the
NonStop S-series server is limited to 25 meters (82 feet). Use high quality cables of the
shortest possible length based on the location of the equipment. PMF, IOMF, and ServerNet
controllers use external or pass-through termination where the cable plugs into the silver
terminator. The PMF 2 and IOMF 2 controllers use internal termination with the cable
plugging directly into the controller.
20 | Cabling and Connecting VTS
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. 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.
Also, a terminator is required when you connect physical tape or disk storage using SCSI.
Each bus (HVD or LVD) requires proper termination. The terminators are typically supplied
with the device hardware.
Cabling the SCSI converter to VTS server module
When the cabling between the SCSI converter and host server is complete, connect the SCSI
converter to the VTS server module. The VTS server module uses LVD SCSI with a VHDCI
style connector. SCSI termination is handled internally, so external termination is not
required.
The SCSI converter uses a female MD68 connector, so the SCSI cable must have a male MD68
connector at that end. The VTS server module uses a female 68-pin VHDCI connector, so the
SCSI cable must have a male VHDCI connector at that end.
The rear of the VTS server module has slots for multiple dual-channel SCSI cards. The
VHDCI SCSI ports on the VTS server unit are clearly visible.
LVD SCSI supports a maximum cable length of 12 meters (39 feet). Because the VTS SCSI
converter is located in the same rack or cabinet as the VTS server module (usually the SCSI
converters are located adjacent to the server module), it is recommended that the cable length
between the SCSI converter and the VTS server module be limited to 2 meters (6.5 feet). Each
VTS model that includes SCSI converters also includes 6-foot male MD68 to male 68 VHDCI
SCSI cables to connect the VTS server module and the SCSI converter.
Cabling and Connecting VTS | 21
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
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
VT5900-H
2U
4
2* (for SAN
connection only)
DVD/CD
VT5900-J
2U
0
6 (2 for SAN
connection, 4 for
VTDs)
DVD/CD
# of FC Ports
Optical or
Magnetic Drives
* Four SCSI ports (in slots 4 and 5) and two 4Gb Fibre Channel (FC) ports (in slot 2) are provided in the base
configuration. Dual-port 2Gb FC cards can be purchased to replace the dual-port SCSI cards in slots 4 and 5.
Note
For the most reliable service, use cables of the highest quality and shortest possible
length based on the location of the equipment in the data center. See Cables on page
16 for a description of cables that may be provided by HP.
Connecting the VT5900-E or VT5900-H
The VT5900-E and VT5900-H are built on a 2U (3.5 inch) chassis and provides four SCSI
buses, numbered 0-3. A dual-channel 4Gb FC card is also provided for connection to the SAN.
This base model allows the use of all four SCSI buses for connecting virtual tape drives (no
ports on the 4Gb FC card can be used for virtual connections).
The recommended cable connection order for the SCSI converter attached to a base model of
VT5900-E and VT5900-H is as follows:
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 0 (PCI-X slot
4A) on VTS server
To bus 1 (PCI-X slot
4B) on VTS server
To bus 2 (PCI-X slot
5A) on VTS server
To bus 3 (PCI-X slot
5B) on VTS server
Note
When attaching NonStop servers to the HVD buses, it is recommended that you
attach to HVD bus D then to HVD bus C and then to HVD buses A and B if necessary.
Also, note that you do not have to use all of the SCSI buses (or converter ports) for
VTDs. You can use the ports as initiators for legacy SCSI tape drives.
22 | Cabling and Connecting VTS
Here is an illustration of the slots on the back of the base model. If the P800 card is installed,
it is placed in slot 3 (below slot 4).
Here is an illustration of the HVD and LVD ports on the back of the SCSI converter:
Note
If you replace one or both of the SCSI cards with the 2Gb FC card(s), as described in
SCSI-to-Fibre Channel Adapter Upgrade on page 141, and you set any of the FC ports
to target mode (to connect the port to a virtual tape drive), bus numbering will
change. 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.
Contact your VTS service and support representative for help correlating bus
numbers to ports on the back of the VTS server.
Connecting the VT5900-G or VT5900-J
The VT5900-G and VT5900-J are built on a 2U (3.5 inch) chassis and provides up to four Fibre
Channel buses, numbered 0-3. A dual-channel 4Gb FC card is also provided for connection to
external storage (buses 4 and 5). This base model allows the use of four 2Gb FC buses for
connecting virtual tape drives (no ports on the 4Gb FC card can be used for virtual
connections).
Here is an illustration of the slots on the back of the base model. If the P800 card is installed,
it is placed in slot 3 (below slot 4).
Cabling and Connecting VTS | 23
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. Then,
present a logical unit number (LUN) that refers to this storage space. Note that each LUN
should not represent more than 2TB of space.
The StorageWorks Modular SAN Array (MSA) will be configured with the storage and
presenting LUNs from the factory. The cable will be LC-to-LC and will originate on one of the
FC ports on the HP VTS. It can be used to connect directly to a FC port of the MSA controller
or can be connected into a FC switch in a shared HP VTS implementation. For additional
storage, the MSA is SCSI cabled to the second unit of disks.
Fibre Channel
Models supporting Fibre Channel can have one or more dual-channel fiber controllers. These
controllers have two female LC fiber connectors. If the external storage unit is a VT5905,
VT5905-B, or StorageWorks MSA, use a male LC-to-LC fiber optical cable to connect the two
units. Other storage units might require a different connector.
Note
As a best practice for the VT5900-G and VT5900-J, use all 4Gb ports first then, if
necessary, connect external storage to the 2Gb ports if they are installed. The 4Gb
ports cannot be used to present virtual tape drives. The 2Gb ports may provide half
the performance as the 4Gb ports and can also be used for presenting virtual tape
drives.
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. To determine connector specifics and termination
24 | Cabling and Connecting VTS
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.
Connecting VTS to SCSI-based external storage that uses a Centronics HVD connector
requires a VTS SCSI converter. Use a cable with a male VHDCI connector on the server side
and a male MD68 connector on the converter side. A second cable is used to connect the SCSI
converter to the SCSI-based external storage. This cable uses a male Centronics connector on
the SCSI converter side and the appropriate (male or female) Centronics connector on the
SCSI storage side. Maximum total cable length between the VTS SCSI converter and the
external SCSI tape drive is 25 meters (82 feet). If a second SCSI tape drive is daisy chained,
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.
Path failover
Path failover is required when more than one physical or logical path exists between VTS and
external disk storage, such as an MSA or HP StorageWorks Enterprise Virtual Array (EVA).
If a path fails, another path becomes active and handles I/O for the LUNs on the failed path.
Only one path is active at a time for a LUN. You can run the multipath -v2 -ll command to
see a list of known multi-pathed disks.
Cabling and Connecting VTS | 25
The Device Mapper Multipath Enablement Kit (dm-multipath and devicemapper RPMs) is
installed by default on the VTS server. You must download the latest version of the
multipath.conf file, which is available here:
http://h20000.www2.hp.com/bizsupport/TechSupport/
SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3559652&prodTypeId=12169&prodSeriesI
d=3559651&swLang=13&taskId=135&swEnvOID=4004
Then, download the latest version of the Device Mapper Multipath Enablement Kit for HP
StorageWorks Disk Arrays Release Notes document from this URL:
http://h20000.www2.hp.com/bizsupport/TechSupport/
DocumentIndex.jsp?lang=en&cc=us&prodClassId=1&contentType=SupportManual&prodTypeId=18964&prodSeriesId=3559651
This document describes how to install and configure the device mapper tools. The following
sections are relevant for the VTS environment:
•
Installing Device Mapper Multipath tools
•
Configuring Device Mapper Multipath to enable HP arrays
•
Setting up Device Mapper Multipath daemon
Cabling to external tape resources
The VTS server module is available with 4-16 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.
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.
Note
Make a note of device IDs and the bus or port numbers to which they are connected.
You need this information to set up VTS.
Fibre Channel
Fibre Channel tape drives can be connected directly to the dual-channel fiber controller
included in some VTS models using a male LC type connector. The connector used on the
opposite end of the cable depends on the Fibre Channel tape drive used.
26 | Cabling and Connecting VTS
SCSI LVD
LVD tape drives can be connected to any SCSI port on the VTS server module that has not
been reserved for use as a virtual tape drive. The VTS server module uses a female VHDCI
connector, so a cable with a male VHDCI is required. Depending on the type of tape drive,
that end of the cable probably uses a male MD68 connector. Two drives can be daisy chained,
and an LVD external terminator is required on the last drive in the chain. SCSI cable length
for a single tape drive is limited to 12 meters (39 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. Up to two drives can be daisy
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.
Port 1 corresponds to Eth0 in Linux, and Port 2 corresponds to Eth1.
Cabling and Connecting VTS | 27
Connecting to a SAN
When defining LUNs on a storage array, start at LUN 0. Otherwise, the Fibre Channel
interface in VTS might not recognize them correctly.
Connecting power
Plug the power cords into grounded electrical outlets; it is recommended that the cables be
routed to separate power sources for redundancy.
Powering up and down
To power up
1. Press the power button located on the front panel of the VTS server module. The power
button on the front panel changes from yellow to green, and the server module self-boots.
Allow the VTS server to completely boot before proceeding. The console will display a
login prompt when it is ready to proceed.
2. Power up the VTS SCSI converter using the power switch on the rear panel.
3. Start tape services on the NonStop server using the SCF START $VTAPE command,
where VTAPE is the name of the tape device. Here is an example of the output of this
command:
SCF - T9082H01 - (04DEC06) (15NOV06) - 10/02/2008 11:58:32 System \DEV5
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
Total Errors = 0
Total Warnings = 0
$SYSTEM SYSTEM 8> SCF STATUS $VTAPE01
SCF - T9082H01 - (04DEC06) (15NOV06) - 10/02/2008 11:58:44 System \DEV5
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
STORAGE - Status TAPE \DEV5.$VTAPE01
LDev State
Primary
Backup
DeviceStatus
PID
PID
289 STARTED
0,312
1,1069
NOT READY
Total Errors = 0
Total Warnings = 0
To power down
1. Stop tape services on the NonStop server by entering the SCF STOP $VTAPE command,
where VTAPE is the name of the tape device. Here is an example of the output:
SCF - T9082H01 - (04DEC06) (15NOV06) - 10/02/2008 11:55:37 System \DEV5
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
Total Errors = 0
Total Warnings = 0
$SYSTEM SYSTEM 6> SCF STATUS $VTAPE01
SCF - T9082H01 - (04DEC06) (15NOV06) - 10/02/2008 11:55:55 System \DEV5
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
STORAGE - Status TAPE \DEV5.$VTAPE01
LDev State
Primary
Backup
DeviceStatus
PID
PID
289 STOPPED
0,312
1,1069
NOT READY
Total Errors = 0
Total Warnings = 0
2. Power down the SCSI converter using the power switch on the rear panel.
28 | Cabling and Connecting VTS
3. Execute the halt command by clicking Supervisor Tools on the navigation pane of the
user interface and then clicking Halt the System.
Allow the VTS server to completely shut down before proceeding. The VTS server’s
console will indicate “System Halted”.
4. Press the power button located on the front panel of the VTS server module. The button
light changes from green to yellow.
Cabling and Connecting VTS | 29
30 | Cabling and Connecting VTS
Configuring Network Settings
By default, Virtual TapeServer (VTS) is configured to use Dynamic Host Configuration
Protocol (DHCP). To change the network configuration, you must connect a monitor,
keyboard, and mouse to VTS before powering it on. To change the default settings, use a
console window and complete the following steps. Before making any changes, obtain a new
IP address, netmask, gateway, and hostname that are appropriate for your site from the
network administrator.
1. Log in as root. See Credentials on page 139 for a list of the default user accounts provided
on the server.
2. Enter startx. The user interface is displayed.
3. From the OS menu, select System Tools→Network Device Control. This displays the
Network Configuration window:
31
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. Select File→Save to save the settings.
8. Click on the Devices tab, select eth0 (or eth1), and click Activate. When prompted, click
Yes to save the changes. Then, click OK on the next popup dialog.
9. To exit the interface, select Logout root from the Linux icon. Click Logout on the popup
dialog that is displayed.
10. Verify the changes by launching a web browser and accessing the VTS web interface by
entering the hostname or IP address of the VTS server.
32 | Configuring Network Settings
Installing GFS
The Global File System (GFS) is an advanced feature that allows Linux servers to
simultaneously read and write files on a single shared file system on a SAN. VTS is based on
Linux, and GFS enables multiple VTS servers to access a shared set of pools and virtual
tapes. The Event Management Service (EMS) can then automatically mount virtual tapes
from the GFS pools as if they were separately mounted. Here is an example GFS
configuration:
With GFS, all VTS servers connect to each other over Fibre Channel to the same storage
array, and GFS allows each VTS to access all vaults at the same time. If a server becomes
unavailable, other servers can still access the vaults.
After installing GFS, you must configure a fencing method for the cluster. You can configure
Fibre Channel switch fencing if the external storage device is connected over Fibre Channel
(for example, if the HP StorageWorks Modular SAN Array provides a built-in Fibre Channel
33
switch). Or, you can configure HP Integrated Lights-Out (iLO) to handle fencing. Refer to the
following for more information about fencing:
•
Fencing overview — http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/
html/Cluster_Suite_Overview/s2-fencing-overview-CSO.html
•
Configuring fencing devices with Conga (luci and ricci) — http://www.redhat.com/docs/enUS/Red_Hat_Enterprise_Linux/5.2/html/Cluster_Administration/s1-config-fence-devicesconga-CA.html
•
All other Red Hat documentation — http://www.redhat.com/docs/manuals/csgfs/
The following topics are relevant: “Red Hat Cluster Suite Overview for RHEL5.2”,
“Configuring and Managing a Red Hat Cluster for RHEL5.2”, “LVM Administrator's
Guide for RHEL5.2”, “Global File System for RHEL5.2”, and “GFS 6.1 Administrator's
Guide”
This chapter describes how to install GFS in the VTS environment. While you can follow the
instructions provided by http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/
html/Cluster_Administration/index.html to configure and manage GFS, this chapter provides
only the steps needed. (http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/
html/Global_File_System/index.html describes GFS and how to install a broader range of
tools.) Also, the steps in this chapter assume that the physical cabling of the servers and
storage is complete and connectivity has been verified.
To install GFS
1. Log in to the operating system of the VTS server as root.
2. Mount the GFS Install/Upgrade DVD. This example illustrates mounting the DVD on
/media/cdrom:
mkdir -p /media/cdrom
mount /dev/cdrom /media/cdrom
3. Install the GFS RPMs by entering the following command:
/media/cdrom/vts-6.04-gfs-install/installGFS.bash
Ignore any warnings that may be displayed.
4. Unmount and eject the DVD:
umount /media/cdrom
eject
5. Enter the following commands to disable clustering services that are included with the
GFS but not used by VTS. Failure to disable these can cause the system to hang.
chkconfig openais off && service openais stop
chkconfig saslauthd off && service saslauthd stop
If any of these commands returns a failure, it is not an error. It indicates that the process
was not running.
6. GFS RPMs inadvertently remove SCSI target mode support. To address this and
maintain correctly functioning virtual tape drives (VTDs), run the following command:
/usr/local/tape/bin/mkinitrd.pl -f
The VTS server is rebooted after this completes.
7. Repeat steps 1-6 on each server (node) that will be included in the cluster.
34 | Installing GFS
Complete the next four steps (steps 8-11) on only one server (node) that will be included in the
cluster. It is recommended that you shutdown all nodes in the cluster other than the one used
in these steps. If you are creating multiple vaults, you must also complete steps 8-11 for each
GFS file system to be used for vault storage.
8. Choose your device(s) to be used for GFS. In the commands and output below, /dev/sde is
used as an example device.
VTS assumes an empty, unpartitioned disk, and further disk partitioning is not
performed. Cluster members will mount devices based on LVM names, not SCSI device
names, and these GFS devices will not use disk labels.
If the vault will be less than 2TB in size, complete the following steps to partition the disk:
a. Enter the following command to partition the device.
fdisk /dev/sde
b. Enter n to add a new partition.
c.
Enter p to specify the primary partition.
d. Enter 1 to specify the first partition.
e.
Press ENTER to accept the defaults.
f.
Enter w to save the configuration.
To confirm the configuration, enter the following command:
fdisk -l /dev/sde
Here is an example of the output:
Disk /dev/sde: 18.4 GB, 18413722112 bytes
255 heads, 63 sectors/track, 2238 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot
Start
End
Blocks
Id
/dev/sde1
1
2238
17976703+
83
System
Linux
If the vault will be 2-4TB in size, complete these steps to partition the disk:
a. Start the partition editor, which is an interactive program similar to fdisk:
parted /dev/sda
b. Create a GPT disk label, which is a GUID partition table:
mklabel gpt
c.
Create a 4TB primary partition at the beginning of the disk:
mkpart primary 0 4000G
Note that you can specify 100% instead of 4000G to create a partition that uses the
entire disk.
d. Quit parted.
quit
9. Perform LVM initialization of the device. /dev/sde1 is used as an example partition on
the /dev/sde device.
a. Create the physical volume by entering the following command:
pvcreate /dev/sde1
Installing GFS | 35
b. Create the volume group by entering the following:
vgcreate gfsvg1 /dev/sde1
c.
Create the logical volume by entering the following command. The -l 100%FREE
argument creates a logical volume using the entire volume group.
lvcreate -l 100%FREE -n lv1 gfsvg1
d. Enter the following command to confirm the physical volume:
pvscan
Here is an example of the output:
PV /dev/sde1
VG gfsvg1
lvm2 [17.14 GB / 0
free]
Total: 1 [17.14 GB] / in use: 1 [17.14 GB] / in no VG: 0 [0
e.
Enter the following command to confirm the volume group:
vgscan
Here is an example of the output:
Reading all physical volumes. This may take a while...
Found volume group "gfsvg1" using metadata type lvm2
f.
Enter the following to display details about the physical volume:
pvdisplay
Here is an example of the output:
--- Physical volume --PV Name
/dev/sde1
VG Name
gfsvg1
PV Size
17.14 GB / not usable 3.37 MB
Allocatable
yes (but full)
PE Size (KByte)
4096
Total PE
4388
Free PE
0
Allocated PE
4388
PV UUID
tTHBFt-6pqc-ILIY-Uis5-L8Yn-bvBu-SCN3MV
g. Enter the following to view details about the volume group:
vgdisplay
Here is an example of the output:
--- Volume group --VG Name
System ID
Format
Metadata Areas
Metadata Sequence No
VG Access
VG Status
MAX LV
Cur LV
Open LV
Max PV
Cur PV
36 | Installing GFS
gfsvg1
lvm2
1
2
read/write
resizable
0
1
1
0
1
]
Act PV
VG Size
PE Size
Total PE
Alloc PE / Size
Free PE / Size
VG UUID
1
17.14 GB
4.00 MB
4388
4388 / 17.14 GB
0 / 0
lm4cH7-4wgq-s1VR-VNwc-pFC6-i54u-h5tKxk
h. Enter the following command to view details about the logical volume:
lvdisplay
Here is an example of the output:
--- Logical volume --LV Name
/dev/gfsvg1/lv1
VG Name
gfsvg1
LV UUID
VQUsmh-LI1E-rBIm-3tCe-9o6K-cjlp-ah8e4j
LV Write Access
read/write
LV Status
available
# open
0
LV Size
17.14 GB
Current LE
4388
Segments
1
Allocation
inherit
Read ahead sectors
0
Block device
253:0
10. Create the GFS file system:
a. Enter the following command. Note that any data that may reside on the logical
volume (dev/gfsvg1/lv1 is used as an example) is destroyed.
gfs_mkfs -p lock_dlm -t cluster_name:gfs01 -j journals /dev/
gfsvg1/lv1
where -p lock_dlm argument sets the lock manager to DLM, -cluster_name specifies
the cluster name, and journals specifies the number of journals to create, which
should be the number of nodes plus two.
b. When prompted, enter y to proceed. Output similar to the following is displayed:
Device:
Blocksize:
Filesystem Size:
Journals:
Resource Groups:
Locking Protocol:
Lock Table:
/dev/gfsvg1/lv1
4096
4394620
3
68
lock_dlm
cma:01
Syncing...
All Done
Installing GFS | 37
11. Start ricci and luci.
For more information about these GFS services, refer to http://www.redhat.com/docs/
manuals/enterprise/RHEL-5-manual/en-US/RHEL510/Cluster_Administration/s1-startluci-ricci-conga-CA.html.
These services must be configured in the cluster before you can mount the newly created
GFS volume. Complete the following steps to start the services.
a. Make sure that the luci system has a proper /etc/hosts file. Here is an example
command to confirm the contents of the file:
cat /etc/hosts
Here is an example of the file:
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1
localhost.localdomain
localhost
192.168.80.2
vtsdev27.commstor.crossroads.com vtsdev27
The file should list all cluster nodes. The localhost entry is for the system you are
using and the other entries are for the cluster nodes.
b. On each node, start ricci:
chkconfig ricci on
service ricci start
To confirm that ricci is running, enter the following:
service ricci status
c.
On one (and only one) of the cluster servers, configure and start the luci service. Red
Hat recommends configuring luci on a non-cluster node. It will function properly on a
cluster node, though web connectivity is lost while the system is rebooting. If the luci
node goes down, the cluster cannot be administered with luci.
luci_admin init
When prompted, enter a new password.
Then, restart the luci service:
service luci restart
Note the URL given in the output; you will access it in the next step.
d. Configure the cluster using the luci web interface:
•
Access the web interface by loading the URL given in the previous step in a web
browser.
•
When prompted, accept the certificate permanently.
•
Click OK if a certificate domain mismatch warning is displayed.
•
Log in by entering the luci admin username and password.
•
Click Add a System.
•
Enter the fully qualified domain name of the GFS system.
•
Enter the root password for that system.
•
Click Add another entry.
38 | Installing GFS
•
Enter each cluster member's name and root password, and click Submit.
•
Click the Cluster tab at top of the page.
•
Click Create a New Cluster.
•
Enter the same cluster name specified in step 10a.
•
Enter each system's fully qualified domain name and root password.
•
Select Use locally installed packages.
•
Make sure Enable Shared Storage Support is selected.
•
Click Submit.
Although the interface states that the systems are rebooted, they are not.
12. Configure fencing:
a. In the browser, under the cluster name in the left column, click Nodes.
b. For each node, click Manage Fencing for this Node.
c.
Under Main Fencing Method, click Add a fence device to this level.
d. Select brocade fabric switch.
e.
Enter the hostname of the Fibre Channel switch. Consult your SAN administrator for
this information.
f.
Enter the IP address of the Fibre Channel switch. Consult your SAN administrator
for this information.
g. Enter the username for accessing the Fibre Channel switch. Consult your SAN
administrator for this information.
h. Enter the corresponding password. Consult your SAN administrator for this
information.
i.
Enter the port of the Fibre Channel switch. Consult your SAN administrator for this
information.
j.
Click Update.
Repeat these steps for each node in the cluster.
13. Add GFS storage to the cluster:
a. In left-hand column of the web interface, under the cluster name, click Resources.
b. Click Add a resource.
c.
Select GFS.
d. For the name, enter the vault name (for example, VAULT10).
e.
For the mount point, enter the location where you want the vault to appear (for
example, /VAULT10).
f.
For the device, enter the name of the device specified in step 10 (for example, /dev/
gfsvg1/lv1).
g. Leave the options and filesystem ID blank.
h. Click Submit.
Because the LUN-to-device mapping can be different on each system, clvm logical volume
names are globally unique. You cannot create duplicates.
Repeat these steps for each GFS file system.
Installing GFS | 39
14. Complete the following steps on each cluster node to verify that all cluster nodes can
access the GFS volumes, mount them, and access files written by other nodes. In the
following steps, VAULT10 is used as the name of the vault.
a. Enter the following commands on the console of the node:
mkdir /VAULT10
chown bill.root /VAULT10
chmod 755 /VAULT10
mount /dev/gfsvg1/lv1 /VAULT10
ls -al /VAULT10
The following is an example of output for the ls command:
total 12
drwxr-xr-x 2 root root 3864 May 15 15:24 .
drwxr-xr-x 4 root root 4096 May 15 17:59 ..
b. Enter the following command to verify that there is free space on the mounted GFS
file system.
df -h /VAULT10
Here is an example of the output:
Filesystem
/dev/mapper/gfsvg1-lv1
c.
Size
Used
Avail Use%
Mounted on
17G
36K
17G
/VAULT10
1%
Enter the following command to verify that you can write to the mounted GFS file
system.
touch /VAULT10/`hostname`
d. Verify that files written by other VTS servers are visible by entering the following
command:
ls -al /VAULT10
Here is an example of the output:
total 28
drwxr-xr-x 2 root root 3864 May 16 11:32 .
drwxr-xr-x 4 root root 4096 May 15 17:59 ..
-rw-r--r-- 1 root root 0 May 16 11:32
vtsdev27.commstor.crossroads.com
After completing these steps on each node, this output lists each system's hostname in
the vault directory. Be sure to delete these files after completing this installation
procedure.
40 | Installing GFS
15. Verify fencing.
Note
These steps verify Brocade Fibre Channel fencing only.
Before performing these steps, make sure you are not logged into the switch through
Telnet. If you are logged in, the brocade fencing script will fails with an error similar to
the following:
/sbin/fence_brocade -a ip_addr -l username -n 2 -p password -o disable
pattern match read eof at ./fence_brocade line 138
# echo $?
255
where ip_addr, username, and password is that of the Fibre Channel switch. Consult your
SAN administrator for this information.
To verify the fencing method, enter the following commands:
/sbin/fence_brocade -a ip_addr -l username -n 2 -p password -o disable
/sbin/fence_brocade -a ip_addr -l username -n 2 -p password -o enable
16. Complete the following steps to configure fencing from luci:
a. From the luci web interface, select the node.
b. Select choose a task...
c.
Select fence this node.
d. From the command line, enter the following:
tail -f /var/log/messages
Here is an example of the output:
May 15 19:06:19 VTS_svr fence_node[28881]: Fence of "VTS_svr2" was
successful
17. Test fencing. In a separate window, enter the following command to view for fencing
messages in the system log file:
tail -f /var/log/messages
Here is an example of the messages:
May 15 19:10:25 VTS_svr fenced[10804]: VTS_svr2 not a cluster member
after 0 sec post_fail_delay
May 15 19:10:25 VTS_svr fenced[10804]: fencing node "VTS_svr2"
May 15 19:10:26 VTS_svr fenced[10804]: fence "VTS_svr2" success
18. Verify the installation. Complete the following steps to verify the GFS installation and
troubleshoot any issues:
a. Verify that the appropriate services are enabled and started by entering the following
commands:
chkconfig cman on && service cman restart
chkconfig clvmd on && service clvmd restart
chkconfig ricci on && service ricci restart
Installing GFS | 41
b. Verify that logical volumes cannot be seen by attempting to mount a logical volume
(/dev/gfsvg1/gfslv1 and VAULT10 are example values):
mount /dev/gfsvg1/gfslv1 /VAULT10
Here is an example of the output if the logical volume is not visible:
mount: special device /dev/gfsvg1/gfslv1 does not exist
c.
Using the luci web interface, ensure that nodes are not fenced.
d. Enter the following command to activate all known volume groups in the system:
vgchange -ay
Here is an example of the output:
1 logical volume(s) in volume group "gfsvg1" now active
e.
Mount the vault by entering this command:
mount /dev/gfsvg1/gfslv1 /VAULT10
f.
If luci will not start or restart, enter the following:
service luci start
or
service luci restart
If luci can see a node but indicates that ricci is not running, but the node shows ricci is
running, output to the similar is displayed:
luci[15356]: Unable to establish an SSL connection to
192.168.80.2:11111: ricci's certificate is not trusted
Enter the following commands to remove luci:
rpm -e luci
rm -rf /var/lib/luci
You may need to reinstall luci or re-import the cluster. The luci RPM is available on
the GFS Install/Upgrade DVD. If necessary, mount the DVD and enter the following
command to install luci:
rpm -ivh /media/cdrom/vts-6.04-gfs-install/luci*.rpm
19. To review the cluster status, enter the following command:
cman_tool status
Here is an example of the output:
Version: 6.0.1
Config Version: 5
Cluster Name: cma
Cluster Id: 711
Cluster Member: Yes
Cluster Generation: 64
Membership state: Cluster-Member
Nodes: 2
Expected votes: 1
Total votes: 2
42 | Installing GFS
Quorum: 1
Active subsystems: 7
Flags: 2node
Ports Bound: 0 11
Node name: 192.168.80.2
Node ID: 2
Multicast addresses: 239.192.2.201
Node addresses: 192.168.80.2
Installing GFS | 43
44 | Installing GFS
Configuring Licensing
Before you can use VTS, you must enable virtual tape drive (VTD) licensing. You can also
enable licensing for optional features — SecureVTS, Instant DR, and AutoCopy (Instant DR
and AutoCopy are licensed together). To obtain license keys, log in to https://
partners.crossroads.com, click Tools, and follow the instructions on the site. License keys are
generated based on the hardware ID of the VTS server. Obtain a set of license keys for each
VTS server in your environment.
Note
The VTD license also enables compression, if included. Also, if the VTS server was
upgraded, you may need a Vital Product Data (VPD) file before you can enable
licensing. See the “Upgrading to 6.04” section of the Virtual TapeServer
Administration and Operations Guide for more information.
Requires Administration group membership
To enter a license key
1. Log in to the VTS web interface 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.
2. Click Supervisor Functions on the navigation pane.
3. Click Manage System Licenses. The following page is displayed:
45
4. If SecureVTS is licensed, type the license key in the Secure VTS Key field.
5. If Instant DR and Autocopy are licensed, type the license key in the IDR Key field.
6. In the VTD Key field, type the license key.
7. Click SUBMIT.
8. On the pop-up dialog, click OK to confirm that you want to add the key.
9. Restart the TapeServer service. Click Supervisor Functions on the navigation pane. On
the Supervisory Functions page, click Stop TapeServer and then click Start
TapeServer.
Submitting a valid license key enables you to perform all other installation and configuration
tasks. Submitting a valid license key for SecureVTS adds the localhost as the key server that
generates keys. You can now add a key database backup host.
46 | Configuring Licensing
Configuring and Validating Virtual Tape Drives
After Virtual TapeServer (VTS) is deployed, you must create virtual tape drives (often
referred to as VTDs). Up to 32 virtual tape drives are supported per VTS server. Then, you
must configure the virtual tape connections in VTS, which define connections between the
hosts and virtual tape drives in your environment. You can then validate that the host
server(s) in the environment can back up data to all virtual tape drives configured in VTS.
Adding a virtual tape drive
The following table describes the properties that you must set when defining a virtual tape
drives. For each property, this table provides a description and whether each property is
presented to the host server when the virtual tape drive responds to a host’s query:
Presented
to Host?
Property
Description
Bus ID
The ID of the bus on the VTS server to which the host is
connected. This ID is not presented directly to the host; the
host will see this bus numbered according to its numbering
scheme. If the connection is over Fibre Channel, the bus ID
is associated with a port WWN that is used by the host to
identify the VTS server. If the connection is over SCSI, the
bus ID on the VTS server has no special significance to the
host.
Indirectly
Target ID
With SCSI, this is the SCSI ID on which the virtual tape
drive responds. This ID is not presented to the host if the
connection is over Fibre Channel. To avoid confusion, this
ID should be set to 0.
Yes, for
SCSI only
Logical unit
number (LUN)
The sub-ID on the bus. This ID is used by the host for SCSI
and Fibre Channel connections.
Yes
Initiator ID
The SCSI ID of the host. This ID has no significance if the
bus is in target mode and, in this case, this ID should be set
to 7.
Yes
Name
A user-friendly name for the virtual tape drive.
Yes
Media type
The type of tape drive that the virtual tape drive emulates.
Yes
47
Presented
to Host?
Property
Description
Host type
The type of host (NonStop S-series, NonStop Integrity,
NonStop BladeSystem, or UNIX server).
No
Serial number
The serial number or other string describing the virtual
tape drive. Only alphanumeric characters should be used.
Yes
The first four properties are collectively referred to as the BTLI of the virtual tape drive. 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.
Requires the View/Manage Configuration and Factory Setup Activities access rights
To add a virtual tape drive
1. Add a new physical tape, as follows:
a. Click Factory Setup on the navigation pane.
b. Log in. See Credentials on page 139 for a list of default user accounts.
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 corresponds to the highest bus
number available. In the example above, this value is 2.
f.
Select a target ID from the target drop-down list. If you are creating more than one
virtual tape drive, select the value above the target noted in step 5b for subsequent
virtual tape drives.
g. Leave the lun drop-down list set to 0.
h. Leave the initiator drop-down list set to 7.
48 | Configuring and Validating Virtual Tape Drives
i.
Specify a name for the virtual tape drive in the name field. If you are creating
multiple virtual tape drives, increment the number that is appended to the physical
tape drive noted in step 5c.
j.
Select RAID from the type drop-down list.
k. Click Add Physical Tape.
2. Add a new logical tape, as follows:
a. Click Setup Tapes at the bottom of the page to display the Manage Tape Connections
page.
b. Click Add a new logical tape. The Add A New Logical Tape page is displayed.
c.
Specify a name for the logical tape in the field in the new tape name column. If you
are creating multiple virtual tape drives, increment the number that is appended to
the logical tape noted in step 5d.
d. Select the physical tape created in step 1.
e.
Click Add Logical Tape.
3. Add a new virtual tape drive, 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 server 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.
d. From the target drop-down list, select the ID on which the virtual tape drive will
respond. This is the ID that the host uses to identify its target, and the ID typically
ranges from 0–15.
Note
Fibre Channel devices use LUN-based addressing. SCSI devices use targetbased addressing. For Fibre Channel devices, the LUN determines the unique
address of the device on the bus. When assigning the target ID and LUN, be
sure to assign a unique combination. For example, you cannot assign target
ID 0 LUN 0 and target ID 1 LUN 0 on the same bus; this creates a conflict. All
Configuring and Validating Virtual Tape Drives | 49
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. 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. (Refer to the NonStop S
server documentation for more information.)
•
For NonStop Integrity (NS) and BladeSystem servers
In general, you can assign values 0–15 to the target ID. (Integrity servers support
Fibre Channel ports only.) Best practices encourage you to assign value 5 to the
target ID.
•
UNIX servers
In general, any ID greater than 0 can be used for the target ID. The backup
management application determines the ID and typically assigns 0 to the robot in
a tape library. Refer to backup management application documentation and host
server to determine the target ID.
If the Fibre Channel is configured for the Arbitrated Loop topology, use the Loop
ID as the target ID here. To find the Loop ID, boot VTS while connected to the
Fibre Channel network. Then, after the startup is complete, access the VTS web
interface. Click Supervisor Functions on the navigation pane, click Examine
the system log file, and search for “Loop id.” The ID is typically set to 0 or 1 but
it can be set as high as 255.
e.
f.
From the lun drop-down list, select the logical unit number. This number identifies
the sub-ID on the bus, and this ID typically ranges from 0 – 255. The appropriate
LUN value depends on the host server. For SCSI connections, this ID is 0 typically:
•
For NonStop S-series servers
Select 0 as the LUN. (0 is the only value supported by NonStop S servers, which
support SCSI ports only and ignore the LUN.)
•
For NonStop Integrity (NS) and BladeSystem servers
Up to four tape devices are supported per port, therefore you can assign values 0–
3 to the LUN. 0 is typically assigned to the LUN for the first tape device, 1 is
typically assigned for the second tape device, 2 for the third, and 3 for the fourth.
•
UNIX servers
In general, set the LUN to any value between 0 and 7. Begin with 0 and increment
the LUN for each additional virtual tape drive that is added on a bus. The backup
management application determines the number. Refer to backup management
application documentation and host server to determine the LUN.
From the initiator drop-down list, select the SCSI ID of the host bus to which VTS is
connected. This value is set by the host, and the default is 7.
g. In the name field, specify a name for the virtual tape. This name is for use in the
interface and by EMS. It is also noted in the configuration file. The name is casesensitive.
50 | Configuring and Validating Virtual Tape Drives
h. Select the media format from the tape_type drop-down list. This property defines the
type of tape that the virtual tape emulates. This property also specifies the icon
selected for the logical drive on user interface pages.
Note
Do not select RAID; this option is provided for physical tapes only.
i.
Specify the host, or initiator, type by choosing an option from the host_type dropdown list. This property is for reference only; it is not presented to the host. This
property also specifies the icon selected for the virtual tape on the interface pages.
j.
In the serial_number field, specify the serial number of your virtual tape. You can
specify up to 10 alphanumeric characters. This string is presented to the host and
should be unique (across all VTS servers and VTDs in the environment).
This field is optional unless the host server is a NonStop BladeSystem. If you do not
enter a serial number, the BTLI will be presented to the host as the serial number but
not shown in the web interface. The default BTLI serial number is unique per VTS
server but other VTS servers may create the same BTLI serial number. In an
environment with more than one VTS server connected to a NonStop BladeSystem,
specify serial numbers that are unique across the environment to avoid conflicts.
k. Click Add Virtual Tape.
4. 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. If successful, the connection is added at the bottom of
the virtual-logical-physical associations on the System Overview page.
5. Repeat steps 1-4 to create additional VTDs. Make note of the values assigned to the
highest numbered physical tape drive:
a. Click View Configurations. The System Overview page is displayed.
Configuring and Validating Virtual Tape Drives | 51
b. Note the bus, target, LUN, and initiator (BTLI) numbers for the highest numbered
physical tape drive to which the RAID type is assigned. In the snapshot provided in
the previous step, the highest BTLI is 30 1 0 7.
c.
Note the name of this physical tape drive. In the snapshot, the physical tape drive is
named PTAPE01.
d. Note the name of the associated logical tape. The example logical tape is named
LTAPE01.
It is recommended that you back up the VTS database after modifying the VTS configuration.
Refer to the Virtual TapeServer Operations and Administration Guide for instructions.
Modifying virtual tape connections
You can modify the virtual tape drives and their connections, if necessary, to reflect exact
connections between the hosts and virtual tape drives in your environment.
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.
On the System Overview page, the relationship between each virtual tape drive and the
logical and physical drives it emulates is shown:
52 | Configuring and Validating Virtual Tape Drives
For example, the $VTAPE01 virtual tape drive is associated with the LTAPE01 logical
drive and the PTAPE01 physical hard drive:
The following steps describe how to disassociate the virtual tape drive ($VTAPE01 in this
example) from its logical and physical drives (LTAPE01 and PTAPE01):
a. In the navigation pane, click Manage Connections. The Manage Tape Connections
page is displayed.
b. Click Delete a tape connection. The Delete A Tape Connection page is displayed:
c.
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 drive is no longer listed in the table on the page.
•
System Overview — Click View Configurations and verify that the virtual tape
drive was moved to the Virtual Tapes section of the page and the logical and
physical drives were moved to the Logical Tapes section of the page.
2. Modify the properties of the virtual tape drive by completing the following steps:
a. Click Manage Connections in the navigation pane. The Manage Tape Connections
page is displayed.
b. Click Edit an existing virtual tape.
Configuring and Validating Virtual Tape Drives | 53
c.
On the Choose A Virtual Tape To Edit page, select the virtual tape drive to edit (the
one for which you deleted the connection) and click Edit. This page is then displayed:
d. Change the values of the virtual tape as needed. See step 3 on page 49 for a
description of the properties.
e.
Click Edit Virtual Tape to save your settings.
3. Re-associate the virtual tape drive with the logical and physical drives:
a. Click Manage Connections in the navigation pane. The Manage Tape Connections
page is displayed.
54 | Configuring and Validating Virtual Tape Drives
b. Click Add a tape connection. The Add A Tape Connection page is displayed:
c.
Select the virtual tape drive you want to reconnect from the Virtual Tapes section of
the page.
d. Select the logical and physical drives to which you want to reconnect the virtual tape
drive from the Logical Tapes section of the page.
e.
Click Add Tape Connection. If successful, the connection is added at the bottom of
the virtual-logical-physical associations on the System Overview page.
It is recommended that you back up the VTS database after modifying the VTS configuration.
Refer to the Virtual TapeServer Operations and Administration Guide for instructions.
Configuring the NonStop BladeSystem Cluster I/O Module
If the NonStop BladeSystem is used as the host server and the Cluster I/O Module (CLIM)
will be used, you must configure the virtual tape drives on the NonStop. Complete the
following steps to do so:
1. Verify that the serial number specified for each virtual tape drive (in VTS) is unique. See
step 3j on page 51 for more information.
2. Verify that the CLIM is connected to the VTS server using a Fibre Channel cable.
3. Issue the following command on BladeSystem server to verify the list of devices, including
those configured in VTS:
CLIMCMD clim_name lunmgr -f
Here is an example of the output:
dev
type
stable address
controller
serial #
revision
sg0
3
tape CPQNSD 5257 #VFHP00
slot 1, port 1
VFHP00
VT36
sg1
3
tape CPQNSD 5257 #VFHP01
slot 1, port 1
VFHP01
VT36
Configuring and Validating Virtual Tape Drives | 55
sg2
3
tape CPQNSD 5257 #VFHP02
slot 1, port 1
VFHP02
VT36
sg3
3
tape CPQNSD 5257 #VFHP03
slot 1, port 1
VFHP03
VT36
sg5
3
tape CPQNSD 5257 #VFHP04
slot 1, port 1
VFHP04
VT36
4. If you do not see devices, issue the following command to scan the devices and detect new
devices:
CLIMCMD clim_name lunmgr -s
5. If the devices are not listed again, issue the following command, which enables you to set
LUNs:
CLIMCMD clim_name lunmgr -a, VERBOSE
6. If steps 4 and 5 are successful, issue the SCF command to add a tape. Here is an example:
SCF ADD TAPE $VFHP00, SENDTO STORAGE, CLIM S1002531, LUN 1,
PRIMARYCPU 2,BACKUPCPU 2.
7. Start the virtual tape drive. If a 224 error occurs, delete the drive and make sure steps 4
and 5 are successful.
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.
Issue the following command on Integrity series servers to configure the virtual tape drive:
SCF ADD TAPE $VTD, SENDTO STORAGE, LOCATION (x,y,z), LUN #, SAC #,
PORTNAME WWN#, COMPRESSION OFF
where
$VTD The virtual tape drive name, such as $TAPE00. The name specified here must match
the value assigned to the ems_hostdevs_NSserver parameter in the VTS
configuration file.
LOCATION (x,y,z)
The location of the Fibre Channel ServerNet adapter (FCSA) in the Integrity server,
such as (110,3,2). This value depends on where the Fibre Channel cable is plugged
into the NonStop server.
LUN # Where the virtual tape drive is defined on VTS. This parameter is specified for Fibre
Channel connections only.
SAC # The Fibre Channel port on the FCSA. Valid values include 1-4. This parameter is
specified for Fibre Channel connections only.
PORTNAME WWN#
The World Wide Name (WWN) of the Fibre Channel port on VTS to which the virtual
tape drive is cabled, which is provided in the documentation shipped with VTS. An
example value is 210000E08B1AC519. Each Fibre Channel port has a unique WWN.
This parameter is specified for Fibre Channel connections only.
56 | Configuring and Validating Virtual Tape Drives
On NonStop S-series servers, issue the following command:
SCF ADD TAPE $VTD, BACKUPCPU #, COMPRESSION OFF, DENSITY 6250,
DEVICEID #, HIGHPIN ON, LOCATION (x,y,z), LUN 0, MAXOPENS 4,
PRIMARYCPU #, PROGRAM $SYSTEM.SYSTEM.OTPPROCP, RECSIZE 2048, SAC #,
SENDTO STORAGE, STARTSTATE STARTED
This command should return messages similar to the following if successful:
SCF - T9082G02 - (06JAN06) (31OCT05) - 01/19/2007 08:42:02 System \DEV3
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
Total Errors = 0
Total Warnings = 0
Then make sure no virtual tapes are mounted and start the virtual tape drive. To verify that
no virtual tapes are mounted, click Virtual Media on the navigation bar of the VTS
interface. Confirm that no virtual tapes are mounted.
To start the virtual tape drive, enter the following command on the NonStop server:
SCF START TAPE $VTD
This command should return messages similar to the following if successful:
SCF - T9082G02 - (06JAN06) (31OCT05) - 01/19/2007 08:42:11 System \DEV3
(C) 1986 Tandem (C) 2006 Hewlett Packard Development Company, L.P.
Total Errors = 0
Total Warnings = 0
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.033
3: Premature process termination with fatal errors or diagnostics
Total Errors = 1
Total Warnings = 0
If system error 190 or 224 occurs, check the cable connections and confirm that they are
attached to the proper location as specified by the LOCATION parameter in the ADD command.
It is also recommended that you check the port on VTS to confirm that it is in the proper
location based on the bus number on which the VTD is configured. Finally, check that the
SCSI converter is powered on and functioning properly.
If you need to stop a virtual tape drive at any time, such as if a problem occurs on the host or
you want to move the location of the connection to the host, enter the following command on
the NonStop server:
SCF STOP TAPE $VTD
Ensure that no virtual tapes are loaded in the virtual tape drive before issuing this command.
Configuring and Validating Virtual Tape Drives | 57
58 | Configuring and Validating Virtual Tape Drives
Configuring Access Control
If you have system administrator privileges, you can configure access control to grant or limit
access to specific VTS functions. Each login ID belongs to a group and each group has a
unique set of privileges.
Note
VTS provides a user that has administrator privileges. You can log in as admin if no
other administrative user is created on the system. The default password for this user
is virtual.
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. A closed system requires
authentication to access resources assigned to a particular group. You can enable or disable
individual rights to resources.
This chapter describes how to configure VTS as a closed system, how to configure users, and
how to configure groups.
59
Enabling a closed system
You can enable a closed system to require authentication. The user can access only the
resources assigned to a particular group. You can enable or disable individual rights to
resources.
Requires the System Access Controls access right
To enable a closed system
1. Click Access Control on the navigation pane.
2. When prompted, log in. After logging in, the Access Control page is displayed.
3. 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.
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. If you grant access to a category, all rights in the
60 | Configuring Access Control
subcategories are granted by default, though you can remove individual rights in
the subcategories.
Rights
Administration Group
Operations
Group
Supervisor
Group
Factory Setup Activities
Supervisory Functions
Access Administration
X
X
X
System Access Controls
X
User Access Controls
X
Block and Unblock TapeServer
X
X
Database Download
X
X
Database Upload
X
Edit VTS Configuration File
X
Halt and Reboot TapeServer
X
X
Manage Scheduled Jobs
X
X
System Maintenance Functions
X
X
System Upgrade/Update
Functions
X
X
Turn Compression On or Off
X
X
Upload Encryption Keys
X
X
Upload VPD
X
VTS/Linux Configuration Backup
X
VTS/Linux Configuration
Restore
X
View log files
X
View/Manage Configuration
X
Virtual Tape Operations
X
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
Configuring Access Control | 61
Rights
Administration Group
Operations
Group
Supervisor
Group
Virtual Tape Mounts and Locks
X
X
Virtual Tape Pool Maintenance
X
X
Erase Cartridges
X
X
HSM Migration
X
X
Mount Cartridges
X
X
Unmount Cartridges
X
X
View System Status
X
X
X
Change Refresh Rate
X
Stop and Start TapeServer
X
X
X
X
X
X
X
X
X
Vault Access
Access to All Vaults
X
Note that, by default, the Factory Setup Activities access right is not assigned to any
group.
62 | Configuring Access Control
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. Click Access Control on the navigation pane.
2. When prompted, log in. After logging in, the Access Control page is displayed.
Configuring Access Control | 63
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.
64 | Configuring Access Control
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.
Configuring Access Control | 65
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.
66 | Configuring Access Control
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.
Configuring Access Control | 67
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.
68 | Configuring Access Control
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.
Configuring Access Control | 69
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.
70 | Configuring Access Control
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 Access Control | 71
Configuring groups
Groups define the access rights that are assigned to users. Three groups are provided:
Administration, Operations, and Supervisor. For a list of the default rights assigned to these
groups, see page 60. You can modify the access rights that are assigned to these groups. You
can also save your changes as a set of custom defaults, which can be restored later if
necessary.
Requires the System Access Controls access right
To modify access rights assigned to the Administration, Operations, and
Supervisor groups
1. Click Access Control on the navigation pane.
2. When prompted, log in. After logging in, the Access Control page is displayed.
72 | Configuring Access Control
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.
Here is a description of each access right:
Right
Description
Factory Setup Activities
Grants access to the Factory Setup page
Supervisory Functions
Grants access to the Supervisory Functions
page
Access Administration
System Access Controls
Grants access to the Access Control page
Enables the user to administer groups and
rights within Access Control
Configuring Access Control | 73
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 user to edit the VTS configuration
file from the Supervisory Functions page
Halt and Reboot TapeServer
Enables the user to halt and reboot VTS from
the Supervisory Functions page
Manage Scheduled Jobs
Obsolete; do not assign this access right
System Maintenance Functions
Enables the user to stop and start the EMS,
Inter-Systems Communication (ISC), XML, and
FTX services from the Supervisory Functions
page, and enables licensing
System Upgrade/Update
Functions
Enables the user to apply revision updates and
apply customized code changes
Turn Compression On or Off
Enables the user to enable or disable
compression from the Supervisory Functions
page
Upload Encryption Keys
Obsolete; do not assign this access right.
Upload VPD
Enables the user to upload the VPD file.
VTS/Linux Configuration Backup
Enables the user to back up the configuration
file from the Administrator Utilities page,
which is displayed by clicking Administrator
Utilities on the Factory Setup page
VTS/Linux Configuration
Restore
Enables the user to restore the configuration
file from the Administrator Utilities page,
which is displayed by clicking Administrator
Utilities on the Factory Setup page
View log files
Enables the user to view log files from the
Supervisory Functions page
View/Manage Configuration
Grants access to the View Configurations and
Manage Connections menus
Virtual Tape Operations
74 | Configuring Access Control
Grants access to the Virtual Media - Operation
page
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 - 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
Erase Cartridges
Enables the user to erase virtual tapes from the
Virtual Media - Operation and Virtual Media Cartridge Maintenance pages
HSM Migration
Enables the user to migrate virtual tapes using
the Migrate button on the Virtual Media Operation page
Mount Cartridges
Enables the user to manually mount virtual
tapes using the Mount button on the Virtual
Media - Operation page
Unmount Cartridges
Enables the user to unmount virtual tapes
using the Unmount button on the Virtual Media
- Operation page
View System Status
Grants access to the System Status page
Change Refresh Rate
Enables the user to change the refresh rate of
the System Status page from the System Status
and Supervisory Functions pages
Stop and Start TapeServer
Enables the user to start and stop VTS from the
Supervisory Functions page
Vault Access
Access to All Vaults
Provides access to vaults.
Provides access to any vault and vault contents.
Configuring Access Control | 75
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.
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.
76 | Configuring Access Control
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 Access Control | 77
78 | Configuring Access Control
Configuring EMS Communication
To automate the process of mounting and dismounting virtual tapes, you must configure the
Event Management System (EMS) on Virtual TapeServer (VTS). The EMS service starts the
EMS distributor on the NonStop server by issuing a Tandem Advanced Command Language
(TACL) command. The distributor notifies the VTS EMS service when an EMS message is
posted on the NonStop server. These EMS messages relate to mount requests, VTSPolicy
commands, TACL heartbeat messages, and critical and error event messages.
Perform the following steps for each NonStop server to which VTS will send messages.
Requires the Edit VTS Configuration File access right to edit the configuration file, and
System Maintenance Functions or Virtual Tape Mounts and Locks access right to restart the
EMS service
To configure EMS
1. On the NonStop server, create a user account that VTS can use for the EMS distributor.
2. On VTS, modify the VTS configuration file to configure EMS, as follows.
Note
A default configuration file is defined for each VTS server. To override the default
settings, you must define settings as described below.
a. Click Supervisor Functions on the navigation pane.
b. Click Edit VTS Configuration File.
c.
Add or modify the following global EMS 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
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.
See the next step for a list of
these parameters.
79
Parameter
Description
Values
Required
ems_notify_enable
Enables EMS messages to be
generated for notifications.
YES or NO
No
YES or NO
No
ALL, INFO,
WARNING,
ERROR,
CRITICAL,
or NONE
No
List of
hostnames
or IP
addresses
separated by
spaces
No
Default value: NO
ems_notification_
enable
Enables VTS to send
notification messages back to
the NonStop host from EMS
messages.
Default value: NO
ems_notification_
level
Enables EMS to acknowledge
certain EMS messages and
generate completion status
(success or failure) messages.
This parameter is synonymous
with the ems_hsm_
backup_notification
parameter set for migration
configuration. Set this
parameter to one or more of the
values, separated by spaces. If
the notification level of the
event matches one of the words,
the event log message is
forwarded to the EMS host. If
you set this parameter to
NONE, no event log messages
are forwarded to the host.
Default value: ERROR
CRITICAL
ems_notify_
hostnames
Specifies the host systems that
VTS will notify. This parameter
defaults to the value of
ems_hostnames if it is not
specified in the configuration
file.
Default value: YES
80 | Configuring EMS Communication
Parameter
Description
Values
Required
ems_keep_alive
Specifies the number of seconds
between periodic EMS messages
that are sent from VTS to the
host so that the Telnet session
does not time out. When set,
EMS filtering on the host can be
increased because the Telnet
connection between the VTS
server and the NonStop host
stays alive. If omitted or set to 0,
keep-alive messaging is
disabled.
Integer
No
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
You can specify ems_notify_
wait_timeout_NSserver
instead of or in addition to this
parameter. If ems_notify_
wait_timeout_NSserver is
specified, its value overrides the
value of this parameter for the
specified host. See the next step
for more information about
ems_notify_wait_timeout_
NSserver.
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.
Note that you can specify the
ems_notify_logout_timeout_
NSserver instead of or in
addition to this parameter. If
ems_notify_logout_timeout_
NSserver is specified, its value
overrides the value of this
parameter for the specified host.
See the next step for more
information about ems_notify_
logout_timeout_NSserver.
Default value: 3
Configuring EMS Communication | 81
Parameter
Description
Values
Required
ems_response_
timeout
Specifies the timeout value (in
seconds) used to wait for each
response during the EMS Telnet
login process.
Integer
No
Note that you can specify the
ems_response_timeout_
NSserver instead of or in
addition to this parameter. If
ems_response_timeout_
NSserver is specified, its value
overrides the value of this
parameter for the specified host.
See the next step for more
information about ems_
response_timeout_NSserver.
Default value: 5
ems_mount_delay
Specifies the minimum number
of seconds that must elapse
after VTS receives a mount
request. The mount is queued
and the virtual tape is locked for
mounting or a restore by a
backup management
application.
Integer
No
ems_InterSystem
Communication_
hosts
Specifies a list of hostnames or
IP addresses of other VTS
systems with which VTS will
coordinate mount processing.
This parameter is required only
if GFS is implemented. It is
primarily used to cancel
pending mounts on other VTS
systems that have simultaneous
access to the same vaults
mounted by GFS.
List of host
names or IP
addresses
separated by
spaces
No
82 | Configuring EMS Communication
Parameter
Description
Values
Required
ems_service_
prompt_type
Specifies the service selection
prompt to which the EMS login
process responds and begins.
Expression
No
Expression
No
Expression
Yes
Expression
No
type is the hostname of the
NonStop server or
TYPE:choice, where choice is
the login service, such as TACL,
TACLS, XYGATE, or
SAFEGUARD. You can also
specify _ANYSYS instead of
_type.
Assign any search pattern as a
Perl regular expression, and the
special %username% and
%password% values may be
used in responses to equate to
those values. All entries should
be enclosed in single quotes
rather than double quotes.
Default value: /^Enter
Choice>\s*$/i (set for
_ANYSYS)
ems_service_
answer_type
Specifies the service response.
See ems_service_prompt
_type for an explanation of type.
Default value: logon (set for
_TYPE:SAFEGUARD)
ems_service_select_
type
Specifies the service. See
ems_service_prompt_type
for an explanation of type.
Default value: TACL (set for
_ANYSYS)
ems_login_
userprompt_type
Defines the user prompt during
the login process. See
ems_service_prompt_type
for an explanation of type.
Default values:
• for _TYPE:TACL: /TACL
1>\s*$/
• for _TYPE:TACLS:
/login:\s*$/i
• for _TYPE:XYGATE: /TACL
1>\s*$/
• for _TYPE:SAFEGUARD:
/TACL 1>\s*$/
Configuring EMS Communication | 83
Parameter
Description
Values
Required
ems_login_
useranswer_type
Defines the user response
shown during the login process.
See ems_service_prompt
_type for an explanation of
type.
Expression
No
Expression
No
Expression
No
Default values:
• for _TYPE:TACL: logon
%username%
• for _TYPE:TACLS:
%username%
• for _TYPE:XYGATE: logon
%username%
• for _TYPE:SAFEGUARD:
logon %username%
ems_login_
passprompt_type
Defines the password prompt
during the login process. See
ems_service_prompt_type
for an explanation of type.
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.
See ems_service_prompt
_type for an explanation of
type.
Default values:
• for _TYPE:TACL:
%password%
• for _TYPE:TACLS:
%password%
• for _TYPE:XYGATE:
%password%
• for _TYPE:SAFEGUARD:
%password%
84 | Configuring EMS Communication
Parameter
Description
Values
Required
ems_login_
successful_type
Defines a command string to
send after successful login. See
ems_service_prompt_type
for an explanation of type.
Expression
or null
No
Default values:
• for _TYPE:TACL:
/Last Logon:/
• for _TYPE:TACLS:
/Last Logon:/
• for _TYPE:XYGATE:
/Last Logon:/
• for _TYPE:SAFEGUARD:
/Last Logon:/
d. For each hostname specified by ems_hostnames, you can add the following hostspecific EMS parameters at the bottom of the file that is displayed.
These parameters end with _NSserver, where NSserver is one of those listed for
ems_hostnames. However, you can also specify _ANYSYS for parameters pertaining
to all hosts. If the same parameter is specified that end with _NSserver, the
corresponding _ANYSYS parameter is overridden.
Parameter
Description
Values
Required
ems_hostaddr_
NSserver
Specifies the Telnet target for
each host.
An IP
address or
DNS name
Yes
ems_hostport_
NSserver
Specifies the target Telnet port.
Integer
No
List of tape
device
names
separated by
spaces
Yes
ems_hostdevs_
NSserver
Default value: 23 (set for
_ANYSYS)
Specifies the list of tape device
names configured on the
NonStop server that are
connected to VTS.
Configuring EMS Communication | 85
Parameter
Description
Values
Required
ems_virtdevs_
NSserver
Specifies the list of virtual tape
drives known to the NonStop
server that correspond to the
list specified by
ems_hostdevs_NSserver. If
this entry is omitted, VTS uses
the same names listed for the
host. If specified, there must be
the same number of virtual tape
names as host tape names.
There is a one-to-one
correspondence.
List of
virtual tape
drives
separated by
spaces
Yes
ems_notify_wait_
timeout_NSserver
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
Integer
No
Default value: 20
ems_notify_logout_
timeout_NSserver
Specifies the number of seconds
to wait after issuing the
LOGOUT command and before
closing the socket connection.
Default value: 3
ems_response_
timeout_NSserver
Specifies the timeout value (in
seconds) used to wait for each
response during the EMS Telnet
login process.
Default value: 5
86 | Configuring EMS Communication
Parameter
Description
Values
Required
ems_login_
command_NSserver
Initiates the EMS Distributor
on the NonStop server. The
name variable in the command
($VTMS1 in the following
example) should be unique for
every VTS server.
An empty
string or CR
to send a
carriage
return
Yes
Example:
ems_login_command_DEV2='
#SET #INFORMAT TACL
|EMSDIST /CPU 0, PRI 100,
NAME $VTMS1, TERM
$ZHOME/ BACKUP 1, TYPE P,
COLLECTOR $0, TEXTOUT
[#MYTERM]'
Multiple
commands
separated by
|
or
Note: When configuring this,
include everything on a single
line.
ems_vaults_
NSserver
Restricts access to vaults from
any hosts.
_ANYSYS is not valid here.
This list of permitted vaults
should be specified as a spacedelimited 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_resetdevs_
NSserver
e.
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.
List of
vaults
separated by
spaces
No
List of tape
names
separated by
spaces
No
Click SAVE to save all changes.
Here is an example of the required parameters:
ems_enable='YES'
ems_hostnames='DEV2'
ems_hostaddr_DEV2='192.168.50.66'
Configuring EMS Communication | 87
ems_hostdevs_DEV2='$TAPE25'
ems_virtdevs_DEV2='VTAPE25'
ems_service_select_DEV2='TACL'
ems_login_command_DEV2='#SET #INFORMAT TACL |EMSDIST /CPU 0, PRI
100, NAME $VTMS1, TERM $ZHOME/ BACKUP 1, TYPE P, COLLECTOR $0,
TEXTOUT [#MYTERM]'
Here is an example of the parameters set in the default VTS configuration file:
ems_enable='NO'
ems_mount_delay='0'
ems_notify_enable='NO'
ems_notification_enable='NO'
ems_notification_level='ERROR CRITICAL'
ems_keep_alive='YES'
ems_notify_hostnames=''
ems_notify_wait_timeout='20'
ems_notify_logout_timeout='3'
ems_InterSystemCommunication_hosts=''
ems_hostport_ANYSYS='23'
ems_response_timeout='5'
ems_service_prompt_ANYSYS='/^Enter Choice>\s*$/i'
ems_service_select_ANYSYS='TACL'
ems_login_userprompt_TYPE:TACL='/TACL 1>\s*$/'
ems_login_useranswer_TYPE:TACL='logon %username%'
ems_login_passprompt_TYPE:TACL='/Password:\s*$/i'
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:XYGATE='%password%'
ems_login_successful_TYPE:XYGATE='/Last Logon:/'
ems_service_answer_TYPE:SAFEGUARD='logon'
ems_login_userprompt_TYPE:SAFEGUARD='/TACL 1>\s*$/'
ems_login_useranswer_TYPE:SAFEGUARD='logon %username%'
ems_login_passprompt_TYPE:SAFEGUARD='/Password:\s*$/i'
ems_login_passanswer_TYPE:SAFEGUARD='%password%'
ems_login_successful_TYPE:SAFEGUARD='/Last Logon:/'
ems_login_command_ANYSYS=''
88 | Configuring EMS Communication
3. Set the username and password for each EMS host:
a. Click Supervisor Functions on the navigation pane.
b. Click Manage Passwords. The following page is displayed:
c.
From the drop-down list, select the EMS host.
Note
If the EMS hostnames are not in the list, the ems_enable parameter may not
be set to YES.
d. In the Username field, type a username for that host.
e.
In the New Password field, type a password for the user.
f.
Retype the password in the New Password (again) field.
g. Click Update.
h. Repeat steps c-g for each additional EMS host defined in the configuration file.
Note
Follow this procedure to change a password after it is set.
4. 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.
Some of the text in the messages and errors is parameterized, as indicated by the dollar
sign ($). In a real message, the parameterized text is replaced by a real value. For
example, the host system that initiated the request is represented in the message text as
$host, but an actual message displays the real hostname, such as DEV2.
•
The severity of the message. The levels of severity include the following:
•
Informational (Inform) — A normal operation has occurred.
•
Warning — A suspicious operation, configuration, or user error has occurred. The
system or application can handle the error with no interruption and limited
degradation of service.
•
Critical — A system or service error has occurred. The system can recover but a
momentary loss or permanent degradation of service may occur.
Configuring EMS Communication | 89
•
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.
AUTOCOPY FAILED: Request by:
$requestor ($retry_number) cannot
reach $target/$filename (rc=$rc)
Critical
No action is required. The task will
be retried.
AUTOCOPY FAILED: Requested
by: $requestor ($retry_number)
from $target/$filename(rc=$rc)
Critical
The autocopy task failed. Correct
the problem and resubmit the job.
AUTOCOPY STARTING: Request
by: $requestor ($retry_number) scp
from $sourcedir/$filename to
$target/$filename
Inform
AUTOCOPY SUCCESSFUL:
Requested by: $requestor
($retry_number) from $sourcedir/
$filename to $target/$filename
Inform
BEX – No files found to restore
Inform
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.
Error: $jobname ENDED
$jobnumber to $backupSystem
Unable to get cartridge lock
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: $jobname ENDED to
$backupSystem rc=$rc
Critical
The IDR request failed. See the Job
History table on the Virtual Media Instant DR page for details. Repair
the failure and resubmit.
90 | Configuring EMS Communication
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. Ensure that the
backup request specifies archive or
backup.
Error: Can’t find any files with data
to backup for $cart_request.
Warning
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.
Error: Count of files backed up by
NetBackup does not agree with
requested filelist for $cart_request.
Critical
An HSM request failed to find or
process the virtual tapes for the
request.
Error: hsmget: no file(s) specified for
$cart_request
Warning
No non-empty files were found for
the HSM backup request.
Error: hsmput: no file(s) specified
for $cart_request, (n=$n: $cart1
$cart2 … $cartn)
Critical
No non-empty files were found for
the HSM backup request.
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
A TSM failure occurred. Examine
the return (error) code and correct
the problem.
Configuring EMS Communication | 91
Message Text
Severity
Error: Non-zero return-code ($rc)
from NetBackup for $cart_request.
Warning
Error: Processing failed, no files
processed for $cart_request
Critical
No files were successfully processed.
See the HSM get or HSM put log
files on the Supervisory Functions
page for details about the HSM
request.
Error: Success message not found in
NetBackup job output for
$cart_request.
Critical
An HSM request failed to find or
process the virtual tapes for the
request.
Error: there is no pool in the file
path for $cart_request.
Critical
The virtual tape path is not valid.
Repair and resubmit the request.
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. Repair and resubmit the
request.
Error: Volser and/or partition
information not found in job output
for $cart_request
Critical
An HSM request failed to find or
process the virtual tapes for the
request.
HSM not enabled
Critical
HSM must be enabled in the VTS
configuration file before it can be
used.
HSM not enabled
Critical
The hsm_enable parameter is
incorrect. Repair and resubmit the
request.
Info: $host $code $policy
Inform
Info: $host $hsm $policy processed #
file(s) for $cart_request.
Inform
Info: $host back up successful to
tape $physical on server $server by
$client for $cart_request
Inform
Info: $host BEX $policy $cartridges
Inform
Info: $host TSM2/TSM $policy
Inform
92 | Configuring EMS Communication
Recommended Action
Message Text
Severity
Recommended Action
Info: $jobname ENDED to
$backupSystem
Inform
Info: AUTOCOPY $requestor
$source $target ($retry_number)
Inform
Info: AUTOCOPY Complete
$requestor $source $target $retry
Inform
Info: autocopy from $source to
$host:$destination
Inform
Info: cancel mount of $tape
Inform
Info: TMFcopy of $tape
Inform
Non-zero return-code ($rc) from
NetBackup bprestore
Warning
Restored $count file(s)
Inform
Restored $count file(s), rc=$rc
Inform
vtape_ems.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.
Warning: hsm_pool_retrieve: $pool
does not contain pool: $pool
Critical
The pool information is missing
from the hsm_pool_retrieve
parameter in the VTS configuration
file, which is available on the
Supervisory Functions page.
Warning: there is no pool in the file
path.
Critical
The virtual tape path is not valid.
Repair and resubmit the request.
Configuring EMS Communication | 93
94 | Configuring EMS Communication
Enabling Instant DR and AutoCopy
Instant DR is an advanced software module (VT5907 or VT5907-A) that enables you to create
and maintain identical copies of backup data on Virtual TapeServer (VTS) disk storage at one
or more locations. In the event of a disaster, remote recovery operations can begin
immediately using the backup data copy on a remote VTS site.
VTS copies data to remote sites over a wide area network (WAN) TCP/IP connection. Virtual
tapes on the originating VTS server are compressed and transmitted to the remote VTS
server.
If Instant DR is licensed, you can create new Instant DR backup schemes as well as launch
and monitor the remote synchronization processes that are in place.
AutoCopy is also an optional VTS software module, and it enables VTS to automatically copy
a virtual tape from one VTS system to another when a virtual tape has been mounted,
modified, and then dismounted by the host server.
95
Instant DR and AutoCopy features have distinct advantages that may be specific to
individual sites or requirements. In general, Instant DR should be used if files do not change
much from day to day. AutoCopy is best used if files change often throughout the day. Keep
the following in mind when enabling these features:
Instant DR
AutoCopy
How often is data copied?
In batches
Individually, as each virtual
tape is unmounted
When is data transmitted?
Synchronized, once or more
per day
As each virtual tape is
unmounted
How is the feature initiated?
By policy scheduling or the
Dispatch button on the
Instant DR page in the VTS
web interface
Automatically, virtual tapes
in the pool are monitored
and copied when necessary
At what level are changes
made (implementation
granularity)?
Vault, pool, or virtual tape
Pool only
How much data is
transmitted?
Data difference only, which
may reduce data
transmission
Bit-for-bit (1:1) copy
operation
When is bandwidth
consumed?
Per schedule, usually offhours
Throughout the day, may
coincide with user activity
How many backup sites are
supported?
Multiple sites, from one site
to many based on setup
Single site, from one site to
another
Is tuning supported?
Initiates multiple jobs to
overcome delays
Single job only
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. When Instant DR is configured, eth1 is
configured with a routable address to communicate with additional VTS servers at remote
locations.
•
The Event Management Service (EMS) is responsible for monitoring mounts and
dismounts relevant to AutoCopy. Therefore, EMS must be configured and running on the
VTS server as described in Configuring EMS Communication on page 79.
96 | Enabling Instant DR and AutoCopy
•
SSH must be configured on all VTS servers involved in AutoCopy operations. You can also
configure SSH if you want to secure data when copying data to remote locations (for
Instant DR). SSH must be configured for Protocol 2 RSA or DSA encryption using Public
Key Identification only. Public Key Identification requires that the sender’s Public Key be
installed in the specific authorized_keys file on the receiver VTS system. The Public
Key is from the secure Public/Private Key pair for the VTS system’s runtime user, which
is the user ID under which the VTS engine runs.
•
It is very important that SSH communications flow though network connections from one
VTS system to another. A single gigabit connection is used to handle the SSH data
transfer and other communications between VTS systems. If non-VTS related traffic is
flowing over this segment of the company intranet, then a completely separate, second
(private) gigabit subnet must be set up between VTS systems and designated for SSH
data traffic only. Network speeds of less than a gigabit are not recommended. The
ProLiant servers do not support speeds of greater than one gigabit.
After completing the procedures in this chapter, refer to the Instant DR and AutoCopy
chapters in the Virtual TapeServer Operations and Administration Guide for instructions to
configure these features. Further configuration is required to use Instant DR and AutoCopy.
Configuring network settings on all VTS servers
To enable Instant DR and AutoCopy, you must configure network settings for all VTS
locations. To configure the local system, you must attach a monitor, keyboard, and mouse to
the VTS server. To configure remote systems, you must use a remote-access application, such
as VNC, to access those systems, or perform the steps at each site. The IP address, which will
differ for each VTS server, must be configured at the local and remote sites. The default
gateway and subnet mask will be the same for all sites.
In addition, you should be familiar with networking concepts to complete the steps in this
section. You will log in to your local VTS server but will access remote servers using FTP.
Obtain the following information before beginning this procedure:
•
Root access to the VTS system; see Credentials on page 139 for a list of the default
accounts provided on the server
•
IP address, subnet mask, and default gateway of each VTS server
The following steps use two sites as an example of enabling Instant DR or AutoCopy between
two sites, Boston 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 139 for a list of the default accounts
provided on the server.
Enabling Instant DR and AutoCopy | 97
c.
At the [[email protected] default]# prompt, enter startx. This starts the VTS operating
system UI.
d. From the operating system UI, click the Linux Start button at the bottom left-hand
side of the window.
e.
Select System →Network Device Control from pop-up list. The Network Device
Control window is displayed.
f.
Select eth1 and click Configure. The Network Configuration window is displayed:
g. Double-click eth1.
h. Select Activate device when computer starts.
i.
Select Statically set IP Addresses.
j.
Provide the IP address, subnet mask, and default gateway. In this example, the
boston 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
eth1 must have a different IP subnet address then eth0.
k. Click OK.
98 | Enabling Instant DR and AutoCopy
3. Set up the hosts file to configure aliases for each IP address of the VTS servers.
a. Click the Hosts tab.
b. Click New.
c.
Provide the IP address, hostname, and alias for the local VTS server. In this example,
the following values are entered:
•
IP Address: 10.10.2.145
•
Hostname: boston.mycompany.com
•
Aliases: boston
d. Click OK.
Enabling Instant DR and AutoCopy | 99
e.
Repeat these steps for each VTS site.
In this example, after completing these steps for all VTS servers, the Hosts tab looks
like this:
f.
Select File→Save.
g. Click OK.
h. Close the Network Configuration window.
i.
Select eth1.
j.
Click Deactivate.
k. Click Activate.
l.
Select eth0.
m. Click Deactivate.
n. Click Activate.
o.
From the operating system GUI, select the Screen icon located at the bottom left-hand
side of the window. A command prompt window is displayed.
100 | Enabling Instant DR and AutoCopy
p. At the [[email protected] default]# prompt, enter service network restart. The
network interfaces are reset:
q. Test connectivity by pinging the network connections. At the prompt, enter ping
hostname. For example, to ping the Boston server, enter ping boston. Output
similar to the following is displayed:
64
ms
64
ms
64
ms
64
ms
bytes from boston (141.36.136.31): icmp_seq=0 ttl=64 time=0.053
bytes from boston (141.36.136.31): icmp_seq=1 ttl=64 time=0.053
bytes from boston (141.36.136.31): icmp_seq=2 ttl=64 time=0.053
bytes from boston (141.36.136.31): icmp_seq=3 ttl=64 time=0.053
Press CTRL-C to stop the ping process.
If you receive a timeout error, check cabling or contact a network administrator for
assistance. If you receive an unknown host error, check the Hosts tab on the Network
Configuration window or use a text editor to check the /etc/hosts file and make sure
everything is correct. Note that the file is case-sensitive.
4. Set up and edit the /home/bill/.rhosts file to define aliases for the IP addresses. Perform
this step for each VTS server.
a. At the command prompt, log in as root. If you Telnet or SSH to the remote VTS server,
you must log in as bill and enter the password when prompted. Then, you must enter
the su command and enter the password. See Credentials on page 139 for a list of the
default accounts provided on the server.
b. Enter chown bill /home/bill/.rhosts to change the ownership of the file to bill.
c.
Enter chmod 600 /home/bill/.rhosts to set the privileges to read and write for bill.
d. Open the /home/bill/.rhosts file for editing using a text editor, such as vi.
e.
Scroll down to the last line in the file.
Enabling Instant DR and AutoCopy | 101
f.
Add the name of all other VTS servers in this file. For example, on the Los Angeles
VTS server, enter boston.
g. Save and exit the file.
5. Set up and authorize secure shell (SSH) if you are configuring VTS for AutoCopy or if you
wish to secure communication for Instant DR.
a. At the command prompt, change to the /home/bill directory.
b. Enter the following command:
ssh-copy-id –i /home/bill/.ssh/id_dsa.pub [email protected]
c.
When prompted, enter yes.
d. Enter the password for the bill user at the destination server.
e.
Enter the following command:
ssh-copy-id –i /home/bill/.ssh/ id_rsa.pub [email protected]
f.
When prompted, enter yes.
g. Enter the password for the bill user at the destination server.
h. Repeat these steps for each VTS server. (If you are on losangeles, you must copy to
boston. If you are on boston, you must copy to losangeles.)
6. Check the RSH connection. At the command prompt, enter rsh server uptime. For
example, on the Boston server, enter rsh boston uptime.
This command displays the amount of time that the system has been up.
Repeat this step on each remote server. You should get similar results.
7. Check the SSH connection, if you configured SSH. At the command prompt, enter ssh
server uptime. For example, on the Boston server, enter ssh boston 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.
Note
RSH and SSH can be setup for one direction or multiple directions. If multiple
directions are configured, these steps should be executed from the other direction.
Configuring TCP/IP security
The need for security while using Instant DR becomes necessary if the communication link
between VTS servers is not completely within your network. If you do not secure the link,
others can gain access to the VTS operating system over TCP/IP from outside the corporate
network. To tighten security, you can configure IP tables to block all TCP/IP traffic going to
eth1 except SSH, RSH, and ICMP (ping and traceroute).
102 | Enabling Instant DR and AutoCopy
To configure TCP/IP security
1. On the VTS server, create the /etc/sysconfig/iptables file and open it for editing.
2. Insert the following lines:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -i eth1 -p tcp -m tcp --dport 22 -j ACCEPT
-A INPUT -i eth1 -p tcp -m tcp --dport 873 -j ACCEPT
-A INPUT -i eth1 -p udp -m udp --dport 873 -j ACCEPT
-A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT
-A INPUT -p tcp -m state --state RELATED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i eth1 -j REJECT --reject-with icmp-port-unreachable
-A INPUT -p tcp -m state --state INVALID -j REJECT
--reject-with icmp-port-unreachable
COMMIT
Here is an explanation of these lines:
•
*filter
Set the “filter” table as the table to be modified.
•
:INPUT ACCEPT [0:0]
Sets the INPUT chain to a default value of ACCEPT. The [0:0] parameter is the count
of packets and bytes to be set when establishing this chain.
•
:FORWARD ACCEPT [0:0]
Sets the FORWARD chain to a default value of ACCEPT and its packet and byte
counters to 0.
•
:OUTPUT ACCEPT [0:0]
Sets the OUTPUT chain to a default value of ACCEPT and its packet and byte
counters to 0.
•
-A INPUT -i eth1 -p tcp -m tcp --dport 22 -j ACCEPT
Allows connections on port 22 (SSH).
•
-A INPUT -i eth1 -p tcp -m tcp --dport 873 -j ACCEPT
-A INPUT -i eth1 -p udp -m udp --dport 873 -j ACCEPT
Allow RSH connections on UDP and TCP port 873.
•
-A INPUT -p tcp -m state --state ESTABLISHED -j ACCEPT
Tracks the connections and allows only established connections. An established
connection is associated with a connection that has seen packets in both directions.
•
-A INPUT -p tcp -m state --state RELATED -j ACCEPT
Allows connections that are of a related state only. A related connection is a new
connection that is associated with an existing connection.
•
-A INPUT -p icmp -j ACCEPT
Allows ICMP traffic (ping and traceroute). This is not required but is helpful when
troubleshooting network issues.
Enabling Instant DR and AutoCopy | 103
•
-A INPUT -i eth1 -j REJECT --reject-with icmp-port-unreachable
Rejects all traffic with the exception of the preceding rules.
•
-A INPUT -p tcp -m state --state INVALID -j REJECT
--reject-with icmp-port-unreachable
Sends a rejected notification to the invalid sender. You can change REJECT to DROP
to drop the traffic without a rejection notification. Note that this should be entered on
one line.
•
COMMIT
Causes the preceding commands to take effect.
3. Save and close the file.
4. Enter the following commands:
chkconfig iptables on
service iptables start
At this point, all TCP/IP traffic is blocked except for SSH, RSH, and ICMP (ping and
traceroute) traffic.
5. Repeat these steps on each VTS server.
Now, complete the configuration steps described in the Virtual TapeServer Operations and
Administration Guide.
104 | Enabling Instant DR and AutoCopy
Enabling Enterprise Integration and Migration
Enterprise integration enables a backup management application server to read and write
files to and from Virtual TapeServer (VTS). You can enable VTS to migrate virtual tapes to
physical tapes. To configure VTS to automatically migrate virtual tapes, you must install a
backup management application client on the VTS server and configure the VTSPolicy
command in conjunction with the Event Management Service (EMS) on VTS. You can also
manually initiate migration by clicking the Migrate button on the Virtual Media - Operation
page. A backup management application client must be installed on the VTS server to enable
manual migration.
VTS supports the following backup management applications for migration:
•
IBM Tivoli Storage Manager
•
Symantec Veritas NetBackup
•
Syncsort Backup Express
•
EMC Legato Networker
Migration allows for better use of the disk space on the storage array. For instance, if a virtual
tape needs to be saved for seven years for legal purposes, it is not fiscally prudent to keep that
data on disk. You could automatically migrate the virtual tape to physical tape. In the
unlikely event that the virtual tape is needed, VTS can automatically request that the backup
management application server restore it from physical tape.
When a virtual tape is migrated to physical tape, all data on the virtual tape is written to
physical tape, including the header information (metadata). The data is then removed from
VTS, though the virtual tape’s metadata is retained. To restore a physical tape that was
automatically migrated by a backup management application, the backup management
application must restore the tape to VTS. Host servers cannot read physical tapes that were
created through migration because the tape is formatted for use by VTS only. After the data is
restored as a virtual tape in VTS, the host server can then restore the data.
Note
You can export a virtual tape to physical tape, which does not require backup
management application integration. See the Virtual TapeServer Operations and
Administration Guide for more information about exporting virtual tapes.
The backup management application client must be installed on the VTS server, which is
based on the Linux operating system. The backup management application treats VTS as a
UNIX host on the enterprise network. Virtual tapes are then migrated to the tape library
105
managed by the backup management application server according to policies set by the
backup management application administrator. The backup management application server
can migrate virtual tapes using the following methods:
•
The backup management application administrator creates a backup job on the backup
management application server and schedules it to run on the backup management
application client. The backup management application server manages the entire
process and maintains a database of the backup files including a list of physical tapes to
which the data was written. The backup management application server also controls the
tape library.
If VTS deletes or erases a virtual tape, the backup management application administrator
must restore the virtual tape, when necessary. If the 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 backup management application server from physical tape.
•
VTS can request that the backup management application server perform a backup or
restore. This request is generated when you manually initiate a migration. This request is
issued using the backup management application command-line interface. VTS generates
the backup management application command request and sends it directly to the backup
management application server. The backup management application server then
identifies the tape to back up or restore and instructs the tape library to perform the
operation.
•
A VTSPolicy command sent from the host server through EMS can initiate migration.
VTSPolicy can initiate many of the commands that are available on the backup
management application server. The command can be scheduled on the host server using
NetBatch or appended to a Tandem Advanced Command Language (TACL) backup script.
This chapter describes how to configure VTS for enterprise integration and migration. It also
includes information about adding a physical tape drive, which may be necessary for
migration. Refer to the Virtual TapeServer Operations and Administration Guide for
instructions to manually initiate migrating virtual tapes, encrypt data during migration, and
automate migration using the VTSPolicy command.
106 | Enabling Enterprise Integration and Migration
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.
Requires the View/Manage Configuration, Factory Setup Activities, and Halt and Reboot
TapeServer access rights
To add a physical drive to the VTS server
1. If necessary, modify the system limits defined for the bus to which you will attach the
physical drive. A virtual tape may be defined on the bus if the full configuration of twelve
virtual tape drives was set during manufacturing of VTS. Complete the following steps:
a. Delete the connection that uses the target bus. On the VTS interface, click Manage
Connections on the navigation pane, and then click Delete a tape connection. The
Delete A Tape Connection page is displayed:
b. Select the connection that assigns the virtual device for the target bus and click
Delete Tape Connection.
Enabling Enterprise Integration and Migration | 107
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. See
Credentials on page 139 for a list of the default accounts provided on the server.
g. Click Factory Options, and then enter the login credentials.
h. Click Manage system limits. The Manage system limits page is displayed.
i.
Select the Physical checkbox that corresponds to the target bus and then click Set
Limits. The VTS server automatically reboots.
2. Power down the VTS server and then cable the physical tape drive (through the SCSI
converter as necessary) to the VTS server. Then, power on the physical tape drive and
SCSI converter.
3. Power on the VTS server.
108 | Enabling Enterprise Integration and Migration
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:
sg_map –x
Here is an example of the output from this command:
/dev/sg0
0 0 3 0
1
/dev/nst0
/dev/sg1
6 0 0 0
5
/dev/scd0
/dev/sg2
6 0 0 1
5
/dev/scd1
/dev/sg3
6 0 0 2
5
/dev/scd2
/dev/sg4
6 0 0 3
5
/dev/scd3
/dev/sg5
6 0 0 4
5
/dev/scd4
/dev/sg6
6 0 0 5
5
/dev/scd5
/dev/sg7
6 0 0 6
5
/dev/scd6
Then, find the nst0 entry (tape drive) attached and then enter this command:
sg_inq /dev/sgn
where sgn is the number that matches the /dev/nstn device. For the output listed above,
you would enter sg_inq /dev/sg0. Here is an example of the output from this command:
standard INQUIRY:
PQual=0 Device_type=1 RMB=1 [ANSI_version=4] version=0x04
[AERC=0] [TrmTsk=0] NormACA=0 HiSUP=0 Resp_data_format=2
SCCS=0 ACC=0 ALUA=0 3PC=0 Protect=0
BQue=0 EncServ=0 MultiP=0 MChngr=0 [ACKREQQ=0] Addr16=1
[RelAdr=0] WBus16=1 Sync=1 Linked=0 [TranDis=0] CmdQue=0
Clocking=0x3 QAS=0 IUS=0
length=74 (0x4a)
Peripheral device type: tape
Vendor identification: CERTANCE
Product identification: ULTRIUM 3
Product revision level: 1770
Product serial number: JD006D2
Repeat for each tape drive that was added.
Configuring migration
Be sure that the backup management application client is installed and configured on the
VTS server. Refer to the backup management application documentation for more
information. Then, modify the VTS configuration file to configure migration, which entails
configuring the hsm_ parameters as defined below, and set the username and password.
Note
A default configuration file is defined for each VTS server. To override the default
settings, you must define settings as described below.
Enabling Enterprise Integration and Migration | 109
Requires the Edit VTS Configuration File access right
To configure migration
1. Click Supervisor Functions on the navigation pane of the VTS interface.
2. Click Edit VTS Configuration File.
3. Add the following parameters at the bottom of the file that is displayed:
Parameter
Description
Values
Req’d?
hsm_enable
Enables migration.
YES or NO
Yes
BEX, NBP,
TSM, or LEG
Yes
Hostname
Yes
Pool name
Yes
Pool names,
separated by
spaces
Yes
checksum,
EOJ, or
retention
Yes
checksum,
EOJ, or
retention
Yes
Name of the
restore device.
No
Default value: YES
hsm_product
Identifies the backup management
application:
•
•
•
•
BEX for Backup Express
NBP for NetBackup
TSM for Tivoli Storage Manager
LEG for Networker
For automated migration, you can
specify any of these values, which
depends on the backup management
application. For manual migration,
you must specify TSM.
Default value: TSM
hsm_server
For Backup Express, NetBackup,
and Networker only:
Specifies the backup management
application server hostname.
hsm_pool
For Networker only:
Specifies the pool name.
hsm_backup_pools
For Backup Express only:
Specifies the pool names where the
virtual tapes to be migrated reside.
hsm_backup_
options
For Backup Express only:
hsm_backup_
options_poolname
For Backup Express only:
hsm_restore_device
For Backup Express only:
Specifies the backup options for all
pools.
Specifies the backup options for the
pool specified by poolname.
Specifies the restore device.
110 | Enabling Enterprise Integration and Migration
Parameter
Description
Values
Req’d?
hsm_optfile
For Tivoli Storage Manager only:
Path
Yes
Path
No
Integer, from
1-30
No
Policy
Yes
Schedule
Yes
YES or NO
No
Integer, from
0-999
No
Specifies the path to the optfile file.
Default value: dsm.opt
hsm_optfile_pool
For Tivoli Storage Manager only:
Specifies the path to the optfile file
for a specific pool. This parameter
overrides the hsm_optfile
parameter for the pool.
hsm_put_batch_size
For Tivoli Storage Manager only:
Specifies the maximum number of
virtual tapes to lock and migrate at
a time, thereby creating batches of
tapes to migrate. This parameter is
optional and set to 0 by default,
which causes VTS to lock all target
virtual tapes until the migration is
complete.
Note: Using this parameter may
impact performance, slowing the
migration.
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. Only the tape data is
erased; the metadata remains.
Default value: NO
hsm_joblog_
maxnum
Specifies the maximum number of
job log files to be retained. These
files contain the output from each
job. This value applies separately to
backup and restore jobs. If set to
zero, no logs are retained.
Default value: 20
Enabling Enterprise Integration and Migration | 111
Parameter
Description
Values
Req’d?
hsm_summary_limit
Specifies the number of lines
retained in the log file, which
records the command used to invoke
each backup or restore job. This is a
joint log that contains only the
commands used, not the job output.
Integer
No
Value
No
YES or NO
No
Default value: 1000
hsm_restore_period
For Backup Express only:
Specifies how far back in time the
backup management application
should search its catalog for the file
to be restored. Specify the restore
period in the nnU format where:
• nn is a number between 1 and 99
• U is the unit; specify “d” for days,
“w” for weeks, or “y” for years
Default value: 90d
ems_hsm_backup_
notification
Sends notifications to the NonStop
kernel (NSK) from the EMS Telnet
policy process. For example, after a
virtual tape is migrated, a
successful or failed message is
generated so that the NSK can
determine if the operation was
successful.
Default value: YES
Here are sample configurations for each backup management application:
•
Backup Express:
hsm_enable='YES'
hsm_product='BEX'
hsm_server='lab-bex'
hsm_backup_pools='MEDIAPOOL DLT DEVICEPOOL'
hsm_backup_options='CHECKSUM Y; EOJ_ACTION U; RETENTION 999;'
hsm_backup_options_LABELED='CHECKSUM Y; EOJ_ACTION U; RETENTION
999;'
hsm_backup_options_CADE='CHECKSUM Y; EOJ_ACTION U; RETENTION 999;'
ems_hsm_backup_notification='YES'
hsm_restore_period='90d'
•
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'
112 | Enabling Enterprise Integration and Migration
•
NetBackup:
hsm_enable='YES'
hsm_product='NBP'
hsm_policy='POLICY'
hsm_schedule='SCHEDULE'
hsm_server='SERVER'
ems_hsm_backup_notification='YES'
•
Networker:
hsm_enable='YES'
hsm_product='LEG'
hsm_pool='POOL'
hsm_server='SERVER'
ems_hsm_backup_notification='YES'
4. Click SAVE.
5. Set the username and password for the backup management application.
Note
This step is required for Backup Express and NetBackup only.
a. Click Supervisor Functions on the navigation pane.
b. Click Manage Passwords. The following page is displayed:
c.
From the drop-down list, select hsm.
d. In the Username field, type the username that is required to log in to the backup
management application.
e.
In the New Password field, type the user’s password.
f.
Retype the password in the New Password (again) field.
g. Click Update.
Enabling Enterprise Integration and Migration | 113
114 | Enabling Enterprise Integration and Migration
Troubleshooting
This appendix provides information to assist you in addressing problems you may encounter
while installing and using Virtual TapeServer (VTS). If you cannot solve an issue using this
information or if you must contact Support, gather the following information:
•
VTS model number
•
The operating system and firmware versions of the VTS server
•
The version of VTS, which can be found on the System Status page
•
Whether external storage is attached to VTS (disk array, network attached storage, and
so on)
•
The symptom of the problem
•
The last time VTS functioned properly
•
The task (backup, restore, export, and so on) that was occurring at the point of failure
You can also run the getVTS_dbginfo utility, which is provided on the VTS server. This utility
collects log files and system information that can used to troubleshoot VTS issues. To run
getVTS_dbginfo, log in to the VTS server as root and enter the following command:
/usr/local/tape/bin/getVTS_dbginfo
Do not run getVTS_dbginfo from the /usr/local/tape/bin directory. A zipped archive file
named VTStimestamp.zip is created in the directory from which the utility is run. For
example, if you run getVTS_dbginfo from /tmp, the file is created in /tmp. After the file is
created, send it to Support.
Diagnostic techniques
For diagnosing problems, the following tools may be helpful.
PuTTY (Telnet/SSH client)
This is a GUI-based application to issue Telnet, SSH, and other connection commands to a
host server. You can download PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/
putty/.
Virtual Network Computing remote control software
VNC software enables you to remotely access the console of a UNIX server. VNC must be
configured on the host server before you can use it from a client. You can download VNC from
http://www.vnc.com/.
115
HP health monitoring utilities
The VTS server provides the following:
•
HP Systems Insight Manager (HPSIM-Linux-C.05.02.02.00.bin)
•
HP System Health Application and the HP Insight Management Agents (hpasm-8.0.0173.rhel5.x86_64.rpm)
•
HP System Management Homepage (hpsmh-2.1.12-200.x86_64.rpm)
•
SNMP agent access to the HP iLO management controller (hp-ilo-8.1.0104.rhel5.x86_64.rpm)
These utilities can be used for managing HP systems to maximize system uptime and health.
The agent package integrates with HP Systems Insight Manager (SIM), Insight Manager
Console, HP Services Essential Remote Support Pack, and HP NonStop Cluster Essentials. It
monitors all serviceable system components (drives, fans, power supplies, and so on).
To use these utilities, you must configure them. Refer to http://h18013.www1.hp.com/
products/servers/management/hpsim/infolibrary.html for instructions. The relevant links
include “Install and configure”, “How to use”, “Advanced management features”, and “Man
pages”.
HP Integrated Lights-Out (iLO) and HP Integrated Lights-Out 2 (iLO 2)
This enables you to log in to the VTS server using the iLO virtual serial port. For more
information about using iLO, refer to http://h20000.www2.hp.com/bc/docs/support/
SupportManual/c00263709/c00263709.pdf. Note that if you are using a serial connection over
the physical serial port (connected through /dev/ttyS0), use the following connection settings:
•
Speed: 115200 bps
•
Data Bits: 8
•
Parity: None
•
Stop bits: 1
After iLO is configured, you can enable iLO access on the system boot menu by running
/usr/local/tape/bin/grub-serial.bash as root and then rebooting the system. Note that after
the VTS server is rebooted, iLO access to the VTS server is available without running this
script, but you cannot access the boot menu to change boot parameters or select a different
kernel.
Common issues
The following sections provide general information to diagnose hardware components and
software features of the VTS system.
NonStop server
If error 190 occurs on the Subsystem Control Facility (SCF), perform the following:
•
Check the power on VTS.
•
Check the SCSI converter. (Blue LED indicates power is on.)
•
Check the SCSI cable connections for bent or loose pins.
•
QTOS users must stop the QTOS process before stopping or starting a virtual tape drive
from SCF.
116 | Troubleshooting
If error 224 occurs on the SCF, perform the following:
•
Verify that the virtual tape is using the 519X or 5257 definition.
•
Verify that the WWPN, SAC, and Module are correctly listed in SCF for the tape device.
If an “end of media” message is displayed on the host, erase expired virtual tapes to clear disk
space.
If a tape drive stops responding from SCF, perform the following:
•
Check the system log for parity errors or other SCSI-related failures.
•
Check power indicators on the SCSI converter.
•
Check that the virtual tape is connected to a logical device on the System Overview page.
VTS server module
You can troubleshoot various areas of the VTS server module.
Host server
Verify the following:
•
Is the server powered on?
•
Are the lights on?
•
Are all of the cables secured tightly?
•
Are any pins bent on any of the cables?
•
Are all of the PCI cards seated properly? Is the plastic clip secured for each?
•
Are messages present in the Power On Self Test (POST)?
If necessary, reseat the PCI cards. Halt VTS from the web interface, power down the server,
unplug the power cord, and then remove cables and reseat the PCI cards.
Hard drives
Verify the following:
•
Are the hard drives seated properly?
•
What is the color of the drive LED?
A green LED indicates normal operation; amber indicates failure. You can also remove all
hard drives and reseat them individually. Be sure to properly shut down VTS before
performing this operation.
SCSI controllers
You can rescan all SCSI controllers and list the devices. Be sure to stop the tape drives in SCF
on the host server before initiating the scan. Use the following commands to rescan the SCSI
controllers:
cd /usr/local/tape/bin
./rescan-scsi-bus.sh -l -c -r -w
Output is listed on screen and in the /usr/local/tape/log/rescan.txt file. The VTS
application must be restarted when a new physical tape device is found and must be used.
If the new devices were not detected, you can unplug the Fibre Channel connection to the VTS
server for two minutes or reboot the system.
Troubleshooting | 117
File system
Verify the following:
•
Has anything changed?
•
Is performance slow?
•
Is GFS running on the system?
•
Is the problem occurring for a particular vault or all vaults? Is the problematic vault on
internal or external disk storage?
•
What is the result of the last vault check on the external storage?
You can check for FSCK messages in the system log, as well as the result of the last vault
check. If GFS is running, check connectivity between the systems by pinging the systems from
the command line of the operating system.
To diagnose file system problems, the following commands are useful:
df
Shows disk utilization
top
Shows CPU utilization, swap space, zombie processes, and so on
top -b -n 10 > output.txt
Runs top in batchmode
Shows file space usage
du
ps –xaf
Lists running processes
tail –f –n 24
Displays a real-time file listing
grep
Searches for a string in a file
man
Displays help
more
Lists a file
reset Resets the current terminal
Database
Use the following commands, respectively, to stop, start, or restart the database (halt VTS
before issuing these commands):
•
/etc/init.d/rhdb stop
•
/etc/init.d/rhdb start
•
/etc/init.d/rhdb restart
You can also reboot VTS to attempt to solve the problem.
Web interface
If the web interface stops responding, verify the following:
•
Access the interface from a different workstation.
•
Ping the address.
•
Check the Ethernet cable.
•
Check Ethernet connectivity and activity LEDs.
118 | Troubleshooting
The Apache web server is responsible for running the VTS web interface. To verify that
Apache is running:
/etc/init.d/httpd status
A message similar to the following should be displayed:
httpd (pid 25380 25015 25014 25013 25012 25011) is running...
Use the following commands, respectively, to stop, start, or restart the web server (halt VTS
before issuing these commands):
•
/etc/init.d/httpd stop
•
/etc/init.d/httpd start
•
service httpd restart
Note
If you restart the HTTPD service using the /etc/init.d/httpd restart command,
the owner is set to “apache” not “bill” and the web service (and interface) stops
responding.
You can also reboot VTS to attempt to solve the problem.
Log files
The following log files may help you diagnose problems.
Operating system:
•
/var/log/messages
•
/var/log/cron
•
/var/log/boot.log
Apache web server:
•
/var/log/httpd/error_log
•
/var/log/httpd/access_log
VTS:
•
/usr/local/tape/log/ems.* (available from the VTS web interface)
•
/usr/local/tape/log/debug.* (available from the VTS web interface; set the severity level
by selecting Factory Setup→Administrator Utilities→Set current debug level)
•
/usr/local/tape/log/mount.log
•
/usr/local/tape/log/export.log (available from the VTS web interface)
•
/usr/local/tape/log/event.log (available from the VTS web interface; see page 123 for
more information)
•
/usr/local/tape/log/scanat.log
•
/usr/local/tape/log/vtape.log
•
/usr/local/tape/log/upgrade.log
•
/usr/local/tape/log/ems.lastmount.cmd
•
/usr/local/tape/log/rescan.txt
•
/usr/local/tape/log/SecureVTS.log
Note
Though you can change the log level of these files, the log level is reset to the default
every time VTS is rebooted.
Troubleshooting | 119
To view log files, the following commands are useful:
vi logfile
To edit and search the file
tail –f –n 35 logfile
To list the file in real-time
grep –ni string logfile
To search for a specific string
more logfile
To search a file by paging through it
SCSI converter
During normal operation, the LEDs on the SCSI converter blink every 3-5 seconds. During
backups, the activity LED is almost solidly lit.
•
Is the power turned on?
•
Are all of the cables secured tightly?
•
Are any pins bent on any of the cables?
•
Are all four ports in use?
•
Is normal communication occurring while SCF is running?
Be sure to stop the tape drive in SCF on the host server and power off the SCSI converter
before disconnecting cables.
External storage or the SAN
Verify the following:
•
Is the storage array powered on?
•
Are the lights on?
•
Are all of the cables secured tightly?
•
Are any cables broken?
•
Is the delink LED on? What is the color of the LED?
A green LED indicates normal operation; amber indicates failure.
If the HP StorageWorks Enterprise Virtual Array (EVA) is used for external storage, you may
see duplicate LUNs if you do not configure path failover. Refer to Path failover on page 25 for
information about configuring path failover.
Software features
Check the System Status page to confirm that all virtual tape devices are listed. This ensures
that VTS is presenting each virtual tape device and indicates which devices are running.
The following sections may help you diagnose problems with various software features of
VTS.
120 | Troubleshooting
Event Management System (EMS)
Verify the following:
•
Has the EMS logon expired?
•
Is there network connectivity between VTS and the NonStop server?
•
Was the VTS operating system or the EMS template upgraded?
•
Is VTS up-to-date with the latest product enhancement code?
•
Is there a typographical error in the VTS configuration file?
You can check the EMS log file for the last timestamp of messages.
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.
•
On the Supervisory Functions page of the VTS web interface, click Stop EMS Service, and
then click Start EMS Service to restart the EMS auto-mounting service.
•
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.
•
From the NonStop server, enter STATUS *, USER (username) to see if the EMSDIST
process is active.
•
Check /usr/local/tape/log/ems.log. Go to the bottom of the log to look for problems.
•
View the Virtual Media - Mounts and Locks page. View the list of locked virtual tapes. If
you are certain that a particular virtual tape is not in use but VTS indicates that it is
locked, remove the lock here.
Virtual tape operations
If you are unable to manually mount a virtual tape, perform the following:
•
Check the color of the virtual tape label. Gray indicates the virtual tape is in use by
Import/Export or is remotely mounted.
•
Verify that the autoloading library containing the virtual tape is not in use.
•
Verify that SecureVTS is enabled and configured properly in a cluster environment. The
mount will fail, for example, if the key server is not configured on all servers.
If you cannot import a physical tape, perform the following:
•
Check the tape drive for power.
•
Check the tape drive for tape ready indicators.
•
Check the SCSI cable to the tape drive.
•
Check file system Free (Pct).
If you cannot export a virtual tape or an export failed, perform the following:
•
Check the tape drive for power.
•
Check the tape drive for tape ready indicators.
•
Check the SCSI cable to tape drive.
Troubleshooting | 121
•
Check that the tape is in the drive.
•
Check the media write-protection.
If you cannot access a virtual tape because it is locked, perform the following:
•
Check MEDIACOM for label in use.
•
Check other VTS systems for remotely mounted virtual tapes.
•
Reboot VTS to clear all local file locks.
If an autoloading pool did not recycle, verify that Autoloading or Recycle is selected on the
Pool Maintenance page.
SecureVTS and failed tape operations
If VTS attempts to perform an operation on an encrypted virtual tape, SecureVTS must be
enabled and the key server that was used to encrypt the tape must be configured on the server
where the tape resides. If not, the tape operation will fail and an error message is displayed
indicating that the operation failed. This section provides an overview of the error messages
that are displayed. See Using SecureVTS on page 81 for instructions on enabling SecureVTS
and configuring a key server.
•
Mounting an encrypted tape
An error similar to the following is displayed:
Also, a message similar to the following is displayed on the web interface:
Request: Mount SHARE:SH0002 on VF40500 for read-write --- Failed!
•
Erasing an encrypted tape:
An error similar to the following is displayed:
Also, a message similar to the following is displayed on the web interface:
Request: Erase SHARE:SH0000 --- Failed!
•
Exporting an encrypted tape:
A message similar to the following is displayed on the web interface:
Thu 2008-01-17 09:49:31: SHARE:SH0000
rc=3
122 | Troubleshooting
Export data transfer failed,
•
Erasing all virtual tapes in a pool on the Cartridge Maintenance page:
A message similar to the following is displayed on the web interface:
Erased 1 cartridge; Erasure of cartridge SH0002 in pool SHARE failed!
•
Setting the virtual tape size on the Pool Maintenance page:
A message similar to the following is displayed on the web interface:
Unable to set size limit on SHARE:SH0001, rc=2. Operation aborted!
After the operation aborts for the encrypted tape, any tapes for which this operation is
attempted will also fail.
You can also check /usr/local/tape/log/SecureVTS.log, which logs all tape operations
associated with encryption. Go to the bottom of the log to look for problems.
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. For example, the log shows
the error that the password is invalid or the IP address did not connect. The event.log file
resides in /usr/local/tape/log on the VTS server.
The system event log file is generated by the VTS operating system (Linux) and records
information about events such as the creation and deletion of virtual tapes, failures of
processes and services, and the status of jobs and policies. The messages are stored in a single
log file, which is plain text and viewable from the user interface. The messages include
information about the time and date of the event as well as the name of the user who initiated
the event. Use the messages in this file to detect problems, track down the source of faults,
and audit users. In addition, information in the system event log can be retrieved by thirdparty applications, such as Prognosis or Insight Manager, for notification purposes.
Requires the View log files access right
To access the system event log from the VTS user interface
Select Supervisor Functions→Log Files→Examine Event Logs.
By default, the Examine the system log file page displays the latest entries in the log, which
are located at the bottom of the file.
•
Click Refresh to refresh the log.
•
Click Top to view the top of the log (and the oldest entries).
•
Click Download to save the entire file to a local directory.
•
Click Previous or Next to page through the file.
Location, retention, and rotation
The /usr/local/tape/log directory contains the current log file, which is named event.log, as
well as the previous 30 log files. The event log is rotated, or “aged,” the same as the other log
files. Log aging is set up to check daily if a log file has reached a size greater than 10KB. If the
size limit is reached then the old log is renamed to a new name containing the rotation
Troubleshooting | 123
number and a new (blank) log begins with the default name. All rotated log files are
compressed except for the first (more recent). Thirty versions of the file are kept. This file is
renewed each day at 4 a.m.
Previous log files are compressed using gzip. If more than seven log files must be maintained,
the files must be backed up manually.
Note
Users must have Read access to the /user/local/tape/log directory.
The following is an example directory listing of seven rotated logs plus the current log file:
-rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--rw-rw-r--
1
1
1
1
1
1
1
1
10240 Jul 25 04:02 ../log/event.log.7.gz
5948 Jul 26 04:02 ../log/event.log.6.gz
2326 Jul 28 04:02 ../log/event.log.5.gz
905 Jul 29 04:02 ../log/event.log.4.gz
998 Aug 1 04:02 ../log/event.log.3.gz
1148 Aug 2 04:02 ../log/event.log.2.gz
1038 Aug 4 04:02 ../log/event.log.1.gz
4521 Aug 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.1|Tapeserver01|administrator|Access Control RESTORE OPEN
defaults have been restored
Entries are divided into the sections described in the following table:
Attribute
Format Example
Description
Timestamp
2006-08-28 16:25:18
Time and date when the message originated, in
a format that is specific to the locale.
Severity
WARNING
The degree of impact or seriousness of the event
reported by the message. (See Message severity
on page 125.)
Message ID
440002
A unique six-digit identifier. All message IDs
contain the severity, subsystem, and message
ID. The unique ID falls within a numerical
range of 0-999999. (See Message IDs on page
126.)
System ID
5900-E
The make and model of VTS on which the
message was generated.
IP address
127.0.0.1
The IP address of the user or client that
initiates a function on a page of VTS.
Server name
Tapeserver01
The Domain Name Server (DNS) name of the
computer that hosts the server instance.
124 | Troubleshooting
Attribute
Format Example
Description
User
administrator
The user ID under which the associated event
was executed.
Message text
Access Control
RESTORE OPEN
defaults have been
restored
A description of the event or condition. (See
Message text on page 126.)
Field limits
Messages are up to 255 characters in length; each message field has a character limit. The
attributes that have a variable length are automatically compressed to the available space.
Message Attributes
Character limit
Timestamp
19
Severity
8
Message ID
6
System ID
7
IP address
15
Server name
15
User
15
Message text
177
Message severity
The severity attribute indicates the potential impact of the event or condition that the
message reports.
Note
Though you can change the debug level on the Set Debug Level page, the debug level
is reset to Error every time VTS is restarted.
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.
4
Warning
A suspicious operation or configuration that might not
affect normal operation.
Troubleshooting | 125
Severity ID
Severity Level
Description
6
Error
A user error that the system or application can handle
with no interruption and limited degradation of service.
8
Critical
A system or service error from which the system can
recover, although there might be a momentary loss or
permanent degradation of service.
Message IDs
Each six-digit message ID is made up of the following:
•
The first digit represents the severity ID (see Message severity on page 125)
•
The second and third digits represent the subsystem ID
•
The final three digits represent the event ID
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.
Event
VTS
Message ID
User restores open system defaults
440002
Access Control RESTORE OPEN
defaults have been restored
User erases a virtual tape
421013
Cartridge XXXXX erased in Pool
XXXXX
User manually mounts a tape
220001
Cartridge XXX for read-write has
been manually mounted
User manually unmounts a tape
220002
Cartridge XXX has been manually
unmounted
Message Text
Message text
The following tables list the message IDs and corresponding message text that are generated
for events in the system event message log.
Media operations
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
20
001
Manual mount
Cartridge XXX for ACCESS has
been manually mounted
EMS
2
126 | Troubleshooting
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
6
20
001
Manual mount
Cartridge XXX mount failed,
rc=RC
8
20
001
Manual mount
Cartridge XXX mount failed,
rc=RC
2
20
002
Manual
unmount
Cartridge XXX has been
manually unmounted
6
20
002
Manual
unmount
Cartridge XXX unmount failed,
rc=RC
2
20
003
EMS mount
ems mount TAPE for HOST as
ACCESS completed
8
20
003
EMS Mount
ems mount TAPE for HOST
failed rc=RC
2
20
004
EMS mount
Read-Only
ems telnet ems mount of TAPE
by HOST as read-only
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 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
EMS Mount
ems queue cancel TAPE for
HOST of type TYPE failed
2
20
010
EMS Policy
Erase
ems telnet Erase by List LIST
2
20
020
EMS Policy
Delete
ems telnet delete LIST
6
20
020
EMS Policy
ems telnet command error
XXXXX
2
20
030
EMS Policy
IDR
ems telnet IDR
2
20
031
EMS Policy
IDR
ems telnet IDR completes, rc=0
Troubleshooting | 127
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
8
20
031
EMS Delete
Cartridge PATH delete in Pool
POOL failed, rc=RC
4
20
032
EMS Policy
IDR
ems telnet IDR completes,
rc=RC
8
20
032
EMS Policy
IDR
vtape-operation-erase-PATHfailed-rc=RC
2
20
033
EMS Policy
Migrate
Cartridge PATH migrated
6
20
033
EMS Policy
Migrate
Cartridge PATH migrate failed,
path in use, rc=RC
8
20
033
EMS Policy
Migrate
Cartridge PATH migrate failed,
rc=RC
2
20
040
EMS Policy
BEX
ems 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 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 NBP completes, rc=0
8
20
062
EMS Policy
NetBackup
ems telnet NBP completes,
rc=RC
2
20
070
EMS Policy
Legato
ems telnet LEG POLICY
2
20
071
EMS Policy
Legato
ems telnet LEG completes, rc=0
8
20
072
EMS Policy
Legato
ems telnet LEG completes,
rc=RC
128 | Troubleshooting
Severity ID
Subsystem
ID
Event
ID
2
20
8
Subsystem
Message text
096
EMS Policy
HSMPUT
hsmput XXXXXX for HOST
completed
20
096
EMS Policy
HSMPUT
hsmput XXXXXX for HOST
failed, error MSG, rc=RC
2
20
097
EMS Policy
HSMGET
hsmget XXXXXX for HOST
completed
8
20
097
EMS Policy
HSMGET
hsmget XXXXXX for HOST
failed, error MSG, rc=RC
2
20
098
EMS Policy
HSMDELETE
hsmdelete XXXXXX for HOST
completed
8
20
098
EMS Policy
HSMDELETE
hsmdelete XXXXXX for HOST
failed, error MSG, rc=RC
2
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
203
EMS Policy
Mount
ems mount TAPE for HOST
failed parametric test
8
20
204
EMS Policy
Mount
ems cancel TAPE for HOST
failed parametric test
8
20
205
EMS Policy
Mount
ems reject TAPE for HOST
virtual cartridge missing
8
20
2060
EMS Policy
Mount
ems reject TAPE for HOST
tapeserver not running
6
20
207
EMS Policy
Mount
ems reject TAPE for HOST no
host drives available
8
20
208
EMS Policy
Mount
ems reject check TAPE failed for
HOST
Troubleshooting | 129
Severity ID
Subsystem
ID
Event
ID
8
20
8
Subsystem
Message text
209
EMS Policy
Mount
ems reject TAPE for HOST no
virtual drives available
20
210
EMS Policy
ems reject TAPE for HOST
immediate request not
recognized
8
20
213
EMS Policy
ems failure TAPE for HOST
already locked
2
20
250
EMS Policy
TSM
ems_telnet TSM2 POLICY
2
20
251
EMS Policy
TSM
ems_telnet TSM2 completes
rc=0
8
20
252
EMS Policy
TSM
ems_telnet TSM2 completes
rc=RC
Cartridge maintenance
2
21
010
Cartridge
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.
4
21
012
EMS Policy
Delete
ems telnet Delete by list XXXXX
2
21
013
Cartridge
erased
Cartridge TAPE erased in Pool
POOL
4
21
013
Cartridge
erased
Cartridge TAPE not erased in
Pool POOL
6
21
013
Cartridge
erased
Cartridge TAPE not erased in
Pool POOL because it is locked.
4
21
014
EMS Policy
Erase
ems telnet erase XXXXX
001
Pool created
vtape_pool libCreate VAULTXX
Pool maintenance
2
130 | Troubleshooting
22
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
4
22
002
Pool deleted
vtape_pool libDelete VAULTXX
4
22
003
Pool renamed
vtape_pool libRename XXXXX
VAULTYY/YYYY
4
22
004
Pool moved
vtape_pool libMove XXXXX
YYYYY
2
22
005
Size set
vtape_pool libApply set tixe
limit PATH from SIZE to SIZE
2
22
007
Retention set
vtape_pool libApply set
retention PATH RETAIN
2
22
008
Retention
modified
vtape_pool libApply vtmeta
FILES from RETAIN to
RETAIN
2
22
009
Set Pool to
Autoloader
vtape_pool libApply change
autoload PATH from PATH to
PATH
2
22
010
Set Pool to
Autoloader
vtape_pool libApply set autoload
PATH
2
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
manually
IDR start NNNN as MMM
2
24
002
Job Stopped
manually
IDR Job JOB stopped by
operator
2
24
003
Job successful
IDR job JOB done rc=0
8
24
004
Job Failed
IDR job JOB done rc=RC
4
24
005
Job deleted
IDR job JOB stopped by
operator
Locks
Instant DR
Troubleshooting | 131
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
2
24
006
Job Completed
IDR job JOB completed rc=0
8
24
006
Job Completed
IDR job JOB completed rc=RC
2
24
007
IDR Save
IDR save JOB
6
24
007
IDR Save
IDR no carts for TAPE
4
24
008
IDR Delete
IDR delete JOB
4
24
010
IDR Stop
IDR stop PID
2
25
001
Job Started
AutoCopy of TAPE started
2
25
002
Job Successful
AutoCopy of TAPE complete
8
25
003
Job Failed
AutoCopy of TAPE failed
6
25
004
Job Retried
AutoCopy (retry NN) of TAPE
started
2
25
010
EMS
AutoCopy
ems telnet start autocopy of
TAPE for HOST
8
25
011
EMS
AutoCopy
Invalid target path: $targetpath
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/stN
2
27
002
Job Successful
vtexport Import complete for
PATH unloading TAPE
8
27
003
Job Failed
vtexport Import WHY for PATH
28
001
Job Started
vtexport Export to /dev/stN
AutoCopy
Scan/Cleanup
Import
Export
2
132 | Troubleshooting
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
2
28
002
Job successful
vtexport Export complete for
PATH unloading TAPE
8
28
003
Job Failed
vtexport Export WHY for PATH
Transaction Management Facility (TMF) Copy
2
30
001
EMS start
TMF copy
ems telnet start TMFcopy of
TAPE to TAPE for HOST
Subsystem
Message text
Supervisor functions
Subsystem
ID
Event
ID
2
33
000
Unblock
TapeServer
Startup
perform UNBLOCK
4
33
001
Block
TapeServer
Startup
perform BLOCK
4
33
002
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.conf
2
33
008
Encryption
Key
encryption key upload
2
35
001
TapeServer
Started
perform START
4
35
002
TapeServer
stopped
perform STOP
Severity ID
Utilities
Services
Troubleshooting | 133
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message text
2
35
004
EMS Started
perform
EMSCONTROL_START
5
35
005
EMS stopped
perform EMSCONTROL_STOP
2
35
007
XML Started
perform XMLSART
4
35
008
XML stopped
perform XMLSTOP
2
35
010
ICS Started
perform VTSISC_START
4
35
011
ICS stopped
perform VTSISC_STOP
2
35
015
TM Started
perform TMSTART
4
35
016
TM stopped
perform TMSTOP
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message Text
4
40
001
Factory Setup
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
restored
4
40
015
Factory Setup
Access Control RESTORE
GROUPS defaults have been
restored
Event
ID
Subsystem
Message Text
Add a tape
connection
Tape connection XXXXX as
YYYYYY added
Factory setup
Manage connections
Severity
Subsystem
ID
Tape Connections
2
134 | Troubleshooting
51
001
Severity
Subsystem
ID
Event
ID
4
51
2
Subsystem
Message Text
002
Delete a tape
connection
Tape connection XXXXX as
YYYYYY deleted
52
001
Add
Logical tape LXXXX added
2
52
002
Edit
Logical tape LXXXX edited
4
52
003
Delete
Logical tape LXXXX deleted
2
53
001
Add
Virtual tape VXXXX added
2
53
002
Edit
Virtual tape VXXXX edited
4
53
003
Delete
Virtual tape VXXXX deleted
Subsystem
ID
Event
ID
Subsystem
Message Text
2
61
001
Access Control
accessed
Access Control 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
users
Access Control UNDO LAST
USERS
2
61
006
Undo last
rights
Access Control UNDO LAST
RIGHTS
2
61
007
Undo last all
Access Control UNDO LAST
ALL
62
001
Add user
Access Control ADD USER
UUUU
Logical tapes
Virtual tapes
Access control
Severity ID
Defaults
Users
2
Troubleshooting | 135
Severity ID
Subsystem
ID
Event
ID
4
62
2
2
Subsystem
Message Text
002
Delete/Remove
user
Access Control REMOVE USER
UUUU
62
003
Set user
password
Access Control SET
PASSWORD for UUUU
62
005
Change user
group
Access Control CHANGE
PASSWORD for UUUU
2
63
001
Add Group
Access Control ADD GROUP
GGGG
4
63
002
Remove Group
Access Control REMOVE
GROUP GGGG
2
64
001
Rights
changed/
altered
Access Control Save Rights
2
64
002
Save rights as
CUSTOM
Access Control Save Custom
Rights
2
64
004
Change Group
Access Control CHANGE USER
GROUP for UUUU to GGGG
Secure
Password
Management
Error retrieving factoryprovided password with label,
<label>:<explanation>
Group
Rights
Secure Password Management
8
65
001
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
4
71
002
Erase by List
erase-by-list-cron
8
71
003
Erase by List
EraseByList command XXXX
not recognized
6
71
004
Erase by List
EraseByList vclear error on
CART is RC
Severity ID
Erase by List
136 | Troubleshooting
Severity ID
Subsystem
ID
Event
ID
Subsystem
Message Text
6
71
005
Erase by List
EraseByList failed
2
72
000
Delete by List
DeleteByList start
2
72
002
Delete by List
DeleteByList complete
8
72
003
Delete by List
DeleteByList command XXXX
not recognized
6
72
004
Delete by List
DeleteByList vclear error on
CART is RC
6
71
005
Delete by List
DeleteByList failed
81
002
Erase by List
erase-by-list-crumb
8
90
003
XML Mount
xml_socket id=50 MSG
2
90
004
XML Mount
xml_socket id=50 safely
mounted VOL
2
90
005
XML Mount
xml_socket id=50 no space check
mount VOL
Delete by List
Crumb
4
XML Mount
System Status
8
91
003
Space check
chk_space MSG
8
91
004
Space check
system_status WARN
Troubleshooting | 137
138 | Troubleshooting
Credentials
Here is a list of the user accounts for the VTS operating system (Linux).
Username
Default Password
root
bbill
bill
bbill
The first time you log in to the VTS operating system using one of these usernames, you are
prompted to change the password. Acceptable passwords must be at least 8 characters in
length and include uppercase and lowercase alphanumeric characters.
If you wish to reset the these accounts to the factory-default settings, you can run the
following script (as root): /usr/local/tape/bin/ResetDefaultPasswords.bash. After running
this script, you must change the password the next time each username is used to log in.
Here is a list of the default user accounts provided for accessing the VTS web interface:
Username
Default
Password
Group
Privileges
admin
virtual
Administration
Can access all VTS functions
except those in Factory Setup
operator
tapelabs
Operations
Can perform virtual tape
operations, view system status,
start and stop VTS, and access
all vaults.
tapelabs
tapelabs
Supervisor
Can perform all VTS functions
but cannot perform factory
setup activities, administer
access control, upload a
database, edit the VTS
configuration file, restore the
Linux configuration, or view and
manage configurations.
access
verboten
--
Can access all VTS functions.
factory
zfactoryz
--
Can access all VTS functions.
See Configuring Access Control on page 59 to modify the VTS user accounts.
139
140 | Credentials
SCSI-to-Fibre Channel Adapter Upgrade
This appendix provides instructions to replace one or more SCSI cards with the same number
of VTS-supported Fibre Channel (FC) cards on the following VTS models:
•
VT5900-E, on the HP ProLiant DL385 G2
•
VT5900-H, on the HP ProLiant DL385 G5
Refer to Upgrading a SCSI Adapter to a Fibre Channel Adapter on page 152 if you need to
upgrade legacy hardware.
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. 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.
e.
f.
Write down the current configuration. Note the following:
•
Maroon boxes indicate buses cannot be set to Virtual (such as those on the 4Gb
Fibre Channel card)
•
Grey boxes indicate buses on the SCSI card(s)
•
Yellow boxes indicate buses on the 2Gb Fibre Channel card(s)
Select the Physical checkbox for all buses and then click Set Limits.
141
g. Click Supervisor Functions on the navigation pane.
h. Click Block TapeServer Startup on the Supervisory Functions page.
2. Unmount all vaults, stop the PMF on the NonStop server, and shut down VTS.
a. From a terminal window on VTS, log in as root.
b. Use the umount /VAULTxx command (where xx is the vault number) to unmount all
vaults. Repeat this command for each vault on the system until all vaults are
unmounted.
c.
Verify that all vaults are unmounted by typing mount in the VTS terminal window.
There should be no vaults mounted.
d. From the terminal window on VTS, open the /etc/fstab file. Use a text editor to
comment out all vaults in the /etc/fstab file by placing a # symbol before each
LABEL=/VAULT line (for example, #LABEL=/VAULT01). Repeat until all vaults are
commented out.
e.
Save all changes and exit the editor.
f.
From the NonStop server, stop all virtual tape drives using the SCF STOP PMFname
command.
g. Power down all VTS SCSI converters using the switch on the rear of each unit.
h. From a terminal window on VTS, enter shutdown now.
3. Remove the SCSI card(s) and install the Fibre Channel card(s).
a. From the rear of the HP ProLiant DL385 G2 server, mark each SCSI cable with the
port position to which it is attached. This will make it easier to reattach them to the
correct SCSI ports later.
b. Disconnect the ProLiant power cords as a precaution. Disconnect all SCSI cables from
the SCSI adapters for easier access to the adapter cards.
c.
If the HP ProLiant DL385 G2 is mounted in a rack, loosen the front pull tabs and slide
the server out so that you can open the top cover. Do not remove the server from the
rails. If there is a stabilizer foot, extend it so the enclosure does not tip forward.
d. Open the ProLiant DL385 G2 top cover, remove it, and set it aside.
e.
Look inside the ProLiant DL385 G2 server to the back right-hand side where a
pluggable module, called the PCI Riser cage, houses the SCSI and Fibre Channel
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 DL385 G2
chassis. Refer to the diagrams on top of the PCI Riser cage if you have any questions
about its removal. Set the PCI Riser cage on a flat surface that allows ample access to
the side of the module where the adapter cards can be accessed. Note the blue tabs or
pull tabs that allow each adapter to be removed from its slot.
f.
Remove SCSI cards from the server; slots 5 and 4 contain SCSI cards.
The following order of SCSI card removal must be followed:
1. Remove the SCSI card in slot 5 and install the first Fibre Channel card in slot 5.
2. Remove the SCSI card in slot 4 and install the second Fibre Channel card in slot 4,
if necessary.
142 | SCSI-to-Fibre Channel Adapter Upgrade
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. Slide the HP DL385 G2 ProLiant
server back into the rack and secure the two quick-disconnect screws on the front
panel.
i.
From the rear of the HP ProLiant DL385 G2 server, reconnect any remaining 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.
4. Restart VTS.
a. Power on the ProLiant server by pushing the power button on the front panel. The
restart process begins and is complete when the screen displays a login prompt.
b. Power on all of the SCSI converters using the switch on the rear of each unit.
Depending on how many SCSI cards were removed from the ProLiant server, some
converter ports or entire units may no longer be used.
5. Configure the remaining SCSI bus(es) with the original settings.
a. On the VTS web interface, 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.
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.
SCSI-to-Fibre Channel Adapter Upgrade | 143
6. Configure the new Fibre Channel bus(es) as virtual devices (targets). For each bus that
you wish to configure for use as a virtual tape drive, complete these steps:
a. Click Factory Setup on the navigation pane.
b. When prompted, enter the login credentials.
c.
Click Factory Options and enter the login credentials again.
d. Click Manage system limits. The Manage system limits page is displayed. Fibre
Channel buses are highlighted in yellow, and there are two buses listed per Fibre
Channel card installed.
e.
Starting at the highest numbered bus, configure the Fibre Channel buses as virtual
devices by selecting the Virtual (target) checkbox for the bus(es).
Note
You cannot skip a Fibre Channel bus. For example, you cannot set buses 15,
14, and 12 to Virtual, leaving port 13 as Physical (if the checkbox is not
selected, it defaults to Physical).
As a reminder, here are the slot-to-bus relationships on the VT5900-E (HP ProLiant
DL385 G2) and VT5900-H (HP ProLiant DL385 G5):
PCI Slot
Bus Number
Card Type
1A
N/A
(P400 controller card)
1B
N/A
(P400 controller card)
2A
4
4G Fibre
Fibre
2B
5
4G Fibre
Fibre
3A
N/A
(left open for P800
controller card)
3B
N/A
(left open for P800
controller card)
4A
0
2G Fibre
$VTAPE00
4B
1
2G Fibre
$VTAPE01
144 | SCSI-to-Fibre Channel Adapter Upgrade
Virtual Tape Name
f.
PCI Slot
Bus Number
Card Type
Virtual Tape Name
5A
2
2G Fibre
$VTAPE02
5B
3
2G Fibre
$VTAPE03
Click Set Limits.
7. Reboot VTS.
8. Use the VTS web interface to reconfigure a virtual tape connection.
After the Fibre Channel ports are configured as virtual devices, the final step in this
process is to reconfigure the virtual tape connections. Virtual tape connections originally
set up as SCSI need to be edited for use on a Fibre Channel bus.
Refer to the steps documented in Modifying virtual tape connections on page 52. 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.
9. 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 142
(remove the # sign in front of each vault, such as #LABEL=/VAULT01 becomes LABEL=/
VAULT01). Do this for all vaults.
10. Save all changes and exit the editor.
11. Reboot VTS.
SCSI-to-Fibre Channel Adapter Upgrade | 145
146 | SCSI-to-Fibre Channel Adapter Upgrade
Hardware Information for Legacy Installations
This chapter describes the hardware that was shipped for the Virtual TapeServer (VTS)
6.03.39, 6.03.41, and 6.03.42 installations and that is supported in an upgraded environment.
It also provides cabling and Fibre Channel upgrade procedures for the old hardware.
Hardware overview
For VTS installations that are upgrading to 6.04, the following hardware may be installed.
Note
Models shipped with 6.03.42 are still shipped with 6.04. Refer to the “Installation
Summary and Checklist” and “Cabling and Connecting VTS” chapters for an overview
of those models and their cabling instructions.
Servers
One of the following VTS server modules was installed:
•
VTS model VT5900-A was built on the HP ProLiant DL585 G1 server:
•
Models VT5900-B and VT5900-C were built on the HP ProLiant DL380 G4 server:
147
SCSI converters
Each SCSI converter converts high-voltage differential (HVD) Ultra160/SCSI-3 to low-voltage
differential (LVD) Ultra-2 SCSI. It provides up to four converter circuits. Here is a picture of
the back of the SCSI converter:
Internal storage
If the VT5900-C, VT5900-E, or VT5900-G was purchased, additional internal storage may
have been purchased for storing virtual tapes. The following additional internal storage
models were available:
•
VT5904-A, which provided one internal disk drive of 146GB storage space
•
VT5904, which provided six internal disk drives of 146GB each
•
VT5904-B, which provided one internal disk drive of 300GB
External disk storage
If VTS model VT5900-A or VT5900-C is installed, the following hardware may have been
installed for external disk storage.
•
VT5905, which is s built on the StorageWorks MSA 1000 and provides a 2TB storage
array. Up to four VT5905 may have been installed with VTS depending on the VTS model.
•
VT5906, which is built on the StorageWorks Modular 4314 and available if additional
storage was needed after purchasing and installing the VT5905. Up to two of these could
have been installed per VT5905. The VT5906 provided a 2TB storage array:
148 | Hardware Information for Legacy Installations
Fibre Channel upgrade card
To replace a SCSI card with a Fibre Channel (FC) card on an HP ProLiant server, the
VT5900-FCU may have been purchased:
This FC upgrade card is a 2 Gb/sec, dual port, 64-Bit/133 MHz, PCI-X-to-Fibre Channel host
bus adapter (HBA).
Cabling and connecting VTS
Cabling for the various VTS models is described in the following sections. Here is a summary
of each model’s configuration:
VTS Model
Hardware
Height
# of
SCSI Buses
# of FC
Buses
Optical or
Magnetic Drives
VT5900-A
DL585 G1
4U
12
4
CD
VT5900-B
DL380 G4
2U
4
(limited to 2
for virtual
drives)
0
DVD/CD, DAT72
VT5900-C
DL380 G4
2U
4
2
DVD/CD
Note
For the most reliable service, use cables of the highest quality and shortest possible
length based on the location of the equipment in the data center.
Hardware Information for Legacy Installations | 149
Connecting the HP ProLiant DL585 G1 (VT5900-A)
The VT5900-A is a 4U (7 inch) chassis and provides 12 SCSI bus assignments, numbered 112. This model includes two dual-channel Fibre Channel cards, providing up to four
connections to external storage.
The recommended cable connection order for the SCSI converters attached to a VT5900-A is
as follows:
Connections from first SCSI converter:
HVD Bus A
HVD Bus B
HVD Bus C
HVD Bus D
To NonStop server
To NonStop server
To NonStop server
To NonStop server
LVD Bus A
LVD Bus B
LVD Bus C
LVD Bus D
To bus 0 (PCI-X slot
8A) on VTS server
To bus 1 (PCI-X slot
8B) on VTS server
To bus 2 (PCI-X slot
7A) on VTS server
To bus 3 (PCI-X slot
7B) on VTS server
Connections from second 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 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
4B) on VTS server
To bus 10 (PCI-X
slot 3A) on VTS
server
To bus 11 (PCI-X
slot 3B) on VTS
server
150 | Hardware Information for Legacy Installations
Here is an illustration of the bus numbers on the back of the VT5900-A (DL585 G1):
Here is an illustration of the HVD and LVD ports on the back of the SCSI converter:
Connecting the HP ProLiant DL380 G4 (VT5900-B and VT5900-C)
The VT5900-B and VT5900-C were built on a 2U (3.5 inch) chassis and provides four SCSI
buses, numbered 0-3. The VT5900-C has a dual-channel Fibre Channel card but no DAT72
drive and is shipped with two (mirrored) 36GB SCSI drives, for use by the software only.
Optional six SCSI disks (146GB or 300GB) are available to give this unit internal storage. The
six SCSI disks replace the two 36GB drives. The VT5900-B model allows the use of all four
SCSI buses for connecting virtual tape drives. The VT5900-C model allows the use of all four
SCSI buses or the two Fibre Channel buses for connecting virtual tape drives.
The recommended cable connection order for the SCSI converter attached to a VT5900-B and
VT5900-C is as follows:
HVD Bus A
HVD Bus B
HVD Bus C
HVD Bus D
To NonStop server
To NonStop server
LVD Bus A
LVD Bus B
LVD Bus C
LVD Bus D
To bus 0 on VTS
server
To bus 1 on VTS
server
To bus 2 on VTS
server
To bus 3 on VTS
server
Here is an illustration of the bus numbers on the back of the DL380 G4:
Hardware Information for Legacy Installations | 151
Here is an illustration of the HVD and LVD ports on the back of the SCSI converter:
Modifying virtual tape connections
When modifying a virtual tape connection in VTS, you must define a virtual tape’s properties.
Refer to Configuring and Validating Virtual Tape Drives on page 47 for an explanation of the
properties and instructions for modifying them. These following provides information needed
when modifying the bus ID for virtual tape connections on 6.03.39 and 6.03.41 hardware.
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.
For legacy hardware, the bus IDs are as follows:
DL380 G4 (VT5900-B, VT5900-C)
PCI-X Slot
Bus #
3A
0
3B
1
2A
2
2B
3
1A
4
1B
5
Upgrading a SCSI Adapter to a Fibre Channel Adapter
SCSI-to-Fibre Channel Adapter Upgrade on page 141 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.42 models are included in that appendix; refer to it for the steps
required to replace a SCSI card. This section describes the specific step needed for the
following VTS models:
•
VT5900-A, on the HP ProLiant DL585 G1
•
VT5900-B and VT5900-C, on the HP ProLiant DL380 G4
152 | Hardware Information for Legacy Installations
On the HP ProLiant DL585 G1 (VT5900-A)
After completing step 2 on page 142, remove the SCSI card(s) and install the Fibre Channel
card(s), as follows:
1. From the rear of the HP ProLiant DL585 server, mark each SCSI cable with the port
position to which it is attached. This will make it easier to reattach them to the correct
SCSI ports later.
2. Disconnect the ProLiant power cords as a precaution. Disconnect all SCSI cables from the
SCSI adapters for easier access to the adapter cards.
3. If the HP ProLiant DL585 is mounted in a rack, loosen the front pull tabs and slide the
server out so that you can open the top cover. Do not remove the server from the rails. If
there is a stabilizer foot, extend it so the enclosure does not tip forward.
4. Open the ProLiant DL585 top cover, remove it, and set it aside.
5. Look inside the ProLiant DL585 server to the back where the SCSI and Fibre adapters
are located. You will see a shipping bracket secured with a quick-disconnect pull tab that
you need to release to remove the shipping bracket. Once the shipping bracket is removed,
you can access the blue tabs that lock and unlock the SCSI and Fibre Channel cards.
6. Remove SCSI cards from the server as follows:
Note
This order must be followed or the upgrade will not work. Every HP ProLiant
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.
Hardware Information for Legacy Installations | 153
The following order of SCSI card removal must be followed:
a. Remove the SCSI card in slot 3 and install the first Fibre Channel card in slot 3.
b. Remove the SCSI card in slot 4 and install the second Fibre Channel card in slot 4, if
necessary.
c.
Remove the SCSI card in slot 2 and install the third Fibre Channel card in slot 2, if
necessary.
d. Remove the SCSI card in slot 1 and install the fourth Fibre Channel card in slot 1, if
necessary.
e.
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. 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.
9. From the rear of the HP ProLiant DL585 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 several extra, unused SCSI cables. Reconnect the
power cords.
Now, continue with step 4 on page 143 and step 5 on page page 143.
154 | Hardware Information for Legacy Installations
On the HP ProLiant DL380 G4 (VT5900-B and VT5900-C)
After completing step 2 on page 142, remove the SCSI card(s) and install the Fibre Channel
card(s), as follows:
1. From the rear of the HP ProLiant DL380 server, mark each SCSI cable with the port
position to which it is attached. This will make it easier to reattach them to the correct
SCSI ports later.
2. Disconnect the ProLiant power cords as a precaution. Disconnect all SCSI cables from the
SCSI adapters for easier access to the adapter cards.
3. If the HP ProLiant DL380 is mounted in a rack, loosen the front pull tabs and slide the
server out so that you can open the top cover. Do not remove the server from the rails. If
there is a stabilizer foot, extend it so the enclosure does not tip forward.
4. Open the ProLiant DL380 top cover, remove it, and set it aside.
5. Look inside the ProLiant DL380 server to the back right-hand side where a pluggable
module, called the PCI Riser cage, houses the SCSI and Fibre adapters. You will see a two
round 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. Set the PCI Riser cage on a
flat surface that allows ample access to the side of the module where the adapter cards
can be accessed. Note the blue tabs or pull tabs that allow each adapter to be removed
from its slot.
6. Remove SCSI cards from the server as follows:
Note
This order must be followed or the upgrade will not work. Every HP ProLiant
DL380 server has SCSI and Fibre Channel cards in the same physical slots.
A Fibre Channel card is always in slot 1, the bottom slot; there is no reason to remove this
card. Slots 2 and 3 contain SCSI cards. A picture showing these slots follows:
Hardware Information for Legacy Installations | 155
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. Then, re-install the
PCI Riser cage in the DL380 chassis. Once aligned, firmly press the module into place. Retighten the two blue pull tabs on the PCI Riser cage.
8. Place the top cover back in place and secure it. Slide the HP DL380 ProLiant server back
into the rack and secure the two quick-disconnect screws on the front panel.
9. From the rear of the HP ProLiant DL380 server, reconnect any remaining SCSI cables to
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 4 on page 143 and step 5 on page page 143.
For step 6e on page 144, consider the following slot-to-bus relationships on the HP ProLiant
DL380 G4 (VT5900-B and VT5900-C):
PCI-X Slot
Bus Number
Virtual Tape Name
3A
0
$VTAPE00
3B
1
$VTAPE01
2A
2
$VTAPE02
2B
3
$VTAPE03
1A
4
Fibre *
1B
5
Fibre *
156 | Hardware Information for Legacy Installations
Specifications
The following outlines the physical and environmental specifications of the ProLiant server
on which Virtual TapeServer is shipped:
Component
Specifications
Electrical
• Rated Line Voltage: 100 VAC, 120 VAC, 200-240 VAC
• Rated Input Current: 10A (at 100 VAC), 9A (at 120 VAC),
6.1A (at 200 VAC)
• Rated Input Frequency: 50 to 60 Hz
• Rated Input Power: 980W (at 100 VAC), 1035W (at 120 VAC),
1170W (at 240 VAC)
• Rated Steady-State Power (Output): 800W (at 100 VAC),
850W (at 120 VAC), 1000W (at 200-240 VAC)
• Maximum Peak Power: 800W (at 100 VAC), 850W (at 120 VAC),
1000W (at 200-240 VAC)
Physical Dimensions
•
•
•
•
•
Operating
Environment
• Operating Temperature: 50° to 95° F (10° to 35° C)
• Shipping Temperature: -22° to 140° F (-30° to 60° C)
• Operating Relative Humidity: 10% to 90%, 82.4° F (28° C)
maximum wet bulb temperature, non-condensing
• Shipping Relative Humidity: 5% to 95%, 38.7°C (101.7°F)
maximum wet bulb temperature, non-condensing
Form factor: standard 2U RETMA rack mount chassis
Height: 3.38 in. (8.59 cm)
Width: 17.54 in. (44.54 cm)
Depth: 26.01 in. (66.07 cm)
Weight: 60 lb (27.22 kg) maximum
157
158 | Specifications
Index
A
access control
overview 59
saving and restoring custom defaults 76
Access Control page, overview 11
access rights, See rights
adding physical tape drive 107
assigning
groups to a user 69
rights to a group 72
attaching physical tape drives to VTS 107
audience vii
AutoCopy
configuring
network settings 97
TCP/IP security 102
configuring SSH 102
enabling 95
licensing 45
automating
mounts 79
B
backup management applications, See BMAs
BMAs
integration 105
supported by VTS 105
BTLI 48
building blocks of VTS 2
bus-to-slot table 49
C
cables 16
cabling
connection order
VT5900-A 150
VT5900-B and VT5900-C 151
VT5900-E 22
VT5900-G 23
external tape resources 26
from Integrity NonStop servers 19
from NonStop S-series servers 20
NonStop server to SCSI converter 20
NonStop S-series server to the SCSI
converter 20
SCSI converter to VTS 21
to external disk resources 24
Cartridge Maintenance page 7
checking SCSI termination 21
checklist, installation 18
CLIM
configuring VTDs 55
closed (access) system 60
configuring
access control 59
automated migration 109
EMS 79
EMS user accounts 89
enterprise integration 109
groups 72
licensing 45
network settings
for Instant DR and AutoCopy 97
for the VTS server 31
passwords
any user’s 66
yours 68
TCP/IP security for Instant DR and
AutoCopy 102
users 63
virtual tape connections
for legacy hardware 152
overview 52
connecting
power 28
to a LAN 27
to a SAN 28
VT5900-A 150
VT5900-B 151
VT5900-C 151
VT5900-E 22
VT5900-G 23
VT5900-H 22
connectiong
VT5900-J 23
contacting Support, information to gather 115
creating
users 63
virtual tape drives 47
custom defaults, saving and restoring 76
Customer Support viii
Index | 159
D
database, troubleshooting 118
debug information 115
default
groups 60
users 60
deleting
users 70
deployment, overview 17
diagnostic
commands 118
tools 115
documentation viii
E
EMS
configuring 79
messages 90
parameters in configuration file 79, 85
troubleshooting 121
user accounts 89
ems_enable parameter 79
ems_hostaddr_NSserver parameter 85
ems_hostdevs_NSserver parameter 85
ems_hostnames parameter 79
ems_hostport_NSserver parameter 85
ems_hsm_backup_notification parameter 112
ems_InterSystemCommunication_hosts
parameter 82
ems_keep_alive parameter 81
ems_login_command_NSserver parameter 87
ems_login_passanswer_type parameter 84
ems_login_passprompt_type parameter 84
ems_login_successful_type parameter 85
ems_login_useranswer_type parameter 84
ems_login_userprompt_type parameter 83
ems_mount_delay parameter 82
ems_notification_enable parameter 80
ems_notification_level parameter 80
ems_notify_enable parameter 80
ems_notify_hostnames parameter 80
ems_notify_logout_timeout parameter 81
ems_notify_logout_timeout_NSserver parameter
86
ems_notify_wait_timeout parameter 81
ems_notify_wait_timeout_NSserver parameter
86
ems_resetdevs_NSserver parameter 87
ems_response_time parameter 82
ems_response_time_hostname parameter 86
ems_response_timeout_NSserver parameter 86
ems_service_answer_type parameter 83
160 | Index
ems_service_prompt_type parameter 83
ems_service_select_type parameter 83
ems_vaults_NSserver parameter 87
ems_virtdevs_NSserver parameter 86
enabling
closed system 60
Instant DR and AutoCopy 95
Event Management System, See EMS
event.log file 123
external
disk resources, cabling 24
storage
for legacy hardware 148
overview 14
tape resources, cabling 26
external storage, troubleshooting 120
F
Factory Setup page, overview 12
features 3
Fibre Channel upgrade
card 16
for legacy hardware 152
procedure 141
VT5900-A 153
VT5900-B and VT5900-C 155
VT5900-E 142
file system
troubleshooting 118
G
getVTS_dbginfo 115
GFS, installing 33
groups
assigning rights 72
default rights 60
H
hard drives, troubleshooting 117
hardware overview
legacy models 147
new installations 13
host devices 6
host server, troubleshooting 117
HP
health monitoring utilities 116
Integrated Lights-Out 116
Systems Insight Manager (SIM) 116
hsm_backup_options parameter 110
hsm_backup_options_poolname parameter 110
hsm_backup_pools parameter 110
hsm_enable parameter 110
hsm_erase_after_backup parameter 111
hsm_joblog_maxnum parameter 111
hsm_optfile parameter 111
hsm_optfile_pool parameter 111
hsm_policy parameter 111
hsm_pool parameter 110
hsm_product parameter 110
hsm_put_batch_size 111
hsm_restore_device parameter 110
hsm_restore_period parameter 112
hsm_schedule parameter 111
hsm_server parameter 110
hsm_summary_limit parameter 112
I
iLO 116
initiator, description 50
installation
checklist 18
overview 17
installing GFS 33
Instant DR
configuring
network settings 97
TCP/IP security 102
configuring SSH 102
enabling 95
licensing 45
internal storage
for legacy hardware 148
overview 14
Intraserver Communication Service (ISC) 4
introduction 1
L
licensing 45
AutoCopy 45
Instant DR 45
migration 113
SecureVTS 45
log files
event.log 123
troubleshooting 119
LUN, description 50
M
Manage Connections page 9
Manage system limits page 108
migration
configuration parameters 110
licensing 113
overview 105
modifying
any user’s password 66
virtual tape connections 52
mounting
automating 79
failures 121
MSA 1000 15, 148
MSA 1500 14
N
network settings for the VTS server 31
NonStop server
troubleshooting 116
validating backups to VTS 56
O
open (access) system 60
Operation page 6
overview
installation 17
internal storage 14
legacy hardware 147
migration 105
VTS 1
VTS models 13
web interface 4
P
passwords, modifying
any user’s 66
yours 68
physical tape drive, adding 107
pools
definition 2
powering up and down 28
powering VTS up and down 28
product overview 1
R
rebooting 28
related documentation viii
rights
assigning to groups 72
descriptions 73
Index | 161
S
SCSI
controllers, troubleshooting 117
converter
cabling
to VTS 21
cabling from NonStop server 20
overview 15
converter, troubleshooting 120
termination 21
upgrading to Fibre Channel for legacy
hardware 152
SCSI-to-Fibre Channel upgrade
current models 141
SecureVTS
licensing 45
page 11
SSH, configuring 102
Supervisory Functions page 10
Support viii
system event log 123
System Overview page 8
System Status page 4
T
target, description 49
troubleshooting
database 118
diagnostic commands 118
diagnostic tools 115
EMS 121
external storage 120
file system 118
hard drives 117
host server 117
log files 119
NonStop server 116
overview 115
SCSI controllers 117
SCSI converter 120
virtual tape operations 121
VTS server module 117
web interface 118
typographical conventions vii
U
users
assigning groups 69
creating 63
default accounts 60
deleting 70
162 | Index
users (cont.)
EMS 89
of VTS vii
V
validating NonStop-to-VTS server backups 56
vaults
definition 2
virtual cartridges, See virtual tapes
Virtual Media
Cartridge Maintenance page 7
Operation page 6
pages, accessing 5
virtual tape connections, configuring
for legacy hardware 152
for new installations 52
virtual tape drives
configuring the CLIM 55
creating 47
definition 2
virtual tapes
definition 2
operations, troubleshooting 121
VT5900-A, Fibre Channel upgrade 153
VT5900-B
Fibre Channel upgrade 155
overview 147
VT5900-C
Fibre Channel upgrade 155
overview 147
VT5900-E
Fibre Channel upgrade 142
overview 14
VT5900-FCU 16
VT5900-G
overview 14
VT5900-H
overview 14
VT5900-J
overview 14
VT5904-E 14
VT5905 15, 148
VT5906 15, 148
VT5907 95
VT5907-A 95
VT5915 14
VT5916 15
VT5918 14
VTS
overview 1
overview of models 13
server module, troubleshooting 117
W
web interface
overview 4
troubleshooting 118
Index | 163
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement