ECO NUMBER: VMS721H1_BACKUP-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1H1 COVER LETTER 1 KIT NAME: VMS721H1_BACKUP-V0100 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: VMS721H1_UPDATE-V0500 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: o VMS721H1_MOUNT96-V0200 o VMS721H1_DRIVER-V0200 o VMS721H1_FIBRE_SCSI-V0400 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-1H1 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 13 March 2002 5 PROBLEMS ADDRESSED IN VMS721H1_BACKUP-V0100 KIT o When doing an image backup from disk to disk, if BACKUP encounters problems writing to the target device it will output an error, for example: WRITEBLOCK, error writing block xxx to DKxxx but it will continue with the backup. This can result in data corruption. BACKUP can only do mount verification for disks mounted with a file system. It cannot go through mount verification and retry the operation on DFS devices or on volumes mounted with the /FOREIGN qualifier. Thus, if a fatal error occurs, BACKUP should abort the operation as the data is inconsistent. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Allow BACKUP to avoid XFC cache. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP will not restore a directory to an ODS-5 volume if the directory name contains a '%' character. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When directories containing legal ODS-5 characters are backed up using the /NOALIAS qualifier, the directories are not saved. For example: BACKUP/NOALIAS DISK$USERS:[000000...]*.*;* NL:ods5.bck/SAVE_SET %BACKUP-W-ADNOTSAVED, alias directory DISK$USERS:[RTR_USER.ANNA.bio]Ny^_mapp.DIR;1 and its directory tree not saved -- COVER LETTER -- Page 3 13 March 2002 Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP can fail with the following error: %RMS-F-SYN, file specification syntax error Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o ODS-5 volumes, using a concealed logical and the /CONVERT parameter, generate spurious RECOVCNT and RECOVCMD messages. For example: BACKUP/CONVERT ODS5_DISK:[directory]a.dat X.SAV/SAVE/LOG %BACKUP-I-ODS5CONV, structure level 5 files will be converted to structure level 2 on SYS$SYSDEVICE: -BACKUP-I-ODS5LOSS, conversion may result in loss of structure level 5 file attributes %BACKUP-S-COPIEDAS, copied ODS5_DISK:[directory]a.dat;2 as ODS5_DISK:[SYSLOST.ADIRECTORY]A.DAT;2 %BACKUP-S-COPIEDAS, copied ODS5_DISK:[directory]a.dat;1 as ODS5_DISK:[SYSLOST.ADIRECTORY]A.DAT;1 %BACKUP-I-RECOVCNT, 1 files could not be converted into a directory on SYS$SYSDEVICE: -BACKUP-I-RECOVCMD, use the Analyze/Disk_Structure/Repair command to recover files. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o The XPQ has changed to update directory dates more often. BACKUP, during incremental backups, tests directory dates. If the MODIFIED date is greater than the BACKUP date, then all files and sub-directories under that directory are selected. This causes BACKUP to select more files than necessary. The incremental backup takes much longer to run and requires more tapes to store the data. -- COVER LETTER -- Page 4 13 March 2002 This change causes BACKUP to only select a directory if its MODIFIED date is greater than its BACKUP date and that this is either a new or renamed directory (BACKUP date was zero) Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP never accounted for a date with a year greater than 2100. Any date that had a year greater than or equal to 2100 was treated as a 21st century date (2000s). Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o If a BACKUP/LIST of a save-set is on a disk that was mounted /FOREIGN, the disk is inaccessible until it is dismounted or until BACKUP is used to create another save-set on the disk. Trying to access the disk fails with a %SYSTEM-F-VOLINV error. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When using BACKUP to copy a directory tree, a directory version limit can be improperly placed on the destination's parent directory. This can occur if the first file copied into the parent directory is a directory file which does have a directory limit. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o If ODS-2 disks are converted to ODS-5 and then converted back to ODS-2, the following problems can occur: - A BACKUP/IMAGE of the disk with the /NOALIAS switch would not pick up the directory structure of any files and directories which were created during the time the disk was an ODS-5 structure. -- COVER LETTER -- Page 5 13 March 2002 - Trying to add ACL's to previously created ODS-5 files, results in the following error: %SET-I-NOALIAS, $11$DUA431:[FMCDBS]SDBXD1.JIM;1 is an alias entry; file not modified - Previously created ODS-5 directories can be deleted when they have files in them, with no error. - An ANALYZE/DISK reports the following error on previously created ODS-5 files which have been deleted after the disk was converted: %ANALDISK-W-LOSTHEADER, file (18,1,1) JP.TXT not found in a directory Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o An incremental BACKUP RESTORE causes a BACKUP-E-INCDELERR error. Also, the operation loops continuously when attempting to perform a directory tree delete on a specific DIR filespec. The following text is an example of the message syntax: %BACKUP-E-INCDELERR, error deleting $4$DUA1:[WINDATA.NETSCAPE.CACHE]CACHE.DIR;1 -SYSTEM-W-NOSUCHFILE, no such file Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o The loss of compaction may occur on a tape device after upgrading to OpenVMS V7.2-1. This could happen in several ways. Appending of savesets to a tape volume may lead to loss of the compaction attribute for tape device or it may not be correctly enabled at the start of a tape volume. Also, use of generic SCSI tape devices may not honor the compaction device attribute after a tape label overwrite or on the initialization of continuation volumes. Images Affected: -- COVER LETTER -- Page 6 13 March 2002 - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Files with an 8388698 (4 Gb.) contiguous block size could not be copied disk to disk correctly using BACKUP. However, a file maybe saved correctly if sent to a tape saveset, depending upon the /blocksize value in the command line. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o A RMS-F-SYN error occurs when a UIC (user identification code) is specified in the BACKUP command line. 'RMS-F-SYN, file specification syntax error' is reported when the BACKUP command line is supplied with a UIC format for a directory filespec. For example: disk:[0,0] rather than disk:[000000]. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Intermittent ACCVIOs occur on a tape volume switch (continuation volumes). Depending on a number of resource issues (the number of queued I/Os [QIOs], the number of files open, or sent but failing QIOs) when a tape volume switch is needed, an ACCVIO may occur just after the new tape volume is requested. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Compaction is not enabled, if BACKUP is called with the API. Running BACKUP interactively or through batch jobs, however, enables compaction and it functions acceptably with remedial images. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE -- COVER LETTER -- Page 7 13 March 2002 o A CREDIRERR error status does not remove files from post-processing when performing a BACKUP/DELETE operation. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o A %BACKUP-W-NOFILES message may be received when backup is run from a search list and <...> is used instead of [...] as the syntax for a directory file specification. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o After upgrading to OpenVMS Alpha 7.2, a BACKUP command specifying a /LABEL of more than six characters fails with: %BACKUP-F-INVQUAVAL, value 'ISNAPBL023' invalid for /LABEL qualifier Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Provide a /NOUNLOAD qualifier fro BACKUP to carry over through continuation volumes of a tape volume set. Before this fix, there was no way to specify /NOUNLOAD in BACKUP, so controlling continuation volumes was not possible. UNLOAD/NOUNLOAD keywords have been added to the RELEASE_TAPE qualifier, with UNLOAD as the default. On the command line, the entry will look like the following: $BACKUP/RELEASE_TAPE=NOUNLOAD !NOUNLOAD the volume $BACKUP/RELEASE_TAPE=UNLOAD !UNLOAD the volume $BACKUP/RELEASE_TAPE !UNLOAD (Default) Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE -- COVER LETTER -- Page 8 13 March 2002 o Backup may abort during a /IMAGE operation of an ODS5 disk with an RMS-F-SYN error. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP is looping with a WAITIDLEBCB error after a fatal drive error. See the partial error message below: %BACKUP-E-FATALERR, fatal error on _$2$MUA561:[]DISK$REPSET2.BCK; -SYSTEM-F-DATALOST, data lost %SLS-E-BACKUPFAIL, backup directive failed %BACKUP-F-ABORT, operator requested abort on fatal error %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer %BACKUP-F-WAITIDLEBCB, attempted wait on idle buffer This may also result in an ACCVIO. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Process quota values may cause BACKUP to ACCVIO. No quota related messages are displayed. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o The following %BACKUP-F-PARSE error occurs when BACKUP has an input-specifier that is somewhat lengthy and includes a wildcard file specification with an implicit device and directory. %BACKUP-F-PARSE, error opening NET*.*;* -RMS-F-SYN, file specification syntax error where NET.*.*;* is the wildcard file specification in the input-specifier. -- COVER LETTER -- Page 9 13 March 2002 The above error will occur whenever the following BACKUP command is issued: $ BACKUP SYS$SYSTEM:NET*.*;*,SYS$SYSTEM:SYSUAF.DAT,RIGHTSLIST.DAT - TAPEDRIVE:SAVESET.BCK It appears that this is a positional problem since if the wildcard file specification appears at the beginning of the input-specifier, the problem is avoided. For example, the following BACKUP command will work successfully: $ BACKUP SYS$SYSTEM:NET*.*;*,SYS$SYSTEM:SYSUAF.DAT,RIGHTSLIST.DAT - TAPEDRIVE:SAVESET.BCK Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o When the BACKUP utility prompts for a new tape, certain invalid replies will abort the backup with a LIB-F-INPSTRTRU error. For the error to occur, a blank followed by a single letter must be entered, e.g., " y" or " r". BACKUP then repeats the prompt. If the user types the full response, i.e., "yes" or "restart", the following error message displays: %BACKUP-F-ABORT, operator requested abort on fatal error -LIB-F-INPSTRTRU, input string truncated Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o Backup cannot write journal records large enough to include longer filenames, which are allowed with ODS5 and the extended character set. Attempts to use long filenames results in a '%BACKUP-F-INVBJLSIZ, invalid record size in BACKUP journal' error. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE -- COVER LETTER -- Page 10 13 March 2002 o A /LIST/FULL operation does not include a 'seconds' output field fro file dates. Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE 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: -- COVER LETTER -- Page 11 13 March 2002 - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE o BACKUP saves incorrect file expiration times on ODS-5 disks. Images Affected: - [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 -- COVER LETTER -- Page 12 13 March 2002 - [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: - [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: -- COVER LETTER -- Page 13 13 March 2002 - [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. 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 -- COVER LETTER -- Page 14 13 March 2002 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. 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 saveset name is lowercase, BACKUP does not explicitly change the case to uppercase. When the tape is initialized the tape volume label is lowercase. Images Affected: - [SYSLIB]BACKUPSHR.EXE o Applications make repetitive calls to backup$start, eventually causing the following error message: %backup-f-insbufspace, insufficient buffer space. -- COVER LETTER -- Page 15 13 March 2002 Images Affected: - [SYSEXE]BACKUP.EXE - [SYSLIB]BACKUPSHR.EXE 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 VMS721H1_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 No reboot is necessary after successful installation of the kit. 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 -- COVER LETTER -- Page 16 13 March 2002 - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS721H1_BACKUP-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $! $ PROD INSTALL VMS721H1_BACKUP/PROD=DEC/BASE=AXPVMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit Copyright (c) Compaq Computer Corporation, 2002 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.