OpenVMS ALPBACK01_061 Alpha V6.1 Backup Utility ECO Summary
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: BACKUP Utility
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: ALPBACK01_061
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 1134 Blocks
Kit Applies To: OpenVMS Alpha V6.1
System Reboot Necessary: No
ECO KIT SUMMARY:
An ECO kit exists for BACKUP on OpenVMS Alpha V6.1. This kit addresses
the following problems:
Problems addressed in the ALPBACK01_061 kit:
o BACKUP may not incrementally restore a disk to the same
directory and file structure that existed at the time of
the most recent incremental save operation. Some of the
directories and their files may not be deleted properly,
which results additional files. This may cause restore
errors due to insufficient space on the output disk
device because the additional files are not deleted.
This problem is corrected in OpenVMS Alpha V6.2.
o When a BACKUP/LIST DDCU:*.*/SAVE_SET operation is performed
on a tape that contains many save sets, the BACKUP utility may
eventually abort with one of the following errors:
- %BACKUP-F-ALLOCMEM, error allocating virtual memory
SYSTEM-F-EXQUOTA, exceeded quota
- %BACKUP-F-INSBUFSPACE, Insufficient virtual memory to
accommodate minimum buffer count
- %BACKUP-F-BUFFERSLOST, all buffers are lost
This problem is corrected in OpenVMS Alpha V6.2.
o A listing file produced during an image backup and a listing
file created from the saveset may not be the same. One may
show several files to be at the end of a tape and the other
may show those same files to be at the beginning of the next
tape. In reality, the files only exist only at the beginning
of the next tape.
This problem is corrected in OpenVMS Alpha V6.2.
o If an existing file name version for a disk saveset is used
for a new disk saveset, BACKUP will overwrite the file. This
causes the destruction of the information in the file and
possibly the loss of data.
This problem is corrected in OpenVMS Alpha V6.2.
o If the /RECORD qualifier is used on a RESTORE operation, an
ACCVIO may occur due to improper checking of qualifiers.
This problem is corrected in OpenVMS Alpha V6.2.
o On a BACKUP file restore operation, a file gets an ACL with
the default ACE created even though there was not one before.
The [DIRECTORY] that the file was in had a default ACE. An
ACE with the DEFAULT option on a directory file causes this
ACE to be added to the restored file's ACL.
NOTE: This problem does not occur on BACKUP/image
save/restore operations.
This problem is corrected in OpenVMS Alpha V6.2.
o Behavior of OpenVMS V6.1 and OpenVMS V6.0 is different with an
input saveset that has errors. Essentially V6.1 prompts the
user for action where V6.0 did not. A problem introduced by
the change in behavior is that besides prompting for (QUIT OR
CONTINUE) on every count of 100, it also prompts on the first
error detected before any XOR recovery could be attempted on
the failing block.
This problem is corrected in OpenVMS Alpha V6.2.
o BACKUP will erroneously abort with a GENMINUS1 error on a
non-shadowed disk.
This problem is corrected in OpenVMS Alpha V6.2.
o If the /INCREMENTAL and the /SINCE qualifier are used on the
same BACKUP command line, unpredictable results occur.
This problem is corrected in OpenVMS Alpha V6.2.
o A power fail test on two tape storage devices, TA90E and TA78,
ended up with two different results. The TA78 recovered the
power fail test but the TA90E failed with:
%BACKUP-E-FATALERR, fatal error on $88$MUA3:[]TEST.BCK;
BACKUP/IMAGE/REW/VER/IGN=INTER SYS$SYSDEVICE:
$88$MUA3:TEST.BCK/SAVE
Power fail the tape storage unit during I/O.
This problem is corrected in OpenVMS Alpha V6.2.
o BACKUP does not continue on the tape that is mounted while
using the /EXACT_ORDER qualifier.
When the first BACKUP command completes on the tape_volume
label "W0" and that volume is only about half full, the second
command requests a tape with label "W0". BACKUP complains and
will not allow that label "W0" to be used. However, if the
tape is dismounted and BACKUP remounts the same tape_volume to
do the append operation or the the /EXACT_ORDER qualifier is
removed from the command line, the tape_volume is mounted
correctly.
This is illustrated by the following command file:
$ write sys$output " backup av ingtab1 "
$ backup/journal/fast -
/exclude=(pppp*.t*,*.m*,*.d*,*.sm*) -
ingtab1:[ingres.data.tds01]*.* -
tape:ingtab1.bck -
/norew -
/block=65024 -
/label=(N0,V0,W0,N1,V1,W1) -
/exact_order
$!
$ write sys$output " backup av ingtab2 "
$ backup/journal/fast -
/exclude=(pppp*.t*,*.m*,*.d*,*.sm*) -
ingtab2:[ingres.data.tds01]*.* -
tape:ingtab2.bck -
/norew -
/block=65024 -
/label=(W0,N1,V1,W1) -
/exact_order
$!
$ exit
This problem is corrected in OpenVMS Alpha V6.2.
o A RESTORE operation completes successfully, but returns the
INVRECTYP message that may cause doubt about the integrity of
the data.
This problem is corrected in OpenVMS Alpha V6.2.
o If a tape volume switch is required during a BACKUP operation
and the Media Manager (MME) is running, the BACKUP operation
will fail with:
"BACKUP-F-NOTANSI - tape is not valid ANSI format".
This problem is corrected in OpenVMS Alpha V6.2.
o OpenVMS BACKUP cannot selectively process directory structures
exceeding 8 levels. Only the BACKUP/IMAGE save and restore
will work.
This problem is corrected in OpenVMS Alpha V6.2.
INSTALLATION NOTES:
The system/cluster does not need to be rebooted after this kit is
installed.
DCLTABLES is modified with this kit to include the new BACKUP
qualifiers. To take advantage of the new syntax, without having
to logout/login, a process' copy of DCLTABLES can be updated by typing:
$ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
alpback01_061.README
alpback01_061.CHKSUM
alpback01_061.CVRLET_TXT
alpback01_061.a-dcx_axpexe
|
