Archive Backup System
for OpenVMS

Installation Guide

Order Number: AA-QHD2T-TE

 

Software Version

Archive Backup System for
OpenVMS Version V4.2

Required Operating System

OpenVMS VAX Version 6.2, 7.1, 7.2 and 7.3

OpenVMS Alpha Version 6.2, 7.1-2,
7.2-1, 7.2-2, 7.3, 7.3-1 or 7.3-2

Required Software

Media, Device and Management
Services for OpenVMS
Version V4.2

 

DECnet (Phase IV) or DECnet-Plus(Phase V)

 

TCP/IP Services for OpenVMS

 

 

 

 

 

 

 

 

 

 

Hewlett-Packard Company

Palo Alto, California

January 2004

 

© 2004 Hewlett-Packard Development Company, L.P.

 

Confidential computer software. Valid license from hp and/or its subsidiaries required for possession, use, or
copying.

 

Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

 

Neither hp nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for hp products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.

 

Printed in the U.S.A.

 

Preface ix
1 Welcome To ABS

1.1 Installing ABS/MDMS 1-1

1.2 Updating ABS/MDMS 1-1

2 Preinstallation

2.1 Decide Where to Install ABS/MDMS software 2-1

2.1.1 ABS/MDMS Server Software 2-1

2.1.2 ABS/MDMS Client Software 2-1

2.1.2.1 OpenVMS Clients 2-1

2.1.2.2 Windows Clients 2-1

2.1.2.3 Tru64 UNIX Clients 2-2

2.2 Verify Requirements 2-2

2.2.1 Required Privileges 2-2

2.2.2 Required OpenVMS Operating System Subclasses 2-2

2.2.3 Hardware, Software, and System Requirements 2-3

2.2.3.1 Required Hardware 2-3

2.2.3.2 Required Software 2-4

2.2.3.3 Optional Software 2-4

2.2.3.4 Required System Parameters 2-5

2.2.3.5 Required Process Account Quotas 2-5

2.2.3.6 Required Processes 2-6

2.2.3.7 Verify the Node is in the MDMS Database 2-8

2.3 Configure Hardware 2-8

2.4 Perform a System Backup 2-8

2.5 Registering ABS Licenses 2-9

3 Installing ABS Software

3.1 Installing Archive Backup System for OpenVMS Software 3-1

3.1.1 Installing ABS/MDMS Server Software 3-2

3.1.2 Installing ABS OpenVMS Client Software 3-4

3.1.3 Installing and Configuring ABS Windows Clients 3-4

3.1.4 Configuring ABS Tru64 UNIX Clients 3-6

3.1.4.1 Modifying the Appropriate Tru64 UNIX Files 3-7

3.1.4.2 Transferring the Tru64 UNIX Backup Agent Sources 3-8

3.1.4.3 Building the Tru64 UNIX Executables 3-9

3.1.5 Authorizing Windows and Tru64 UNIX Clients 3-12

4 Performing Postinstallation Tasks

4.1 Installing ABS for the First Time 4-2

4.2 Create a Node Object 4-2

4.3 Verifying ABS Installation 4-2

4.4 Providing Automatic Start Up and Shut Down 4-3

4.5 ABS and MDMS Startup Queues 4-3

4.6 Modifying ABS and MDMS Command Procedures 4-3

4.7 Meeting OpenVMS Cluster Requirements 4-4

4.8 Configure MDMS 4-4

4.9 Configure Remote Tape Drives 4-5

4.10 Granting the Appropriate ABS/MDMS Access Right Identifiers 4-5

4.10.1 Revoking An Access Rights Identifier 4-7

4.11 Verifying Windows and Tru64 UNIX Client Quotas 4-7

4.12 Adding Windows Parameter 4-7

4.13 Allowing ABS Access to All Files on the Windows Systems 4-8

4.14 ABS/MDMS Graphical User Interface (GUI) Installation 4-8

4.14.1 Installing the GUI on OpenVMS Alpha 4-9

4.14.2 Installing the GUI on Intel Windows NT/95/98 4-10

4.15 Running the GUI 4-10

4.15.1 Running the GUI on OpenVMS Alpha 4-10

4.15.1.1 Running the GUI on Windows NT/95/98 4-11

4.16 Configuration of ABS/MDMS for System Backup to Tape for Oracle Databases 4-11

A Examples of Authorizing Windows and Tru64 UNIX Clients

A.1 Adding Client Licenses A-1

A.2 Modifying Client Licenses A-1

A.3 Showing Client Licenses A-2

A.4 Removing Client Licenses A-3

B How to Delete ABS/MDMS From Your System

Table 2-1 Required Software 2-4

Table 2-2 Optional Software 2-4

Table 2-3 System Parameters - Minimum Values 2-5

Table 2-4 Required Installing Account Process Quotas 2-6

Table 2-5 How to Start DECnet and the OpenVMS Queue Manager 2-7

Table 2-6 How to Register Your ABS Licenses Using VMSLICENSE.COM 2-11

Table 3-1 Stages of Installing ABS Software 3-1

Table 3-2 How to Install ABS Software 3-3

Table 3-3 Installing ABS OpenVMS Client Software 3-4

Table 3-4 Stages of Installing an ABS Windows Client 3-5

Table 3-5 Installing and Configuring an ABS Windows Client 3-5

Table 3-6 Stages of Installing and Configuring an ABS Tru64 UNIX Client 3-6

Table 3-7 Modifying the Appropriate Tru64 UNIX Files 3-7

Table 3-8 Authorizing NT and Tru64 UNIX Client Nodes 3-13

Table 4-1 Updating the DCL Tables 4-4

Preface

Intended Audience

This document is intended for storage administrators who are experienced OpenVMS system managers. This document should be used in conjunction with the Introduction to OpenVMS System Management manual.

Conventions

The following conventions are used in this document:

Convention

Description

{}

In format command descriptions, braces indicate required elements.

[ ]

In format command descriptions, square brackets indicate optional elements of the command syntax. You can omit these elements if you wish to use the default responses.

boldface type

Boldface type in text indicates the first instance of a term defined in the Glossary or defined in text.

italic type

Italic type emphasizes important information, indicates variables, indicates complete titles of manuals, and indicates parameters for system information.

Starting test ...

This type font denotes system response, user input, and examples.

Ctrl/x

Hold down the key labels Ctrl (Control) and the specified key simultaneously (such as Ctrl/Z).

PF1 x

The key sequence PF1 x instructs you to press and release the PF1 key, and then press and release another key (indicated here by x).

n

A lowercase italic n denotes the generic use of a number. For example, 19nn indicates a four digit number in which the last two digits are unknown.

x

A lowercase x denotes the generic use of a letter. For example, xxx indicates any combination of three alphabetic characters.

Related Products

The following related products may be mentioned in this document:

Product

Description

HSM

HSM refers to Hierarchical Storage Management for OpenVMS software.

MDMS

MDMS refers to Media and Device Management Services for OpenVMS software.

OpenVMS

OpenVMS refers to OpenVMS operating system.

SLS

SLS refers to Storage Library System for OpenVMS software.

Associate Documents

The following documents are part of Archive Backup System for OpenVMS documentation set:

1

Welcome To ABS

1.1 Installing ABS/MDMS

If you are installing Archive Backup System (ABS)/Media Device and Management System (MDMS) for the first time, read through this installation guide before installing the products. Also refer to the Archive Backup System Guide to Operations for information on configuring ABS/MDMS.

1.2 Updating ABS/MDMS

If you are updating ABS/MDMS, you should review the release notes provided in the installation kit. You may extract the release notes by entering the command:

@SYS$UPDATE:VMSINSTAL kit_name kit_location OPTIONS N

The upgrade from ABS/MDMS V3.x to V4.0 requires a conversion of the ABS policy database. See Appendix D for instructions on the conversion procedure.

If you want to upgrade from ABS/MDMS V3.x, please upgrade to ABS/MDMS V4.1 as a first step. Then you should upgrade to ABS/MDMS V4.2.

 

2

Preinstallation

To ready your OpenVMS system for either the ABS/MDMS server or ABS/MDMS client software installation procedure, you must perform certain tasks and requirements:

  • Decide where to install the ABS/MDMS software
  • Verify requirements
  • Configure hardware
  • Perform a system backup prior to the installation
  • Install licenses

2.1 Decide Where to Install ABS/MDMS software

  1. 2.1.1 ABS/MDMS Server Software

Install ABS/MDMS server software on a disk with adequate space. This disk may be the system disk or another disk dedicated to ABS/MDMS. Disk space required for the installation are listed in See Required Hardware. You should also take into account the space required for log files, catalogs and databases. Additional catalog disks may be added at a later time.

The ABS/MDMS server software should reside on a system which will be managing the policy and media databases for itself and any client nodes connected to it. The MDMS server provides access to the policy and media databases.

You must install ABS/MDMS server software on at least one OpenVMS node or OpenVMS cluster system.

There is one kit for both ABS/MDMS servers and clients. The installation will provide the appropriate configuration based on what server names are entered during the installation. The configuration may be modified at a later time by updating the node and server information in the MDMS database.

  1. 2.1.2 ABS/MDMS Client Software
  2. 2.1.2.1 OpenVMS Clients

ABS/MDMS client software should be installed on any OpenVMS node that can communicate with the ABS/MDMS server and for which you want to create ABS save/restore requests. This communication may be done using DECnet or TCP/IP.

  1. 2.1.2.2 Windows Clients

For Windows clients, you must install the ABS Windows software provided in the ABS/MDMS installation kit. You must also authorize access for Windows clients on the ABS server node. These tasks are described in Chapters 3 and 4.

  1. 2.1.2.3 Tru64 UNIX Clients

Tru64 UNIX clients do not require a separate client installation. However, you must transfer the GNU tar files provided by the ABS/MDMS installation kit to the client system, and then you must build the executable images on the Tru64 system. You must also authorize the clients on the ABS server node. These tasks are described in Chapters 3 and 4.

Both Windows and Tru64 UNIX clients have their backup operations occur on the ABS server node. The ABS server communicates with the Windows and Tru64 UNIX clients for data transfer and control.

Given that you have the appropriate amount of licenses and adequate resources available, any number of ABS client nodes may be connected to a single ABS server node.

2.2 Verify Requirements

  1. 2.2.1 Required Privileges

To install ABS, log on to the SYSTEM account or to an account that has SETPRV or, at a minimum, has the following privileges enabled:

Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation procedure.

  1. 2.2.2 Required OpenVMS Operating System Subclasses

OpenVMS operating system comes with a variety of support options, or subclasses. Subclasses include such features as networking and RMS journaling. To use ABS, your system should have the following subclasses resident:

How to verify:
For information about verifying these components, refer to either OpenVMS VAX Installation Procedures or OpenVMS Alpha Installation Procedures.

  1. 2.2.3 Hardware, Software, and System Requirements

To make sure that your system is ready for the installation, verify that your system meets the following requirements:

To install software, you must meet the following minimum hardware requirements:

If you are providing remote drive support, you must answer yes to the remote drive question during MDMS installation procedure. This requires additional free disk space.

Enter the following command to show the amount of used disk space on your disk:

$ SHOW DEVICE disk-name

Disk space required during an full installation on an Alpha system is 214,500 blocks with 167,400 required after the installation. Disk space required on a VAX is 204,000 blocks with 120,000 required after the installation.

  1. 2.2.3.2 Required Software

Table 2-1 lists the software you must have installed on your system before you can install ABS.

Required Software

Software

Purpose

System

DECnet Phase IV or
DECnet Plus for OpenVMS or TCP/IP Services for OpenVMS

Provides network support

 

Note:

This software must be up and running before you start the installation procedure if you will be using a network with ABS/MDMS

ABS OpenVMS Server

ABS OpenVMS Client

OpenVMS Operating Systema

Provides OpenVMS and DCL capabilities.

ABS OpenVMS Server

ABS OpenVMS Client

a. See ABS Software Product Description (SPD) for supported versions.

 

  1. 2.2.3.3 Optional Software

Table 2-2 describes the optional software you can use with ABS software

Optional Software

Software

Purpose

System

ABS NT Client

Software

Provides the ability to save data from Windows NT systems to ABS OpenVMS server system using ABS software (provided with ABS, not purchased separately).

Windows Client

C Compiler

Provides the ability to build the executable files on Tru64 UNIX clients

Tru64 UNIX Client

DCSC1(Digital Cartridge Server Component)

If you have a StorageTek Automated Cartridge Server (ACS), you must install the DCSC software.

The system where the StorageTek silo resides.

TCP/IP Services for OpenVMSa

Provides network support for Windows and Tru64 UNIX clients.

ABS/MDMS OpenVMS Server,ABS/MDMS OpenVMS Clients, system where GUI will be run.

Media Robot Utility (MRU)

Provides library and loader testing, diagnostics, and control.

The OpenVMS system where the robotic device is physically connected

Java Run-Time Environment (JRE) V1.2 or 1.3.1

Provides run-time environment for

MDMSView GUI.

The OpenVMS or Microsoft Windows system where the GUI will be run.

 

  1. 2.2.3.4 Required System Parameters

To install ABS, the system parameters must be set to the minimum value or higher. Table 2-3 lists the minimum system parameter values required for the installation procedure to run successfully. Depending on the kinds of programs and applications running at your site, you may need higher values.

System Parameters - Minimum Values

System Parameter

Minimum Value

Dynamic

PQL_DENQLM

300

Y

GBLPAGES2

2000

N

GBLSECTIONSa

4

N

LOCKIDTBL

45000

N

PQL_MENQLM

300

Y

PQL_MPGFLQUOTA

10000

Y

PROCSECTCNT

100

N

PQL_MTQELM

200

Y

To see the current system parameter values on your system, enter the following command:

$ MCR SYSGEN
SYSGEN> SHOW/GEN

Result:
Shows the current values of all the system parameters. If you need to modify one or more of the system parameters, see the following example:

$ MCR SYSGEN
SYSGEN> SET GLBPAGES 2000
SYSGEN> WRITE CURRENT
SYSGEN> EXIT

The changed parameters should be added to SYS$SYSTEM:MODPARAMS.DAT for future changes made with AUTOGEN. You must then reboot the system so the non dynamic parameter values are recognized.

More information:
Refer to OpenVMS System Manager's Manual: Managing System Parameters for detailed information about required system parameters.

  1. 2.2.3.5 Required Process Account Quotas

The account you use to install ABS (typically the SYSTEM account) must have sufficient quotas to enable you to perform the installation. If your SYSTEM account quotas are the same as or higher than the default values provided with the OpenVMS operating system, then these values should be sufficient to install the software.

Table 2-4 summarizes the process quotas and the quotas that VMSINSTAL requires to perform the installation.

Required Installing Account Process Quotas

Account Quota

Minimum Value

ASTLM

200

BIOLM

10000

BYTLM

18000

DIOLM

200

ENQLM

2048

FILLM

300

PGFLQUO

10000

TQELM

200

To see your current process quotas, see the following example:

$ MCR AUTHORIZE
UAF> SHOW SMITH

Result:
This command shows all your process quotas. If you need to increase your process account quotas, see the following example:

$ MCR SYS$SYTEM:AUTHORIZE
UAF> MODIFY SMITH/ENQLM=2048
UAF> EXIT

If you are supporting NT or UNIX clients, to ensure successful save and restore operations, set the quotas to the following values from ABS OpenVMS server node:

UCX> SET PROTOCOL TCP/QUOTA=(SEND:50000,RECEIVE:50000)

If you have to reboot the machine, make sure that you reset these values after rebooting.

More information:
For detailed instructions about modifying account quotas, see the description of Authorize Utility in OpenVMS System Management Subkit.

  1. 2.2.3.6 Required Processes

Before beginning the installation procedure, check to see that DECnet Phase IV, DECnet Plus or TCP/IP and the OpenVMS Queue Manager are running. Network software is not required if you are on a standalone system and you will not be using the GUI. To see if these processes are active on your system, enter the following command:

$ SHOW SYSTEM

The following information is displayed for DECnet Phase IV:

OpenVMS V7.1 on node NODE1 8-AUG-1997 13:39:28.23Uptime 0 23:36:26
Pid Process Name State Pri I/O CPU Page flts Page
.
.
.
20A0022C QUEUE_MANAGER HIB 8 72 0 00:00:00.83 751 1210
.
.
.
20A00212 NETACP HIB 10 285 0 00:00:02.84 338 666

The following information is displayed for DECnet Plus:

37C00215 NET$ACP HIB 4 629 0 00:27:23.22 1894 2465
.
.
.
37C0024A QUEUE_MANAGER HIB 8 3333 0 00:07:45.24 1246 1766

The following information is displayed for UCX (earlier version of TCP/IP)

20A00444 UCX$INET_ACP HIB...

The following information is displayed for TCP/IP:

20A00555 TP_SERVER HIB...

If these processes are not active, follow the steps in Table 2-5.

How to Start DECnet and the OpenVMS Queue Manager

Step

Action
  1. 1.

Start DECnet software.

 

For DECnet Phase IV, enter the following command at DCL prompt:

$ @SYS$MANAGER:STARTNET.COM

For DECnet Plus, enter the following command at DCL prompt:

$ @SYS$STARTUP:NET$STARTUP.COM
  1. 2.

Start OpenVMS Queue Manager. Enter the following command at DCL prompt:

$ START/QUEUE/MANAGER
  1. 3.

Start the TCP/IP software.

 

For TCP/IP Version 4-n, enter the following command at the DCL prompt:

$ @SYS$SYSTEM:UCX$STARTUP.COM

For TCP/IP Version 5.n, enter the following command at the DCL prompt:

$ @SYS$MANAGER:TCPIP$STARTUP.COM

 

  1. 2.2.3.7 Verify the Node is in the MDMS Database

If this installation is not the initial installation of MDMS, you need to verify that the node you are installing MDMS on is in the MDMS database. Enter the following command on a node that has MDMS already installed on it and verify that the node you are installing MDMS on is in the database:

$ MDMS SHOW NODE node_name_you_are_installing_on
%MDMS-E-NOSUCHOBJECT, specified object does not exist

If the node is not in the database, you receive the %MDMS-E-NOSUCHOBJECT error message and you should create the node using the following command:

$ MDMS CREATE NODE node_name_you_are_installing_on

See the Archive Backup System for OpenVMS MDMS Reference Guide for the qualifiers to use.

If the node you are adding is an MDMS server node, the installation procedure will create the node using the /DATABASE qualifier. In addition, you need to edit all SYS$STARTUP:MDMS$SYSTARTUP.COM files in your domain and add this node to the definition of MDMS$DATABASE_SERVERS.

2.3 Configure Hardware

For your storage application to work, the hardware it depends on must be installed, connected, and configured to function with the operating system. To configure your hardware, see the hardware manuals provided with the hardware device. Also see the Archive Backup System Guide to Operations for troubleshooting suggestions.

If you are installing tape jukeboxes for use with ABS/MDMS, you should verify that the hardware is working correctly before installing ABS/MDMS. You may use the Media Robot Utility (MRU) to verify the hardware. If you do not have this software installed, it may be downloaded from

http://www.support.compaq.com/sms/mru/

Consider RDF Configuration

MDMS provides RDF software to facilitate operations that require access to remote, network connected tape drives. This allows you to copy data from a local site to a remote site, or copy data from a remote site to a local site. RDF requires that DECnet is installed and running.

RDF is not available if you are installing MDMS with the ABS-OMT license.

During the installation you will be asked questions on whether you want to install on this node, the software that will allow it to act as a server and/or client for the RDF software. You need to decide if you want the server and/or client installed on the node.

2.4 Perform a System Backup

hp recommends that you perform a backup operation on the system disk before installing any software. For details about performing a backup operation on a system disk, see the OpenVMS System Manager's Manual.

2.5 Registering ABS Licenses

To use ABS software, you must register and load the licenses before you begin the installation procedure. This information is supplied in the License PAK document which is packaged along with Archive Backup System for OpenVMS Cover Letter.

To register a license under OpenVMS, use the following procedure:

  1. 1. Log in to the system where you will be installing the software. Log in under SYSTEM account, or enable your account with the privileges described in See Required Privileges. Select one of the following methods to register the licenses:
  2. At DCL prompt, enter the LICENSE REGISTER command with appropriate qualifiers that correspond to License PAK information. See See If you plan to use ABS on more than one node in an OpenVMS Cluster, you must load the licenses on other nodes after you install ABS. See Table 2-6, Step 10 for instructions.How to Register Your ABS Licenses Using the LICENSE REGISTER Command.
  3. Invoke SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. See See How to Register Your ABS Licenses Using VMSLICENSE.COM.

If you plan to use ABS on more than one node in an OpenVMS Cluster, you must load the licenses on other nodes after you install ABS. See Table 2-6, Step 10 for instructions.How to Register Your ABS Licenses Using the LICENSE REGISTER Command

Step

Action
  1. Step 1.

Enter the LICENSE REGISTER command with the product name followed by a dash (-):

 

$ LICENSE REGISTER ABS-SERVER-VAX -
! Register this license on the ABS VAX server node

$ LICENSE REGISTER ABS-SERVER-ALPHA -
! Register this license on the ABS Alpha server node

$ LICENSE REGISTER ABS-CLIENT-VAX -
! Register this license on all ABS VAX client nodes

$ LICENSE REGISTER ABS-CLIENT-ALPHA -
! Register this license on all ABS Alpha client nodes

$ LICENSE REGISTER ABS-NT-CLIENT-USER -
! Register this license on the ABS server node where you plan to support NT clients.

$ LICENSE REGISTER PAB-UNIX-CLIENT-USER -
! Register this license on the ABS server node where you plan to support UNIX clients.

$ LICENSE REGISTER ABS-OMT -
! Register this license on all ABS server nodes where you have to install the ABS
software

$ LICENSE REGISTER ABS-OMT-UPG -
! Register this license on all ABS server nodes where you want to upgrade the
ABS-OMT license to the full ABS product

Important:
Enter a dash (-) at the end of each command from Steps 1 through 8.
  1. Step 2.

Enter the /ISSUER qualifier information, assigning the value DEC between quotation marks.

_$ /ISSUER="DEC" -

  1. Step 3.

Enter the /AUTHORIZATION qualifier information, assigning it the value from the AUTHORIZATION NUMBER3 entry of the PAK:

_$ /AUTHORIZATION=xxxxxx -

Step

Action
  1. Step 4.

Enter the /PRODUCER qualifier information, assigning the value DEC in quotes:

_$ /PRODUCER="DEC" -
  1. Step 5.

Enter the /UNITS qualifier information, assigning it the value from the UNITSa entry of the PAK

_$ /UNITS=nn -
  1. Step 6.

Enter the /DATE qualifier information, assigning the product's release date value from the PRODUCT RELEASE DATEa entry of the PAK:

_$ /DATE=dd-mmm-yyyy -
  1. Step 7.

Enter the /AVAILABILITY qualifier information, assigning the value from the AVAILABILITY TABLE CODEa entry of the PAK:

_$ /AVAILABILITY=x -
  1. Step 8.

Enter the /OPTIONS qualifier information, assigning the value from the KEY OPTIONSa entry of the PAK:

_$ /OPTIONS=xxxxxx -
  1. Step 9.

Enter the /CHECKSUM qualifier information, assigning the value from the CHa entry of the PAK:

 

_$ /CHECKSUM=1-xxxx-xxxx-xxxx-xxxx
Important:
Do NOT end the entry with a dash.
  1. Step 10.

Invoke the LICENSE LOAD command with the product name:

$ LICENSE LOAD product_name

See How to Register Your ABS Licenses Using VMSLICENSE.COM describes how to register your license using the command procedure.

How to Register Your ABS Licenses Using VMSLICENSE.COM

Step

Action
  1. Step 1.

From the system prompt, enter the following command:

$ @SYS$UPDATE:VMSLICENSE.COM
  1. Step 2.

Select Option 1. "REGISTER a Product Authorization Key"
  1. Step 3.

Answer the questions according to the information supplied in the LICENSE PAK document (provided with the software kit).

The following is only an example. Supply the information provided in the PAK to the prompts:

Type ? at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to return to the main menu.

Issuer[DEC]
Authorization Number[]:
Authorization Number[]:ALS-NQ-1996JUN10-181
Product Name[]:ABS-SERVER
Producer[DEC]:
Number of Units[]:1050
Version[]:
Product Release Date[]:
Key Termination Date[]:
Availability Table Code[]:H
Activity Table Code[]:
Key Options[]:MOD_UNITS,ALPHA
Product Token[]:
Hardware-Id[]:
Checksum[]:2-PIBA-KIPP=BIGE-DDHC

  1. Step 4.

Verify the information that you entered is correct. Enter Yes.
  1. Step 5.

To exit the command procedure, select Option 99.

 

3

Installing ABS Software

This chapter contains instructions for installing Archive Backup System for OpenVMS software.

Before proceeding with the installation procedure, make sure you have completed all of the following preinstallation tasks:

  • Did you decide where to install ABS server and client software?
  • Did you set your default directory to SYS$UPDATE?
  • Did you log into an account with the proper quotas and privileges?
  • Did you perform a system backup operation?
  • If you are doing an upgrade installation, did you shutdown ABS and MDMS?
  • Did you verify the hardware and disk space requirements?
  • Did you verify the software requirements?
  • Did you check to see if DECnet (Phase IV), DECnet-Plus or TCP/IP, and the QueueManager are running?
  • Did you register the appropriate licenses?

3.1 Installing Archive Backup System for OpenVMS Software

See See Stages of Installing ABS Software for the stages of installing and configuring ABS/MDMS software.

Before installing ABS in a real time, storage management environment, hp recommends that you first install and configure ABS in a test environment. If you are not satisfied with the test installation, delete ABS and reinstall it.

Stages of Installing ABS Software

Stage

Action
  1. 1.

Install ABS server software as described in See Installing ABS/MDMS Server Software.

 

Note:

If you are installing ABS in a mixed architecture environment (VAX and Alpha systems resident in a single OpenVMS Cluster), install the software in a common location. This will place the database and catalog files in a common location for the entire cluster. Images will be placed on the system disks for each system. Install ABS/MDMS on each node.
  1. 2.

Install ABS OpenVMS client software as described in See Installing ABS OpenVMS Client Software.

 

Note:

OpenVMS client support is not available with an ABS-OMT license.
  1. 3.

Install ABS Windows client software as described in See Installing and Configuring ABS Windows Clients.
  1. 4.

Install ABS Tru64 UNIX clients as described in See Configuring ABS Tru64 UNIX Clients.
  1. 5.

Authorize Windows and Tru64 UNIX clients as described in See Authorizing Windows and Tru64 UNIX Clients.
  1. 6.

Follow the Post-Installation steps in Chapter 4.
  1. 3.1.1 Installing ABS/MDMS Server Software

ABS/MDMS installation procedure consists of a series of questions and informational messages. The procedure will give you an option of doing a standard installation or not. The standard installation will install the ABS/MDMS software in the following manner:

ABS will be installed with the following options:
Device for ABS/MDMS - SYS$COMMON (will use current values if either MDMS or ABS are already installed)
UIC for the ABS account - [311,311]
Nodes for the database severs - Current node or already existing server nodes
What scheduling option do you want - INTERNAL
Are you using backup-via-shelving - YES (If HSM is present)

MDMS will be installed with the following options:
Device for ABS/MDMS - SYS$COMMON (or current installed location)
UIC for MDMS Account - [312,312] (or will be constructed from ABS UIC)
Node for database servers - Current node or already existing server nodes
Do you want to replace MRD$RTL.EXE - YES

MDMS GUI will files will be installed with the following options:
Do you want the MDMS GUI installed on Alpha OpenVMS - YES (if on Alpha)
Do you want files extracted for Microsoft Windows on Intel - YES

Remote Device Facility (RDF) will be installed with the following options:
Do you want MDMS support for RDF Server - YES
Do you want MDMS support for RDF Client - YES

Questions always asked:
Do you want to purge files - YES
Do you want to run the IVP - YES (except if ABS-OMT installation)

If for any reason you need to abort the installation procedure, at any time you can press CTRL/Y and the installation procedure deletes all files it has created up to that point and then exits. From this point, you can restart the installation procedure again.

Follow the steps in See How to Install ABS Software to install ABS software.

How to Install ABS Software

Step

Action
  1. 1.

Invoke VMSINSTAL:

 

$ @SYS$UPDATE:VMSINSTAL saveset-name drive-name OPTIONS N

To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command procedure:

 

save set name

The installation name for the component.

ABS042 (for example)


drive-name

The name of the drive where the media that contains the kit is located. For example, MTA0: is the device name for a tape drive or device:[directory] can be the CD-ROM drive name. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete.

OPTIONS N

An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation.

Note:
If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. If you specify more than one option, separate them with commas (OPTIONS A,N).

The following examples invoke VMSINSTAL to install ABS from the tape drive MTA0: and shows the responses. This example uses the OPTIONS N release note parameter.

$ @SYS$UPDATE:VMSINSTAL saveset_name MTA0: OPTIONS N

OpenVMS VAX Software Product Installation Procedure V7.2
It is 21-JUL-1996 at 10:00
Enter a question mark (?) at any time for help.

If you do not supply either the product name or the drive name, VMSINSTAL prompts you for this information later in the installation procedure.

Note:
VMSINSTAL does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation procedure. See OpenVMS documentation located in the OpenVMS System Management Subkit for detailed information on these options.

 

 

  1. 3.1.2 Installing ABS OpenVMS Client Software

OpenVMS client support is not available with an ABS-OMT license.

When installing ABS software, notice that ABS does not provide two separate software kits. Instead, installation of ABS OpenVMS server or client software is determined by the OpenVMS node name that you enter during the installation procedure.

See Installing ABS OpenVMS Client Software describes how to install and configure an ABS OpenVMS client.

In See Installing ABS OpenVMS Client Software, ABS server node is referred to as SVNODE::, and ABS client node is referred to as CLNODE::

Installing ABS OpenVMS Client Software

Step

Action
  1. 1.

Install ABS software on the OpenVMS client node as on the server node, with one exception.

 

When the installation procedure prompts for the node name for the server (ABS OpenVMS server node), do not accept the default node name (client node name). Instead, enter the OpenVMS Cluster alias or OpenVMS node name that you entered when you installed ABS OpenVMS server software:

* Node name list for Database Servers : SVNODE

Result:
ABS installs only the client portion of ABS software on the node named CLNODE::.
  1. 2.

Create save and restore requests for OpenVMS clients as described in Archive Backup System for OpenVMS Guide to Operations .
  1. 3.

Create (or modify) storage and environment policies. Archive Backup System for OpenVMS Guide to Operations describes how to create those policies.
  1. 4.

Create system and user backup operations using the correct storage and environment policies. Archive Backup System for OpenVMS Guide to Operations , provides instructions for these tasks.

 

  1. 3.1.3 Installing and Configuring ABS Windows Clients

Requirements:

If you use FTP to copy the setup files to the Windows System, be sure to copy the files in binary mode.

See Stages of Installing an ABS Windows Client describes the stages of installing and configuring an ABS Windows client node.

Stages of Installing an ABS Windows Client

Stage

Action
  1. 1.

Register ABS Windows license on ABS OpenVMS server node. See See Registering ABS Licenses for instructions.
  1. 2.

Install ABS Windows client software on Windows client system as described in See Installing and Configuring an ABS Windows Client.

Note:
You must perform a separate installation on each Wndows client node that you want ABS to back up.
  1. 3.

Authorize the Windows client systems that you plan to back up using ABS (described in See Authorizing Windows and Tru64 UNIX Clients and See .
  1. 4.

Create save and restore requests for the Windows client system by using the GUI on the Windows client system, or by using the GUI or DCL on ABS OpenVMS server node. See Archive Backup System for OpenVMS Guide to Operations and Archive Backup System For OpenVMS MDMS Reference Guide for instructions about creating save and restore requests for Windows clients.

To install and configure the Windows client software, use the procedure in See Installing and Configuring an ABS Windows Client.

 

Installing and Configuring an ABS Windows Client

Step

Action
  1. 1.

Copy all files from one of the following directory located on ABS OpenVMS server node to the Windows client system where you plan to install the Windows client software, or to a location accessible by the Windows client system.


The Windows client software is provided during ABS server installation procedure. ABS creates the appropriate directory and places the Windows client software kit in the following directory:

ABS$ROOT:[CLIENTS.NT.INTEL]

 
  1. 2.

Run SETUP.EXE from this location to install ABS Windows client software.

 

Result:
ABS Windows client installation procedure prompts for information about the ABS server and the local host port number.

 

Answer the prompts exactly as you answered them during ABS server installation procedure:

 

ABS server node-Enter the node(s) on which ABS server software has been installed and will be providing ABS services for the Windows client backup operations. If multiple nodes are specified, separate them with semi-colons. This node also verifies connection requests. If a server node is multihomed (has more than one IP address/name), specify all the names which may be used during a backup request.

 

Local host port number-The Windows client system uses a TCP/IP port to communicate with ABS server to initiate save and restore requests. The default port number is 1800. If you decide to change the port number, it is limited to a range between 1024 and 65535. This port number is arbitrary, but it must match the port number you use when you authorize Windows clients, described in Appendix A.

To test to see if port number 1800 is already in use, enter the following command from ABS OpenVMS server system prompt:

$ TELNET node 1800
Where: node is the node name of the OpenVMS server node

Note:
Make sure that the number you provide does not conflict with a previously installed software application.
  1. 3.

Authorize the Windows clients you plan to back up using ABS as described in See Authorizing Windows and Tru64 UNIX Clients and Appendix A.

 

 

  1. 3.1.4 Configuring ABS Tru64 UNIX Clients

To allow ABS to perform backup and restore operations for Tru64 UNIX clients, you must configure access between the OpenVMS systems that run ABS server software and the Tru64 UNIX client systems that contain the files to be backed up. The stages of installing and configuring a Tru64 UNIX client is described in See Stages of Installing and Configuring an ABS Tru64 UNIX Client.

There is no extra software kit provided for Tru64 UNIX clients.

 

Stages of Installing and Configuring an ABS Tru64 UNIX Client

Stage

Action
  1. 1.

Register ABS Tru64 UNIX license on the ABS OpenVMS server node. See Section 2.11 for instructions.
  1. 2.

Register ABS Tru64 UNIX license on the ABS OpenVMS server node. See Section 2.11 for instructions.
  1. 3.

Modify the appropriate files on the Tru64 UNIX client system as described in the See Modifying the Appropriate Tru64 UNIX Files.
  1. 4.

Transfer the gtar and gzip sources from ABS OpenVMS server node to each Tru64 UNIX client system that you intend to back up using ABS. See See Transferring the Tru64 UNIX Backup Agent Sources.
  1. 5.

Build the executables on each Tru64 UNIX client system that you plan to back up using ABS as described in See Building the Tru64 UNIX Executables.
  1. 6.

Authorize the Tru64 UNIX clients as described in See Authorizing Windows and Tru64 UNIX Clients and Appendix A.
  1. 7.

Create save and restore requests for theTru64 UNIX client from the OpenVMS server node. See Archive Backup System for OpenVMS Guide to Operations and Archive Backup System for OpenVMS MDMS Reference Guide for instructions about creating save and restore requests for Tru64 UNIX clients.

 
  1. 3.1.4.1 Modifying the Appropriate Tru64 UNIX Files

See Modifying the Appropriate Tru64 UNIX Files, lists the files that you need to modify on each Tru64 UNIX client system that ABS is going to back up, and it describes the modifications to make for those specific files.

Tru64 UNIX is a case sensitive system. Be sure to enter the commands on the Tru64 UNIX client system exactly as they are shown in See Modifying the Appropriate Tru64 UNIX Files and See Transferring the Backup Agent Sources.

 

Modifying the Appropriate Tru64 UNIX Files

File

Modification

/.rhosts 4

Replace the ASCII readable internet address with ABS OpenVMS server nodes. The file format is:

# readable ip address account
node01.vms.real.node ABS #ABS on node NODE01

In this example, replace node01.vms.real.node with ABS OpenVMS server node names. The account name must stay the same (ABS), and it must be specified in capital letters.

Example of /.rhosts:

node01.vms.real.node ABS
node02.vms.real.node ABS

Requirement:
You must always modify the /.rhosts file. If the file does not exist, then you must create it. Be sure that the /.rhosts file is located in the root directory and that is owned by the root account because ABS uses this directory during the backup operation.

/etc/hostsa

List the numeric internet address and the ASCII readable internet address of ABS OpenVMS server nodes. The file format is:

 

# Internet Address Hostname # Comments
nn.nn.nn.nn node01.vms.real.node # example entry for hosts file

Where:

 

  • nn.nn.nn.nn is the numeric internet address of ABS node that executes save and restore requests.
  • node01.vms.real.node is the ASCII readable internet address of nn.nn.nn.nn. You must enter every node name on which ABS may execute.

Example of /etc/hosts:

01.02.03.04 node01.vms.real.node # node01 running ABS
01.02.01.04 node02.vms.real.node # node02 running ABS

Note:
If ABS OpenVMS server nodes are already listed in the file /etc/hosts, you do not need to add them again.
  1. 3.1.4.2 Transferring the Tru64 UNIX Backup Agent Sources

During the installation of ABS server software, the installation procedure creates a directory named ABS$ROOT:[CLIENTS.UNIX] on ABS server node. This directory contains the following two uncompressed sources that make up the Tru64 UNIX backup agent:

To configure a Tru64 UNIX client, you must transfer the gtar and gzip sources to each Tru64 UNIX client system that ABS is going to back up, build the executables, and place them in /usr/bin.

Refer to See Transferring the Backup Agent Sources to transfer the gtar and gzip sources from ABS server node to theTru64 UNIX client system.

  1. Transferring the Backup Agent Sources

u_node> ftp node01 # Connect to the ABS OpenVMS Server Node
Connected to node01.vms.dec.com.
220 node01 FTP Server (Version 3.3) Ready.
Name (node01:user1): user1
331 Username USER1 requires a Password.
Password:
230 User logged in.
Remote system type is VMS.

ftp> cd abs$root:[clients.unix] # Change to the directory that contains the files
250 CWD command successful.
ftp> pwd
257 "ABS$ROOT:[CLIENTS.UNIX]" is current directory.
ftp> ls # List the files in this directory
200 PORT command successful.
150 Opening data connection for (16.82.16.75,1174)
gnu_general_public_license.txt;4
gnu_readme_where_to_get.txt;4
gzip-1_2_4.tar;4
tar-1_13.tar;4
226 NLST Directory transfer complete.

ftp> bin # set the file transfer mode to binary
200 TYPE set to IMAGE.

ftp> get # Get the sources
(remote-file) tar-1_13.tar
(local-file) tar-1_13.tar
200 PORT command successful.
150 Opening data connection for tar-1_13.tar (16.82.16.75,1178)
226 Transfer complete.
2662400 bytes received in 5.7 seconds (4.6e+02 Kbytes/s)

ftp> get # Get the sources
(remote-file) gzip-1_2_4.tar
(local-file) gzip-1_2_4.tar
200 PORT command successful.
150 Opening data connection for gzip-1_2_4.tar (16.82.16.75,1494)
226 Transfer complete.
798720 bytes received in 1.8 seconds (4.3e+02 Kbytes/s)

ftp> quit
221 Goodbye

  1. 3.1.4.3 Building the Tru64 UNIX Executables

After you have transferred the gtar and gzip sources, you are required to build the executables on the Tru64 UNIX client system. With a Tru64 UNIX OS version upgrade, it is mandatory to rebuild ABSgtar and ABSgzip executables on the Tru64 UNIX client.

The following sections describe how to build the tar and gzip executables.

  1. 3.1.4.3.1 Building the tar Executable

Use the following procedure to build the tar executable:

  1. 1. Use native tar to expand the tar file
  2. 2. Change directory to the tar directory
  3. 3. Enter the command ./configure --disable-nls
  4. 4. Enter the command make to build the tar image
  5. 5. Verify the tar image was created
  6. 6. Change directory to src
  7. 7. Verify that it is an executable image
  8. 8. Change to super user
  9. 9. Copy the executable from src/tar to usr/bin/ABSgtar
  10. 10. Change the protection on the image
  11. 11. Display the complete directory
  12. 12. Exit super user
  13. 13. Perform a cleanup operation

Example of tar

u_node> tar -xvf tar-1_13.tar 1
tar-1.13/README
tar-1.13/AUTHORS
.

.

.
tar-1.13/po/sv.gmo

u_node> cd tar-1.13 2
u_node> ./configure --disable-nls 3
creating cache ./config.cache
checking host system type... alpha-dec-osf3.2

.

.

.
creating config.h

u_node> make 4
for subdir in doc lib intl src scripts po; do \

echo making all in $subdir; \
(cd $subdir && make CC='gcc' CFLAGS='-g -O' LDFLAGS='' LIBS=''
prefix='/usr/local' exec_prefix='/usr/local'
bindir='/usr/local/bin' libexecdir='/usr/local/libexec'
infodir='/usr/local/info' infodir='/usr/local/info'
libexecdir='/usr/local/libexec' all) || exit 1; \

done
making all in doc

.

.

.
make[1]: Leaving directory `/usr/users/user1/tar-1.13/po'

u_node> ls src 5
Makefile checktar.sh extract.o list.c open3.h rmt.o tar.h
.

.

.
buffer.c diffarch.o gnu.c names.c rmt.c tar 5

u_node> cd src 6
u-node> file tar 7
tar: COFF format alpha dynamically linked, demand paged
executable or object module not stripped
- version 3.13-14

u-node> su 8
Password:

# cp tar /usr/bin/ABSgtar 9
# chmod ugo+x /usr/bin/ABSgtar 10
# ls -l /usr/bin/ABSgtar 11
-rwxr-xr-x 1 root system 655794 Jan 24 11:07 ABSgtar
# exit 12

u-node> cd .. 13
u-node> rm -rf tar-1_13 13
%rm -f tar-1_12.tar 13

  1. 3.1.4.3.2 Building the gzip Executable

Use the following procedure to build the gzip executable:

  1. 1. Use the native tar to expand the gzip-1_2_4.tar image
  2. 2. Change directory to gzip-1.2.4
  3. 3. Enter the command ./configure
  4. 4. Enter the command make
  5. 5. Verify that the gzip file is there
  6. 6. Make sure it is an executable
  7. 7. Change to super user
  8. 8. Copy gzip file to /usr/bin/ABSgzip
  9. 9. Change the protection on the image
  10. 10. Exit super user
  11. 11. Perform a cleanup operation

Example of gzip

u_node> tar -xvf gzip-1_2_4.tar 1
gzip-1.2.4/README

.

.

.
gzip-1.2.4/primos/include/sysTypes.h

u_node> cd gzip-1.2.4 2

u_node> ./configure 3
checking for gcc

.

.

.
checking for gzip to derive installation directory prefix
chose installation directory prefix /usr/local
creating config.status
creating Makefile

u_node> make 4
gcc -c -DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1 -DDIRENT=1 -O gzip.c

.

.

.
gcc -O -o gzip gzip.o zip.o deflate.o trees.o bits.o unzip.o
inflate.o util.o crypt.o lzw.o unlzw.o unpack.o unlzh.o getopt.o
/usr/ucb/ld:
Warning: Linking some objects which contain exception information sections and some which do not. This may cause fatal runtime exception handling problems (last obj encountered without exceptions was crypt.o).

rm -f gunzip zcat
ln gzip gunzip
ln gzip zcat

u_node> ls gzip 5
gzip
u_node> file gzip 6
gzip: COFF format alpha dynamically linked, demand paged executable or object module not stripped
- version 3.11-8

u-node> su 7
Password:
# cp gzip /usr/bin/ABSgzip 8
# chmod ugo+x /usr/bin/ABSgzip 9
# ls -l /usr/bin/ABSgzip
-rwxr-xr-x 1 root system 654785 Jan 24 11:08 ABSgzip
# ln -s /usr/bin/ABSgzip /usr/bin/gzip
# exit 10

u-node> cd .. 11
u-node> rm -rf gzip-1.2.4 11
u-node> rm -f gzip-1_2_4.tar 11

If you have problems transferring or building the tar or gzip files, see your Tru64 UNIX system manager.

  1. 3.1.5 Authorizing Windows and Tru64 UNIX Clients

After you have registered and loaded the Windows or Tru64 UNIX client license on ABS server node, run the authorization executable file to authorize the Windows or Tru64 UNIX client node names that you intend to back up using ABS. You must authorize access on the ABS OpenVMS server system for each Tru64 UNIX and Windows system that you are going to back up using ABS.

See Authorizing NT and Tru64 UNIX Client Nodes describes how to authorize Windows and Tru64 UNIX client nodes.

ABS Windows and Tru64 UNIX client licenses are sold in units according to the number of nodes that you want to support: 1, 5, 10, 25, 50, or 100. ABS calculates the number of nodes authorized versus the number of units the license allows. You cannot authorize more Windows or Tru64 UNIX clients than the number of units allowed by the Windows or Tru64 UNIX client license that you have purchased.

Authorizing NT and Tru64 UNIX Client Nodes

Step

Action
  1. 1.

Enter the following command from ABS server:

$ RUN SYS$SYSTEM:ABS$CLIENT_LICENSE.EXE
  1. 2.

Add the node names of the Tru64 UNIX or Windows client nodes. When prompted, specify an NT or UNIX client:

 

Would you like to Add/Modify/Remove/Show the Client License?: ADD

Enter Node Name: CLIENT_NODE_NAME

Client Node Type (UNIX or NT) [UNIX]: NT

Enter TCPIP Port Number [1800]:

Note:

The port number is arbitrary, but it must match the port number you use when you install the NT clients.
  1. 3.

If the client node is an Windows client, enter the port number. The default is 1800.
  1. 4.

Make sure that the logical named ABS$CLIENT_DB is defined as
/SYSTEM/EXEC and that it translates to ABS$ROOT:[DATABASE]CLIENT_DB.DAT. This logical name should be defined during the startup procedure. You can verify that the logical name is defined correctly by entering the following command:

$ SHOW LOGICAL/FULL ABS$CLIENT_DB

More Information:
For an example of adding, modifying, removing and showing Windows or Tru64 UNIX clients, see See .

4

Performing Postinstallation Tasks

Complete ABS/MDMS postinstallation tasks described in this chapter after you have successfully installed ABS/MDMS OpenVMS server or client software:

OpenVMS client support is not available with an ABS-OMT license.

4.1 Installing ABS for the First Time

If you are installing ABS as a new installation, database initialization programs may fail to run. To initialize the database with the default storage policies and execution policies, run the following executable:

RUN SYS$SYSTEM:ABS$DB_INIT.EXE

4.2 Create a Node Object

If this is the initial installation of MDMS, you may need to create the node object in the MDMS node database for this node. Use the MDMS CREATE NODE command to create this initial database node. Refer to the command reference guide for the qualifiers for this command. The following is an example:

$ MDMS CREATE NODE NABORS -
! NABORS is the DECnet Phase IV node name or a
! name you make up if you do not use DECnet
! Phase IV in your network
/DATABASE_SERVER -
! a potential database node
! must also be defined in
! in SYS$STARTUP:MDMS$SYSTARTUP.COM
/TCPIP_FULLNAME=NABORS.SITE.INC.COM -
! the TCP/IP full node name if you
! are using TCP/IP you need this if
! you are using the GUI
/DECNET_FULLNAME=INC:.SITE.NABORS -
! this is the full DECnet Phase V node name
! do not define if you do not have DECnet Phase V on this node
! be sure to define if you have DECnet Phase V installed on this node
/TRANSPORT=(DECNET,TCPIP)
! describes the transports that listeners are
! started up on

4.3 Verifying ABS Installation

If you did not execute the IVP during the installation procedure, you can execute it immediately after installing ABS/MDMS software. Enter the following command at the DCL system prompt:

$ @SYS$TEST:ABS$IVP.COM

$ @SYS$TEST:MDMS$IVP.COM

Support for installation IVP procedure is not available with an ABS-OMT license.

If an error occurs during the IVP, the following message is displayed:

ABS Version V4.2 Installation Verification Procedure failed.

%VMSINSTAL-E-IVPFAIL, The IVP for ABS Version V4.2 has failed.

Errors can occur during the installation if any of the following conditions exist:

For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message.

4.4 Providing Automatic Start Up and Shut Down

You must edit the startup and shutdown files to provide automatic startup and shutdown of ABS/MDMS software. To make sure that ABS/MDMS automatically starts up and shuts down, follow these steps:

  1. Step 1. Add the following command line to the system startup file named
    SYS$MANAGER:SYSTARTUP_ VMS.COM:

    $ @SYS$STARTUP:ABS$STARTUP
  2. Step 2. Add the following line to the system shutdown file named
    SYS$MANAGER:SYSHUTDWN.COM:

    $ @SYS$STARTUP:ABS$SHUTDOWN
    $ @SYS$STARTUP:MDMS$SHUTDOWN
  3. Step 3. When using MDMS with ABS, the MDMS startup is executed automatically. A logical name is defined by the MDMS startup which is needed by ABS.

4.5 ABS and MDMS Startup Queues

ABS$STARTUP uses the ABS$<node> queue to start the ABS processes. This queue will always exist after an ABS installation.

MDMS$STARTUP uses one of several queues to startup the MDMS$SERVER process. There is a logical name, MDMS$STARTUP_QUEUE, which may be defined in MDMS$SYSTARTUP.COM. This logical points to the queue which MDMS$STARTUP.COM will use. If you do not have this defined, it will attempt to use the ABS$<node> queue, then SYS$BATCH. If the logical is not defined and neither ABS$node or SYS$BATCH exist, the MDMS startup will fail.

4.6 Modifying ABS and MDMS Command Procedures

If you are updating ABS/MDMS and you have made customizations to any of the ABS/MDMS command procedures, you may need to modify those procedures to work with ABS/MDMS V4.2. There are four procedures for which we provide template files. If the template files have changed, you should include your customizations in the new template files and then rename them to the command procedure name. The four procedures and the templates are:

SYS$STARTUP:ABS$SYSTARTUP.COM - SYS$STARTUP:ABS$SYSTARTUP.TEMPLATE

SYS$STARTUP:MDMS$SYSTARTUP.COM - SYS$STARTUP:MDMS$SYSTARTUP.TEMPLATE

MDMS$SYSTEM:MDMS$EXT_QUEUE_MANAGER.COM - MDMS$SYSTEM:MDMS$EXT_QUEUE_MANAGER.TEMPLATE

MDMS$SYSTEM:MDMS$EXT_SCHEDULER.COM - MDMS$SYSTEM:MDMS$EXT_SCHEDULER.TEMPLATE

4.7 Meeting OpenVMS Cluster Requirements

If you installed ABS server software on an OpenVMS Cluster system, perform the steps in See Updating the DCL Tables on each node in the OpenVMS Cluster (excluding the installing node) where you want to use ABS.

The command line interface is not available with the ABS-OMT license, you must use the GUI.

Updating the DCL Tables

Step

Action
  1. 1.

Run the command procedure ABS$STARTUP from each node that you want to use ABS. This ensures ABS$/MDMS$ logical names are defined the same across all nodes in the OpenVMS Cluster:

$ @SYS$STARTUP:ABS$STARTUP.COM
  1. 2.

Update the DCL table on each node in the OpenVMS Cluster (excluding the installing node).

 

Enter the following command on each node:

$ INSTALL REPLACE SYSLIBRARY:DCLTABLES.EXE
  1. 3.

Have all system users log off and log on again to enable them to use the DCL ABS/MDMS commands (unless performing an upgrade).

 

4.8 Configure MDMS

Now that you have installed MDMS you need to configure the MDMS database. MDMS provides a command procedure that you can use to configure the MDMS database in a new installation. The procedure is completely self-documenting with a help facility, and all key object attributes are defined. The procedure guides you through the following configuration objects:

The procedure is activated using the following command:

$ @ MDMS$SYSTEM:MDMS$CONFIGURE.COM

Please refer to the Archive Backup System for OpenVMS Guide to Operations, Appendix "Configuration Example" for an example of using this procedure. If you are upgrading from SLS or ABS V2.9x, you should use the procedure MDMS$CONVERT_V2_TO_V3 instead. Refer to Appendix D.

Once MDMS is installed, and any conversions are performed, you may wish to adjust your configuration prior to performing MDMS operations.

In addition to configuring MDMS, you may also have to configure robots for jukeboxes you are planning to use. For MRD-controlled jukeboxes, the robot name is the OpenVMS device name of the robot device, and they normally fall into one of several formats:

If the jukebox is controlled by direct-connect SCSI (first option), the robot device must first be loaded on the system with one of the following DCL commands:

Alpha - $ MCR SYSMAN IO CONNECT GKxxx/NOADAPTER/DRIVER=SYS$GKDRIVER.EXE

VAX - $ MCR SYSGEN CONNECT GKxxx/NOADAPTER/DRIVER=GKDRIVER

and the device name must begin with GK. It is suggested that these commands be included in a system startup file so that they are automatically configured at boot time.

4.9 Configure Remote Tape Drives

If you installed the RDF software, you need to configure the remote tape drives. RDF is not available if you are installing MDMS with the ABS-OMT license.

For each tape drive served with RDF Server software, make sure there is a drive object record in the MDMS database that describes it. Refer to the chapters on MDMS configuration in the Archive Backup System for OpenVMS Guide to Operations and the MDMS CREATE DRIVE command in the command reference guide.

For each node connected to the tape drive, edit the file TTI_RDEV:CONFIG_node.DAT and make sure that all tape drives are represented in the file. See the Archive Backup System for OpenVMS Guide to Operations for more information on remote drive setup.

During startup of MDMS, the RDF client and server are also started. The RDF images are linked on your system. If you see the following link errors on Alpha V6.2, this is not an RDF bug. The problem is caused by installed VMS patches ALPCOMPAT_062 and ALPCLUSIO01_062.

%LINK-I-DATMISMCH, creation date of 11-FEB-1997 15:16 in
shareable image SYS$COMMON:[SYSLIB]DISMNTSHR.EXE;3
differs from date of 4-MAY-1995 22:33 in shareable image library
SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1
.
.
.

This is a known problem and is documented in TIMA. To correct the problem, issue the following DCL commands:

$ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:DISMNTSHR.EXE
$ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:INIT$SHR.EXE
$ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:MOUNTSHR.EXE

4.10 Granting the Appropriate ABS/MDMS Access Right Identifiers

When ABS Server installation procedure is complete, the user account that performed the installation (typically the SYSTEM account) is granted the following ABS access rights identifiers. These identifiers are only needed if you use ABS DCL commands, or if you have the ABS_RIGHTS option turned on in the MDMS domain. For details on MDMS rights identifiers refer to Section 5.1 of ABS/MDMS Operations Guide.

Before any user can use MDMS commands or the MDMSView GUI, you must grant MDMS rights to those users. Enabling an Access Rights Identifier. See the Archive Backup System for OpenVMS Guide to Operations "Security" Chapter for more information on the use of identifiers.

 

To grant an access rights identifier to a user's account, run the AUTHORIZE utility.

Example:

$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE

UAF>GRANT/IDENTIFIER ABS_LOOKUP_ALL USER1

%UAF-I-GRANTMSG, identifier ABS_LOOKUP_All granted to USER1

UAF>EXIT

Do not enable the access rights identifier by performing a SET RIGHTS_LIST at the DCL prompt.

  1. 4.10.1 Revoking An Access Rights Identifier

To remove an access right identifier, run AUTHORIZE utility and revoke the identifier from the user's account:

$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE

UAF>REVOKE/IDENTIFIER ABS_BYPASS USER1
%UAF-I-REVOKEMSG, identifier ABS_BYPASS revoked from USER1

You can modify the other policy objects provided by ABS in the same manner. See Archive Backup System for OpenVMS Guide to Operations for instructions about adding users and enabling access controls.

Before using your storage policy, you may need to modify the MDMS related information in the policy. For example, you may wish to use a different media type than the default media type from your MDMS domain. When ABS is installed, the storage policies are initialized with the defaults from the domain. Issue an MDMS SHOW DOMAIN command to see the defaults. Make sure that your storage policy contains the desired settings before executing a save request.

4.11 Verifying Windows and Tru64 UNIX Client Quotas

If you are supporting Windows or Tru64 UNIX clients, to ensure successful save and restore operations, set the quotas to the following values on ABS OpenVMS server node:

UCX> SET PROTOCOL TCP /QUOTA=(SEND:50000,RECEIVE:50000)

4.12 Adding Windows Parameter

Issuing multivolume SAVE requests to Windows client requires you to modify the Registry Path

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Sevices\Tcpip\Parameters

with the following Windows parameter (20 or greater is recommended).

TcpMaxDataRetransmissions REG_DWORD 20

This change to the default built in Windows parameter/subkey ensures that the TCP/IP connection is not prematurely terminated with send failure.

After making the changes to the parameter, you need to reboot the system to allow the changes to take effect.

4.13 Allowing ABS Access to All Files on the Windows Systems

ABS must have access to all the files you wish to backup on your Windows system. There are two ways to do this:

To set the file access,

This gives the SYSTEM account access to the files.

ABS, by default, uses the SYSTEM account to backup the files. If you wish to change the account used by ABS, you may do this by modifying the properties of the service:

The account that you select should be a member of the Administrator group. The administrator group should be able to access all the files on your Windows system, unless you set access denied for Administrator on a file.

4.14 ABS/MDMS Graphical User Interface (GUI) Installation

This section describes how to install and run the Graphical User Interface (GUI) on various platforms.

As the GUI is based on Java, you must have the Java Runtime Environment (JRE) installed on the system where you are running the GUI. If you do not have the JRE installed on your system see the information below for kit locations.

The ABS/MDMS installation procedure extracts files from the kit and places them in MDMS$ROOT:[GUI...]. You can then move the Windows files to a Windows system and install them.

For the GUI to communicate with the MDMS server, you must have TCP/IP services on the node where you have the MDMS server running.

The GUI re quires the following in order to run:

Java Runtime Environment V1.2 or above - Since the ABS/MDMS GUI is a Java application, it requires the platform specific JRE. You can download the correct kit from the given URLs. For the OpenVMS installation, you may alternatively install the Standard Edition kit instead of the JRE kit. This is packaged as a PCSI kit, which is simpler to install. Issues concerning availability and installation can be directed to:

http://java.sun.com/products (for Microsoft Windows)

http://www.compaq.com/java (for OpenVMS Alpha)

Memory - On Windows systems, the hard drive space requirement is 4 MB for the MDMS GUI. The main memory space requirement for running the GUI is 10 MB.

  1. 4.14.1 Installing the GUI on OpenVMS Alpha

During the ABS/MDMS installation, the following question will be asked:

Do you want the MDMS GUI installed on OpenVMS Alpha [YES]?

Reply "Yes" to the question if you want to install the GUI on OpenVMS. Files will be moved to MDMS$ROOT:[GUI.VMS] and the GUI installation will be complete.

If you have not already installed the JRE, you should install it by following the instructions provided at the download site, http://www.compaq.com/java. The version specific setup command procedure provided by the Java installation will establish defaults for the logical names and symbols on the system. You should add a command line to the

SYS$COMMON:[SYSMGR]SYLOGIN.COM

command procedure to run this Java setup command procedure at login.

The JAVA$CLASSPATH is defined for the GUI in the

MDMS$SYSTEM:MDMS$START_GUI.COM

command procedure provided during the installation. The call to Java to invoke the GUI is also included in this command procedure.

Make sure that the logical JAVA$USER_DCL is not defined or the GUI will not work.

  1. 4.14.2 Installing the GUI on Intel Windows NT/95/98

During the ABS/MDMS installation, the following question will be asked:

Do you want files extracted for Microsoft Windows [YES]?

Reply "Yes" if you want to install the GUI on a Microsoft Windows platform. Files will be moved to MDMS$ROOT:[GUI.WINTEL].

Move the file MDMS$ROOT:[GUI.WINTEL]SETUP.EXE to the Windows machine and run it to install the GUI.

If you have not installed the JRE, you should install it by following the instructions at the download site: http://java.sun.com/products.

4.15 Running the GUI

Now that you have installed the GUI, you have to make sure that the server node is configured to accept communications from the GUI. The server node for the GUI must have:

To enable TCP/IP communications on the server, you have to set the TCP/IP Fullname attribute and enable the TCP/IP transport. See the command reference guide for information about setting these attributes on a node.

MDMS rights for the user must be enabled in the SYSUAF record so that the user may login to the server using the GUI. Refer to the command reference guide for information on MDMS rights.

The OpenVMS Alpha account which will be used to run the GUI should have the PGFLQUO account quota set to 200,000. Correspondingly, the system pagefile should contain enough space to handle the large pgflquo value. The account should also have a WSQUOTA value of at least 10,000. The sysgen parameter WSMAX should be 10,000 or higher. The system should also have a minumum of 128 meg of RAM, with a higher amount recommended.

  1. 4.15.1 Running the GUI on OpenVMS Alpha

To use the MDMS GUI on OpenVMS Alpha systems, use the following commands:

$ SET DISPLAY/CREATE/NODE=node_name/TRANSPORT=transport

$ MDMS/INTERFACE=GUI

For the SET DISPLAY command, the node_name is the name of the node on which the monitor screen exists. This allows you to use the GUI on systems other than those running OpenVMS Alpha V7.2 or higher. The transport must be a keyword of:

To use the ABS/MDMS GUI on Microsoft Windows platforms, double click on the batch file named MDMSView.bat in the MDMSView directory on the drive where you installed the GUI.

To view the ABS/MDMS GUI correctly, you must have the display property settings for the screen area set to 1024 X 768 or higher.

If you have Java installed in a location other than the normal default location, you will need to first edit the MDMSView.bat file to include the correct path. The default in this file is

C:\Program Files\JavaSoft\JRE\1.2\bin\java.exe

4.16 Configuration of ABS/MDMS for System Backup to Tape for Oracle Databases

If you are configuring ABS/MDMS for System Backup to Tape for Oracle Databases, refer to the System Backup to Tape for Oracle Databases section in the Archive Backup System for OpenVMS Guide to Operations.

 

 

Examples of Authorizing Windows and Tru64 UNIX Clients

This appendix contains examples of how to authorize Windows and Tru64 UNIX clients. This includes adding, modifying, showing, and removing Windows and Tru64 UNIX client licenses.

To use the license command as shown in the example in this appendix, you can define the following symbol at the system prompt:

$ LICENSE := $SYS$SYSTEM:ABS$CLIENT_LICENSE.EXE

All of the examples in the following sections use this symbol definition.

  1. A.1 Adding Client Licenses

See Adding Client Licenses shows how to add a Tru64 UNIX or Windows client license

  1. Adding Client Licenses

$ LICENSE

Would you like to Add/Modify/Remove/Show the Client License?: ADD
Enter Node Name: NTNODE
Client Node Type (UNIX or NT) [UNIX]: NT
Enter TCPIP Port Number [1800]: 1800
Client NTNODE successfully ADDED to License Database
License Count: 1 used of 6 total

$ LICENSE

Would you like to Add/Modify/Remove/Show the Client License?: ADD
Enter Node Name: UNIX_1
Client Node Type (UNIX or NT) [UNIX]: UNIX
Client UNIX_1 successfully ADDED to License Database
License Count: 1 used of 25 total

  1. A.2 Modifying Client Licenses

See Modifying a Client License shows how to modify the port number of an Windows or Tru64 UNIX client license.

The port number that you enter here must match the port number you assigned during the NT client installation.

  1. Modifying a Client License

$ LICENSE

Would you like to Add/Modify/Remove/Show the Client License?: MODIFY
Enter Node Name: NTNODE
Client Node Type (UNIX or NT) [UNIX]: NT
Current values
Type: Windows NT
Transport:TCP/IP
Port:1800

New Port #?: 1800
Client NTNODE successfully MODIFIED in License Database

License Count: 1 used of 6 total

$ LICENSE

Would you like to Add/Modify/Remove/Show the Client License?: MODIFY
Enter Node Name: UNIX_1
Client Node Type (UNIX or NT) [UNIX]: UNIX
Current values
Type: UNIX
Transport: TCP/IP
Port: 514

New Port #?: 1800
Client UNIX_1 successfully MODIFIED in License Database

License Count: 1 used of 25 total

  1. A.3 Showing Client Licenses

See Showing Client Licenses illustrates how to show an Windows or Tru64 UNIX client license.

  1. Showing Client Licenses

$ LICENSE

Enter Node Name or [ALL]: ALL
Client Node Type (UNIX or NT) [UNIX]: NT

Node Name Type Transport Port
--------- ---- --------- ----
NTNODE Windows NT TCP/IP 1800

License Count: 1 used of 6 total

$ LICENSE

Enter Node Name or [ALL]: ALL
Client Node Type (UNIX or NT) [UNIX]: UNIX

Node Name Type Transport Port
--------- ---- --------- ----
UNIX_1 UNIX TCP/IP 1800

License Count: 1 used of 25 total

  1. A.4 Removing Client Licenses

See Removing Client Licenses shows how to remove Windows or Tru64 UNIX client licenses:

  1. Removing Client Licenses

$ LICENSE

Would you like to Add/Modify/Remove/Show the Client License?: REMOVE
Enter Node Name: NTNODE
Client Node Type (UNIX or NT) [UNIX]: NT
Client NTNODE successfully REMOVED from License Database
License Count: 0 used of 6 total

 

 

How to Delete ABS/MDMS From Your System

To delete ABS software from your system, shut down ABS and delete it from the system:

$ @SYS$STARTUP:ABS$SHUTDOWN
$ @ABS$SYSTEM:ABS$DELETE_ABS

To delete MDMS software from your system, shut down MDMS and uninstall it from your system:

$ @SYS$STARTUP:MDMS$SHUTDOWN
$ @SYS$STARTUP:MDMS$UNINSTALL.COM

Index

A

ABS

deleting C-1

installation 3-1

NT clients 3-4

OpenVMS clients 3-4

UNIX clients 3-6

ABS and MDMS Startup Queues 4-3

ABS$SYSTARTUP.COM 4-3

ABS/MDMS Client Software 2-1

ABS/MDMS Graphical User Interface (GUI) Installation 4-8

ABS/MDMS Server Software 2-1

Adding Client Licenses A-1

Adding Windows Parameter 4-7

Allowing ABS Access to All Files on the Windows Systems 4-8

B

Batch Queues 4-3

C

Clients

NT 3-4

OpenVMS 3-4

UNIX 3-6

Configuration of ABS/MDMS for System Backup to Tape for Oracle Databases 4-11

Configure MDMS 4-4

Configure Remote Tape Drives 4-5

Convert ABS Policy Database to MDMS Database 4-5

Create a Node Object 4-2

D

Decide Where to Install ABS/MDMS software 2-1

Deleting

ABS C-1

G

Granting the Appropriate ABS/MDMS Access Right Identifiers 4-5

H

Hardware

requirements 2-3

I

Installation

ABS 3-1

NT clients 3-4

OpenVMS clients 3-4

UNIX clients 3-6

hardware requirements 2-3

optional software 2-4

privileges 2-2

process account quotas 2-5

required processes 2-6

software requirements 2-4

system parameters 2-5

verifying 4-2

Installing ABS for the First Time 4-2

Installing ABS/MDMS 1-1

IVP 4-2

J

Java Runtime Environment 4-8

M

MDMS$STARTUP_QUEUE Logical Name 4-3

MDMS$SYSTARTUP.COM 4-3

Meeting OpenVMS Cluster Requirements 4-4

Modifying ABS and MDMS Command Procedures 4-3

Modifying Client Licenses A-1

N

Node in MDMS Database 2-8

O

OpenVMS Clients 2-1

P

Parameters

system 2-5

Privileges

required 2-2

system 2-2

Process account quotas 2-5

Processes

required 2-6

Providing Automatic Start Up and Shut Down 4-3

Q

Quotas

process account 2-5

R

RDF 4-5

RDF Configuration 2-8

Removing Client Licenses A-3

Removing SLS/MDMS V2.x Automatic Startup 4-4

Requirements

hardware 2-3

optional software 2-4

privileges 2-2

process account quotas 2-5

processes 2-6

software 2-4

system parameters 2-5

Right Identifiers 4-5

Running the GUI 4-10

S

Showing Client Licenses A-2

Software

requirements 2-4

Software requirements

optional 2-4

T

TCPIP Quotas for Clients 4-7

Tru64 UNIX C lient 3-6

Tru64 UNIX Clients 2-2

U

UNIX 3-6

Updating ABS/MDMS 1-1

V

Verification

installation 4-2

Verifying ABS Installation 4-2

Verifying Windows and Tru64 UNIX Client Quotas 4-7

W

Windows Client 3-4

Windows Clients 2-1

Windows Parameter 4-7

1. See ABS Software Product Description (SPD) for supported versions.

2. The values listed for these system parameters represent the number of free global pages and global sections required to install and run ABS, not the total number you need to operate your system and other software.

3. This information is supplied in the LICENSE PAK document (provided with the software kit).

4. File is not replaced, only modified.