Hierarchical_Storage_Management_for_OpenVMS_________ Installation and Configuration Guide Order Number: AA-QUJ1D-TE Software Version: HSM Version 2.2 Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ 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 sublicensor, or the identified licensor. 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 1997. All Rights Reserved. Printed in the U.S.A. Alpha, DEC, DECnet, DECthreads, OpenVMS, POLYCENTER Scheduler, TA, TK, VAX, VAXcluster, VMS, VMScluster, and the DIGITAL logo are trademarks of Digital Equipment Corporation. PostScript is a registered trademark of Adobe Systems, Inc. StorageTek is a registered trademark of Storage Technology Corp. 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................................................... ix 1 Welcome to HSM 1.1 What Do All Storage Environments Have In Common?.......................................... 1-1 1.2 What Makes a Storage Environment Unique?......... 1-1 1.3 How Does HSM Complement Your Storage Environment?..................................... 1-2 1.4 What Is The Purpose of a Managed Media and Device Environment?..................................... 1-3 1.5 What is the Difference Between HSM Basic Mode and Plus Mode?....................................... 1-4 1.5.1 HSM Basic Mode Functions ...................... 1-5 1.5.2 HSM Plus Mode Functions ....................... 1-5 1.5.3 HSM Mode Comparison Table ..................... 1-6 1.5.4 Choosing HSM Modes ............................ 1-7 1.5.5 HSM Mode Change Restrictions .................. 1-8 1.6 HSM License Types................................ 1-8 1.6.1 HSM Base Licenses ............................. 1-8 1.6.2 HSM Capacity Licenses ......................... 1-9 1.7 HSM Concurrent Use Licenses...................... 1-10 1.8 Installation Changes when SLS is Present......... 1-10 1.9 HSM Upgrade Considerations....................... 1-11 1.10 Backing HSM Up the Catalog....................... 1-12 1.11 Backing up Your System Disk...................... 1-12 1.12 VMScluster System Considerations................. 1-12 1.13 Mixed Architecture Environments.................. 1-13 1.13.1 Mixed Architecture Environments ............... 1-13 1.13.2 Principles Guiding Mixed Architecture Configuration.................................. 1-14 iii 1.13.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster................... 1-15 1.13.3.1 Separate Disk Configuration................. 1-15 1.13.3.2 Separate Root Configuration................. 1-16 1.13.3.3 Separate Subdirectory Configuration......... 1-16 1.13.4 Implementation Specific Approach .............. 1-17 1.14 Overview of the HSM Installation Process......... 1-17 2 MDMS Preinstallation Requirements 2.1 Configuring Your Hardware........................ 2-1 2.1.1 Hardware Configuration For an Automated Media Library........................................ 2-1 2.1.1.1 Hardware Installation....................... 2-2 2.1.1.2 Test the Hardware........................... 2-2 2.1.2 Hardware Configuration for a Media Loader ..... 2-3 2.1.2.1 Hardware Installation....................... 2-3 2.1.2.2 Test the Hardware........................... 2-4 2.1.3 Hardware Configuration for an Operator Attended Drive.......................................... 2-5 2.1.3.1 Hardware Installation....................... 2-5 2.1.3.2 Test the Hardware........................... 2-6 3 MDMS Software Installation and Configuration 3.1 Installing the Media and Device Management Software......................................... 3-1 3.1.1 Installing the MDMS Server Software ........... 3-3 3.1.2 Installing the MDMS Client Software ........... 3-8 3.1.3 How to Configure for VAX and Alpha Systems .... 3-10 3.2 MDMS Postinstallation Tasks...................... 3-11 3.2.1 Verifying the MDMS Installation ............... 3-12 3.2.2 Providing Automatic Start Up and Shut Down .... 3-12 3.2.3 Defining Global Symbols for MDMS Users ........ 3-12 3.2.4 Defining the OpenVMS Cluster Alias Name and the Failover Server Nodes.......................... 3-13 3.2.5 Defining a Network Object on an OpenVMS Cluster........................................ 3-13 3.2.6 Configuring MDMS for an Automated Tape Library System......................................... 3-16 3.2.6.1 Configure MDMS.............................. 3-16 3.2.6.2 Test the MDMS Configuration................. 3-17 iv 3.2.7 Configuring MDMS for a Media Loader ........... 3-19 3.2.7.1 Configure MDMS.............................. 3-19 3.2.7.2 Test the MDMS Configuration................. 3-21 3.2.8 Configuring for an Operator Attended Drive .... 3-22 3.2.8.1 Configure MDMS.............................. 3-23 3.2.8.2 Test the MDMS Configuration................. 3-24 3.2.9 Configuring Remote Tape or Optical Drives ..... 3-24 3.2.9.1 On The System Where the Tape or Optical Drive Resides............................... 3-25 3.2.9.2 On The System Where the Data Resides........ 3-26 4 Meeting the HSM Installation Requirements 4.1 Requirements List................................ 4-1 4.2 Read the Release Notes........................... 4-1 4.3 Required Software................................ 4-2 4.4 Required for HSM Basic Mode...................... 4-2 4.5 Required for HSM Plus Mode....................... 4-2 4.6 Required for HSM Repack Function................. 4-3 4.7 Required Hardware Disk Space..................... 4-3 4.8 Required System Privileges....................... 4-4 4.9 Required System Parameters....................... 4-4 4.10 Required for VMSINSTAL........................... 4-4 4.11 Installing DECthreads Images..................... 4-6 4.12 Registering Your HSM License..................... 4-6 5 Installing HSM Software 5.1 Installing the HSM Software...................... 5-1 5.1.1 The Installation Procedure .................... 5-1 5.1.2 Error Recovery ................................ 5-7 5.2 After Installing HSM Software.................... 5-8 5.2.1 Editing the System Startup and Shutdown Files.......................................... 5-8 5.2.2 Creating an HSM Catalog ....................... 5-9 5.3 Installation Verification Procedure.............. 5-10 v 6 Getting Started with HSM 6.1 HSM's Default Configuration...................... 6-1 6.1.1 The Default Facility .......................... 6-2 6.1.2 The Default Shelf ............................. 6-2 6.1.3 The Default Device ............................ 6-3 6.1.4 The Default Volume ............................ 6-3 6.1.5 The Default Policies .......................... 6-4 6.2 Running HSM with the Default Configuration....... 6-5 6.2.1 Verifying the Facility Definition ............. 6-5 6.2.2 Defining Archive Classes for Use .............. 6-6 6.2.3 Selecting Archive Classes for the Default Shelf.......................................... 6-7 6.2.4 Defining Devices for the Archive Classes ...... 6-8 6.2.5 Initializing Tape Volumes for Each Archive Class.......................................... 6-10 6.2.6 Set Volume Retention Times for Policy-Based Shelving....................................... 6-12 6.3 Additional Configuration Items................... 6-13 6.3.1 Authorizing Shelf Servers ..................... 6-13 6.3.2 Working with a Cache .......................... 6-14 6.3.3 Running Default Policies ...................... 6-15 6.3.4 Template Policy Definitions ................... 6-15 6.3.4.1 Using a Template Policy Definition.......... 6-16 6.3.4.2 Changing Default Policy Definitions......... 6-17 6.4 Plus Mode Offline Environment.................... 6-17 6.4.1 How HSM Plus Mode and MDMS Work Together ...... 6-18 6.4.2 How MDMS Supports HSM ........................ 6-18 6.4.3 MDMS Commands for HSM Plus Mode Use ........... 6-19 6.4.4 MDMS Configuration Tasks Required to Support HSM Plus Mode.................................. 6-20 6.4.4.1 Defining Media Triplets..................... 6-21 6.4.4.2 Defining Tape Jukeboxes..................... 6-21 6.4.4.3 Adding Volumes to MDMS Database for HSM to Use......................................... 6-22 6.4.4.4 Authorizing HSM Access to Volumes........... 6-23 6.4.4.5 Importing Volumes Into a Jukebox............ 6-23 6.4.4.6 Configuring Magazines....................... 6-23 6.4.4.7 Importing Magazines or Volumes Into the Jukebox..................................... 6-24 6.4.4.8 Working with RDF-served Devices in HSM Plus Mode........................................ 6-25 6.5 HSM Plus Mode Configuration Examples............. 6-25 6.5.1 Sample TA90 Configuration ..................... 6-26 vi 6.5.2 Sample TZ877 Configuration .................... 6-27 6.5.3 Sample TL820 Configuration .................... 6-29 6.5.4 Sample RDF-served TL820 Configuration ......... 6-30 6.5.4.1 Definitions on Client Node.................. 6-30 6.5.4.2 Definitions on the RDF-served Node.......... 6-31 6.6 HSM Basic Mode Configuration Examples............ 6-32 6.6.1 TZ877 Sample Configuration .................... 6-33 6.6.2 RW500 Example ................................. 6-35 7 DFS, NFS, and PATHWORKS Access 7.1 DFS, NFS and PATHWORKS Access Support............ 7-1 7.1.1 DFS Access .................................... 7-1 7.1.2 NFS Access .................................... 7-1 7.1.3 PATHWORKS ..................................... 7-3 7.1.4 New Logical Names for NFS and PATHWORKS Access......................................... 7-4 A HSM Basic Mode Installation Example B HSM Plus Mode Installation Example C HSM Logicals C.1 HSM Logical Names................................ C-1 D HSM Files D.1 HSM File Names................................... D-1 E MDMS Logicals E.1 MDMS Logical Names............................... E-1 F MDMS Files F.1 MDMS File Names.................................. F-1 vii Index Examples E-1 Sample List of LNM$SLS$VALUES Entries ......... E-4 Tables 1-1 HSM Basic and Plus Functionality .............. 1-6 1-2 HSM Base Licenses ............................. 1-9 1-3 HSM Additional Capacity Licenses .............. 1-9 1-4 HSM Concurrent Use Licenses ................... 1-10 1-5 HSM Installation and Congifuration ............ 1-18 3-1 Stages of Installing MDMS ..................... 3-2 3-2 How to Install the MDMS Software .............. 3-4 3-3 How to Install the MDMS Client Software ....... 3-9 3-4 How to Configure in a Mixed Architecture OpenVMS Cluster System......................... 3-10 3-5 Comparing Logical Definitions Between VAX and Alpha Systems.................................. 3-11 3-6 How to Define the SLS$DBX NCP Object .......... 3-13 3-7 Enabling Remote Drive Selection ............... 3-25 4-1 Disk Space Requirements ....................... 4-3 4-2 System Parameters for VAX and ALPHA ........... 4-4 4-3 How to Register Your HSM License .............. 4-6 5-1 How to Install the HSM Software ............... 5-1 6-1 Archive Class Identifier/Label Reference for HSM Basic Mode................................. 6-10 6-2 Supplied Default Policy Definitions ........... 6-15 6-3 MDMS Commands for HSM Plus Mode ............... 6-19 D-1 HSM Files Installed ........................... D-1 E-1 MDMS Logical Names ............................ E-1 F-1 MDMS Files Installed .......................... F-1 viii _________________________________________________________________ Preface Purpose of This Document This document contains installation and configuration information about HSM for OpenVMS. Use this document to install, and configure your HSM environment. Intended Audience The audience for this document are persons who install HSM software. The users of this document should have some knowledge of the following: o OpenVMS system management o DCL commands and utilities Document Structure This document is organized in the following manner and includes the following information: Chapter 1 Provides and introduction to the HSM environment and how it compliments your storage environment. Chapter 2 Describes the MDMS Preinstallation Tasks. Chapter 3 Describes the MDMS installation and configuration tasks. Chapter 4 Describes the HSM software and hardware requirements. Chapter 5 Describes the HSM installation tasks. Chapter 6 Describes the HSM configuration tasks in preparation for use. ix Chapter 7 Describes configuring the HSM environment for remote access through DFS, NFS, or PATHWORKS. Appendix A Shows a sample HSM Basic mode installation. Appendix B Shows a sample HSM Plus mode installation. Appendix C Provides a list of the HSM Logicals used Appendix D Provides a list of the HSM File names. Appendix E Provides a list of the MDMS Logicals used Appendix F Provides a list of the MDMS File names. Related Documents The following documents are related to this documentation set or are mentioned in this manual. The lower case x in the part number indicates a variable revision letter. ___________________________________________________________ Document__________________________________Order_No.________ HSM for OpenVMS Installation and AA-QUJ1x-TE Configuration Guide HSM for OpenVMS Guide to Operations AA-PWQ3x-TE HSM for OpenVMS Command Reference Guide AA-R8EXx-TE HSM for OpenVMS Software Product AE-PWNTx-TE Description HSM Hard Copy Documentation Kit (Consist QA-0NXAA-GZ of the above HSM documents and a cover letter) Storage Library System for OpenVMS Guide AA-QHLEx-TE to Backup and Restore Operations Storage Library System for OpenVMS AA-KY16x-TE Installation Guide OpenVMS System Management Utilities AA-PV5Px-TK Reference Manual: A-L OpenVMS DCL Dictionary: A-M AA-PV5Kx-TK OpenVMS DCL Dictionary: N-Z AA-PV5Lx-TK OpenVMS License Management Utility AA-PVXUx-TK Manual x ___________________________________________________________ Document__________________________________Order_No.________ OpenVMS_User's_Manual_____________________AA-PV5Jx-TK______ Related Products The following related products are mentioned in this documentation. ___________________________________________________________ Product_______Description__________________________________ HSM HSM refers to Hierarchical Storage Management for OpenVMS software. MDMS MDMS refers to Media and Device Management Services for OpenVMS software. SLS SLS refers to Storage Library System for OpenVMS software. SSMgr SSMgr refers to POLYCENTER Save Set Manager ______________for_OpenVMS_software.________________________ Conventions The following conventions are used in this document. ___________________________________________________________ Convention__Description____________________________________ { } In format command descriptions, braces indicate required elements. You must include one of the elements. [ ] Brackets show optional elements in a command syntax. You can omit these elements if you wish to use the default response. Horizontal ellipsis points indicate the . omission of information from a sentence or . paragraph that is not important to the topic . being discussed. xi ___________________________________________________________ Convention__Description____________________________________ . . . 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. OpenVMS This term refers to the OpenVMS Alpha operating Alpha system. OpenVMS This term refers to the OpenVMS VAX operating VAX_________system.________________________________________ Determining and Reporting Problems If you encounter a problem while using HSM, report it to Digital[TM] through your usual support channels. xii Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated previously or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. xiii 1 _________________________________________________________________ Welcome to HSM The information presented in this chapter is intended to give you an "overall picture" of a typical storage environment, and to explain how HSM complements that environment. 1.1 What Do All Storage Environments Have In Common? All storage environments that plan to implement HSM 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 o Removable media that is compatible with the tape drives for storing shelved 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 (stacters/loaders/libraries) o Types of tape drive connections (direct-connect SCSI or controller-connected) Welcome to HSM 1-1 Welcome to HSM 1.2 What Makes a Storage Environment Unique? o Location of tape drives (remote or local) o Number of disks o Number of tape drives o Optical Devices 1.3 How Does HSM Complement Your Storage Environment? On most storage systems, 80% of the I/O requests access only 20% of the stored data. The remaining 80% of the data occupies expensive media (magnetic disks), but is used infrequently. HSM solves this problem by automatically and transparently moving data between magnetic disk and low- cost shelf-storage (tapes or optical disks) according to file usage patterns and policies that you specify. HSM is most suitable for large data-intensive storage operations where the backup times become excessive. By moving infrequently used data to off-line storage, HSM can greatly reduce the amount of backup time required. The benefits of using HSM are: o Limits on-line capacity to frequently used files, thus speeding access to current data. o Provides faster backups with less on-line data needing regular backup. o The backup-via-shelving capability reduces backup requirements up to 90%. o Storage administrators no longer need to manage disk capacity on a daily basis, since HSM monitors this for them. o Production applications won't fail due to "disk full" or "disk quota exceeded" exceptions because HSM prevents disks from filling up. o Allows you to customize your storage hierarchy according to your requirements. o The tape re-packing feature recovers shelf space on tapes used for deleted files or obsolete data. o The flexible management system lets you move files between disk volumes or systems without any unshelving. 1-2 Welcome to HSM Welcome to HSM 1.3 How Does HSM Complement Your Storage Environment? o The multi-file savesets feature provides full use of tape capacity and greatly increased shelving performance. o The multiple catalogs feature allows much larger HSM systems by not limiting the number of shelved files. 1.4 What Is The Purpose of a Managed Media and Device Environment? HSM software is dependent on the Media and Device Management Services (MDMS) software to access storage devices. 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. 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." HSM recognizes these media type definitions, and depending upon which media type your storage class uses, performs the shelving 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. HSM depends upon MDMS Welcome to HSM 1-3 Welcome to HSM 1.4 What Is The Purpose of a Managed Media and Device Environment? to select the appropriate tape drives determined by the media type. HSM 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). HSM enables you to set the retention criteria for data saved on volumes, while MDMS enables you to define when to move or recyle volumes. 1.5 What is the Difference Between HSM Basic Mode and Plus Mode? HSM software operates in one of two modes: o HSM Basic mode-Provides shelving, preshelving, and unshelving functionality using simple devices, Digital Linear Tape (DLT) magazine loaders, and 4mm DAT loaders. o HSM Plus mode-Provides shelving, preshelving, and unshelving functionality using the full suite of devices supported through Media and Device Management Services for OpenVMS (MDMS), including robotically-controlled devices like TL820s and StorageTek[TM] silos. Except for the media and device management configuration and support, both modes operate identically. ________________________ Note ________________________ If you don't already have SLS installed on your system, then you must install MDMS before you can use the HSM Plus Mode functionality. Don't install MDMS if SLS is already present. ______________________________________________________ 1-4 Welcome to HSM Welcome to HSM 1.5 What is the Difference Between HSM Basic Mode and Plus Mode? 1.5.1 HSM Basic Mode Functions HSM Basic mode provides the following functionality and features: o Complete HSM functionality for small to medium customer environments that can use smaller capacity tape loaders (for example, DLT loaders), standalone tape devices, and magneto-optical devices o A simple, integrated user interface provided completely by HSM o Limited media management that is not integrated with other storage management products o Support of up to 36 archive classes for data reliability o An HSM naming convention for tape volume labels o Local tape device support within the VMScluster[TM] environment: the shelf server nodes must have visibility to all tape devices (this can include TMSCP-served devices) 1.5.2 HSM Plus Mode Functions HSM Plus mode provides the following functionality and features: o Complete HSM functionality for medium to large customer environments that use large tape jukeboxes and for locations that already have the MDMS or SLS software installed o Support for large capacity nearline devices that support multiple terabytes of data, such as the TL820 and StorageTek[TM] silos o Common media management with other OpenVMS storage management products through the MDMS software o Device and media management support provided through the MDMS command line and menu interfaces; this requires a more complex configuration process than for HSM Basic mode o Support of up to 9999 archive classes for data reliability Welcome to HSM 1-5 Welcome to HSM 1.5 What is the Difference Between HSM Basic Mode and Plus Mode? o No fixed naming conventions for HSM tape volumes; the Storage Administrator controls volume names through MDMS o Tape device support within the cluster: the shelf server nodes do not require direct visibility to all tape devices within the cluster o Support for remote tape devices, those that are not directly connected within the cluster, through the Remote Device Facility[TM] (RDF) portion of MDMS 1.5.3 HSM Mode Comparison Table Table 1-1 identifies the functionality HSM for OpenVMS provides and which mode provides it. Table_1-1_HSM_Basic_and_Plus_Functionality_________________ Function___________________Basic_______Plus________________ OpenVMS Versions 6.1 thru 6.1 thru 7.1 7.1 Supported hardware VAX, Alpha VAX, Alpha platforms Common media and device No Yes, through MDMS management with other Digital storage products Support for Digital Yes Yes Linear Tape (DLT) magazine loaders as robotically-controlled devices Support for TL81x, TL82x No Yes Maximum number of archive 36 9999 classes Requires specific HSM Yes No volume names Provides support for No Yes remote devices (continued on next page) 1-6 Welcome to HSM Welcome to HSM 1.5 What is the Difference Between HSM Basic Mode and Plus Mode? Table_1-1_(Cont.)_HSM_Basic_and_Plus_Functionality_________ Function___________________Basic_______Plus________________ Uses a single, Yes No integrated interface for_configuration_and_use__________________________________ All other functions, including HSM policies and cache, are provided in both modes. 1.5.4 Choosing HSM Modes One of the pivotal decisions you must make before starting HSM is which mode you wish to run in. Select Plus mode if: o You wish to have consolidated media management with other Digital Storage Management products (e.g SLS, PAB) o You are planning to use large multi-drive tape jukeboxes such as the TL81x, TL82x or StorageTek Silo o You are planning to use any kind of remote (RDF- accessed) tape drive o You wish to choose your tape volume labels, or use bar- coded volume labels Select Basic mode if: o You do not want consolidated media management, or are using an alternative media manager o You are not using large multi-drive tape jukeboxes (for example, you can use single-drive TZ8xx loaders in either mode) o You are not planning to use tapes at all (for example, you might be using optical jukeboxes) You should select the mode before continuing with any further HSM configuration. Welcome to HSM 1-7 Welcome to HSM 1.5 What is the Difference Between HSM Basic Mode and Plus Mode? 1.5.5 HSM Mode Change Restrictions You choose an HSM mode to operate when you install the HSM for OpenVMS software. However, you can change modes after you make the initial decision. The following restrictions apply to changing modes after installation: o You can always change from Basic mode to Plus mode. o You can change from Plus mode to Basic mode only if you have not written any shelved file information to a catalog in Plus mode. Once you write information to a catalog in Plus mode, you cannot change back to Basic mode. o For a change in operating mode to have effect, you must restart HSM. 1.6 HSM License Types HSM offers three kinds of license types. These are: o HSM base licenses o HSM Capacity licenses o HSM Concurrent Use licenses 1.6.1 HSM Base Licenses A base HSM license is required to use HSM. This base license provides 20 GB of capacity. Additional capacity licenses are available as is an unlimited capacity license. The capacity is calculated according to the online storage space freed up when files are shelved. The total capacity is checked against the allowable capacity when a shelving operation occurs. If you exceed your capacity license, users will be able to unshelve data, but will not be able to shelve data until the license capacity is extended. When you shelve a file, the amount of space freed up by the file's truncation is subtracted from the total capacity available. When you unshelve or delete the file, the file's allocated space is added to the capacity available. Periodically, HSM scans the volumes in the VMScluster system and compares the amount of storage space for the shelved files to the remaining capacity. The SMU SHOW 1-8 Welcome to HSM Welcome to HSM 1.6 HSM License Types FACILITY command displays the license capacity remaining for the HSM facility (VMScluster system). Base licenses are available for all-VAX clusters, all- Alpha clusters, and mixed architecture clusters. These base licenses are shown in Table 1-2. Table_1-2_HSM_Base_Licenses________________________________ Base Licenses: VAX only Cluster QL-0NXA9-AA Alpha only Cluster QL-3J1A9-AA Mixed_Cluster______________QP-03PAA-01_____________________ 1.6.2 HSM Capacity Licenses HSM uses an online capacity licensing strategy. Because HSM increases online capacity for active data at low cost, the license strategy attempts to capitalize on this lower cost per megabyte. HSM reduces the cost of system management by providing this functionality with a reduced amount of operator intervention. You may increase your HSM storage capacity by purchasing additional capacity licenses. Digital makes it easy for you by combining a base license in the same capacity license package so only one part number is needed. These licenses expand your shelving capacity by 140 GB, 280 GB, 500 GB, or 1000 GB increments of storage. Table 1-3 lists these licenses. Table_1-3_HSM_Additional_Capacity_Licenses_________________ HSM Capacity Licenses: 140 GB Capacity License* QP-03TAA-01 280 GB Capacity License* QP-03TAA-02 500 GB Capacity License* QP-03TAA-04 1000_GB_Capacity_License*____________QP-03TAA-03___________ ________________________ Note ________________________ The * in the above table means that these additional capacity licenses also include the base license for Welcome to HSM 1-9 Welcome to HSM 1.6 HSM License Types VAX clusters, Alpha clusters, and mixed-architecture clusters. ______________________________________________________ 1.7 HSM Concurrent Use Licenses In addition to the HSM Capacity licenses, Digital also has available some HSM Concurrent Use Licenses. These concurrent use licenses are different from the above capacity licenses in that they don't include a base license in the same package. Obtaining a concurrent use license and a base license requires two part numbers. Table 1-4 lists these licenses. Table_1-4_HSM_Concurrent_Use_Licenses______________________ Concurrent Use Licenses: 20 GB Concurrent Use License QL-2AWAA-3B 500 GB Concurrent Use License QL-2AWAA-3G Unlimited_Concurrent_Use_License_____QL-2AWAA-3H___________ 1.8 Installation Changes when SLS is Present When the Storage Library System (SLS) product is already present on the system where you are installing HSM, you must NOT install MDMS. The HSM Product will use the MDMS software already running under SLS. If you reinstall MDMS again, it will overide the MDMS software running under SLS and cause SLS to lose some functionality. See the Caution note that follows. _______________________ Caution _______________________ If you currently use the Storage Library System for OpenVMS (SLS), do not install MDMS. MDMS does not contain the backup and restore functionality of SLS. If you install MDMS over SLS backup and restore functionality, you must reinstall your version of SLS. SLS includes the MDMS functionality. ______________________________________________________ 1-10 Welcome to HSM Welcome to HSM 1.9 HSM Upgrade Considerations 1.9 HSM Upgrade Considerations If you are installing HSM Version 2.2 over an existing HSM product, there are several additional tasks you must perform. 1. All HSM V2.x versions contain an HSDRIVER with a different interface than the HSM V1.x versions. HSM V2.x version will not work with the V1.x version of HSDRIVER installed. So, if you are upgrading from an HSM V1.x version to an HSM V2.x version, you must reboot your system after the HSM installation or the system will crash. If you are operating in a VMScluster, all nodes in the cluster using HSM must be rebooted to use the new HSDRIVER. 2. If you are upgrading from a lower HSM V2.x version to HSM V2.2, you do not have to reboot your system right after HSM installation. You may operate HSM V2.2 with an older V2.x HSDRIVER. However, you should plan to reboot your system in the near future to take advantage of the full HSDRIVER functionality. 3. The format of the HSM catalog and the SMU databases found in HSM$MANAGER have changed for HSM Version 2.2 from V1.x. As a result, the installation procedure may convert the existing catalog and multifile save sets to the new format and you cannot downgrade to earlier versions. In case something should happen during conversion, Digital strongly recommends you back up the existing catalog and SMU databases before you install HSM Version 2.2 software. The catalog is located at: HSM$CATALOG:HSM$CATALOG.SYS and the SMU databases at: HSM$MANAGER:*.SMU. 4. You must shut down HSM before you perform the installation. If you do not, the installation will fail. To shut down HSM, use the following command: $ SMU SHUTDOWN/NOW Welcome to HSM 1-11 Welcome to HSM 1.10 Backing HSM Up the Catalog 1.10 Backing HSM Up the Catalog Because the HSM catalog is such a critical file for HSM, it is very important that it gets backed up on a regular basis. The contents of shelved files are retrievable only through the catalog. You should therefore plan for the catalog to be in a location where it will get backed up frequently. 1.11 Backing up Your System Disk At the beginning of the installation, VMSINSTAL prompts you about the backup of your system disk. Digital recommends that you back up your system disk before installing any software. Use the backup procedures that are established at your site. For details about performing a system disk backup, see the section on the Backup utility (BACKUP) in the OpenVMS System Management Utilities Reference Manual: A-L. 1.12 VMScluster System Considerations If you installed HSM on a VMScluster system, there are four things you may need to do: o Reinstall DCLTABLES on all nodes in the VMScluster system. o Make sure that SYS$STARTUP:HSM$LOGICALS.COM is the same across all nodes in the VMScluster system and that all nodes can access any devices referenced in the logicals. o Because HSM creates new DCL command verbs, all system users need to log out and log in again to see those verbs. o To ensure all logicals are correctly defined and that HSM functionality is fully available on all devices in the VMScluster system, you may want to reboot all nodes in the VMScluster system. 1-12 Welcome to HSM Welcome to HSM 1.13 Mixed Architecture Environments 1.13 Mixed Architecture Environments _ Before You Install your Storage Management Software _ If you are planning to install HSM Plus 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.13.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.13.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.13.3 describes three possible approaches to implementing a mixed architecture environment. o Section 1.13.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.13.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 HSM 1-13 Welcome to HSM 1.13 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.13.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-14 Welcome to HSM Welcome to HSM 1.13 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.13.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.13.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 HSM 1-15 Welcome to HSM 1.13 Mixed Architecture Environments 1.13.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.13.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-16 Welcome to HSM Welcome to HSM 1.13 Mixed Architecture Environments 1.13.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. 1.14 Overview of the HSM Installation Process The following table provides an overview of the steps involved in the full HSM installation and configuration process. Welcome to HSM 1-17 Welcome to HSM 1.14 Overview of the HSM Installation Process Table_1-5_HSM_Installation_and_Congifuration_______________ StepsTasks_________________________Reference______Check-off 1 Preinstall Hardware on Chapter 2 _____ System 2 Install MDMS Section 3.1.2 _____ 3 Verify the MDMS Installation Section 3.2.1 _____ 4 Modify the Automatic Startup Section 3.2.2 _____ and Shutdown 5 Define Global Symbols Section 3.2.3 _____ 6 Define OpenVMS Cluster Alias Section 3.2.4 _____ 7 Define Failover Server Nodes Section 3.2.4 _____ 8 Define Networked Object Section 3.2.5 _____ 9 Configure Hardware for MDMS Section 3.2.6 _____ 10 Test MDMS Hardware Section 3.2.6.2_____ installation 11 Check that you meet the HSM Section 4.3 _____ software requirements 12 Decide on HSM Basic or Plus Section 4.4, _____ Mode Section 4.5 13 Decide on whether you will Section 4.6 _____ use HSM Repack 14 Check that you meet the Section 4.7 _____ hardware requirements 15 Check that you have the Section 4.8 _____ right system privileges 16 Check that you meet the Section 4.9 _____ system parameters 17 Check that you meet the Section 4.10 _____ VMSINSTAL requirements 18 Check if you need to install Section 4.11 _____ DECthread Images 19 Register your HSM License Section 4.12 _____ 20 Install HSM Section 5.1.1 _____ (continued on next page) 1-18 Welcome to HSM Welcome to HSM 1.14 Overview of the HSM Installation Process Table_1-5_(Cont.)_HSM_Installation_and_Congifuration_______ StepsTasks_________________________Reference______Check-off 21 Edit HSM startup and Section 5.2.1 _____ shutdown 22 Create an HSM Catalog Section 5.2.2 _____ 23 Back up the catalog Section 1.10 _____ 24 Verify the HSM Installation Section 5.3 _____ 25 Read the HSM Getting Started Chapter 6 _____ _____Chapter_______________________________________________ Welcome to HSM 1-19 2 _________________________________________________________________ MDMS Preinstallation Requirements This chapter describes how to configure your hardware so your system will recognize it, prior to having MDMS recongize it. 2.1 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 HSM 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.1.1. o For a media loader, refer to Section 2.1.2. o For an operator attended drvie, refer to Section 2.1.3. 2.1.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 Section 3.2.6. MDMS Preinstallation Requirements 2-1 MDMS Preinstallation Requirements 2.1 Configuring Your Hardware 2.1.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.1.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: 2-2 MDMS Preinstallation Requirements MDMS Preinstallation Requirements 2.1 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 [DRIVE drv_num] [ROBOT robot_name] $ ROBOT LOAD SLOT slot_num [DRIVE drv_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 [DRIVE drv_number] 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.1.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 Section 3.2.7. 2.1.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. MDMS Preinstallation Requirements 2-3 MDMS Preinstallation Requirements 2.1 Configuring Your Hardware 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.1.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 6.6.1. ______________________________________________________ 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: 2-4 MDMS Preinstallation Requirements MDMS Preinstallation Requirements 2.1 Configuring Your Hardware $ ROBOT SHOW SLOT 0-n [DRIVE drv_num] [ROBOT robot_name] $ ROBOT LOAD SLOT slot_num [DRIVE drv_num] [ROBOT robot_name] 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 [DRIVE drv_number] 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.1.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 Section 3.2.8. 2.1.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. MDMS Preinstallation Requirements 2-5 MDMS Preinstallation Requirements 2.1 Configuring Your Hardware 2.1.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-6 MDMS Preinstallation Requirements 3 _________________________________________________________________ MDMS Software Installation and Configuration This chapter describes how to install the MDMS software. 3.1 Installing the Media and Device Management Software Before installing the HSM 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 HSM, 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 HSM 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. ______________________________________________________ Table 3-1 shows the stages of installing and configuring the MDMS software before you begin the HSM Version 2.2 installation procedure. MDMS Software Installation and Configuration 3-1 MDMS Software Installation and Configuration 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 HSM 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.______________________________________________ 3-2 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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. 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. ______________________________________________________ MDMS Software Installation and Configuration 3-3 MDMS Software Installation and Configuration 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) 3-4 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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) MDMS Software Installation and Configuration 3-5 MDMS Software Installation and Configuration 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) 3-6 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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 4-1 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) MDMS Software Installation and Configuration 3-7 MDMS Software Installation and Configuration 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. 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._____________________________________ 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. 3-8 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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.13.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 MDMS Software Installation and Configuration 3-9 MDMS Software Installation and Configuration 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. 3-10 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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 HSM Version 2.2. These tasks apply whether you have installed the MDMS server or client software. MDMS Software Installation and Configuration 3-11 MDMS Software Installation and Configuration 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: 3-12 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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) MDMS Software Installation and Configuration 3-13 MDMS Software Installation and Configuration 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) 3-14 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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__________________________________________ MDMS Software Installation and Configuration 3-15 MDMS Software Installation and Configuration 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 3-16 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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. MDMS Software Installation and Configuration 3-17 MDMS Software Installation and Configuration 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 3-18 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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: MDMS Software Installation and Configuration 3-19 MDMS Software Installation and Configuration 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 3-20 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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 MDMS Software Installation and Configuration 3-21 MDMS Software Installation and Configuration 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. 3-22 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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 MDMS Software Installation and Configuration 3-23 MDMS Software Installation and Configuration 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. 3-24 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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 MDMS Software Installation and Configuration 3-25 MDMS Software Installation and Configuration 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. 3-26 MDMS Software Installation and Configuration MDMS Software Installation and Configuration 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. MDMS Software Installation and Configuration 3-27 4 _________________________________________________________________ Meeting the HSM Installation Requirements This chapter presents all the requirements to meet before installing the HSM software. 4.1 Requirements List The requirements list to meet before installing HSM software is as follows: o Read the HSM Software Release Notes o Required Software o Requirements for HSM Basic Mode o Requirements for HSM Plus Mode o Requirements for HSM Repack Function o Required Hardware Disk Sapce o Required System Privileges o Required System Parameters o Required for VMSINSTAL o Installing DECthread Images o Registering your HSM Licence 4.2 Read the Release Notes The HSM kit includes online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. The release notes are in a text file named SYS$HELP:HSM022.RELEASE_NOTES and a Postscript[R] file named SYS$HELP:HSM022_RELEASE_NOTES.PS. Meeting the HSM Installation Requirements 4-1 Meeting the HSM Installation Requirements 4.3 Required Software 4.3 Required Software The software requirements list for HSM is as follows: o HSM Version 2.2 is supported on the Alpha and VAX OpenVMS Operating System V6.1 through V7.1. o HSM Basic Mode does not require any software other than HSM and the OpenVMS Operating System. o HSM Plus Mode requires MDMS V2.5B or newer software, or SLS V2.5B or newer software. However, you should use the latest version of MDMS or SLS (V2.9) to take advanatge of the latest enhancements and device support. An MDMS license is not required for HSM use. An SLS license is required only if SLS is to be used independently of HSM. 4.4 Required for HSM Basic Mode When HSM is used in Basic Mode, the only software required, in addition to HSM, is the OpenVMS Operating System Versions 6.1 through 7.1. Media and Device Management Services (MDMS) is required only if you wish to convert from HSM Basic Mode to HSM Plus Mode. 4.5 Required for HSM Plus Mode HSM Plus mode requires the use of Media and Device Management Services for OpenVMS (MDMS) Version 2.5B or newer software for managing media and devices. MDMS software comes packaged with HSM and can be obtained from one of the following sources: o Off the HSM distribution kit o Included with Storage Management Library System for OpenVMS (SLS). o Included as a separate source with Archive/Backup System for OpenVMS (ABS) or Sequential Media Filesystem for OpenVMS (SMF) software ________________________ Note ________________________ MDMS software must be installed before you install HSM in Plus mode, unless SLS is already present on 4-2 Meeting the HSM Installation Requirements Meeting the HSM Installation Requirements 4.5 Required for HSM Plus Mode the system. If SLS is present, do not install MDMS since HSM will use the SLS version of MDMS. MDMS is not required for operating in HSM Basic mode. ______________________________________________________ 4.6 Required for HSM Repack Function The HSM SMU REPACK Command allows you to do an analyis of valid and obsolete data on shelf media and copy the valid data to other media, thus freeing up storage space. This Repack functionality is found in HSM Plus Mode. The HSM Repack function requires the use of two tape drives since this is a direct tape to tape transfer process. One tape must match the media type of the source archive class and the other tape must match the media type of the destination archive class. 4.7 Required Hardware Disk Space Table 4-1 summarizes the disk space requirements for installing and running HSM. Table_4-1_Disk_Space_Requirements__________________________ Item________Blocks_Needed____Description___________________ Install 28,000 Temporary blocks for Kit installation. HSM 16,000 Permanent blocks for software. Software Catalog 100,000 Catalog grows at the average rate of 1.25 blocks for each file copy shelved. Digital recommends 100,000 blocks be set aside initially for this _____________________________catalog.______________________ HSM requires 16,000 free disk blocks on the system disk. To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: Meeting the HSM Installation Requirements 4-3 Meeting the HSM Installation Requirements 4.7 Required Hardware Disk Space $ SHOW DEVICE SYS$SYSDEVICE 4.8 Required System Privileges To install HSM software, you must be logged into an account that has the SETPRV privilege. Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation. 4.9 Required System Parameters The installation for HSM may require that you raise the values of the GBLSECTIONS and GBLPAGES system parameters if they do not meet the minimum criteria shown in Table 4-2. Table_4-2_System_Parameters_for_VAX_and_ALPHA______________ System_Parameters__________VAX_________ALPHA_______________ Additional GBLPAGES 1783 2926 Additional_GBLSECTIONS_____6___________36__________________ To find your current system parameters, use the following command: $ MCR SYSGEN SYSGEN> SHOW GBLPAGES SYSGEN> SHOW GBLSECTIONS 4.10 Required for VMSINSTAL When you invoke VMSINSTAL, it checks for the following: o Whether you are logged into a privileged account o Whether you have adequate quotas for installation o Whether DECnet[TM] software is running o Whether any users are logged into the system Note that VMSINSTAL requires that the installation account have a minimum of the following quotas: ASTLM = 40 (AST Quota) BIOLM = 40 (Buffered I/O limit) BYTLM = 32,768 (Buffered I/O byte count quota) 4-4 Meeting the HSM Installation Requirements Meeting the HSM Installation Requirements 4.10 Required for VMSINSTAL DIOLM = 40 (Direct I/O limit) ENQLM = 200 (Enqueue quota) FILLM = 300 (Open file quota) Type the following command to find out where your quotas are set. $ show process/quota If VMSINSTAL detects any problems during the installation, it notifies you and prompts you to continue or stop the installation. In some instances, you can enter YES to continue. Enter NO to stop the installation and correct the problem. User account quotas are stored in the SYSUAF.DAT file. Use the OpenVMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM, and then run AUTHORIZE, as shown in the following example: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the system displays messages indicating whether changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. Meeting the HSM Installation Requirements 4-5 Meeting the HSM Installation Requirements 4.11 Installing DECthreads Images 4.11 Installing DECthreads Images If DECthreads[TM] images are not installed, you must install them before you install HSM. DECthreads consists of several images. To check for them, you will need to execute the following commands. These commands require CMKRNL privileges and will need to be executed on all nodes in the cluster running HSM. $ install list sys$library:cma$rtl.exe $ install list sys$library:cma$lib_shr.exe $ install list sys$library:cma$open_lib_shr.exe $ install list sys$library:cma$open_rtl.exe If any of these list commands fails, then the DECthread images need to be installed. To install them, execute the following commands. $ install add sys$library:cma$rtl.exe/open/head/share $ install add sys$library:cma$lib_shr.exe/open/head/share $ install add sys$library:cma$open_lib_shr.exe.open/head/share S install add sys$library:cma$open_rtl.exe/open/head/share 4.12 Registering Your HSM License To register your HSM license or to add additional capacity licenses, follow the steps in Table 4-3. Before you attempt to register your PAK, be sure to have the PAK information in front of you. Table_4-3_How_to_Register_Your_HSM_License_________________ Step___Action______________________________________________ 1 Enter the LICENSE REGISTER command with the product name and a dash. $ LICENSE REGISTER HSM-SERVER - Important: Enter a dash at the end of each command in steps 1 through 8. ___________________________________________________________ (continued on next page) 4-6 Meeting the HSM Installation Requirements Meeting the HSM Installation Requirements 4.12 Registering Your HSM License Table_4-3_(Cont.)_How_to_Register_Your_HSM_License_________ 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 entry of the PAK. _$ /AUTHORIZATION=xxxxxxx - ___________________________________________________________ 4 Enter the /PRODUCER qualifier information, assigning the value DEC in quotes. _$ /PRODUCER="DEC" - ___________________________________________________________ 5 Enter the /UNITS qualifier information, assigning the value from the UNITS entry of the PAK. This is the value that determines your HSM online capacity. _$ /UNITS=nn - ___________________________________________________________ 6 Enter the /DATE qualifiers information, assigning the product's release date value from the PRODUCT RELEASE DATE entry of the PAK. _$ /DATE=dd-mmm-yyyy - ___________________________________________________________ 7 Enter the /AVAILABILITY qualifier information, assigning the value from the AVAILABILITY TABLE CODE entry of the PAK. _$ /AVAILABILITY=x - ___________________________________________________________ 8 Enter the /OPTIONS qualifier information, assigning the value from the KEY OPTIONS entry of the PAK. _$ /OPTIONS=xxxxxx - (continued on next page) Meeting the HSM Installation Requirements 4-7 Meeting the HSM Installation Requirements 4.12 Registering Your HSM License Table_4-3_(Cont.)_How_to_Register_Your_HSM_License_________ Step___Action______________________________________________ ___________________________________________________________ 9 Enter the /CHECKSUM qualifier information, assigning the value from the CH entry of the PAK. Important: Do NOT end the entry with a dash. _$ /CHECKSUM=n-xxxx-xxxx-xxxx-xxxx ___________________________________________________________ 10 Invoke the LICENSE LOAD command with the product name. _______$_LICENSE_LOAD_HSM-SERVER___________________________ 4-8 Meeting the HSM Installation Requirements 5 _________________________________________________________________ Installing HSM Software This chapter contains instructions for installing HSM Version 2.2 software on the OpenVMS operating system. 5.1 Installing the HSM Software This section contains a step-by-step description of the installation procedure. Installing HSM will take approximately 10 to 20 minutes, depending on your system configuration and media. Running the Installation Verification Procedure (IVP) on a standalone system takes about 5 minutes. 5.1.1 The Installation Procedure The HSM installation procedure consists of a series of questions and informational messages. Table 5-1 shows the installation procedure. For a complete example of an HSM installation and verification procedure for HSM Basic mode, see Appendix A; for HSM Plus mode, see Appendix B. To abort the installation procedure at any time, enter Ctrl/Y. When you enter Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. Table_5-1_How_to_Install_the_HSM_Software__________________ Step_Action________________________________________________ 1 Load and mount the media that contains the software kit. ___________________________________________________________ (continued on next page) Installing HSM Software 5-1 Installing HSM Software 5.1 Installing the HSM Software Table_5-1_(Cont.)_How_to_Install_the_HSM_Software__________ Step_Action________________________________________________ 2 Invoke the VMSINSTAL procedure. Use the following command: $@SYS$UPDATE:VMSINSTAL HSM022 location: OPTIONS N Where: location is the tape device (or directory) that contains the software kit save set. OPTIONS N is an optional parameter that tells VMSINSTAL to ask you to choose Release Notes options. 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 Identify the location for the software to be mounted. * Where will the distribution volumes be mounted: You may specify a tape drive, a local disk, or a remote disk. Enter the appropriate information and press . ___________________________________________________________ (continued on next page) 5-2 Installing HSM Software Installing HSM Software 5.1 Installing the HSM Software Table_5-1_(Cont.)_How_to_Install_the_HSM_Software__________ Step_Action________________________________________________ 6 If you entered OPTIONS N on the VMSINSTAL command line, respond to the 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]: Enter the number of the desired option and press . ___________________________________________________________ 7 Answer if you want to purge old files. * Do you want to purge files replaced by this installation [YES]? Enter Y and press . ___________________________________________________________ 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 . ___________________________________________________________ (continued on next page) Installing HSM Software 5-3 Installing HSM Software 5.1 Installing the HSM Software Table_5-1_(Cont.)_How_to_Install_the_HSM_Software__________ Step_Action________________________________________________ 9 Confirm the PAK registration. *** HSM License *** Correct installation and operation of this software requires that one of the following Product Authorization Keys (PAKs) reflecting your software license be present on this system: HSM-SERVER HSM-USER * Does this product have an authorization key registered and loaded [Y]? Enter Y and press . ___________________________________________________________ 10 Determine whether to install HSM Basic or HSM Plus mode. *** HSM Mode *** With this version, HSM can operate in one of two possible modes: BASIC - The standalone HSM product which supports a limited number of nearline and offline devices. PLUS - The integrated HSM product, integrated with Media and Device Management Services (MDMS) which supports an expanded number of nearline and offline devices. NOTE: MDMS or SLS V2.5B or newer must be installed before installing HSM PLUS mode. Also, once files are shelved in PLUS mode, you may *not* change back to BASIC mode. Enter BASIC or PLUS to select the mode in which you want HSM to operate. * Enter the mode to install [PLUS]: (continued on next page) 5-4 Installing HSM Software Installing HSM Software 5.1 Installing the HSM Software Table_5-1_(Cont.)_How_to_Install_the_HSM_Software__________ Step_Action________________________________________________ The default shown varies according to whether the HSM install detects the presence of MDMS or SLS Version 2.5B or newer software on your system. If it does, the default is Plus mode; if it does not, the default is Basic mode. If you tell HSM to install HSM Plus mode, but MDMS or SLS software is not installed on your system, the installation fails. ___________________________________________________________ 11 Identify the HSM manager account UIC. If you see the following message: *** HSM Account *** A privileged account named HSM$SERVER will be created for use by HSM processes. This account will not allow interactive logins and the password will be automatically generated. The installation procedure will not proceed until you enter a valid user identification code (UIC) for the HSM$SERVER account. The UIC must be unique and within the SYSTEM group. * Enter the UIC to be used for HSM$SERVER account [[1,22]]: Press . ___________________________________________________________ (continued on next page) Installing HSM Software 5-5 Installing HSM Software 5.1 Installing the HSM Software Table_5-1_(Cont.)_How_to_Install_the_HSM_Software__________ Step_Action________________________________________________ 12 Select a location for the HSM configuration databases and log files. Restriction: The location must have at least 100,000 (100K) free blocks and be available to all nodes in the VMScluster system that will use HSM. *** HSM Device *** You will now be asked to enter a disk device specification to be used as a repository for HSM configuration databases and log files. NOTE: *** This device must have at least 100000 free blocks and be available to all nodes in the cluster that will be running HSM *** * Enter the disk device to use for HSM files [SYS$SYSDEVICE:]: The default location for HSM files is SYS$SYSDEVICE:[HSM$SERVER]. VMSINSTAL prompts you to verify the file location before continuing. ___________________________________________________________ 13 Set quotas and flags for the HSM account. VMSINSTAL will automatically set quotas and flags for the account. ___________________________________________________________ 14 Create HSM catalog and databases. HSM requires a catalog and databases to run. The VMSINSTAL can create them upon completion of the software installation for you. Recommendation: Digital recommends you answer Y to the following question: * Do you want to run the database creation procedure [YES]? ___________________________________________________________ (continued on next page) 5-6 Installing HSM Software Installing HSM Software 5.1 Installing the HSM Software Table_5-1_(Cont.)_How_to_Install_the_HSM_Software__________ Step_Action________________________________________________ 15 Set system disk files as not shelvable. VMSINSTAL can submit a command file to set all system disk files as non-shelvable. This protects the integrity of the system disk. Recommendation: Digital recommends you answer Y to the following question: * Do you want to submit SETFILENOSHELV.COM [YES]? ___________________________________________________________ 16 At this point, the installation proceeds without further operator intervention. If you requested VMSINSTAL run the IVP, it runs it _____here._________________________________________________ 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. 5.1.2 Error Recovery If errors occur during the installation procedure, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of HSM has failed. If the IVP fails, you see this message: The HSM Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for HSM has failed. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. Installing HSM Software 5-7 Installing HSM Software 5.1 Installing the HSM Software 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. 5.2 After Installing HSM Software The following postinstallation tasks should be performed after installing HSM software: o Edit the system startup and shutdown files. o Modify system parameter settings. o Create an HSM catalog, if you did not have the installation do so. o Install special device drivers. 5.2.1 Editing the System Startup and Shutdown Files You must edit the system startup and shutdown files to provide for automatic startup and shutdown. Add the command line that starts HSM to the system startup file, called SYS$MANAGER:SYSTARTUP_VMS.COM. HSM cannot start until after the network has started. You must place this new command line after the line that executes the network startup command procedure. The following example shows the network startup command line followed by the HSM startup command line: $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:HSM$STARTUP.COM 5-8 Installing HSM Software Installing HSM Software 5.2 After Installing HSM Software The HSM$STARTUP.COM procedure defines logicals required by the HSM software, connects the HSDRIVER software for VAX or Alpha systems, and issues an SMU STARTUP command to start the shelf handler process. The shelf handler process runs continuously and exits only with the SMU SHUTDOWN command. You may restart the shelf handler manually by using the SMU STARTUP command. You also can connect the HSDRIVER software manually. To do this, use one of the following commands: o For a VAX system: $ MCR SYSGEN CONNECT HSA0:/NOADAPTER o For an Alpha system: $ MCR SYSMAN IO CONNECT HSA0: /NOADAPTER Add the following command line to the system shutdown file, called SYS$MANAGER:SYSHUTDWN.COM: $ SMU SHUTDOWN/NOW 5.2.2 Creating an HSM Catalog The HSM catalog is the one and only authority containing information about shelved files. It grows as files get shelved. If you did not have the installation create an HSM catalog for you, you must create it manually before you start HSM. To manually create the catalog, invoke SYS$STARTUP:HSM$CREATE_CATALOG.COM. This creates a single catalog for HSM to access. When a catalog is created in this manner, it will be configured in Basic mode by default. SMU SET FACILITY /MODE=PLUS should be executed after the catalog is created if Plus mode is desired. Creating a new Basic mode catalog in an environment that was previously defined in Plus mode can cause unpredictable results. The HSM$STARTUP.COM file placed in SYS$STARTUP at installation time creates several systemwide logicals used by HSM. These logicals are stored in a file called HSM$LOGICALS.COM and includes the logical HSM$CATALOG. This logical points to the directory where HSM should look for the shelving catalog. If you wish to change the location of Installing HSM Software 5-9 Installing HSM Software 5.2 After Installing HSM Software the catalog, the line in SYS$STARTUP:HSM$LOGICALS.COM that defines this logical should be changed. ________________________ Note ________________________ HSM does not automatically create a new catalog if it cannot find the catalog in the location pointed to by HSM$CATALOG; this condition aborts HSM startup with an error message. ______________________________________________________ The system logical HSM$CATALOG should be created ahead of time to specify the location for the catalog. If you have not already created the logical, you are prompted to define it now and to restart the procedure. You still must modify the line in HSM$LOGICALS.COM to reflect that location if it is other than the default. The new catalog file is empty when created. 5.3 Installation Verification Procedure As mentioned in the installation procedure itself, VMSINSTAL can run an IVP upon completion of the HSM installation. The IVP attempts to verify that HSM can shelve and unshelve files using default configuration information. For a complete example of the HSM IVP, see Appendix A for HSM Basic mode or Appendix B for HSM Plus mode. ________________________ Note: ________________________ You can run the IVP by itself. If you do, it shuts down HSM. Use SYS$STARTUP:HSM$STARTUP.COM to restart HSM after the IVP finishes. ______________________________________________________ 5-10 Installing HSM Software 6 _________________________________________________________________ Getting Started with HSM HSM comes with a set of default configuration definitions that enable you to get HSM up and running quickly. This chapter explains how to use those definitions and perform other essential configuration tasks to start using HSM. Once HSM is up and running, you can modify the configuration for optimal performance in your operational environment. Read the Customizing the HSM Environment Chapter in the HSM Guide to Operations Manual for more information on tuning. This chapter includes the following topics: o A description of the default configuration installed with HSM o A discussion of how to make minimal adjustments to the default configuration for HSM to function in your operational environment o A description of how to set up the near-line and off- line environments for both Basic and Plus modes o Example off-line configurations for both Basic and Plus modes 6.1 HSM's Default Configuration After installation, HSM is configured with all the default definitions designed into the software. This section explains in detail what the default configuration definitions are and how you need to modify them to get HSM up and running. If you follow the steps in this section, you should be able to shelve and unshelve data on your system. For more information on optimizing HSM functions for your environment, read the Customizing the HSM Environment Chapter in the HSM Guide to Operations Manual. Getting Started with HSM 6-1 Getting Started with HSM 6.1 HSM's Default Configuration When you install HSM, it sets up several default elements you can use to run HSM with few modifications. These default elements include the following: o A default facility definition o A default shelf definition o A default device definition o A default volume definition o Default policy definitions 6.1.1 The Default Facility The facility is initially set up with the following attributes: o All HSM operations are enabled o All event logging is enabled o All nodes are authorized as shelf servers o Use of a catalog server is disabled o Default mode depends on whether MDMS/SLS is installed on your system These operations and event logging defaults represent the behavior that is recommended and expected to be used most of the time that HSM is in operation. You should customize your shelf servers to be restricted to the larger systems in your cluster and to those that have access to the desired near-line and off-line devices. 6.1.2 The Default Shelf HSM provides a default shelf that supports all online disk volumes. The default shelf enables HSM operations. Note that no archive classes are set up for the default shelf at initialization. To enable HSM operations to near-line and off-line devices, you need to configure the default shelf to one or more archive classes. 6-2 Getting Started with HSM Getting Started with HSM 6.1 HSM's Default Configuration 6.1.3 The Default Device HSM provides a default device record, which applies when you create a device without specifying attributes for the device. The default attributes are: o The device is shared with other applications. o Shelving and unshelving operations are enabled. o No archive classes are associated with the device. For the device to be used by HSM, you must at minimum associate one or more archive classes with the device. You may also choose to dedicate any device for exclusive HSM use. 6.1.4 The Default Volume HSM provides a default volume record, which applies to all online disk volumes in the system unless a specific volume entity exists for them. The default volume contains the following attributes: o Explicit HSM operations (preshelving, shelving, unshelving, file faults, unpreshelving) are enabled. o Implicit HSM operations (policy-based operations) are disabled. o Contiguous files are ineligible for shelving o Placed files are eligible for shelving o The high water mark is 90 percent. If these attributes are acceptable, no further configuration of volume records is needed. You may change the volume attributes in one of two ways: o Update the default volume record, which will affect all online disk volumes associated with the default volume. o Create an individual volume entity for each online disk volume you want to change. This is recommended if you turn on policy-based HSM operations. Getting Started with HSM 6-3 Getting Started with HSM 6.1 HSM's Default Configuration Digital recommends you examine disk usage before enabling implicit shelving operations on your cluster. For example, enabling a high water mark criterion on the default volume could cause immediate mass shelving on all volumes if the disk usage is already above the high water mark. Digital also recommends that you create an individual volume record for each system disk and disable all HSM operations on those volumes. 6.1.5 The Default Policies HSM provides three default policies as follows: o HSM$DEFAULT_POLICY-This is used as a template for all policy definitions, including the other two default policies. o HSM$DEFAULT_OCCUPANCY-This policy is used as the default reactive policy definition in the system for device full and high water mark triggers. o HSM$DEFAULT_QUOTA-This policy is used as the default reactive policy definition in the system for exceeded quota triggers. At installation time, all three default policies contain the same attributes: o The policy is enabled for shelving (rather than preshelving). o The comparison date used for file selection is the expiration date, which when used in conjunction with OpenVMS volume retention time, provides an effective date of last read or write access. o The elapsed time is set to 180 days; This means that files that have been accessed within 180 days will not be selected for shelving. o The low water mark goal for the policy is 80 percent. o The primary policy file selection algorithm is space time working set (STWS). o The secondary policy file selection algorithm is least recently used (LRU). 6-4 Getting Started with HSM Getting Started with HSM 6.1 HSM's Default Configuration These default policy definitions allow HSM to function effectively with the minimum of advance configuration and can be used without any modifications or additional information. By default, all volumes use the appropriate default policies without any further configuration being required. 6.2 Running HSM with the Default Configuration Although HSM provides the default elements described above, you cannot simply try to run HSM with these items. You must verify the facility definition and configure the following additional items for HSM to function: o Define archive classes for use. o Select archive classes for the default shelf. o Define devices to support each archive class. o Initialize the tape volumes for each archive class. o Set volume retention times on all online disks on which you want policy-based shelving to occur. 6.2.1 Verifying the Facility Definition As mentioned earlier, HSM provides a default facility definition. Before you start using HSM, however, you want to verify that the default facility definition is correct for your environment. The following example shows how to view information about the facility: Getting Started with HSM 6-5 Getting Started with HSM 6.2 Running HSM with the Default Configuration $ SMU SHOW FACILITY HSM is enabled for Shelving and Unshelving Facility history: Created: 22-APR-1996 12:10:37.13 Revised: 22-APR-1996 12:10:37.13 Designated servers: NODE1 NODE2 Current server: NODE1 Catalog server: Disabled Event logging: Audit Error Exception HSM mode: Plus Remaining license: 20 gigabytes The information displayed indicates: o Whether the facility is enabled for shelving, unshelving, or both o Which nodes on the cluster are designated as shelf servers o The current shelf server node o An indication of whether all catalog writes and caching operations are performed by the shelf server node o What log options are turned on o The HSM operational mode (Basic or Plus) o The remaining license space (in gigabytes) for the HSM facility If any of these attributes are not correct for your facility, you need to modify them before continuing to configure HSM. 6.2.2 Defining Archive Classes for Use To define an archive class for HSM to use, use one of the following commands depending on the mode in use. For HSM Basic Mode use: $ SMU SET ARCHIVE n ! for Basic Mode 6-6 Getting Started with HSM Getting Started with HSM 6.2 Running HSM with the Default Configuration For HSM Plus Mode use: $ SMU SET ARCHIVE n - _$ /MEDIA_TYPE=string - _$ /DENSITY=string - _$ /ADD_POOL=string Where n is a list of archive class numbers from 1 to 36 (Basic mode), or 1 to 9999 (Plus mode). In Plus mode, the DENSITY and ADD_POOL qualifiers are optional. The MEDIA_TYPE and DENSITY must exactly match the definitions in TAPESTART.COM (see Section 6.4). 6.2.3 Selecting Archive Classes for the Default Shelf During installation, HSM creates a default shelf named HSM$DEFAULT_SHELF. To allow shelving operations, the shelf must be associated with one or more archive classes. When data is copied to the shelf, it is copied to each of the archive classes specified. Having several archive classes provides you additional safety for your shelved files. Each archive class is written to its own set of media. Digital recommends having at least two archive classes. Archive classes are represented in HSM by both an archive name and an archive identifier. The properties of archive classes depends on the selected HSM operational mode: o Basic Mode - Basic mode supports up to 36 archive classes named HSM$ARCHIVE01 to HSM$ARCHIVE36, with associated archive identifiers of 1 to 36 respectively. The media type for the archive class is determined by the devices associated with the archive class. It is not specifically defined. o Plus Mode - Plus mode supports up to 9999 archive classes named HSM$ARCHIVE01 to HSM$ARCHIVE9999, with associated archive identifiers of 1 to 9999 respectively. You specify the media type and (optionally) density which must exactly agree with the corresponding fields associated with off-line devices in the MDMS/SLS file TAPESTART.COM. Specifying a volume pool allows you to reserve specific volumes for HSM use. Getting Started with HSM 6-7 Getting Started with HSM 6.2 Running HSM with the Default Configuration Restore archive classes are the classes to be used when files are unshelved. HSM attempts to unshelve files from the restore archive classes in the specified order until the operation succeeds. To establish your restore archive classes, you use the /RESTORE qualifier. The following command associates archive classes 1 and 2 with the default shelf. It also specifies that UNSHELVE operations use the restore archive classes 1 and 2. Each archive class has an associated media type. $ SMU SET SHELF/DEFAULT/ARCHIVE_ID=(1,2)/RESTORE_ARCHIVE=(1,2) ___________________________________________________________ IF You Want to_._._._________THEN_Use_._._.____________________________ Use one archive SMU SET SHELF/DEFAULT /ARCHIVE=1 class /RESTORE=1 Use two archive SMU SET SHELF/DEFAULT /ARCHIVE=(1,2) classes /RESTORE=(1,2) Use three SMU SET SHELF/DEFAULT /ARCHIVE=(1,2,3) archive_classes__/RESTORE=(1,2,3)__________________________ 6.2.4 Defining Devices for the Archive Classes Now you need to specify which near-line/off-line devices you want to use for copying shelved file data to the archive classes. You must specify a minimum of one device to support near-line or off-line shelving. Dedicating Devices In some circumstances, it is beneficial to dedicate a device for HSM operations. You may want to dedicate a device if you expect a lot of HSM operations on that device and you do not want those operations to be interrupted by another process. For each device definition you create, you have the option of dedicating the device or sharing the device. A dedicated device is allocated to the HSM process. A shared device is allocated to HSM only in response to a request to read or write to the media. Once the operation completes, the device is available to other applications. 6-8 Getting Started with HSM Getting Started with HSM 6.2 Running HSM with the Default Configuration The SMU SET DEVICE/DEDICATE command is used to dedicate a device, the SMU SET DEVICE/SHARE command is used to share a device. The following options are for dedicating or sharing a device: o ALL (default)-Uses the device for shelve, preshelve, unshelve, and cache flush operations o SHELVE-Uses the device exclusively for shelve, preshelve, and cache flush operations o UNSHELVE-Uses the device exclusively for unshelve operations ________________________ Note ________________________ When you dedicate a device for HSM operations, you must make sure the archive classes you assign to the device are compatible with the operations you want to perform. ______________________________________________________ ___________________________________________________________ IF_You_Want_to_._._.__THEN_Use_Command/Qualifier_._._._____ Specify a dedicated SMU SET DEVICE device: /DEDICATE=ALL device Specify a shared SMU SET DEVICE device: /SHARE=ALL device Support the device SMU SET DEVICE device: /ARCHIVE=1 for one archive class Support the device SMU SET DEVICE device: for two archive /ARCHIVE=(1,2) classes Support the device SMU SET DEVICE device: for three archive /ARCHIVE=(1,2,3) classes____________________________________________________ Archive Class, Device, and Media Type For HSM Basic mode, when you associate an archive class with a particular device, you implicitly define the media type for that archive class. HSM, in Basic mode, determines media type for a given device based on the device type. Getting Started with HSM 6-9 Getting Started with HSM 6.2 Running HSM with the Default Configuration Robot Name In Basic mode, you must associate a Robot Name with a tape magazine loader if you wish it to be robotically controlled. 6.2.5 Initializing Tape Volumes for Each Archive Class After setting up the devices, you must initialize each tape volume for the archive classes to be used. For Plus mode, the tape volumes are defined by using STORAGE ADD VOLUME commands to MDMS/SLS. For jukebox loaders such as the TL81x and TL82x, it is important that the volumes names match the external volume label and bar code on the volume. You can use the OpenVMS INITIALIZE command to initialize volumes, or use the SLS Operator Menu (option 3) to do this. HSM Basic mode uses a different approach. There are fixed labels for use in each archive class as shown in Table 6-1: Table 6-1 Archive Class Identifier/Label Reference for HSM __________Basic_Mode_______________________________________ Archive Archive Archive Volume Volume Volume Id_____Label_______Id_____Label_______Id_____Label_________ 1 HS0xxx 13 HSCxxx 25 HSOxxx 2 HS1xxx 14 HSDxxx 26 HSPxxx 3 HS2xxx 15 HSExxx 27 HSQxxx 4 HS3xxx 16 HSFxxx 28 HSRxxx 5 HS4xxx 17 HSGxxx 29 HSSxxx 6 HS5xxx 18 HSHxxx 30 HSTxxx 7 HS6xxx 19 HSIxxx 31 HSUxxx 8 HS7xxx 20 HSJxxx 32 HSVxxx 9 HS8xxx 21 HSKxxx 33 HSWxxx 10 HS9xxx 22 HSLxxx 34 HSXxxx 11 HSAxxx 23 HSMxxx 35 HSYxxx 12_____HSBxxx______24_____HSNxxx______36_____HSZxxx________ 6-10 Getting Started with HSM Getting Started with HSM 6.2 Running HSM with the Default Configuration In the table, the values for xxx are as follows: 001, 002, ..., 099, 101, 102, ..., 199, 201, 202, ..., 999, A01, A02, ..., A99, B01, B02, ..., Z99 This naming convention must be adhered to for Basic Mode, allowing up to 3564 volumes per archive class. An archive class always starts with the "001" value and progresses up in order, as shown. Use the OpenVMS INITIALIZE command to initialize the physical tape volumes for each archive class that you use. The following examples show how to initialize two tape volumes each for archive class 1 and 2. Archive Class ID | _ $ INITIALIZE $1$MUA100: HS0001 ! tape 1 for archive class ID 1 $ INITIALIZE $1$MUA200: HS0002 ! tape 2 for archive class ID 1 $ INITIALIZE $1$MUA100: HS1001 ! tape 1 for archive class ID 2 $ INITIALIZE $1$MUA200: HS1002 ! tape 2 for archive class ID 2 --- | Tape volume ______________________ Important ______________________ It is vital for correct use for all tape volumes to have different labels. If you initialize multiple volumes with the same label, HSM will not be able to differentiate between them and will not be able to unshelve files on the volumes. ______________________________________________________ Getting Started with HSM 6-11 Getting Started with HSM 6.2 Running HSM with the Default Configuration 6.2.6 Set Volume Retention Times for Policy-Based Shelving Each template policy uses the expiration date as the basis for selecting files for shelving. This default is intended to be used with the OpenVMS volume retention feature to provide an effective date of last access. The date of last access is the optimal way to select truly dormant files for shelving by policy. To use the default policy effectively, you must enable volume retention on each volume used for shelving. If you do not specifically enable volume retention on a volume, expiration dates for files on the volume usually will be zero. In this case, the default policy will not select any files for shelving. Verifying Privileges To set volume retention, you must be allowed to enable the SYSPRV system privilege or have write access to the disk volume index file. Setting Volume Retention To set volume retention dates, use the following procedure. For more information about the OpenVMS command SET VOLUME /RETENTION, see the OpenVMS DCL Dictionary. 1. Enable the system privilege for your process: $ SET PROCESS/PRIVILEGE=SYSPRV 2. Enable retention times for each disk volume on your system: $ SET VOLUME/RETENTION=(min,[max]) For min and max, specify the minimum and maximum periods of time you want the files retained on the disk using delta time values. If you enter only one value, the system uses that value for the minimum retention period and calculates the maximum retention period as either twice the minimum or as the minimum plus seven days, whichever is less. If you are not already using expiration dates, the following settings for retention times are suggested: $ SET VOLUME/RETENTION=(1-, 0-00:00:00.01) 6-12 Getting Started with HSM Getting Started with HSM 6.2 Running HSM with the Default Configuration Initializing File Expiration Dates Once you set volume retention on a volume and define a policy using expiration date as a file selection criteria, the expiration dates on files on the volume must be initialized. HSM automatically initializes expiration dates the first time a policy runs on the volume. This initializes dates for all files on the volume that do not already have an expiration date. The expiration date is set to the current date and time, plus the maximum retention time as specified in the SET VOLUME/RETENTION command. After the expiration date has been initialized, the OpenVMS file system automatically updates the expiration date upon read or write access to the file, at a frequency based on the minimum and maximum retention times. 6.3 Additional Configuration Items There are three additional configuration tasks you may want to perform to use in connection with HSM's default configuration: o Authorize shelf servers o Specify a cache for HSM to use o Schedule default policy execution 6.3.1 Authorizing Shelf Servers If your cluster contains a mixture of large nodes and smaller satellite workstations, you may want to restrict shelf server operation to the larger nodes for better performance. Use the SET FACILITY command to initially authorize your shelf server. See the SMU SET FACILITY command in the HSM Guide to Operations for detailed information on this command. In the following example, two nodes (NODE1 and NODE2) are authorized as shelf servers. By default, all shelving operations and all event logging are enabled also. $ SMU SET FACILITY/SERVER=(NODE1,NODE2) Getting Started with HSM 6-13 Getting Started with HSM 6.3 Additional Configuration Items If you omit the /SERVER qualifier, all nodes in the cluster are authorized as shelf servers. ___________________________________________________________ IF_You_Want_to_._._.__THEN_Use_._._._______________________ Authorize one node SMU SET FACILITY/SERVER=node for shelf server operation Authorize several SMU SET FACILITY nodes for shelf /SERVER=(node, node,...) server operation Authorize all nodes SMU SET FACILITY/NOSERVER (default) for shelf server operation__________________________________________________ 6.3.2 Working with a Cache A cache provides many performance benefits for HSM operations, for example, a significant improvement in the response time during shelving operations. If you would like to use a magneto-optical device as a shelf device instead of, or in addition to near-line /off-line devices, define the magneto-optical device as a cache. ___________________________________________________________ IF_You_Want_to_._._.__THEN_Use_Command/Qualifier_._._._____ Define a cache SMU SET CACHE device: volume Set the cache block SMU SET CACHE device: /BLOCK=value size Change the flush SMU SET CACHE device: /INTERVAL=time interval Specify the flush SMU SET CACHE device: /AFTER=time start_time_________________________________________________ An Example of Managing Online Disk Cache A system manager has decided that approximately 250,000 blocks of online disk cache will improve application availability by reducing shelving time. 6-14 Getting Started with HSM Getting Started with HSM 6.3 Additional Configuration Items There are three user disks that contain various amounts of available storage capacity: $1$DUA13, $1$DUA14, and $1$DUA15. The three disk volumes are defined as cache devices with differing amounts of capacity: o $1$DUA13 is set to 100,000 blocks o $1$DUA14 is set to 50,000 blocks o $1$DUA15 is set to 100,000 blocks 6.3.3 Running Default Policies HSM includes a set of default policy definitions to provide a working system upon installation. These definitions are created during the installation procedure and are immediately implemented. The definitions also are used when creating additional definitions. Although schedules are maintained in a database, there is no supplied schedule for the default preventive policy HSM$DEFAULT_POLICY. If you want to implement a preventive policy, you must use the SMU SET SCHEDULE command as shown in the HSM Guide to Operations. Table 6-2 lists the supplied default policy definitions that are configured for operation upon installing HSM. Table_6-2_Supplied_Default_Policy_Definitions______________ Definition________Name_____________________________________ Preventive HSM$DEFAULT_POLICY + policy Reactive HSM$DEFAULT_OCCUPANCY policies HSM$DEFAULT_QUOTA +These_default_definitions_cannot_be_deleted.______________ ___________________________________________________________ 6.3.4 Template Policy Definitions The default definitions for the disk volume, shelf, and preventive policy are also template definitions. When you create new disk volume, shelf, and policy definitions, any parameters not given a value use the parameter value in the template definition. Getting Started with HSM 6-15 Getting Started with HSM 6.3 Additional Configuration Items 6.3.4.1 Using a Template Policy Definition The following steps show how the policy template definition HSM$DEFAULT_POLICY provides values for a newly created policy definition. 1. Examine the template definition values. The policy template definition contains the default values. $ SMU SHOW POLICY/DEFAULT/FULL Policy HSM$DEFAULT_POLICY is enabled for shelving Policy History: Created: 8-JUN-1995 12:39:32.34 Revised: 8-JUN-1995 12:39:32.34 Selection Criteria: State: Enabled Action: Shelving File Event: Expiration date Elapsed time: 180 00:00:00 Before time: Since time: Low Water Mark: 80 % Primary Policy: Space Time Working Set (STWS) Secondary Policy: Least Recently Used (LRU) Verification: Mail notification: Output file: 2. Create a new policy in which the comparison date is based on the last backup date and the low water mark is set to 40 percent. $ SMU SET POLICY NEW_POLICY /BACKUP/LOWWATER_MARK=40 3. Examine the newly created policy definition and compare the values with the default. In this example, The primary policy and secondary policy values are from the default policy definition; the comparison date and the low water mark values have been changed. 6-16 Getting Started with HSM Getting Started with HSM 6.3 Additional Configuration Items $ SMU SHOW POLICY/FULL NEW_POLICY Policy NEW_POLICY is enabled for shelving Policy History: Created: 20-OCT-1994 13:49:26.64 Revised: 20-OCT-1994 13:49:26.64 Selection Criteria: State: Enabled Action: Shelving File Event: Backup date Elapsed time: 180 00:00:00 Before time: Since time: Low Water Mark: 40 % Primary Policy: Space Time Working Set(STWS) Secondary Policy: Least Recently Used(LRU) Verification: Mail notification: Output file: 6.3.4.2 Changing Default Policy Definitions You may use the values supplied in the template definition or change them to suit your needs. To change the values of a template definition, use the SMU SET POLICY command to change the named default definition, or use the /DEFAULT qualifier to change the template itself. Examples Either of the following commands set the HSM$DEFAULT_POLICY secondary policy to STWS: SMU> SMU SET POLICY /SECONDARY_POLICY=STWS/DEFAULT SMU> SMU SET POLICY HSM$DEFAULT_POLICY /SECONDARY_POLICY=STWS 6.4 Plus Mode Offline Environment In Plus mode, you are using MDMS or SLS as your media manager. In addition to setting up the HSM configuration as described above, you also need to set up the MDMS/SLS environment to agree with the HSM definitions. This section discusses the minimum MDMS/SLS operations to run HSM in Plus mode. Getting Started with HSM 6-17 Getting Started with HSM 6.4 Plus Mode Offline Environment This section does not explain everything you need to do to first set up MDMS in an environment. For detailed instructions on installing and configuring MDMS, see the Media and Device Management Services for OpenVMS Guide to Operations. 6.4.1 How HSM Plus Mode and MDMS Work Together By using Media and Device Management Services for OpenVMS (MDMS) software, HSM Plus mode uses common media and device management capabilities. MDMS provides these common services for various storage management products, such as Archive Backup System (ABS) and Storage Library System for OpenVMS (SLS), as well as HSM. 6.4.2 How MDMS Supports HSM MDMS provides the following services: o An integrated and shared approach to controlling access to devices o A shared database to media and device information o Common commands that allow you to manage media across storage management products What this means for HSM is: o If you already use MDMS to support some other storage management product, you will need to do little to add functionality for HSM. o If you do not use MDMS for other storage management products now, you can start using it for HSM and add other products later without having to shift your media and device management approach. o HSM can now support more devices, including TL820s as fully robotic devices. o HSM can support gravity-controlled loading in a Digital Linear Tape (DLT) magazine loader in addition to robotically-controlled loading in a DLT. 6-18 Getting Started with HSM Getting Started with HSM 6.4 Plus Mode Offline Environment 6.4.3 MDMS Commands for HSM Plus Mode Use For HSM to work with MDMS, there are various MDMS commands you may need to use. Table 6-3 lists the MDMS commands you may need to use for HSM Plus mode and describes what each one does. Later sections of this chapter describe how to use some of these commands. For detailed information on working with MDMS, see the Media and Device Management Services for OpenVMS Guide to Operations. Table_6-3_MDMS_Commands_for_HSM_Plus_Mode__________________ MDMS_Command__________Description__________________________ ADD DRIVE Returns a drive to the pool of available drives for MDMS to use. ADD MAGAZINE Adds a magazine name to the magazine database. ADD VOLUME Adds a new volume record with the specified attributes to the volume database. BIND Binds a volume to a slot in a magazine. CREATE LABEL Closes the current label file for MDMS and opens a new one. EXPORT CARTRIDGE Exports a tape cartridge to the out port of a tape jukebox, such as a TL820. EXPORT MAGAZINE Requests that a specific magazine be removed from a tape jukebox. IMPORT CARTRIDGE Imports a single cartridge from the in port of a tape jukebox to a slot inside the jukebox. IMPORT MAGAZINE Imports a magazine into the jukebox. INVENTORY JUKEBOX Performs a physical inventory of the cartridges in a tape jukebox, such as a TL820 or a DLT loader. (continued on next page) Getting Started with HSM 6-19 Getting Started with HSM 6.4 Plus Mode Offline Environment Table_6-3_(Cont.)_MDMS_Commands_for_HSM_Plus_Mode__________ MDMS_Command__________Description__________________________ LABEL Generates a printable label for a volume or volume set. REMOVE DRIVE Removes a drive from the pool of available drives for MDMS to use. REMOVE MAGAZINE Removes a magazine name from the magazine database. REMOVE VOLUME Removes a volume record from the volume database. SET VOLUME Modifies the attributes of a volume. SHOW Various SHOW commands to display MDMS values and attributes. UNBIND Unbinds a volume from a magazine and removes the volume name from the ______________________magazine_database.___________________ 6.4.4 MDMS Configuration Tasks Required to Support HSM Plus Mode To enable HSM to work with MDMS, you must perform the following tasks: 1. Define media triplets in SYS$MANAGER:TAPESTART.COM. 2. Add volumes and volume pools to the MDMS database. 3. Authorize HSM to access volumes in appropriate pools. 4. If you are using magazines for HSM, add magazines to the magazine database and bind the volumes to them. 5. If you are using large tape jukeboxes, there are some special configuration items in TAPESTART.COM. Also, you will need to import the volumes into the jukebox. For detailed instructions on performing MDMS tasks, refer to the MDMS Software Installation and Configuration Chapter in this book. see the Media and Device Management Services for OpenVMS Guide to Operations. 6-20 Getting Started with HSM Getting Started with HSM 6.4 Plus Mode Offline Environment 6.4.4.1 Defining Media Triplets MDMS uses a concept called a media triplet to identify media types and drives the software is allowed to use. The media triplet is comprised of the following symbols: o MTYPE_n-A name that identifies the media type, often related to the physical media type, such as TK85K, TA90, or HSM_TK50. This is the item you identify when you use the SMU SET ARCHIVE /MEDIA_TYPE command in HSM. o DENS_n-The density for media of this type. If there is a value here, you also must include it in the SMU SET ARCHIVE /DENSITY command in HSM. - If the drives for this media type support tape data compaction, set DENS_n to COMP. - For some types of media, such as 9-track, set DENS_n to the real density of the media (for example, 800, 1600, or 6250 for 9-track) - Otherwise, leave DENS_n blank. o DRIVES_n-The tape drives that can support this type of media. Although a drive is listed here, HSM only uses that drive if you enable it with the SMU SET DEVICE command. Some products that interact with MDMS use a fourth item, CAPACITY_n, in their media definitions. For HSM, this symbol is not needed, but can be defined in the media triplet. 6.4.4.2 Defining Tape Jukeboxes If you are going to use robotically-controlled tape jukeboxes, you need to define the jukeboxes in TAPESTART.COM. There are two symbols you must define in TAPESTART.COM to use any type of tape jukeboxes with robotic loading. These symbols are: o TAPE_JUKEBOXES-A list of all tape jukebox names. o tape_jukebox_name-For each name in TAPE_JUKEBOXES, identifies the robot device and tape drives controlled by that device. Getting Started with HSM 6-21 Getting Started with HSM 6.4 Plus Mode Offline Environment The following example shows a correctly-configured jukebox definition: $! $! -------------------------- $! Node Name $! $ NODE := 'F$TRNLNM ("SYS$NODE")' $ NODE = NODE - "::" - "_" $! $!--------------------------------------------------------------------- $! $! Jukebox definitions $! $!--------------------------------------------------------------------- $ $ TAPE_JUKEBOXES := "TL810_1" $ TL810_1 := "''NODE'::$1$DUA810, ''NODE'::$1$MUA43, - ''NODE'::$1$MUA44, ''NODE'::$1$MUA45, ''NODE'::$1$MUA46" Notice that the node name is required in such definitions, and should reflect the node name on which the command procedure is run. As such, the use of the variable ''NODE' parameter is recommended. The drives referenced in this definition must also appear in the media triplets. 6.4.4.3 Adding Volumes to MDMS Database for HSM to Use Once you have defined all the appropriate symbols in TAPESTART.COM, you need to make MDMS aware of the volumes HSM will use. To do this, you use the STORAGE ADD VOLUME command. STORAGE ADD VOLUME has a number of possible qualifiers. For HSM's purposes, the only qualifiers that are essential are: o /MEDIA_TYPE-Must identify the media type you defined in TAPESTART.COM for this volume. o /POOL-Identifies the volume pool to which the volume belongs. o /DENSITY-Must identify the density defined in TAPESTART.COM for this media type, if something is assigned to DENS_n. Digital recommends you put HSM volumes into volume pools. This prevents other applications from using HSM volumes and vice-versa. 6-22 Getting Started with HSM Getting Started with HSM 6.4 Plus Mode Offline Environment 6.4.4.4 Authorizing HSM Access to Volumes If you decide to put HSM volumes into volume pools (as described above), then you need to authorize HSM to access those pools. You authorize access to volume pools by using the Volume Pool Authorization function of the Administrator menu. To access the Administrator menu, use one of the following commands: $ RUN SLS$SYSTEM:SLS$SLSMGR or $ SLSMGR The second command works only if you have installed MDMS and run the SYS$MANAGER:SLS$TAPSYMBOL.COM procedure to define short commands for the MDMS menus. To authorize HSM access to volume pools, use the user name HSM$SERVER. 6.4.4.5 Importing Volumes Into a Jukebox Unless you are configuring a magazine loader (see Section 6.4.4.6), you need to import volumes into the jukebox. For this, use the STORAGE IMPORT CARTRIDGE command. 6.4.4.6 Configuring Magazines If you are using magazines (a physical container with some number of slots that hold tape volumes) with magazine loaders in MDMS, you need to: 1. Add the magazine names to the magazine database. 2. Let MDMS know which volumes belong to which magazines. To add magazines to the magazine database, you use the STORAGE ADD MAGAZINE command. This command adds a magazine name into the magazine database. This command does not verify that this magazine exists or is available to any particular device for use. It simply adds a record to the database to identify the magazine. Getting Started with HSM 6-23 Getting Started with HSM 6.4 Plus Mode Offline Environment To manually associate volumes with a magazine, you use the STORAGE BIND command. This command creates a link in the databases for the specified volume and magazine. Again, this does not ensure the specified volume is in the specified magazine, it simply updates the database entries. You must use the /SLOT qualifier to identify the slot in the magazine where the volume resides (or will reside). If you prefer, you can automatically associate volumes with a magazine. To do this, you must have physical access to the magazine and an appropriate device and the volumes to be associated must be in the magazine. Then, you IMPORT the magazine into the device and use the STORAGE INVENTORY JUKEBOX command. STORAGE INVENTORY JUKEBOX reads the labels of the volumes in the magazine, binds the volumes to the magazine, assigns the magazine slot numbers to the volumes, and updates the magazine and volume databases. Note that the volumes need to be initialized before issuing the INVENTORY command. 6.4.4.7 Importing Magazines or Volumes Into the Jukebox Once you have defined the volumes, and optionally magazines, to use in the jukebox, they need to be imported into the jukebox. The command to use this depends on the actual hardware being used. o For a large tape jukebox such as a TL81x or TL82x, you import volumes directly into the jukebox ports using the STORAGE IMPORT CARTRIDGE command. o For a magazine loader such as a TZ877, you import the entire magazine into the jukebox using the STORAGE IMPORT MAGAZINE command. o To import volumes into a StorageTek silo, you use the STORAGE IMPORT ACS command. Refer to the HSM Command Reference Guide for more detail on this command. 6-24 Getting Started with HSM Getting Started with HSM 6.4 Plus Mode Offline Environment 6.4.4.8 Working with RDF-served Devices in HSM Plus Mode HSM Plus mode supports the use of RDF-served devices for shelving and unshelving. This means you can define devices that are physically separated from the cluster on which the shelving operations initiate. To do this, you must: o Install remote capability (RDF) through MDMS. o Define the device as a remote device in the MDMS configuration o Use the /REMOTE qualifier on the SMU SET DEVICE command. The following example shows how to set up the HSM device definition to work with a remote device: $ SMU SET DEVICE FARNODE::$2$MIA21 /REMOTE /SHARE=ALL /ARCHIVE=(3,4) The following restrictions apply to working with remote devices: o The node name must be included in the SMU SET DEVICE /REMOTE command. o HSM does not have to exist on the remote server node, although RDF does. o The archive classes you define to work with the RDF- served devices are logically different on each cluster. o RDF-served devices cannot be dedicated for HSM use. 6.5 HSM Plus Mode Configuration Examples The following sections illustrate various sample configurations for HSM Plus mode: o The first example sets up four TA90E drives, which support a specific media type. Three of the drives also support generic TA90 access from other applications besides HSM. o The second example shows how a TZ877 device can be configured with three magazines for HSM use. o The third example shows how a local TL820 can be configured with 50 HSM volumes. o The fourth example shows how to set up a RDF-served TL820 for HSM operations. Getting Started with HSM 6-25 Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples These examples show device and archive class configurations for HSM and MDMS. Other HSM details, such as associating archive classes with shelves, are not shown, but are the same as for HSM Basic mode. These examples illustrate device definitions for HSM and MDMS. They do not attempt to show all commands needed to use HSM. For example, the following additional actions may be necessary: o Loading the HSDRIVER and (if needed) GKDRIVER (see Installation Guide) o Setting up an optional cache o Setting up policies o Starting up MDMS and HSM 6.5.1 Sample TA90 Configuration The following procedure defines a media type for a basic device (TA90), adds 50 volumes of that media type to a particular pool, authorizes HSM only to access that pool, and defines the appropriate archive classes and HSM devices for these volumes. 1. Define the media triplet in TAPESTART.COM. $ MTYPE_1 := TA90E $ DENS_1 := COMP $ DRIVES_1 := $1$MUA20, $1$MUA21, $1$MUA22, $1$MUA23 2. Define 50 volumes and add them to a volume pool called HSM_POOL. $ STORAGE ADD VOLUME AA0001/POOL=HSM_POOL/MEDIA_TYPE=TA90E/DENSITY=COMP $ STORAGE ADD VOLUME AA0002/POOL=HSM_POOL/MEDIA_TYPE=TA90E/DENSITY=COMP ... $ STORAGE ADD VOLUME AA0050/POOL=HSM_POOL/MEDIA_TYPE=TA90E/DENSITY=COMP 3. Use the MDMS Administrator Menu to authorize user HSM$SERVER for access to volume pool HSM_POOL on all nodes in the cluster. User HSM$SERVER is the only user allowed to access volumes from this pool, thus the volumes are dedicated to HSM. If a pool is not used, the default pool for HSM$SERVER is used (if any), or the MDMS default pool is used. $ SLSMGR 6-26 Getting Started with HSM Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples 4. Define two archive classes for HSM, both of which use media from HSM_POOL, with media type TA90E with compaction. $ SMU SET ARCHIVE 1 /ADD_POOL=HSM_POOL /DENSITY=COMP /MEDIA_TYPE=TA90E $ SMU SET ARCHIVE 2 /ADD_POOL=HSM_POOL /DENSITY=COMP /MEDIA_TYPE=TA90E 5. Define the devices for HSM use, with $1$MUA23: being dedicated for HSM use. $ SMU SET DEVICE $1$MUA20:, $1$MUA21:, $1$MUA22: /ARCHIVE=(1,2) $ SMU SET DEVICE $1$MUA23: /DEDICATE=ALL /ARCHIVE=(1,2) 6. Associate the default shelf with the archive classes. $ SMU SET SHELF /DEFAULT /ARCHIVE=(1,2) /RESTORE=(1,2) 6.5.2 Sample TZ877 Configuration The following procedure defines a media type and two jukeboxes for TZ877 DLT loaders, defines 14 volumes with two volume pools, authorizes HSM to access those volume pools, and defines the appropriate archive classes and HSM devices for these volumes. 1. Define the media type in TAPESTART.COM. $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := $1$MUA500:, $1$MUA600: 2. Define the jukebox devices in TAPESTART.COM. The TZ877s are connected through an HSJ controller to give them cluster-wide access, where the robot names (command disk names) are $1$DUA500: and $1$DUA600: for devices $1$MUA500: and $1$MUA600: respectively. $ NODE := 'F$TRNLNM ("SYS$NODE")' $ NODE = NODE - "::" - "_" $! $ TAPE_JUKEBOXES := "JUKEBOX1, JUKEBOX2" $ JUKEBOX1 := "''NODE'::$1$DUA500:, ''NODE'::$1$MUA500:" $ JUKEBOX2 := "''NODE'::$1$DUA600:, ''NODE'::$1$MUA600:" 3. Define 14 volumes and add them to two volume pools called HSM_POOL1 and HSM_POOL2. This allows the specification of a separate pool for each magazine resulting in optimal selection of volumes when shelving files. Getting Started with HSM 6-27 Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples $ STORAGE ADD VOLUME TZ0001/POOL=HSM_POOL1/MEDIA_TYPE=TK85K ... $ STORAGE ADD VOLUME TZ0007/POOL=HSM_POOL1/MEDIA_TYPE=TK85K $ STORAGE ADD VOLUME TZ0008/POOL=HSM_POOL2/MEDIA_TYPE=TK85K ... $ STORAGE ADD VOLUME TZ0014/POOL=HSM_POOL2/MEDIA_TYPE=TK85K 4. Use the MDMS Administrator Menu to authorize HSM$SERVER to access the volume pools for all nodes in the cluster. User HSM$SERVER is the only user allowed to access volumes from these pools, thus the volumes are dedicated to HSM. $ SLSMGR 5. Define two magazines containing volumes for each archive class. The magazines are "named" HSM001 and HSM002. $ STORAGE ADD MAGAZINE HSM001/SLOTS=7 $ STORAGE ADD MAGAZINE HSM002/SLOTS=7 6. Bind the volumes to the magazines. $ STORAGE BIND TZ0001 HSM001/SLOT=0 ... $ STORAGE BIND TZ0007 HSM001/SLOT=6 $ STORAGE BIND TZ0008 HSM002/SLOT=0 ... $ STORAGE BIND TZ0014 HSM002/SLOT=6 7. IMPORT the magazines into the loaders as follows: $ STORAGE IMPORT MAGAZINE HSM001 JUKEBOX1 $ STORAGE IMPORT MAGAZINE HSM002 JUKEBOX2 8. Define two archive classes for HSM, using media from pools HSM_POOL1 and HSM_POOL2, with media type TK85K. Note that in this configuration, each magazine contains volumes for a single archive class. $ SMU SET ARCHIVE 1 /MEDIA_TYPE=TK85K /ADD_POOL=HSM_POOL1 $ SMU SET ARCHIVE 2 /MEDIA_TYPE=TK85K /ADD_POOL=HSM_POOL2 9. Define the devices for shared use. $ SMU SET DEVICE $1$MUA500:, $1$MUA600: /ARCHIVE=(1,2) 10.Associate the default shelf with the archive classes. $ SMU SET SHELF /DEFAULT /ARCHIVE=(1,2) /RESTORE_ARCHIVE=(1,2) 6-28 Getting Started with HSM Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples 6.5.3 Sample TL820 Configuration The following procedure defines a media type and jukebox definition for a TL820 device on the local cluster, defines 50 volumes and adds them to a pool, authorizes HSM and other applications to access the volumes in this pool, and defines appropriate archive classes and devices for use. In this example, the TL820 is connected to an HSJ controller with a robot name (command disk name) of $1$DUA820:. 1. Define the media type in TAPESTART.COM. $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := $1$MUA100:, $1$MUA200:, $1$MUA300: 2. Define the jukebox device in TAPESTART.COM. $ NODE := 'F$TRNLNM ("SYS$NODE")' $ NODE = NODE - "::" - "_" $! $ TAPE_JUKEBOXES := "TL820_1" $ TL820_1 := "''NODE'::$1$DUA820:, ''NODE'::$1$MUA100:, - ''NODE'::$1$MUA200:, ''NODE'::$1$MKU300:" 3. Define 50 volumes and add them to a volume pool called TL820_POOL. $ STORAGE ADD VOLUME ACP001 /POOL=TL820_POOL /MEDIA_TYPE=TK85K $ STORAGE ADD VOLUME ACP002 /POOL=TL820_POOL /MEDIA_TYPE=TK85K ... $ STORAGE ADD VOLUME ACP050 /POOL=TL820_POOL /MEDIA_TYPE=TK85K 4. Using the MDMS Administrator Menu, authorize HSM, along with other applications such as Sequential Media Filesystem or Archive/Backup Systemto access this volume pool. $ SLSMGR 5. The TL820 will be treated as a port loader, rather than a magazine loader. Import all 50 volumes into the loader. Note that MDMS and the TL820 hardware determine into which slot the volumes are loaded. HSM needs no knowledge of this. Getting Started with HSM 6-29 Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples $ STORAGE IMPORT CARTRIDGE ACP001 TL820_1 $ STORAGE IMPORT CARTRIDGE ACP002 TL820_1 ... $ STORAGE IMPORT CARTRIDGE ACP050 TL820_1 6. Define three archive classes for HSM, all of which use media from TL820_POOL, with media type TK85K $ SMU SET ARCHIVE 1 /ADD_POOL=TL820_POOL /MEDIA_TYPE=TK85K $ SMU SET ARCHIVE 2 /ADD_POOL=TL820_POOL /MEDIA_TYPE=TK85K $ SMU SET ARCHIVE 3 /ADD_POOL=TL820_POOL /MEDIA_TYPE=TK85K 7. Define the devices for HSM use. One device (drive in the TL820) is set up for dedicated HSM use on archive class 1 only (the primary archive class). $ SMU SET DEVICE $1$MUA100:, $1$MUA200: /ARCHIVE=(1,2,3) $ SMU SET DEVICE $1$MUA300: /DEDICATE=ALL /ARCHIVE=1 8. Set the default shelf to utilize the archive classes: $ SMU SET SHELF /DEFAULT /ARCHIVE=(1,2,3) /RESTORE=(1,2,3) 6.5.4 Sample RDF-served TL820 Configuration The following procedure defines a configuration for an RDF-served TL820 device that resides on a remote node. This example also shows the client and server definitions for setting up both nodes so that a client HSM system can access the TL820. 6.5.4.1 Definitions on Client Node The configuration for TAPESTART.COM on the client node (the one running HSM) is as follows: 1. Define the database node and media triplet in TAPESTART.COM. Because the drives are on a RDF-served node, the node name must be specified in DRIVES_n. The RDF-served node is named BOSTON. $ PRI := BOSTON $ DB_NODES := BOSTON $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := BOSTON::$1$MUA21:, BOSTON::$1$MUA22:, BOSTON::$1$MUA23: 6-30 Getting Started with HSM Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples 2. Define the jukebox device in TAPESTART.COM. All device references must be prefaced by the node name of the RDF-served node. $ TAPE_JUKEBOXES := "JUKE_TL820" $ JUKE_TL820 := "BOSTON::$1$DUA100:, BOSTON::$1$MUA21:, - BOSTON::$1$MUA22:, BOSTON::$1$MUA23:" 3. Define 20 volumes and add them to a volume pool called TL820_POOL. $ STORAGE ADD VOLUME APW201 /POOL=TL820_POOL /MEDIA_TYPE=TK85K $ STORAGE ADD VOLUME APW202 /POOL=TL820_POOL /MEDIA_TYPE=TK85K ... $ STORAGE ADD VOLUME APW220 /POOL=TL820_POOL /MEDIA_TYPE=TK85K 4. Using the MDMS Administrator Menu, authorize HSM, along with other applications such as Sequential Media Filesystem or Archive/Backup System to access this volume pool. $ SLSMGR 5. Define two archive classes for HSM, both of which use media from TL820_POOL, with media type TK85K $ SMU SET ARCHIVE 1 /ADD_POOL=TL820_POOL /MEDIA_TYPE=TK85K $ SMU SET ARCHIVE 2 /ADD_POOL=TL820_POOL /MEDIA_TYPE=TK85K 6. Define the devices for HSM use. All remote devices must be set up for shared access. The device names must match exactly those specified in DRIVES_n in TAPESTART.COM. $ SMU SET DEVICE BOSTON::$1$MUA21: /REMOTE /ARCHIVE=(1,2) $ SMU SET DEVICE BOSTON::$1$MUA22: /REMOTE /ARCHIVE=(1,2) $ SMU SET DEVICE BOSTON::$1$MUA23: /REMOTE /ARCHIVE=(1,2) 7. Associated the default shelf with the archive classes. $ SMU SET SHELF /DEFAULT /ARCHIVE=(1,2) /RESTORE_ARCHIVE=(1,2) 6.5.4.2 Definitions on the RDF-served Node The configuration for TAPESTART.COM on the RDF-served node (the one containing the TL820 device). Note that HSM does not have to be running on the RDF-served node, but MDMS or SLS must be installed and running. Also note that node BOSTON is the database node for MDMS for the enterprise. Getting Started with HSM 6-31 Getting Started with HSM 6.5 HSM Plus Mode Configuration Examples 1. Define the media type in TAPESTART.COM. Note that because the drives are local to this system, no node name is specified. $ PRI := BOSTON $ DB_NODES := BOSTON $! $ MTYPE_1 := TK85K $ DENS_1 := $ DRIVES_1 := $1$MUA21:, $1$MUA22:, $1$MUA23: 2. Define the jukebox device in TAPESTART.COM. $ NODE := 'F$TRNLNM ("SYS$NODE")' $ NODE = NODE - "::" - "_" $! $ TAPE_JUKEBOXES := "JUKE_TL820" $ JUKE_TL820 := "''NODE'::$1$DUA100:, ''NODE'::$1$MUA21:, - ''NODE'::$1$MUA22:, ''NODE'::$1$MUA23:" 3. The TL820 will be treated as a port loader, rather than a magazine loader. Import all 20 volumes into the loader. Note that MDMS and the TL820 hardware determine into which slot the volumes are loaded. HSM needs no knowledge of this. This command must be entered at the RDF-served node. $ STORAGE IMPORT CARTRIDGE APW201 JUKE_TL820 $ STORAGE IMPORT CARTRIDGE APW202 JUKE_TL820 ... $ STORAGE IMPORT CARTRIDGE APW220 JUKE_TL820 Because node BOSTON is the database node, the volume and pool authorization entered on the client node are also valid on the server node. 6.6 HSM Basic Mode Configuration Examples The following example shows how to configure the default shelf, archive classes, devices and caches in HSM Basic mode for two different configurations: o The first example sets up two TZ877 devices for HSM use, each containing seven 20 GB cartridges. With two archive classes, the total HSM shelf size is 140 GB. 6-32 Getting Started with HSM Getting Started with HSM 6.6 HSM Basic Mode Configuration Examples o The second example sets up an RW500 optical jukebox for use as the HSM shelf repository. These examples illustrate device definitions for HSM. They do not attempt to show all commands needed to use HSM. For example, the following additional actions may be necessary: o Loading the HSDRIVER and (if needed) GKDRIVER (see Installation Guide) o Setting up an optional cache o Setting up policies o Starting up HSM 6.6.1 TZ877 Sample Configuration The following procedure defines archive classes 1 and 2 for HSM use. We will assign one TZ877 loader to each archive class. In this example, the magazine loaders are connected directly to a SCSI bus on node OMEGA: as such, they can only be accessed from this node. $! $ SMU SET ARCHIVE 1,2 $ SMU SET SHELF /DEFAULT /ARCHIVE=(1,2) /RESTORE_ARCHIVE=(1,2) $ SMU SET DEVICE $1$MKA100: /ARCHIVE=1 /ROBOT_NAME=$1$GKA101: $ SMU SET DEVICE $1$MKA200: /ARCHIVE=2 /ROBOT_NAME=$1$GKA201: $ SMU SET FACILITY /SERVER=OMEGA $! $! Confirm Setup $! $ SMU SHOW ARCHIVE HSM$ARCHIVE01 has not been used Identifier: 1 Media type: CompacTape III, Loader Label: HS0001 Position: 0 Device refs: 1 Shelf refs: 2 Getting Started with HSM 6-33 Getting Started with HSM 6.6 HSM Basic Mode Configuration Examples HSM$ARCHIVE02 has not been used Identifier: 1 Media type: CompacTape III, Loader Label: HS1001 Position: 0 Device refs: 1 Shelf refs: 2 $ SMU SHOW SHELF Shelf HSM$DEFAULT_SHELF is enabled for Shelving and Unshelving Catalog File: SYS$SYSDEVICE:[HSM$SERVER.CATALOG]HSM$CATALOG.SYS Shelf History: Created: 30-MAY-1996 13:16:33.79 Revised: 30-MAY-1996 13:56:00.27 Backup Verification: Off Save Time: Updates Saved: All Archive Classes: Archive list: HSM$ARCHIVE01 id: 1 HSM$ARCHIVE02 id: 2 Restore list: HSM$ARCHIVE01 id: 1 HSM$ARCHIVE02 id: 2 $ SMU SHOW DEVICE HSM drive HSM$DEFAULT_DEVICE is enabled. Shared access: < shelve, unshelve > Drive status: Not configured Media type: Unknown Type Robot name: Enabled archives: HSM drive _$1$MKA100: is enabled. Dedicated access: < shelve, unshelve > Drive status: Configured Media type: CompacTape III, Loader Robot name: _$1$GKA101: Enabled archives: HSM$ARCHIVE01 id: 1 HSM drive _$1$MKA200: is enabled. Dedicated access: < shelve, unshelve > Drive status: Configured Media type: CompacTape III, Loader Robot name: _$1$GKA201: Enabled archives: HSM$ARCHIVE02 id: 2 6-34 Getting Started with HSM Getting Started with HSM 6.6 HSM Basic Mode Configuration Examples In addition, the tape volumes in each TZ877 loader must be initialized before using HSM. Either manually (using the front panel), or by using the Media Robot Utility (MRU), load each volume and initialize it as follows: $ ROBOT LOAD SLOT 0 ROBOT $1$GKA101 $ INITIALIZE $1$MKA100: HS0001 $ ROBOT LOAD SLOT 1 ROBOT $1$GKA101 $ INITIALIZE $1$MKA100: HS0002 ... $ ROBOT LOAD SLOT 6 ROBOT $1$GKA101 $ INITIALIZE $1$MKA100: HS0007 $ ROBOT LOAD SLOT 0 ROBOT $1$GKA201 $ INITIALIZE $1$MKA200: HS1001 $ ROBOT LOAD SLOT 1 ROBOT $1$GKA201 $ INITIALIZE $1$MKA200: HS1002 ... $ ROBOT LOAD SLOT 6 ROBOT $1$GKA201 $ INITIALIZE $1$MKA200: HS1007 6.6.2 RW500 Example In this example, we are configuring 8 out of 32 platters in an RW500 optical jukebox to be a permanent shelf repository for HSM. Note that the optical platters are set up as a permanent HSM cache, with no cache flushing and no specific block size restrictions. In addition, HSM shelving and unshelving operations must be specifically disabled on the cache devices and all other other platters in the optical jukebox. $ SMU SET CACHE $2$JBA0: /BLOCK=0 /NOINTERVAL /HIGHWATER=100 /NOHOLD $ SMU SET CACHE $2$JBA1: /BLOCK=0 /NOINTERVAL /HIGHWATER=100 /NOHOLD ... $ SMU SET CACHE $2$JBA7: /BLOCK=0 /NOINTERVAL /HIGHWATER=100 /NOHOLD $! $! Disable all shelving on ALL platters in the jukebox $! $ SMU SET VOLUME $2$JBA0: /DISABLE=ALL $ SMU SET VOLUME $2$JBA1: /DISABLE=ALL ... $ SMU SET VOLUME $2$JBA31: /DISABLE=ALL Note that shelving must be disabled on all platters when any of the platters are being used as an HSM cache to avoid platter load thrashing. Getting Started with HSM 6-35 7 _________________________________________________________________ DFS, NFS, and PATHWORKS Access This chapter describes the remote access features of HSM using DFS, NFS, or PATHWORKS. 7.1 DFS, NFS and PATHWORKS Access Support HSM Version 2.2 supports file access to shelved files on client systems where access is through DFS, NFS and PATHWORKS. At installation, HSM sets up such access by default. However, you may want to review this access and change it as needed, because it can potentially affect all accesses. 7.1.1 DFS Access File faulting (and therefore file events) work as expected, with the exception of CTRL-Y/exit. Typing CTRL-Y exit during a file fault has no effect. The client side process waits until the file fault completes and the file fault is not canceled. In addition, with DFS one can determine the shelving state of a file just as if the disk was local (i.e. DIRECTORY /SHELVED and DIRECTORY/SELECT both work correctly). The shelve and unshelve commands do not work on files on DFS-served devices. The commands do work on the VMScluster that has local access to the devices, however. 7.1.2 NFS Access The normal default faulting mechanism (fault on data access), does not work for NFS-served files. The behavior is as if the file is a zero-block sequential file. Performing "cat" (or similar commands) results in no output. DFS, NFS, and PATHWORKS Access 7-1 DFS, NFS, and PATHWORKS Access 7.1 DFS, NFS and PATHWORKS Access Support However, at installation time, HSM Version 2.2 enables such access by defining a logical name that allows file faults on an OPEN of a file by the NFS process. By default, the following system and cluster wide logical name is defined: $ DEFINE/SYSTEM HSM$FAULT_ON_OPEN "NFS$SERVER" This definition supports access to NFS-served files upon an OPEN of a file. If you do not want NFS access to shelved files, simply de-assign the logical name as follows: $ DEASSIGN/SYSTEM HSM$FAULT_ON_OPEN For a permanent change, this command should be placed in: SYS$STARTUP:HSM$LOGICALS.COM For NFS-served files, file events (device full and user quota exceeded) occur normally with the triggering process being the NFS$SERVER process. The quota exceeded event occurs normally because the any files extended by the client are charged to the client's proxy not NFS$SERVER. If the new logical is defined for the NFS$SERVER, the fault will occur on OPEN and appears transparent to the client, with the possible exception of messages as follows: % cat /usr/oreo/shelve_test.txt.2 NFS2 server oreo not responding still trying NFS2 server oreo ok The first message appears when the open doesn't complete immediately. The second message (ok) occurs when the open completes. The file contents, in the above example, are then displayed. Typing CTRL-C during the file fault returns the user to the shell. Since the NFS server does not issue an IO$_CANCEL against the faulting I/O, the file fault is not canceled and the file will be unshelved eventually. It is not possible from the NFS client to determine whether a given file is shelved. Further, like DFS devices, the shelve and unshelve commands are not available to NFS mounted devices. 7-2 DFS, NFS, and PATHWORKS Access DFS, NFS, and PATHWORKS Access 7.1 DFS, NFS and PATHWORKS Access Support 7.1.3 PATHWORKS Normal attempts to access a shelved file from a PATHWORKS client initiate a file fault on the server node. If the file is unshelved quickly enough (e.g. from cache), the user sees only the delay in accessing the file. If the unshelve is not quick enough, an application-defined timeout occurs and a message window pops up indicating the served disk is not responding. The timeout value varies on the application. No retry is attempted. However, this behavior can be modified by changing HSM's behavior to a file open by returning a file access conflict error, upon which most PC applications retry (or allow the user to retry) the operation after a delay. After a few retries, the file fault will succeed and the file can be accessed normally. To enable PATHWORKS access to shelved files using the retry mechanism, HSM defines the following logical name on installation: $ DEFINE/SYSTEM HSM$FAULT_AFTER_OPEN "PCFS_SERVER, PWRK$LMSRV" This definition supports access to PATHWORKS files upon an OPEN of a file. If you do not want PATHWORKS to access shelved files via retries, simply de-assign the logical name as follows: $ DEASSIGN/SYSTEM HSM$FAULT_AFTER_OPEN For a permanent change, this command should be placed in: SYS$STARTUP:HSM$LOGICALS.COM The decision on which access method to use depends upon the typical response time to access shelved files in your environment. If the logical name is defined, HSM imposes a 3-second delay in responding to the OPEN request for PATHWORKS accesses only. During this time, the file may be unshelved: otherwise, a "background" unshelve is initiated which will result in a successful open after a delay and retries. At this point, the file fault on the server node is under way and cannot be canceled. DFS, NFS, and PATHWORKS Access 7-3 DFS, NFS, and PATHWORKS Access 7.1 DFS, NFS and PATHWORKS Access Support The affect of the access on the PC environment varies according to the PC operating system. For windows 3.1 and DOS, the computer waits until the file is unshelved. For Windows NT and Windows-95, only the windows application itself waits. File events (device full and user quota exceeded) occur normally with the triggering process being the PATHWORKS server process. The quota exceeded event occurs normally because the any files extended by the client are charged to the client's proxy not the PATHWORKS server. It is not possible from a PATHWORKS client to determine whether a file is shelved. In addition, there is no way to shelve or unshelve files explicitly (via shelve- or unshelve-like commands). There is also no way to cancel a file fault once it has been initiated. Most PC applications are designed to handle "file sharing" conflicts. Thus, when HSM detects the PATHWORKS server has made an access request, it can initiate unshelving action, but return "file busy". The typical PC application will continue to retry the original open, or prompt the user to retry or cancel. Once the file is unshelved, the next OPEN succeeds without shelving interaction. 7.1.4 New Logical Names for NFS and PATHWORKS Access As just discussed, HSM supports two logical names that alter the behavior of opening a shelved file for NFS and PATHWORKS access support. These are: o HSM$FAULT_ON_OPEN - This logical name forces a file fault on an Open of a file for the processes listed in the equivalence name, and the open waits until the file fault is complete. Designed for use with the NFS server. o HSM$FAULT_AFTER_OPEN - This logical name forces a deferred file fault on the file when it is opened. If the fault completes within three seconds, the open completes successfully, otherwise it fails with "file busy", but initiates a "background" file fault. Repeated attempts to open the file will eventually succeed. Designed for use with the PATHWORKS server. 7-4 DFS, NFS, and PATHWORKS Access DFS, NFS, and PATHWORKS Access 7.1 DFS, NFS and PATHWORKS Access Support The default behavior is to perform no file fault on Open; rather the file fault occurs upon a read or write to the file. Each logical name can take a list of process names to alter the behavior of file faults on open. For example: $ DEFINE/SYSTEM HSM$FAULT_ON_OPEN "NFS$SERVER, USER_SERVER, SMITH" The HSM$FAULT_ON_OPEN can also be assigned to "HSM$ALL", which will cause a file fault on open for all processes. This option is not allowed for HSM$FAULT_AFTER_OPEN. As these logicals are defined to allow NFS and PATHWORKS access, they are not recommended for use with other processes, since they will cause many more file faults than are actually needed in a normal OpenVMS environment. When used, the logicals must be system-wide, and should be defined identically on all nodes in the VMScluster environment. These logical name assignments or lack thereof take effect immediately without the need to restart HSM. DFS, NFS, and PATHWORKS Access 7-5 A _________________________________________________________________ HSM Basic Mode Installation Example This appendix contains a sample HSM Basic mode installation on a VAX system. Upon completion of the actual installation, this example runs the IVP to determine whether the installation was correct. ________________________ Note ________________________ HSM must be shut down using $ SMU SHUTDOWN on the installation system and all VMScluster nodes that use the installation system's system disk before you install the new version of the HSM software, otherwise, the installation fails. ______________________________________________________ $ @SYS$UPDATE:VMSINSTAL HSM022 DISK$:[DIR] OpenVMS VAX Software Product Installation Procedure V6.1 It is 10-JAN-1997 at 14:12. 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: HSM V2.2 Beginning installation of HSM V2.2 at 14:13 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. HSM Basic Mode Installation Example A-1 HSM Basic Mode Installation Example **************************************************************** * Hierarchical Storage Management (HSM) * * for OpenVMS V2.2 Installation * * * * Copyright(c) Digital Equipment Corporation 1994 - 1997. * * All Rights Reserved. Unpublished rights reserved under the * * copyright laws of the United States. * **************************************************************** * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? *** HSM License *** Correct installation and operation of this software requires that one of the following Product Authorization Keys (PAKs) reflecting your software license be present on this system: HSM-SERVER HSM-USER * Does this product have an authorization key registered and loaded [YES]? *** HSM Mode *** With this version, HSM can operate in one of two possible modes: BASIC - The standalone HSM product which supports a limited number of nearline and offline devices. PLUS - The integrated HSM product, integrated with Media and Device Management Services (MDMS) which supports an expanded number of nearline and offline devices. NOTE: MDMS or SLS V2.5B or newer must be installed before installing HSM PLUS mode. Also, once files are shelved in PLUS mode, you may *not* change back to BASIC mode. Enter BASIC or PLUS to select the mode in which you want HSM to operate. * Enter the mode to install [PLUS]: BASIC %HSM-I-MODE, Installing HSM V2.2 BASIC mode *** HSM Account *** A privileged account named HSM$SERVER will be created for use by HSM processes. This account will not allow interactive logins and the password will be automatically generated. The installation procedure will not proceed until you enter a valid user identification code (UIC) for the HSM$SERVER account. The UIC must be unique and within the SYSTEM group. A-2 HSM Basic Mode Installation Example HSM Basic Mode Installation Example * Enter the UIC to be used for HSM$SERVER account [[1,22]]: *** HSM Device *** You will now be asked to enter a disk device specification to be used as a repository for HSM configuration databases and log files. NOTE: *** This device must have at least 100000 free blocks and be available to all nodes in the cluster that will be running HSM *** * Enter the disk device to use for HSM files [SYS$SYSDEVICE:]: The HSM files will be placed at SYS$SYSDEVICE:[HSM$SERVER] * Is this correct [YES]? %VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named HSM$SERVER. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier HSM$SERVER value [000001,000022] added to rights database %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named HSM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named HSM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named HSM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[HSM$SERVER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[HSM$SERVER.LOG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[HSM$SERVER.CATALOG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[HSM$SERVER.MANAGER]. %HSM-I-CHKQUO, Checking for DISKQUOTAs on device SYS$SYSDEVICE: %VMSINSTAL-I-RESTORE, Restoring product save set B ... The file SYS$STARTUP:HSM$STARTUP.COM contains specific commands needed to start the HSM Software. This file should not be modified. To start the software at system startup time, add the line $ @SYS$STARTUP:HSM$STARTUP.COM to the system startup procedure SYS$MANAGER:SYSTARTUP_VMS.COM The HSM Catalog and SMU Databases must be created before running HSM. This procedure can create the HSM Catalog and SMU Databases automatically for you as a post-installation task. * Do you want to run the database creation procedure [YES]? The file SYS$SYSTEM:SETFILENOSHELV.COM should be executed to set all system disk files as NON-SHELVABLE. This is important to preserve the integrity of your system disk. HSM Basic Mode Installation Example A-3 HSM Basic Mode Installation Example This procedure can submit SETFILENOSHELV.COM to a batch execution queue for you as a post-installation task. * Do you want to submit SETFILENOSHELV.COM [YES]? ***************************************************************** * IMPORTANT * ***************************************************************** * When you upgrade to a new version of VMS you should invoke * * SYS$SYSTEM:SETFILENOSHELV.COM again. The installation of VMS * * does not and will not automatically set your system disk * * files to NON-SHELVABLE for you. * ***************************************************************** %HSM-I-DONEASK, No further questions will be asked during this installation. -HSM-I-DONEASK, The installation should take less than 10 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. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %HSMPOST-I-START, executing HSM Post-Installation procedure %HSMPOST-I-CREATE_CATALOG, Creating HSM catalog This command file creates the default HSM Catalog file. The Catalog file is a directory of every file that was ever shelved. It should be protected as such by controlling access to it. You should only have to create the Catalog file once because that catalog will be used from that point on and contains a history of shelving activity and more importantly locates the offline data for the shelved files. You should make sure that the Catalog file gets backed up on a regular basis since loss of this file could mean loss of the data for your shelved files. %HSMPOST-S-CREATE_CATALOG, HSM catalog created successfully %HSMPOST-I-CREATE_DB, Creating HSM SMU database files %HSMPOST-S-CREATE_DB, HSM SMU database files created successfully A-4 HSM Basic Mode Installation Example HSM Basic Mode Installation Example %HSMPOST-I-SETMODE, setting HSM mode to BASIC Job SETFILENOSHELV (queue HSM$POLICY_NODE, entry 2) holding until 10-JAN-1997 14:24 %HSMPOST-I-DONE, HSM post-installation procedure complete *** HSM for OpenVMS V2.2 Installation Verification Procedure (IVP) *** Copyright(c) Digital Equipment Corporation 1994 - 1997. %HSM-I-IVPSTART, starting HSM shelving facility on node NODE %SMU-S-SHP_STARTED, shelf handler process started 000000AE %SMU-S-PEP_STARTED, policy execution process started 000000AF HSM Shelf Handler version - V2.x (BLxx), Oct 20 1997 HSM Shelving Driver version - V2.x (BLxx), Oct 20 1997 HSM Policy Execution version - V2.x (BLxx), Oct 20 1997 HSM Shelf Management version - V2.x (BLxx), Oct 20 1997 HSM for OpenVMS is enabled for Shelving and Unshelving Facility history: Created: 10-JAN-1997 14:19:28.26 Revised: 10-JAN-1997 14:19:41.83 Designated servers: Any cluster member Current server: NODE Catalog server: Disabled Event logging: Audit Error Exception HSM mode: Basic Remaining license: Unlimited %SMU-I-CACHE_CREATED, cache device _NODE$DKB300: created %SMU-I-SHELF_UPDATED, shelf HSM$DEFAULT_SHELF updated %SMU-I-VOLUME_CREATED, volume _NODE$DKB300: created %SHELVE-S-SHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP1.TMP;1 shelved %UNSHELVE-S-UNSHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP1.TMP;1 unshelved %SHELVE-S-SHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP2.TMP;1 shelved %HSM-I-UNSHLVPRG, unshelving file NODE$DKB300:[SYSCOMMON.SYSTEST.HSM]HSM_IVP2.TMP;1 %SMU-I-POLICY_CREATED, policy HSM$IVP_POLICY created %SMU-I-SCHED_CREATED, scheduled policy HSM$IVP_POLICY for volume _NODE$DKB300: was created on server NODE Job _NODE$DKB300: (queue HSM$POLICY_NODE, entry 3) started on HSM$POLICY_NODE %HSM-I-IVPWAIT, waiting for HSM$IVP_POLICY to execute... %HSM-I-IVPWAIT, waiting for HSM$IVP_POLICY to execute... %UNSHELVE-S-UNSHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP3.TMP;1 unshelved %HSM-I-IVPSHUT, shutting down HSM shelving facility on node NODE %HSM-I-IVPSHUTWAIT, waiting for HSM to shutdown... %HSM-I-IVPSHUTWAIT, waiting for HSM to shutdown... HSM Basic Mode Installation Example A-5 HSM Basic Mode Installation Example *** The IVP for HSM V2.2 was successful! *** Hierarchical Storage Management (HSM) for OpenVMS, Version V2.2 Copyright Digital Equipment Corporation 1994 - 1997. All Rights Reserved. %SMU-S-SHP_STARTED, shelf handler process started 000000B2 %SMU-S-PEP_STARTED, policy execution process started 000000B3 HSM for OpenVMS is enabled for Shelving and Unshelving Facility history: Created: 10-JAN-1997 14:19:04.15 Revised: 10-JAN-1997 14:22:03.89 Designated servers: Any cluster member Current server: NODE Catalog server: Disabled Event logging: Audit Error Exception HSM mode: Basic Remaining license: Unlimited HSM Software has been successfully started Installation of HSM V2.2 completed at 14:22 VMSINSTAL procedure done at 14:22 A-6 HSM Basic Mode Installation Example B _________________________________________________________________ HSM Plus Mode Installation Example This appendix contains a sample HSM Plus mode installation on a VAX system. In this instance, HSM Version 2.2 is installed over an existing HSM environment. Upon completion of the actual installation, this example runs the IVP to determine whether the installation was correct. ________________________ Note ________________________ HSM must be shut down using $ SMU SHUTDOWN on the installation system and all VMScluster nodes that use the installation system's system disk before you install the new version of the HSM software, otherwise, the installation fails. ______________________________________________________ $ @SYS$UPDATE:VMSINSTAL HSM022 DISK$:[DIR] OpenVMS VAX Software Product Installation Procedure V6.1 It is 10-JAN-1997 at 14:40. 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: HSM V2.2 Beginning installation of HSM V2.2 at 14:40 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. HSM Plus Mode Installation Example B-1 HSM Plus Mode Installation Example **************************************************************** * Hierarchical Storage Management (HSM) * * for OpenVMS V2.2 Installation * * * * Copyright(c) Digital Equipment Corporation 1994 - 1997. * * All Rights Reserved. Unpublished rights reserved under the * * copyright laws of the United States. * **************************************************************** * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? *** HSM License *** Correct installation and operation of this software requires that one of the following Product Authorization Keys (PAKs) reflecting your software license be present on this system: HSM-SERVER HSM-USER * Does this product have an authorization key registered and loaded [YES]? *** HSM Mode *** With this version, HSM can operate in one of two possible modes: BASIC - The standalone HSM product which supports a limited number of nearline and offline devices. PLUS - The integrated HSM product, integrated with Media and Device Management Services (MDMS) which supports an expanded number of nearline and offline devices. NOTE: MDMS or SLS V2.5B or newer must be installed before installing HSM PLUS mode. Also, once files are shelved in PLUS mode, you may *not* change back to BASIC mode. B-2 HSM Plus Mode Installation Example HSM Plus Mode Installation Example Enter BASIC or PLUS to select the mode in which you want HSM to operate. * Enter the mode to install [PLUS]: %HSM-I-MODE, Installing HSM V2.2 PLUS mode %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named HSM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named HSM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named HSM$SERVER. %UAF-I-MDFYMSG, user record(s) updated %HSM-I-CHKQUO, Checking for DISKQUOTAs on device SYS$SYSDEVICE: %VMSINSTAL-I-RESTORE, Restoring product save set B ... %HSM-I-CHKMRU, Checking version of Media Robot Utility (MRD$SHR.EXE) %HSM-I-CHKHSD, Checking for updated version of HSDRIVER The file SYS$STARTUP:HSM$STARTUP.COM contains specific commands needed to start the HSM Software. This file should not be modified. To start the software at system startup time, add the line $ @SYS$STARTUP:HSM$STARTUP.COM to the system startup procedure SYS$MANAGER:SYSTARTUP_VMS.COM The file SYS$SYSTEM:SETFILENOSHELV.COM should be executed to set all system disk files as NON-SHELVABLE. This is important to preserve the integrity of your system disk. This procedure can submit SETFILENOSHELV.COM to a batch execution queue for you as a post-installation task. * Do you want to submit SETFILENOSHELV.COM [YES]? NO ***************************************************************** * IMPORTANT * ***************************************************************** * When you upgrade to a new version of VMS you should invoke * * SYS$SYSTEM:SETFILENOSHELV.COM again. The installation of VMS * * does not and will not automatically set your system disk * * files to NON-SHELVABLE for you. * ***************************************************************** %HSM-I-DONEASK, No further questions will be asked during this installation. -HSM-I-DONEASK, The installation should take less than 10 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. HSM Plus Mode Installation Example B-3 HSM Plus Mode Installation Example 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. %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %HSMPOST-I-START, executing HSM Post-Installation procedure %HSMPOST-I-SMUDBCONVERT, converting SMU databases %SMUDBCONVERT-I-ARCHIVE, converting SMU archive database %SMUDBCONVERT-I-CURRENT, SMU archive database conversion not required %SMUDBCONVERT-I-CACHE, converting SMU cache database %SMUDBCONVERT-I-CURRENT, SMU cache database conversion not required %SMUDBCONVERT-I-CONFIG, converting SMU shelf database %SMUDBCONVERT-S-CONFIG, SMU shelf database converted %SMUDBCONVERT-I-DEVICE, converting SMU device database %SMUDBCONVERT-S-DEVICE, SMU device database converted %SMUDBCONVERT-I-POLICY, converting SMU policy database %SMUDBCONVERT-S-POLICY, SMU policy database converted %SMUDBCONVERT-I-VOLUME, converting SMU volume database %SMUDBCONVERT-S-VOLUME, SMU volume database converted %HSMPOST-S-SMUDBCONVERT, SMU databases successfully converted %HSMPOST-I-CATCONVERT, converting default catalog %HSMPOST-I-CATCURRENT, catalog conversion not required %HSMPOST-I-CATATTRUPD, updating catalog file attributes %HSMPOST-S-CATATTRUPD, catalog file attributes updated %HSMPOST-I-SETMODE, setting HSM mode to PLUS %HSMPOST-I-DONE, HSM post-installation procedure complete *** HSM for OpenVMS V2.2 Installation Verification Procedure (IVP) *** Copyright(c) Digital Equipment Corporation 1994 - 1997. %HSM-I-IVPSTART, starting HSM shelving facility on node NODE %SMU-S-SHP_STARTED, shelf handler process started 000000C3 %SMU-S-PEP_STARTED, policy execution process started 000000C4 HSM Shelf Handler version - V2.x (BLxx), Oct 20 1997 HSM Shelving Driver version - V2.x (BLxx), Oct 20 1997 HSM Policy Execution version - V2.x (BLxx), Oct 20 1997 HSM Shelf Management version - V2.x (BLxx), Oct 20 1997 B-4 HSM Plus Mode Installation Example HSM Plus Mode Installation Example HSM for OpenVMS is enabled for Shelving and Unshelving Facility history: Created: 10-JAN-1997 14:52:28.26 Revised: 10-JAN-1997 14:52:41.83 Designated servers: Any cluster member Current server: NODE Catalog server: Disabled Event logging: Audit Error Exception HSM mode: Basic Remaining license: Unlimited %SMU-I-CACHE_CREATED, cache device _NODE$DKB300: created %SMU-I-SHELF_UPDATED, shelf HSM$DEFAULT_SHELF updated %SMU-I-VOLUME_CREATED, volume _NODE$DKB300: created %SHELVE-S-SHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP1.TMP;1 shelved %UNSHELVE-S-UNSHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP1.TMP;1 unshelved %SHELVE-S-SHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP2.TMP;1 shelved %HSM-I-UNSHLVPRG, unshelving file NODE$DKB300:[SYSCOMMON.SYSTEST.HSM]HSM_IVP2.TMP;1 %SMU-I-POLICY_CREATED, policy HSM$IVP_POLICY created %SMU-I-SCHED_CREATED, scheduled policy HSM$IVP_POLICY for volume _NODE$DKB300: was created on server NODE Job _NODE$DKB300: (queue HSM$POLICY_NODE, entry 5) started on HSM$POLICY_NODE %HSM-I-IVPWAIT, waiting for HSM$IVP_POLICY to execute... %HSM-I-IVPWAIT, waiting for HSM$IVP_POLICY to execute... %UNSHELVE-S-UNSHELVED, file SYS$COMMON:[SYSTEST.HSM]HSM_IVP3.TMP;1 unshelved %HSM-I-IVPSHUT, shutting down HSM shelving facility on node NODE %HSM-I-IVPSHUTWAIT, waiting for HSM to shutdown... %HSM-I-IVPSHUTWAIT, waiting for HSM to shutdown... *** The IVP for HSM V2.2 was successful! *** Hierarchical Storage Management (HSM) for OpenVMS, Version V2.2 Copyright Digital Equipment Corporation 1994 - 1997. All Rights Reserved. %SMU-S-SHP_STARTED, shelf handler process started 00000103 %SMU-S-PEP_STARTED, policy execution process started 00000104 HSM Plus Mode Installation Example B-5 HSM Plus Mode Installation Example HSM for OpenVMS is enabled for Shelving and Unshelving Facility history: Created: 10-JAN-1997 14:51:04.15 Revised: 10-JAN-1997 14:54:03.89 Designated servers: Any cluster member Current server: NODE Catalog server: Disabled Event logging: Audit Error Exception HSM mode: Basic Remaining license: Unlimited HSM Software has been successfully started Installation of HSM V2.2 completed at 14:55 VMSINSTAL procedure done at 14:55 B-6 HSM Plus Mode Installation Example C _________________________________________________________________ HSM Logicals C.1 HSM Logical Names This appendix lists the logical names entered into the logical name tables when HSM 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. (LNM$PROCESS_TABLE) (LNM$JOB_8CE40840) (LNM$GROUP_000107) (LNM$SYSTEM_TABLE) "HSM$CATALOG" = "DISK$USER1:[HSM$SERVER.CATALOG]" "HSM$FAULT_AFTER_OPEN" = "PCFS_SERVER, PWRK$LMSRV" "HSM$FAULT_ON_OPEN" = "NFS$SERVER" "HSM$LOG" = "DISK$USER1:[HSM$SERVER.LOG]" "HSM$MANAGER" = "DISK$USER1:[HSM$SERVER.MANAGER]" "HSM$PEP_REQUEST" = "MBA454:" "HSM$PEP_RESPONSE" = "MBA455:" "HSM$PEP_TERMINATION" = "MBA427:" "HSM$REPACK_DURATION" = "0" "HSM$ROOT" = "DISK$AIM2:[HSM$ROOT.]" "HSM$SHP_REQUEST" = "MBA451:" "HSM$SHP_RESPONSE" = "MBA452:" "HSM$SHP_URGENT" = "MBA450:" (DECW$LOGICAL_NAMES) HSM Logicals C-1 D _________________________________________________________________ HSM Files D.1 HSM File Names The HSM installation procedure creates several files on your system. Table D-1 lists and describes the files installed on server and client nodes. File names with an asterisk (*) preceding them are installed only on server nodes. Table_D-1_HSM_Files_Installed____________________________________ File_Name__________________Description___________________________ HSM$SERVER:_directory____________________________________________ CATALOG.DIR Directory where the HSM catalog databases are kept LOG.DIR Directory where HSM audit and error logs are kept MANAGER.DIR Directory where the HSM management databases are kept SETFILENOSHELV.LOG Shows which files were set non- shelvable _________________________________________________________________ HSM$SERVER.CATALOG:_directory____________________________________ HSM$CATALOG.SYS This is the default catalog database. The user may define other catalogs that would be placed in this directory. (continued on next page) HSM Files D-1 HSM Files D.1 HSM File Names Table_D-1_(Cont.)_HSM_Files_Installed____________________________ File_Name__________________Description___________________________ HSM$SERVER.MANAGER:_directory____________________________________ HSM$ARCHIVE_DB.SMU Contain the archive class database HSM$CACHE_DB.SMU;1 Contains HSM cache database HSM$CONFIG_DB.SMU;1 Contains system configuration database HSM$DEVICE_DB.SMU;1 Contains HSM device database HSM$POLICY_DB.SMU;1 Contains HSM policy database HSM$SHELF_LOG_ CONFIG.TXT;1 HSM$SHP_REQUEST.SYS;1 Keeps a record of the shelf-handler requests for the cluster HSM$SHP_REQUEST_ Keeps a record of the shelf_handler node.SYS;1 requests for the node HSM$VOLUME_DB.SMU;1 Contains HSM Volume database. _________________________________________________________________ HSM$SERVER.LOG:_directory________________________________________ HSM$PEP_AUDIT.LOG Event audit log of HSM policy execution HSM$PEP_ERROR.LOG;1 Error log of HSM policy execution HSM$SHELF_HANDLER.LOG;1 Log file of shelf handler process HSM$SHELF_PEP.LOG;1 Log file of Policy execution process HSM$SHP_AUDIT.LOG;1 Event audit log of shelf handler activity HSM$SHP_ERROR.LOG;1________Error_log_of_shelf_handler_activity___ D-2 HSM Files E _________________________________________________________________ MDMS Logicals E.1 MDMS Logical Names Table E-1 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. The LNM$JOB table also contains logical names that are defined when a user logs in to a system running MDMS software. Table_E-1_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. (continued on next page) MDMS Logicals E-1 MDMS Logicals E.1 MDMS Logical Names Table_E-1_(Cont.)_MDMS_Logical_Names_____________________________ Logical_Name_______Definition_and_Description____________________ LNM$SYSTEM_TABLE Entries__________________________________________________________ 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] 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) E-2 MDMS Logicals MDMS Logicals E.1 MDMS Logical Names Table_E-1_(Cont.)_MDMS_Logical_Names_____________________________ Logical_Name_______Definition_and_Description____________________ 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 E-1. MDMS Logicals E-3 MDMS Logicals E.1 MDMS Logical Names Example E-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) E-4 MDMS Logicals MDMS Logicals E.1 MDMS Logical Names Example E-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) MDMS Logicals E-5 MDMS Logicals E.1 MDMS Logical Names Example E-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) E-6 MDMS Logicals MDMS Logicals E.1 MDMS Logical Names Example E-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) MDMS Logicals E-7 MDMS Logicals E.1 MDMS Logical Names Example E-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) E-8 MDMS Logicals MDMS Logicals E.1 MDMS Logical Names Example E-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" MDMS Logicals E-9 F _________________________________________________________________ MDMS Files F.1 MDMS File Names The MDMS installation procedure creates several files on your system. Table F-1 lists and describes the files installed on server and client nodes. File names with an asterisk (*) preceding them are installed only on server nodes. Table_F-1_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 (continued on next page) MDMS Files F-1 MDMS Files F.1 MDMS File Names Table_F-1_(Cont.)_MDMS_Files_Installed___________________________ _________________________________________________________________ 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 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 (continued on next page) F-2 MDMS Files MDMS Files F.1 MDMS File Names Table_F-1_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ 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 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 (continued on next page) MDMS Files F-3 MDMS Files F.1 MDMS File Names Table_F-1_(Cont.)_MDMS_Files_Installed___________________________ File_Name__________________Description___________________________ SLS$SYSTEM:_directory____________________________________________ 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) F-4 MDMS Files MDMS Files F.1 MDMS File Names Table_F-1_(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) MDMS Files F-5 MDMS Files F.1 MDMS File Names Table_F-1_(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) F-6 MDMS Files MDMS Files F.1 MDMS File Names Table_F-1_(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) MDMS Files F-7 MDMS Files F.1 MDMS File Names Table_F-1_(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________ F-8 MDMS Files _________________________________________________________________ Index A Changing policy definitions, _______________________________ 6-17 Allocating devices, 6-8 Configuration archive class additional items, 6-13 initializing tape volumes, Basic mode example, 6-32 6-12 default, 6-1, 6-5 Archive class magazines, 6-23 default shelf, 6-7 MDMS tasks, 6-20 defining, 6-8 RW500, 6-35 defining devices, 6-8 Correcting installation identifier, 6-10 problems, 4-5 initializing tape media, 6-10 D______________________________ label reference table, 6-10 Dedicating devices, 6-9 Authorizing shelf servers, Default 6-13 cache, 6-14 device, 6-3 B______________________________ facility, 6-2 Backup operations facility definition, 6-5 remote, 3-25 HSM configuration, 6-5 Basic mode, 1-4 policies, 6-4 see HSM Basic policy definitions, 6-12 policy definitions/no C schedule, 6-15 _______________________________ shelf, 6-2 Cache, 6-14 shelf for acrchive class, defining for default, 6-14 6-7 managing, 6-14 template policy definitions, Catalog, 5-9 6-15 creating manually, 5-9 volume attributes, 6-3 logicals, 5-9 volume record attributes, 6-3 Index-1 Default policy definitions changing, 6-17 F______________________________ Defining archive classes, 6-8 Facility Device default definition, 6-5 allocating, 6-8 File dedicating, 6-9 expiration dates, 6-13 default, 6-3 HSM022.RELEASE_NOTES, 4-1 magneto-optical, 6-14 HSM022_RELEASE_NOTES.PS, 4-1 sharing, 6-9 Files DFS, 7-1 expiration date, 6-12 DFS access, 7-1 HSM$STARTUP.COM, 5-9 Disk cache managing, 6-14 SYS$STARTUP_VMS.COM, 5-8 SYSHUTDWN.COM, 5-9 E______________________________ Editing the system login file, G______________________________ 3-12 GBLSECTIONS required value, Editing the systemwide command 4-4 files, 3-12 Getting started, 6-1 Example Global symbols associating archive class, defining, 3-12 6-8 authorizing shelf servers, H______________________________ 6-13 How to Basic mode configuration, edit the system login file, 6-32, 6-33 3-12 changing policy, 6-17 register HSM license, 4-6 defining archive class, 6-6 register PAK, 4-6 defining jukeboxes, 6-21 HSDRIVER optical device as cache, connecting, 5-9 6-14 HSM RDF-served TL820, 6-30 default device, 6-3 remote device setup, 6-25 default facility, 6-2 RW500 configuration, 6-35 default policies, 6-4 setting volume retention, default policy template, 6-4 6-12 default shelf, 6-2 specifying a device, 6-9 default volume, 6-3 TA90 configuration, 6-26 define archive classes, 6-8 TL820 configuration, 6-29 devices, 6-8 TZ877 configuration, 6-27 disk space, 4-3 initializing tape media, 6-10 installing, 5-1 mode comparison, 1-6 modes, 1-7 Index-2 HSM (cont'd) privileges, 4-4 L______________________________ restarting, 5-9 License shelf servers, 6-13 how to register, 4-6 software modes, 1-4 License types, 1-8 starting, 5-9 licenses stopping, 5-9 base, 1-8 template definitions, 6-15 capacity, 1-9 HSM Basic concurrent use, 1-10 configuration, 6-32 LNM$SLS$TABLE entries, E-3tbl functions, 1-5 LNM$SLS$VALUES entries robot name, 6-10 sample, E-3fig HSM installation LNM$SYSTEM_TABLE entries, overview, 1-17 E-1tbl HSM Plus Logical names, E-1tbl functions, 1-5 LNM$JOB, E-1 MDMS commands, 6-19 LNM$SLS$TABLE, E-1 MDMS configuration, 6-20 LNM$SLS$VALUES, E-3 offline environment, 6-17 LNM$SYSTEM_TABLE, E-1 HSM$DEFAULT_OCCUPANCY, 6-4 HSM$DEFAULT_POLICY, 6-4 M______________________________ HSM$DEFAULT_QUOTA, 6-4 Magazine HSM$STARTUP.COM, 5-9 configuration, 6-23 I Magneto-optical devices, 6-14 _______________________________ using as a shelf, 6-14 Initializing tape media, 6-10 Managing HSM environment installation online disk cache, 6-14 time estimates, 5-1 MDMS Installation adding volumes, 6-22 correcting problems, 4-5 authorizing volumes, 6-23 disk space, 4-3 commands, 6-19 MDMS, 3-1 configuration tasks, 6-20 privileges, 4-4 configuring magazines, 6-23 procedure, 3-1 importing jukebox volumes, system parameters, 4-4 6-23 user account quotas, 4-5 media triplet, 6-21 RDF-served devices, 6-25 J______________________________ services, 6-18 Jukebox MDMS client node, 3-8 configuration, 6-21 MDMS client node access importing magazines, 6-24 registering, 3-8 importing volumes, 6-24 Media triplets, 6-21 RW500, 6-35 MO devices, 6-14 Index-3 N______________________________ R______________________________ NFS, 7-1 RDF NFS ACCESS, 7-1 remote devices, 6-25 NFS logical names, 7-4 Release notes, 4-1 Node Remote backup operations, 3-25 shelf server, 6-13 Remote Device Facility server support, 3-25 O______________________________ Remote drives, 3-25 Optical devices configuring, 3-25 for cache, 6-14 Restarting HSM, 5-9 RW500, 6-35 Robot name, 6-10 Options for dedicating/sharing RW500 a device, 6-9 configuration, 6-35 P S______________________________ _______________________________ Server PAK initial configuration, 6-13 See Product Authorization Key Sharing devices, 6-9 PATHWORKS, 7-1, 7-3 Shelf PATHWORKS logical names, 7-4 authorizing servers, 6-13 Plus mode, 1-4 default, 6-2 see HSM Plus defining archive classes, Policy 6-8 changing defaults, 6-17 setting up, 6-7 default, 6-4 Shelf handler template definitions, 6-15 starting, 5-9 Policy definitions Shelf server default, 6-15 authorizing, 6-13 deleting, 6-17 Starting HSM, 5-9 Postinstallation Stopping HSM, 5-9 editing systemwide command Symbols files, 3-12 global, 3-12 editing the system login SYS$STARTUP_VMS.COM, 5-8 file, 3-12 SYSHUTDWN.COM, 5-9 Product Authorization Key System parameters registration, 4-6 (GBLSECTIONS), 4-4 System startup procedure, 3-12 Q______________________________ Quotas user account, 4-5 Index-4 TZ877 T______________________________ configuration, 6-27 TA90 configuration in Basic mode, configuration, 6-26 6-33 tape volumes initializing, 6-12 U______________________________ Tapes User account quotas, 4-5 jukeboxes, 6-21 volume initialization, 6-10 V______________________________ Template definitions VMSINSTAL, 4-4 policy, 6-15 Volume TL820 default attributes, 6-3 configuration, 6-29 retention, 6-12 RDF-served configuration, Volume retention 6-30 setting, 6-12 Index-5