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 VSI Archive Backup System for OpenVMS Guide to Operations for information on configuring ABS/MDMS.

If you are updating ABS/MDMS, you should review the release notes provided in the installation kit. You can extract the release notes by using the following 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. You can directly upgrade from ABS/MDMS V3.x to any ABS/MDMS V4.x version.

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, refer to VSI Archive Backup System for OpenVMS 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. To verify the hardware installed, you can use the MRU kit that is provided along with the ABS kit.

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.

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.

VSI 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, refer to the VSI OpenVMS System Manager's Manual.

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 the Archive Backup System for OpenVMS Cover Letter.

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

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 for instructions.

Table 2.6 describes how to register your license using the LICENSE REGISTER command.

Table 2.7 describes how to register your license using the command procedure.

$ @SYS$UPDATE:VMSLICENSE.COM

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

See Table 3.1 for the stages of installing and configuring ABS/MDMS software.

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

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

ABS044 (for example)

$ @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.

* Node name list for Database Servers : SVNODE

ABS$ROOT:[CLIENTS.NT.INTEL]

$ TELNET node 1800

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

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

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

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

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

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

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

$ RUN SYS$SYSTEM:ABS$CLIENT_LICENSE.EXE

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]:

$ SHOW LOGICAL/FULL ABS$CLIENT_DB

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

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

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

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

ABS Version V4.4 Installation Verification Procedure failed.
%VMSINSTAL-E-IVPFAIL, The IVP for ABS Version V4.4 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.

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:

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.

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.4. 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

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

$ @SYS$STARTUP:ABS$STARTUP.COM

$ INSTALL REPLACE SYSLIBRARY:DCLTABLES.EXE

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

Refer to VSI Archive Backup System for OpenVMS Guide to Operations for an example of using this procedure. If you are upgrading from SLS or ABS V2.9x, you must use the MDMS$CONVERT_V2_TO_V4 command procedure.

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 might 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
I64 - $ MCR SYSMAN IO CONNECT GKxxx/NOADAPTER/DRIVER=SYS$GKDRIVER.EXE

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.

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.

RDF is supported on OpenVMS Alpha V8.3 but not supported on OpenVMS I64 V8.2-1 and later versions.

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 VSI Archive Backup System for OpenVMS Guide to Operations and the MDMS CREATE DRIVE command in the VSI OpenVMS ABS/HSM 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. Refer to VSI 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

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 VSI Archive Backup System for OpenVMS Guide to Operations.

Requirement:

To create Windows or Tru64 UNIX save requests, the requester (creating process) must have the ABS_CREATE_REMOTE_JOBS access rights identifier enabled.

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

$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF>REVOKE/IDENTIFIER ABS_BYPASS USER1
%UAF-I-REVOKEMSG, identifier ABS_BYPASS revoked from USER1

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)

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.

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

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.

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.

The GUI requires 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.hp.com/java (for OpenVMS Alpha and OpenVMSI64)

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.

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

SYS$COMMON:[SYSMGR]SYLOGIN.COM

MDMS$SYSTEM:MDMS$START_GUI.COM

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

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 that 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 minimum of 128 meg of RAM, with a higher amount recommended.

$ SET DISPLAY/CREATE/NODE=node_name/TRANSPORT=transport
$ MDMS/INTERFACE=GUI

C:\Program Files\Java\j2re1.4.2_06\bin\java.exe

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 VSI Archive Backup System for OpenVMS Guide to Operations.