OpenVMS VAXBACK04_071 OpenVMS VAX V7.1 Backup Utility ECO Summary
TITLE: OpenVMS VAXBACK04_071 OpenVMS VAX V7.1 Backup Utility ECO Summary
Modification Date: 14-JUL-1999
Modification Type: Updated Kit: Supersedes VAXBACK04_071
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.
Copyright (c) Compaq Computer Corporation 1998, 1999. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENT: BACKUP Utility
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXBACK04_071
ECO Kits Superseded by This ECO Kit: VAXBACK03_071
VAXBACK02_071
VAXBACK01_071
ECO Kit Approximate Size: 522 Blocks
Kit Applies To: OpenVMS VAX V7.1
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: N/A
Installation Rating: 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:
VAXY2K01_071
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
VAXSYSA02_071
VAXDISM01_071
VAXINIT01_071
VAXMOUN05_071
VAXMTAA01_071
ECO KIT SUMMARY:
An ECO kit exists for BACKUP on OpenVMS VAX V7.1. This kit addresses
the following problems:
PROBLEMS ADDRESSED IN VAXBACK04_071:
o An %BACKUP-F-BADOPTVAL error can occur when using an
Identifier String for a BACKUP/BY_OWNER qualifier value.
For example:
$ BACKUP SOURCE:*.*/BY_OWNER=USER TAPE:A.BCK/SAV
%BACKUP-F-BADOPTVAL, invalid callable interface option
value, argument position 7, option type = 59, option
value = 2147549409
Image(s) Affected: [SYSEXE]BACKUP.EXE; [SYSLIB]BACKUPSHR.EXE
o Using OpenVMS VAX V7.1 [SSB] as the basis for API definitions,
ONLY add new definitions (since V7.1).
An obsolete reference to STRUCTURE (keyword/qualifier) was
also removed.
o The following problems are corrected by backporting fixes
from V7.2:
1. BACKUP/SINCE and /BEFORE produces unexpected results.
2. BACKUP/OWNER=FRED results in an error.
3. A process dump cannot be produced if BACKUP fails.
4. Using BACKUP/ENCRYPT in BATCH results in a
%BACKUP-F-ENCNOTSUP error.
5. The default for /BEFORE=(value) is now the same as
/SINCE= (value).
Image(s) Affected:
- [SYSEXE]BACKUP.EXE
- [SYSLIB]BACKUPSHR.EXE
- [CLD]BACKUP.CLD
PROBLEMS ADDRESSED IN VAXBACK03_071:
o After installing a new MOUNT kit (VAXMOUN02_062), BACKUP
/NOASSIST no longer behaved correctly (/ASSIST still worked).
Changes to MOUNT then returned status that BACKUP did not
expect. The problem occurred especially for tapes with
continuation volumes.
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_071
VAXMTAA01_071
VAXDISM01_071
VAXINIT01_071
VAXMOUN04_071
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.
o Although a VAX version of Snapshot Services is not yet
available, new feature compatibility was done for forthcoming
product Snapshot Services for OpenVMS. The changes enable a
form of incremental backup when the source device is a
short-lived snapshot of a volume.
This feature involves the addition of the /SNAPSHOT qualifier,
which when used in conjunction with /SINCE=BACKUP (or even
/BEFORE=BACKUP) on a snapshot source volume, causes BACKUP to
fetch the date to be used as the base comparison date from the
snapshot device driver rather than use the backup date
recorded on the source volume. The date is fetched from the
snapshot device driver when backing up snapshots, rather than
the original volume. A sample normal sequence of events is:
1. Create SNAPSHOT/RECORD DWS of original volume
2. BACKUP/SNAPSHOT/SINCE=BACKUP DWS to tape
3. Delete SNAPSHOT DWS
This sequence will cause a copy of the original volume to be
taken and attached to a new device, with both the original and
the copy then being independent. Thus, the original volume
can remain in normal operation while the backup operation
takes place on the copy. If the normal backup regime makes
use of incremental backups, the backup dates will be stored on
the snapshot (copy) of the volume, not the original and will
be lost when the snapshot is deleted.
However, if the /RECORD qualifier is added to the snapshot
creation, then the snapshot device driver will record the
creation date of the new snapshot on the original volume and
will copy the previous snapshot creation date from the
original volume onto the new snapshot. If the backup
operation is done with /SNAPSHOT and /SINCE=BACKUP, BACKUP
will fetch the date of creation of the previous snapshot from
the new snapshot. BACKUP will then use this date as the
comparison date and so will only backup files that have
changed since the previous snapshot was created.
o An access violation occurs in BACKUP if MME is installed/enabled.
The ACCVIO happens because status information in a common block
is no longer available due to the memory being freed by the time
that the EXIT_HANDLER is invoked.
o The DCL command "SET PROCESS/DUMP" failed. The BACKUP API did
not allow error signals to reach beyond its entry point. Only
a status code was returned.
PROBLEMS ADDRESSED IN VAXBACK02_071:
o An %BACKUP-F-WAITIDLEBCB error is possible when a media error
is encountered with the Backup utility.
PROBLEMS ADDRESSED IN VAXBACK01_071 KIT:
o Four major problems occurred:
1. 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$DUA1:[WINDATA.NETSCAPE.CACHE]CACHE.DIR;1
-SYSTEM-W-NOSUCHFILE, no such file
2. A possible ACCVIO (access violation) can occur when backing
up volume sets, particularly individual relative volumes.
3. A problem with the /OWNER and /BY_OWNER qualifiers occurred
with an error message such as:
BACKUP/LOG TEST.BCK/SAVE/BY_OWNER=[20,0] X.X
%BACKUP-F-BADOPTVAL, invalid callable interface option
value, argument position 7, option type = 59,
option value = 1048576
4. Since upgrading to OpenVMS V7.1 from OpenVMS V6.2, BACKUP
procedures could not be run. BACKUP fails with an ACCVIO
error PC=0000000000000000. Although the problem matches
the contents of the article listed below, workarounds
described in the article failed at the customer site.
Identifier: CTI_SRC970415001958 VEGA Item Number: 55327
Title:[OpenVMS] BACKUP Fails W/ACCVIO At PC=0000000000000000
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).
Copyright (c) Compaq Computer Corporation 1998. All rights reserved.
Modification Date: 01-MAR-99
Modification Type: Updated Information:
VAXY2K01_071 must be installed before this kit.
OP/SYS: DIGITAL OpenVMS VAX
COMPONENT: BACKUP Utility
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VAXBACK03_071
ECO Kits Superseded by This ECO Kit: VAXBACK02_071
VAXBACK01_071
ECO Kit Approximate Size: 522 Blocks
Kit Applies To: OpenVMS VAX V7.1
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: N/A
Installation Rating: 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:
VAXY2K01_071
In order to receive all the corrections listed in this
kit, the following remedial kits should also be installed:
VAXSYSA02_071
VAXDISM01_071
VAXINIT01_071
VAXMOUN04_071
VAXMTAA01_071
ECO KIT SUMMARY:
An ECO kit exists for BACKUP on OpenVMS VAX V7.1. This kit addresses
the following problems:
PROBLEMS ADDRESSED IN VAXBACK03_071:
o After installing a new MOUNT kit (VAXMOUN02_062), BACKUP
/NOASSIST no longer behaved correctly (/ASSIST still worked).
Changes to MOUNT then returned status that BACKUP did not
expect. The problem occurred especially for tapes with
continuation volumes.
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_071
VAXMTAA01_071
VAXDISM01_071
VAXINIT01_071
VAXMOUN04_071
NOTE: The documentation for this kit calls out a dependency on the
VAXMOUN04_071 remedial kit. This MOUNT kit is not currently
available but will be released at a future date
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.
o Although a VAX version of Snapshot Services is not yet
available, new feature compatibility was done for forthcoming
product Snapshot Services for OpenVMS. The changes enable a
form of incremental backup when the source device is a
short-lived snapshot of a volume.
This feature involves the addition of the /SNAPSHOT qualifier,
which when used in conjunction with /SINCE=BACKUP (or even
/BEFORE=BACKUP) on a snapshot source volume, causes BACKUP to
fetch the date to be used as the base comparison date from the
snapshot device driver rather than use the backup date
recorded on the source volume. The date is fetched from the
snapshot device driver when backing up snapshots, rather than
the original volume. A sample normal sequence of events is:
1. Create SNAPSHOT/RECORD DWS of original volume
2. BACKUP/SNAPSHOT/SINCE=BACKUP DWS to tape
3. Delete SNAPSHOT DWS
This sequence will cause a copy of the original volume to be
taken and attached to a new device, with both the original and
the copy then being independent. Thus, the original volume
can remain in normal operation while the backup operation
takes place on the copy. If the normal backup regime makes
use of incremental backups, the backup dates will be stored on
the snapshot (copy) of the volume, not the original and will
be lost when the snapshot is deleted.
However, if the /RECORD qualifier is added to the snapshot
creation, then the snapshot device driver will record the
creation date of the new snapshot on the original volume and
will copy the previous snapshot creation date from the
original volume onto the new snapshot. If the backup
operation is done with /SNAPSHOT and /SINCE=BACKUP, BACKUP
will fetch the date of creation of the previous snapshot from
the new snapshot. BACKUP will then use this date as the
comparison date and so will only backup files that have
changed since the previous snapshot was created.
o An access violation occurs in BACKUP if MME is installed/enabled.
The ACCVIO happens because status information in a common block
is no longer available due to the memory being freed by the time
that the EXIT_HANDLER is invoked.
o The DCL command "SET PROCESS/DUMP" failed. The BACKUP API did
not allow error signals to reach beyond its entry point. Only
a status code was returned.
PROBLEMS ADDRESSED IN VAXBACK02_071:
o An %BACKUP-F-WAITIDLEBCB error is possible when a media error
is encountered with the Backup utility.
PROBLEMS ADDRESSED IN VAXBACK01_071 KIT:
o Four major problems occurred:
1. 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$DUA1:[WINDATA.NETSCAPE.CACHE]CACHE.DIR;1
-SYSTEM-W-NOSUCHFILE, no such file
2. A possible ACCVIO (access violation) can occur when backing
up volume sets, particularly individual relative volumes.
3. A problem with the /OWNER and /BY_OWNER qualifiers occurred
with an error message such as:
BACKUP/LOG TEST.BCK/SAVE/BY_OWNER=[20,0] X.X
%BACKUP-F-BADOPTVAL, invalid callable interface option
value, argument position 7, option type = 59,
option value = 1048576
4. Since upgrading to OpenVMS V7.1 from OpenVMS V6.2, BACKUP
procedures could not be run. BACKUP fails with an ACCVIO
error PC=0000000000000000. Although the problem matches
the contents of the article listed below, workarounds
described in the article failed at the customer site.
Identifier: CTI_SRC970415001958 VEGA Item Number: 55327
Title:[OpenVMS] BACKUP Fails W/ACCVIO At PC=0000000000000000
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).
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
vaxback04_071.README
vaxback04_071.CHKSUM
vaxback04_071.CVRLET_TXT
vaxback04_071.a-dcx_vaxexe
vaxback04_071.CVRLET_TXT
|
