**************************** ECO SUMMARY INFORMATION **************************** Release Date: 22-DEC-2006 Kit Name: ABS_I64VMS_V44_901.ZIP Kit Applies To: OpenVMS I64 V8.2, 8.2-1 and V8.3 Approximate Kit Size: 65484 blocks Installation Rating: INSTALL_2 Reboot Required: No Superseded Kits: None Mandatory Kit Dependencies: None Optional Kit Dependencies: None Checksums: ABS_I64VMS_V44_901.ZIP Checksum: 3582858248 ABS_I64VMS_V44_901.ZIP MD5 Checksum: 4999B4BD67F521ECA1F31DA72AF8F24C ____________________________________________________ HP Archive/Backup System for OpenVMS Version V4.4-ECO01 Release Notes December 2006 This release note describe new features, known restrictions, and errors found in the Archive/Backup System software and documentation, and provides a brief description of the changes for this version. The "New Features/Enhancements", "Known Problems and Restrictions", and "Documentation Updates and Errata" sections are updated for V4.4-ECO01 release. All other sections remain same from V4.4 release. Software Version: HP Archive/Backup System for OpenVMS Version V4.4-ECO01 Required Operating System: OpenVMS VAX V7.3, OpenVMS Alpha V7.3-2, V8.2 and V8.3, OpenVMS I64 V8.2, V8.2-1 and V8.3 Required Software: HP Media, Device and Management Services for OpenVMS Version V4.4-ECO01 Optional Software: DECnet (Phase IV) or DECnet-Plus (PhaseV) or TCP/IP Services for OpenVMS ________________________________________________________________ December 2006 © Copyright 2006 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group. Java is a US trademark of Sun Microsystems, Inc. Oracle, Oracle RDB, and Oracle RMU are all registered trademarks of Oracle Corporation. Printed in the US This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Introduction..................................... 1 1.1 Installing ABS/MDMS ........................... 3 2 Software Version Requirements.................... 4 2.1 Archive/Backup System Software Version Requirements................................... 4 2.2 Media Management Software Version Requirements................................... 5 3 New Features/Enhancements........................ 6 4 Problems Fixed in this Release................... 7 4.1 Archive/Backup System Problems Fixed in this Release........................................ 7 4.2 Media Management Problems Fixed in this Release........................................ 7 5 Known Problems and Restrictions.................. 7 5.1 Archive/Backup System Known Problems in V4.4-ECO01..................................... 7 5.1.1 Duplex backup using Oracle 10g fails with "RMAN-03009" and "ORA-00447" errors even if BACKUP_TAPE_IO_SLAVES is enabled............ 7 5.1.2 Restriction with SBT........................ 7 5.2 Archive/Backup System Known Problems in V4.4 .. 8 5.2.1 Volume Placement shows ONSITE after the Volume Database is Converted back to SLS/MDMS V2.x Environment................... 8 5.2.2 SBT Functionality on OpenVMS................ 8 5.2.3 Aborted Save Logs Multiple Messages on OpenVMS I64................................. 8 5.2.4 Staging Unpack Operation Logs CMA Exception on OpenVMS I64.............................. 8 5.2.5 ABS Save Fails with CMA Exception if the Catalog is not Present...................... 8 5.2.6 SBT Test Program with RDF Devices........... 9 iii 5.2.7 One Movement Type Allowed Per Save Request.. 9 5.2.8 ABS REPORT SAVE_LOG Fails when Searching SLS Catalogs.................................... 10 5.2.9 ABS might have Problems in Saving Files Greater than 2 GB in Size................... 10 5.2.10 Setting Volume on Archive while Save is Running..................................... 10 5.2.11 Inherited Problems in Backup Agent ABS$BACKUP.EXE.............................. 10 5.2.12 Verifying Installation...................... 11 5.2.13 Permission Denied or Invalid Argument Error on Windows Save Request..................... 11 5.2.14 Save Request must Specify the Correct Object Type........................................ 12 5.2.15 ABS RESTORE with Brief Listing Fails to Provide Listing File........................ 12 5.2.16 RMU Backup Exclude_Specification Parameter.. 12 5.2.17 RMU Backup Include_Specification Parameter.. 13 5.2.18 Selective Restore Operation................. 14 5.2.19 Avoid Use of ABS$UBS_VERBOSE Logical Name... 14 5.3 Archive/Backup System Restrictions ............ 14 5.3.1 Parallel Save and Restore Requests must not be Executed during Catalog Cleanup.......... 14 5.3.2 SCSNODE must be Defined for ABS/MDMS to Start....................................... 15 5.3.3 Using DECnet-Plus (Phase V) with ABS........ 15 5.3.4 Post-processing Command Fails to Execute.... 15 5.3.5 Restriction On The "-bnn" Value for UNIX or NT Clients.................................. 15 5.3.6 Restoring an Entire Tru64 UNIX Filesystem... 16 5.3.7 Tape Device Protection...................... 16 5.3.8 OPCOM Restriction........................... 17 5.3.9 Request Restart............................. 17 5.3.10 No Restart Operation........................ 17 5.3.11 Restoring Multi-File Oracle RDB Databases... 17 5.3.12 Restrictions with ABS Windows 2000 Client... 17 5.4 Known Media Management Problems and Restrictions................................... 18 5.4.1 Logical Pointing to Disk Name must be Defined during the Restore Operation........ 18 5.4.2 Specifying Wildcard * to Maintain Directory Structure during the Restore Operation...... 18 iv 5.4.3 /NOASSIST Qualifer Cannot be Used with the /PORT Qualifier............................. 18 5.4.4 /PORT Qualifier Cannot be Used from the MDMS GUI......................................... 18 5.4.5 ALLOCATE DRIVE Preceded by LOAD VOLUME Results in Allocation of a Wrong Drive...... 19 5.4.6 RDF is not Supported on OpenVMS I64......... 19 5.4.7 DCL Syntax for Lists must be Followed or You might Get Unexpected Results................ 19 5.4.8 Motif Look and Feel......................... 19 5.4.9 /AFTER_SCHEDULE Logic Misbehaves if ABS is Shutdown when a Save is in Progress......... 20 5.4.10 /AFTER_SCHEDULE Qualifier................... 20 5.4.11 V4.1 Stores Object Names in Upper Case Only........................................ 20 5.4.12 Fiber Channel Environment................... 21 5.4.13 MDMS does not Support Multiple NIC Interfaces with TCP/IP on the same Node..... 22 6 Documentation Updates and Errata for V4.4-ECO01.. 22 6.1 Expiration Date and Retention Days ............ 22 6.2 Errata ........................................ 24 7 Media Management Configuration and Operation..... 25 8 Converting ABS 3.* to V4.4....................... 25 9 Upgrading from ABS V2.*.......................... 26 10 How to Remove V4.4 ABS/MDMS Files................ 27 v _________________________________________________________________ Preface Conventions The following conventions are used in this document: ___________________________________________________________ Convention_______Meaning___________________________________ {} In format command descriptions, braces indicate required elements. [ ] In format command descriptions, square brackets indicate optional elements of the command syntax. You can omit these elements if you wish to use the default responses. boldface text Boldface type in text indicates the first instance of a term defined in the Glossary or defined in text. italic text Italic type emphasizes important information, indicates variables, indicates complete titles of manuals, and indicates parameters for system information. Starting test This type font denotes system response, ... user input, and examples. Ctrl/x Hold down the key labels Ctrl (Control) and the specified key simultaneously (such as Ctrl/Z). v ___________________________________________________________ Convention_______Meaning___________________________________ PF1 x The key sequence PF1 x instructs you to press and release the PF1 key, and then press and release another key (indicated here by x). n A lowercase italic n denotes the generic use of a number. For example, 19nn indicates a four-digit number which the last two digits are unknown. x A lowercase x denotes the generic use of a letter. For example, xxx indicates any combination of three alphabetic _________________characters._______________________________ Related Products The following related products may be mentioned in this document: ___________________________________________________________ Product__________Description_______________________________ HSM HSM refers to Hierarchical Storage Management for OpenVMS software. MDMS MDMS refers to Media, Device and Management Services for OpenVMS software. OpenVMS OpenVMS refers to OpenVMS operating system. SLS SLS refers to Storage Library System for _________________OpenVMS_software._________________________ Associated Documents The following documents are part of the Archive/Backup System documentation set: o HP Archive/Backup System for OpenVMS Installation Guide o HP Archive/Backup System for OpenVMS Guide to Operations o HP Archive/Backup System for OpenVMS Command Reference Guide vi 1 Introduction This document describes new features and/or enhancements, known problems, restrictions, and errors found in the Archive/Backup System software and documentation. This document also includes Media, Device and Management Services changes for version V4.4-ECO01. o ABS V4.4 uses the MDMS server to manage policies (saves, restores, archives, and environments). See the MDMS sections of the release notes for more information on using the new database. ________________________ Note ________________________ Before upgrading from V3.n, we recommend that you do an ABS SHOW object/FULL/ OUT=filename on all your ABS objects. This is useful for comparison of the objects after the upgrade and the conversion. ______________________________________________________ o During the upgrade to V4.4 from V3.n, the MDMS database files will be copied to files named MDMS$DATABASE_LOCATION:MDMS$*_DB.DAT_COPY. The ABS policy engine configuration file is also renamed to ABS$SYSTEM:ABS$POLICY_CONFIG.DAT_OLD and the ABS$SYSTEM:ABS$EXT_*.COM files are renamed to ABS$EXT_ *.COM_OLD. These are used if you remove the V4.3A files, see Section 10 o ABS V4.0 did NOT allow a rolling upgrade on the servers or clients. This is because the policy engine has been moved into the MDMS server, so all nodes must be using the same mechanism to talk to the database server. If you are on an ABS V4.x stream you once again have the rolling upgrade option. o The MDMS V4.4 server provides the scheduling of save and restore requests. See the MDMS sections of the release notes for more information on the scheduling options. 1 o If you are upgrading from 3.n, the DECSCHEDULER scheduling option will be converted to SCHEDULER during the installation. Jobs will be submitted to DECscheduler using the MDMS$SYSTEM:MDMS$EXT_SCHEDULER.COM command procedure. ________________________ Note ________________________ Because of this change, the SCHEDULER option will not work if you do not have a license for DECscheduler. If you are using the DECscheduler for flexibility of scheduling, check out the options available in V4.4 for the INTERNAL schedule with custom schedules. It offers very flexible scheduling. ______________________________________________________ o The ABS$SYSTEM:ABS$EXT*.COM external scheduling files were changed between V3.n and V4.0. In V3.n, the files were called ABS$SYSTEM:ABS$EXT_*.COM. In V4.0, these were moved and renamed to MDMS$SYSTEM:MDMS$EXT*.COM. If you are upgrading from V3.n and if you have made modifications to these procedures, be sure to incorporate your modifications into the new versions. Take the changes from ABS$SYSTEM:ABS$EXT_*.COM and put them into the MDMS$SYSTEM:MDMS$EXT*.COM files. The installation will not incorporate your changes into the command procedures, it will provide a new command procedure. The new command procedure must be used for the V4.4 external scheduling to work. o ABS V4.4 does not require DECnet for server communications. Since MDMS server handles the communications, you may use TCP/IP and/or DECnet. o If you are using the MDMS Graphical User Interface (GUI) on Microsoft Windows and if Java is installed, then typing java in the command line should execute java.exe from the installed location. However, if this does not happen, you will need to first edit the MDMSView.bat file to include the correct path of java.exe. Example: C:\Program Files\Java\j2re1.4.2_06\bin\java.exe 2 o When using the MDMS GUI on OpenVMS Alpha, the account quota PGFLQUO should be set to at least 200,000. Correspondingly, the system pagefile should be large enough to accommodate this quota. The process quota WSQUOTA should be set to 10,000. Correspondingly, the sysgen parameter WSMAX, should be set to 10,000 or higher. The system where you are running the GUI should have at least 128 MB of memory (preferably higher). o When you install ABS and you are using HSM on your system, the installation procedure will ask you if you want to use the backup-via-shelving paradigm. If you answer "yes", a logical will be defined in your ABS$SYSTARTUP.COM file. If you say "no", the logical is not defined. If you later decide to use the backup-via-shelving paradigm, you must define the logical ABS$SHELVING_ SUPPORT to TRUE in your ABS$SYSTARTUP.COM procedure. Failure to define the logical will mean that /noshelved and /nopreshelved qualifiers will not be used during backup and files will be unshelved during the backup. o Earlier versions of ABS had allowed the use of SLS/MDMS V2.9x as the media manager. That interface has been removed from ABS V4.4. You must be prepared to use MDMS V4.4 before upgrading. See the chapter, "Converting to ABS/MDMS V4.X" cX" in the HP Archive Backup System for OpenVMS, Guide to Operations for important information and guidelines on MDMS V2.9x to MDMS V4.4 conversion. o ABS V4.4 does not support the use of an RDB database for the ABS policies. If you are currently using ABS with an RDB database you must convert the RDB database using the conversion procedure described in the release notes for V3.2A prior to upgrading to V4.4. 1.1 Installing ABS/MDMS If you are installing Archive Backup System (ABS)/Media, Device and Management System (MDMS) for the first time, refer to the HP Archive Backup System for OpenVMS Installation Guide before installing the products. Refer to the HP Archive Backup System Guide to Operations for information on configuring ABS/MDMS. 3 ABS/MDMS V4.4-ECO01 kit contains the following savesets: o ABS044.A - Installation procedure and Release Note o ABS044.B - Common files o ABS044.C - OpenVMS Alpha Executables o ABS044.D - OpenVMS VAX Executables o ABS044.E - RDF kit o ABS044.F - GUI kit for OpenVMS Alpha/I64 o ABS044.G - GUI kit for Windows o ABS044.H - OpenVMS I64 Executables 2 Software Version Requirements The following sections describe the software version requirements for ABS and MDMS. 2.1 Archive/Backup System Software Version Requirements Ensure that the following requirements are satisfied before installing ABS V4.4-ECO01: o OpenVMS VAX V7.3 o OpenVMS Alpha V7.3-2, V8.2 and V8.3 o OpenVMS I64 V8.2, V8.2-1 and V8.3 o DECnet Phase IV or DECnet-Plus for OpenVMS if you plan to use DECnet for communication. o TCP/IP Services for OpenVMS if you plan to support UNIX or Windows clients, or use TCP/IP for the server communication. o Java Runtime Environment (JRE) version 1.2 or later. Installing JRE is optional; it is only required if you plan to use MDMS GUI. ________________________ Note ________________________ ABS for OpenVMS works with HP TCP/IP services for OpenVMS. Our limited testing of Multinet with ABS/MDMS has not uncovered any issues. Engineering will not reject an escalation because of the use with this product. But, if through investigation Multinet is 4 suspected of being the problem, the customer will be asked to pursue remedy through their existing contract with Multinet service. ______________________________________________________ 2.2 Media Management Software Version Requirements MDMS V4.4-ECO01 is supported on the following OpenVMS versions: o OpenVMS Alpha V7.3-2, V8.2 and V8.3 o OpenVMS VAX V7.3 o OpenVMS I64 V8.2, V8.2-1 and V8.3 In addition, the GUI is supported on the following OpenVMS versions for MDMS V4.4-ECO01: o OpenVMS Alpha V7.3-2, V8.2 and V8.3 o OpenVMS I64 V8.2, V8.2-1 and V8.3 o Windows Intel Platforms (2000/XP) The GUI requires the Java Runtime Environment (JRE) or Java Development kit (JDK) V1.2 or later. In addition, the GUI communicates with the MDMS server on an OpenVMS system using the TCP/IP protocol. Therefore, a product supporting the TCP/IP protocol (example: TCP/IP Services for OpenVMS or Multinet) is a pre-requisite for using the MDMS GUI. If you are using ABS V4.4 for the first time, MDMS V4.4 can be installed and configured as a new installation, For OpenVMS on VAX and Alpha servers, you can upgrade from any ABS V3.x, V4.0, V4.1, V4.2, V4.3 or V4.3A environments to ABS V4.4. Alternatively, if you have a previous installation of SLS/MDMS V2.9x, the SLS to ABS Migration tool provided with the ABS V4.4 kit facilitates you to migrate from SLS /MDMS V2.9x to ABS/MDMS V4.x. The migration happens in the following phases: - Converting MDMS V2.x Symbols and databases to MDMS V4.x database objects: To convert the MDMS V2.x TAPESTART.COM, volume and magazine databases into MDMS V4.x database objects, use the following command procedure: 5 $ @MDMS$SYSTEM:MDMS$CONVERT_V2_TO_V4 - Applying Prev3 Support: Set the MDMS$PREV3_SUPPORT logical to "TRUE" in SYS$MANAGER:MDMS$STARTUP.COM to restore the SLS backed up data after the conversion. - Converting SLS SBK Symbols to ABS Policy objects: To convert the SLS SBK Symbols to ABS Policy objects, use the following command procedure: $ @ABS$SYSTEM:SLS_CONVERT.COM 3 New Features/Enhancements The following sections describe the new features and changes provided in ABS/MDMS V4.4-ECO01. System Backup to Tape (SBT) for Oracle databases feature The System Backup to Tape (SBT) for Oracle databases feature of Archive Backup System (ABS) has been qualified to back up Oracle10g (10.1.0.3.0) database using Oracle's Recovery Manager on OpenVMS Alpha V8.2. Expiration Date and Retention Days Display Modified MDMS has been enhanced to display the following message when /RETENTION_DAYS = 0 is specified while creating an archive using MDMS CREATE ARCHIVE or modifying its attributes using MDMS SET ARCHIVE: %MDMS-I-CONFIRM, SETTING RETENTION TO 0 WILL RESULT IN VOLUMES HAVING THEIR SCRATCH DATE SET TO THE SAME DAY AS THE COMPLETION OF THE BACKUP. NO RETENTION OF THE DATA WILL TAKE PLACE. ARE YOU SURE (Y/N): Selecting Y will scratch the data on the same day as the completion of the backup; else selecting N will ignore the command with the following confirmation: %MDMS-I-CMDIGNORED, The previous command was ignored This message is displayed to make you aware of the consequences of setting /RETENTION_DAYS = 0. 6 4 Problems Fixed in this Release 4.1 Archive/Backup System Problems Fixed in this Release There are no problems fixed in this release. 4.2 Media Management Problems Fixed in this Release There are no problems fixed in this release. 5 Known Problems and Restrictions The following sections describe known problems and restrictions with ABS and MDMS. 5.1 Archive/Backup System Known Problems in V4.4-ECO01 The following section describes the known problems with ABS V4.4-ECO01: 5.1.1 Duplex backup using Oracle 10g fails with "RMAN-03009" and "ORA-00447" errors even if BACKUP_TAPE_IO_SLAVES is enabled When backing up datafiles, archived redo log files, server parameter files and control files into backup pieces, RMAN can duplex* the backup set, producing up to four identical copies of each backup piece in the backup set on different backup destinations with one BACKUP command. When trying to execute a duplex backup, the following error is encountered: "ORA-00447: fatal error in background process" *For more information about duplex backup, see the Oracle Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) 5.1.2 Restriction with SBT System Backup to Tape (SBT) feature of ABS for Oracle Recovery manager (RMAN) does not support the "proxy copy" feature of ORACLE RMAN. 7 5.2 Archive/Backup System Known Problems in V4.4 The following sections describe the known problems with ABS. 5.2.1 Volume Placement shows ONSITE after the Volume Database is Converted back to SLS/MDMS V2.x Environment After converting back the volume database from ABS/MDMS V4.x environment to SLS/MDMS V2.x environment, when you give the STORAGE REPORT VOLUME command from the client node, the volume placement for some of the volumes is shown as OUTSIDE or ONSITE. This error on volume placement to ONSITE or OUTSIDE location is not consistent across the volumes in the volume database. It is also occassionally observed when you migrate from SLS/MDMS V2.x to ABS/MDMS V4.x environment. A possible workaround to this issue could be taking a fresh inventory of volumes after the migration from/to ABS/MDMS V4.x and SLS/MDMS V2.x environments. 5.2.2 SBT Functionality on OpenVMS SBT functionality is not available on OpenVMS I64. 5.2.3 Aborted Save Logs Multiple Messages on OpenVMS I64 When an ABS save/restore request is aborted, the status "Job Terminated" is written in the Log file multiple times. 5.2.4 Staging Unpack Operation Logs CMA Exception on OpenVMS I64 When staging is enabled for a catalog, the staging unpack operation after writing all the files into the catalog fails with a CMA exception and creates a dump file in ABS$ROOT directory. This exception will not affect the normal operation of saves/restores. ABS save will be successful and all the files will be cataloged. The user will also be able to restore the data. 5.2.5 ABS Save Fails with CMA Exception if the Catalog is not Present ABS save fails with a CMA exception instead of CATLG_DB_ NOT_FOUND if the catalog specified in the archive is not present. 8 5.2.6 SBT Test Program with RDF Devices SBT is provided as a shareable image, which is invoked by the Oracle Recovery Manager (RMAN) to backup Oracle databases. SBT allocates and mounts the devices for RMAN to backup databases. SBT test program which is supplied with SBT is used to test SBT interface with ABS/MDMS 4.x. An attempt to backup and restore to an RDF device using the SBT test program fails with the following footprint: MMAPI error: err_code=7501, Fatal media movement error Failed to allocate drive System Error: %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XH, PC=!XH, PS=!XL %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XH, PC=!XH, PS=!XL The problem is seen only with Rdserver running on OpenVMS (Alpha) 6.2-1 and 7.2-1 and Rdclient running on OpenVMS Alpha (7.2-1). The problem is not seen with Rdserver running on OpenVMS (VAX).The problem is seen only when both backup and restore operation is done in a single session from the SBT test program .We are in touch with RDF Engineering to resolve this problem. However you can still use the RDF with the Rdserver running on OpenVMS (Alpha and VAX) to backup and restore your Oracle database without any problems as long as backup and restore operations of the database are done in separate sessions. Before doing the configuration for SBT, Ensure that Oracle's Recovery Manager is setup and you are able to access it. Please refer to the chapter "System Backup to tape for Oracle Databases" in ABS guide to operations manual for configuring SBT. 5.2.7 One Movement Type Allowed Per Save Request Only one movement type is allowed per save request. The movement types are FULL, INCREMENTAL, and SELECTIVE. If you specify include specifications for more than one type of movement, you may get backup errors. For example, if your save request contains include specifications with a disk name and also other objects with more than a disk name (ie. 9 disk:[dir]), backup will return an error on some objects because an image backup works with a disk name only. Workaround: Include only one type of include specification in your save request. For example, a save request should only include disk names, or directory names. 5.2.8 ABS REPORT SAVE_LOG Fails when Searching SLS Catalogs If you do an ABS REPORT SAVE_LOG command and do not specify a catalog or storage_class, once ABS has searched an SLS catalog, the command will stop and will not search the remaining catalogs on the system. Workaround: Until this problem has been resolved, specify a catalog or storage_class name on the ABS REPORT SAVE_LOG command. 5.2.9 ABS might have Problems in Saving Files Greater than 2 GB in Size You might have problems saving files greater than 2 GB in size on Unix and Windows NT systems. On Unix systems, please refer to the documentation provided with the gtar you are using. The gtar version that we supply for Windows NT and the source that we provide for Unix do not accommodate files greater than 2 GB in size. 5.2.10 Setting Volume on Archive while Save is Running Adding a volume set name to an archive while a save request is running can cause problems with the cleanup after the save request (leaving it in a locked state). Two archives referencing the same volume set is not supported. 5.2.11 Inherited Problems in Backup Agent ABS$BACKUP.EXE Problem: If you are using Backup-Via-Shelving the default backup agent for backing up OpenVMS files is SYS$SYSTEM:ABS$BACKUP.EXE. This image was built using the V6.1 source code of OpenVMS Backup (BACKUP.EXE) with some HSM features added. Thus, ABS$BACKUP has inherited the problems known to exist in V6.1 of BACKUP and new features added to BACKUP since V6.1 are not available in ABS$BACKUP. Solution: 10 The HSM features will be incorporated into BACKUP in an OpenVMS remedial ECO scheduled for release sometime after OpenVMS V7.3. If you are not using Backup-Via-Shelving ABS will use SYS$SYSTEM:BACKUP.EXE. 5.2.12 Verifying Installation Problem: When installing ABS as a new installation, the database initialization programs might fail to run. In this case, IVP fails with errors failing to show the storage classes and execution environments. Solution: After the installation, run SYS$SYSTEM:ABS$DB_INIT.EXE. This executable initializes the database with the default storage classes and execution environments. 5.2.13 Permission Denied or Invalid Argument Error on Windows Save Request Problem: ABS may produce the following log file errors after executing an NT save request: ABSgtar: can't add file C:\AFILE.EXT: : Permission denied ABSgtar: can't open directory C:\ADIR: : Invalid argument The cause of these errors is either the directory or file is open for write access by a user or application, or the system has been denied read access to the file or directory. ABS runs under the system account. Workaround: Close all open files or set the access on the files for the SYSTEM account. To set the file access, select the file from a fileview window. Select Properties from the File drop-down menu. Click the Security tab and then select Permissions. Select Add and highlight SYSTEM. Add the type of access (full control is best, so you can restore files). Click the Add button. This gives the SYSTEM account access to the files. Solution: 11 This problem will be corrected in the future version of ABS. 5.2.14 Save Request must Specify the Correct Object Type Problem: If you create a save request for a Tru64 UNIX or Windows file and you do not specify the UNIX_FILES_GTAR or WINDOWS_ NT_FILES_GTAR object type (default is VMS_FILES), ABS produces a scheduler error. Solution: Be sure to specify the UNIX_FILES_GTAR or WINDOWS_NT_FILES_ GTAR object type for the include specification. 5.2.15 ABS RESTORE with Brief Listing Fails to Provide Listing File Problem: If you are executing a RESTORE request which uses an environment policy with a BRIEF_LISTING setting, the restore will not create a listing file. Workaround: You may set the environment policy to FULL_LISTING and get a full listing instead. Solution: This problem will be addressed in a future version of ABS. 5.2.16 RMU Backup Exclude_Specification Parameter Problem: Save Request If you create or modify a save request for an Oracle RDB storage area and enter an exclude_specification parameter, ABS generates an incorrect syntax for the RMU Backup Utility. As a result, the save request fails. Solution: This problem will be corrected in a future version of ABS software. Problem: Restore Request 12 If you create or modify a restore request for an Oracle RDB database or storage area and enter an exclude_specification parameter, ABS ignores the file name entered for exclude_ specification parameter. Solution: None. The RMU Backup Utility does not support an exclude_ specification parameter for a restore request. 5.2.17 RMU Backup Include_Specification Parameter Problem: Wildcard Character The RMU Backup Utility does not support wildcard characters (* or %) in the include_specification parameter for a save or restore request. However, if you enter one of these characters, ABS fails to invalidate the illegal entry. ABS executes the save or restore request but generates an incorrect file name and as a result, the save or restore request fails. Solution: For an Oracle RDB database or storage area, do not enter any wildcard characters in the include_specification parameter. Problem: Comma-Separated List If the include_specification parameter on a restore request for an Oracle RDB database or storage area consists of a comma-separated list of disks or file names, ABS may not correctly restore the data. Example: The Include-Specification Contains: DISK$USER1:[USER1]SITE_PERSONNEL.RDB,DISK$USER2:[USER2]PERSONNEL.RDB Possible result: If the restore of DISK$USER1:[USER1]SITE_PERSONNEL.RDB includes any incremental restore operations, ABS may terminate the restore operation without restoring the subsequent Oracle RDB file names specified in the list. Solution: 13 For each Oracle RDB database or storage area that you want to restore, create a separate restore request or use Add Object option on the GUI to individually add each file name. Table 9-3 in Archive/Backup System for OpenVMS Guide to Operations explains how to use Add Object option. 5.2.18 Selective Restore Operation Problem: If a selective restore request is performed for an Oracle RDB storage area, but the last backup operation of the Oracle RDB database was an incremental, the restore request fails and ABS generates the following message: %RMU-F-WRNGDBBTYP, save_set_name does not contain a full backup Solution: Create an incremental restore request so that ABS will restore both full and incremental backups of the storage area. 5.2.19 Avoid Use of ABS$UBS_VERBOSE Logical Name Problem: The system logical name ABS$UBS_VERBOSE should be defined only when requested by HP. It may cause adverse side- effects after Save request failures, which include unintended initialization of the output volume. Check to ensure that this logical name has not been defined on nodes running ABS. 5.3 Archive/Backup System Restrictions The following are known restrictions for ABS V4.4. 5.3.1 Parallel Save and Restore Requests must not be Executed during Catalog Cleanup Parallel Save or Restore requests must not be executed when the cleanup of the Volume_Set type of catalog is in progress. If executed, it results in catalog having dangling AOEI entries. 14 5.3.2 SCSNODE must be Defined for ABS/MDMS to Start The Sysgen parameter SCSNODE must be defined on your system to run ABS/MDMS. The current startup procedures require this value or the SYS$NODE logical name to be defined. 5.3.3 Using DECnet-Plus (Phase V) with ABS If you use DECnet-Plus with ABS, you must define Phase IV synonyms (6 characters or less) for your nodes. ABS cannot use the long node names. 5.3.4 Post-processing Command Fails to Execute Problem: If a Save request does not complete successfully, and a post-processing command is specified either on the save request or the environment policy, the post-processing command will not execute. Solution: None. ABS only executes the post-processing command on the basis of a successful completion. The next time the save request completes successfully, ABS will execute the post-processing command. 5.3.5 Restriction On The "-bnn" Value for UNIX or NT Clients Problem: When doing Windows or UNIX save or restore requests, you may have set the agent qualifier "-bnn" to set the block length of a disk. If you set the value of "-bnn" to a number higher than 127 (-b127), you may get unexpected results for the save request. In this situation, ABS may generate ASSERT and ACCVIO errors. Solution: This is a restriction in OpenVMS. Do not set the -bnn agent qualifier value to a number higher than 127. If the disk is large enough to exceed this amount, create more than one save request for that particular disk. More Information: For more information about the -bnn qualifier, see Archive /Backup System for OpenVMS Guide to Operations. 15 5.3.6 Restoring an Entire Tru64 UNIX Filesystem You cannot restore an entire Tru64 UNIX filesystem to either the original location or to a different location by specifying only a "/" for the include specification. To restore the entire UNIX filesystem, you must specify each top level directory as shown in the following example: /usr /dev 5.3.7 Tape Device Protection Problem: When performing a user backup, if the tape device is protected against the user, the following error is logged in the execution log file: THREAD #1:%BACKUP-F-PARSE, error opening NODE01MKA500:[000000]13JUL19951339120.; THREAD #1: -RMS-E-PRV, insufficient privilege or file protection violation Workaround: If this error occurs, check the device protection of the target tape device by entering the following command from a privileged account: $ SHOW SECURITY/CLASS=device _Object name: MKA500 _MKA500: object of class DEVICE Owner: [SYSTEM] Protection: (System: RWPL, Owner: RWPL, Group: RWPL, World) Access Control List: To set the protection of the tape device for the world access, enter the following command: $ SET SECURITY/CLASS=DEVICE/PROT=(W:RWPL) MKA500 $ SHOW SECURITY /CLASS=DEVICE MKA500 _MKA500: object of class DEVICE Owner: [SYSTEM] Protection: (System: RWPL, Owner: RWPL, Group: RWPL, World: RWPL) Access Control List: 16 When the tape drive enables access to the user, the insufficient privilege problem from the backup command is eliminated. 5.3.8 OPCOM Restriction If you select OPCOM as the method of notification, then you must select the BRIEF option. If you select VERBOSE or NORMAL, the message could be truncated. 5.3.9 Request Restart ABS does not support restarting a save or restore request in the middle of the operation. All save and restore requests are restarted from the beginning. 5.3.10 No Restart Operation ABS does not attempt to replace a faulty member of a volume set and, as a result, the save operation fails. ABS also may not take advantage of the restart capabilities built into some of the backup agents. 5.3.11 Restoring Multi-File Oracle RDB Databases Do not specify an output location while restoring a multi-file Oracle RDB database. If an output location is specified, ABS places all storage area files in the specified output location. 5.3.12 Restrictions with ABS Windows 2000 Client - Encrypted files not supported - Backup of open files not supported - Mount point save and restore operations are successful when mount point exists while restoring. But if the mount point is removed, ABS Windows Client would restore the data of the mounted volumes to a new folder. This folder is no longer a mount point. - Restoration of Hard Link files results in the hard link being broken and two different individual files being restored. - The backup agent (ABSgtar) for Windows client does not allow wildcards in the file specification strings for save requests. 17 5.4 Known Media Management Problems and Restrictions This section describes known problems and restrictions for MDMS V4.4. 5.4.1 Logical Pointing to Disk Name must be Defined during the Restore Operation If a logical is used to specify the disk name, which is part of the destination specified for the restore request (the location where the data is restored), then ensure that the logical is defined before executing the restore request. If the destination is not exclusively provided for the /DESTINATION qualifier, then the restore request considers the include specification path as the default destination. If the logical is not properly defined, then the restore request fails displaying the NO_SUCH_DEVICE error. 5.4.2 Specifying Wildcard * to Maintain Directory Structure during the Restore Operation In case the include specification in the Save request had a directory tree structure, then to maintain the same during the Restore operation, you must specify the wildcard "*" in the include specification of the Restore request. /Include = TPRD:[TPRD.APPFILES*]*.*;* If you do not use the wildcard "*" or specify a wildcard other than "*" in the include specification, then all the files are automatically restored to the root directory. /Include = TPRD:[TPRD.APPFILES]*.*;* /Include = TPRD:[TPRD.APPFILES%]*.*;* 5.4.3 /NOASSIST Qualifer Cannot be Used with the /PORT Qualifier The /NOASSIST qualifier cannot be used with the /PORT qualifier when executing the MDMS MOVE VOLUME request using the /PORT qualifier. 5.4.4 /PORT Qualifier Cannot be Used from the MDMS GUI /PORT qualifier cannot be used with the MDMS MOVE command when this command is issued from the MDMS GUI. 18 5.4.5 ALLOCATE DRIVE Preceded by LOAD VOLUME Results in Allocation of a Wrong Drive ALLOCATE DRIVE preceded by the LOAD VOLUME, vol_name /DRIVE=drive_name results in the allocation of a wrong drive. An internal QAR has been raised to resolve this issue and the solution will be provided in the future release. However, this problem is observed when the command is given at the DCL prompt only. 5.4.6 RDF is not Supported on OpenVMS I64 RDF is not supported on OpenVMS I64 V8.2-1. 5.4.7 DCL Syntax for Lists must be Followed or You might Get Unexpected Results If you do not use the correct syntax when specifying lists in MDMS commands, DCL parsing may cause the command to work differently than expected. Since MDMS allows multiple objects on all commands, if a list is specified for one of the qualifiers, you must put parentheses () or quotes "" around the lists or you will get unexpected behavior. For example: $MDMS CREATE DRIVE d1/MEDIA=m1,m2 This will create two drives, d1 and m2. No error would be generated. If you use the correct syntax, you will get one drive d1 with two media types. The correct syntax is: $MDMS CREATE DRIVE d1/MEDIA=(m1,m2) Workaround: Use the syntax as described in the MDMS Reference Guide and in MDMS help. 5.4.8 Motif Look and Feel We have the arrow button for List, Combo and Date fields in MDMSGUI. The size of the arrow button is same for all the above fields. But the arrow button size varies in the Motif Look and Feel using Java 1.4 version. 19 5.4.9 /AFTER_SCHEDULE Logic Misbehaves if ABS is Shutdown when a Save is in Progress Consider a schedule TEST_SAVE_SCHED corresponding to save TEST. When the schedule is started, MDMS just initiates the save, which executes in the context of ABS. When the save completes, ABS updates the status of the save request in the 'transaction status' field. If ABS is shutdown when the save request is executing/initiated, the save status is not updated to the 'transaction status' field (since ABS is not running), which continues to show the status from the previous run. Since the 'transaction status' field continues to have the old status, the /AFTER_SCHEDULE logic ends up using this old status to schedule the after schedule jobs. Hence we see the /AFTER_SCHEDULE logic misbehaving. This problem will be fixed in a remedial after V4.1. 5.4.10 /AFTER_SCHEDULE Qualifier There is a restriction with using the /AFTER_SCHEDULE qualifier to link jobs. Only those schedules(created automatically by MDMS) that have an associated save can be assigned to the /AFTER_SCHEDULE qualifier. Schedules that do NOT have an associated save cannot be assigned to the /AFTER_SCHEDULE qualifier. Hence, any schedule(one with an associated save, or one which executes DCL commands) can have a dependency on a schedule with an associated save, but not on a schedule which executes DCL commands. This is a current MDMS design limitation. 5.4.11 V4.1 Stores Object Names in Upper Case Only ABS V3.x versions allowed both lower and upper case for object names. But ABS/MDMS V4.1 supports only upper case names. That is the names are stored in uppercase in the database. Hence if you upgrade from V3.2A to V4.1, and you have two drives names "xxx", and "XXX", you may not be able to modify the attributes of the drive named "xxx". Any attempts to change the attributes will affect the drive named "XXX"(uppercase) only. 20 5.4.12 Fiber Channel Environment In FC environment, we don't have any universal manager who maintains the information of devices (like which node has the device allocated). Further in FC enviroment VMS does not manage the allocation of drive across two or more clusters. Hence multiple users can allocate the same drive at the same time from two nodes (they may be either standalone nodes or they may be present in two different clusters). To overcome this MDMS polls the nodes listed in the drive object to ensure that none of the nodes listed in the drive list has allocated the device. Thus, if MDMS cannot reach a node it returns the drive check error. MDMS will not allow other nodes to access the drive without knowing the status of drive on one node as it may possibly lead to a data loss scenario. This is a design restriction with MDMS and the system administrator has to take judicious decision when the node is not reachable for some reasons like a node was shutdown. This restriction may lead to a potential save failure with a drive access error. A possible workaround to the issue is listed below: The customer needs to create an MDMS GROUP object. The GROUP object should consist of all the NODEs accessing the DRIVE/JUKEBOX and the DRIVE/JUKEBOX objects should have the GROUP listed in the DRIVE/JUKEBOX objects. At the time of system bootup the following command needs to be executed. $ MDMS SET GROUP xyx/NODE=node_name/ADD At the time of the system shutdown the following needs to be executed. $ MDMS SET GROUP xyx/NODE=node_name/REMOVE The above workaround is applicable only when the node is shutting down normally. In case the node is not reachable when there is a network issue due to reasons other than a normal node shutdown (example: due to a node crash or due to a network cable issue), the above-mentioned workaround will not be applicable. 21 Another alternative the system administrator can consider is to remove the NODE name from the DRIVE object in case of the customer wants to shutdown one of the nodes in a FC environment. 5.4.13 MDMS does not Support Multiple NIC Interfaces with TCP/IP on the same Node Due to a design limitation, MDMS does not support multiple NIC interfaces on the same node. We will plan to provide this support in the future releases. 6 Documentation Updates and Errata for V4.4-ECO01 The following section describes the documentation updates and errata for ABS/MDMS documentation set, and MDMS Help. 6.1 Expiration Date and Retention Days In Section 3.1.7 of the Archive Backup System for OpenVMS Guide to Operations guide, the /RETENTION_DAYS and /EXPIRATION_DATE qualifiers for MDMS CREATE ARCHIVE command are not defined completely. The /EXPIRATION_DATE and /RETENTION_DAYS qualifier for the archive object are mutually exclusive, as a result of which input values can be provided for only one of the qualifiers. Hence, the MDMS SHOW ARCHIVE command is modified to display the qualifier that has been used. When either of the qualifiers are used, the value for the other qualifier in the MDMS SHOW ARCHIVE command is displayed as "-". If none of these qualifiers are used in the MDMS CREATE ARCHIVE command, a default retention period of 365 days is used. When /RETENTION_DAYS = 0 is specified while creating an archive using MDMS CREATE ARCHIVE or modifying the attributes of an archive using MDMS SET ARCHIVE, the following message is displayed: %MDMS-I-CONFIRM, SETTING RETENTION TO 0 WILL RESULT IN VOLUMES HAVING THEIR SCRATCH DATE SET TO THE SAME DAY AS THE COMPLETION OF THE BACKUP. NO RETENTION OF THE DATA WILL TAKE PLACE. ARE YOU SURE (Y/N): Selecting Y will scratch the data on the same day as the completion of the backup; else selecting N will ignore the command with the following confirmation: %MDMS-I-CMDIGNORED, The previous command was ignored 22 The following table lists the usage of these qualifiers and the appropriate values: _________________________________________________________________ As displayed for MDMS SHOW ARCHIVE command Input speci- Qualifier EXPIRATION_ RETENTION_ Usage_________fication______specified___DATE__________DAYS_______ Definite Date format xx:xx:xx - retention /EXPIRATION_ DATE=xx:xx:xx Number of - xxxx days /RETENTION_ DAYS=xxxx Infinite NONE - retention /NOEXPIRATION For ZERO - 0 retention /RETENTION_ ____________________________DAYS=0_______________________________ The following example shows the creation of an archive using /RETENTION=0 and the display of the archive using MDMS SHOW ARCHIVE: $ MDMS CREATE ARCHIVE TEST/RETENTION=0 %MDMS-I-CONFIRM, SETTING RETENTION TO 0 WILL RESULT IN VOLUMES HAVING THEIR SCRATCH DATE SET TO THE SAME DAY AS THE COMPLETION OF THE BACKUP. NO RETENTION OF THE DATA WILL TAKE PLACE. ARE YOU SURE (Y/N):y $ MDMS SHOW ARCHIVE TEST 23 Archive: TEST Description: Access Control: NONE Owner: UNO::SYSTEM Archive Type: TAPE Catalog - - Name: ABS_CATALOG - Nodes: Consolidation - - Interval: 0007 00:00:00 - Savesets: 0 - Volumes: 0 Destination: Drives: Expiration Date: -- Location: Maximum Saves: 1 Media Type: Pool: Retention Days: 0 Volume Sets: 6.2 Errata o In the Archive Backup System for OpenVMS MDMS Reference Guide (on pages 1-19 and 1-144) and MDMS Help, the following text for the commands MDMS CREATE ARCHIVE and MDMS SET ARCHIVE: "If neither an expiration date nor retention days are specified, then the data is retained indefinitely" stands corrected as "If neither expiration date nor retention days are specified, then the data is retained for 365 days." o In the Archive Backup System for OpenVMS Guide to Operations, the display for Expiration Date in the examples specified for "Creating an Archive" (Section 9.4.2, Page 9-9) and "$ MDMS SHOW ARCHIVE SYSTEM_ BACKUPS" (in Appendix A, Page A-9) should be "-" instead of "NONE". 24 o In the Archive Backup System for OpenVMS MDMS Reference Guide (on page 1-135) and MDMS Help, the following text for the MDMS MOVE VOLUME command, Qualifiers - /PORT: "All the OPCOMS are displayed once and do not require user acknowledgement." must be replaced with: "This OPCOM displays the status on volume(s) movement and does not require user acknowledgement." 7 Media Management Configuration and Operation Once MDMS V4.4-ECO01 is installed and any conversions are performed, you might want to adjust the configuration prior to performing MDMS operations. A DCL command procedure MDMS$SYSTEM:MDMS$CONFIGURE.COM has been provided for initial installation (not a conversion from V2.9x). Refer to the Guide to Operations section of your ABS documentation set for more information on configuration and operation. 8 Converting ABS 3.* to V4.4 In ABS V4.4, the ABS Policy engine is in the MDMS Server. To upgrade to ABS V4.4, the ABS 3.x Policy Database information needs to be exported to the MDMS Database. Before running the conversion ensure that: o On the V3.x system, you have done an ABS SHOW object /FULL and kept the listing files. These will be useful when comparing the results of the conversion. o The old ABS Policy database files (ABS$DATABASE:EPCOT.DB%) are not being currently used. o ABS V4.4 and MDMS V4.4 are configured and running on all the Clients and Servers. Run the SYS$SYSTEM:ABS$CONVERT_V3_TO_V4.EXE utility to convert the ABS 3.x database to the MDMS Database. The utility exports only the highest version of the policy object. Details of new MDMS objects created are logged in ABS$CONVERT_V3_TO_V4.LOG. 25 Sample Conversion: $ RUN SYS$SYSTEM:ABS$CONVERT_V3_TO_V4.EXE Enter the Path of ABS V3.x Policy Database Files [ABS$DATABASE:] : Converting ARCHIVE Objects... Converting ENVIRONMENT Objects... Converting SAVE Objects... Converting RESTORE Objects... 9 Upgrading from ABS V2.* If you are upgrading from ABS Version 2.1, 2.1A, or 2.1B, you must execute the catalog upgrade utility prior to executing any save and restore requests using ABS Version 2.2 or higher. The catalog upgrade utility upgrades catalogs from their previous format to the new ABS Version 2.2 format. It also deletes expired summary records from those catalogs. A log file named ABS_LOG:ABS_CATALOG_V22_UPGRADE.LOG is generated with information about all of the catalog entries it has modified or deleted. The catalog upgrade utility has one update parameter: p1. The input to the p1 parameter is the name of the catalog you wish to upgrade. You can use the catalog upgrade utility to upgrade a single ABS catalog or all ABS catalogs. To upgrade an ABS single catalog, specify the catalog name to the p1 parameter. To upgrade all catalogs, enter an asterisk (*) as the wildcard character, or do not supply anything to the p1 parameter. To run the utility, use the following procedure: 1. Define the following symbol: $ CATALOG_UPGRADE :== $ABS_SYSTEM:ABS$CATALOG_UPGRADE.EXE 26 2. Enter one of the following commands: $ CATALOG_UPGRADE ! Upgrades all ABS catalogs and ! deletes all expired summary entry records. $ CATALOG_UPGRADE * ! Equivalent to example above. $ CATALOG_UPGRADE ABS_CATALOG ! Upgrades the ABS ! catalog named ABS_CATALOG and deletes all ! expired summary entry records from ! ABS_CATALOG. Restriction: The ABS catalogs must be inactive while executing the catalog upgrade utility. The catalog that is being upgraded will be locked; no save, restore, or lookup operations are allowed while the upgrade is in progress. 10 How to Remove V4.4 ABS/MDMS Files Rolling back ABS to V3.2 must only be used in EMERGENCY situations. Any save requests done since the upgrade will be lost. Any MDMS database changes done since the upgrade will be lost. If tape volumes have been allocated, deallocated, or re-used since the upgrade, these will not be reflected in the volume database after the rollback. Please use caution when deciding to do a rollback. ________________________ Note ________________________ Prior to upgrading to ABS V4.4, to be able to get back to the exact V3.2A situation you were at before the upgrade, your catalogs would have to be backed up while in a quiet state. Then, you could restore the V3.2A catalogs and they would not reflect any saves run after the V4.1 upgrade. If you do not do this, then there will be entries in the catalog which reference tapes which may be in a free state in the old database files. ______________________________________________________ If you have installed ABS V4.4 and then need to do a rollback to V3.n: 1. Shutdown ABS and MDMS. 27 2. Manually deassign the logicals ABS_CATALOG_VAOE_CLEANUP and ABS_V40_LOOKUP in the System table if defined earlier. 3. Execute the following command procedure: $ @ABS$SYSTEM:ABS$REMOVE_V40_FILES.COM 4. Reinstall ABS/MDMS V3.2A. Be sure that you do not use the STANDARD installation option and that you install both ABS and MDMS. You may optionally restore backups of your ABS catalogs. 28