Classification:
Prologue:
Epilogue:
Hello everyone,
I am forwarding the following warning from ADSM client development.
Andy Raibeck
ADSM Level 2 Support
========================================
WARNING: BINDERY on NetWare 3.1x Server NOT always backed up.
A problem was accidentally introduced in ADSM Novell NetWare
Client at Version 2, Release 1, Level 0.6f (PTF IP20988). When
performing an incremental backup on the BINDERY, the bindery
will not be backed up.
Following is a description of apar IC16969.
IC16969 - On NetWare 3.1x, if the BINDERY is modified after
its initial backup, ADSM's incremental backup does
not detect the change, and never again backs up
the BINDERY.
The problem will only occur on Novell NetWare 3.1x environments.
This does not affect Novell NetWare 4.xx servers.
You can circumvent this failure by performing a SELECTIVE backup
of the BINDERY. Or if you are not using the greater than 2 gig
file support, you can regress back to level 5 code.
ADSM Client development has a fix for IC16969, and is building a
new PTF IP21123. This will be Version 2, Release 1, Level 0.7 of
the NetWare client. Once PTF 7 has passed test, it will be placed
on the anonymous FTP Server 'INDEX.STORSYS.IBM.COM', hopefully
within the next two weeks, and will be built on media for shipment.
We apologize for this error.
Dale Mark Mock
ADSM Client Development
========================================
Attached below is the text of APAR IC16969.
amr
APAR= IC16969 SER= IN INCORROUT
NETWARE CLIENT 2.1.0.6F DOES NOT AUTOMATICALLY BACK UP THE
BINDERY AFTER IT HAS BEEN MODIFIED.
ERROR DESCRIPTION:
After applying PTF IP20988 (ADSM Novell NetWare client version
2.1.0.6f), the Novell NetWare bindery is no longer backed up as
part of the normal incremental backup process.
During incremental backup with 2.1.0.6f, you will see something
like this:
Incremental backup of volume 'TURIN\BINDERY:'
Successful incremental backup of 'TURIN\BINDERY'
What it is supposed to look like is this:
Incremental backup of volume 'TURIN\BINDERY:'
Normal File--> 2,048,000 TURIN\BINDERY:/BINDERY Sent
Successful incremental backup of 'TURIN\BINDERY'
SELECTIVE backups of the bindery can still be performed
successfully; it is only during incremental backup that the
bindery is not backed up.
LOCAL FIX:
There are a couple of options:
1) Define a new schedule such that:
ACTION=SELECTIVE
OBJECTS=BINDERY
Next, associate each NetWare client with this new schedule.
2) Manually back up the bindery with the SELECTIVE BINDERY
command.
PROBLEM SUMMARY:
****************************************************************
* USERS AFFECTED: ADSM Novell Netware client on Novell 3.X *
****************************************************************
* PROBLEM DESCRIPTION: With PTF 6 (IP20988) and Novell 3.X, *
* once the BINDERY has been backed up to *
* the ADSM server, any future modification*
* to the BINDERY will not be detected, and*
* incrementals will never back it up again*
****************************************************************
* RECOMMENDATION: Apply the csd when available. Backup the *
* BINDERY with selective backups until then. *
****************************************************************
PROBLEM CONCLUSION: The fix to IC12035 in IP20988 also included
a change to the comparison of stream data. This change caused
the comparison of the current version of the BINDERY to always
equal the backed up version of the BINDERY, even when they were
no longer equal, such as after the BINDERY had been modified.
The BINDERY is never again backed up by an incremental, and
there is no error message, since ADSM thinks they are the same.
The compare code was changed to detect changes in the BINDERY.
TEMPORARY FIX: Selective backups of the BINDERY work fine,
so schedule a selective backup of the BINDERY, or periodically
issue a selective backup of the BINDERY manually.
CIRCUMVENTION: Use Selective backups to periodically backup
the BINDERY, either via a schedule or manually.
|
