Archive/Backup_System_for_OpenVMS___________________ Installation and Configuration Guide Order Number: AA-QHD2E-TE Software Version: Archive/Backup System for OpenVMS Version 2.1B Required Operating System: OpenVMS Version 6.1 or higher Required Software: Storage Library System For OpenVMS Version 2.6 or higher Media and Device Management Services For OpenVMS Version 2.6 or higher Required Software: DECnet Phase IV or DECnet-Plus Optional Software Version: Digital TCP/IP Services for OpenVMS ________________________________________________________________ October 1997 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from DIGITAL, an authorized sublicenser, or the identified licenser. While DIGITAL believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Digital Equipment Corporation makes no representations that the interconnection of its products in the manner described in this document will not infringe existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. © Digital Equipment Corporation 1995, 1996, 1997. All Rights Reserved. Printed in the United States of America. Alpha, DCL, DECnet, Digital UNIX, eXcursion, OpenVMS, OpenVMS Cluster, StorageWorks, VAXTPU, VAX, VMS, and the DIGITAL logo are all trademarks of Digital Equipment Corporation. AIX is registered trademark of International Business Machines Corporation. FTP Software is a trademark of FTP SOFTWARE, INC. HP is a registered trademark of Hewlett-Packard Company. Motif is a registered trademark of the Open Software Foundation, Inc. NT is a trademark of Microsoft Corporation. Oracle, Oracle Rdb, and Oracle RMU are all registered trademarks of Oracle Corporation. PostScript is a registered trademark of Adobe Systems, Inc. RDF is a trademark of Touch Technologies, Inc. SGI is a registered trademark of Chemical Bank. Solaris is a registered trademark of Sun Microsystems, Inc. StorageTek is a registered trademark of Storage Technology Corporation. SunOS is a trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Windows and Windows NT are both trademarks of Microsoft Corporation. X Window System is a trademark of Massachusetts Institute of Technology. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Welcome to ABS 1.1 What Do All Storage Environments Have In Common?.......................................... 1-1 1.2 What Makes a Storage Environment Unique?......... 1-2 1.3 How Does ABS Compliment Your Storage Environment?..................................... 1-2 1.4 What Is The Purpose of a Managed Media and Device Environment?..................................... 1-3 1.5 Mixed Architecture Environments.................. 1-5 1.5.1 Mixed Architecture Environments ............... 1-5 1.5.2 Principles Guiding Mixed Architecture Configuration.................................. 1-6 1.5.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster................... 1-7 1.5.3.1 Separate Disk Configuration................. 1-7 1.5.3.2 Separate Root Configuration................. 1-8 1.5.3.3 Separate Subdirectory Configuration......... 1-8 1.5.4 Implementation Specific Approach .............. 1-9 2 Meeting ABS Installation Requirements 2.1 Deciding Where to Install the ABS Server Software......................................... 2-4 2.2 Deciding Where To Install the ABS Client Software......................................... 2-5 2.3 Deciding Where to Install MDMS Server Software... 2-6 2.4 Deciding Where To Install The MDMS Client Software......................................... 2-7 2.5 Recommended Installation......................... 2-7 2.6 Using the Installation Worksheets................ 2-8 iii 2.7 Configuring Your Hardware........................ 2-10 2.7.1 Hardware Configuration For an Automated Media Library........................................ 2-10 2.7.1.1 Hardware Installation....................... 2-11 2.7.1.2 Test the Hardware........................... 2-11 2.7.2 Hardware Configuration for a Media Loader ..... 2-12 2.7.2.1 Hardware Installation....................... 2-12 2.7.2.2 Test the Hardware........................... 2-13 2.7.3 Hardware Configuration for an Operator Attended Drive.......................................... 2-14 2.7.3.1 Hardware Installation....................... 2-14 2.7.3.2 Test the Hardware........................... 2-15 2.8 Required Privileges.............................. 2-15 2.9 Required OpenVMS Operating System Subclasses..... 2-16 2.10 Hardware, Software, and System Requirements...... 2-16 2.10.1 Required Hardware ............................. 2-16 2.10.2 Required Software ............................. 2-18 2.10.3 Optional Software ............................. 2-19 2.10.4 Required System Parameters .................... 2-21 2.10.5 Required Process Account Quotas ............... 2-22 2.10.6 Required Processes ............................ 2-23 2.11 Registering the ABS Licenses..................... 2-24 2.12 Installing POLYCENTER Scheduler.................. 2-28 2.12.1 Sample Installation For VSCHED_E09B02 For a VAX System......................................... 2-28 2.12.2 Sample Installation ASCHED_E01B021 for an Alpha System......................................... 2-31 2.12.3 Sample Installation for ASCHED_E0903B021 for an Alpha System................................... 2-35 2.12.4 Configuring POLYCENTER Scheduler for a Mixed-Architecture OpenVMS Cluster............. 2-38 3 Installing the Software 3.1 Installing the Media and Device Management Software......................................... 3-2 3.1.1 Installing the MDMS Server Software ........... 3-4 3.1.2 Installing the MDMS Client Software ........... 3-9 3.1.3 How to Configure for VAX and Alpha Systems .... 3-11 3.2 MDMS Postinstallation Tasks...................... 3-12 3.2.1 Verifying the MDMS Installation ............... 3-13 3.2.2 Providing Automatic Start Up and Shut Down .... 3-13 3.2.3 Defining Global Symbols for MDMS Users ........ 3-13 iv 3.2.4 Defining the OpenVMS Cluster Alias Name and the Failover Server Nodes.......................... 3-14 3.2.5 Defining a Network Object on an OpenVMS Cluster........................................ 3-14 3.2.6 Configuring MDMS for an Automated Tape Library System......................................... 3-17 3.2.6.1 Configure MDMS.............................. 3-17 3.2.6.2 Test the MDMS Configuration................. 3-18 3.2.7 Configuring MDMS for a Media Loader ........... 3-20 3.2.7.1 Configure MDMS.............................. 3-20 3.2.7.2 Test the MDMS Configuration................. 3-22 3.2.8 Configuring for an Operator Attended Drive .... 3-23 3.2.8.1 Configure MDMS.............................. 3-24 3.2.8.2 Test the MDMS Configuration................. 3-25 3.2.9 Configuring Remote Tape or Optical Drives ..... 3-25 3.2.9.1 On The System Where the Tape or Optical Drive Resides............................... 3-26 3.2.9.2 On The System Where the Data Resides........ 3-27 3.3 Installing the ABS Software...................... 3-28 3.3.1 Installing the ABS Server Software ............ 3-29 3.3.2 Installing ABS in a Mixed-Architecture OpenVMS Cluster........................................ 3-38 3.3.3 Installing the ABS OpenVMS Client Software .... 3-42 3.3.4 Installing and Configuring ABS NT Clients ..... 3-44 3.3.5 Configuring ABS UNIX Clients .................. 3-47 3.3.5.1 Modifying the Appropriate UNIX Files........ 3-48 3.3.5.2 Transferring the UNIX Backup Agent Sources.. 3-50 3.3.5.3 Building the UNIX Executables............... 3-52 3.3.5.4 Building the tar Executable................. 3-52 3.3.5.5 Building the gzip Executable................ 3-54 3.3.6 Authorizing NT and UNIX Clients ............... 3-56 3.4 ABS Postinstallation Tasks....................... 3-57 3.4.1 Verifying the ABS Installation ................ 3-57 3.4.2 Providing Automatic Start Up and Shut Down .... 3-58 3.4.3 Meeting OpenVMS Cluster Requirements .......... 3-58 3.4.4 Granting the Appropriate ABS Access Right Identifiers.................................... 3-59 3.4.4.1 Enabling an Access Rights Identifier........ 3-60 3.4.4.2 Revoking An Access Rights Identifier........ 3-60 3.4.5 Modifying ABS Default Policy Objects .......... 3-60 3.4.5.1 Default Policy Object Attributes............ 3-61 3.4.5.2 Modifying Default Policy Objects............ 3-61 v 3.4.6 Performing a Backup, Lookup, and Restore Operation...................................... 3-62 4 Performing Postinstallation Tasks 4.1 Adding New Media into the Media Environment...... 4-1 4.1.1 Adding Media for Automated Media Libraries .... 4-1 4.1.2 Adding Media for Media Loaders ................ 4-3 4.1.3 Adding Media for Operator Attended Drives ..... 4-4 A Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File........ A-8 A.2 MDMS Client Installation Example Log File........ A-15 B Examples of Authorizing NT and UNIX Clients B.1 Adding Client Licenses........................... B-1 B.2 Modifying Client Licenses........................ B-3 B.3 Showing Client Licenses.......................... B-4 B.4 Removing Client Licenses......................... B-4 C Files and Logical Names C.1 ABS File Names.................................. C-1 C.2 MDMS File Names.................................. C-5 C.3 ABS Logical Names............................... C-13 C.4 MDMS Logical Names............................... C-14 Glossary Index Examples 3-1 Transferring the Backup Agent Sources ......... 3-51 B-1 Adding Client Licenses ........................ B-1 B-2 Modifying Client Licenses ..................... B-3 B-3 Showing Client Licenses ....................... B-4 B-4 Removing Client Licenses ...................... B-4 C-1 Sample List of LNM$SLS$VALUES Entries ......... C-18 vi Tables 2-1 Preinstallation Tasks For a New ABS Installation................................... 2-1 2-2 Preinstallation Tasks For An Upgrade ABS Installation................................... 2-3 2-3 Example Installation Worksheet ................ 2-9 2-4 Installation Worksheet ........................ 2-9 2-5 Required Disk Space ........................... 2-17 2-6 Required Software ............................. 2-19 2-7 Optional Software ............................. 2-19 2-8 System Parameter Values-Minimum Requirements .. 2-21 2-9 Process Account Quotas for the Installing Account........................................ 2-22 2-10 How to Start DECnet and OpenVMS Queue Manager........................................ 2-24 2-11 How to Register Your Licenses Using the LICENSE REGISTER Command............................... 2-25 2-12 How to Register Your Licenses Using VMSLICENSE.COM................................. 2-27 2-13 Configuring POLYCENTER Scheduler for a Mixed-Architecture OpenVMS Cluster............. 2-38 3-1 Stages of Installing MDMS ..................... 3-3 3-2 How to Install the MDMS Software .............. 3-5 3-3 How to Install the MDMS Client Software ....... 3-10 3-4 How to Configure in a Mixed Architecture OpenVMS Cluster System......................... 3-11 3-5 Comparing Logical Definitions Between VAX and Alpha Systems.................................. 3-12 3-6 How to Define the SLS$DBX NCP Object .......... 3-14 3-7 Enabling Remote Drive Selection ............... 3-26 3-8 Stages of Installing the ABS Software ......... 3-29 3-9 How to Install the ABS Software ............... 3-30 3-10 Installing ABS in a Mixed-Architecture OpenVMS Custer......................................... 3-39 3-11 Installing and Configuring the ABS OpenVMS Client Software................................ 3-43 3-12 Stages of Installing and Configuring an ABS NT Client......................................... 3-45 3-13 Installing and Configuring an NT Client ....... 3-46 vii 3-14 Stages of Configuring a ABS UNIX Client ....... 3-48 3-15 Modifying the Appropriate UNIX Files .......... 3-49 3-16 Authorizing NT or UNIX Client Nodes ........... 3-56 3-17 Default Policy Objects ........................ 3-60 C-1 ABS Files Installed .......................... C-1 C-2 MDMS Files Installed .......................... C-6 C-3 ABS Logical Names ............................ C-13 C-4 MDMS Logical Names ............................ C-15 viii _________________________________________________________________ Preface This document contains the following information: o Preinstallation decisions o Preinstallation tasks o Installation procedures o Postinstallation tasks o Sample installation procedures o File names and logical names produced by the installation procedure Intended Audience This Installation Guide is written for experienced OpenVMS, UNIX, and NT system managers; it should be used in conjuction with Introduction to OpenVMS System Management. Conventions The following conventions are used in this guide: ___________________________________________________________ Convention__Description____________________________________ { } In format command descriptions, braces indicate required elements. You must include one of the elements. [ ] Square brackets show optional elements in command syntax. You can omit these elements if you wish to use the default response. vii ___________________________________________________________ Convention__Description____________________________________ . . . Horizontal ellipsis points indicate the omission of information from a sentence or paragraph that is not important to the topic being discussed. Vertical ellipsis points indicate the omission . of information from an example or command . format. The information has been omitted . because it is not important to the topic being discussed. boldface Boldface type in text indicates the first type instance of terms defined in the Glossary or in text. italic Italic type emphasizes important information, type indicates variables, indicates complete titles of manuals, and indicates parameters for system information. Starting This type font denotes system response, user test . . . input, and examples. Ctrl/x Hold down the key labeled Ctrl (Control) and the specified key simultaneously (such as Ctrl /Z). PF1 x The key sequence PF1 x indicates that you press and release the PF1 key, and then you press and release another key (indicated here by x). n A lowercase italic n indicates 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 italic x indicates the generic use of a letter. For example, xxx indicates any ____________combination_of_three_alphabetic_characters.____ Related Products The following related products are mentioned in this document: viii ___________________________________________________________ Product_______Description__________________________________ ABS ABS refers to Archive/Backup System for OpenVMS[TM] software. ABS OMT ABS OMT refers to Archive/Backup System for OpenVMS Management Tools[TM] software. HSM HSM refers to HSM for OpenVMS software. MDMS MDMS refers to Media and Device Management Services for OpenVMS software. OpenVMS Refers to the OpenVMS operating system. SMF SMF refers to Sequential Media Filesystem for OpenVMS software. SLS SLS refers to Storage Library System for ______________OpenVMS_software.____________________________ Associated Documents The following documents are associated with Archive/Backup System for OpenVMS. o Archive/Backup System for OpenVMS Guide to Operations o Archive/Backup System for OpenVMS Reference Guide o Archive/Backup System for OpenVMS Management Tools User's Guide o Archive/Backup System for OpenVMS Management Tools Installation Guide o Media and Device Management Services for OpenVMS Guide to Operations o Storage Library System for OpenVMS Guide to Backup and Restore Operations ix 1 _________________________________________________________________ Welcome to ABS ________________________ Note ________________________ If you are installing ABS for the first time, it is essential that you review the information presented in this chapter. If you are an existing ABS user and you are upgrading your version of ABS, you may want skip to Chapter 2. ______________________________________________________ Welcome to Archive/Backup System for OpenVMS (ABS) Version 2.1B. Because you have selected ABS to help you manage your data safety needs (archive and backup operations), you have a hardware and software environment (subsequently referred to as storage environment) that contains a set of common elements. Your storage environment also contains very specific or unique elements. The information presented in this chapter is intended to give you an "overall picture" of a typical storage environment, and to explain how ABS compliments that environment. 1.1 What Do All Storage Environments Have In Common? All storage environments that plan to implement ABS have the following common hardware and software: o OpenVMS[TM] VAX[TM] or Alpha systems o OpenVMS software Version 6.1 or higher for VAX and Alpha systems o Disk devices for online storage/transactions o DECnet[TM] Phase IV or DECnet-Plus o Tape drives Welcome to ABS 1-1 Welcome to ABS 1.1 What Do All Storage Environments Have In Common? o Removable media that is compatible with the tape drives for storing archived and backed up data 1.2 What Makes a Storage Environment Unique? All storage environments have some or all of the following characteristics that make them unique: o Mixed architecture (a combination of VAX and Alpha systems) o Heterogeneous client systems (OpenVMS, NT, UNIX) o Types of tape drives (TLZ06, TZ877, and so forth) o Types of robotic devices (jukeboxes or gravity-fed loaders) o Types of tape drive connections (direct-connect SCSI or controller-connected) o Location of tape drives (remote or local) o Number of disks o Number of tape drives 1.3 How Does ABS Compliment Your Storage Environment? ABS enables you to implement a backup management policy that takes advantage of your storage environment. Because ABS is layered on the Media and Device Management Services for OpenVMS (MDMS) software, ABS uses MDMS to manage media and devices for its archive, backup, and restore operations. Once MDMS is installed and configured to match your site-specific storage environment, ABS can provide data safety (archive and backup operations) in a " set and forget" fashion, taking advantage of a managed media and device environment. The following list describes the policy object that are components of the ABS software. These policy objects enable you to implement a backup management policy that compliments your storage management environment: 1-2 Welcome to ABS Welcome to ABS 1.3 How Does ABS Compliment Your Storage Environment? o Storage classes-Storage classes define such characteristics as the type of media and associated drives to use for backup operations. o Execution environments-Execution environments define how to execute archive, backup, and restore operations and define such characteristics as who can use the execution environment, default notification methods, and user profile attributes for save requests. o Save requests-Save requests enable you to schedule automatic, repetative backup operations that define what data to save, where to save the data (storage class), and how to save the data (execution environment). o Restore requests-Restore requests enable you to easily restore data that was saved using ABS. o Catalogs-Catalog objects contain history information about ABS backup operations. These catalogs are a key component to finding and restoring data that was saved using ABS. ABS provides default storage classes, execution environments, and catalogs when the installation procedure has sucessfully completed. ABS enables you to modify those default policy objects so that your backup management policy meets your site-specific requirements. ABS also allows you to create additional policy objects and to delete policy objects when needed. Figure 1-3 illustrates how ABS compliments your storage management environment. 1.4 What Is The Purpose of a Managed Media and Device Environment? The purpose of a managed media and device environment is to maintain a logical view of the physical elements of your storage environment to serve your nearline and offline data storage needs. A managed media and device environment defines the media and defines the drives that can use the media. It also defines the locations where media is stored, the locations of the drives that are compatible with the media, and the policy that governs the use of media. Welcome to ABS 1-3 Welcome to ABS 1.4 What Is The Purpose of a Managed Media and Device Environment? The following list summarizes the characteristics of the managed media and device environment: o Media is defined as a media type in MDMS. Media type definitions are stored in the MDMS volume configuration database. All managed media are known in terms of type, location, capability, availability, and authorization (who can use that media). Before you can use media in your managed storage environment, you must add the media to the MDMS volume configuration database, and initialize the media for use. Once this is done, the media is known as a "volume." ABS recognizes these media type definitions, and depending upon which media type your storage policy uses, performs the backup operation using the appropriate media type and tape drives. o Tape drive definitions also are stored in MDMS. Tape drives are used to serve the volumes known to MDMS. The MDMS software maintains a logical link between the volumes and the compatible tape drives, both in terms of physical and logical boundaries. Volumes and tape drives can be managed logically from locations miles away from where they are physically located. ABS depends upon MDMS to select the appropriate tape drives determined by the media type. ABS storage classes associate these logical connections. o The MDMS software enables you to set the default criteria for moving and recycling volumes. This criteria includes rotation between onsite and offsite locations for safekeeping of the volumes, and the schedule that moves the volume through its lifecycle (retention, use, and reuse). ABS enables you to set the retention criteria for data saved on volumes, while MDMS enables you to define when to move or recyle volumes. ________________________ Note ________________________ ABS does not have its own method of determining whether a volume needs to be moved offsite or returned to onsite. MDMS currently provides this capability. ______________________________________________________ 1-4 Welcome to ABS Welcome to ABS 1.5 Mixed Architecture Environments 1.5 Mixed Architecture Environments _ Before You Install your Storage Management Software _ If you are planning to install ABS software in a mixed architecture OpenVMS Cluster, you should understand the configuration issues explained in this section. If you do not consider these configuration issues, you could spend considerable time deleting and editing files, and reinstalling the software. ______________________________________________________ This section addresses the characteristics of a mixed architecture environment and describes some fundamental approaches to installing and configuring your software to run in it. The following list identifies the topics and their purposes o Section 1.5.1 defines the mixed architecture environment and discusses ways in which they can come about, change, then disappear. Each of these occurrences requires some consideration about how to configure your software. o Section 1.5.2 lists the guiding principles that require you to make special considerations for mixed architecture implementation, and what these principles mean to you. o Section 1.5.3 describes three possible approaches to implementing a mixed architecture environment. o Section 1.5.4 explains why the documentation includes procedures for a specific approach. If you cannot use the documented procedures, you should decide on an approach before you begin installation. 1.5.1 Mixed Architecture Environments A mixed architecture OpenVMS Cluster includes at least one VAX system and at least one Alpha system. Creating_a_Mixed_Architecture_Configuration: If you add an Alpha system to a homogenous VAX OpenVMS Cluster, or if you are currently running a homogenous Alpha OpenVMS Cluster and inherit a VAX system, you will have a mixed architecture environment. Welcome to ABS 1-5 Welcome to ABS 1.5 Mixed Architecture Environments Before you integrate the Alpha or VAX node into the system, you should decide an approach to take for handling mixed architecture issues. Operating_a_Mixed_Architecture_Configuration: If you are currently operating a mixed architecture environment, and you want to add a VAX system or an Alpha system you must integrate it into your current configuration consistently with your other applications. You should understand the particular requirements of any new application you introduce into a mixed architecture OpenVMS Cluster. Dissolving_a_Mixed_Architecture_Configuration: If you remove the last VAX or Alpha system, leaving a homogenous OpenVMS Cluster, you should remove any aspects of configuration that accounted for the heterogenous nature of the mixed architecture system. This includes (but is not limited to) removing startup files, duplicate directory structures, and logical tables. 1.5.2 Principles Guiding Mixed Architecture Configuration Hardware_Limitations: VAX systems cannot execute image files compiled on an Alpha system, and Alpha systems cannot execute image files compiled on a VAX system. Other types of files cannot be shared, including object code files (.OBJ), and user interface description files (.UID). You must place files that cannot be shared in different locations: VAX files accessible only to VAX OpenVMS Cluster nodes, and Alpha files accessible only to Alpha OpenVMS Cluster nodes. What_it_Means: Data files, in most cases, must be shared between OpenVMS Cluster nodes. You should place all shared files in directories accessible by both VAX and Alpha OpenVMS Cluster nodes. Logical names, that reference files which cannot be shared, or the directories in which they reside, must be defined differently on VAX and Alpha systems. 1-6 Welcome to ABS Welcome to ABS 1.5 Mixed Architecture Environments Files that assign logical name values must therefore be architecture specific. Such files may either reside on node-specific disks or shared only among OpenVMS Cluster nodes of the same hardware architecture. 1.5.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster This section describes three approaches to configuring applications to run in a mixed architecture OpenVMS Cluster. The one you choose depends on your existing configuration, and the needs of the particular application you are installing. These approaches are given as examples only. You should decide which you want to implement based on your own situation and style of system management. All of these approaches have two aspects in common: o All shared files reside in one location o All files that cannot be shared reside in separate locations 1.5.3.1 Separate Disk Configuration These characteristics describe the separate disk configuration: o Product directories are installed on two separate disks. o One of the product directories is a complete installation containing all data (and other shared) files, and all executable (and other nonshared) files for either VAX or Alpha systems. o The other of the product directories is a partial product installation, with only those directories that contain either Alpha or VAX system executables and other nonshared files. o The systems using the disk with the complete installation uses logicals that normally reference the product executables and shared files. o The systems using the disk with only the nonshared files use normal product logical definitions to point to shared files and directories. System logicals that point to nonshared files are assigned to the specific device, directory and/or file names. Welcome to ABS 1-7 Welcome to ABS 1.5 Mixed Architecture Environments 1.5.3.2 Separate Root Configuration These characteristics describe the separate root configuration: o Product directories are installed on the same disk, but at different root locations. o One of the product directories is a complete installation containing all data (and other shared files), and all executable (and other nonshared) files for either VAX or Alpha systems. o The other of the product directories is a partial product installation, with only those subdirectories that contain either Alpha or VAX system executables and other nonshared files. o The systems using the directory with the complete installation uses logicals that normally reference the product executables and shared files. o The systems using the directory with only the nonshared files use normal product logical definitions to point to shared files and directories. System logicals that point to nonshared files are assigned to the specific device, directory and/or file names. 1.5.3.3 Separate Subdirectory Configuration These characteristics describe the separate directory configuration: o Product directories are installed on the same disk, and under the same root. o Any directory which would normally contain the nonshared files (under a single architecture installation) has two subdirectories: one for VAX system nonshared files, and one for Alpha system nonshared files. o Logicals that reference nonshared files are assigned search list values that point to the directories which holds shared files, and to the architecture specific subdirectories holding nonshared files. 1-8 Welcome to ABS Welcome to ABS 1.5 Mixed Architecture Environments 1.5.4 Implementation Specific Approach This document includes specific procedures for a recommended approach based on current product configuration and the behavior of the installation software with respect to its use of logical definitions during upgrades. If the recommended approach is inconsistent with the way you currently manage your system, you should decide on a different approach before you begin your installation procedures. Welcome to ABS 1-9 2 _________________________________________________________________ Meeting ABS Installation Requirements To ready your OpenVMS system for the either the ABS server or client software installation procedure, you must perform certain tasks and meet certain requirements. If you are installing ABS for the first time, Table 2-1 shows the tasks you must perform before installing ABS. If you are upgrading your version of ABS, refer to Table 2-2. Table_2-1_Preinstallation_Tasks_For_a_New_ABS_Installation_______ Step_Action______________________________________________________ 1 Decide on which system and disk to install the ABS and MDMS server software. You must make this decision before you can perform the remaining preinstallation tasks. Refer to Sections 2.1 and 2.3 for information about the ABS and MDMS server software. Use the worksheet provided in Table 2-3 to record your configuration. 2 Decide on which systems and disks to install the ABS and MDMS client software. Refer to Sections 2.2 and 2.4 for information about the ABS and MDMS client software. Use the worksheet provided in Table 2-3 to record your configuration. (continued on next page) Meeting ABS Installation Requirements 2-1 Meeting ABS Installation Requirements Table 2-1 (Cont.) Preinstallation Tasks For a New ABS __________________Installation___________________________________ Step_Action______________________________________________________ 3 Configure your hardware. Before you can use the ABS software, you must first install and test your hardware configuration. It is recommended that you do this prior to installing the ABS and MDMS software. These tasks are described in Section 2.7. Note: The Media Robot Utility (MRU) software provides you with the ability to control the operation of an automated library system or a media loader system without having to access front panel controls on the system. MRU is especially useful for installing, configuring, and testing the operation of a these types of system. DIGITAL distributes the MRU software with its newest libraries and loaders. If you have recently purchased and installed a one of these systems, you already should have installed the MRU software package. If you are using an earlier DIGITAL library or loader and would like to use MRU software, contact your DIGITAL sales representative. 4 Log in to the SYSTEM account and enable all privileges. Most system managers install software from the system account. See Section 2.8 for the privileges required to install ABS Version 2.1B. 5 Perform a system backup operation. DIGITAL 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. 6 Verify the OpenVMS operating system subclasses. Subclasses are provided in the OpenVMS save set that contains support for the OpenVMS operating system. Section 2.9 lists the OpenVMS operating system subclasses required to install ABS Version 2.1B. (continued on next page) 2-2 Meeting ABS Installation Requirements Meeting ABS Installation Requirements Table 2-1 (Cont.) Preinstallation Tasks For a New ABS __________________Installation___________________________________ Step_Action______________________________________________________ 7 See Section 2.10 to verify the following requirements: o Hardware and software requirements o System parameters o Account process quotas o System processes 8 Register the ABS licenses as described in Section 2.11. 9 Install POLYCENTER Scheduler. ABS requires that POLYCENTER Scheduler be installed and active on your system before installing ABS. The ABS installation procedure will fail if POLYCENTER Scheduler is not currently running. If you do not have Scheduler (purchased separately) installed on your system, ABS Version 2.1B provides the full POLYCENTER Scheduler Version 2.1B kits, ASCHED_E01B021 and ASCHED_ E0903B021, as part of the ABS software kit. See Section 2.12 _____for_instructions.___________________________________________ Table_2-2_Preinstallation_Tasks_For_An_Upgrade_ABS_Installation__ Step_Action______________________________________________________ 1 If you have new tape drives that you want to add to your current storage environment, follow the instructions provided in Section 2.7. It is recommended that you do this prior to upgrading the ABS or MDMS software. 2 Log in to the SYSTEM account and enable all privileges. Most system managers install software from the system account. See Section 2.8 for the privileges required to install ABS Version 2.1B. (continued on next page) Meeting ABS Installation Requirements 2-3 Meeting ABS Installation Requirements Table 2-2 (Cont.) Preinstallation Tasks For An Upgrade ABS __________________Installation___________________________________ Step_Action______________________________________________________ 3 Perform a system backup operation. DIGITAL 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. 4 Shutdown ABS. If you are upgrading ABS and it is currently running, shut down ABS by entering the following commands on all nodes in the OpenVMS Cluster system: $ @SYS$MANAGER:ABS$SHUTDOWN.COM 5 Verify the OpenVMS operating system subclasses. Subclasses are provided in the OpenVMS save set that contains support for the OpenVMS operating system. Section 2.9 lists the OpenVMS operating system subclasses required to install ABS Version 2.1B. 6 See Section 2.10 to verify the following requirements: o Hardware and software requirements o System parameters o Account process quotas o System processes _________________________________________________________________ 2.1 Deciding Where to Install the ABS Server Software ABS is designed upon a client-server technology. Before installing the ABS Version 2.1B software, decide which OpenVMS node or OpenVMS Cluster will contain the ABS server software. The ABS server software is installed on an OpenVMS node or OpenVMS Cluster system and provides the policy database for itself and for any ABS client nodes connected to it. The ABS server software makes the policy database available to all ABS clients. 2-4 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.1 Deciding Where to Install the ABS Server Software _____________________ Requirement _____________________ You must install the ABS server software on at least one OpenVMS node or OpenVMS Cluster system. ______________________________________________________ Although the installation procedure does not have separate kits for the client and server software, the ABS server is determined by the placement of the ABS policy engine. During the installation procedure, you will be prompted to supply an OpenVMS Cluster alias name or an OpenVMS node name (or names) where you want the ABS policy engine to reside. This OpenVMS node or OpenVMS Cluster becomes the ABS server. 2.2 Deciding Where To Install the ABS Client Software OpenVMS_clients: Install the ABS OpenVMS client software on any node that can communicate with the ABS server and for which you want to create ABS backup operations. The ABS OpenVMS client node can communicate with an ABS server node using the DECnet software. When an ABS client node needs to perform an ABS operation, the ABS client node communicates with the ABS server, retrieves policy information, updates the ABS policy object database, and then relinquishes its communications with the ABS server when the operation has completed. NT_clients: For NT clients, you must install the ABS NT client software provided in the ABS software kit. You must also authorize access for NT clients on the ABS server node. Instructions for these tasks are described in 3.3.4 and Section 3.3.6. UNIX_clients: UNIX clients do not require a separate client installation. However, you must transfer the GNUtar files provided by the ABS software to the UNIX client system, and then you must build the executable files on the UNIX client system. Also, you must authorize access for UNIX clients on the ABS server node. Instructions for these tasks are described in 3.3.5 and 3.3.6. Meeting ABS Installation Requirements 2-5 Meeting ABS Installation Requirements 2.2 Deciding Where To Install the ABS Client Software Both NT and UNIX clients have their backup operations occur on the ABS server node and the ABS server communicates with the NT or UNIX client system for data transfer and control. ________________________ Note ________________________ Given 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.3 Deciding Where to Install MDMS Server Software ABS requires the Media and Device Management Services for OpenVMS (MDMS) software to be installed before you install the ABS software. If you plan to use tape drives or robotic devices for your archive, backup, and restore operations, MDMS supports ABS by enabling you to configure your tape drives and robotic devices, both local and remote, so that ABS can use them for its backup and restore operations. Install the MDMS server software on the same OpenVMS node or OpenVMS Cluster system where you will be installing the ABS server software, and also typically on the same disk device as the ABS server software. MDMS provides media management services for itself and for any MDMS client nodes connected to it. The MDMS server software provides the MDMS volume and magazine databases. The volume database contains definitions of all removable media known to the MDMS software, and the associated tape drive definitions, such as if the tape drive is local or remote to the MDMS server. It also contains information about volume locations and volume pool access authorization. The MDMS server software updates the MDMS volume and magazine databases when any transactions are performed against the volumes. _____________________ Requirement _____________________ You must install the MDMS server software on at least one OpenVMS node or OpenVMS Cluster[TM] system in 2-6 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.3 Deciding Where to Install MDMS Server Software the network if you plan to use tape drives or robotic devices for your ABS backup operations. ______________________________________________________ 2.4 Deciding Where To Install The MDMS Client Software The MDMS client software must be installed on all OpenVMS nodes that have the ABS OpenVMS client software. The MDMS client node can communicate with an MDMS server node using the DECnet software. When an MDMS client node needs to perform an MDMS operation, the MDMS client node communicates with the MDMS server node. The MDMS server node updates the volume and magazine databases, and the MDMS client node relinquishes its communications with the MDMS server node. Each MDMS client node must have a DECnet connection to an MDMS server node. ________________________ Note ________________________ Given you have the appropriate amount of licenses, any number of MDMS client nodes may be connected to a single MDMS server node, provided you have adequate resources available. ______________________________________________________ Figure 2-1 illustrates a typcial client-server configuration. 2.5 Recommended Installation In the event of a disaster situation, it is essential to know where to install ABS and its dependent products so that you can recover the affected system as quickly as possible. To ease the recovery process in the event of a disaster situation, review this information to understand the most efficient way to install ABS, MDMS, and any dependent layered products. ________________________ Note ________________________ The information provided is only for OpenVMS VAX or Alpha systems. If you have other types of systems to Meeting ABS Installation Requirements 2-7 Meeting ABS Installation Requirements 2.5 Recommended Installation consider, see the platform-specific documentation for recovery information. ______________________________________________________ Consider the following important guidelines: o You should install the ABS server software and the MDMS server software on one disk in a system. This disk should also contain POLYCENTER Scheduler. This disk could be the system disk, or another disk dedicated to ABS and its dependent layered products. The advantage of placing ABS and its dependent layered products on the system disk is that a less complicated restore process is required. However, the system disk then requires more space for ABS catalogs, the MDMS database, and so forth. o This disk should be dedicated to ABS and its dependent layered products; not shared with other interactive processes that could impede the performance of ABS. o The system that contains this disk must have access to a tape device compatible with the media that will contain the save sets for this disk. Figure 2-2 illustrates the recommended installation. Before you begin the installation procedure, use the worksheets provided in Section 2.6 to identify which OpenVMS system and disk device will contain the ABS and MDMS server software, and POLYCENTER Scheduler. 2.6 Using the Installation Worksheets To help you with the installation procedure, the worksheet in Table 2-4 provides a work area to help you identify where you are going to install the ABS and MDMS OpenVMS server and client software. Table 2-3 provides an example of how to use the worksheet in Table 2-4. 2-8 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.6 Using the Installation Worksheets Table_2-3_Example_Installation_Worksheet_________________________ Node Name Disk Support a Support Server or Cluster Device Remote Tape a Remote /Client_______Name________Name________Device?__________Backup?___ ABS_Server NODESV DISK$USER1: MDMS_server NODESV DISK$USER1: No Yes ABS/MDMS_clien_ODECA DISK$USER1: Yes No _________________________________________________________________ Table_2-4_Installation_Worksheet_________________________________ Node Name Disk Support a Support Server or Cluster Device Remote Tape a Remote /Client_______Name________Name________Device?__________Backup?___ ABS_server __________ __________ _______________ __________ MDMS_server __________ __________ _______________ __________ ABS/MDMS_clien__________ __________ _______________ __________ __________ __________ _______________ __________ __________ __________ _______________ __________ __________ __________ _______________ __________ ABS_NT_client __________ __________ __________ __________ __________ __________ __________ __________ ABS_UNIX_clien__________ __________ __________ __________ (continued on next page) Meeting ABS Installation Requirements 2-9 Meeting ABS Installation Requirements 2.6 Using the Installation Worksheets Table_2-4_(Cont.)_Installation_Worksheet_________________________ Node Name Disk Support a Support Server or Cluster Device Remote Tape a Remote /Client_______Name________Name________Device?__________Backup?___ __________ __________ __________ __________ _________________________________________________________________ 2.7 Configuring Your Hardware This section describes how to configure automated media libraries, media loaders, and operator attended drives to enable MDMS to provide a managed media environment. This means installing, connecting, and testing the tape drives. After you have installed ABS and MDMS, you can then configure MDMS to manage these drives. Configuring MDMS to manage media and drives is described in Chapter 3. Each procedure depends on the kind of tape drive that you plan to use. Use the procedures appropriate for the tape drives you plan to include in the managed media environment: o For an automated media library, refer to Section 2.7.1. o For a media loader, refer to Section 2.7.2. o For an operator attended drvie, refer to Section 2.7.3. 2.7.1 Hardware Configuration For an Automated Media Library The following procedure applies to the installation and testing of an automated media library. Configuration and testing of MDMS to manage an automated media library is described in Chapter 4. 2-10 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.7 Configuring Your Hardware 2.7.1.1 Hardware Installation During this procedure, refer to the drive-specific hardware installation procedure information for details. The following procedure provides only the basic steps necessary to later configure MDMS against the drive: 1. Install and connect the hardware. Apply power to the drives. 2. If you are using an HSx controller, configure it to allow the OpenVMS system to communicate with the drives. 3. Make note of the drive name after you complete your connection procedure. You will need this, especially if you are going to use the Media Robot Utility software. 2.7.1.2 Test the Hardware With an automated media library, use a utility such as the Media Robot Utility (MRU) or use the front panel of the drive and the OpenVMS system to test the connection between the host and drive. Use the following procedure to test the hardware connection between the automated tape library and the OpenVMS system: 1. Verify the robot device name and the drive names located in the automatic tape library. Issue the DCL SHOW DEVICE command and/or the ROBOT SHOW ROBOT command. If there is a problem with drive name or the connection, it becomes apparent here. $ SHOW DEVICE [drive-name[:]] The following is the StorageWorks Media Robot Utility command for examining the robot: $ ROBOT SHOW ROBOT [robot_name] If you have problems with the drive name, refer to the OpenVMS system and drive-specific hardware documentation for remedial action. 2. Place a volume in the robot. 3. Inject the volume through a port on the robot by using the front panel controls or, if you are using StorageWorks Media Robot Utility, by issuing the ROBOT INJECT command: Meeting ABS Installation Requirements 2-11 Meeting ABS Installation Requirements 2.7 Configuring Your Hardware $ ROBOT INJECT [PORT port_number] SLOT slot_number [ROBOT robot_name] Alternately, you can expose the internal storage slots and place the volume directly into the robot. You also should consider placing one or more cleaning volumes into the robot at this time. 4. Load the volume into the drive by using the front panel controls or, if you are using MRU, by issuing the ROBOT SHOW and ROBOT LOAD command: $ ROBOT SHOW SLOT 0-n [ROBOT robot_name] $ ROBOT LOAD SLOT slot_num [ROBOT robot_name] 5. After loading the volume, check the OpenVMS system connection to the drive by mounting and dismounting the volume. Mount the volume foreign: $ MOUNT/FOREIGN/NOASSIST drive_name[:] Dismount the volume: $ DISMOUNT drive_name[:] 6. Remove the volume from the drive by using the front panel controls or, if you are using MRU, by issuing the ROBOT UNLOAD command: $ ROBOT UNLOAD SLOT slot_number [ROBOT robot_name] After having completed this procedure, the volume remains in the robot but is not loaded in the drive. 2.7.2 Hardware Configuration for a Media Loader The following procedure applies to the installation and testing of a media loader. Configuration and testing of MDMS to manage a media loader is described in Chapter 4. 2.7.2.1 Hardware Installation During this procedure, refer to the drive-specific hardware installation information for details. This procedure provides only the basic steps necessary to later configure MDMS against the drive: 1. Install and connect the hardware. Apply power to the drives. 2. If you are using an HSx controller, configure it to allow the OpenVMS system to communicate with the drives. 2-12 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.7 Configuring Your Hardware 3. Make note of the drive name after you complete your connection procedure. You will need this, especially if you are going to use the Media Robot Utility software. 2.7.2.2 Test the Hardware With a media loader, use a utility such as the Media Robot Utility (MRU) or use the front panel of the drive and the OpenVMS system to test the connection between the OpenVMS system and drive. ________________________ Note ________________________ Before you perform this procedure, you must have a compatible, initialized volume in the robot. Use this initialized volume to perform this test. To initialize media, refer to Section 4.1.2. ______________________________________________________ Use the following procedure to test the hardware connection between the tape loader and the OpenVMS system: 1. Verify the changer device name and the drive names. Issue the DCL SHOW DEVICE command and/or the ROBOT SHOW ROBOT command. If there is a problem with drive name or the connection, it becomes apparent here: $ SHOW DEVICE [drive-name[:]] The following is the MRU command for examining the robot: $ ROBOT SHOW ROBOT [robot_name] If you have problems with the drive name, refer to the drive-specific hardware documentation for remedial action. 2. Place a volume in a magazine; place the magazine into the drive. 3. Load a volume into the robot by using the front panel controls or, if you are using MRU, by issuing the ROBOT SHOW and ROBOT LOAD command: $ ROBOT SHOW SLOT 0-n [ROBOT robot_name] $ ROBOT LOAD SLOT slot_num [ROBOT robot_name] Meeting ABS Installation Requirements 2-13 Meeting ABS Installation Requirements 2.7 Configuring Your Hardware 4. After loading the volume, check the OpenVMS system connection to the drive by mounting and dismounting the volume. Mount the volume with the OpenVMS MOUNT/FOREIGN command: $ MOUNT/FOREIGN/NOASSIST drive_name[:] Dismount the volume with the OpenVMS DISMOUNT command. Be sure to include the /NOUNLOAD qualifier: $ DISMOUNT/NOUNLOAD drive_name[:] 5. Remove the volume from the drive by using the front panel controls or, if you are using MRU, by issuing the ROBOT UNLOAD command. $ ROBOT UNLOAD SLOT slot_number [ROBOT robot_name] After having completed this procedure, the magazine with the volume remains in the media loader, but it is not loaded in the drive. 2.7.3 Hardware Configuration for an Operator Attended Drive This procedure applies to the installation and testing of an operator attended drive. The configuration and testing of MDMS to manage the operator attended drive is described in Chapter 4. 2.7.3.1 Hardware Installation During this procedure, refer to the drive-specific hardware installation information for details. This procedure provides only basic steps necessary to later configure MDMS against the drive: 1. Install and connect the hardware. Apply power to the drive. 2. If you are using an HSx controller, configure it to allow the OpenVMS system to communicate with the drive. 3. Make note of the drive name after you complete your connection procedure. 2-14 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.7 Configuring Your Hardware 2.7.3.2 Test the Hardware Use the following procedure to test the hardware installation and connection with the OpenVMS system: 1. Verify the drive names. Issue the DCL SHOW DEVICE command. If there is a problem with drive name or the connection, it becomes apparent here. $ SHOW DEVICE [drive-name[:]] If you have problems with the drive name, refer to the drive-specific hardware documentation for remedial action. 2. Load a volume into the drive. 3. After loading the volume, check the OpenVMS system connection to the drive by mounting and dismounting the volume. Mount the volume with the OpenVMS MOUNT/FOREIGN command. $ MOUNT/FOREIGN/NOASSIST drive_name[:] Dismount the volume with the OpenVMS DISMOUNT command. $ DISMOUNT drive_name[:] 4. Remove the volume from the drive. 2.8 Required Privileges To install ABS Version 2.1B, log in to the SYSTEM account or to an account that has SETPRV or, at a minimum, has the following privileges enabled: o CMKRNL o WORLD o SYSPRV o TMPMBX o NETMBX Note that VMSINSTAL turns off BYPASS privilege at the start of the installation. Meeting ABS Installation Requirements 2-15 Meeting ABS Installation Requirements 2.9 Required OpenVMS Operating System Subclasses 2.9 Required OpenVMS Operating System Subclasses The 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, and those subclasses are provided in the OpenVMS Save Set C: o Programming support o Utilities o System programming environment o Secure user's environment o Network support How_to_verify: For information about verifying these components, refer to either the OpenVMS VAX Installation Procedures or OpenVMS Alpha Installation Procedures. 2.10 Hardware, Software, and System Requirements To make sure that your system is ready for the installation, verify that your system meets the following requirements: o Hardware o Software o System parameters o Process account quotas o Processes 2.10.1 Required Hardware To install the ABS Version 2.1B software, you must meet the following minimum hardware requirements: o A VAX[TM] system, a MicroVAX[TM] system, a VAXstation[TM], or an Alpha system. o Four megabytes of memory for VAX systems, or 16 megabytes of memory for Alpha systems. 2-16 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements o One or more tape drives if you plan to back up your data to removable media. Refer to Section 2.7 for instructions about configuring your hardware. o One disk, such as a DIGITAL RD-[TM] or RZ-[TM] series disk. o Adequate disk space. Refer to Table 2-5 to make sure there is adequate disk space to install ABS. Verify that there are enough free blocks on the disk where you are installing the software. If you are providing remote drive support, you must answer yes to the remote drive question during the installation MDMS 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 The Table 2-5 lists the amount of disk spaced required for the installation. Table_2-5_Required_Disk_Space______________________________ IF you are in- Supporting stalling . . . Remote ______________Drives?_____THEN_you_need_._._.______________ MDMS Server Yes 10,800 peak blocks during software installation 8,400 net blocks after installation (permanent) No 10,200 peak blocks during installation 7,800 net blocks after installation (permanent) (continued on next page) Meeting ABS Installation Requirements 2-17 Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements Table_2-5_(Cont.)_Required_Disk_Space______________________ IF you are in- Supporting stalling . . . Remote ______________Drives?_____THEN_you_need_._._.______________ MDMS Client Yes 10,800 peak blocks during software installation 8,400 net blocks after installation (permanent) No 10,200 peak blocks during installation 7,800 net blocks after installation (permanent) ABS Server N/A 50,000 blocks are required during Software the installation procedure 50, 000 blocks are required after installation plus additional blocks for the catalog size requirements ABS Client N/A 50,000 blocks are required during Software the installation procedure 50, 000 blocks are required after installation plus additional blocks for the catalog size __________________________requirements_____________________ 2.10.2 Required Software Table 2-6 lists the software you must have installed on your system before you install ABS Version 2.1B. 2-18 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements Table_2-6_Required_Software______________________________________ Prerequisite Software______________Purpose_______________System_______________ OpenVMS Operating Provides OpenVMS and ABS OpenVMS server System [1] DCL capabilities and ABS OpenVMS client system POLYCENTER Scheduler Provides scheduling ABS OpenVMS server [1] capabilities. and ABS OpenVMS client system Media and Device Provides media and ABS OpenVMS server Management Services device management system and all for OpenVMS [1] support. ABS OpenVMS client systems. DECnet Phase IV or Provides network ABS OpenVMS Server DECnet-Plus for support. and ABS OpenVMS OpenVMS client system [1]_See_the_ABS_Version_2.1B_Software_Product_Description_(SPD)__ for required versions _________________________________________________________________ 2.10.3 Optional Software Table 2-7 describes the optional software you can use with the ABS software. Table_2-7_Optional_Software______________________________________ Optional_Software_____Purpose_______________System_______________ Oracle Rdb for VAX Provides distributed ABS OpenVMS server or Alpha systems [1] database and system multi-streaming capabilities. [1]_See_the_ABS_Version_2.1B_Software_Product_Description_(SPD)__ for required versions (continued on next page) Meeting ABS Installation Requirements 2-19 Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements Table_2-7_(Cont.)_Optional_Software______________________________ Optional_Software_____Purpose_______________System_______________ Note: If you select Oracle Rdb for the ABS policy database, the version of Oracle Rdb that you select must be up and running before you install ABS. Also, the file SYS$LIBRARY:SQL$USER.OLB or SYS$LIBRARY:SQL$USER_n.OLB (where n is version-specific) must pre-exist on your system. If you have Oracle Rdb Version 6.0, you must apply engineering change order (ECO) number 5. Motif for X-Windows Provides graphical ABS OpenVMS server [1] user interface and ABS OpenVMS capabilities. client system DIGITAL TCP/IP Provides network ABS OpenVMS server Services for support for NT and system OpenVMS[1] UNIX clients. C compiler Provides the UNIX client systems ability to build the executable files on UNIX clients eXcursion [1] Provides the ability NT client system to display the graphical user interface (GUI) on NT client systems. DCSC (Digital If you have a The system where Cartridge Server StorageTek Automated the StorageTek silo Component) [1] Cartridge Server resides. (ACS), you must install the DCSC software. [1]_See_the_ABS_Version_2.1B_Software_Product_Description_(SPD)__ for required versions (continued on next page) 2-20 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements Table_2-7_(Cont.)_Optional_Software______________________________ Optional_Software_____Purpose_______________System_______________ Media Robot Utility Provides library The OpenVMS system (MRU) and loader testing, where the robotic diagnostics, and device is physically ______________________control.______________connected.___________ 2.10.4 Required System Parameters To install ABS, the system's parameters must be set to the minimum value or higher. Table 2-8 lists the minimum system parameter values required for the installation. Depending on the kinds of programs and applications running at your site, you may need higher values. Table_2-8_System_Parameter_Values-Minimum_Requirements_____ System_Parameter___________Minimum_Value___________________ DENQLM 300 GBLPAGES[1] 2000 GBLSECTIONS[1] 4 LOCKIBTBL 45000 MENQLM 300 PGFLQUO 10000 PROCSECTCNT 100 TQELM 200 [1]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. ___________________________________________________________ To see the current system parameter values on your system, enter the following command: $ MCR SYSGEN SYSGEN> SHOW/GEN Result: Meeting ABS Installation Requirements 2-21 Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements This command shows the current values of all of the system parameters. If you need to modify one or more of the system parameters, see the following example command: $ MCR SYSGEN SYSGEN> SET GLBPAGES 2000 SYSGEN> WRITE CURRENT SYSGEN> EXIT You must then reboot the system so the changed system parameter values are recognized. More_information: Refer to the OpenVMS System Manager's Manual: Managing System Parameters for detailed information about required system parameters. 2.10.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-9 summarizes the process quotas and the quotas that VMSINSTAL requires to perform the installation. Table_2-9_Process_Account_Quotas_for_the_Installing_Account Account_Quota____Value_____________________________________ ASTLM 200 BIOLM 10000 BYTLM 18000 DIOLM 200 ENQLM 2048 FILLM____________300_______________________________________ To see your current process quotas, enter the following command: $ MCR AUTHORIZE UAF> SHOW SMITH 2-22 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements Result: This command shows all of your process quotas. If you need to increase your process account quotas, see the following example command: $ MCR SYS$SYTEM:AUTHORIZE UAF> MODIFY SMITH ENQLM 2048 UAF> EXIT ________________________ Note ________________________ If you are supporting NT or UNIX clients, to ensure successful save and restore operations, set the quotas to the following values from the ABS OpenVMS server node: ucx> set protocol tcp /quota=(send:250000,receive:250000) 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 the Authorize Utility in the OpenVMS System Management Subkit. 2.10.6 Required Processes Before beginning the installation procedure, check to see that DECnet Phase IV or DECnet-Plus and the OpenVMS Queue Manager are running. To see if these processes are active on your system, enter the following command: $ SHOW SYSTEM Meeting ABS Installation Requirements 2-23 Meeting ABS Installation Requirements 2.10 Hardware, Software, and System Requirements OpenVMS V7.1 on node NODE1 8-AUG-1997 13:39:28.23 Uptime 0 23:36:26 Pid Process Name State Pri I/O CPU Page flts Pages . . . 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 If these processes are not active, follow the steps in Table 2-10 to start them. Table_2-10_How_to_Start_DECnet_and_OpenVMS_Queue_Manager___ Step__Action_______________________________________________ 1 Start the DECnet software. Enter the following command at the DCL prompt: $ @SYS$MANAGER:STARTNET 2 Start the OpenVMS Queue Manager. Enter the following command at the DCL prompt: ______$_START/QUEUE/MANAGER________________________________ 2.11 Registering the ABS Licenses To use the 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: 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 Section 2.8. 2-24 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.11 Registering the ABS Licenses 2. Select one of the following methods to register the licenses: o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to License PAK information. See Table 2-11 o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. See Table 2-12. 3. If you plan to use ABS on more than one node in an OpenVMS Cluster, you must load the licenses on the other nodes after you install ABS. See Table 2-11, Step 10 for instructions. Table 2-11 How to Register Your Licenses Using the LICENSE ___________REGISTER_Command______________________________________ Step_Action______________________________________________________ 1 Enter the LICENSE REGISTER command with the product name followed by a dash (-): $ LICENSE REGISTER SLS-MGR - ! Register this license on the ABS server node $ LICENSE REGISTER SLS-REMOTE - ! Register this license on the ABS client node $ LICENSE REGISTER SLS-ACS - ! Register this license on the node where the StorageTek silo resides. $ LICENSE REGISTER PAB-UNIX-CLIENT-USER - ! Register this license on the ABS server node if you plan to support UNIX clients. $ LICENSE REGISTER ABS-NT-CLIENT-USER - ! Register this license on the ABS server node if you plan to support NT clients. Important: Enter a dash (-) at the end of each command in Steps 1 through 8. (continued on next page) Meeting ABS Installation Requirements 2-25 Meeting ABS Installation Requirements 2.11 Registering the ABS Licenses Table 2-11 (Cont.) How to Register Your Licenses Using the ___________________LICENSE_REGISTER_Command______________________ Step_Action______________________________________________________ 2 Enter the /ISSUER qualifier information, assigning the value DEC between quotation marks. _$ /ISSUER="DEC" - 3 Enter the /AUTHORIZATION qualifier information, assigning it the value from the AUTHORIZATION NUMBER[1] entry of the PAK: _$ /AUTHORIZATION=xxxxxx - 4 Enter the /PRODUCER qualifier information, assigning the value DEC in quotes: _$ /PRODUCER="DEC" - 5 Enter the /UNITS qualifier information, assigning it the value from the UNITS[1] entry of the PAK _$ /UNITS=nn - 6 Enter the /DATE qualifiers information, assigning the product's release date value from the PRODUCT RELEASE DATE[1] entry of the PAK: _$ /DATE=dd-mmm-yyyy - 7 Enter the /AVAILABILITY qualifier information, assigning the value from the AVAILABILITY TABLE CODE[1] entry of the PAK: _$ /AVAILABILITY=x - 8 Enter the /OPTIONS qualifier information, assigning the value from the KEY OPTIONS[1] entry of the PAK: _$ /OPTIONS=xxxxxx - 9 Enter the /CHECKSUM qualifier information, assigning the value from the CH[1] entry of the PAK: _$ /CHECKSUM=1-xxxx-xxxx-xxxx-xxxx Important: Do NOT end the entry with a dash. [1]This_information_is_supplied_in_the_LICENSE_PAK_document______ (provided with the software kit). (continued on next page) 2-26 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.11 Registering the ABS Licenses Table 2-11 (Cont.) How to Register Your Licenses Using the ___________________LICENSE_REGISTER_Command______________________ Step_Action______________________________________________________ 10 Invoke the LICENSE LOAD command with the product name: _____$_LICENSE_LOAD_SLS-MGR______________________________________ Table_2-12_How_to_Register_Your_Licenses_Using_VMSLICENSE.COM____ Step_Action______________________________________________________ 1 From the system prompt, enter the following command: $ @SYS$UPDATE:VMSLICENSE.COM 2 Select Option 1. REGISTER a Product Authorization Key 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 []:SLS-REMOTE 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 4 Verify that the information you entered is correct. Enter Yes. (continued on next page) Meeting ABS Installation Requirements 2-27 Meeting ABS Installation Requirements 2.11 Registering the ABS Licenses Table 2-12 (Cont.) How to Register Your Licenses Using ___________________VMSLICENSE.COM________________________________ Step_Action______________________________________________________ 5____To_exit_the_command_procedure,_select_Option_99.____________ For complete information about using LMF, see the OpenVMS License Management Utility Manual. 2.12 Installing POLYCENTER Scheduler If POLYCENTER Scheduler does not already exist on your system, ABS provides the POLYCENTER Scheduler save sets so you can install POLYCENTER Scheduler before you install ABS. Use the following kit names when installing POLYCENTER Scheduler from the ABS kit: o VAX systems-VSCHED_E09B021 o Alpha systems-ASCHED_E01B021 and ASCHED_E0903B021 If you are installing POLYCENTER Scheduler on an Alpha system, first install the Alpha kit (ASCHED_E01B021) and then install the ECO (ASCHED_E0903B021). ASCHED_ E0903B021 provides the callable interface. After installing these kits, POLYCENTER Scheduler is licensed for use only under the context of ABS (for example, only the POLYCENTER Scheduler commands necessary for use by ABS can be issued), unless a separate POLYCENTER Scheduler license is also purchased and installed. 2.12.1 Sample Installation For VSCHED_E09B02 For a VAX System The following example shows how to answer the installation questions when installing POLYCENTER Scheduler on a VAX system: _____________________ Restriction _____________________ Do not attempt to run the POLYCENTER Scheduler IVP or it will fail. Answer NO to the IVP question as shown in the following example. ______________________________________________________ 2-28 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler $ @SYS$UPDATE:VMSINSTAL VSCHED_E09B021 DISK$USER:[KITS.ABSA021] OpenVMS VAX Software Product Installation Procedure V7.1 It is 7-AUG-1997 at 14:06. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: VSCHED_E09B V2.1 Beginning installation of VSCHED_E09B V2.1 at 14:06 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? NO * Do you want to purge files replaced by this installation [YES]? YES Product: DECSCHEDULER Producer: DEC Version: 2.0 Release Date: 8-JUN-1992 * Does this product have an authorization key registered and loaded? YES * Start POLYCENTER Scheduler after installation [YES]? YES (C) COPYRIGHT 1989, 1995 DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS ALL RIGHTS RESERVED Enter ? at any prompt if you need additional help. POLYCENTER Scheduler files go into the [NSCHED] directory. You must specify the device for this directory. Usually this will be SYS$COMMON, unless you are installing in a VAXcluster which has separate system disks for various nodes. (in that case you MUST use a shared disk). If you installed the POLYCENTER Scheduler previously or have a previous installation of DECscheduler, the location of your current job database is the default answer and your old job database will be used. * Enter device where [NSCHED] directory is to be located [SYS$COMMON:]: If you plan to write programs that use the callable interface, then answer yes to the following question. This will cause the file NSCHED_SUBS.OLB to be placed in your NSCHED$ directory. This will require approximately 1400 blocks of disk space. Meeting ABS Installation Requirements 2-29 Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler * Do you want the callable interface [YES]? YES * Do you want the DECwindows interface [YES]? NO DECforms not found on your system. The TCP/IP Network Sevices Connection was found to be installed and running on your system. Support for remote agent command execution is an available option for the POLYCENTER Scheduler if desired. * Do you want support for remote Agent command execution [YES]? YES %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED]. All questions regarding the installation have been asked. The installation will now proceed on its own. The installation length depending upon the number of options requested will take approximately 15-25 minutes Providing wide-area network support... Linking Images... Linking NSCHED... Linking SCHED_REMOTE... Linking SCHED_DECNET... Linking SCHEDULER$INTERFACE... Linking RETRY... Linking SCHEDULER$MANAGER... Linking SCHEDULER$SHELL_INTERFACE... Linking SCHEDULER$SUMMARIZE... Linking SCHEDULER$DOO_COMMAND... Linking DB_UTILITY... Linking VSS_REPORTS... Linking SCHED$LISTENER... Linking SCHED$GET_BEST_NODE... Linking completed... Providing DCL interface, utilities, and HELP... Providing Wide Area Network capabilities... Providing Remote Executor capabilities for Agent... Providing Callable API Interface... Starting POLYCENTER Scheduler... Please take the following actions after the installation completes: 1) Make sure that your system startup procedure contains the following line $ @SYS$STARTUP:SCHEDULER$STARTUP.COM You may want to edit SCHEDULER$STARTUP.COM to change default values for Max_jobs, or to enable load balancing. 2-30 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler Users who are currently logged on must log off and then back on again to gain access to the Scheduler's DCL command interface. 2) Make sure that your site specific system shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM, contains the following line $ @NSCHED$:SCHEDULER$SHUTDOWN This will assure a proper shutdown of POLYCENTER Scheduler. You may run the Installation Verification Procedure at any time by typing the command: $ @SYS$TEST:SCHEDULER$IVP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of VSCHED_E09B V2.1 completed at 14:16 VMSINSTAL procedure done at 14:16 2.12.2 Sample Installation ASCHED_E01B021 for an Alpha System The following output is from a successful ASCHED_E01B021 installation on an OpenVMS Alpha Version 7.1 system: $ @SYS$UPDATE:VMSINSTAL ASCHED_E01B021 DISK1:[DIST_DIR] OpenVMS AXP Software Product Installation Procedure V7.1 It is 9-JUL-1997 at 13:57. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: _FTA27: _FTA28: * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: ASCHED_E01B V2.1 Beginning installation of ASCHED_E01B V2.1 at 13:57 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? NO * Do you want to purge files replaced by this installation [YES]? YES WARNING Meeting ABS Installation Requirements 2-31 Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler One or more of the system (our current) account quota parameter(s) is less than the REQUIRED value(s) to run the POLYCENTER Scheduler at start up time; and it is REQUIRED that you modify the following quota value(s). Please modify the appropriate system quota value(s) before start-up. See the POLYCENTER Scheduler installation guide for more details. Parameter Current Value Required Minimum Correct ASTLM 250 200 TRUE BIOLM 150 10000 FALSE DIOLM 150 200 FALSE ENQLM 2000 300 TRUE FILLM 100 100 TRUE TQELM 10 200 FALSE PGFLQUO 50000 10000 TRUE These are MINIMUM REQUIRED System Quota setting to run POLYCENTER Scheduler * Abort the POLYCENTER Scheduler installation now [NO]? NO Product: DECSCHEDULER Producer: DEC Version: 2.0 Release Date: 8-JUN-1992 * Does this product have an authorization key registered and loaded? YES * Stop / restart POLYCENTER Scheduler during this installation [YES]? NO %ASCHED_E01B-W-NOIVP, IVP will not be run, POLYCENTER Scheduler needs to be stopped and restarted. %ASCHED_E01B-I-IVP, It is recommended that the IVP be run after the POLYCENTER Scheduler is restarted. (C) COPYRIGHT 1989, 1995 DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS ALL RIGHTS RESERVED Enter ? at any prompt if you need additional help. * Do you want the DECwindows interface [YES]? NO DECforms is not being supported with this release of the POLYCENTER Scheduler for OpenVMS AXP 6.1 The TCP/IP Network Services Connection was found to be installed and running on your system. Support for remote agent command execution is an available option for the POLYCENTER Scheduler if desired. * Do you want support for remote Agent command execution [YES]? YES 2-32 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler POLYCENTER Scheduler files go into the [NSCHED] directory. You must specify the device for this directory. Usually this will be SYS$COMMON, unless you are installing in a VMScluster which has separate system disks for various nodes. (in that case you MUST use a shared disk). If you installed POLYCENTER Scheduler previously, the location of your current job database is the default answer and your old job database will be used. * Enter device where [NSCHED] directory is to be located [SYS$COMMON:]: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED]. %CREATE-I-EXISTS, SYS$COMMON:[NSCHED] already exists All questions regarding the installation have been asked. The installation will now proceed on its own. The installation length will take approximately 15 minutes %VMSINSTAL-I-RESTORE, Restoring product save set B ... Linking Images... Linking NSCHED... Linking SCHED_DECNET... Linking SCHEDULER$INTERFACE... Linking RETRY... Linking SCHEDULER$MANAGER... Linking SCHEDULER$SHELL_INTERFACE... Linking SCHEDULER$SUMMARIZE... Linking SCHEDULER$DOO_COMMAND... Linking DB_UTILITY... Linking VSS_REPORTS... Linking SCHED$LISTENER... Linking SCHED$GET_BEST_NODE... Providing the DECwindows interface image (NSCHED:SCHEDULER$XUI.EXE)... Linking completed... Providing DCL interface, utilities, and HELP... Providing Wide Area Network capabilities... Providing DECWindows Interface... Providing Remote Executor capabilities for Agent... Please take the following actions after the installation completes: 1) Make sure that your system startup procedure contains the following line $ @SYS$STARTUP:SCHEDULER$STARTUP.COM You may want to edit SCHEDULER$STARTUP.COM to change default values for Max_jobs, or to enable load balancing. Meeting ABS Installation Requirements 2-33 Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler Users who are currently logged on must log off and then back on again to gain access to the Scheduler's DCL command interface. 2) Make sure that your site specific system shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM, contains the following line $ @NSCHED$:SCHEDULER$SHUTDOWN This will assure a proper shutdown of POLYCENTER Scheduler. You may run the Installation Verification Procedure at any time by typing the command: $ @SYS$TEST:SCHEDULER$IVP.COM %VMSINSTAL-I-SENDMAIL, Sending mail notification to the developers %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of ASCHED_E01B V2.1 completed at 14:02 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ASCHED_E01B021.VMI_DATA VMSINSTAL procedure done at 14:03 --------------------------------------------------------------------------- *** IMPORTANT ***: If you answer "YES" to the DECwindows interface prompt during the installation of ASCHED_E01B021, you will not be able to run the POLYCENTER Scheduler DECwindows interface. This version of Scheduler is not linked with OpenVMS V7.1 images. If you attempt to run the DECwindows interface, you will receive the following error: $ SCHEDULER/INTERFACE=DECWINDOWS %DCL-W-ACTIMAGE, error activating image SCHED_RTL_TV -CLI-E-IMGNAME, image file $1$DKA100:[SYS0.SYSCOMMON.][NSCHED]SCHED_RTL.EXE;4 -SYSTEM-F-PRIVINSTALL, shareable images must be installed to run privileged image 2-34 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler 2.12.3 Sample Installation for ASCHED_E0903B021 for an Alpha System The following output is from a successful ASCHED_E0903B021 installation on an OpenVMS Alpha Version 7.1 system: $ @SYS$UPDATE:VMSINSTAL ASCHED_E0903B021 DISK1:[DIST_DIR] OpenVMS AXP Software Product Installation Procedure V7.1 It is 10-JUL-1997 at 15:10. Enter a question mark (?) at any time for help. %VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account. %VMSINSTAL-W-ACTIVE, The following processes are still active: _FTA31: _FTA32: * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? YES The following products will be processed: ASCHED_E0903B V2.1 Beginning installation of ASCHED_E0903B V2.1 at 15:10 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Do you want to run the IVP after the installation [YES]? NO * Do you want to purge files replaced by this installation [YES]? YES WARNING One or more of the system (our current) account quota parameter(s) is less than the REQUIRED value(s) to run the POLYCENTER Scheduler at start up time; and it is REQUIRED that you modify the following quota value(s). Please modify the appropriate system quota value(s) before start-up. See the POLYCENTER Scheduler installation guide for more details. Parameter Current Value Required Minimum Correct ASTLM 250 200 TRUE BIOLM 150 10000 FALSE DIOLM 150 200 FALSE ENQLM 2000 300 TRUE FILLM 100 100 TRUE TQELM 10 200 FALSE PGFLQUO 50000 10000 TRUE Meeting ABS Installation Requirements 2-35 Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler These are MINIMUM REQUIRED System Quota setting to run POLYCENTER Scheduler * Abort the POLYCENTER Scheduler installation now [NO]? NO Product: DECSCHEDULER Producer: DEC Version: 2.0 Release Date: 8-JUN-1992 * Does this product have an authorization key registered and loaded? YES Calling vss$get_history to summarize success records... ..done, status=1 Calling get_history to summarize failure records... ..done, status=1 %NONAME-W-NOMSG, Message number 00000000 * Stop / restart POLYCENTER Scheduler during this installation [YES]? YES (C) COPYRIGHT 1989, 1995 DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS ALL RIGHTS RESERVED Enter ? at any prompt if you need additional help. If you plan to write programs that use the callable interface, then answer yes to the following question. This will cause the file AXP_NSCHED_SUBS.OLB to be placed in your NSCHED$ directory. This will require approximately 6,200 blocks of disk space. * Do you want the callable interface [YES]? YES DECforms is not being supported with this release of the POLYCENTER Scheduler for OpenVMS AXP 6.1 The TCP/IP Network Services Connection was found to be installed and running on your system. Support for remote agent command execution is an available option for the POLYCENTER Scheduler if desired. * Do you want support for remote Agent command execution [YES]? YES POLYCENTER Scheduler files go into the [NSCHED] directory. You must specify the device for this directory. Usually this will be SYS$COMMON, unless you are installing in a VMScluster which has separate system disks for various nodes. (in that case you MUST use a shared disk). If you installed POLYCENTER Scheduler previously, the location of your current job database is the default answer and your old job database will be used. * Enter device where [NSCHED] directory is to be located [SYS$COMMON:]: 2-36 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$COMMON:[NSCHED]. %CREATE-I-EXISTS, SYS$COMMON:[NSCHED] already exists All questions regarding the installation have been asked. The installation will now proceed on its own. The installation length will take approximately 15 minutes Linking Images... Linking NSCHED... Linking SCHED_DECNET... Linking SCHEDULER$INTERFACE... Linking RETRY... Linking SCHEDULER$MANAGER... Linking SCHEDULER$SHELL_INTERFACE... Linking SCHEDULER$SUMMARIZE... Linking SCHEDULER$DOO_COMMAND... Linking DB_UTILITY... Linking VSS_REPORTS... Linking SCHED$LISTENER... Linking SCHED$GET_BEST_NODE... Linking completed... Providing DCL interface, utilities, and HELP... Providing Wide Area Network capabilities... Providing Callable API Interface... Providing Remote Executor capabilities for Agent... Restarting POLYCENTER Scheduler... Please take the following actions after the installation completes: 1) Make sure that your system startup procedure contains the following line $ @SYS$STARTUP:SCHEDULER$STARTUP.COM You may want to edit SCHEDULER$STARTUP.COM to change default values for Max_jobs, or to enable load balancing. Users who are currently logged on must log off and then back on again to gain access to the Scheduler's DCL command interface. 2) Make sure that your site specific system shutdown procedure, SYS$MANAGER:SYSHUTDWN.COM, contains the following line $ @NSCHED$:SCHEDULER$SHUTDOWN This will assure a proper shutdown of POLYCENTER Scheduler. Meeting ABS Installation Requirements 2-37 Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler You may run the Installation Verification Procedure at any time by typing the command: $ @SYS$TEST:SCHEDULER$IVP.COM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %RUN-S-PROC_ID, identification of created process is 0000023E %RUN-S-PROC_ID, identification of created process is 00000245 Installation of ASCHED_E0903B V2.1 completed at 15:14 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ASCHED_E0903B021.VMI_DATA VMSINSTAL procedure done at 15:14 --------------------------------------------------------------------------- 2.12.4 Configuring POLYCENTER Scheduler for a Mixed-Architecture OpenVMS Cluster If your OpenVMS Cluster contains both VAX and Alpha systems, you will need to configure POLYCENTER Scheduler so that both systems can find their required files. You will need to: o Create new directories and move the appropriate VAX and Alpha POLYCENTER Scheduler files o Redefine the logical NSCHED$ in the file SYS$STARTUP:SCHEDULER$STARTUP.COM on both the VAX and Alpha system Follow the instructions in Table 2-13 to set up POLYCENTER Scheduler in a mixed-architecture OpenVMS Cluster. Table 2-13 Configuring POLYCENTER Scheduler for a Mixed- ___________Architecture_OpenVMS_Cluster____________________ Step_Action________________________________________________ 1. Install POLYCENTER Scheduler on the VAX system as described in Section 2.12.1. 2 The installation procedure for POLYCENTER Scheduler creates a directory named NSCHED. (continued on next page) 2-38 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler Table 2-13 (Cont.) Configuring POLYCENTER Scheduler for a ___________________Mixed-Architecture_OpenVMS_Cluster______ Step_Action________________________________________________ 2. While located in the NSCHED directory, create a new directory named VAX: $ SET DEFAULT SYS$SYSDEVICE:[VMS$COMMON.NSCHED] $ CREATE/DIRECTORY [.VAX] 3. Move all of the .EXE and .OLB files from the directory NSCHED to the new VAX directory: $ RENAME *.EXE,*.OLB [.VAX] Example_of_the_new_VAX_directory: Directory SYS$SYSDEVICE:[VMS$COMMON.NSCHED.VAX] DB_UTILITY.EXE;1 NSCHED.EXE;1 NSCHED_SUBS.OLB;1 RETRY.EXE;1 SCHED$GET_BEST_NODE.EXE;1 SCHED$LISTENER.EXE;1 SCHEDULER$DOO_COMMAND.EXE;1 SCHEDULER$INTERFACE.EXE;1 SCHEDULER$MANAGER.EXE;1 SCHEDULER$SHELL_INTERFACE.EXE;1 SCHEDULER$SUMMARIZE_LOG.EXE;1 SCHED_DECNET.EXE;1 SCHED_REMOTE.EXE;1 VSS_REPORTS.EXE;1 4. Install POLYCENTER Scheduler on the Alpha system as described in Section 2.12.2. 5. While located in the NSCHED directory, create a new directory named ALPHA: $ SET DEF SYS$SYSDEVICE:[VMS$COMMON.NSCHED] $ CREATE/DIRECTORY [.ALPHA] (continued on next page) Meeting ABS Installation Requirements 2-39 Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler Table 2-13 (Cont.) Configuring POLYCENTER Scheduler for a ___________________Mixed-Architecture_OpenVMS_Cluster______ Step_Action________________________________________________ 6. Move all of the .EXE and .OLB files from the directory NSCHED to the new ALPHA directory: $ RENAME *.EXE,*.OBL [.ALPHA] Example_of_the_ALPHA_directory: Directory SYS$SYSDEVICE:[VMS$COMMON.NSCHED.ALPHA] AXP_NSCHED_SUBS.OLB;1 DB_UTILITY.EXE;1 NSCHED.EXE;1 RETRY.EXE;1 SCHED$GET_BEST_NODE.EXE;1 SCHED$LISTENER.EXE;1 SCHEDULER$DOO_COMMAND.EXE;1 SCHEDULER$INTERFACE.EXE;1 SCHEDULER$MANAGER.EXE;1 SCHEDULER$SHELL_INTERFACE.EXE;1 SCHEDULER$SUMMARIZE_LOG.EXE;1 SCHED_DECNET.EXE;1 SCHED_RTL.EXE;1 VSS_REPORTS.EXE;1 7. Edit the file SYS$STARTUP:SCHEDULER$STARTUP.COM on the VAX system and and define the logical NSCHED$ as a search list: $! define/system/exec NSCHED$ SYS$COMMON:[NSCHED] $! previous line commented out and replaced with the following $! search list definition: $ define/system/exec NSCHED$ DISK$VAXVMSV71:[VMS$COMMON.NSCHED], - DISK$VAXVMSV71:[VMS$COMMON.NSCHED.VAX] $ define/system/exec NSCHED_DEFAULT_SD_ACTION SKIP $ define/system/exec NSCHED$REMOTE_SUPPORT_ENABLED "TRUE" (continued on next page) 2-40 Meeting ABS Installation Requirements Meeting ABS Installation Requirements 2.12 Installing POLYCENTER Scheduler Table 2-13 (Cont.) Configuring POLYCENTER Scheduler for a ___________________Mixed-Architecture_OpenVMS_Cluster______ Step_Action________________________________________________ 8. Edit the file SYS$STARTUP:SCHEDULER$STARTUP.COM on the Alpha system and and define the logical NSCHED$ as a search list: $! define/system/exec NSCHED$ SYS$COMMON:[NSCHED] $! previous line commented out and replaced with the following $! search list definition: $ define/system/exec NSCHED$ DISK$VAXVMSV71:[VMS$COMMON.NSCHED], - DISK$VAXVMSV71:[VMS$COMMON.NSCHED.ALPHA] $ define/system/exec NSCHED_DEFAULT_SD_ACTION SKIP $ define/system/exec NSCHED$REMOTE_SUPPORT_ENABLED "TRUE" 9. Issue the shutdown and startup commands for POLYCENTER Scheduler to redefine the logical name NSCHED$: $ @DISK$VAXVMSV71:[VMS$COMMON.NSCHED]SCHEDULER$SHUTDOWN _____$_@SYS$COMMON:[SYS$STARTUP]SCHEDULER$STARTUP__________ Meeting ABS Installation Requirements 2-41 3 _________________________________________________________________ Installing the Software This chapter contains the instructions for installing the Archive/Backup System for OpenVMS Version 2.1B software and the Media and Device Management Services for OpenVMS Version 2.9 software. The Media and Device Management Services (MDMS) software must be installed before you install the Archive/Backup System (ABS) software. Once you have completed the software installations, you are required to perform some postinstallation tasks before you can create your first backup operation. The information presented in this chapter includes those tasks, and it provides instructions on how to verify that the tasks have been implemented correctly. Before proceeding with the installation procedure, make sure you have completed all of the following preinstallation tasks: o Did you decide where to install the ABS and MDMS server software? o Did you configure and test the hardware? o Did you set your default directory to SYS$UPDATE? o Did you log into an account with the proper quotas and privileges? o Did you perform a system backup operation? o If you are doing an upgrade installation, did you shutdown ABS? o Did you verify the hardware and disk space requirements? o Did you verify the software requirements? o Did you check to see if DECnet or DECnet-Plus and the QueueManager are running? o Did you register the appropriate licenses? Installing the Software 3-1 Installing the Software o Did you install POLYCENTER Scheduler or is it already installed? Once you have completed all of the preinstallation tasks, you are ready to continue with the installation procedure. 3.1 Installing the Media and Device Management Software Before installing the ABS software, you must first install Media and Device Management Services for OpenVMS (MDMS). _______________________ Caution _______________________ If you currently use Storage Library System for OpenVMS (SLS) for backup and restore operations, and if you plan to continue to use SLS along with ABS, do not install MDMS. MDMS does not contain the backup and restore functionality of SLS. If you install MDMS over SLS, you lose the ability to restore data saved through SLS. To continue using SLS backup and restore functionality, install only the ABS software. If you want SLS to include the most current tape drive support, upgrade to the latest version of SLS. The media and device management functionality is inclusive with SLS. ______________________________________________________ ________________________ Note ________________________ If you plan to use SLS concurrently with ABS, see the Storage Library System for OpenVMS Installation and Configuration Guide for SLS installation instructions. After you have installed or upgraded SLS, proceed to Section 3.3. ______________________________________________________ Table 3-1 shows the stages of installing and configuring the MDMS software before you begin the ABS Version 2.1B installation procedure. 3-2 Installing the Software Installing the Software 3.1 Installing the Media and Device Management Software Table_3-1_Stages_of_Installing_MDMS________________________ Stage__Action______________________________________________ 1 Install the MDMS server software as described in Section 3.1.1. 2 Install the MDMS client software as described in Section 3.1.2. 3 Verify the MDMS installation procedure as described in Section 3.2.1. 4 Edit the startup and shutdown files as described in Section 3.2.2. 5 Define global symbols for as described in Section 3.2.3. 6 Define the OpenVMS Cluster alias name symbol and the failover server nodes symbol in the file SYS$MANAGER:TAPESTART.COM. See Section 3.2.4. 7 Define a network object for an OpenVMS Cluster system as described in Section 3.2.5. 8 Configure a tape or optical drive so that MDMS will recognize it. When you have completed the ABS installation, you will be able to perform a backup and restore operation using this drive: o If you will be using an automated media library system, see Section 3.2.6. o If you will be using a media loader system, see Section 3.2.7. o If you will be using an operator attended system, see Section 3.2.8. o If the tape or optical drive is remote from the disks that contain the backup data, see Section 3.2.9. 9 Verify the connections between the MDMS software and drives as described in Sections 3.2.6, 3.2.7, and _______3.2.8.______________________________________________ Installing the Software 3-3 Installing the Software 3.1 Installing the Media and Device Management Software 3.1.1 Installing the MDMS Server Software The MDMS installation procedure consists of a series of questions and informational messages. Appendix A provides a sample installation log file. 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 Table 3-2 to install MDMS Version 2.9 server software. ________________________ Note ________________________ During the installation of the MDMS software, you will be prompted whether you want to back up the data on the system where you are installing the MDMS software to a drive located on a remote system, or whether you want to allow a remote system to back up its data to a drive located on the system where you are installing the MDMS software. If you answer "Yes" to either of these prompts, you will be enabling remote backup operations and the MDMS installation procedure automatically will install the Remote Device Facility[TM](RDF) software. ______________________________________________________ ________________________ Note ________________________ If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press RETURN. Correct the problem before restarting the installation. ______________________________________________________ 3-4 Installing the Software Installing the Software 3.1 Installing the Media and Device Management Software Table_3-2_How_to_Install_the_MDMS_Software_______________________ Step_Action______________________________________________________ 1 Load and mount the media that contains the software kit. 2 Invoke the VMSINSTAL procedure for the type of software that you are installing: o Server software-Enter the VMSINSTAL command in the following format: $@SYS$UPDATE:VMSINSTAL MDMS029 location: OPTIONS N o Client software-Enter the VMSINSTAL command in the following format: $@SYS$UPDATE:VMSINSTAL MDMSCLIENT029 location: OPTIONS N Where: o location is the tape drive (or disk device directory name) that contains the software kit save set. o OPTIONS N is an optional parameter that displays or prints the release notes. The default behavior is to move the release notes to SYS$HELP. 3 If you see the following message: %VMSINSTAL-W- ACTIVE, The following processes are still active * Do you want to continue anyway [NO]? Enter Y and press , else go to step 4. 4 Confirm the state of the system backup. * Are you satisfied with the backup of your system disk [Yes]? Press . 5 If you did not include the location on the VMSINSTAL command line, identify the location for the software to be mounted. * Where will the distribution volumes be mounted: SLS$KITS: You may specify a tape drive, a local disk, or a remote disk. Enter the appropriate information and press . (continued on next page) Installing the Software 3-5 Installing the Software 3.1 Installing the Media and Device Management Software Table_3-2_(Cont.)_How_to_Install_the_MDMS_Software_______________ Step_Action______________________________________________________ 6 Respond to the installation options: Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 * Enter installation options you wish to use (none): Enter the number of the desired option and press . 7 Continue the installation. MDMS displays the following message: ***************************************************************** * WARNING * ***************************************************************** * MDMS should NOT be installed on a system which is currently running * * SLS. The MDMS installation will supersede the existing SLS * * installation. In this situation, there may be old SLS files not * * removed by the MDMS installation such as SLS$SYSBAK.EXE. This could* * lead to unpredictable and unsupported behavior if any SLS backups * * are attempted after the MDMS installation. * ************************************************************************* * Do you want to continue with this installation [No]? Enter Y and press . (continued on next page) 3-6 Installing the Software Installing the Software 3.1 Installing the Media and Device Management Software Table_3-2_(Cont.)_How_to_Install_the_MDMS_Software_______________ Step_Action______________________________________________________ 8 Select to run the Installation Verification Procedure (IVP). * Do you want to run the IVP after the installation [YES]? Recommendation: Running the IVP procedure is recommended. Press to run the IVP, else enter No and press . 9 Client_software_only: Enter the MDMS server location: * Are you ready to proceed? [YES]? * What is the name or OpenVMS Cluster system alias of the MDMS/SLS server node: At this point, enter the MDMS server node name or OpenVMS Cluster system alias name. 10 RDF_(Remote_Device_Facility)_software: If you want to support remote backup operations, respond to the following queries: * Do you want to backup disks on this system to a drive on a remote system? Enter Yes to install the RDF software, else enter No. * Do you want to allow remote backups access to the tape drives on this system? Enter Yes to install the RDF software, else enter No. Note: If you select to support remote drives on an Alpha system, you must reboot the system after the installation procedure is complete. Each Alpha server node and each Alpha client node must be rebooted because the device drivers cannot be reloaded on Alpha nodes. (continued on next page) Installing the Software 3-7 Installing the Software 3.1 Installing the Media and Device Management Software Table_3-2_(Cont.)_How_to_Install_the_MDMS_Software_______________ Step_Action______________________________________________________ 11 Specify the disk device name where MDMS software will reside. * Enter the name of the disk device the MDMS/SLS software will use [DUA0:]: Enter the name of the disk device you noted in Table 2-5 and press . 12 Enter the directory name where MDMS software will reside: * Enter the name of the directory the MDMS/SLS software will use [SLS$FILES]: Press to accept the default or enter a new directory name and press . 13 Identify the MDMS manager account UIC. If you see the following message: * Enter the UIC for the SLS manager account. [[1,21]] Press , else, go to Step 16. 14 Enter and verify the MDMS account password. Restriction: The password must be at least 15 and no more than 31 characters. * Password: * Verify password: 15 Set quotas and flags for the MDMS account. MDMS automatically sets quotas and flags for the account. * Do you wish to update these flags now [YES]? Press . Updating the MDMS process account quotas and the flags causes the Authorize utility to run. (continued on next page) 3-8 Installing the Software Installing the Software 3.1 Installing the Media and Device Management Software Table_3-2_(Cont.)_How_to_Install_the_MDMS_Software_______________ Step_Action______________________________________________________ 16 At this point, the installation procedure continues without further operator intervention. Note the following important items about the MDMS installation procedure: o When you install MDMS on a new system (one on which there is no existing TAPESTART.COM file), the MDMS installation procedure generates a default configuration file that contains the media triplets for the known tape or optical drives on your system. These media triplets are placed in your TAPESTART.COM file. For instructions about this file, media triplets, and configuring MDMS, see Media and Device Management Services for OpenVMS Guide to Operations. o If you chose to run the IVP at Step 8, it runs now. For a complete installation and IVP example, see Appendix Appendix A. 17 If you answered YES to either question in Step 10 (remote device support (RDF)), you must reboot the node to install _____the_new_device_drivers._____________________________________ Example_Installation: For an example of the MDMS server installation, see Appendix A. 3.1.2 Installing the MDMS Client Software Before you can install the MDMS client software, you must have already installed the MDMS server software and registered the nodes on which you plan to install the MDMS client software. Table 3-3 describes how to register MDMS client nodes and then install the MDMS client software. Installing the Software 3-9 Installing the Software 3.1 Installing the Media and Device Management Software Table_3-3_How_to_Install_the_MDMS_Client_Software__________ Step_Action________________________________________________ 1 Register the MDMS client nodes on the MDMS server node. From the SYSTEM account on the MDMS server node, enter the following command: $ RUN SLS$SYSTEM:SLS$SLSMGR Result: MDMS displays the Administrator Menu. 2 Select the Database Access Authorization option from the numeric keypad: Enter 3 and press . 3 Invoke the record insertion feature from the numeric keypad: Press keypad < 8 > or press the key. 4 Enter the name of the MDMS client node(s) in the Node field and press . Result: MDMS displays the list of MDMS client nodes with the new entry or entries. 5 Save the changes to the database: Enter Y and press . 6 Install the MDMS client software on each of the MDMS client nodes (also ABS OpenVMS client nodes) that you registered. Use the installation procedure described _____in_Table_3-2._________________________________________ DIGITAL recommends configuring according to the approach outlined in Section 1.5.3.2. The steps outlined in Table 3-4 implement that approach. This configuration assumes two installations: a primary installation for which all files and directories will be used, and a secondary installation for which only architecture-compatible executables or other nonshared files are located. With this installation, systems with logicals that point to shared locations must be defined to point to the primary installation file locations. This procedure describes how 3-10 Installing the Software Installing the Software 3.1 Installing the Media and Device Management Software to change key logical definitions to point the primary installation files. 3.1.3 How to Configure for VAX and Alpha Systems Table 3-4 shows the steps for configuring in a mixed architecture OpenVMS Cluster system. Table 3-4 How to Configure in a Mixed Architecture OpenVMS __________Cluster_System.__________________________________ Step__Action_______________________________________________ 1 Edit the SYS$MANAGER:TAPESTART.COM file logical on the secondary system so they point to the primary installation 2 Edit SLS$SYSTEM:LOADER.COM on the secondary system to change the definition of the logical that points to the Pool Authorization and user history update parameters SLS$PARAMS 3 Shutdown and restart on the secondary system so the ______new_logical_definitions_can_take_effect._____________ Table 3-5 shows logical definitions on both VAX and Alpha systems in a mixed architecture OpenVMS Cluster. In this particular configuration, the VAX system installation is the primary, the Alpha the secondary. The logicals on the Alpha system point to shared files in the VAX system directory. Installing the Software 3-11 Installing the Software 3.1 Installing the Media and Device Management Software Table 3-5 Comparing Logical Definitions Between VAX and Alpha __________Systems________________________________________________ VAX System Logical Definitions___________________Alpha_System_Logical_Definitions___ VAXSYS>SHOW LOGICAL SLS$* ALPHASYS> SHOW LOGICAL SLS$* SLS$CUSTOM = SLS$ROOT:[CUSTOM]SLS$CUSTOM = SLS$ROOT:[CUSTOM] SLS$DATA = SLS$ROOT:[DATA.ALPHASYS] SLS$DATA = SLS$ROOT:[DATA.VAXSSLS$DATAC = SLS$ROOT:[DATA] SLS$LABEL = _NL: SLS$DATAC = SLS$ROOT:[DATA] SLS$LABEL_TEMPLATE = SLS$LABEL = _NL: SLS$SYSTEM:PRINTED_LABEL_V21.TEMPLATE SLS$LABEL_TEMPLATE = SLS$SYSTEM:PRINTED_LABEL_V21SLS$MAILBOX = MBA36: SLS$MASTER = SLS$MAILBOX = MBA71: $1$DUA3:[VAX.SLS$FILES.PRIMAST] SLS$MASTER = SLS$PARAMS = SLS$ROOT:[PRIMAST] $1$DUA3:[VAX.SLS$FILES.PARAMS] SLS$PARAMS = SLS$ROOT = SLS$ROOT:[PARAMS] $1$DUA3:[ALPHA.SLS$FILES.] SLS$ROOT = SLS$STARTUP_P1 = REBOOT $1$DUA3:[VAX.SLS$FILES.] SLS$SYSTEM = SLS$ROOT:[CUSTOM] SLS$STARTUP_P1 = REBOOT = SLS$ROOT:[SYSTEM] SLS$SYSTEM = SLS$ROOT:[CUSTOM]SLS$VAULT = DPS = SLS$ROOT:[SYSTEM] SLS$VAULT_=_DPS__________________________________________________ 3.2 MDMS Postinstallation Tasks Complete the MDMS postinstallation tasks described in Sections 3.2.1 through 3.2.9 before installing ABS Version 2.1B. These tasks apply whether you have installed the MDMS server or client software. 3-12 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks 3.2.1 Verifying the MDMS Installation If you did not execute the IVP during the installation procedure, you can execute it immediately after installing the MDMS software. Enter the following command at the DCL system prompt: $ @SYS$TEST:MDMS_SLS$IVP Requirements: o The MDMS software must be installed and running on the system where the IVP is executed. o When executing the IVP on an MDMS client node, the MDMS client node must have been registered on the MDMS server node (see Section 3.1.2). 3.2.2 Providing Automatic Start Up and Shut Down You must edit the startup and shutdown files to provide automatic startup and shutdown of the MDMS software. To make sure that MDMS automatically starts up and shuts down, use the following procedure: 1. Add the following command line to the one of the following system startup files determined by your version of OpenVMS: o SYS$MANAGER:SYSTARTUP_V5.COM o SYS$MANAGER:SYSTARTUP_VMS.COM for OpenVMS Version 6.0. Add the following line after the STARTNET command: $ @SYS$STARTUP:SLS$STARTUP 2. Add the following line to the system shutdown file, SYS$MANAGER:SYSHUTDOWN.COM: $ @SLS$SYSTEM:SLS$SHUTDOWN 3.2.3 Defining Global Symbols for MDMS Users To define global symbols for MDMS software users, edit the system login file SYS$MANAGER:SYLOGIN.COM, and add the following line: $ @SYS$MANAGER:SLS$TAPSYMBOL Requirement: Installing the Software 3-13 Installing the Software 3.2 MDMS Postinstallation Tasks Include the symbol definitions in a section of the SYLOGIN.COM file that is executed by all accounts, typically before the BATCH command. 3.2.4 Defining the OpenVMS Cluster Alias Name and the Failover Server Nodes Once you have installed either the MDMS server or client software, you must edit the file SYS$MANAGER:TAPESTART.COM to define the primary server system and the node names of the systems designated to become the MDMS server should the any one of the nodes fail. The two symbols you must define are PRI and DB_NODES. The symbols should be defined exactly the same on both the MDMS server and any MDMS client nodes. Example: $ PRI :== WAGON ! OpenVMS Cluster alias name $ DB_NODES :== WHEEL,REINS,HORSES ! Nodes in the WAGON OpenVMS ! Cluster that can be MDMS servers 3.2.5 Defining a Network Object on an OpenVMS Cluster Follow the steps in Table 3-6 to define the SLS$DBX NCP object. Requirement: If you intend to implement the high-availability features of MDMS software, all nodes that participate in the OpenVMS Cluster system alias must have the SLS$DBX NCP object defined. Table_3-6_How_to_Define_the_SLS$DBX_NCP_Object_____________ Step_Action________________________________________________ 1 From an account with BYPASS privilege, on the node on which MDMS software was just installed, invoke the Network Control Program (NCP) utility by entering the following command: $ RUN SYS$SYSTEM:NCP (continued on next page) 3-14 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks Table_3-6_(Cont.)_How_to_Define_the_SLS$DBX_NCP_Object_____ Step_Action________________________________________________ 2 Obtain the password for the MDMS account: NCP> SHOW OBJECT SLS$DBX CHARACTERISTICS Result: Object Volatile Characteristics as of 2-DEC-1996 13:08:15 Object = SLS$DBX Number = 0 File id = SYS$SYSTEM:SLS$FIND_DB_NODE.EXE User id = SLS Password = password Note: The password is displayed only when the BYPASS privilege is enabled. 3 Exit the NCP utility: NCP> EXIT 4 Invoke the SYSMAN utility: $RUN SYS$SYSTEM:SYSMAN (continued on next page) Installing the Software 3-15 Installing the Software 3.2 MDMS Postinstallation Tasks Table_3-6_(Cont.)_How_to_Define_the_SLS$DBX_NCP_Object_____ Step_Action________________________________________________ 5 Set the SYSMAN environment to include the OpenVMS Cluster system nodes that participate in the DECnet OpenVMS Cluster system alias. Participating_nodes: The participating nodes in a OpenVMS Cluster can be all of the nodes or only some of the nodes. To identify the participating nodes, use one of the following commands: o To identify all nodes in a OpenVMS Cluster, enter the following SYSMAN command: SYSMAN> SET ENVIRONMENT /CLUSTER o To identify only specific nodes, enter the SYSMAN command in the following format: SYSMAN> SET ENVIRONMENT /NODE=(node_1,node_2,...node_n) Note: The nodes defined here are typically the same nodes that you assigned to DB_NODES in the SYS$MANAGER:TAPESTART.COM file. 6 Define the SLS$DBX object by entering SYSMAN command in the following format: SYSMAN>DO MCR NCP DEFINE OBJECT SLS$DBX NUMBER 0 USER SLS - _SYSMAN> FILE SYS$SYSTEM:SLS$FIND_DB_NODE.EXE PASSWORD password Requirement: The password entered with this command must be the same as the password used for the MDMS account during installation. 7 Read the SLS$DBX object on the node: SYSMAN> DO MCR NCP SET KNOWN OBJECT ALL 8 Exit the SYSMAN utility: _____SYSMAN>_EXIT__________________________________________ 3-16 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks 3.2.6 Configuring MDMS for an Automated Tape Library System If your storage management environment contains an automated tape library (ATL), you must define the ATL in the MDMS file SYS$MANAGER:TAPESTART.COM. You must then test the configuration to make sure it is correct. 3.2.6.1 Configure MDMS The following procedure requires you to edit the MDMS file named SYS$MANAGER:TAPESTART.COM. You can use any ASCII text editor to accomplish these edits: 1. Identify the primary processing node. Define the symbol PRI to the name of the node or the OpenVMS Cluster alias name executing the MDMS server. If you defined the symbol PRI to the OpenVMS Cluster alias, you must define the symbol DB_NODES to the names of the nodes in the OpenVMS Cluster system that you want to allow to be an MDMS servers. 2. Identify the node on which the current TAPESTART.COM file resides. Assign the node name to the NODE symbol. 3. Define the QUICKLOAD symbol to 1 to facilitate unattended backup. 4. Create the ATL definition. Use the following example as a guideline: Example:_Defining_An_Automated_Tape_Library_(ATL)_System o Assign the name meaningful name (such as ABS_JUKE) to the TAPE_JUKEBOXES symbol: $ TAPE_JUKEBOXES := "ABS_JUKE" o Define the robot device name and the tape drives to the jukebox name you assigned to the TAPE_JUKEBOXES symbol: $ ABS_JUKE := "NODE01::$1$DUA810:,NODE01::$1$MUA43:,NODE01::$1$MUA44:" Where: - NODE01::$1$DUA810: is the node name plus the robot device name Installing the Software 3-17 Installing the Software 3.2 MDMS Postinstallation Tasks - NODE01::$1$MUA43: and NODE01::$1$MUA44 are the node names plus the names of the drives located in the ATL ________________________ Note ________________________ The robot device name and the tape drive names must be prefixed with a node name. ______________________________________________________ 5. Define the media triplets. Media triplets are a set of symbols used to associate types of media with drives capable of accessing them. Use the following example as a guideline: Example:_Defining_the_Media_Triplets_for_an_ATL_System $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := $1$MUA43:,$1$MUA44: 6. Shut down and restart MDMS to enable all the changes made to the TAPESTART.COM file. Use the following command: $ @SLS$SYSTEM:SLS$SHUTDOWN $ @SYS$STARTUP:SLS$STARTUP 3.2.6.2 Test the MDMS Configuration This procedure guides you through testing the configuration for the automated tape library system (ATL). ________________________ Note ________________________ Before you perform the procedure, you must have an initialized volume that is compatible with the drive in the ATL. Use this initialized volume to perform this test. ______________________________________________________ If you have MRU software, you can take this opportunity to learn more about the nature of the managed media environment. Compare the results of the STORAGE and ROBOT commands, or use MRU to verify the state of the automated media library after issuing a STORAGE command. 3-18 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks Issue STORAGE and ROBOT commands at the DCL prompt. 1. Check the response of the automated tape library to MDMS. Issue the STORAGE SHOW JUKEBOX command: $ STORAGE SHOW JUKEBOX [tape_jukebox_name] Issue the ROBOT SHOW ROBOT command and compare the results: $ ROBOT SHOW ROBOT [robot_name] 2. Add a volume to the volume database with the STORAGE ADD VOLUME command: $ STORAGE ADD VOLUME volume_id 3. Verify the volume you just added with the STORAGE SHOW VOLUME command: $ STORAGE SHOW VOLUME volume_id 4. Prepare to reply to MDMS requests with the OpenVMS OPCOM REPLY command: $ REPLY/ENABLE=TAPES 5. Insert the volume for which you have just created a volume database record into the library. Issue the STORAGE IMPORT CARTRIDGE command: $ STORAGE IMPORT CARTRIDGE volume_id tape_jukebox_name Translate the location information from the STORAGE IMPORT CARTRIDGE command into a slot location and issue the ROBOT SHOW SLOT command to verify the volume is in the slot: $ ROBOT SHOW [ROBOT robot_name] SLOT [[[slot_number]|[slot_number-slot_number]],...] 6. Load the volume into the drive with the STORAGE LOAD command: $ STORAGE LOAD drive-name volume-id Using the ROBOT SHOW DRIVE command, validate that the volume has been loaded: $ ROBOT SHOW [ROBOT robot_name] DRIVE [[[drv_number]|[drv_number-drv_number]],...] 7. Unload the volume from the drive using the STORAGE UNLOAD command: $ STORAGE UNLOAD VOLUME volume-id Installing the Software 3-19 Installing the Software 3.2 MDMS Postinstallation Tasks Using the ROBOT SHOW SLOT command, validate the volume has been returned to the slot from which it was loaded: $ ROBOT SHOW [ROBOT robot_name] SLOT [[[slot_number]|[slot_number-slot_number]],...] 8. Remove the volume from the library with the STORAGE EXPORT CARTRIDGE command: $ STORAGE EXPORT CARTRIDGE volume-name 3.2.7 Configuring MDMS for a Media Loader If your storage management environment contains a media loader, you must define the media loader in the MDMS file SYS$MANAGER:TAPESTART.COM. You must then test the configuration to make sure it is correct. 3.2.7.1 Configure MDMS The following procedure requires you to edit the MDMS file named SYS$MANAGER:TAPESTART.COM. You can use any ASCII text editor to accomplish these edits: 1. Identify the primary processing node. Define the symbol PRI to the name of the node or the OpenVMS Cluster alias name executing the MDMS server. If you defined the symbol PRI to the OpenVMS Cluster alias, you must define the symbol DB_NODES to the names of the nodes in the OpenVMS Cluster system that you want to act as MDMS servers. 2. Identify the node on which the current TAPESTART.COM file resides. Assign the node name to the NODE symbol. 3. Define the QUICKLOAD symbol to 1 to facilitate unattended backup. 4. Create the media loader definition. Use the following example as a guideline: Example:_Defining_a_Media_Loader Define a symbol ABS_JUKE to the names of the robot device and tape drive of the automated media library system. The following example shows how define the TAPE_ JUKEBOXES symbol: 3-20 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks Assign a meaningful name (such as ABS_JUKE) to the TAPE_ JUKEBOXES symbol: $ TAPE_JUKEBOXES := "ABS_JUKE" Define the robot device name and the tape drive to the jukebox name defined by the TAPE_JUKEBOXES symbol: $ ABS_JUKE := "NODE01::$1$DUA810:,NODE01::$1$MUA43: Where: o NODE01::$1$DUA810: is the robot changer name o NODE01::$1$MUA43: is the node name plus the drive name of the media loader ________________________ Note ________________________ The robot device name and the tape drive names must be prefixed with a node name. ______________________________________________________ 5. Define the media triplets. Media triplets are a set of symbols used to associate types of media with drives capable of accessing them. Use the following example as a guideline: Example:_Defining_the_Media_Triplets_for_a_Media_Loader $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := $1$MUA43:,$1$MUA44: 6. Shut down and restart MDMS to enable all the changes made to the TAPESTART.COM file. Use the following command: $ @SLS$SYSTEM:SLS$SHUTDOWN $ @SYS$STARTUP:SLS$STARTUP Installing the Software 3-21 Installing the Software 3.2 MDMS Postinstallation Tasks 3.2.7.2 Test the MDMS Configuration This procedure guides you through testing the MDMS configuration. ________________________ Note ________________________ Before you perform the procedure, you must have an initialized volume that is compatible with the drive in the media loader. Use this initialized volume to perform this test. ______________________________________________________ If you have MRU software, you can take this opportunity to learn more about the nature of the managed media environment. Compare the results of the STORAGE and ROBOT commands, or use MRU to verify the state of the media loader after issuing a STORAGE command. Issue STORAGE and ROBOT commands at the DCL prompt. 1. Check the response of the media loader to MDMS. Issue the STORAGE SHOW JUKEBOX command: $ STORAGE SHOW JUKEBOX [tape_jukebox_name] Issue the ROBOT SHOW ROBOT command and compare the results: $ ROBOT SHOW ROBOT [robot_name] 2. Add a volume to the volume database with the STORAGE ADD VOLUME command: $ STORAGE ADD VOLUME volume_id 3. Verify the volumes you just added with the STORAGE SHOW VOLUME command: $ STORAGE SHOW VOLUME volume_id 4. Prepare to reply to MDMS requests with the OpenVMS OPCOM REPLY command: $ REPLY/ENABLE=TAPES 5. Add a magazine to the media management database by issuing the STORAGE ADD MAGAZINE command: $ STORAGE ADD MAGAZINE magazine_name /SLOTS=n 3-22 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks 6. Place the volume into the magazine and bind it with the STORAGE BIND command: $ STORAGE BIND volume_id magazine_name /SLOT=n 7. Verify the volume has been bound to the magazine with the STORAGE SHOW MAGAZINE command: $ STORAGE SHOW MAGAZINE [volume_id magazine_name] 8. Issue the STORAGE IMPORT MAGAZINE command and insert the magazine into the loader: $ STORAGE IMPORT MAGAZINE magazine_name tape_jukebox_name 9. Load the volume into the drive with the STORAGE LOAD command: $ STORAGE LOAD drive-name volume-id Using the ROBOT SHOW DRIVE command, validate the volume has been loaded: $ ROBOT SHOW [ROBOT robot_name] DRIVE [[[drv_number]],...] 10.Unload the volume from the drive using the STORAGE UNLOAD command: $ STORAGE UNLOAD VOLUME volume-id Using the ROBOT SHOW SLOT command, validate the volume has been returned to the slot from which it was loaded: $ ROBOT SHOW [ROBOT robot_name] SLOT [[[slot_number]|[slot_number-slot_number]],...] 11.Remove the magazine from the loader with the STORAGE EXPORT MAGAZINE command: $ STORAGE EXPORT MAGAZINE magazine_name] 3.2.8 Configuring for an Operator Attended Drive If your storage management environment has an operator attended drive or drives, you must define the drive(s) in the MDMS file SYS$MANAGER:TAPESTART.COM. You must then test the configuration to make sure it is correct. Installing the Software 3-23 Installing the Software 3.2 MDMS Postinstallation Tasks 3.2.8.1 Configure MDMS The following procedure requires you to edit the SYS$MANAGER:TAPESTART.COM file. You can use any ASCII text editor to accomplish these edits. 1. Identify the primary processing node. Define the symbol PRI to the name of the node or the OpenVMS Cluster alias name executing the MDMS server. If you defined the symbol PRI to the OpenVMS Cluster alias, you must define the symbol DB_NODES to the names of the nodes in the OpenVMS Cluster system that you want to allow to be an MDMS server. 2. Identify the node on which the current TAPESTART.COM file resides. Define the NODE symbol to that name. 3. Define the media triplets. Media triplets are a set of symbols used to associate a media type with the drives capable of accessing them. Use the following example as a guideline: Example:_Defining_a_Media_Triplet_for_an_Operator_Attended_Drive $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := $1$MUA560:,$1$MUA561:,$1$MUA562: 4. Decide whether operator intervention and acknowledgment is needed then define the QUICKLOAD symbol accordingly. 5. Configure the Volume Pools. Use the MDMS Administrators Menu. From OpenVMS, issue the SLSMGR command. More_information: For detailed information about the MDMS menus, refer to the Media and Device Management Services for OpenVMS Guide to Operations. 6. Shut down and restart MDMS to enable all the changes made to the TAPESTART.COM file. Use the following command: $ @SYS$STARTUP:SLS$STARTUP 3-24 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks 3.2.8.2 Test the MDMS Configuration This procedure guides you through testing the MDMS configuration. Issue STORAGE commands at the DCL prompt. 1. Add a volume to the volume database with the STORAGE ADD VOLUME command: $ STORAGE ADD VOLUME volume_id 2. Verify the volumes you just added with the STORAGE SHOW VOLUME command: $ STORAGE SHOW VOLUME volume_id 3. Prepare to reply to MDMS requests with the OpenVMS OPCOM REPLY command: $ REPLY/ENABLE=TAPES 4. Load the volume into the drive with the STORAGE LOAD command: $ STORAGE LOAD drive-name volume-id 5. Unload the volume from the drive using the STORAGE UNLOAD command: $ STORAGE UNLOAD VOLUME volume-id Additional_Information: For additional information about configuring MDMS to work with particular media and drives, see Media and Device Management Services for OpenVMS Guide to Operations. 3.2.9 Configuring Remote Tape or Optical Drives If you answered "Yes" to either of the remote support prompts during the MDMS installation procedure, then MDMS automatically installed the RDF software. Table 3-7 describes how to configure the files SLS$ROOT:[TTI_RDEV]CONFIG_nodename.DAT and SYS$MANAGER:TAPESTART.COM to enable remote drive selection. Installing the Software 3-25 Installing the Software 3.2 MDMS Postinstallation Tasks Table_3-7_Enabling_Remote_Drive_Selection________________________ On the system where the tape or On the system where the data optical_drive_resides________________to_back_up_resides__________ Configure the file SLS$ROOT:[TTI_ N/A DEV]CONFIG_nodename.DAT to contain the tape drive names. See Section 3.2.9.1. Configure media triplets in the Configure media file SYS$MANAGER:TAPESTART.COM triplets in the file and define the drives as local SYS$MANAGER:TAPESTART.COM drives (Do not include a node name and define the drives as prefix). See Section 3.2.9.1. remote drives (include a node name prefix). See _____________________________________Section_3.2.9.2.____________ 3.2.9.1 On The System Where the Tape or Optical Drive Resides Use the following procedure to configure SLS$ROOT:[TTI_RDEV]CONFIG_nodename.DAT and SYS$MANAGER:TAPESTART.COM on the system where the drive resides: 1. Determine which tape or optical drive(s) will receive the backup data. 2. Check the file SLS$ROOT:[TTI_RDEV]CONFIG_nodename.DAT to make sure the drives are defined in this file. The installation procedure creates a drive configuration file named SLS$ROOT:[TTI_RDEV]CONFIG_nodename.DAT. In this file, include the drive names you wish to use for remote backup operations. Example_of_SLS$ROOT:[TTI_RDEV]CONFIG_nodename.DAT: ! The format of this configuration file is: ! ! DEVICE servable_device [characteristic1,...] !--------------------------------------------------------------- device $1$MUA200: MUA200 device $1$MUA210: MUA210 device $1$MUA220: MUA220 3-26 Installing the Software Installing the Software 3.2 MDMS Postinstallation Tasks 3. Edit the file SYS$MANAGER:TAPESTART.COM and make sure the drives appear as local drives (do not prefix the drive name with a node name). Create media triplets that define the media type, density, and corresponding drive name. The drive name must consist of either a physical name or the characteristic name of the drive or drives available for remote backup operations. Example_of_SYS$MANAGER:TAPESTART.COM: ! Media triplet definitions $ MTYPE_8 := TK86K $ DENS_8 := $ DRIVES_8 := $1$MUA200: $! $ MTYPE_9 := NODE01TK85K $ DENS_9 := NOCOMP $ DRIVES_9 := $1$MUA210: $! $ MTYPE_10 := NODE01TK85K_COMP $ DENS_10 := COMP $ DRIVES_10 := $1$MUA220: Restriction: Media type names cannot exceed 16 characters. 3.2.9.2 On The System Where the Data Resides On the system that contains the disks with the data you want to back up, add one or more media triplets that define the remote drive names in the SYS$MANAGER:TAPESTART.COM file. Media triplets define the media type, density, and corresponding drive name. The drive name must consist of either a physical name or the characteristic name of the drive or drives available for remote backup operations. Include the node name where the drive is physically connected. If you also have drives that are local to this system, do not assign the node name to those drives. Installing the Software 3-27 Installing the Software 3.2 MDMS Postinstallation Tasks Example_of_SYS$MANAGER:TAPESTART.COM: ! Media triplet definitions $ MTYPE_8 := TK86K $ DENS_8 := $ DRIVES_8 := NODE01::$1$MUA200: $! $ MTYPE_9 := NODE01TK85K $ DENS_9 := NOCOMP $ DRIVES_9 := NODE01::$1$MUA210: $! $ MTYPE_10 := NODE01TK85K_COMP $ DENS_10 := COMP $ DRIVES_10 := NODE01::$1$MUA220: See Media and Device Management Services for OpenVMS Guide to Operations for additional information about creating media triplets and defining remote drives. 3.3 Installing the ABS Software Now that you have successfully installed and configured the MDMS software, see Table 3-8 for the stages of installing and configuring the ABS Version 2.1B software. ________________________ Note ________________________ Before installing ABS in a real-time, storage management environment, DIGITAL recommends that you first install and configure ABS in a test environment. If you are not satisfied with the test installation and configuration, delete ABS and reinstall it. How_to_delete_ABS_from_your_system: To delete the ABS software from your system, shut down ABS and delete it from the system: $ @SYS$MANAGER:ABS$SHUTDOWN $ @ABS$SYSTEM:DELETE_ABS ______________________________________________________ 3-28 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-8_Stages_of_Installing_the_ABS_Software____________ Stage__Action______________________________________________ 1 Install the ABS server software as described in Section 3.3.1. Note: If you are installing ABS in a mixed-architecture environment (VAX and Alpha systems), follow the installation instructions in Section 3.3.2. 2 Install the ABS OpenVMS client software as described in Section 3.3.3. 3 Install the ABS NT client software as described in Section 3.3.4. 4 Install ABS UNIX clients as described in Section 3.3.5. 5 Authorize NT and UNIX clients as described in Section 3.3.6. 6 Verify the ABS installation procedure as described in Section 3.4.1. 7 Edit the system startup and shutdown files as described in Section 3.4.2. 8 Verify that all OpenVMS Cluster requirements have been met as described in Section 3.4.3. 9 Verify that all default policy objects are resident on the ABS server node as described in Section 3.4.5. 10 Modify the default policy objects as described in Section 3.4.5.2. 11 Verify the tape drive connections as described in _______Section_3.4.6.______________________________________ 3.3.1 Installing the ABS Server Software The ABS installation procedure consists of a series of questions and informational messages. Appendix A provides a sample installation log file. 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 Installing the Software 3-29 Installing the Software 3.3 Installing the ABS Software up to that point and then exits. From this point, you can restart the installation procedure again. Follow the steps in Table 3-9 to install ABS Version 2.1B server software. Table_3-9_How_to_Install_the_ABS_Software________________________ Step_Action______________________________________________________ 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: saveset-name The installation name for the component. ABSB021 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. 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. (continued on next page) 3-30 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 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. See the OpenVMS documentation on software installation in the OpenVMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). Example: The following examples invoke VMSINSTAL to install ABS from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release note parameter. $ @SYS$UPDATE:VMSINSTAL ABSB021 MTA0: OPTIONS N OpenVMS VAX Software Product Installation Procedure V6.1 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. (continued on next page) Installing the Software 3-31 Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 2 Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press RETURN. Otherwise, enter NO to abort the installation. After you back up your system disk, you can restart the installation. (continued on next page) 3-32 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ (continued on next page) Installing the Software 3-33 Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 3 Select a release notes option. Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the following options for reviewing the release notes. IF you select . . . o Option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. o Option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can press RETURN to send the file to the default output print device or you can enter another queue name. o Option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. o Option 4, the release notes are not displayed or printed. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press RETURN. In either case, the release notes are copied to the SYS$HELP::ABSB021.RELEASE_NOTES file. The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. Do 3-34 nottdelete releasetnotes for previous versions of ABS. (continued on next page) Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 4 Purge files * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of ABS that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. 5 Choose the Installation Verification Procedure (IVP) option. * Do you want to run the IVP after the installation [YES]? The installation procedure now asks if you want to run the IVP. The IVP for ABS checks to be sure that the installation is successful. It is recommended that answer Yes to this prompt. If errors occur during the installation procedure, VMSINSTAL displays the following message: %VMSINSTAL-E- INSFAIL, The installation of ABS Version 2.1B has failed. Note: If you answered No to this prompt, after ABS is installed you can run the IVP independently to verify that the software is available on your system. Also, you may need to run the IVP after a system failure to make sure that users can access ABS. Section 3.4.1 describes how to independently run the IVP. (continued on next page) Installing the Software 3-35 Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 6 Respond to license registration queries. SLS SLS-ACS SLS-MGR SLS-REMOTE SLS-REMOTE-MGR PAB-UNIX-CLIENT-USER ABS-NT-CLIENT-USER * Does this product have an authorization key registered and loaded? The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You must register and load the PAK to successfully complete the installation. If you have not done so, stop the installation, register and load the PAK, and restart the installation. 7 Choose the ABS$ROOT disk device: * Enter the disk device name to use for ABS files [SYS$COMMON]: This disk device will contain the ABS images, databases, and log files. Requirement: This disk device must have at least 40,000 free blocks and be available to all nodes in the OpenVMS Cluster that will be running ABS. 8 Enter the ABS account UIC: * Enter the UIC to be used for ABS account [[311,311]]: The ABS account is not an interactive account and is used only for ABS processes. The password for the ABS account is automatically generated by the installation procedure. If you choose to change the default UIC assignment, it must be unique and it cannot be a member of a SYSTEM UIC group. (continued on next page) 3-36 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 9 Choose the policy engine node or OpenVMS Cluster: * Cluster or node list for ABS Policy Engine [SVNODE::]: SVNODE Enter the OpenVMS Cluster or OpenVMS node name that you have designated to house the ABS policy engine database. This OpenVMS Cluster or node becomes the ABS server node, sometimes referred to as the central security domain (CSD). Note: The policy engine node information resides in the file ABS$SYSTEM:ABS$POLICY_CONFIG.DAT. If at some point in time you want to change the location of the ABS server, you can edit this file to change the policy engine (server) location without having to reinstall ABS. Locate the last line in the file and change the node information: ABS$POLICY_ENGINE_LOCATION = NODESV:: Do not change any other information in this file. 10 Read the informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. The following messages are displayed: %VMSINSTAL-I- MOVEFILES, files will now be moved to their target directories... 11 Observe the installation Verification Procedure (IVP). If you chose to run the IVP in Step 7, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: (continued on next page) Installing the Software 3-37 Installing the Software 3.3 Installing the ABS Software Table_3-9_(Cont.)_How_to_Install_the_ABS_Software________________ Step_Action______________________________________________________ 12 End the installation procedure. Installation of ABS Version 2.1B completed at 12:46 VMSINSTAL procedure done at 12:47 The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 21-JUL-1996 12:50:00:00 Note: Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should _____log_out_and_log_in_again.___________________________________ 3.3.2 Installing ABS in a Mixed-Architecture OpenVMS Cluster If you are installing ABS on an OpenVMS Cluster system that contains both both VAX and Alpha systems, you must meet the following requirements and install ABS as described in Table 3-10. Requirements: o The version of ABS must be the same on the OpenVMS VAX and the OpenVMS Alpha system(s). o If you are using Oracle Rdb for the policy database, the versions of Oracle Rdb installed on the OpenVMS VAX and OpenVMS Alpha system(s) must be compatible. For example, you cannot have Oracle Rdb Version 6.0 on the OpenVMS Alpha system and Oracle Rdb Version 5.1 on the OpenVMS VAX system. Those two versions of Oracle Rdb are not compatible. To ensure that ABS functions correctly, each architecture must have its own set of .EXE and .UID files, but all other files required by ABS can be shared by both the VAX and Alpha system(s) on a common disk. 3-38 Installing the Software Installing the Software 3.3 Installing the ABS Software To accomplish this, follow the procedure described in Table 3-10. Table 3-10 Installing ABS in a Mixed-Architecture OpenVMS ___________Custer__________________________________________ Step_Actions_______________________________________________ 1 Install ABS on the VAX system in the OpenVMS Cluster as instructed in Section 3.3.1. When the installation procedure prompts for the disk name to use for ABS files (Step 9 in Table 3-9), enter the disk name that can be accessed by both the VAX and Alpha system in the OpenVMS Cluster. For example, assume that the VAX system has a disk named DISK$SYSTEM_1 that is common to both the VAX and Alpha nodes in the OpenVMS Cluster (see Figure 3-1). Result: The installation procedure creates a directory named DISK$SYSTEM_1:[ABS] (which translates to ABS$ROOT) on the VAX system and also creates all of its subdirectories. 2 Create two new directories on the common disk that will contain the .EXE and .UID files for the VAX and Alpha systems: $ CREATE/DIRECTORY ABS$ROOT:[SYSTEM.VAX] $ CREATE/DIRECTORY ABS$ROOT:[SYSTEM.ALPHA] 3 Move the .EXE and .UID files from the VAX installation to the VAX directory: $ SET DEFAULT ABS$ROOT:[SYSTEM] $ RENAME *.EXE,*.UID [.VAX] 6 Install ABS on the OpenVMS Alpha system in the OpenVMS Cluster as instructed in Section 3.3.1. When the installation procedure prompts for a disk name to use for ABS files, enter one the Alpha disks. For example, assume that the Alpha system has a disk named DISK$ALPHA. (continued on next page) Installing the Software 3-39 Installing the Software 3.3 Installing the ABS Software Table 3-10 (Cont.) Installing ABS in a Mixed-Architecture ___________________OpenVMS_Custer__________________________ Step_Actions_______________________________________________ Result: The installation procedure creates a directory named DISK$ALPHA:[ABS] (which translates to ABS$ROOT) on the Alpha system and also creates all of its subdirectories (see Figure 3-1). 6 Copy the .EXE and .UID files from the Alpha installation to the appropriate directory on the common disk located on the VAX system: $ SET DEFAULT ABS$ROOT:[SYSTEM] $ COPY *.EXE,*.UID DISK$SYSTEM_1:[ABS.SYSTEM.ALPHA] 6 Edit the file SYS$STARTUP:ABS$ALTERNATE_ROOT.COM on both the VAX and Alpha systems. Define the logical ABS$ROOT to point to the common disk on the VAX system: $ Define/System/Exec/Trans=Conc ABS$ROOT DISK$SYSTEM_1:[ABS.] $ Exit (continued on next page) 3-40 Installing the Software Installing the Software 3.3 Installing the ABS Software Table 3-10 (Cont.) Installing ABS in a Mixed-Architecture ___________________OpenVMS_Custer__________________________ Step_Actions_______________________________________________ 7 Edit the file SYS$STARTUP:ABS$STARTUP.COM on both the VAX and Alpha systems. Define the logical ABS$SYSTEM to be a search list: VAX_system: . . . $! $ SysDefine ABS_SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.VAX] $ SysDefine ABS$SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.VAX] . . . Alpha_system: . . . $! $ SysDefine ABS_SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.ALPHA] $ SysDefine ABS$SYSTEM ABS$ROOT:[SYSTEM],ABS$ROOT:[SYSTEM.ALPHA] . . . (continued on next page) Installing the Software 3-41 Installing the Software 3.3 Installing the ABS Software Table 3-10 (Cont.) Installing ABS in a Mixed-Architecture ___________________OpenVMS_Custer__________________________ Step_Actions_______________________________________________ 8 Edit the file ABS$SYSTEM:ABS$POLICY_CONFIG.DAT on the common disk to include both the VAX and Alpha node names: . . . $ ABS$POLICY_ENGINE_LOCATION = NODE_V:: $ ABS$POLICY_ENGINE_LOCATION = NODE_A:: 9 Shutdown and restart ABS on both the VAX and Alpha systems by entering the following command at the system prompt on each system: $ @SYS$MANAGER:ABS$SHUTDOWN _____$_@SYS$STARTUP:ABS$STARTUP____________________________ ________________________ Note ________________________ To increase disk space, once you have copied the .EXE and .UID files to the common disk, you can delete the extra ABS files on the Alpha system: $ SET DEFAULT ALPHA$DISK:[ABS] $ DELETE *.*;* You may have to set protections on directories to delete those files. ______________________________________________________ 3.3.3 Installing the ABS OpenVMS Client Software When installing the ABS software, notice that ABS does not provide two separate software kits. Instead, installation of the ABS OpenVMS server or client software is determined by the OpenVMS Cluster alias name or OpenVMS node name that you enter during the installation procedure. 3-42 Installing the Software Installing the Software 3.3 Installing the ABS Software Table 3-11 describes how to install and configure an ABS OpenVMS client. Table 3-11 Installing and Configuring the ABS OpenVMS ___________Client_Software_________________________________ Step_Action________________________________________________ Note: In this example the ABS server node is SVNODE:: and the ABS client node is CLNODE:: 1 Install the ABS software on the OpenVMS client node. Following the steps in Table 3-9 except replace Step 11 with the following information: When the installation procedure prompts for the node name where the ABS policy engine resides (the ABS OpenVMS server node), do not accept the default node name (client node). Instead, enter the OpenVMS Cluster alias or OpenVMS node name that you entered when you installed the ABS OpenVMS server software: * cluster or node list for ABS policy engine [CLNODE::] : SVNODE Result: ABS installs only the client portion of the ABS software on the node named CLNODE. (continued on next page) Installing the Software 3-43 Installing the Software 3.3 Installing the ABS Software Table 3-11 (Cont.) Installing and Configuring the ABS ___________________OpenVMS_Client_Software_________________ Step_Action________________________________________________ 2 After installing the ABS software on the OpenVMS client node, create a proxy account for the ABS OpenVMS server node on the ABS OpenVMS client node. Because ABS uses POLYCENTER Scheduler as its mechanism to submit save and restore requests, POLYCENTER Scheduler requires a proxy account to submit a save or restore request from the OpenVMS client node. On the ABS OpenVMS client node (CLNODE::), enter the following set of DCL commands: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> ADD/PROXY SVNODE::ABS ABS/DEFAULT UAF> EXIT Result: These commands allow CLNODE:: to submit a save or restore request from the client node. 3 Create save and restore requests for OpenVMS clients as described in Archive/Backup System for OpenVMS Guide to Operations. 4 Create (or modify) storage classes and execution environments that meet system and user backup requirements. Archive/Backup System for OpenVMS Guide to Operations describes how to create those policy objects. 5 Create system and user backup operations using the correct storage classes and execution environments. Archive/Backup System for OpenVMS Guide to Operations _____describes_how_to_do_this._____________________________ 3.3.4 Installing and Configuring ABS NT Clients _____________________ Requirement _____________________ Before installing the NT client software, the eXcursion software must already be installed on the NT client system. ______________________________________________________ 3-44 Installing the Software Installing the Software 3.3 Installing the ABS Software Table 3-12 describes the stages of installing and configuring an ABS NT client node. Table 3-12 Stages of Installing and Configuring an ABS NT ___________Client__________________________________________ Stage_Action_______________________________________________ 1 Register the ABS NT license on the ABS OpenVMS server node. See Section 2.11. 2 Install the ABS NT client software on the NT client system as described in Table 3-13. Note: You must perform a separate installation on each NT client that you want ABS to back up. 3 Authorize the NT client systems that you plan to back up using ABS (described in Section 3.3.6 and Appendix B). 4 Create save and restore requests for the NT client system by using the GUI on the NT client system, or by using the GUI or DCL on the ABS OpenVMS server node. See Archive/Backup System for OpenVMS Guide to Operations and Archive/Backup System for OpenVMS Reference Guide for instructions about creating save ______and_restore_requests_for_NT_clients._________________ To install and configure the NT client software, follow the procedure in Table 3-13. Installing the Software 3-45 Installing the Software 3.3 Installing the ABS Software Table_3-13_Installing_and_Configuring_an_NT_Client_________ Step_Action________________________________________________ 1 Copy all files from the appropriate directory on the ABS OpenVMS server node to the NT client system where you plan to install the NT client software, or to a location accessible by the NT client system. The NT client software is provided during the ABS server installation procedure. ABS creates the appropriate directories and places the NT client software kits for Alpha and Intel systems in those directories: ABS$ROOT:[NTCLIENT.ALPHA] ABS$ROOT:[NTCLIENT.INTEL] (continued on next page) 3-46 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-13_(Cont.)_Installing_and_Configuring_an_NT_Client_ Step_Action________________________________________________ 2 Run SETUP.EXE from this location to install ABS NT client software. Result: The ABS NT client installation procedure prompts for information about the ABS server and the local host port number. Answer these prompts exactly as you answered them during the ABS server installation procedure: o ABS server node Enter the node on which the ABS server software has been installed and will be providing ABS services for the NT client backup operations. This node also verifies connection requests. o Local host port number The NT client system uses a TCP/IP port to communicate with the 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 authorizing NT clients. Note: Make sure that the number you provide does not conflict with a previously installed software application. 3 Authorize the NT clients you plan to back up using ABS _____as_described_in_Section_3.3.6_and_Appendix_B._________ 3.3.5 Configuring ABS UNIX Clients To allow ABS to perform backup and restore operations for UNIX clients, you must configure access between the OpenVMS systems that run the ABS server software and the UNIX client systems that contain the files to be backed up. The stages of installing and configuring a UNIX client is described in Table 3-14. Installing the Software 3-47 Installing the Software 3.3 Installing the ABS Software ________________________ Note ________________________ There is no software kit provided for UNIX clients. ______________________________________________________ Table_3-14_Stages_of_Configuring_a_ABS_UNIX_Client_________ Stage_Action_______________________________________________ 1 Register and load the UNIX license on the ABS OpenVMS server node. See Section 2.11. 2 Modify the appropriate files on the UNIX client system as described in the Section 3.3.5.1. 3 Transfer the gtar and gzip sources from the ABS OpenVMS server node to each UNIX client system that you intend to back up using ABS. See Section 3.3.5.2. 4 Build the executables on each UNIX client system that you plan to back up using ABS as described in Section 3.3.5.3. 5 Authorize the UNIX clients as described in Section 3.3.6 and Appendix B. 6 Create save and restore requests for the UNIX client system from the OpenVMS server node. See Archive /Backup System for OpenVMS Guide to Operations and Archive/Backup System for OpenVMS Reference Guide for instructions about creating save and restore requests ______for_UNIX_clients.____________________________________ 3.3.5.1 Modifying the Appropriate UNIX Files Table 3-15 lists the files that you need to modify on each UNIX client system that ABS is going to back up, and it describes the modifications to make for those specific files. ________________________ Note ________________________ UNIX is a case-sensitive system. Be sure to enter the commands on the UNIX client system exactly as they are shown in Table 3-15 and Example 3-1. ______________________________________________________ 3-48 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-15_Modifying_the_Appropriate_UNIX_Files__________________ File________Modification_________________________________________ Replace the ASCII readable internet address with the /.rhosts[1] 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.on.exp with the 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 because ABS uses this directory during the backup operation. [1]File_is_not_replaced,_only_modified.__________________________ (continued on next page) Installing the Software 3-49 Installing the Software 3.3 Installing the ABS Software Table_3-15_(Cont.)_Modifying_the_Appropriate_UNIX_Files__________ File________Modification_________________________________________ /etc List the numeric internet address and the ASCII /hosts[1] readable internet address of the 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: o nn.nn.nn.nn is the numeric internet address of the ABS node that executes save and restore requests. o 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 the ABS OpenVMS server nodes are already listed in the file /etc/hosts, you do not need to add them to the file. [1]File_is_not_replaced,_only_modified.__________________________ _________________________________________________________________ 3.3.5.2 Transferring the UNIX Backup Agent Sources During the installation of the ABS server software, the installation procedure creates a directory named ABS$ROOT:[CLIENTS] on the ABS server node. This directory contains the following two uncompressed sources that make up the UNIX backup agent: o ABS$ROOT:[CLIENTS]TAR-1_11_8.TAR o ABS$ROOT:[CLIENTS]GZIP-1_2_4.TAR To configure a UNIX client, you must transfer the gtar and gzip sources to each UNIX client system that ABS is going to back up, build the executables, and place them in /usr /bin. 3-50 Installing the Software Installing the Software 3.3 Installing the ABS Software Refer to Example 3-1 (shown from a Digital UNIX system) to transfer the gtar and gzip sources from the ABS server node to the UNIX client system. Example 3-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] # Change to the directory that contains the files 250 CWD command successful. ftp> pwd 257 "ABS$ROOT:[CLIENTS]" 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_11_8.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_11_8.tar (local-file) tar-1_11_8.tar 200 PORT command successful. 150 Opening data connection for tar-1_11_8.tar (16.82.16.75,1178) 226 Transfer complete. 2662400 bytes received in 5.7 seconds (4.6e+02 Kbytes/s) (continued on next page) Installing the Software 3-51 Installing the Software 3.3 Installing the ABS Software Example 3-1 (Cont.) Transferring the Backup Agent Sources 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. 3.3.5.3 Building the UNIX Executables After you have transferred the gtar and gzip sources, you are required to build the executables on the UNIX client system. The following sections describe how to build the tar and gzip executables. 3.3.5.4 Building the tar Executable Use the following procedure to build the tar executable: 1 Use native tar to expand the tar file 2 Change directory to the tar directory 3 Enter the command configure - -disable-nls 4 Enter the command make to build the tar image 5 Verify the tar image was created 6 Change directory to src 7 Verify that it is an executable image 8 Change to super user 9 Copy the executable from src/tar to usr/bin/ABSgtar 10 Change the protection on the image 11 Display the complete directory 12 Exit super user 13 Perform a cleanup operation 3-52 Installing the Software Installing the Software 3.3 Installing the ABS Software Example_of_tar: u_node> tar -xvf tar-1_11_8.tar 1 tar-1.11.8/README tar-1.11.8/AUTHORS . . . tar-1.11.8/po/sv.gmo u_node> cd tar-1.11.8 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.11.8/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.11-8 Installing the Software 3-53 Installing the Software 3.3 Installing the ABS Software 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_11_8 13 %rm -f tar-1_11_8.tar 13 3.3.5.5 Building the gzip Executable Use the following procedure to build the gzip executable: 1 Use the native tar to expand the gzip-1_2_4.tar image 2 Change directory to gzip-1.2.4 3 Enter the command configure 4 Enter the command make 5 Verify that the gzip file is there 6 Make sure it is an executable 7 Change to super user 8 Copy the file from gzip to /usr/bin/ABSgzip 9 Change the protection on the image 10 Exit super user 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 3-54 Installing the Software Installing the Software 3.3 Installing the ABS Software 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 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 u-node Installing the Software 3-55 Installing the Software 3.3 Installing the ABS Software If you have problems transferring or building the tar or gzip files, see your UNIX system manager. 3.3.6 Authorizing NT and UNIX Clients After you have registered and loaded the NT or UNIX client license on the ABS server node, run the authorization executable file to authorize the NT or UNIX client node names that you intend to back up using ABS. You must authorize access on the ABS OpenVMS server system for each UNIX and NT system that you are going to back up using ABS. Table 3-16 describes how to authorize NT and UNIX client nodes. ________________________ Note ________________________ ABS NT and 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 NT or UNIX clients than the number of units allowed by the NT or UNIX client license that you have purchased. ______________________________________________________ Table_3-16_Authorizing_NT_or_UNIX_Client_Nodes_____________ Step___Action______________________________________________ 1. Enter the following command from the ABS server: $ RUN ABS$SYSTEM:ABS_CLIENT_LICENSE.EXE 2. Add the node names of the UNIX or NT client nodes. When prompted, specify if it is 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]: (continued on next page) 3-56 Installing the Software Installing the Software 3.3 Installing the ABS Software Table_3-16_(Cont.)_Authorizing_NT_or_UNIX_Client_Nodes_____ Step___Action______________________________________________ 3. If the client node is an NT client, enter the port number. The default is 1800. 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___________________ For an example of adding, modifying, removing and showing NT or UNIX clients, see Appendix B. 3.4 ABS Postinstallation Tasks Complete the ABS postinstallation tasks described in Sections 3.4.1 through 3.4.6. These tasks apply whether you have installed the ABS server or ABS OpenVMS client software. 3.4.1 Verifying the ABS Installation If you did not execute the IVP during the installation procedure, you can execute it immediately after installing the ABS software. Enter the following command at the DCL system prompt: $ @SYS$TEST:ABS$IVP.COM If an error occurs during the IVP, the following message is displayed: ABS Version 2.1B Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for ABS Version 2.1B has failed. Errors can occur during the installation if any of the following conditions exist: o ABS is currently running. o The operating system version is incorrect. o A prerequisite software version is incorrect. Installing the Software 3-57 Installing the Software 3.4 ABS Postinstallation Tasks o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS help library is currently in use. o The product license has not been registered and loaded. 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. 3.4.2 Providing Automatic Start Up and Shut Down You must edit the startup and shutdown files to provide automatic startup and shutdown of the ABS software. To make sure that ABS automatically starts up and shuts down, follow these steps: 1. Add the following command line to the system startup file SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$STARTUP:ABS$STARTUP 2. Add the following line to the system shutdown file, SYS$MANAGER:SYSHUTDOWN.COM: $ @SYS$MANAGER:ABS$SHUTDOWN 3.4.3 Meeting OpenVMS Cluster Requirements If you installed the ABS server software on a node in an OpenVMS Cluster system, perform the following tasks on each node (excluding the installing node) in the OpenVMS Cluster where you want to use ABS: o Run the common file ABS$STARTUP from each node that you want to use ABS. This ensures the ABS$ logical names are defined the same across all nodes in the OpenVMS Cluster: $@ABS_SERVER_DISK:[ABS.STARTUP]ABS$STARTUP.COM o Update the DCL table on each node in the OpenVMS Cluster (excluding the installing node). 3-58 Installing the Software Installing the Software 3.4 ABS Postinstallation Tasks Enter the following command on each node: $ INSTALL REPLACE SYSLIBRARY:DCLTABLES.EXE o Have all system users log out and log in again so they can use the DCL ABS commands (unless performing an upgrade). 3.4.4 Granting the Appropriate ABS Access Right Identifiers When the ABS installation procedure is complete, the user account that performed the installation (typically the system account) is granted the following access rights identifiers: o ABS_CREATE_STORAGE_CLASS-Users who are granted this access right identifier can create a storage class (only applicable on the ABS server system). o ABS_CREATE_EXECUTION_ENV-Users who are granted this access right identifier can create an execution environment (only applicable on the ABS server system). o ABS_SHOW_ALL-Users who are granted this access right identifier can show all ABS policy objects (only applicable on the ABS server system). o ABS_LOOKUP_ALL-Users who are granted this access right identifier can look up all ABS archive data objects from any catalog (applicable on any ABS node). o ABS_CREATE_REMOTE_JOBS-Users who are granted this access right identifier can submit a save or restore request that will be executed on a remote client node (only applicable on the ABS server system). Requirement: To perform NT or UNIX backup operations, the requester must have the ABS_CREATE_REMOTE_JOBS access rights identifier enabled. o ABS_BYPASS - Users who are granted this access right identifier can perform any ABS function (only applicable on the ABS server system). This includes creating, deleting, modifying, or showing any ABS policy objects. Installing the Software 3-59 Installing the Software 3.4 ABS Postinstallation Tasks 3.4.4.1 Enabling an Access Rights Identifier You must run the AUTHORIZE utility to grant an access rights identifier to a user's account. Do not enable the access rights identifier by performing a SET RIGHTS_LIST at the DCL prompt. 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 3.4.4.2 Revoking An Access Rights Identifier To remove an access right identifier, run the 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 UAF>EXIT 3.4.5 Modifying ABS Default Policy Objects ABS provides a set of default policy objects so you can start using ABS for your backup operations immediately after installation. Table 3-17 lists the ABS default policy objects that are resident on your system when the installation procedure has successfully completed. Table_3-17_Default_Policy_Objects__________________________ Storage_Classes_______Execution_Environments_______________ ABS_ARCHIVE ABS_ARCHIVE_ENV DISASTER_RECOVERY DISASTER_RECOVERY_ENV SYSTEM_BACKUPS SYSTEM_BACKUPS_ENV (continued on next page) 3-60 Installing the Software Installing the Software 3.4 ABS Postinstallation Tasks Table_3-17_(Cont.)_Default_Policy_Objects__________________ Storage_Classes_______Execution_Environments_______________ USER_BACKUPS USER_BACKUPS_ENV UNIX_BACKUPS UNIX_BACKUPS_ENV ______________________DEFAULT_ENV__________________________ 3.4.5.1 Default Policy Object Attributes Each of the ABS default policy objects have the following attributes set at the completion of the installation procedure: o The owner of a default policy object is the user name of the account who installed the software (typically SYSTEM). o Access to a default policy object is allowed only from the ABS server node and by the ABS account. Upon completion of the ABS installation procedure, the ABS default objects enable you to create save and restore requests objects only from the ABS server node. At this point in time the default access controls are set to allow access only from the ABS server system; you cannot create a save or restore request object from an ABS client system. Attempting to run a save request from an ABS client system would cause an access violation to the default storage classes, with the exception of the USER_BACKUPS storage class. The USER_BACKUPS storage class default attributes allows users from ABS client systems to create save and restore requests. To enable access to the other default ABS policy objects by ABS client systems, you must modify the default policy objects as described Section 3.4.5.2.) 3.4.5.2 Modifying Default Policy Objects ABS provides a number of default policy objects (shown in Table 3-17) that allow you to quickly perform ABS operations. Because the installing account has been granted the ABS_ BYPASS access right identifier, only this account can access the ABS default policy objects at this point in time. Installing the Software 3-61 Installing the Software 3.4 ABS Postinstallation Tasks For maintenance purposes, modify the ABS default policy objects in the following manner: 1. Add the storage administrator as a user to the ABS default policy objects. Grant the CONTROL access right identifier to the storage administrator's account so that he can modify the ABS default policy objects. DCL_Example: $ ABS STORAGE STORAGE SYSTEM_BACKUPS /ACCESS=(USER_ID=SMITH,ACCESS="CONTROL") Modify the policy objects that you want to enable access by ABS client systems from the ABS account. DCL_Example: $ ABS SET STORAGE SYSTEM_BACKUPS /ACCESS=(USER_ID=*::ABS) See Archive/Backup System for OpenVMS Guide to Operations for instructions about adding users and enabling access controls on ABS policy objects. 3.4.6 Performing a Backup, Lookup, and Restore Operation To make sure that you can use ABS for your backup and restore operations, use the following procedure to test your installation: o Log into the ABS server node under the same user account where you installed the software (SYSTEM). o Create a save request for the ABS server node and specify the file name provided by ABS for this test. Enter the following command: $ ABS SAVE ABS_TEST.DAT /NAME=TEST_SAVE/STORAGE=SYSTEM_BACKUPS o Verify that the file you saved is recorded in the ABS catalog by entering the ABS LOOKUP command: $ ABS LOOKUP ABS_TEST.DAT o Restore the file back to its original location using ABS. Enter the following command: $ ABS RESTORE ABS_TEST.DAT/CONFLICT_OPTIONS=NEW_VERSION o If you installed any ABS clients, log into one of the client nodes and create a save request. 3-62 Installing the Software 4 _________________________________________________________________ Performing Postinstallation Tasks This chapter describes the tasks you need to perform after installing the MDMS and ABS software: o Section 4.1 lists the steps for adding new media into management. This procedure applies during initial configuration and periodically thereafter. 4.1 Adding New Media into the Media Environment This section describes how to add more media into management. The procedures you use depend on the kind of media device you use for your storage management applications: o For an automated media library system, refer to Section 4.1.1. o For a media loader system, refer to Section 4.1.2. o For an operator managed system, refer to Section 4.1.3. 4.1.1 Adding Media for Automated Media Libraries This procedure describes how to add media for automated media libraries into the volume database: a. Prepare to respond to OPCOM messages generated by MDMS. Issue the OpenVMS OPCOM REPLY command: $ REPLY/ENABLE=TAPES b. For each volume, issue the STORAGE ADD VOLUME command: $ STORAGE ADD VOLUME volume_id Alternatively, you can use the MDMS Operator Menu, Maintenance option, Add Volume Series feature to add all volumes into the volume database. Performing Postinstallation Tasks 4-1 Performing Postinstallation Tasks 4.1 Adding New Media into the Media Environment c. To prepare the cartridges for access by the device, issue the STORAGE IMPORT CARTRIDGE command for each cartridge: $ STORAGE IMPORT CARTRIDGE volume_id tape_jukebox_name Alternatively, you can expose the internal storage slots and place the cartridges directly into the system. d. Select the drive you want to initialize your cartridges. Issue the STORAGE SELECT command: $ STORAGE SELECT logical-drive-name volume-id e. For each cartridge you have added to the database, initialize the media with these commands: a. Load the cartridge in the drive with the STORAGE LOAD command. Use the /NOCHECK qualifier: $ STORAGE LOAD/NOCHECK drive-name volume-id b. Initialize the media with the desired label with the OpenVMS INITIALIZE command: $ INITIALIZE device-name[:] volume-label c. Verify the media initialization with the OpenVMS MOUNT command: $ MOUNT device-name[:] volume-label d. Dismount the media with the OpenVMS DISMOUNT command: $ DISMOUNT device-name[:] e. Remove the media from the drive with the STORAGE UNLOAD command: $ STORAGE UNLOAD VOLUME volume-id f. After initializing the media, return the device to other applications with the OpenVMS DEALLOCATE command: $ DEALLOCATE device-name[:] g. Inventory the library with the STORAGE INVENTORY JUKEBOX command, specifying the slots with the SLOT_RANGE qualifier: $ STORAGE INVENTORY JUKEBOX/SLOT_RANGE=([start_slot,] count) tape_jukebox_name 4-2 Performing Postinstallation Tasks Performing Postinstallation Tasks 4.1 Adding New Media into the Media Environment h. Check each volume in the database with the STORAGE SHOW VOLUME command: $ STORAGE SHOW VOLUME volume_id 4.1.2 Adding Media for Media Loaders This procedure describes how to add media and magazines for media loaders into the volume database: 1. Prepare to respond to OPCOM messages generated by. MDMS. Issue the OpenVMS OPCOM REPLY command: $ REPLY/ENABLE=TAPES 2. For each volume of removable media, issue the STORAGE ADD VOLUME command: $ STORAGE ADD VOLUME volume_id Alternatively, you can use the MDMS Operator Menu, Maintenance option, Add Volume Series feature to add all volumes into the volume database. 3. For each magazine you intend to manage, issue the STORAGE ADD MAGAZINE command: $ STORAGE ADD MAGAZINE magazine_name /SLOTS=n 4. To load the media into the drive for initialization, you must bind it into a managed magazine. Use the STORAGE BIND command for each medium you bind into a managed magazine: $ STORAGE BIND volume_id magazine_name /SLOT=n 5. To prepare the magazine and its cartridges for access by the device, issue the STORAGE IMPORT MAGAZINE. Reply to the OPCOM message and insert the magazine into the device: $ STORAGE IMPORT MAGAZINE magazine_name tape_jukebox_name 6. Select the drive you want to initialize your cartridges. Issue the STORAGE SELECT command: $ STORAGE SELECT logical-drive-name volume-id 7. For each cartridge you have added to the database, initialize the media with these commands: a. Load the cartridge in the drive with the STORAGE LOAD command. Use the /NOCHECK qualifier: Performing Postinstallation Tasks 4-3 Performing Postinstallation Tasks 4.1 Adding New Media into the Media Environment $ STORAGE LOAD/NOCHECK drive-name volume-id b. Initialize the media with the desired label with the OpenVMS INITIALIZE command: $ INITIALIZE device-name[:] volume-label c. Verify the media initialization with the OpenVMS MOUNT command: $ MOUNT device-name[:] volume-label d. Dismount the media with the OpenVMS DISMOUNT command: $ DISMOUNT/NOUNLOAD device-name[:] e. Remove the media from the drive with the STORAGE UNLOAD command: $ STORAGE UNLOAD VOLUME volume-id 8. After initializing the media, return the device to other applications with the OpenVMS DEALLOCATE command: $ DEALLOCATE device-name[:] 9. Check each volume in the database with the STORAGE SHOW VOLUME command: $ STORAGE SHOW VOLUME volume_id 10.If necessary, remove the magazine from the device with the STORAGE EXPORT MAGAZINE command: $ STORAGE EXPORT MAGAZINE magazine_name 4.1.3 Adding Media for Operator Attended Drives This procedure describes how to add media for manually loaded drives into the volume database. 1. Prepare to respond to OPCOM messages generated by MDMS. Issue the OpenVMS OPCOM REPLY command: $ REPLY/ENABLE=TAPES 2. For each volume of removable media, issue the STORAGE ADD VOLUME command: $ STORAGE ADD VOLUME volume_id Alternatively, you can use the MDMS Operator Menu, Maintenance option, Add Volume Series feature to add all volumes into the volume database. 4-4 Performing Postinstallation Tasks Performing Postinstallation Tasks 4.1 Adding New Media into the Media Environment 3. Select the drive you want to initialize your cartridges. Issue the STORAGE SELECT command: $ STORAGE SELECT logical-drive-name volume-id 4. For each cartridge you have added to the database, initialize the media with these commands: 1. Place the cartridge in the drive with the STORAGE LOAD command. Use the /NOCHECK qualifier: $ STORAGE LOAD/NOCHECK drive-name volume-id 2. Initialize the media with the desired label with the OpenVMS INITIALIZE command: $ INITIALIZE device-name[:] volume-label 3. Verify the media initialization with the OpenVMS MOUNT command: $ MOUNT device-name[:] volume-label 4. Dismount the media with the OpenVMS DISMOUNT command: $ DISMOUNT device-name[:] 5. Remove the media from the drive with the STORAGE UNLOAD command: $ STORAGE UNLOAD VOLUME volume-id 5. After initializing the media, return the device to other applications with the OpenVMS DEALLOCATE command: $ DEALLOCATE device-name[:] 6. Check each volume in the database with the STORAGE SHOW VOLUME command: $ STORAGE SHOW VOLUME volume_id Performing Postinstallation Tasks 4-5 A _________________________________________________________________ Sample ABS Installation Log File This appendix contains a sample installation log files of an ABS installation, a MDMS server installation, and a MDMS client installtion. These samples were run on a system that had no previous versions of the ABS or MDMS installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. The sample installations makes the following assumptions: o DECnet has been shut down o Users are logged off the system o OPTIONS N is specified to print the release notes o The Installation Verification Procedure (IVP) runs at the end of the installation procedure. The following sample log file is from an ABS installation on an OpenVMS Version 7.1 Alpha system: $ @ SYS$UPDATE:VMSINSTAL OpenVMS AXP Software Product Installation Procedure V7.1 It is 15-OCT-1997 at 13:44. Enter a question mark (?) at any time for help. * Do you want to continue anyway [NO]? yes * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: resd$:[kit] Enter the products to be processed from the first distribution volume set. * Products: absb021 * Enter installation options you wish to use (none): The following products will be processed: ABSB V2.1 Beginning installation of ABSB V2.1 at 13:45 Sample ABS Installation Log File A-1 Sample ABS Installation Log File %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. **************************************************************** * Archive/Backup (ABS) V2.1B for OpenVMS * * Installation * * * * Copyright(c) Digital Equipment Corporation 1997. * * All Rights Reserved. Unpublished rights reserved under the * * copyright laws of the United States. * **************************************************************** %ABSB-I-SYSGENCHK, Checking SYSGEN parameters... LICENSING FOR ABS IS REQUIRED: One of the following licenses must be loaded and active on this system for the ABS installation to complete successfully. SLS SLS-ACS SLS-MGR SLS-REMOTE SLS-REMOTE-MGR * Does this product have an authorization key registered and loaded [YES]? * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? *** ABS$ROOT Device *** You will now be asked to enter a disk device specification to be used as a repository for ABS images, databases and log files. NOTE: *** This device must have at least 40000 free blocks and be available to all nodes in the cluster that will be running ABS *** * Enter the device to use for ABS files [SYS$COMMON:]: The ABS files will be placed at SYS$COMMON:[ABS.] * Is this correct [YES]? *** ABS Policy Engine Nodes *** Please enter the cluster name, or list of nodes on which to find the ABS Policy Engine. If you enter the local cluster name or a list of names in the local cluster, the ABS Policy Engine will be installed on this node. * Cluster or node list for ABS Policy Engine [NODE01::]: %ABSB-I-CHKLOCALPE, Checking for local Policy Engine A-2 Sample ABS Installation Log File Sample ABS Installation Log File ABS can now provide its policy database in RMS files or OracleRdb database. Answer YES to the following question if RMS files are to be provided as the ABS policy database. * Install RMS files as the ABS policy database [YES]? This kit includes a BOOKREADER file, ABS$HELP.DECW$BOOK, which provides help text for the Graphical User Interface. * Do you want this BOOKREADER file placed on your system? [YES]? Attempting to locate writeable directory in DECW$BOOK:... Trying SYS$COMMON:[DECW$BOOK]... The first writeable translation of DECW$BOOK is: SYS$COMMON:[DECW$BOOK] * Please enter the location for ABS$HELP.DECW$BOOK [SYS$COMMON:[DECW$BOOK]]: * ABS$HELP will be placed into SYS$COMMON:[DECW$BOOK], is this correct? [YES]? %ABSB-I-DONEASK, No further questions will be asked during this installation. -ABSB-I-DONEASK, The installation should take less than 15 minutes to complete. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. Sample ABS Installation Log File A-3 Sample ABS Installation Log File %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ABS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named ABS. %UAF-I-MDFYMSG, user record(s) updated %ABSB-I-CREID, Creating ABS rights identifiers... %ABSB-I-CREDIR, Creating ABS directory structure... %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.TEMPLATES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.DATABASE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.SYSTEM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.CATALOG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.LOG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.LISTINGS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.CLIENTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.NTCLIENTS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.NTCLIENTS.ALPHA]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DISK$1:[SYS0.SYSCOMMON.ABS.NTCLIENTS.INTEL]. %ABSB-I-CRELOG, Creating logical names... %ABSB-I-CREATEQUE, Creating ABS batch queue. %VMSINSTAL-I-RESTORE, Restoring product save set D ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... %ABSB-I-SECUREFILES, Setting security on ABS files... %ABSB-I-PROVIDEFILE, Providing ABS files... %ABSB-I-PROVIDEPE, Providing ABS Policy Engine... %ABSB-I-CREATECATLG, Creating default catalog... %ABSB-I-CREATECATLG, Creating disaster_recovery catalog... %ABSB-I-PROVIDEINI, Providing Database Init programs... %ABSB-I-PROVIDEGUI, Providing ABS$GUI... %ABSB-I-PROVIDEGUI, Providing Alternative GUI... %ABSB-I-PROVIDEGZIP, Providing gzip and gtar files... %ABSB-I-PROVIDENT, Providing NT client setup files... A-4 Sample ABS Installation Log File Sample ABS Installation Log File %ABSB-I-PROVIDEDB, Providing ABS Database... Client License Database successfully CREATED %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %ABSB-I-RENAMFILES, Renaming nt client setup files. %JBC-E-STARTED, queue already started Starting ABS Policy Engine... Job ABS$START_POLICY_ENGINE (queue ABS$NODE01, entry 721) started on ABS$NODE01 Job START_COORD_CLEANUP (queue ABS$NODE01, entry 722) started on ABS$NODE01 Starting ABS Catalog Cleanup... %NSCHED-I-RQSTSUCCSS, Job 53432 - Created Starting ABS Database Cleanup... %NSCHED-I-RQSTSUCCSS, Job 53433 - Created %ABSB-I-NODBINIT, Creating SYSTEM_BACKUPS storage class and SYSTEM_BACKUPS_ENV environment ABS_DB_INIT - Starting ABS database initialization... ABS_DB_INIT - Initializing ABS Storage Classes... ABS_DB_INIT - Creating ABS_ARCHIVE Storage Class ABS_DB_INIT - Creating SYSTEM_BACKUPS Storage Class ABS_DB_INIT - Creating DISASTER_RECOVERY Storage Class ABS_DB_INIT - Creating USER_BACKUPS Storage Class ABS_DB_INIT - Creating UNIX_BACKUPS Storage Class ABS_DB_INIT - Initializing ABS Execution environments... ABS_DB_INIT - Creating ABS_ARCHIVE_ENV Execution Environment ABS_DB_INIT - Creating DEFAULT_ENV Execution Environment ABS_DB_INIT - Creating SYSTEM_BACKUPS_ENV Execution Environment ABS_DB_INIT - Creating DISASTER_RECOVERY_ENV Execution Environment ABS_DB_INIT - Creating UNIX_BACKUPS_ENV Execution Environment ABS_DB_INIT - Creating USER_BACKUPS_ENV Execution Environment ABS_DB_INIT - Ending ABS database initialization. %ABSB-I-NODBINIT, Creating OMT_BACKUPS storage class and OMT_BACKUPS_ENV environment. ABS_DB_INIT - Starting ABS database initialization... ABS_DB_INIT - Initializing ABS Storage Class... ABS_DB_INIT - Creating OMT_BACKUPS Storage Class ABS_DB_INIT - Initializing ABS Execution environments... ABS_DB_INIT - Creating OMT_BACKUPS_ENV Execution Environment ABS_DB_INIT - Ending ABS database initialization. Post-installation Instructions: In order to complete the installation of Archive/Backup, you need to perform the following steps: 1) Edit the file SYS$MANAGER:SYSTARTUP_VMS.COM, and add the line $ @SYS$STARTUP:ABS$STARTUP Sample ABS Installation Log File A-5 Sample ABS Installation Log File after the startup of Storage Library System (SLS) and POLYCENTER Scheduler. This will ensure that the ABS software is properly initialized at each system startup. 2) If you are updating from a previous version of PAB or ABS, you MUST execute a catalog conversion command procedure prior to executing save and restore requests. It is not necessary to run this command procedure if you are upgrading from V2.1 to V2.1A. Do the following steps to convert the catalogs: After you have installed ABS Version 2.1A, run the following command procedure to convert your target catalogs. Respond to the questions as shown in Example 1. Restrictions: ------------ The ABS catalogs must be quiescent while executing the catalog conversion command procedure. The catalog that is being converted will be locked; no save, restore or lookup operations are allowed while the conversion is occuring. Example 1 Converting ABS Target Catalogs ----------------------------------------- $ @ABS$SYSTEM:CONVERT_CATALOG_V21 ABS Catalogs ... ABS_CATALOG ABS_UNIX_CATALOG DISASTER_RECOVERY Which catalog would you like to convert? abs_catalog Starting conversion of abs_catalog catalog abs_catalog catalog conversion complete Would you like to convert another catalog (Yes/[No])? n Archive/Backup V2.1B for OpenVMS VAX Installation Verification Procedure (IVP) Copyright © Digital Equipment Corporation 1994, 1997 All Rights Reserved. A-6 Sample ABS Installation Log File Sample ABS Installation Log File Verifying Archive/Backup logical names... Checking Archive/Backup configuration... Verifying Archive/Backup files... Verifying Archive/Backup account... Verifying Storage Class Creation... Storage Class Name - SYSTEM_BACKUPS Version - 1 Node Name - NODE01 Primary Archive Type - SLS/MDMS Number Of Copies - 4 Catalog Name - ABS_CATALOG Storage Class Name - USER_BACKUPS Version - 1 Node Name - NODE01 Primary Archive Type - SLS/MDMS Number Of Copies - 4 Catalog Name - ABS_CATALOG Storage Class Name - DISASTER_RECOVERY Version - 1 Node Name - NODE01 Primary Archive Type - SLS/MDMS Number Of Copies - 4 Catalog Name - DISASTER_RECOVERY Storage Class Name - UNIX_BACKUPS Version - 1 Node Name - NODE01 Primary Archive Type - SLS/MDMS Number Of Copies - 4 Catalog Name - ABS_CATALOG Sample ABS Installation Log File A-7 Sample ABS Installation Log File Storage Class Name - OMT_BACKUPS Version - 1 Node Name - NODE01 Primary Archive Type - SLS/MDMS Number Of Copies - 4 Catalog Name - ABS_CATALOG The IVP for Archive/Backup V2.1B was successful. Installation of ABSB V2.1 completed at 13:49 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]ABSB021.VMI_DATA A.1 MDMS Server Installation Example Log File The following example shows an installation of the MDMS server software on a VAX system running OpenVMS Version 7.0. This example also installs server-side support for RDF, asks you about viewing the release notes, and runs an IVP. Username: SYSTEM Password: Welcome to OpenVMS VAX version V7.0 on node NODE01 Last interactive login on Monday, 12-JUL-1997 13:43 Last non-interactive login on Monday, 12-JUL-1997 09:59 $ @sys$update:vmsinstal OpenVMS VAX Software Product Installation Procedure V7.0 It is 12-JUL-1997 at 15:04. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: sys$sysdevice:[mdmskits] Enter the products to be processed from the first distribution volume set. * Products: MDMS029 * Enter installation options you wish to use (none): The following products will be processed: MDMS V2.9 Beginning installation of MDMS V2.9 at 15:05 A-8 Sample ABS Installation Log File Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************************** * WARNING * ************************************************************************** * * * MDMS V2.9 (client and server) is not compatible with any previous * * versions of MDMS prior to V2.5. All nodes running MDMS which interact* * with each other should also be upgraded to V2.5 or above. * * * ************************************************************************** * Do you want to continue with this installation [No]? yes * Do you want to run the IVP after the installation [YES]? Product: MDMS Producer: DEC Version: 2.9 Release Date: 8-JUL-1996 * Does this product have an authorization key registered and loaded? yes * Do you want to purge files replaced by this installation [YES]? MDMS provides support for remote backups. This function allows you to backup disks on this system to a tape drive located on some other system with MDMS installed, or to allow other systems to backup their disks to the tape drives on this system. * Do you want to backup disks on this system to a drive on a remote system? yes Remote Device Facility Client support will be provided. * Do you want to allow remote backups access to the tape drives on this system? UYES Remote Device Facility Server support will be provided. * Enter the name of the disk device the MDMS/SLS software will use [DSA1:]: * Enter the name of the directory the MDMS/SLS software will use [SLS$FILES]: * Where to place summary files from system backups [SLS$ROOT:[SYSBAK.SUMMARY_FILES]]: * Where to place intermediate history files [SLS$ROOT:[SYSBAK.TEMP_HISTORY]]: * Where to place maintenance log files [SLS$ROOT:[DATA]]: * Where to place system backup log files [SLS$ROOT:[SYSBAK.SYSBAK_LOGS]]: If you have been using earlier versions of MDMS software, there will be log files and summary files resident in SLS$SYSBAK from previous system backups. This installation procedure has the ability to automatically distribute these old files into the directories you have specified. Sample ABS Installation Log File A-9 Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File * Do you want to automatically move these old files? [Y]? In order for the MDMS/SLS software to perform system management tasks, a privileged account called SLS is created. You must specify a unique UIC for this account so that it will not conflict with other accounts on your system. %SLS-I-EXISTS, the identifier SLS already exists with UIC [1,20] This procedure will assume the SLS account also exists. Please enter a password for the SLS account. The password you specify must contain at least 15 and no more than 31 characters and may not refer to the account/product name, or your system node or cluster name. Valid characters include A through Z, 0 through 9, $ (dollar sign) and _ (underscore). As with the DCL SET PASSWORD command, your input will not echo on the terminal and you will be asked to verify the password. * Password: * Verify password: %SLS-I-UPDACC, Updating account SLS with specified password %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %SLS-I-UPDACC, Updating account SLS for client network access %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %SLS-I-UPDACC, Updating account SLS privileges and login directory %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated The following quotas will be set for the SLS account: Maxjobs: 0 Fillm: 500 Bytlm: 128000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 128 JTquota: 1024 Prclm: 10 DIOlm: 4096 WSdef: 1024 Prio: 4 ASTlm: 4096 WSquo: 16384 Queprio: 4 TQElm: 32 WSextent: 16384 CPU: (none) Enqlm: 2500 Pgflquo: 100000 A-10 Sample ABS Installation Log File Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File %SLS-I-UPDACC, Updating quotas for account SLS... %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated * Do you wish to update these flags now [YES]? The following fields will be set for the SLS account: /FLAGS= NoAudit DisMail NoDisReport DefCLI DisNewMail NoDisUser NoDisCtlY DisReconnect NoGenPwd /BATCH /NOINTERACTIVE /NOLOCAL /NODIALUP /NOREMOTE /NOEXPIRATION /PWDEXPIRED /NETWORK %SLS-I-UPDACC, Updating flags for account SLS... %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %SLS-I-QUOTA, Checking for DISKQUOTAs on the SLS server device ... There will be no further questions asked. The installation of MDMS/SLS will take an average of 30 minutes more to complete. It may take longer if the log files and summary files from previous system backups are going to be automatically distributed into the system backup directories you have specified. Sample ABS Installation Log File A-11 Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File %VMSINSTAL-I-RESTORE, Restoring product save set B ... %SLS-I-PROCEED, Proceeding with saveset B %SLS-I-LINKING, Linking privileged shareable image %SLS-I-CRTSTART, Creating TAPESTART.COM %SLS-I-CRTDIR, Creating SLS subdirectories... %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.AUDIT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.CUSTOM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.DATA]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.HIST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.PARAMS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.PRIMAST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.SYSBAK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.SYSTEM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA1:[SLS$FILES.USRBAK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[SYSBAK.SUMMARY_FILES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[SYSBAK.TEMP_HISTORY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[DATA]. %CREATE-I-EXISTS, SLS$ROOT:[DATA] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[SYSBAK.SYSBAK_LOGS]. Since a new TAPESTART.COM was created for this installation, a media triplet template file will be generated for you. This file will be created in SLS$DATAC and called SLS$AUTOCONFIGURE_MEDIA_TRIPLETS.TXT. This file should be included in TAPESTART.COM (see that file for appropriate location) and possibly modified to fit your needs. The devices in this file were found on this system. %SLS-I-GENTRIPTEMP, Generating media triplet template file %SLS-I-DEFFILE, Defining files that need to be moved %SLS-I-PROVRDF, Providing Remote Device Facility Support %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[TTI_RDEV]. %SLS-I-SPLITSYSBAK, Moving old log files and summary files as requested. %SLS-I-SPLITDONE, Finished moving old log files and summary files. ------------------------------------------------------------------ The following post-installation steps are necessary. Refer to the Installation Guide for details. A-12 Sample ABS Installation Log File Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File 1. Edit the system startup procedure to start the MDMS software on this client. Add $ @SYS$STARTUP:SLS$STARTUP 2. Edit the system wide login file. Add $ @SYS$MANAGER:SLS$TAPSYMBOL 3. Run SLS$SYSTEM:SLS$SLSMGR.EXE to perform the following functions: a. Authorize access to the SLS server database for SLS client nodes. b. Authorize access to SLS pools for SLS users. 4. Customize SYS$MANAGER:TAPESTART.COM to reflect SLS environment parameters. 5. Check that SLS$DBX object is defined on all nodes participating in the VMScluster System alias. 6. For Remote Device Facility client support, you should add one or more media-type triplets (MTYPE_x, DENS_x, DRIVES_x) to your TAPESTART.COM to describe the remote tape drives. Be sure to include the remote nodename in each drive name. 7. For Remote Device Facility server support, you should check the file SLS$ROOT:[TTI_RDEV]CONFIG_TRMBNE.DAT to ensure that the tape devices you wish to serve are included in this RDF configuration file. This file will be created initially when SLS is started after this installation. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %SLS-I-STARTUP, Starting SLS %RUN-S-PROC_ID, identification of created process is 20200247 %SLS-I-WAIT, Waiting for the SLS software to start ******************************************************************************** Beginning MDMS Version 2.9 Installation Verification Procedure (IVP) ******************************************************************************** Installation verification begun at 12-JUL-1997 15:18:31.07 Checking for correct version of VMS. Checking for presence of DECnet. Checking for SLS executable images. Checking system-wide logical names. Sample ABS Installation Log File A-13 Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File Checking for SLS database files. Checking for SLS client process. Checking for SLS server process. Checking for FMS executable images. Checking for correct version of SLS. Waiting for subprocess SLS$IVP to complete. %MDMS-I-VERSION, Media and Device Management System for OpenVMS, Version 2.9 Doing a STORAGE ADD VOLUME. Waiting for subprocess SLS$IVP to complete. Waiting for subprocess SLS$IVP to complete. Waiting for subprocess SLS$IVP to complete. Doing a STORAGE ALLOCATE. Doing a STORAGE SHOW VOLUME. Volume: XYZZY9 Owner: CLSTR1::SLS Format: BACKUP Brand: Allocated: 12-JUL-1997 15:18 Scratch: 11-JUL-1998 15:18 Purchased: 12-JUL-1997 15:18 Cleaned: 12-JUL-1997 15:18 Media type: 9TRACK Length: 0 Mounts: 0 UIC: [SLS] Location: HEADQUARTERS Protection: S:RW,O:RW,G:R,W: Notes: Offsite: Onsite: IO Errors: 0 Flag: ALLOCATED Next volume: *none* Previous: *none* Pool: Rec len: 0 Block factor: 0 Initialized: 12-JUL-1997 15:18 Density: 6250 Slot number: Side: Other side: Jukebox / slot: / Drive: Volume is not in a jukebox. Volume is not in a magazine. A-14 Sample ABS Installation Log File Sample ABS Installation Log File A.1 MDMS Server Installation Example Log File Doing a STORAGE DEALLOCATE. Doing a STORAGE REMOVE VOLUME. Doing a STORAGE SHOW VOLUME; there should be no such volume. %SLS-W-NOSUCHVOL, no such volume(s) * * * All tests have completed sucessfully. * * * Installation verification finished at 12-JUL-1997 15:19:06.85 ******************************************************************************** Successful Installation Verification of MDMS Version 2.9 ******************************************************************************** Installation of MDMS V2.9 completed at 15:19 Enter the products to be processed from the next distribution volume set. * Products: VMSINSTAL procedure done at 15:19 A.2 MDMS Client Installation Example Log File The following example shows an installation of the MDMS client software on a VAX system running OpenVMS Version 7.0. This example also installs support for the RDF client and does not run an IVP. Username: SYSTEM Password: Welcome to OpenVMS VAX version V7.0 on node NODE10 Last interactive login on Monday, 12-JUL-1997 13:43 Last non-interactive login on Monday, 12-JUL-1997 09:59 $ @sys$update:vmsinstal OpenVMS VAX Software Product Installation Procedure V6.2 It is 14-JUL-1997 at 13:37. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: sys$sysdevice:[mdmskits] Enter the products to be processed from the first distribution volume set. * Products: MDMSCLIENT029 Sample ABS Installation Log File A-15 Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File * Enter installation options you wish to use (none): The following products will be processed: MDMSCLIENT V2.9 Beginning installation of MDMSCLIENT V2.9 at 13:38 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************************** * WARNING * ************************************************************************** * * * MDMS V2.9 (client and server) is not compatible with any previous * * versions of MDMS prior to V2.5. All nodes running MDMS which interact* * with each other should also be upgraded to V2.5 or above. * * * ************************************************************************** * Do you want to continue with this installation [No]? * Do you want to run the IVP after the installation [YES]? Product: MDMSCLIENT Producer: DEC Version: 2.9 Release Date: 24-JUN-1997 * Does this product have an authorization key registered and loaded? yes * Do you want to purge files replaced by this installation [YES]? Before proceeding with the installation of the MDMS software, you should have read the MDMS Installation Guide discussion about the use of the MDMS server node or VMScluster System alias. You will need the name of the MDMS server node or VMScluster System alias. * Are you ready to proceed [YES]? yes * What is the name or VMScluster System alias of the MDMS server node: CLSTR1 MDMS provides support for remote backups. This function allows you to backup disks on this system to a tape drive located on some other system with MDMS installed, or to allow other systems to backup their disks to the tape drives on this system. A-16 Sample ABS Installation Log File Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File * Do you want to backup disks on this system to a drive on a remote system? y Remote Device Facility Client support will be provided. * Do you want to allow remote backups access to the tape drives on this system? y Remote Device Facility Server support will be provided. * Enter the name of the disk device the MDMS software will use [DSA0:]: * Enter the name of the directory the MDMS software will use [SLS$FILES]: * Where to place summary files from system backups [SLS$ROOT:[SYSBAK.SUMMARY_FILES]]: * Where to place intermediate history files [SLS$ROOT:[SYSBAK.TEMP_HISTORY]]: * Where to place maintenance log files [SLS$ROOT:[DATA]]: * Where to place system backup log files [SLS$ROOT:[SYSBAK.SYSBAK_LOGS]]: If you have been using earlier versions of MDMS software, there will be log files and summary files resident in SLS$SYSBAK from previous system backups. This installation procedure has the ability to automatically distribute these old files into the directories you have specified. * Do you want to automatically move these old files? [Y]? In order for the MDMS software to perform system management tasks, a privileged account called MDMS is created. You must specify a unique UIC for this account so that it will not conflict with other accounts on your system. %SLSCLIENT-I-EXISTS, the identifier SLS already exists with UIC [1,20] This procedure will assume the MDMS account also exists. Please enter a password for the MDMS account. The password you specify must contain at least 15 and no more than 31 characters and may not refer to the account/product name, or your system node or cluster name. Valid characters include A through Z, 0 through 9, $ (dollar sign) and _ (underscore). As with the DCL SET PASSWORD command, your input will not echo on the terminal and you will be asked to verify the password. * Password: * Verify password: Sample ABS Installation Log File A-17 Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File %SLSCLIENT-I-UPDACC, Updating account SLS with specified password %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %SLSCLIENT-I-UPDACC, Updating account SLS privileges and login directory %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated The MDMS account is used to establish quotas for the processes in which Backups are run. The quota values should be updated in accordance with the recommendations set forth in the `VMS Backup Utility Reference Manual'. If you wish, this installation procedure will automatically update these quotas now. * Do you wish to update these quotas now [YES]? The following quotas will be set for the MDMS account: Maxjobs: 0 Fillm: 500 Bytlm: 128000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 128 JTquota: 1024 Prclm: 10 DIOlm: 4096 WSdef: 1024 Prio: 4 ASTlm: 4096 WSquo: 16384 Queprio: 4 TQElm: 32 WSextent: 16384 CPU: (none) Enqlm: 2500 Pgflquo: 100000 %SLSCLIENT-I-UPDACC, Updating quotas for account SLS... %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated Digital recommends that the MDMS account be used only by the MDMS software and not as an interactive account. It is recommended that the Storage Administrator and Operators use other accounts to perform MDMS functions. If you wish, this installation procedure will automatically set the appropriate flags to disallow interactive access to this account. * Do you wish to update these flags now [YES]? The following fields will be set for the MDMS account: A-18 Sample ABS Installation Log File Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File /FLAGS= NoAudit DisMail NoDisReport DefCLI DisNewMail NoDisUser NoDisCtlY DisReconnect NoGenPwd /BATCH /NOINTERACTIVE /NOLOCAL /NODIALUP /NOREMOTE /NOEXPIRATION /PWDEXPIRED /NONETWORK %SLSCLIENT-I-UPDACC, Updating flags for account SLS... %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named SLS. %UAF-I-MDFYMSG, user record(s) updated %SLSCLIENT-I-QUOTA, Checking for DISKQUOTAs on the SLS device ... There will be no further questions asked. The installation of MDMS/SLS will take an average of 30 minutes more to complete. It may take longer if the log files and summary files from previous system backups are going to be automatically distributed into the system backup directories you have specified. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %SLSCLIENT-I-PROCEED, Proceeding with saveset B %SLSCLIENT-I-LINKING, Linking privileged shareable image %SLSCLIENT-I-CRTSTART, Creating TAPESTART.COM %SLSCLIENT-I-CRTDIR, Creating SLS subdirectories... %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.AUDIT]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.CUSTOM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.DATA]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.HIST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.PARAMS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.SYSBAK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DSA0:[SLS$FILES.SYSTEM]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory Sample ABS Installation Log File A-19 Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File DSA0:[SLS$FILES.USRBAK]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[SYSBAK.SUMMARY_FILES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[SYSBAK.TEMP_HISTORY]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[DATA]. %CREATE-I-EXISTS, SLS$ROOT:[DATA] already exists %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[SYSBAK.SYSBAK_LOGS]. Since a new TAPESTART.COM was created for this installation, a media triplet template file will be generated for you. This file will be created in SLS$DATAC and called SLS$AUTOCONFIGURE_MEDIA_TRIPLETS.TXT. This file should be included in TAPESTART.COM (see that file for appropriate location) and possibly modified to fit your needs. The devices in this file were found on this system. %SLSCLIENT-I-GENTRIPTEMP, Generating media triplet template file %SLSCLIENT-I-DEFFILE, Defining files that need to be moved %SLSCLIENT-I-PROVRDF, Providing Remote Device Facility Support %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-SYSDIR, This product creates system disk directory SLS$ROOT:[TTI_RDEV]. %SLS-I-SPLITSYSBAK, Moving old log files and summary files as requested. %SLS-I-SPLITDONE, Finished moving old log files and summary files. ------------------------------------------------------------------ The following post-installation steps are necessary. Refer to the Installation Guide for details. 1. Edit the system startup procedure to start the MDMS software on this client. Add $ @SYS$STARTUP:SLS$STARTUP 2. Edit the system wide login file. Add $ @SYS$MANAGER:SLS$TAPSYMBOL 3. Customize SYS$MANAGER:TAPESTART.COM to reflect MDMS environment parameters. 4. For Remote Device Facility client support, you should add one or more media-type triplets (MTYPE_x, DENS_x, DRIVES_x) to your TAPESTART.COM to describe the remote tape drives. Be sure to include the remote nodename in each drive name. A-20 Sample ABS Installation Log File Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File 5. For Remote Device Facility server support, you should check the file SLS$ROOT:[TTI_RDEV]CONFIG_SNRDRM.DAT to ensure that the tape devices you wish to serve are included in this RDF configuration file. This file will be created initially when MDMS is started after this installation. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %SLS-I-STARTUP, Starting MDMS %RUN-S-PROC_ID, identification of created process is 20400738 %SLS-I-WAIT, Waiting for the MDMS software to start ******************************************************************************** Beginning MDMS Version 2.9 Installation Verification Procedure (IVP) ******************************************************************************** Installation verification begun at 14-JUL-1997 13:58:44.77 Checking for correct version of VMS. Checking for presence of DECnet. Checking for SLS executable images. Checking system-wide logical names. Checking for SLS client process. Checking for FMS executable images. Checking for correct version of SLS. Waiting for subprocess SLS$IVP to complete. %SLS-I-VERSION, Media and Device Management System for OpenVMS, Version 2.9 Doing a STORAGE ADD VOLUME. Waiting for subprocess SLS$IVP to complete. Waiting for subprocess SLS$IVP to complete. Waiting for subprocess SLS$IVP to complete. Doing a STORAGE ALLOCATE. Doing a STORAGE SHOW VOLUME. Sample ABS Installation Log File A-21 Sample ABS Installation Log File A.2 MDMS Client Installation Example Log File Volume: XYZZY9 Owner: CLSTR1::SLS Format: BACKUP Brand: Allocated: 12-JUL-1997 15:18 Scratch: 11-JUL-1998 15:18 Purchased: 12-JUL-1997 15:18 Cleaned: 12-JUL-1997 15:18 Media type: 9TRACK Length: 0 Mounts: 0 UIC: [SLS] Location: HEADQUARTERS Protection: S:RW,O:RW,G:R,W: Notes: Offsite: Onsite: IO Errors: 0 Flag: ALLOCATED Next volume: *none* Previous: *none* Pool: Rec len: 0 Block factor: 0 Initialized: 12-JUL-1997 15:18 Density: 6250 Slot number: Side: Other side: Jukebox / slot: / Drive: Volume is not in a jukebox. Volume is not in a magazine. Doing a STORAGE DEALLOCATE. Doing a STORAGE REMOVE VOLUME. Doing a STORAGE SHOW VOLUME; there should be no such volume. %SLS-W-NOSUCHVOL, no such volume(s) * * * All tests have completed sucessfully. * * * Installation of MDMSCLIENT V2.9 completed at 13:59 A-22 Sample ABS Installation Log File B _________________________________________________________________ Examples of Authorizing NT and UNIX Clients This appendix contains examples of how to authorize NT and UNIX clients, which includes adding, modifying, showing, and removing those 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 := $ABS$SYSTEM:ABS_CLIENT_LICENSE.EXE B.1 Adding Client Licenses Example B-1 shows how to add a UNIX or NT client license. Example B-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 (continued on next page) Examples of Authorizing NT and UNIX Clients B-1 Examples of Authorizing NT and UNIX Clients B.1 Adding Client Licenses Example B-1 (Cont.) Adding Client Licenses Client UNIX_1 successfully ADDED to License Database License Count: 1 used of 25 total B-2 Examples of Authorizing NT and UNIX Clients Examples of Authorizing NT and UNIX Clients B.2 Modifying Client Licenses B.2 Modifying Client Licenses Example B-2 shows how to modify the port number of an NT or UNIX client license. Note: The port number that you enter here must match the port number you assigned during the NT client installation. Example B-2 Modifying Client Licenses $ 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: Windows NT Transport: TCP/IP Port: 514 New Port #?: 1800 Client UNIX_1 successfully MODIFIED in License Database License Count: 1 used of 25 total Examples of Authorizing NT and UNIX Clients B-3 Examples of Authorizing NT and UNIX Clients B.3 Showing Client Licenses B.3 Showing Client Licenses Example B-3 illustrates how to show an NT or UNIX client license: Example B-3 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 B.4 Removing Client Licenses Example B-4 shows how to remove NT or UNIX client licenses: Example B-4 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 (continued on next page) B-4 Examples of Authorizing NT and UNIX Clients Examples of Authorizing NT and UNIX Clients B.4 Removing Client Licenses Example B-4 (Cont.) Removing Client Licenses License Count: 0 used of 6 total Examples of Authorizing NT and UNIX Clients B-5 C _________________________________________________________________ Files and Logical Names The installation procedure produces several files on your system and defines numerous logical names. The following sections are provided so you may verify that the appropriate file names and logical names are resident on your system when the installation procedure is complete. Sections C.1 and C.2 list the names of the files installed. Sections C.3 and C.4 list the logical names that are added to the system logical name table. C.1 ABS File Names Table C-1 lists the names of the ABS files created on your system after ABS is installed. Table_C-1__ABS_Files_Installed___________________________________ File_Location/Name______________File_Name________________________ SYS$HELP:_directory______________________________________________ ABSB021.RELEASE_NOTES ABS$HELP.HLB _________________________________________________________________ SYS$LIBRARY:_directory___________________________________________ ABS$COSISHR.EXE ABS$SHR.EXE ABS$SLS_SERVICES.EXE ABS$USSSHR.EXE _________________________________________________________________ SYS$MANAGER:_directory___________________________________________ ABS$SHUTDOWN.COM (continued on next page) Files and Logical Names C-1 Files and Logical Names C.1 ABS File Names Table_C-1_(Cont.)__ABS_Files_Installed___________________________ File_Location/Name______________File_Name________________________ SYS$SYSROOT:_directory___________________________________________ ABS$GUI.DAT ABS-OMT.DAT _________________________________________________________________ SYS$STARTUP:_directory___________________________________________ ABS$ALTERNATE_ROOT.COM ABS$STARTUP.COM ABS$SHUTDOWN.COM _________________________________________________________________ SYS$TEST:_directory______________________________________________ ABS$IVP.COM _________________________________________________________________ ABS$ROOT:_directory______________________________________________ [000000]LOGIN.COM [CATALOG]ABS_CATALOG_BAOE.DAT [CATALOG]ABS_CATALOG_BAOE_ INSNC.DAT [CATALOG]ABS_CATALOG_ [CATALOG]ABS_CATALOG_OBJECTS.DAT BTLE.DAT;2 [CLIENTS]GNU_GENERAL_PUBLIC_ [CLIENTS]GNU_README_WHERE_TO_ LICENSE.TXT GET.TXT [CLIENTS]GZIP-1_2_4.TAR [CLIENTS]TAR-1_11_8.TAR [DATABASE]CLIENT_DB.DAT [DATEBASE]EPCOT.DB1 [DATABASE]EPCOT.DB2 [DATABASE]EPCOT.DB3 (continued on next page) C-2 Files and Logical Names Files and Logical Names C.1 ABS File Names Table_C-1_(Cont.)__ABS_Files_Installed___________________________ _________________________________________________________________ ABS$TEMPLATES:_directory_________________________________________ GTAR-1.AGENT_INFORMATION GTAR-1.FULL_ARCHIVE_TEMPLATE GTAR-1.INCREMENTAL_RESTORE_ GTAR-1.PARSE_TEMPLATE TEMPLATE GTAR-1.SELECTIVE_ARCHIVE_ GTAR-1.SELECTIVE_RESTORE_TEMPLATE TEMPLATE NT_GTAR-1.AGENT_INFORMATION NT_GTAR-1.FULL_ARCHIVE_TEMPLATE NT_GTAR-1.FULL_RESTORE_ NT_GTAR-1.INCREMENTAL_ARCHIVE_ TEMPLATE TEMPLATE NT_GTAR-1.INCREMENTAL_RESTORE_ NT_GTAR-1.PARSE_TEMPLATE TEMPLATE NT_GTAR-1.SELECTIVE_ARCHIVE_ NT_GTAR-1.SELECTIVE_RESTORE_ TEMPLATE TEMPLATE RMU_BACKUP_42-2.AGENT_ RMU_BACKUP_42-2.FULL_ARCHIVE_ INFORMATION TEMPLATE RMU_BACKUP_42-2.FULL_RESTORE_ RMU_BACKUP_42-2.INCREMENTAL_ TEMPLATE ARCHIVE_TEMPLATE RMU_BACKUP_42-2.INCREMENTAL_ RMU_BACKUP_42-2.PARSE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_42-2.SELECTIVE_ RMU_BACKUP_42-2.SELECTIVE_ ARCHIVE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_51-2.AGENT_ RMU_BACKUP_51-2.FULL_ARCHIVE_ INFORMATION TEMPLATE RMU_BACKUP_51-2.FULL_RESTORE_ RMU_BACKUP_51-2.INCREMENTAL_ TEMPLATE ARCHIVE_TEMPLATE RMU_BACKUP_51-2.INCREMENTAL_ RMU_BACKUP_51-2.PARSE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_51-2.SELECTIVE_ RMU_BACKUP_51-2.SELECTIVE_ ARCHIVE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_60-2.AGENT_ RMU_BACKUP_60-2.FULL_ARCHIVE_ INFORMATION TEMPLATE (continued on next page) Files and Logical Names C-3 Files and Logical Names C.1 ABS File Names Table_C-1_(Cont.)__ABS_Files_Installed___________________________ File_Location/Name______________File_Name________________________ ABS$TEMPLATES:_directory_________________________________________ RMU_BACKUP_60-2.FULL_RESTORE_ RMU_BACKUP_60-2.INCREMENTAL_ TEMPLATE ARCHIVE_TEMPLATE RMU_BACKUP_60-2.INCREMENTAL_ RMU_BACKUP_60-2.PARSE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_60-2.SELECTIVE_ RMU_BACKUP_60-2.SELECTIVE_ ARCHIVE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_61-2.AGENT_ RMU_BACKUP_61-2.FULL_ARCHIVE_ INFORMATION TEMPLATE RMU_BACKUP_61-2.FULL_RESTORE_ RMU_BACKUP_61-2.INCREMENTAL_ TEMPLATE ARCHIVE_TEMPLATE RMU_BACKUP_61-2.INCREMENTAL_ RMU_BACKUP_61-2.PARSE_TEMPLATE RESTORE_TEMPLATE RMU_BACKUP_61-2.SELECTIVE_ RMU_BACKUP_61-2.SELECTIVE_ ARCHIVE_TEMPLATE RESTORE_TEMPLATE VMS_BACKUP-2.AGENT_INFORMATION VMS_BACKUP-2.FULL_ARCHIVE_ TEMPLATE VMS_BACKUP-2.FULL_RESTORE_ VMS_BACKUP-2.INCREMENTAL_ARCHIVE_ TEMPLATE TEMPLATE VMS_BACKUP-2.INCREMENTAL_ VMS_BACKUP-2.PARSE_TEMPLATE RESTORE_TEMPLATE VMS_BACKUP-2.SELECTIVE_ VMS_BACKUP-2.SELECTIVE_RESTORE_ ARCHIVE_TEMPLATE TEMPLATE _________________________________________________________________ ABS$SYSTEM:_directory____________________________________________ ABS$CLEAN_DB_UTIL.COM ABS$CLEAN_DB_UTIL.EXE ABS$COORD_CLEANUP.EXE ABS$COORD_CLEANUP.FDL ABS$GUI.EXE ABS$GUI_CATALOG.UID ABS$GUI_CREATE.UID ABS$GUI_DATE.UID ABS$GUI_DEFAULTS.COM ABS$GUI_EXECENV.UID ABS$GUI_MAINWINDOW.UID ABS$GUI_MSGBOXES.UID (continued on next page) C-4 Files and Logical Names Files and Logical Names C.1 ABS File Names Table_C-1_(Cont.)__ABS_Files_Installed___________________________ File_Location/Name______________File_Name________________________ ABS$SYSTEM:_directory____________________________________________ ABS$POLICY_CONFIG.DAT ABS$POLICY_ENGINE.EXE ABS$POLICY_MAINT.EXE ABS$START_POLICY_ENGINE.COM ABS$UBS.EXE ABS_CATALOG_OBJECT.EXE ABS_CATALOG_OBJECTS.FDL ABS_CATLG_MAINTENANCE.EXE ABS_CLIENT_LICENSE.EXE ABS_STG_CATLG_UNPACK.EXE ALTERNATE_BACKUP.EXE AOE_BRIEF.FDL AOE_INSTANCE_BRIEF.FDL CATALOG.XBM CONVERT_CATALOG_V20.COM CONVERT_CATALOG_V21.COM COORDINATOR.COM COORDINATOR.EXE COORD_CLEANUP.DAT DB_EPCOT_DB1.FDL DB_EPCOT_DB2.FDL DB_EPCOT_DB3.FDL DELETE_ABS.COM DISASTER_DB_INIT.EXE EPCOT_DB_INIT.EXE EPCOT_USER_BACKUP_UTILITY.EXE EXECCMDLINE.DAT LITE_DB_INIT.EXE LUI_CATALOG.UID LUI_MAIN.EXE LUI_MAIN.UID LUI_MANAGE.UID LUI_RESTORE.UID LUI_SAVE.UID MANAGE.XBM RESTORE.XBM RESTORECMDLINE.DAT SAVE.XBM SAVECMDLINE.DAT START_CATALOG_CLEANUP.COM START_COORD_CLEANUP.COM TLE_BRIEF.FDL UNIX_DB_INIT.EXE_________________________________________________ C.2 MDMS File Names The MDMS installation procedure creates several files on your system. Table C-2 lists and describes the files installed on server and client nodes. File names with an asterisk (*) preceding them are installed only on server nodes. Files and Logical Names C-5 Files and Logical Names C.2 MDMS File Names Table_C-2_MDMS_Files_Installed___________________________________ File_Name__________________Description___________________________ SYS$LIBRARY:_directory___________________________________________ SLS$SHR.EXE MDMS shareable image; contains application interface routines for history file access _________________________________________________________________ SYS$MANAGER:_directory___________________________________________ SLS$TAPSYMBOL.COM Normal user login symbol definitions _________________________________________________________________ SYS$MESSAGE:_directory___________________________________________ SLS$MSG.EXE Contains text of MDMS messages _________________________________________________________________ SYS$SYSTEM:_directory____________________________________________ * SLS$FIND_DB_NODE.EXE Verifies the MDMS database node SLS$STARTUP.COM Startup command file _________________________________________________________________ SYS$TEST:_directory______________________________________________ MDMS_SLS$IVP.COM Installation verification procedure _________________________________________________________________ SLS$PARAMS:_directory____________________________________________ * POOLAUTH.FDL Pool authorization file definition _________________________________________________________________ SLS$DATABASE:_directory__________________________________________ * SLOTMAST.FDL Slot master file definition * TAPEMAST.FDL FDL for TAPEMAST.DAT _________________________________________________________________ SLS$SYSTEM:_directory____________________________________________ ACCTABLES.COM Accesses LNM$SLS logical name table ADV_MAIL.COM Announces processing location (continued on next page) C-6 Files and Logical Names Files and Logical Names C.2 MDMS File Names Table_C-2_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ ALLOCATED_TAPES_ Allocated Tapes report definition file MSTRPT.COM ALLOCATION_ORDER_ Allocation Order report definition MSTRPT.COM file CLEANUP.COM Early morning cleanup batch job CLEAN_LIST_MSTRPT.COM Cleanable tapes report definition file COMING_ONSITE_MSTRPT.COM Coming onsite report definition file CREDEF.COM Creates a symbol definition file (in [.DATA]) CR_SB_FILES.COM Creates a SYSBAK history FILES file DEFTAPES.COM Installs DATATRIEVE information DOWN_TAPES_MSTRPT.COM Prints a list of down tapes control file DTSV.COM Defines a LNM$SLS_VALUE logical name FIND_SYSTEM.COM Finds a file in SYS$SYSTEM FREE_TAPES_MSTRPT.COM Free tapes report definition file GOING_OFFSITE_MSTRPT.COM Going offsite report definition file INITTAPES.COM Operator initialize tapes utility LOADER.COM MDMS system bootstrap loader LOGIN.COM SLS manager account login file MAIL_ADVANCE_RUN.COM Procedure to run MAIL_ADVANCE MAIL_ADVANCE_SEND.COM Displays scratchable tape MSTRPT.COM Master report batch job MSTRPT_MSTRPT.COM Master report template definition file OPERSYMBOL.COM Operator login symbol definitions PRINTED_LABEL_ Template file for printed labels V20.TEMPLATE PRINTED_LABEL_ Template file for printed labels V21.TEMPLATE (continued on next page) Files and Logical Names C-7 Files and Logical Names C.2 MDMS File Names Table_C-2_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ QUANTITY_REPORT.COM Quantity report batch job REBOOT.COM System startup command file RELEASE_TRANS.COM Releases several tapes that are in transition SEQUENTIAL.FDL RMS definition file to convert a system history file to a sequential file SET_VAULT_DATES.COM Sets up onsite and offsite dates * SLSMGR.FLB Screens for SLSMGR.EXE SLS$ABORT.EXE Utility to abort a process SLS$AUTOCONFIGURE_MEDIA_ Searches system to create system- TRIPLETS.EXE specific default media triplets on new MDMS systems to use in TAPESTART.COM SLS$CHKCOMP.EXE Checks tape drives for data compaction capability SLS$COLLECT.EXE Accounting period data collector SLS$CREJOBTBL.EXE Creates the LNM$JOB table with W:RE protection (continued on next page) C-8 Files and Logical Names Files and Logical Names C.2 MDMS File Names Table_C-2_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ SLS$CREMBX.EXE Creates a permanent mailbox for DCL use SLS$DCSC_MGMT_EXPORT.COM Operator Export Volume function for the ACS SLS$DCSC_MGMT_IMPORT.COM Operator Import Volume function for the ACS SLS$DCSC_MGMT_INIT_VOL_ Operator Initialize Volume Series SERIES.COM function for the ACS SLS$DCSC_MGMT_ Operator Inventory Range of Volumes INVENTORY.COM function for the ACS SLS$DCSC_MGMT_LOAD.COM Operator Load Volume Onto Drive function for the ACS SLS$DCSC_MGMT_MENU.COM Operator SLS-ACS Management Menu SLS$DCSC_MGMT_UNLOAD_ Operator Unload Drive function for the DRIVE.COM ACS SLS$DCSC_MGMT_UNLOAD_ Operator Unload Volume function for VOL.COM the ACS SLS$DCSC_RELEASE_ Executable to release a drive DRIVE.EXE allocated to DCSC SLS$DEALLOCATE.COM Deallocates a local or remote tape device SLS$DELMBX.EXE Deletes a permanent mailbox that CREMBX made SLS$FORCEX.EXE Executes a FORCEX system service call SLS$GETMBX.EXE Reads from a permanent mailbox from DCL SLS$GETUAI.EXE Gets information from SYSUAF.DAT SLS$HELP.HLP DCL STORAGE command help file SLS$IBMNLBRDE.EXE IBM [TM] nonlabeled tape reading utility (continued on next page) Files and Logical Names C-9 Files and Logical Names C.2 MDMS File Names Table_C-2_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ SLS$IBMNLBWRT.EXE IBM [TM] nonlabeled tape writing utility SLS$IS_DRIVE_DCSC.EXE For SLS-ACS support, determines whether DCSC (Digital Cartridge Server Component) software accesses a device SLS$MAIL_ADVANCE.EXE Finds tapes that need to have advance mail sent SLS$MAINT.EXE Maintenance screen executable SLS$MSTRPT.EXE Master report executable SLS$OPCOM_SERVER.EXE Image for SLS$OPCOM process; sends and receives remote OPCOM messages and device control requests SLS$PUTMBX.EXE Writes to a permanent mailbox from DCL SLS$QUANTITY.EXE Quantity report executable SLS$RDB_GETVER.COM Command procedure to determine version of RMU software SLS$REQUEST.EXE DCL request that can define a symbol SLS$SETUSR.EXE Sets process username SLS$SHUTDOWN.COM Shuts down MDMS software * SLS$SLSMGR.EXE SLS manager's authorization menu SLS$SLTRPT.EXE Prints a slot report SLS$START_OPCOM_ Starts SLS$OPCOM process SERVER.COM SLS$SYNTAX.CLD DCL STORAGE command definition SLS$TAPE.EXE DCL TAPE command executable SLS$TAPEJUKE_INIT_VOL_ Command procedure to initialize a SERIES.COM volume series in a jukebox SLS$TAPEPURGE.EXE Purges scratchable tape's executable SLS$TAPEUSAGE.EXE Generate tape usage report executable * SLS$TAPMGRDB.EXE DB manager executable (continued on next page) C-10 Files and Logical Names Files and Logical Names C.2 MDMS File Names Table_C-2_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ SLS$TAPMGRRQ.EXE RQ manager executable SLS$TRANSPORT.EXE Moves volumes to vault SLS$VAULT_PROFILE_RPT.EXE Vault profile report executable SLS$VERSION_CHECK_AND_ Command procedure to verify your COPY.COM OpenVMS software version against the versions of BACKUPCMD.CLD and VMSBUXX.EXE; you use this procedure if you upgrade OpenVMS after you have installed MDMS SLS$VOLUME.EXE Maintenance program for volumes in StorageTek ACS robots SLS.FLB File library for MDMS STABACK_TAPES.COM Allocates tapes for a standalone backup STARTUP.COM MDMS startup command file * SWITCHLABEL.COM Used in label printing TAPEMENU.HLP Help file for TUSERMENU.COM TAPEPURGEX.COM Purges scratchable tape's subprocess TAPEPURGEX.MSG Purges scratchable tape's mail message TAPES_OFFSITE_MSTRPT.COM Tapes offsite report definition file TAPEUSERUN.COM Generates tape usage report batch job * TAPMGRDBOFF.COM DB manager shutdown command file * TAPMGRDBRUN.COM DB manager startup command file * TAPMGRDBXEQ.COM DB manager detached process command file TAPMGRRQRUN.COM RQ manager startup command file TAPMGRRQXEQ.COM RQ manager detached process command file TAPMGRRUN.COM Starts TAPMGRDB and TAPMGRRQ command files (continued on next page) Files and Logical Names C-11 Files and Logical Names C.2 MDMS File Names Table_C-2_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ TAPMGRUTXEQ.COM Utility manager detached process command file TAPMGRUT_FREE.COM Free tape utility processor TAPMGRUT_MIDNIT.COM Midnight utility processor TOPERMENU.COM TOPER menu command file TRANS_TAPES_MSTRPT.COM Defines volume report for volumes in transition TUSERMENU.COM Another user menu VAULT.COM Sets location of volumes in or out of vault VAULTMENU.COM Vault menu command file VAULT_DATES.DAT Onsite and offsite dates for SET_ VAULT_DATES VAULT_PROFILE_RPT_RUN.COM__Vault_profile_report_batch_job________ C-12 Files and Logical Names Files and Logical Names C.3 ABS Logical Names C.3 ABS Logical Names The following logical names are entered into the system logical name table when the ABS installation procedure is complete. These names are stored in the startup file, SYS$STARTUP:ABS$STARTUP.COM. They are automatically entered into the system logical name table whenever the system reboots or whenever the software is invoked. Table_C-3__ABS_Logical_Names_______________________________ Logical_Name__________Description__________________________ ABS$CATALOG This logical name points to the directory containing the ABS catalogs. ABS$CLIENT_DB Stores the license information for UNIX and NT clients. ABS$DATABASE This logical name points to the Rdb/VMS database used by ABS to store policy objects. ABS$GUI This logical name points to the executable image of the ABS graphical user interface (GUI). ABS$LISTINGS This logical name points to the directory where listing files produced by ABS will reside when requested by the customer. ABS$LOG This logical name points to the directory where all log files for save and restore operations are placed. ABS$ROOT This logical name defines the top of the directory tree used by ABS to store its files. For_portability_purposes,_each_logical_name_also_has_a_____ corresponding "underscore" version of the logical name. For example, ABS$CATALOG also translates as ABS_CATALOG. (continued on next page) Files and Logical Names C-13 Files and Logical Names C.3 ABS Logical Names Table_C-3_(Cont.)__ABS_Logical_Names_______________________ Logical_Name__________Description__________________________ ABS$SYSTEM This logical name points to the directory where all ABS system files and images reside. ABS$TEMPLATES This logical name points to the directory where the templates used to control backup agents are stored. Recommendation: It is not recommended that you modify these templates. The behavior of ABS in regard to its backup agents is defined by these templates. ABS_CATALOG_CLEANUP Defined when the catalog cleanup utility is executed. ABS_DIAGNOSTIC_LEVEL Typeiclly, ABS provides all diagnostic levels in the log files. You can limit the number of messages output to the log file by setting this to a smaller number. ABS_PIXMAP_LOC Defines the location of the .PXM files used by the GUI. ABS_UID_LOC Defines the location of the .UID files used by the GUI. MOUNT_RETRY_INTERVAL Defines the amount of time that ABS waits before attempting to retry the next save or restore operation. For_portability_purposes,_each_logical_name_also_has_a_____ corresponding "underscore" version of the logical name. For example, ABS$CATALOG also translates as ABS_CATALOG. ___________________________________________________________ C.4 MDMS Logical Names Table C-4 lists the logical names entered into the logical name tables LNM$SYSTEM_TABLE and LNM$SLS$TABLE when MDMS software is installed. These names are defined by the product's startup file. They are automatically entered into these logical name tables whenever the system reboots or whenever the software is invoked. C-14 Files and Logical Names Files and Logical Names C.4 MDMS Logical Names The LNM$JOB table also contains logical names that are defined when a user logs in to a system running MDMS software. Table_C-4_MDMS_Logical_Names_____________________________________ Logical_Name_______Definition_and_Description____________________ LNM$SYSTEM_TABLE Entries__________________________________________________________ SLS$CUSTOM SLS$ROOT:[CUSTOM] This directory contains customized MDMS files for your site. SLS$DATA SLS$ROOT:[DATA.nodename] This directory stores all the log files for your current MDMS system. SLS$DATAC SLS$ROOT:[DATA] This is the top level directory for log file storage. SLS$LABEL filespec or _NL: or device: This logical points to the current label file or printer where labels are printed. SLS$LABEL_ fullfilespec TEMPLATE This logical points to the current label file template. SLS$MAILBOX mbx_id The mailbox used for communication to the SLS$TAPMGRRQ process. SLS$MASTER SLS$ROOT:[PRIMAST] This directory points to the node's database, whether this is your current node or a node remote to you. SLS$PARAMS SLS$ROOT:[PARAMS] (continued on next page) Files and Logical Names C-15 Files and Logical Names C.4 MDMS Logical Names Table_C-4_(Cont.)_MDMS_Logical_Names_____________________________ Logical_Name_______Definition_and_Description____________________ LNM$SYSTEM_TABLE Entries__________________________________________________________ This directory contains the system dependent parameter files for MDMS software. SLS$ROOT device:[SLS$FILES.] This directory points to the top level directory for MDMS files. SLS$STARTUP_P1 REBOOT Used internally during startup. SLS$SYSTEM SLS$ROOT:[CUSTOM] SLS$ROOT:[SYSTEM] This directory contains all the files for running MDMS software. SLS$VAULT DPS The location for volumes sent offsite. (continued on next page) C-16 Files and Logical Names Files and Logical Names C.4 MDMS Logical Names Table_C-4_(Cont.)_MDMS_Logical_Names_____________________________ _________________________________________________________________ LNM$SLS$TABLE_Entries____________________________________________ PRINODNAME nodename Name of node where primary volume database resides. SERVER_NODES nodename Name of node(s) defined as MDMS server nodes. This logical only appears on MDMS client nodes. SLS$LCLMAST ? Defined as a "?". TAPMGRDB_PROCID proc_id Points to the process ID of the database manager process. This logical only appears on MDMS serveer nodes. TAPMGRRQ_PROCID proc_id Points to the process ID of the request _________________________manager_process.________________________ More logical names for MDMS software can be found in the logical name table LNM$SLS$VALUES. These logicals are defined whenever TAPESTART.COM executes. Sample output is shown in Example C-1. Files and Logical Names C-17 Files and Logical Names C.4 MDMS Logical Names Example C-1 Sample List of LNM$SLS$VALUES Entries $ SHOW LOGICAL/TABLE=LNM$SLS$VALUES (LNM$SLS$VALUES) "BACKUP_DEFAULT_REEL" = " " "DEFAULT_ALLDEV" = " " "DEFAULT_ALLOCSCRATCH" = "365 0:0:0" "DEFAULT_ALLOCSIZE" = "2400" "DEFAULT_ALLTIM" = "0 0:0:30" "DEFAULT_BACKUPSCRATCH" = "365 0:0:0" "DEFAULT_BACKUPSIZE" = "0" "DEFAULT_BAKFMT" = "BACKUP" "DEFAULT_BAKOPT" = "DUMMY" "DEFAULT_BAKUIC" = "0" "DEFAULT_BATCHQUEUE" = "SLS$ILDUCE" "DEFAULT_DCSC_DRIVES" = " " "DEFAULT_DCSC_EXPORT_MTYPE" = "DCSC_EXPORT_MTYPE" "DEFAULT_DENS_1" = "6250" "DEFAULT_DENS_10" = " " "DEFAULT_DENS_11" = " " "DEFAULT_DENS_12" = " " "DEFAULT_DENS_13" = " " "DEFAULT_DENS_14" = " " "DEFAULT_DENS_15" = " " "DEFAULT_DENS_16" = " " "DEFAULT_DENS_17" = " " "DEFAULT_DENS_18" = " " "DEFAULT_DENS_19" = " " (continued on next page) C-18 Files and Logical Names Files and Logical Names C.4 MDMS Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_DENS_2" = " " "DEFAULT_DENS_20" = " " "DEFAULT_DENS_21" = " " "DEFAULT_DENS_22" = " " "DEFAULT_DENS_23" = " " "DEFAULT_DENS_24" = " " "DEFAULT_DENS_25" = " " "DEFAULT_DENS_26" = " " "DEFAULT_DENS_27" = " " "DEFAULT_DENS_28" = " " "DEFAULT_DENS_29" = " " "DEFAULT_DENS_3" = " " "DEFAULT_DENS_30" = " " "DEFAULT_DENS_31" = " " "DEFAULT_DENS_32" = " " "DEFAULT_DENS_4" = " " "DEFAULT_DENS_5" = " " "DEFAULT_DENS_6" = " " "DEFAULT_DENS_7" = " " "DEFAULT_DENS_8" = " " "DEFAULT_DENS_9" = " " "DEFAULT_DRIVES_1" = " " "DEFAULT_DRIVES_10" = " " "DEFAULT_DRIVES_11" = " " "DEFAULT_DRIVES_12" = " " "DEFAULT_DRIVES_13" = " " "DEFAULT_DRIVES_14" = " " "DEFAULT_DRIVES_15" = " " "DEFAULT_DRIVES_16" = " " "DEFAULT_DRIVES_17" = " " "DEFAULT_DRIVES_18" = " " "DEFAULT_DRIVES_19" = " " (continued on next page) Files and Logical Names C-19 Files and Logical Names C.4 MDMS Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_DRIVES_2" = " " "DEFAULT_DRIVES_20" = " " "DEFAULT_DRIVES_21" = " " "DEFAULT_DRIVES_22" = " " "DEFAULT_DRIVES_23" = " " "DEFAULT_DRIVES_24" = " " "DEFAULT_DRIVES_25" = " " "DEFAULT_DRIVES_26" = " " "DEFAULT_DRIVES_27" = " " "DEFAULT_DRIVES_28" = " " "DEFAULT_DRIVES_29" = " " "DEFAULT_DRIVES_3" = " " "DEFAULT_DRIVES_30" = " " "DEFAULT_DRIVES_31" = " " "DEFAULT_DRIVES_32" = " " "DEFAULT_DRIVES_4" = " " "DEFAULT_DRIVES_5" = " " "DEFAULT_DRIVES_6" = " " "DEFAULT_DRIVES_7" = " " "DEFAULT_DRIVES_8" = " " "DEFAULT_DRIVES_9" = " " "DEFAULT_FRESTA" = "2" "DEFAULT_MAXSCRATCH" = "31-DEC-9999 23:59:59.99" "DEFAULT_MTYPE_1" = "9TRACK" "DEFAULT_MTYPE_10" = " " "DEFAULT_MTYPE_11" = " " "DEFAULT_MTYPE_12" = " " "DEFAULT_MTYPE_13" = " " "DEFAULT_MTYPE_14" = " " "DEFAULT_MTYPE_15" = " " (continued on next page) C-20 Files and Logical Names Files and Logical Names C.4 MDMS Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_MTYPE_16" = " " "DEFAULT_MTYPE_17" = " " "DEFAULT_MTYPE_18" = " " "DEFAULT_MTYPE_19" = " " "DEFAULT_MTYPE_2" = " " "DEFAULT_MTYPE_20" = " " "DEFAULT_MTYPE_21" = " " "DEFAULT_MTYPE_22" = " " "DEFAULT_MTYPE_23" = " " "DEFAULT_MTYPE_24" = " " "DEFAULT_MTYPE_25" = " " "DEFAULT_MTYPE_26" = " " "DEFAULT_MTYPE_27" = " " "DEFAULT_MTYPE_28" = " " "DEFAULT_MTYPE_29" = " " "DEFAULT_MTYPE_3" = " " "DEFAULT_MTYPE_30" = " " "DEFAULT_MTYPE_31" = " " "DEFAULT_MTYPE_32" = " " "DEFAULT_MTYPE_4" = " " "DEFAULT_MTYPE_5" = " " "DEFAULT_MTYPE_6" = " " "DEFAULT_MTYPE_7" = " " "DEFAULT_MTYPE_8" = " " "DEFAULT_MTYPE_9" = " " "DEFAULT_PROTECTION" = "307" "DEFAULT_RESOPT" = "DUMMY" "DEFAULT_SELDEV" = " " (continued on next page) Files and Logical Names C-21 Files and Logical Names C.4 MDMS Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "DEFAULT_USRRSS" = "128" "DEFAULT_VERBOSE" = "0" "ESC_ALLOC_BOLD" = ". .[1m" "ESC_ALLOC_NORM" = ". .[m" "ESC_LOAD_BLNK" = ".[5m.[7w" "ESC_LOAD_BOLD" = ".[1m.[7w" "ESC_LOAD_NORM" = ".[m.[w" "ESC_MOUNT_BOLD" = ". .[1m" "ESC_MOUNT_NORM" = ". .[m" "ESC_MOUNT_OPER" = "...[1m.#6 OPERATOR:" "LOCATION" = "HEADQUARTERS" "MGRPRI" = "8" "NET_REQUEST_TIMEOUT" = "120" "NODENAME" = "ILDUCE" "PRIV_CLEAN" = "OPER" "PRIV_LABEL" = "OPER" "PRIV_MAXSCR" = "OPER" "PRIV_MODANY" = "OPER" "PRIV_MODOWN" = "TMPMBX" "PRIV_SEEANY" = "OPER" "PRIV_V_CLEAN" = "18" "PRIV_V_LABEL" = "18" "PRIV_V_MAXSCR" = "18" "PRIV_V_MODANY" = "18" "PRIV_V_MODOWN" = "15" "PRIV_V_SEEANY" = "18" "QUICKLOAD" = "0" "QUICKLOAD_RETRIES" = "80" "REMOTE_RETRIES" = "5" "TAPEPURGE_MAIL" = "SYSTEM " "TAPEPURGE_WORK" = "MAIL " "TOPERMASK" = "1024" (continued on next page) C-22 Files and Logical Names Files and Logical Names C.4 MDMS Logical Names Example C-1 (Cont.) Sample List of LNM$SLS$VALUES Entries "TOPERSTRING" = "TAPES" "TRANS_AGE" = "14 0:0:0" "USERBACK_FIRSTLINE" = "$!" "USERNAME" = "SLS" "VERSION" = "T25" "VMSV5" = "1" "XREQ_LEN" = "241" "XREQ_REPL_LEN" = "232" Files and Logical Names C-23 _________________________________________________________________ Glossary This glossary contains terms defined for the Archive/Backup System for OpenVMS (ABS). It also contains some terms associated with the following products when related to ABS: o Media and Device Management Services for OpenVMS (MDMS) o Storage Library System for OpenVMS (SLS) absolute time A data-entry format for specifying the date or time of day. The format for absolute time is [dd-mmm- yyyy[:]][hh:mm:ss.cc]. You can specify a specific date and time, or use the keywords TODAY, TOMORROW, or YESTERDAY. access port The port on a DCSC-controlled silo where cartridges can be inserted into the silo. active server process The MDMS server process that is currently active. The active server process responds to requests issued from an MDMS client process. allocate To reserve something for private use. In MDMS software, a user is able to allocate volumes or devices. allocated The state of a device or resource when a process is granted exclusive use of that device or resource. The device or resource remains allocated until the process gives up the allocation. Glossary-1 allocated state One of four volume states. Volumes that are reserved for exclusive use by a user are placed in the allocated state. Allocated volumes are available only to the user name assigned to that volume. ANSI The abbreviation for the American National Standards Institute, an organization that publishes computer industry standards. ANSI-labeled A magnetic tape that complies with the ANSI standards for label, data, and record formats. The format of VMS ANSI- labeled magnetic tape volumes is based on Level 3 of the ANSI standard for magnetic tape labels and file structure. archive A repository of data that consists of o Archive media that contains zero or more archive files. o One or more archive catalogs that record information about archive files and archive objects stored on archive media. o A set of archive services which are used to define configuration and site policy. They are also used to move data between the archive client and the archive media. archive file system The file system that contains the archived data. archive object The data object that resides in offline storage. archiving Saving data to the appropriate media for the purpose of long-term storage. Glossary-2 ASCII The abbreviation for the American Standard Code for Information Interchange. This code is a set of 8-bit binary numbers representing the alphabet, punctuation, numerals, and other special symbols used in text representation and communications protocols. back up To make duplicate copies of one or more files, usually onto different media than the original media. This provides the availability to restore the original data if it is lost or corrupted. backup agent The client or utility that performs the actual data movement and backup operation. Examples are the VMS BACKUP Utility and the RMU Backup Utility. backup engine The backup engine is used to move data to and from the archive. Examples: VMS BACKUP and RMU BACKUP. BACKUP format Standard VMS BACKUP format. The BACKUP format is the recording format used by the VMS Backup utility to back up data to save sets. backup management domain A node or OpenVMS Cluster system that has control over creating save requests. A backup management domain is usually controlled by a single storage administrator. bind The act of logically binding volumes into a magazine. This makes the volumes a logical unit that cannot be separated unless an UNBIND operation is done on the volumes. Glossary-3 blocking factor The number of records in a physical tape block. The length of a physical block written to magnetic tape is determined by multiplying the record length by the blocking factor. For example, if a record length of 132 and a blocking factor of 20 are specified, the length of each physical block written to tape will be 2640 bytes (or characters). The blocking factor is only used when MDMS software is writing an EBCDIC tape. catalog Contains records of data movement operations. Each time a save request is initiated, the history of the data movement operation is recorded in an associated ABS catalog. central security domain The node or OpenVMS Cluster system where the ABS policy server is installed. This domain controls all ABS policy objects, particularly storage classes and execution environments. client node Client nodes send database requests to the the server node. combination time A data-entry format for specifying date and time. Combination time consists of an absolute time value plus or minus a delta time value. Examples: "TODAY+7-" indicates current date plus seven days "TODAY+7" indicates current date plus seven hours "TOMORROW-1" indicates current date at 23:00 hours command An instruction, generally an English word, entered by the user at a terminal. The command requests the software to perform a predefined function. CRC The acronym for cyclic redundancy check. It is a verification process used to ensure data is correct. Glossary-4 consolidation count The criteria under which ABS creates new volume sets. consolidation inteval The number of days (in VMS time format) between the creation of new volume sets. consolidation size The desired maximum number of volumes allowed in a volume set. data object A data object specification, such as an OpenVMS file name or an Rdb/VMS database file name. data movement request Either a save or restore request initiated through either the DCL command interface or the ABS graphcial user interface. deallocate To relinquish ownership of a device or media set. o When a drive is deallocated, it is then available for allocation by other processes. o When a media set is deallocated, it is either immediately available for allocation by other users or moved into a transition state. default A value or operation automatically included in a command or field unless the user specifies differently. density The number of bits per inch (bpi) on magnetic tape. Typical values are 6250 bpi and 1600 bpi. device A physical device, such as a tape drive or disk or disk device. Glossary-5 down One of four volume states. Volumes that are either damaged, lost, or temporarily removed for cleaning are placed in the down state. EBCDIC Extended Binary Coded Decimal Interchange Code. EBCDIC is an unlabeled IBM recording format. Volumes in EBCDIC format do not have records in the MDMS volume database. execution environment The ABS policy object that defines the environment in which data movement operations occur. expiration The date and time at which an archived data object is no longer considered useful. The archived data object can be deleted and its space removed. format See recording format. free state The volume state that allows volumes to be selected by users or other software applications. in port The physical opening in a jukebox where cartridges can be imported into the jukebox. interface A shared physical or logical boundary between computing system components. Interfaces are used for sending and /or accepting information and control between programs, machines, and people. inventory The act of automatically updating the MDMS database. MDMS can mount each volume located in a magazine and update the MDMS volume database through this process. Glossary-6 I/O station A jukebox component that enables an operator to manually insert and retrieve volumes. The I/O station consists of an I/O station door on the outside of the jukebox and an I/O station slot on the inside. See also I/O station door and I/O station slot. I/O station door An actual door on the outside of the jukebox that can be opened and closed. Behind the I/O station door is the I/O station slot. I/O station slot An I/O slot that holds a cartridge when it is entering or leaving the jukebox. label o Information recorded at a fixed location on the media that identifies the volume to software. o The physical printed label attached to the outside of a tape or cartridge to identify it. labeled A recording format that includes a volume label. LEBCDIC Labeled EBCDIC format. See also EBCDIC. load The process which makes a volume physically available to the computer system, such as for read or write operations. local symbol A symbol meaningful only to the module or DCL command procedure that defines it. log file Any file into which status and error messages are written to reflect the progress of a process. Glossary-7 MDMS software The MDMS software is an OpenVMS software service that enables you to implement media and device management for your storage management operations. MDMS provides services to SLS, ABS, HSM, and SMF. MDMS standby server process Any MDMS server process that is not currently active. The standby server process waits and becomes active if the active server process fails. magazine A physcial container that holds from 5 to 11 tape cartridges (volumes). The magazine contains a set of logically bound volumes that reside in the MDMS database. magazine database The MDMS database that contains the magazine name and the volume names associated with that magazine. media A mass storage unit. Media provides a physical surface on which data is recorded. Examples are magnetic tape, tape cartridge, and optical cartridge. media type A set of site-specific names with associated densities, drives, in MDMS. nearline storage Storage in which file headers are accessible through the operating system, but accessing data requires extra intervention. Nearline storage employs a robotic device to move media between drives and the media storage locations. Nearline storage is less costly for each megabyte of data stored. Access times for data in nearline storage vary. Access to data may be nearly instantaneous when a cartridge containing the data is already loaded in a drive. The time required for a robotic device to move to the most distant storage location, retrieve a cartridge, load it into a Glossary-8 drive, and position the media determines the maximum access time. The devices of nearline storage technology include, but are not limited to, automated tape libraries and optical media jukeboxes. offline storage Storage in which neither the file headers nor the data is accessible by the operating system and requires extra intervention. Offline storage requires some type of intervention to move media between drives and the media storage locations. Offline storage is the least costly for each megabyte of data stored. Access times for data in offline storage vary for the same reasons as described for nearline storage. For archive data stored in a remote vault, access time can take more than a day. The devices of offline storage technology include, but are not limited to, standalone tape drives, optical disk drives, and sequential stack loader tape drives. online storage Storage in which file headers and data can be accessed through the operating system. Online storage is the most costly for each megabyte of data stored. As a trade off, online storage also offers the highest access performance. Online storage devices offer continuous service. The devices of online storage technology include disk storage and electronic (RAM) storage that uses disk I/O channels. OPCOM VMS Operator Communication Manager. An online communication tool that provides a method for users or batch jobs to request assistance from the operator, and allows the operator to send messages to interactive users. Glossary-9 OPER privilege The level of privilege required by a system operator to suspend an MDMS operation and to perform a variety of maintenance procedures on volumes, as well as archive files and saved system files. out port The physical opening in a jukebox where cartridges can be exported from the jukebox. policy The decisions and methods in which you implement your ABS policy. This includes when and how often you back up or archive data objects from online to offline storage. policy engine The component in ABS that makes intelligent decisions based upon the implementation of your ABS policy. policy objects The method in which ABS enables you to implment your ABS policy. ABS provides the following policy objects: o Storage class o Save request o Restore request o Execution environment policy server The ABS server component. Placement of this component determines the central security domain (CSD). pool A set of volumes in the free state. Those volumes can be allocated by users who have access to the volume pool. The storage administrator creates and authorizes user access to pools. Glossary-10 record A set of related data treated as a unit of information. For example, each volume that is added to the MDMS volume database has a record created that contains information about the volume. record length The length of a record in bytes. See also blocking factor. recorded label The label recorded on the media. recording format The unique arrangement of data on a volume according to a predetermined standard. Examples of recording format are BACKUP, EBCDIC, and ANSI. restore process The method by which the contents of a file are recovered from a volume or volumes that contain the saved file. SLS software will restore file contents by reading BACKUP save sets from one or more volumes, extracting the file contents from those save sets, and placing the information onto a Files-11 structured disk where the restored file can be accessed by a user. restore request A request to restore data from the archive media to either its original location or an alternate location. Restore requests are initiated either through the DCL command interface or the ABS graphical user interface. requester The user who submits a save or restore request. requester profile The requester profile is the profile of the user who is creating the save or restore request. This profile is captured at the time the request is created. Glossary-11 restore request The ABS policy object that defines the request for the restoration of data object sets. robot device A tape or optical device that provides automatic loading of volumes, such as a TF867 or a TL820. save process The method by which copies of files are made on magnetic or optical cartridges for later recovery or for transfer to another site. For BACKUP formatted volumes, an ABS save operation creates BACKUP save sets on magnetic tape, a system disk, or optical cartridge. save request The ABS policy object that defines the request for saving data object sets. save set A file created by the VMS Backup utility on a volume. When the VMS Backup utility saves files, it creates a file in BACKUP format called a save set on the specified output volume. A single BACKUP save set can contain numerous files. Only BACKUP can interpret save sets and restore the files stored in the save set. deassign date The day on which an allocated volume is scheduled to go into the transition state or the free state. server node The node to which all MDMS database requests are sent to be serviced. In a high-availability configuration, when the active server node fails, another node in the OpenVMS Cluster system becomes the active server node. Glossary-12 slot A vertical storage space for storing a cartridge. The storage racks and cabinets used in data centers contain multirow slots that are labeled to easily locate stored media. state The MDMS state at which volumes are placed in the volume life cycle. Valid states are allocated, scratch, down, and released. See also volume state. storage administrator One or more privileged users responsible for installing, configuring, and maintaining the ABS software. This user has enhanced ABS authorization rights and privileges and controls the central security domain (CSD) by creating and maintaining storage classes and execution environments. storage class The ABS policy object that defines the location of archive data. SYSPRV privilege The level of privilege required to install the MDMS software and add user names to the system. system backup ABS system backup procedure. The system backup procedure backs up system files. Using POLYCENTER Scheduler, the system backup can direct the ABS software to perform automatic save operations on a predetermined schedule. tape A basic unit of media. transition state Volumes in the transition state are in the process of being deallocated, but are not yet fully deallocated. The transition state provides a grace period during which a volume can be reallocated to the original owner if necessary. Glossary-13 UASCII Unlabeled ASCII format. See also ASCII. UIC User identification code. The pair of numbers assigned to users, files, pools, global sections, common event flag clusters, and mailboxes. The UIC determines the owner of an object. UIC-based protection determines the type of access available to the object for its owner, members of the same UIC group, system accounts, and other (world) users. UID A globally unique identifier for this instance of an object. unbind The act of unbinding a volume or volumes from a magazine. unlabeled A recording format that does not include a recorded label. user backup A backup operation initiated by an individual user (not the system) when they would like to make copies of a file or set of files for later recovery or for transfer to another site. user profile The set of information about a user that defines the user's right to access data on a VMS system and execute privileged commands. For ABS on VMS, this includes the following information: User name UIC Privileges Access right identifiers vault An off-site storage location to where volumes are transferred for safekeeping. Glossary-14 VMS Backup utility A VMS Operating System utility that performs save and restore operations on files, directories, and disks using the BACKUP recording format. volume A logical unit of data that is stored on media. A volume can be stored on a single magnetic tape or disk, or as in the case of an optical cartridge, can refer to one side of double-sided media. A volume assigns a logical name to a piece of media, or to a side of double-sided media. volume ID The volume identification used to verify that the correct volume has been selected. The volume label should be the same as the volume ID. volume name An internal, machine-readable name associated with a media object to allow software to verify the media. volume set A set of volumes containing one or more save sets. ABS adds volumes to a volume set until the storage class consolidation criteria is exceeded. volume set One or more volumes logically connected in a sequence to form a single set. Volume sets are usually created when a single logical unit of data needs to be stored on more than one physical medium. volume state A volume status flag. In MDMS software, volumes are placed in one of the following states: o Free o Allocated o Transition o Down Glossary-15 wildcard character A nonnumeric or nonalphanumeric character such as an asterisk (*) or percent sign (%) that is used in a file specification to indicate "ALL" for a given field or portion of a field. Wildcard characters can replace all or part of the file name, file type, directory name, or version number. Glossary-16 _________________________________________________________________ Index A______________________________ F______________________________ Access control, 3-59 File names, C-1 to C-23 Access right identifiers, 3-59 Free blocks Alpha system, 3-38 how to determine, 2-17 with OpenVMS system, 3-38 B G______________________________ _______________________________ Global symbols Backup operations defining, 3-13 remote, 3-26 C H______________________________ _______________________________ Hardware Clients requirements, 2-16 authorizing, B-1 How to Configuration determine free blocks, 2-17 default policy, 3-60 edit the system login file, D 3-13 _______________________________ Default policy configuration, I______________________________ 3-60 Installation, 3-1 Disk space requirements, 2-17 ABS, 3-28 Alpha system, 3-38 E______________________________ MDMS, 3-2 Editing the system login file, mixed-architecture system, 3-13 3-38 Editing the systemwide command POLYCENTER Scheduler, 2-28 files, 3-13 prerequisites, 2-1 Error recovery, 3-57 procedure, 3-2, 3-283-62 Examples Installation Verification authorizing NT clients, B-1 Procedure authorizing UNIX clients, see IVP B-1 Index-1 Installing NT clients, 3-44 O______________________________ IVP OpenVMS Cluster error recovery, 3-57 mixed-architecture, 3-38 requirements, 3-58 L______________________________ OpenVMS operating system License, 2-24 to 2-28 classes adding NT clients, B-1 required, 2-16 adding UNIX clients, B-1 OpenVMS system loading, 2-24 Alpha system, 3-38 registering, 2-24 Operating system requirements, LNM$SLS$TABLE entries, C-17tbl 2-16 LNM$SLS$VALUES entries sample, C-17fig P______________________________ LNM$SYSTEM_TABLE entries, POLYCENTER Scheduler C-15tbl installation, 2-28 Logical names, C-1 to C-23 Port, 3-47, B-2 LNM$JOB, C-15 Postinstallation LNM$SLS$TABLE, C-14 editing systemwide command LNM$SLS$VALUES, C-17 files, 3-13 LNM$SYSTEM_TABLE, C-14 editing the system login M file, 3-13 _______________________________ Preinstallation MDMS client node, 3-9 tasks, 2-1 MDMS client node access Prerequisites registering, 3-9 software, 2-18 Mixed-architecture system, Privileges, 3-59 3-38 Process requirements, 2-23 N______________________________ Process account quotas, 2-22 NT clients R adding licenses, B-1 _______________________________ authorizing, B-1 Remote backup operations, 3-26 installing, 3-44 Remote Device Facility modifying, B-3 server support, 3-26 port number, 3-47, B-2 Remote drives, 3-26 removing, B-4 configuring, 3-26 showing, B-4 Requirement POLYCENTER Scheduler, 2-28 Requirements, 2-16 disk space, 2-17 hardware, 2-16 installation, 2-4 client software, 2-5, 2-7 Index-2 Requirements Software requirements, 2-18 installation (cont'd) Symbols server software, 2-5, 2-6 global, 3-13 OpenVMS Cluster, 3-58 System OpenVMS operating system OpenVMS Cluster, 3-58 classes, 2-16 parameter requirements, 2-21 process account quotas, 2-22 parameters, 2-21 processes, 2-23 process account quotas, 2-22 quotas, 2-22 System startup procedure, 3-13 software, 2-18 T system parameters, 2-21 _______________________________ Tasks S______________________________ preinstallation, 2-1 Server U definition, 2-4 _______________________________ Software UNIX clients, 3-47 to 3-57 client, 2-5, 2-7 adding licenses, B-1 installing, 3-1 authorizing, B-1 installing ABS, 3-28 configuring, 3-47 to 3-57 requirements, 2-18 modifying, B-3 server, 2-5, 2-6 removing, B-4 installing, 3-28 showing, B-4 Index-3