ECO NUMBER: VMS721_BACKUP-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 COVER LETTER 1 KIT NAME: VMS721_BACKUP-V0200 2 KITS SUPERSEDED BY THIS KIT: None. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: o VMS721_PCSI-V0100 o VMS721_UPDATE-V0300 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-1 4.2 Files patched or replaced: o [SYSEXE]BACKUP.EXE (new image) o [SYSLIB]BACKUPSHR.EXE (new image) o [SYSUPD]BACKUP.CLD (new file) -- COVER LETTER -- Page 2 3 December 2001 5 PROBLEMS ADDRESSED IN VMS721_BACKUP-V0200 KIT o The command: $ Backup /Record /Since=Backup Disk:[000000...] Target: fails to update the backup date of the MFD directory 000000.DIR. Consequently, if the modification date of 000000.DIR is greater than the backup date, each invocation of the above command will result in the whole disk being backed-up. To correct this problem, when the user selects the whole disk via the use of a Disk:[000000...] input specifier, the backup date on the MFD (000000.DIR) will be updated. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o The following commands exhibit the listed behavior: Command: Behavior: ======== ========= $BACKUP/SINCE=[date]- Correctly selects files _/CREATED $BACKUP/SINCE=[date]- _/MODIFIED/NOINCREMENTAL Correctly selects files $BACKUP/SINCE=[date]- _/MODIFIED Incorrectly selects all files If the parent directory meets the selection criteria and the /SINCE qualifier is used, this indicates that some sort of incremental backup is to be performed. If the user does not explicitly enter the MFD or the /NOINCREMENTAL qualifier then all files in the directory will be saved and no comparison is done between the input date specifier and the files in the directory. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP saves incorrect file expiration times on ODS-5 disks. Images Affected: -- COVER LETTER -- Page 3 3 December 2001 - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Backup did not preserve the File Caching attributes during file copy operations. When a new directory or file was created, it inherited its caching attribute from its parent directory. When a new version of an existing file was created, the new file inherited its caching attribute from the highest version of the existing file. BACKUP now looks at the file header of the source file and sets the File Caching Attribute of the destination file based on that value, thus preserving the File Caching Attribute. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Japanese filename support has been added. Unicode filenames in VTF-7 encoding are now converted to Super DEC Kanji(sdeckanji) encoding. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP, in the CREATE_DIR routine, does a two part creation of a directory file. The first part creates an empty file with all the correct attributes. The second writes the first block with the correct data (0xFFFF with zeros). If a CTRL-Y interruption occurs between the create and the write phases, the directory created can be left with bad data. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP uses the XFC cache. This can impact the performance of other applications that use the XFC cache. This change keeps BACKUP from monopolizing the XFC cache. Images Affected: -- COVER LETTER -- Page 4 3 December 2001 - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When performing incremental RESTORE operations, BACKUP needs more data to make correct decisions during the incremental restore delete phase. This means that incremental SAVE operations need to save more data. To do this, BACKUP checks the modification date of the directory with the selection criteria and, if it meets this criteria, then all subdirectories and files will get selected for backup. The flexibility of invoking old style /SINCE=BACKUP behavior was added later. Recent changes to the XQP, which update modification dates for a directory file more frequently, result in more data being saved during incremental BACKUP. This may result in customers actually using the old style behavior. Testing has determined that for a /SINCE=BACKUP type operation this can cause problems. The restored disk is, at best, not as exact as it should be and worse case, is in error. For this reason, the old style /SINCE=BACKUP behavior is being disallowed. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When using the /EXCLUDE qualifier with a long list of exclusions, BACKUP fails with a %BACKUP-F-NOAPIARGS error. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP ignores files with ^00 in the filename. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When BACKUP operations are done on a system with many resources and where either the authorized privileges or SYSGEN PQL values are very large, an ACCVIO can occur. -- COVER LETTER -- Page 5 3 December 2001 Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP fails when the input saveset is referenced via a searchlist. For example: $ DIR VDE$SYSTEM:*.BCK Directory SYS$COMMON:[VDE] VDE$UPLOAD.BCK;1 Total of 1 file. $ BACKUP VDE$SYSTEM:VDE$UPLOAD.BCK/SAVE/LIST Listing of save set(s) %BACKUP-F-OPENIN, error opening CLU$COMMON:[VDE.ALP_IMAGES]VDE$UPLOAD.BCK; as input -RMS-E-FNF, file not found Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP fails with a %BACKUP-E-POSITERR, -SYSTEM-F-ILLIOFUNC error combination with RMT or INFOSERVER remotely accessed tape devices. Particularly when only a /LIST and no /DENSITY/MEDIA qualifiers are supplied in the BACKUP command line. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Systems with a large amount of physical memory can have very large page file quota values. Specifying a small blocksize, such as BACKUP/BLOCK=2048, under those circumstances may result in an ACCVIO. Removing the blocksize qualifier from the BACKUP command line or reducing process values could bypass the problem. -- COVER LETTER -- Page 6 3 December 2001 Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Doing a concurrent BACKUP/LIST with the /ENCRYPTION qualifier can result in BACKUP-E-INVATTSTR and/or BACKUP-E-INVATTSIZ error messages. Removing the /LIST qualifier while the saveset is being encrypted and doing a /LIST later on the encrypted saveset has no errors. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When a backup fails part way through, if the set is remounted using the backup target disk, the backup target disk is wrongly chosen as the master member. The valid disk is added as a copy member and the data is lost. Images Affected: - [SYSLIB]BACKUPSHR.EXE o BACKUP will create a tape volume label from the saveset name if no name is provided in the BACKUP command. When PARSE_STYLE = EXTENDED and the savset name is lowercase, BACKUP does not explicitly change the case to uppercase. When the tape is initialized the tape volume label in lowercase. Images Affected: - [SYSLIB]BACKUPSHR.EXE o BACKUP never accounted for dates with a year greater than 2100. Any date that had a year greater or equal to 2100 was treated as a 21st century (2000s). Images Affected: - [SYSLIB]BACKUPSHR.EXE -- COVER LETTER -- Page 7 3 December 2001 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_3 : To be installed by customers experiencing the problems corrected. 7 INSTALLATION INSTRUCTIONS: Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS721_BACKUP /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt This kit requires a system reboot. Compaq strongly recommends that a reboot is performed immediately after kit installation to avoid system instability If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 7.1 Special Installation Instructions: 7.1.1 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE -- COVER LETTER -- Page 8 3 December 2001 - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V2.0 - De-assign the logicals assigned For example, a sample command file to install the VMS721_BACKUP-V0200 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS721_BACKUP/PROD=DEC/BASE=AXPVMS/VER=V2.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Copyright (c) Compaq Computer Corporation, 2001 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. COMPAQ, the Compaq logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq 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. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided as is without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.