Hierarchical Storage Management for OpenVMS Installation Guide Order Number: AA-QUJ1G-TE This manual contains installation information for HSM and Media and Device management Services (MDMS). Required Operating System OpenVMS V6.2 or higher Storage Library System for OpenVMS V2.9B or Required Software higher, or Media and Device Management Services for OpenVMS Version 2.9C, 2.9D or 3.0B DECnet (Phase IV) or DECnet-Plus (Phase V) TCP/IP Services for OpenVMS Revision/Update This manual replaces version AA-PWQ3J-TE. Information: Software Version: HSM Version 3.0A Compaq Computer Corporation Houston, Texas April, 2000 Possession, use, or copying of the software described in this documentation is authorized only pursuant to a valid written license from COMPAQ, an authorized sublicenser, or the identified licenser. While COMPAQ believes the information included in this publication is correct as of the date of publication, it is subject to change without notice. Compaq Computer 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. (c) Compaq Computer Corporation 2000. All Rights Reserved. Printed in the United States of America. COMPAQ, DIGITAL, DIGITAL UNIX, and the COMPAQ and DIGITAL logos Registered in U.S. Patent and Trademark Office. DECconnect, HSZ, StorageWorks, VMS, and OpenVMS are trademarks of Compaq Computer Corporation. AIX is registered trademark of International Business Machines Corporation. FTP Software is a trademark of FTP SOFTWARE, INC. HP is a registered trademark of Hewlett-Packard Company. NT is a trademark of Microsoft Corporation. Oracle, Oracle Rdb, and Oracle RMU are all registered trademarks of Oracle Corporation. PostScript is a registered trademark of Adobe Systems, Inc. RDF is a trademark of Touch Technologies, Inc. SGI is a registered trademark of Chemical Bank. Solaris is a registered trademark of Sun Microsystems, Inc. StorageTek is a registered trademark of Storage Technology Corporation. SunOS is a trademark of Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. Windows and Windows NT are both trademarks of Microsoft Corporation. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using Adobe FrameMaker Version 5.5. Preface vii Intended Audience vii Document Structure vii Related Documents viii Related Products viii Conventions ix Determining and Reporting Problems 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-1 1.4 What is the Purpose of a Managed Media & Device Environment? 1-2 1.5 Differences - HSM Basic& Plus Mode 1-3 1.5.1 HSM Basic Mode Functions 1-3 1.5.2 HSM Plus Mode Functions 1-3 1.5.3 HSM Mode Comparison Table 1-4 1.5.4 Choosing HSM Modes 1-5 1.5.5 HSM Mode Change Restrictions 1-5 1.6 HSM License Types 1-5 1.6.1 HSM Base Licenses 1-5 1.6.2 HSM Capacity Licenses 1-6 1.7 HSM Concurrent Use Licenses 1-7 1.8 Installation Changes when SLS is Present 1-7 1.9 HSM Upgrade Considerations 1-7 1.10 Backing HSM Up the Catalog 1-8 1.11 Backing up Your System Disk 1-8 1.12 VMScluster? System Considerations 1-8 1.13 Mixed Architecture Environments 1-9 1.13.1 Mixed Architecture Environments 1-9 1.13.2 Principles Guiding Mixed Architecture Configuration 1-10 1.13.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster 1-10 1.13.3.1 Separate Disk Configuration 1-10 1.13.3.2 Separate Root Configuration 1-11 1.13.3.3 Separate Subdirectory Configuration 1-11 1.13.4 Implementation Specific Approach 1-11 1.14 Overview of the HSM Installation Process 1-12 2 Installing MDMS Software 2.1 MDMS Pre-installation Tasks 2-1 2.1.1 Hardware and Software Requirements 2-2 2.1.2 Meet Patch Requirements 2-3 2.1.3 Install CMA Shareable Images 2-4 2.1.4 Shutdown Previous Version of MDMS 2-4 2.1.5 Register the MDMS License 2-4 2.1.6 Verify the Node is in the MDMS Database 2-5 2.1.7 Consider RDF Configuration 2-5 2.2 Installing the MDMS Software 2-6 2.3 MDMS Post-installation Tasks 2-6 2.3.1 Create a Node Object 2-7 2.3.2 Provide Automatic Start Up and Shut Down 2-7 2.3.3 Configure MDMS 2-7 2.3.4 Configure Remote Tape Drives 2-8 2.3.5 Grant MDMS Rights to Users 2-9 2.3.6 Installing the DCL Tables on Nodes 2-9 2.3.7 Using ABS/MDMS V2 Client Systems with MDMS V3 2-9 2.4 Graphical User Interface (GUI) Installation 2-9 2.4.1 Requirements 2-9 2.4.2 Installation on OpenVMS Alpha V7.1 and V7.2 2-10 2.4.3 Installation on Intel Windows NT/95/98 2-12 2.4.4 Installation on Alpha Windows NT 2-13 2.5 Running the GUI 2-13 2.5.1 Running the GUI on OpenVMS Alpha 2-14 2.5.2 Running the GUI on Intel Windows NT/95/98 2-14 2.5.3 Running the GUI on Alpha Windows NT 2-14 3 Meeting the HSM Installation Requirements 3.1 Read the Release Notes 3-1 3.2 Required Hardware Disk Space 3-1 3.3 Required Software 3-2 3.3.1 Required for HSM Basic Mode 3-2 3.3.2 Required for HSM Plus Mode 3-2 3.3.3 Required for HSM Repack Function 3-3 3.4 Required System Privileges 3-3 3.5 Required System Parameters 3-3 3.6 Required for VMSINSTAL 3-3 3.7 Installing DECthreads? Images 3-4 3.8 Registering Your HSM License 3-5 4 Installing HSM Software 4.1 Installing the HSM Software 4-1 4.1.1 The Installation Procedure 4-1 4.1.2 Error Recovery 4-4 4.2 After Installing HSM Software 4-5 4.3 Editing the System Startup and Shutdown Files 4-5 4.4 Creating an HSM Catalog 4-6 4.5 Installation Verification Procedure 4-6 5 Getting Started with HSM 5.1 HSM's Default Configuration 5-1 5.1.1 The Default Facility 5-1 5.1.2 The Default Shelf 5-2 5.1.3 The Default Device 5-2 5.1.4 The Default Volume 5-2 5.1.5 The Default Policies 5-3 5.2 Running HSM with the Default Configuration 5-3 5.2.1 Verifying the Facility Definition 5-4 5.2.2 Defining Archive Classes for Use 5-4 5.2.3 Selecting Archive Classes for the Default Shelf 5-5 5.2.4 Defining Devices for the Archive Classes 5-5 5.2.5 Initializing Tape Volumes for Each Archive Class 5-6 5.2.6 Set Volume Retention Times for Policy-Based Shelving 5-8 5.3 Additional Configuration Items 5-9 5.3.1 Authorizing Shelf Servers 5-9 5.3.2 Working with a Cache 5-9 5.3.3 An Example of Managing Online Disk Cache 5-10 5.3.4 Running Default Policies 5-10 5.3.5 Template Policy Definitions 5-10 5.3.5.1 Using a Template Policy Definition 5-10 5.3.5.2 Changing Default Policy Definitions 5-11 5.4 Plus Mode Offline Environment 5-12 5.4.1 How HSM Plus Mode and MDMS Work Together 5-12 5.4.2 How MDMS Supports HSM 5-12 5.4.3 MDMS Commands for HSM Plus Mode Use 5-12 5.4.4 MDMS Configuration Tasks Required to Support HSM Plus Mode 5-13 5.4.4.1 Defining Media Triplets 5-14 5.4.4.2 Defining Tape Jukeboxes 5-14 5.4.4.3 Adding Volumes to MDMS Database for HSM to Use 5-15 5.4.4.4 Authorizing HSM Access to Volumes 5-15 5.4.4.5 Importing Volumes Into a Jukebox 5-15 5.4.4.6 Configuring Magazines 5-15 5.4.4.7 Importing Magazines or Volumes Into the Jukebox 5-16 5.4.4.8 Working with RDF-served Devices in HSM Plus Mode 5-16 5.5 HSM Plus Mode Configuration Examples 5-17 5.5.1 Sample TA90 Configuration 5-17 5.5.2 Sample TZ877 Configuration 5-18 5.5.3 Sample TL820 Configuration 5-19 5.5.4 Sample RDF-served TL820 Configuration 5-20 5.5.4.1 Definitions on Client Node 5-20 5.5.4.2 Definitions on the RDF-served Node 5-21 5.6 HSM Basic Mode Configuration Examples 5-22 5.6.1 TZ877 Sample Configuration 5-22 5.6.2 RW500 Example 5-23 6 DFS, NFS, and PATHWORKS Access 6.1 DFS, NFS and PATHWORKS Access Support 6-1 6.1.1 DFS Access 6-1 6.1.2 NFS Access 6-1 6.1.3 PATHWORKS 6-2 6.1.4 New Logical Names for NFS and PATHWORKS Access 6-3 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 Rights and Privileges E.1 MDMS Rights - Types E-1 E.1.1 High Level Rights E-1 E.1.2 Low-level rights E-2 E.1.3 ABS Rights E-4 E.2 Default High-Level to Low-Level Mapping E-5 E.2.1 MDMS_USER: E-5 E.2.2 MDMS_OPERATOR Rights: E-6 E.2.2.1 Domain Commands for Mapping Privileges E-6 F MDMS Files and Logical Names F.1 MDMS File Names F-1 F.2 MDMS Logical Names F-3 G Sample Configuration of MDMS G.1 Configuration Order G-1 G.1.1 Configuration Step 1 Example - Defining Locations G-2 G.1.2 Configuration Step 2 Example - Defining Media Type G-2 G.1.3 Configuration Step 3 Example - Defining Domain Attributes G-2 G.1.4 Configuration Step 4 Example - Defining MDMS Database Nodes G-4 G.1.5 Configuration Step 5 Example - Defining a Client Node G-5 G.1.6 Configuration Step 6 Example - Creating a Jukebox G-5 G.1.7 Configuration Step 7 Example - Defining a Drive G-6 G.1.8 Configuration Step 8 Example - Defining Pools G-7 G.1.9 Configuration Step 9 Example - Defining Volumes using the /VISION qualifier G-7 Preface This document contains installation and configuration information about HSM for OpenVMS V3.0A. 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: * OpenVMS system management * 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 installation and configuration tasks. Chapter 3 Describes the HSM software and hardware requirements. Chapter 4 Describes the HSM installation tasks. Chapter 5 Describes the HSM configuration tasks in preparation for use. Chapter 6 Describes configuring the HSM environment for remote access through DFS, NFS, or PATHWORKS. Appendix AShows a sample HSM Basic mode installation. Appendix BShows a sample HSM Plus mode installation. Appendix CProvides a list of the HSM Logicals used. Appendix DProvides a list of the HSM File names. Appendix EProvides a list of the MDMS Logicals used. Appendix FProvides 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 Configuration Guide AA-QUJ1x-TE HSM for OpenVMS Guide to Operations AA-PWQ3x-TE HSM for OpenVMS Command Reference Guide AA-R8EXx-TE HSM for OpenVMS Software Product Description AE-PWNTx-TE HSM Hard Copy Documentation Kit (Consist of the above HSM documents and a cover letter) QA-0NXAA-GZ Storage Library System for OpenVMS Guide to Backup and Restore Operations AA-QHLEx-TE Storage Library System for OpenVMS Installation Guide AA-KY16x-TE OpenVMS System Management Utilities Reference Manual: A-L AA-PV5Px-TK OpenVMS DCL Dictionary: A-M AA-PV5Kx-TK OpenVMS DCL Dictionary: N-Z AA-PV5Lx-TK OpenVMS License Management Utility Manual AA-PVXUx-TK 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 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 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 type emphasizes important information, type indicates italic variables, indicates complete titles of manuals, and indicates parameters for system information. Starting This type font denotes system response, user input, and test . . . examples. Ctrl/x Hold down the key labeled Ctrl (Control) and the specified key simultaneously (such as Ctrl /Z). The key sequence PF1 x indicates that you press and release PF1 x the PF1 key, and then you press and release another key (indicated here by x). A lowercase italic n indicates the generic use of a number. n For example, 19nn indicates a four-digit number in which the last two digits are unknown. A lowercase italic x indicates the generic use of a letter. x For example, xxx indicates any combination of three alphabetic characters. OpenVMS AlphaThis term refers to the OpenVMS Alpha operating system. OpenVMS VAX This term refers to the OpenVMS VAX operating system. Determining and Reporting Problems If you encounter a problem while using HSM, report it to COMPAQ through your usual support channels. 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 COMPAQ for reporting SPD nonconformance problems. 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: * OpenVMS?, VAX? or Alpha systems * OpenVMS software Version 6.2 or higher for VAX and Alpha systems * Disk devices for online storage/transactions * DECnet? Phase IV or DECnet-Plus (Phase V) * Tape drives * 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: * Mixed architecture (a combination of VAX and Alpha systems) * Heterogeneous client systems (OpenVMS, NT, UNIX) * Types of tape drives (TLZ06, TZ877, and so forth) * Types of robotic devices (stackers/loaders/libraries) * Types of tape drive connections (direct-connect SCSI or controller-connected) * Location of tape drives (remote or local) * Number of disks * Number of tape drives * 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: * Limits on-line capacity to frequently used files, thus speeding access to current data. * Provides faster backups with less on-line data needing regular backup. * The backup-via-shelving capability reduces backup requirements up to 90%. * Storage administrators no longer need to manage disk capacity on a daily basis, since HSM monitors this for them. * Production applications won't fail due to "disk full" or "disk quota exceeded" exceptions because HSM prevents disks from filling up. * Allows you to customize your storage hierarchy according to your requirements. * The tape re-packing feature recovers shelf space on tapes used for deleted files or obsolete data. * The flexible management system lets you move files between disk volumes or systems without any unshelving. * The multi-file savesets feature provides full use of tape capacity and greatly increased shelving performance. * 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 & 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: * the drives that can use the media. * 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: * Media - are defined media types 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 (permitted users of these 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 start to be known as "volumes." 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. * 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 to select the appropriate tape drives determined by the media type. HSM storage classes associate these logical connections. * MDMS enables you to set the default criteria for moving and recycling volumes. These criteria include 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 recycle volumes. 1.5 Differences - HSM Basic& Plus Mode HSM software operates in one of two modes: * HSM Basic mode Provides shelving, preshelving, and unshelving functionality using simple devices, Digital Linear Tape (DLT) magazine loaders, and 4mm DAT loaders. * 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? silos. Except for the media and device management configuration and support, both modes operate identically. 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.5.1 HSM Basic Mode Functions HSM Basic mode provides the following functionality and features: * 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 * A simple, integrated user interface provided completely by HSM * Limited media management that is not integrated with other storage management products * Support of up to 36 archive classes for data reliability * An HSM naming convention for tape volume labels * Local tape device support within the VMScluster? 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: * 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 * Support for large capacity nearline devices that support multiple terabytes of data, such as the TL820 and StorageTek? silos * Common media management with other OpenVMS storage management products through the MDMS software * 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 * Support of up to 9999 archive classes for data reliability * No fixed naming conventions for HSM tape volumes; the Storage Administrator controls volume names through MDMS * Tape device support within the cluster: the shelf server nodes do not require direct visibility to all tape devices within the cluster * Support for remote tape devices, those that are not directly connected within the cluster, through the Remote Device Facility? (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 platforms VAX, Alpha VAX, Alpha Common media and device management with other Yes, through Digital storage products No MDMS Support for Digital Linear Tape (DLT) magazine loaders as robotically-controlled devices Yes Yes Support for TL81x, TL82x No Yes Maximum number of archive classes 36 9999 Requires specific HSM volume names Yes No Provides support for remote devices No Yes Uses a single, integrated interface for configuration and use Yes No 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 - Plus or Basic. Select Plus mode if: * You wish to have consolidated media management with other Storage Management products (e.g SLS, ABS...) * You are planning to use large multi-drive tape jukeboxes such as the TL81x, TL82x or StorageTek Silo * You are planning to use any kind of remote (RDF - accessed) tape drive * You wish to choose your tape volume labels, or use bar-coded volume labels Select Basic mode if: * You do not want consolidated media management, or are using an alternative media manager * You are not using large multi-drive tape jukeboxes (for example, you can use single-drive TZ8xx loaders in either mode) * 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. 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: * You can always change from Basic mode to Plus mode. * 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. * 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: * HSM Base licenses * HSM Capacity licenses * 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, its 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 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 ClusterQL-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. Compaq 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 The * in the above table means that these additional capacity licenses also include the base license for VAX clusters, Alpha clusters, and mixed-architecture clusters. 1.7 HSM Concurrent Use Licenses In addition to the HSM Capacity licenses, Compaq 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 LicenseQL-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 override the MDMS software running under SLS and cause SLS to lose some functionality. See the Caution note that follows. 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.9 HSM Upgrade Considerations If you are installing HSM V3.0A on an Alpha running OpenVMS 7.2 you will be installing the latest HSDRIVER. If you are upgrading from HSM V2.x, (on Alpha/VAX systems running Open VMS versions below 7.2), please note that though the HSDRIVER provided in this kit, is the latest version, you need not reboot your systems after installation in order to run HSM V3.0.A Do not run HSM V3.0A with the HSM V1.x driver installed. Doing so may crash your system. The additional tasks you must perform are described below: 1. 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. 2. If you are upgrading from a lower HSM V2.x version to HSM V3.0A, you do not have to reboot your system right after HSM installation. You may operate HSM V3.0A 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. 3. The format of the HSM catalog and the SMU databases found in HSM$MANAGER have changed for HSM Version 3.0 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, Compaq strongly recommends you back up the existing catalog and SMU databases before you install HSM Version 3.0 software. The catalog is located at: HSM$CATALOG:HSM$CATALOG.SYS and the SMU databases at: HSM$MANAGER:*.SMU. 1. 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 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. Compaq 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: * Reinstall DCLTABLES on all nodes in the VMScluster? system. * 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. * Because HSM creates new DCL command verbs, all system users need to log out and log in again to see those verbs. * 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.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: 1.13.1 Mixed Architecture Environments 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. 1.13.2 Principles Guiding Mixed Architecture Configuration lists the guiding principles that require you to make special considerations for mixed architecture implementation, and what these principles mean to you. 1.13.3 Configuring Applications in a Mixed Architecture OpenVMS Cluster describes three possible approaches to implementing a mixed architecture environment. 1.13.4 Implementation Specific Approach 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. 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 heterogeneous 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. 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: * All shared files reside in one location * All files that cannot be shared reside in separate locations 1.13.3.1 Separate Disk Configuration These characteristics describe the separate disk configuration: * Product directories are installed on two separate disks. * 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. * 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. * The systems using the disk with the complete installation uses logicals that normally reference the product executables and shared files. * 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. 1.13.3.2 Separate Root Configuration These characteristics describe the separate root configuration: * Product directories are installed on the same disk, but at different root locations. * 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. * 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. * The systems using the directory with the complete installation uses logicals that normally reference the product executables and shared files. * 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: * Product directories are installed on the same disk, and under the same root. * 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. * 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.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 process 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.To make sure you go through the installation process properly, you could use the `Check-Off' column in Table 1-5 HSM Installation and Configuration. Table 1-5 HSM Installation and Configuration Step Task Reference Check-off 1. Check for HSM - Required Software, Space and See Required Software Privileges 1. 2. Required for HSM Basic 3.3.1 Required for HSM Mode Basic Mode 1. 3. Required for HSM Plus Mode 3.3.2 Required for HSM Plus Mode 1. 4. Required for HSM Repack 3.3.3 Required for HSM Function Repack Function 1. 5. Required Hardware Disk 3.2 Required Hardware Space Disk Space 1. 6. Required System Privileges 3.4 Required System Privileges 1. 7. Required System Parameters 3.5 Required System Parameters 1. 8. Required for VMSINSTAL 3.6 Required for VMSINSTAL 1. 9. Installing DECthreads 3.7 Installing DECthreads Images Images 1. 10. Registering your HSM 3.8 Registering Your HSM License License 1. 11. Installing the HSM 4.1 Installing the HSM Software Software 4.3 Editing the System 1. 12. Editing the System Startup Startup and Shutdown and Shutdown Files Files 1. 13. Creating an HSM Catalog 4.4 Creating an HSM Catalog 1. 14. Installation Verification 4.5 Installation Procedure Verification Procedure 1. 15. Getting Started with HSM Chapter 5 1. 16. MDMS Pre-installation 2.1 MDMS Pre-installation Tasks Tasks 1. 17. Installing the MDMS 2.2 Installing the MDMS Software Software 1. 18. MDMS Post-installation 2.3 MDMS Tasks Post-installation Tasks Graphical User 2.4 Graphical User 1. 19. Interface(GUI) Interface(GUI) Installation Installation 1. 20. Running the GUI 2.5 Running the GUI 1. 21. Hardware and Software 2.1.1 Hardware and Requirements Software Requirements 1. 22. Meet Patch Requirements 2.1.2 Meet Patch Requirements 1. 23. Install CMA Shareable 2.1.3 Install CMA Images Shareable Images 1. 24. Shutdown Previous Version 2.1.4 Shutdown Previous of MDMS Version of MDMS 1. 25. Shutdown Previous Version 2.1.5 Register the MDMS of MDMS License 1. 26. Register the MDMS License 2.1.5 Register the MDMS License 1. 27. Verify the Node is in the 2.1.6 Verify the Node is MDMS Database in the MDMS Database 1. 28. Consider RDF Configuration 2.1.7 Consider RDF Configuration 1. 29. Create a Node Object 2.3.1 Create a Node Object 1. 30. Provide Automatic Start Up 2.3.2 Provide Automatic and Shut Down Start Up and Shut Down 1. 31. Remove SLS/MDMS V2.x 2.3.3 Remove SLS/MDMS Automatic Startup V2.x Automatic Startup 1. 32. Configure MDMS 2.3.4 Configure MDMS 1. 33. Configure Remote Tape 2.3.5 Configure Remote Drives Tape Drives 1. 34. Grant MDMS Rights to Users 2.3.6 Grant MDMS Rights to Users 1. 35. Installing the DCL tables 2.3.7 Installing the DCL on Nodes tables on Nodes 2.4.2 Installation on 1. 36. Installation on OpenVMS OpenVMS Alpha V7.1 and Alpha V7.1 and 7.2 V7.2 1. 37. Installation on Intel 2.5.2 Running the GUI on Windows NT/95/98 Intel Windows NT/95/98 1. 38. Installation on Alpha 2.4.4 Installation on Windows NT Alpha Windows NT 1. 39. Running the GUI on OpenVMS 2.5.1 Running the GUI on Alpha OpenVMS Alpha 1. 40. Running the GUI on Intel 2.5.2 Running the GUI on Windows NT/95/98 Intel Windows NT/95/98 1. 41. Running the GUI on Alpha 2.5.3 Running the GUI on Windows NT Alpha Windows NT 2 Installing MDMS Software This chapter explains how to install the Media and Device Management Services (MDMS) Version 3.0B software. The sections in this chapter cover the three procedures involved in installing the software, namely: * pre-installation tasks * installation * post-installation tasks If this is the initial installation of MDMS you should install MDMS on a node that is going to be one of your MDMS database server nodes. You may want to read the MDMS configuration chapters in the Guide to Operations to make better decisions when installing MDMS. This version of MDMS installs the system executable files into system specific directories. Because of this, there is no special consideration for mixed architecture OpenVMS cluster system installations. At a minimum, you will install MDMS twice in a mixed architecture OpenVMS Cluster system, once on an OpenVMS Alpha node and once on an OpenVMS VAX node. If you are installing MDMS with the ABS-OMT license, the following features of MDMS are not available: * Support of remote devices through the Remote Device Facility (RDF) * Support of DCSC-controlled StorageTek (r) silos 2.1 MDMS Pre-installation Tasks The following table lists out exactly which section describes the particular pre-installation task, to help you ensure that the installation takes place correctly. Table 2-1 MDMS Pre-installation Tasks Action Section Meet hardware and software See Hardware and Software requirements Requirements Meet prerequisite patches requirements See Meet Patch Requirements Install CMA shareable images See Install CMA Shareable Images Shutdown previous version of MDMS See Shutdown Previous Version of MDMS Register the MDMS License See Register the MDMS License Verify the Node is in the MDMS See Verify the Node is in the MDMS Database Database Consider RDF Configuration See Consider RDF Configuration 2.1.1 Hardware and Software Requirements MDMS's free disk space requirements differ during installation (peak utilization) and after installation (net utilization). As a pre-installation step please make sure that the required space is available during and post-installation respectively. See Disk Space Requirements shows the different space requirements. Table 2-2 Disk Space Requirements If you are Installing the Kit You will need 102,000 (Alpha), 44,000 (VAX) peak blocks during installation MDMS Complete Kit 90,000 (Alpha), 33,000 (VAX) net blocks after installation (permanent) 11,000 (Alpha), 5,000 (VAX) peak blocks during installation Minimal Kit 3,000 net blocks after installation (permanent) The installation variants require disk space as follows: Table 2-3 Installation Variants Variant Peak Alpha Net Alpha Peak VAXNet VAX MDMS Basic Kit (Minimal) 11,000 3,000 5,000 3,000 Remote Device Facility 11,000 7,000 11,000 2,000 OpenVMS GUI (Alpha only) 12,000 12,000 N/A N/A Intel NT/95/98 GUI 12,000 12,000 12,000 12,000 Alpha NT GUI 16,000 16,000 16,000 16,000 OpenVMS Java Kit (Alpha only) 40,000 40,000 N/A N/A Complete kit with all options selected 102,000 90,000 44,000 33,000 The files for MDMS are placed in two locations: * system disk: for executables * MDMS$ROOT: for * Command procedures * Log files * Database files * GUI files for all three platforms If disk space is an issue, it is advisable to place MDMS$ROOT: on a disk other than your system disk because MDMS creates log files that can grow quite large. OpenVMS V6.2 is the minimum version of software necessary to run MDMS. OpenVMS V7.1 Alpha is the minimum version of software on which to run the OpenVMS GUI. The GUI does not run on VAX systems. The GUI requires the availability of TCP/IP on all platforms. 2.1.2 Meet Patch Requirements See Prerequisite Patches describes the patch requirements for MDMS: Table 2-4 Prerequisite Patches Component Operating System Version Patch MDMS$SERVEROpenVMS Alpha V6.2 ALPY2K_062 OpenVMS VAX V6.2 VAXLIBR06_070 GUI OpenVMS Alpha V7.1 to V7.1-H2 ALPBASE02_071 V7.1 to V7.1-H2 ALPACRT06_071 V7.1 to V7.1-H2 ALPDCL01_071 V7.1 to V7.1-H2 ALPSYSA01_071 V7.1 to V7.1-H2 ALPSYSB02_071 V7.1 to V7.1-H2 ALPTHREADS_03071 V7.1-2 ONLY VMS712_PTHREADS If the server patches are not installed, you will see the following error while trying to start the server: 09-Mar-1999 10:38:16 %MDMS-I-TEXT, "10k Day" patch not installed! You can obtain these patches or the latest revision by contacting your Compaq representative. If the patches for the MDMS$SERVER are not installed, the server will not start but you can successfully install MDMS, then install the patches and start the server. 2.1.3 Install CMA Shareable Images If you are installing MDMS on an OpenVMS V6.2 VAX system, you have to install the following three files: * SYS$COMMON:[SYSLIB]CMA$RTL * SYS$COMMON:[SYSLIB]CMA$OPEN_RTL * SYS$COMMON:[SYSLIB]CMA$LIB_SHR If these images are not installed by default, include the following lines in the SYS$STARTUP:SYSTARTUP_VMS.COM: $! $! Install CMA stuff for MDMS $! $ INSTALL = "$INSTALL/COMMAND_MODE" $ IF .NOT. F$FILE_ATTRIBUTES("SYS$COMMON:[SYSLIB]CMA$RTL.EXE", "KNOWN") $ THEN - $ INSTALL ADD SYS$COMMON:[SYSLIB]CMA$RTL $ ENDIF $ IF .NOT. F$FILE_ATTRIBUTES("SYS$COMMON:[SYSLIB]CMA$OPEN_RTL.EXE", "KNOWN") $ THEN $ INSTALL ADD SYS$COMMON:[SYSLIB]CMA$OPEN_RTL $ ENDIF $ IF .NOT. F$FILE_ATTRIBUTES("SYS$COMMON:[SYSLIB]CMA$LIB_SHR.EXE", "KNOWN") $ THEN $ INSTALL ADD SYS$COMMON:[SYSLIB]CMA$LIB_SHR $ ENDIF 2.1.4 Shutdown Previous Version of MDMS If you have been running a version of MDMS prior to Version 3.0, you must shut it down using the following command: $ @SLS$SYSTEM:SLS$SHUTDOWN If you are using MDMS V3.0 or later, use the following command to shut down MDMS: $ @SYS$STARTUP:MDMS$SHUTDOWN 2.1.5 Register the MDMS License As MDMS does not have a separate license, you need one of the following licenses to run MDMS: * ABS-CLIENT-ALPHA * ABS-CLIENT-VAX * ABS-OMT * ABS-OMT-UPG * ABS-SERVER-ALPHA * ABS-SERVER-VAX * HSM-SERVER * SLS * SLS-MGR * SLS-REMOTE * SLS-REMOTE-MGR If you do not have one of these licenses registered, please refer to the section on registering the license for ABS or HSM whichever you are installing. 2.1.6 Verify the Node is in the MDMS Database If this installation is not the initial installation of MDMS, you need to verify that the node you are installing MDMS on is in the MDMS database. Enter the following command on a node that has MDMS already installed on it and verify that the node you are installing MDMS on is in the database: $ MDMS SHOW NODE node_name_you_are_installing_on %MDMS-E-NOSUCHOBJECT, specified object does not exist If the node is not in the database, you receive the %MDMS-E-NOSUCHOBJECT error message and you should create the node using the following command: $ MDMS CREATE NODE node_name_you_are_installing_on See the Command Reference Guide for the qualifiers to use. If the node you are adding is an MDMS server node, the installation procedure will create the node using the /DATABASE qualifier. In addition, you need to edit all SYS$STARTUP:MDMS$SYSTARTUP.COM files in your domain and add this node to the definition of MDMS$DATABASE_SERVERS. 2.1.7 Consider RDF Configuration MDMS provides RDF software to facilitate operations that require access to remote, network connected tape drives. This allows you to copy data from a local site to a remote site, or copy data from a remote site to a local site. RDF is not available if you are installing MDMS with the ABS-OMT license. During the installation you will be asked questions on whether you want to install on this node, the software that will allow it to act as a server and/or client for the RDF software. You need to decide if you want the server and/or client installed on the node. * Install the RDF Server software on all nodes that are connected to the tape drives used for remote operations. * Install the RDF Client software on all nodes that initiate remote operations to tape drives on the RDF Server node. After installing RDF you may have to reboot your system. A new driver is included with this kit. If you have never installed RDF before a reboot is not needed. If you already have RDF installed, you do not need to reboot unless you need the new driver installed. It will be installed on the next reboot. 2.2 Installing the MDMS Software The MDMS installation procedure consists of a series of questions and informational messages. Once you start the installation procedure, it presents you with a variety of questions that will change depending on whether the installation is the first or a subsequent installation. The installation procedure provides detailed information about the decisions you will make. 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 exits. Note that you can restart the installation procedure from this point, at any time. Be sure to read See Graphical User Interface (GUI) Installation for information on selecting GUI kits to be extracted from the saveset during this installation. To install MDMS: 1. Load the distribution medium into a suitable device, and mount the volume 1. 2. Invoke the VMSINSTAL procedure using the following command: $ @SYS$UPDATE:VMSINSTAL MDMSB030 location: OPTIONS N Where: location: is the device and directory that contains the software kit save set. OPTIONS: N is an optional parameter that indicates you want to see the question on Release Notes. If you do not include the OPTIONS:N parameter, VMSINSTAL does not ask you about the Release Notes. You should review the Release Notes before proceeding with the installation in case they contain additional information about the installation procedure. Follow the instructions as you are prompted to complete the installation. Each question you are asked is provided with alternatives for the decision you can take and an explanation for the related decision. Questions and decisions offered by the installation procedure vary. Subsequent installations will not prompt you for information you provided during the first installation. 2.3 MDMS Post-installation Tasks The following sections describe the post-installation tasks needed after installing the MDMS: Table 2-5 Post-Installation Tasks Action Section Create a Node Object See Create a Node Object Provide Automatic Start Up and See Provide Automatic Start Up and Shut Down Shut Down Remove SLS/MDMS V2.x Automatic See Provide Automatic Start Up and Startup Shut Down Configure MDMS See Configure MDMS Configure remote tape drives See Configure Remote Tape Drives Grant MDMS Rights to Users See Grant MDMS Rights to Users Installing the DCL tables on Nodes See Installing the DCL Tables on Nodes 2.3.1 Create a Node Object If this is the initial installation of MDMS, you may need to create the node object in the MDMS node database for this node. Use the MDMS CREATE NODE command to create this initial database node. Refer to the Command Reference Guide for the qualifiers for this command. The following is an example: $ MDMS CREATE NODE NABORS - ! NABORS is the DECnet Phase IV node name or a ! name you make up if you do not use DECnet ! Phase IV in your network /DATABASE_SERVER - ! a potential database node ! must also be defined in ! in SYS$STARTUP:MDMS$SYSTARTUP.COM /TCPIP_FULLNAME=NABORS.SITE.INC.COM - ! the TCP/IP full node name if you ! are using TCP/IP you need this if ! you are using the GUI /DECNET_FULLNAME=INC:.SITE.NABORS - ! this is the full DECnet Phase V node name ! do not define if you do not have DECnet Phase V on this node ! be sure to define if you have DECnet Phase V installed on this node /TRANSPORT=(DECNET,TCPIP) ! describes the transports that listeners are ! started up on 2.3.2 Provide Automatic Start Up and Shut Down To automatically start MDMS when you initiate a system start up, at a location after the DECnet or TCP/IP start up command, add the following line in the system's start up file, SYS$MANAGER:SYSTARTUP_VMS.COM: $ @SYS$STARTUP:MDMS$STARTUP To automatically stop MDMS when you initiate a system shut down, enter the following into the system's shut down file: $ @SYS$STARTUP:MDMS$SHUTDOWN While using MDMS with ABS, make sure that MDMS startup is executed prior to ABS startup. ABS needs a logical name that is defined by the MDMS startup. 2.3.3 Configure MDMS Now that you have installed MDMS you need to configure MDMS by creating the following objects: * Media types * Locations * Nodes * Groups * Jukeboxes * Tape Drives * Magazines * Pools * Volumes Please refer to the MDMS section in the Guide to Operations for more information on configuration and operation. If you are upgrading from SLS/MDMS V2.x you can convert the SLS/MDMS V2.x symbols and database to the MDMS V3 database. Use the procedures described in the Guide to Operations See Converting SLS/MDMS V2.X Symbols and Database. 2.3.4 Configure Remote Tape Drives If you installed the RDF software, you need to configure the remote tape drives. RDF is not available if you are installing MDMS with the ABS-OMT license. For each tape drive served with RDF Server software, make sure there is a drive object record in the MDMS database that describes it. Refer to the chapters on MDMS configuration in the Guide to Operations and the MDMS CREATE DRIVE command in the Command Reference Guide. For each node connected to the tape drive, edit the file TTI_RDEV:CONFIG_node.DAT and make sure that all tape drives are represented in the file. The syntax for representing tape drives is given in the file. During startup of MDMS, the RDF client and server are also started. The RDF images are linked on your system. If you see the following link errors on Alpha V6.2, this is not an RDF bug. The problem is caused by installed VMS patches ALPCOMPAT_062 and ALPCLUSIO01_062. %LINK-I-DATMISMCH, creation date of 11-FEB-1997 15:16 in shareable image SYS$COMMON:[SYSLIB]DISMNTSHR.EXE;3 differs from date of 4-MAY-1995 22:33 in shareable image library SYS$COMMON:[SYSLIB]IMAGELIB.OLB;1 . . . This is a known problem and is documented in TIMA. To correct the problem, issue the following DCL commands: $ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:DISMNTSHR.EXE $ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:INIT$SHR.EXE $ LIBRARY/REPLACE/SHARE SYS$LIBRARY:IMAGELIB.OLB SYS$SHARE:MOUNTSHR.EXE 2.3.5 Grant MDMS Rights to Users Before any user can use MDMS, you must grant MDMS rights to those users. Refer to the MDMS Rights and Privileges Appendix in the HSM or ABS for OpenVMS Command Reference Guide for explanation of MDMS rights and how to assign them. 2.3.6 Installing the DCL Tables on Nodes To make MDMS commands available on all nodes of the cluster, you should ensure that all nodes have the latest version of DCLTABLES.EXE installed. You can do this by using SYSMAN or by logging into each node in the cluster and enter the following command: $ INSTALL REPLACE SYS$COMMON:[SYSLIB]DCLTABLES.EXE 2.3.7 Using ABS/MDMS V2 Client Systems with MDMS V3 In order to support rolling upgrades of ABS, HSM and MDMS across the domain, an MDMS V3 database server can support client nodes running SLS/MDMS V2.x. Refer to the Guide to Operations Appendix section "Using SLS/MDMS V2.x Clients with the MDMS V3 Database" for information on how to set upthis environment. Once all nodes in your domain have been upgraded to use MDMS V3, then remove the following line from your system's start-up file: $ @SYS$STARTUP:SLS$STARTUP 2.4 Graphical User Interface (GUI) Installation This section describes how to install and run the Graphical User Interface (GUI) on various platforms. As the GUI is based on Java, you must have the Java virtual machine installed on the system you run the MDMS GUI on. If you do not have Java installed on your system, these sections describe what is needed and where to get it. This installation procedure extracts files from the MDMS kit and places them in MDMS$ROOT:[GUI...]. You can then move the files to your Windows system and install them. For the GUI to communicate with the MDMS server, you must have TCP/IP services on the node where you have the MDMS server running. After installation be sure to refer to See Graphical User Interface (GUI) Installation, to run the GUI. 2.4.1 Requirements The GUI requires the following in order to run: Virtual Machine Since the MDMS GUI is a Java application, it requires the platform specific Java Virtual Machine. The availability of each Java Virtual Machine is described in the following sections. The best way of getting a Java Virtual Machine is to down load the platform-specific kit from the given URLs. If this is not possible, the MDMS package also contains a copy for your convenience. Issues concerning availability and installation of the Java Virtual Machine can be directed to: http://www.sun.com/java/products for Windows NT and http://www.digital.com/java/download/jdk_ovms/1.1.8/index.html for OpenVMS A Java Virtual Machine is included in this MDMS kit for the purpose of completeness. MDMS provides both the pointers (URLs) of downloading a Java Virtual Machine and the actual files of the Java Virtual Machine in the release package. However, the downloading approach is encouraged. Memory The hard drive space requirement is 6 MB for Java Virtual Machine and 2 MB for MDMS GUI. The main memory space requirement for running MDMS GUI is 10 MB. 2.4.2 Installation on OpenVMS Alpha V7.1 and V7.2 The following steps describe how to install and run the MDMS GUI on OpenVMS Alpha: 1. If you are installing the GUI on OpenVMS Alpha V7.1, then the following patches (or their latest equivalent) need to be installed on the system. Please contact your Compaq representative for obtaining these patches. Table 2-6 Patches Required for OpenVMS V7.1 for JAVA Patch Required For OpenVMS Fix Description Version ALPBASE02_071 V7.1 to Fixes needed to enable ALPACRT06_071 and V7.1-H2 ALPSYSA01_071. Must be installed first. ALPACRT06_071 V7.1 to DECC fixes-fork, exec V7.1-H2 ALPDCL01_071 V7.1 to Fixes for multiple kernel threading V7.1-H2 problem. ALPSYSA01_071 V7.1 to Higher-priority thread blocking V7.1-H2 ALPSYSB02_071 V7.1 to IEEE arithmetic V7.1-H2 ALPTHREADS_03071 V7.1 to DECthreads; support for Java, selected V7.1-H2 fixes VMS712_PTHREADS V7.1-2 ONLY DECthreads; support for Java, selected fixes These patches are not required for installation on OpenVMS Alpha V7.2. 1. 2. Extract the files for the OpenVMS Java Virtual Machine. You may use the Java kit provided with the MDMS kit or download files from the Web. If you want to install from the MDMS kit, answer YES to the following question: Do you want the OpenVMS Java kit extracted [NO]? If you install from the MDMS kit, a file called: MDMS$ROOT:[GUI.VMS]DEC-AXPVMS-JAVA-V0101-81-1.PCSI_DCX_AXPEXE is created. Use this file to install Java as in step 4. 1. 3. In the MDMS installation, the following question is asked. Do you want the MDMS GUI installed on Alpha OpenVMS [YES]? Reply `Yes' to the question if you want to install the GUI on OpenVMS. Files will be moved to MDMS$ROOT:[GUI.VMS] and the GUI installation will be completed. 1. 4. Following the MDMS installation, you should install Java by first extracting the PCSI file for the Java installation using the following commands: $ SET DEFAULT MDMS$ROOT:[GUI.VMS] $ RUN DEC-AXPVMS-JAVA-V0101-81-1.PCSI_DCX_AXPEXE Extract and read the Release Notes for additional information on how to use this product in an OpenVMS environment: $ PRODUCT EXTRACT RELEASE_NOTES JAVA- /SOURCE=[directory_where_you_put_the_PCSI_file]- /FILE=[directory_where_you_want_it]JDK118_VMS_RELEASE_NOTES.HTML- /BASE_SYSTEM=AXPVMS Install the JDK1.1.8 from the .PCSI file obtained: $ PRODUCT INSTALL JAVA- /SOURCE=[directory_where_you_put_the_PCSI_file]/BASE_SYSTEM=AXPVMS The following files are installed by PCSI (POLYCENTER Software Installation utility) with file attribute of ARCHIVE: SYS$MANAGER:JAVA$SETUP.COM SYS$MANAGER:JAVA$STARTUP.COM SYS$SYSROOT:[JAVA.LIB]FONT.PROPERTIES SYS$SYSROOT:[JAVA.LIB]FONT_PROPERTIES.JA If a file having any of these names already exists on the system, the installation process renames it to a new name with the file type ending `_OLD', before loading the new copy from the kit. Only the latest version of the existing file is preserved (by being renamed to file.type_old) before PCSI deletes all remaining versions. For example, an existing SYS$MANAGER:JAVA$SETUP.COM is renamed to SYS$MANAGER:JAVA$SETUP.COM_OLD before the new copy is copied from the kit. If you have previously personalized any of these files, you might need to merge your personalizations with the new copy. The JDK documentation is installed on your system at the following location: SYS$COMMON:[SYSHLP.JAVA]INDEX.HTML 1. 5. After installation you must do the following: $ EDIT SYS$STARTUP:JAVA$SETUP.COM and include the following logical name definition at the end of the file: $ DEFINE JAVA$CLASSPATH - MDMS$ROOT:[GUI.VMS]MDMS.ZIP,- MDMS$ROOT:[GUI.VMS]SYMANTEC.ZIP, - MDMS$ROOT:[GUI.VMS]SWINGALL.JAR, - SYS$COMMON:[JAVA.LIB]JDK118_CLASSES.ZIP, [-] 1. 6. Run JAVA$SETUP.COM to establish defaults for the logical names CLASSPATH and JAVA$FILENAME_CONTROLS, and to define symbols that determine whether Java will interpret commands as either foreign commands or DCL commands: $ @SYS$MANAGER:JAVA$SETUP.COM Add the above command line to SYS$COMMON:[SYSMGR]SYLOGIN.COM so that when users login, they will have the Java definitions. Make sure that the logical JAVA$USE_DCL is not defined or the GUI will not work. 1. 7. The JAVA$SETUP.COM procedure calls: SYS$SYSROOT:[SYSHLP.JAVA]JAVA$FILENAME_CONTROLS.COM to establish the JAVA$FILENAME_CONTROLS default values. You can edit this file to see what defaults are being used and how to change them. (This information is also in the "UNIX Style Filenames on an OpenVMS System" section of the JDK release notes.) 1. 8. Rename the file SYS$COMMON:[JAVA.LIB]FONT.PROPERTIES to another name. This file remaps the fonts and makes the MDMS GUI appear incorrect. Renaming the file to another name will cause Java to use the default fonts, which are necessary to run the MDMS GUI. 2. 9. If you are running the GUI using a non-PC keyboard, for example an OpenVMS keyboard, issue the following command on the system running the GUI: $ MCR decw$utils:xmodmap -e "keysym Delete = BackSpace Delete" Note that this command affects all DECwindows sessions. In order to get the proper operation on both the GUI session and other DECwindows sessions, the following sequence should be employed: $ MCR decw$utils:xmodmap -e "keysym Delete = BackSpace Delete" $ MDMS/INTERFACE=GUI $ MCR decw$utils:xmodmap -e "keysym Delete = Delete" This resets the behavior of all the other windows to normal while the Java GUI still retains the earlier definition. This way, both the GUI and the other DECwindows can co-exist, both retaining the required functionality. 1. 10. The Java kit and MDMS GUI are provided in zipped files. The Java Virtual Machine is capable of reading zipped files directly. Do not unzip any of the zipped files provided with the GUI. 2.4.3 Installation on Intel Windows NT/95/98 The following describes how to install the MDMS GUI on Intel platforms running Windows NT/ 95/98: 1. In the MDMS installation, the following question is asked. Do you want files extracted for Microsoft Windows NT/95/98 on Intel [YES]? Reply YES if you want to install the GUI on Intel Windows NT/95/98. 1. 2. Install the Java Virtual Machine - If Java Virtual Machine is not already installed on your PC, down load JRE 1.1.8 from: http://www.javasoft.com/products/jdk/1.1/jre or http://www.sun.com/developers/developers.html and follow the instructions to perform a default installation. You may use other versions of JRE, preferably 1.1.8 or later. If a Java Virtual Machine is not available, you may use MDMS$ROOT:[GUI.INTEL]JRE117WINTEL.EXE. Simply double-click on this file to install Java, and follow the setup instructions. 1. 3. Install the MDMS GUI: Make MDMS$ROOT:[GUI.INTEL]SETUP_INTEL.EXE available to the target machine (Intel PC running Windows NT/95/98) Run SETUP_INTEL.EXE on the target machine. 2.4.4 Installation on Alpha Windows NT The following describes how to install the MDMS GUI on an Alpha platform running Windows NT: 1. In the MDMS installation, the following question is asked. Reply YES if you want to install the GUI on Alpha NT. Do you want the MDMS GUI files extracted for Alpha NT [YES] ? 1. 2. Install the Java Virtual Machine - If Java Virtual Machine is not already installed on your Alpha, down load JRE 1.1.8 from: http://www.digital.com/java/download/jre_nt/1.1.8/jre118_down.html and follow the instruction to perform a default installation. If a Java Virtual Machine is not available, you may use: MDMS$ROOT:[GUI.ALPHA_NT]JRE118ALPHANT.EXE. 1. 3. Install FX!32 if not installed and make sure FX!32 is enabled. 2. 4. Install the MDMS GUI: 3. Make MDMS$ROOT:[GUI.ALPHA_NT]SETUP_ALPHA_NT.EXE available to the target machine (Alpha PC running Windows NT) 4. Run SETUP_ALPHA_NT.EXE on the target machine. 5. If the 'Unzip To' folder has been modified to anything other than default directory, remember to modify the MDMS_GUI.BAT. 2.5 Running the GUI Now that you have installed the GUI, you have to make sure the server node is configured to accept communications from the GUI. The server node for the GUI must have: * TCP/IP enabled and * the MDMS rights enabled in the SYSUAF record for the user To enable TCP/IP communications on the server, you have to set the TCP/IP Fullname attribute and enable the TCPIP transport. See the Command Reference Guide for information about setting these attributes in a node. MDMS rights for the user must be enabled in the SYSUAF record to log into the server using the GUI. Refer to the Command Reference Guide for information about MDMS rights. The following sections describe how to run the GUI on various platforms. 2.5.1 Running the GUI on OpenVMS Alpha To use the MDMS GUI on OpenVMS Alpha systems, use the following commands: $ @SYS$STARTUP:JAVA$SETUP.COM $ SET DISPLAY/CREATE/NODE=node_name/TRANSPORT=transport $ MDMS/INTERFACE=GUI For the SET DISPLAY command, the node_name is the name of the node on which the monitor screen exists. This allows you to use the GUI on systems other than those running OpenVMS Alpha V7.1 or higher. The transport must be a keyword of: * LOCAL - if you are running the GUI on the same node as the monitor * DECNET - if you are running the GUI on a monitor connected to another node and you wish to use DECnet protocol between the monitor node and the GUI Java node. * TCPIP - if you are running the GUI on a monitor connected to another node and you wish to use TCPIP protocol between the monitor node and the GUI Java node. 2.5.2 Running the GUI on Intel Windows NT/95/98 To use the MDMS GUI on Intel Windows NT/95/98 platforms, double click MDMS_GUI\MDMS_GUI.BAT. 2.5.3 Running the GUI on Alpha Windows NT To use the MDMS GUI on Alpha Windows NT, do one the following: 1. If both the Java Virtual Machine and the MDMS GUI were installed with default selection, then double click MDMS_GUI\MDMS_GUI.BAT 1. 2. Otherwise in MDMS_GUI\MDMS_GUI.bat, replace the Java Virtual Machine directory and MDMS_GUI directory as necessary, double click MDMS_GUI\MDMS_GUI.BAT. 3 Meeting the HSM Installation Requirements This chapter enlists requirements to be met before installing the HSM software. Go through the following list before you begin installation. Requirements List The requirements list to meet before installing HSM software is as follows: * Read the HSM Software Release Notes * Required Software * Requirements for HSM Basic Mode * Requirements for HSM Plus Mode * Requirements for HSM Repack Function * Required Hardware Disk Space * Required System Privileges * Required System Parameters * Required for VMSINSTAL * Installing DECthreads? Images * Registering your HSM Licence 3.1 Read the Release Notes The HSM kit includes online release notes. Compaq strongly recommends that you read the release notes before proceeding with the installation. The release notes are in a text file named SYS$HELP:HSM30.RELEASE_NOTES and a Postscript (r) file named SYS$HELP:HSM30_RELEASE_NOTES.PS. 3.2 Required Hardware Disk Space See Disk Space Requirementssummarizes the disk space requirements for installing and running HSM. Table 3-1 Disk Space Requirements Item Blocks Needed Description Install 28,000 Temporary blocks for Kit HSM Software16,000 Permanent blocks for software Catalog grows at the average rate of 1.25 Catalog 100,000 blocks for each file copy shelved. Compaq 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: $ SHOW DEVICE SYS$SYSDEVICE 3.3 Required Software The software requirements list for HSM is as follows: * HSM V3.0A is supported on the OpenVMS Alpha V6.2, V7.1, V7.2, and V7.2-1, and OpenVMS VAX Operating System V6.2, V7.1, and V7.2. HSM V3.0A does not support ODS5 disk volumes. * HSM Basic Mode does not require any software other than HSM and the OpenVMS Operating System. * 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 advantage of the latest enhancements and device support. An MDMS license is not required for using HSM. An SLS license is required only if SLS is to be used independently of HSM. 3.3.1 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.2 through 7.2 - see above. Media and Device Management Services (MDMS) is required only if you wish to convert from HSM Basic Mode to HSM Plus Mode. 3.3.2 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: * Off the HSM distribution kit * Included with Storage Management Library System for OpenVMS (SLS). * Included as a separate source with Archive/Backup System for OpenVMS (ABS) or Sequential Media File system for OpenVMS (SMF) software MDMS software must be installed before you install HSM in Plus mode, unless SLS is already present on 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. 3.3.3 Required for HSM Repack Function The HSM SMU REPACK Command allows you to do an analysis 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. 3.4 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. 3.5 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 See System Parameters for VAX and ALPHA. Table 3-2 System Parameters for VAX and ALPHA System Parameters VAX ALPHA Additional GBLPAGES 1783 2926 Additional GBLSECTIONS6 36 To find your current system parameters, use the following command: $ MCR SYSGEN SYSGEN> SHOW GBLPAGES SYSGEN> SHOW GBLSECTIONS 3.6 Required for VMSINSTAL When you invoke VMSINSTAL, it checks for the following: * Whether you are logged into a privileged account * Whether you have adequate quotas for installation * Whether DECnet? software is running * 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) 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. 3.7 Installing DECthreads? Images If DECthreads? 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 DECthreads? 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 $ install add sys$library:cma$open_rtl.exe/open/head/share 3.8 Registering Your HSM License To register your HSM license or to add additional capacity licenses, follow the steps in See How to Register Your HSM License. Before you attempt to register your PAK, be sure to have the PAK information in front of you. Table 3-3 How to Register Your HSM License Step Action Enter the LICENSE REGISTER command with the product name and a dash. 1. $ LICENSE REGISTER HSM-SERVER - Important: Enter a dash at the end of each command in steps 1 through 8. Enter the /ISSUER qualifier information, assigning the value 1. 2. DEC between quotation marks. _$ /ISSUER="DEC" - Enter the /AUTHORIZATION qualifier information, assigning it 1. 3. the value from the AUTHORIZATION NUMBER entry of the PAK. _$ /AUTHORIZATION=xxxxxxx - Enter the /PRODUCER qualifier information, assigning the value 1. 4. DEC in quotes. _$ /PRODUCER="DEC" - Enter the /UNITS qualifier information, assigning the value from the UNITS entry of the PAK. This is the value that 1. 5. determines your HSM online capacity. _$ /UNITS=nn - Enter the /DATE qualifiers information, assigning the product's release date value from the PRODUCT RELEASE DATE entry of the 1. 6. PAK. _$ /DATE=dd-mmm-yyyy - Enter the /AVAILABILITY qualifier information, assigning the 1. 7. value from the AVAILABILITY TABLE CODE entry of the PAK. _$ /AVAILABILITY=x - Enter the / OPTIONS qualifier information, assigning the value 1. 8. from the KEY OPTIONS entry of the PAK. _$ /OPTIONS=xxxxxx - Enter the /CHECKSUM qualifier information, assigning the value from the CH entry of the PAK. Important:Do NOT end the entry 1. 9. with a dash. _$ /CHECKSUM=n-xxxx-xxxx-xxxx-xxxx Invoke the LICENSE LOAD command with the product name. 1. 10. $_LICENSE_LOAD_HSM-SERVER 4 Installing HSM Software This chapter contains instructions for installing HSM Version 3.0A software on the OpenVMS operating system. 4.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. 4.1.1 The Installation Procedure The HSM installation procedure consists of a series of questions and informational messages. See How to Install the HSM Software 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 4-1 How to Install the HSM Software Step Action 1 Load and mount the media that contains the software kit. Invoke the VMSINSTAL procedure. Use the following command: $@SYS$UPDATE:VMSINSTAL HSM022 location: OPTIONS N Where: 2 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. If you see the following message: 3 %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. Confirm the state of the system backup. 4 * Are you satisfied with the backup of your system disk [Yes]? Press . Identify the location for the software to be mounted. * Where will the distribution volumes be mounted: 5 You may specify a tape drive, a local disk, or a remote disk. Enter the appropriate information and press . 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: 6 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 . Answer if you want to purge old files. 7 * Do you want to purge files replaced by this installation [YES]? Enter Y and press . Select to run the Installation Verification Procedure (IVP). * Do you want to run the IVP after the installation [YES]? 8 Recommendation: Running the IVP procedure is recommended. Press to run the IVP, else enter No and press . 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: 9 HSM-SERVER HSM-USER * Does this product have an authorization key registered and loaded [Y]? Enter Y and press 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.9B or newer must be installed before installing 10 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]: The default shown varies according to whether the HSM install detects the presence of MDMS or SLS Version 2.9B 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. 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 11 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 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 12 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$SYSDVICE:[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. 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. 14 Recommendation: Compaq recommends you answer Y to the following question: * Do you want to run the database creation procedure [YES]? 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. 15 Recommendation: Compaq recommends you answer Y to the following question: * Do you want to submit SETFILENOSHELV.COM [YES]? At this point, the installation proceeds without further operator 16 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. 4.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: * The operating system version is incorrect. * Quotas necessary for successful installation are insufficient. * System parameter values for successful installation are insufficient. * The OpenVMS help library is currently in use. * 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. 4.2 After Installing HSM Software The following postinstallation tasks should be performed after installing HSM software: * Edit the system startup and shutdown files. * Modify system parameter settings. * Create an HSM catalog, if you did not have the installation do so. * Install special device drivers. 4.3 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 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: * For a VAX system: $ MCR SYSGEN CONNECT HSA0:/NOADAPTER * 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 4.4 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 system wide 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 the catalog, the line in SYS$STARTUP:HSM$LOGICALS.COM that defines this logical should be changed. 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. 4.5 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. 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 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: * A description of the default configuration installed with HSM * A discussion of how to make minimal adjustments to the default configuration for HSM to function in your operational environment * A description of how to set up the near-line and off-line environments for both Basic and Plus modes * Example off-line configurations for both Basic and Plus modes 5.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. 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: * A default facility definition * A default shelf definition * A default device definition * A default volume definition * Default policy definitions 5.1.1 The Default Facility * The facility is initially set up with the following attributes: * All HSM operations are enabled * All event logging is enabled * All nodes are authorized as shelf servers * Use of a catalog server is disabled * 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. 5.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. 5.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: * The device is shared with other applications. * Shelving and unshelving operations are enabled. * 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. 5.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: * Explicit HSM operations (preshelving, shelving, unshelving, file faults, unpreshelving) are enabled. * Implicit HSM operations (policy-based operations) are disabled. * Contiguous files are ineligible for shelving * Placed files are eligible for shelving * 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: * Update the default volume record, which will affect all online disk volumes associated with the default volume. * 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. Compaq 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. Compaq also recommends that you create an individual volume record for each system disk and disable all HSM operations on those volumes. 5.1.5 The Default Policies HSM provides three default policies as follows: * HSM$DEFAULT_POLICY-This is used as a template for all policy definitions, including the other two default policies. * HSM$DEFAULT_OCCUPANCY-This policy is used as the default reactive policy definition in the system for device full and high water mark triggers. * 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: * The policy is enabled for shelving (rather than preshelving). * 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. * 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. * The low water mark goal for the policy is 80 percent. * The primary policy file selection algorithm is space time working set (STWS). * The secondary policy file selection algorithm is least recently used (LRU). 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. 5.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: * Define archive classes for use. * Select archive classes for the default shelf. * Define devices to support each archive class. * Initialize the tape volumes for each archive class. * Set volume retention times on all online disks on which you want policy-based shelving to occur. 5.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: $ SMU SHOW FACILITY HSM is enabled for Shelving and Unshelving Facility history: Created: 22-APR-1999 12:10:37.13 Revised: 22-APR-1999 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: * Whether the facility is enabled for shelving, unshelving, or both * Which nodes on the cluster are designated as shelf servers * The current shelf server node * An indication of whether all catalog writes and caching operations are performed by the shelf server node * What log options are turned on * The HSM operational mode (Basic or Plus) * 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. 5.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 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). 5.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. Compaq 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: 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. 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. 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 class SMU SET SHELF/DEFAULT /ARCHIVE=1/RESTORE=1 Use two archive classes SMU SET SHELF/DEFAULT /ARCHIVE=(1,2) /RESTORE=(1,2) Use three archive classesSMU SET SHELF/DEFAULT/ARCHIVE=(1,2,3) /RESTORE=(1,2,3) 5.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. 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: ALL (default) Uses the device for shelve, preshelve, unshelve, and cache flush operations SHELVE Uses the device exclusively for shelve, preshelve, and cache flush operations Uses the device exclusively for unshelve operations. When UNSHELVE 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 device: SMU SET DEVICE /DEDICATE=ALL device Specify a shared device: SMU SET DEVICE /SHARE=ALL device Support the device for one archive class SMU SET DEVICE device: /ARCHIVE=1 Support the device for two archive classes SMU SET DEVICE device:/ARCHIVE=(1,2) Support the device for three archive classes SMU SET DEVICE device: /ARCHIVE=(1,2,3) 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. Robot Name In Basic mode, you must associate a Robot Name with a tape magazine loader if you wish it to be robotically controlled. 5.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 See Archive Class Identifier/Label Reference for HSM Basic Mode Archive: Table 5-1 Archive Class Identifier/Label Reference for HSM Basic Mode Archive Archive Id Archive Label Volume Id Volume Label Volume 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 HSZxxx 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 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. 5.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) 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. 5.3 Additional Configuration Items There are three additional configuration tasks you may want to perform to use in connection with HSM's default configuration: * Authorize shelf servers * Specify a cache for HSM to use * Schedule default policy execution 5.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) 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 for shelf server operation SMU SET FACILITY/SERVER=node Authorize several nodes for shelf server operation SMU SET FACILITY/SERVER=(node,node,...) Authorize all nodes for shelf server operation SMU SET FACILITY/NOSERVER (default) 5.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 volume SMU SET CACHE device: Set the cache block SMU SET CACHE device: /BLOCK=value size Change the flush device: SMU SET CACHE /INTERVAL=time interval Specify the flush SMU SET CACHE device: /AFTER=time start_time 5.3.3 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. 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: $1$DUA13 is set to 100,000 blocks $1$DUA14 is set to 50,000 blocks $1$DUA15 is set to 100,000 blocks 5.3.4 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. See Supplied Default Policy Definitions lists the supplied default policy definitions that are configured for operation upon installing HSM. Table 5-2 Supplied Default Policy Definitions Definition Name Preventive policy HSM$DEFAULT_POLICY + HSM$DEFAULT_OCCUPANCY, HSM$DEFAULT_QUOTA + Reactive policies These default definitions cannot be deleted. 5.3.5 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. 5.3.5.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. 11. 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-1999 12:39:32.34 Revised: 8-JUN-1999 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: 1. 12. 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 1. 13. 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. $ 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: 5.3.5.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 5.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. 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. 5.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. 5.4.2 How MDMS Supports HSM MDMS provides the following services: * An integrated and shared approach to controlling access to devices * A shared database to media and device information * Common commands that allow you to manage media across storage management products What this means for HSM is: If you already use MDMS to support some other storage management product, you will need to do little to add functionality for HSM. 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. HSM can now support more devices, including TL820s as fully robotic devices. HSM can support gravity-controlled loading in a Digital Linear Tape (DLT) magazine loader in addition to robotically-controlled loading in a DLT. 5.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. See MDMS Commands for HSM Plus Mode 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 5-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 JUKEBOXPerforms a physical inventory of the cartridges in a tape jukebox, such as a TL820 or a DLT loader. 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. 5.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. 1. 2. Add volumes and volume pools to the MDMS database. 2. 3. Authorize HSM to access volumes in appropriate pools. 3. 4. If you are using magazines for HSM, add magazines to the magazine database and bind the volumes to them. 4. 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. 5.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: A name that identifies the media type, often related to the MTYPE_n 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. 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. DENS_n * If the drives for this media type suppor