|
|
 |
OpenVMS VAXBACK03_062 OpenVMS VAX V6.2 Backup Utility ECO Summary
|
TITLE: OpenVMS VAXBACK03_062 OpenVMS VAX V6.2 Backup Utility ECO Summary
NOTE: An OpenVMS saveset or PCSI installation file is stored
on the Internet in a self-expanding compressed file.
The name of the compressed file will be kit_name-dcx_vaxexe
for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
Once the file is copied to your system, it can be expanded
by typing RUN compressed_file. The resultant file will
be the OpenVMS saveset or PCSI installation file which
can be used to install the ECO.
*OpenVMS] VAXBACK03_062 OpenVMS VAX V6.2 Backup Utility ECO Summary
Copyright (c) Compaq Computer Corporation 1998. All rights reserved.
Modification Date: 18-MAR-1999
Modification Type: Article Updated as VAXMOUN03_062 is Now Available
Modification Date: 02-DEC-1998
Modification Type: Updated Article to list the dependent ECO
VAXMOUN03_062 as unavailable until a later date.
Modification Date: 14-JAN-1999
Modification Type: Updated to indicate that the VAXY2K02_062 kit must
be installed before installation of this kit.
Modification Date: 20-NOV-1998
Modification Type: Updated ECO Kit - Supersedes VAXDISM01_062
NOTE: The documentation for this kit calls out a dependency on the
VAXMOUN03_062 remedial kit. This MOUNT kit is not currently
available but will be available at a future date.
OP/SYS: DIGITAL OpenVMS VAX
COMPONENT: BACKUP Utility
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXBACK03_062
ECO Kits Superseded by This ECO Kit: VAXBACK02_062
VAXBACK01_062
ECO Kit Approximate Size: 414 Blocks
Kit Applies To: OpenVMS VAX V6.2
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Not Applicable
Installation Rating: INSTALL_3
3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VAXY2K02_062
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
VAXSYSA02_062
VAXMTAA03_062
VAXDISM02_062
VAXINIT01_062
VAXMOUN03_062
ECO KIT SUMMARY:
An ECO kit exists for BACKUP on OpenVMS VAX V6.2. This kit addresses
the following problems:
Problems Addressed in VAXBACK03_062:
o A possible system crash occurs during Host Based RAID Unbinds
with MME code enabled. A mailbox read synchronization problem
causes the crash.
This problem only occurs when a host-based RAID UNBIND command
is done while an MME-based application is running.
The problem may occur in several different code areas of the
operating system. In order get eliminate all known instances
of this problem, the following remedial kits (or their
supersedants) will also need to be installed:
VAXSYSA02_062
VAXMTAA03_062
VAXDISM02_062
VAXINIT01_062
VAXMOUN03_062
o A process using MME could potentially "miss" the VOL1 label on
a tape. Also, a process could "hang" trying to send a message
to the MME process.
Problems Addressed in VAXBACK02_062:
o The VAXBACK01_062 remedial kit should have included the
BACKUP.CLD file to update DCLTABLES.EXE. After installing the
VAXBACK01_062 kit, users saw error messages due to a missing
/NO_INCREMENTAL qualifier.
If systems in the cluster utilize different DCLTABLES, even if
booting from a common system disk, this kit must be installed
on those systems to update the DCLTABLES.EXE.
Problems Addressed in VAXBACK01_062:
o Incremental restores may get an INCDELERR error message and
loop 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$DUA153:[GHONEY.WINDATA.NETSCAPE.CACHE]CACHE.DIR;1
-SYSTEM-W-NOSUCHFILE, no such file
o A possible ACCVIO (access violation) can occur when backing up
volume sets, particularly individual relative volumes.
o A possible loss of device cacheability when volume labels are
overwritten could occur. Tape subsystems behave differently.
Re-initializing a tape device cache value on volume switches
may result in the loss of characteristic. The type of tape
subsystem and it's stickiness of characteristic aggravates the
problem.
o One cannot append to a non-expired tape on saveset appends when
using the /EXACT_LABEL qualifier. Tape_expiration logic has a
check specifically for the (/EXACT_LABEL) qualifier.
o BACKUP may invoke a Restart operation during a network RESTORE
operation when the link breaks. BACKUP was treating the
network saveset read as if it were a tape device.
o A new qualifier was added to invoke pre-OpenVMS V6.2 /SINCE
behavior.
After enhancements to INCREMENTAL restores was done, feedback
from customers and Customer Support Centers (CSCs) indicated
that not everyone was completely pleased with the new /SINCE
behavior.
Old style (pre-OpenVMS V6.2) /SINCE behavior can be invoked by
adding the new /NO_INCREMENTAL qualifier to the BACKUP command
line.
Note that this change was implemented differently in OpenVMS
V7.1. Check the OpenVMS V7.1 release notes for that
implementation.
o After installing VAXMOUN02_062, BACKUP/NOASSIST no longer
works. However, BACKUP/ASSIST works fine.
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if the system is a member of a VMScluster, the other cluster
members should be rebooted or this kit should be installed on each
system in order to make use of the new image(s).
|
Files on this server are as follows:
|
»vaxback03_062.README
»vaxback03_062.CHKSUM
»vaxback03_062.CVRLET_TXT
»vaxback03_062.a-dcx_vaxexe
|
