Problem is that I do not have a support contract at this time. Budget did
not allow for it this year.
The binaries mentioned in the reply from Legato (nsrmmd, tapeexer,
scanner) are all available in the 6.0.3 update.
Does anyone know if I can copy these 6.0.3 binaries into my 6.0.2
installation?
I can't install 6.0.3 as there is a bug that comes up with some
installations (LGTpa36998).
Thanks.
On Tue, 13 Aug 2002 08:24:54 -0400, Davina Treiber <treiber AT HOTPOP DOT COM>
wrote:
>On Mon, 12 Aug 2002 12:04:54 -0400, colin_mcfadyen AT carleton DOT ca
><colin_mcfadyen AT CARLETON DOT CA> wrote:
>
>>Davina,
>>Where would I get the hotfix? I am running 6.0.2 on W2K.
>
>Legato should supply it on request as part of the support call you have
>open with them. They sent it to me for the same problem, and it worked.
>Perhaps I was luckier with the engineer that dealt with my call, you seem
>to have been landed with one who doesn't know as much. Here is the info
>that Legato sent me about the bug.
>
>---snip---
>Here are the information about the LGTpa30132:
>
> Fact NetWorker 6.0.2
>
> Fact Backup works fine
>
> Symptom Error: 'media emergency: Bad or missing record: save set ID
>(#), low water mark (#), current offset (#)'
>
> Symptom Error: 'nsrclone: error, bad or missing record: ssid (#),
low
>(#), current (#)'
>
> Symptom Error: '(server_name): bad or missing record: ssid (#), low
>(#);, current (#)'
>
> Symptom Error: 'recover: Unable to read checksum from save stream'
>
> Symptom Error: 'recover: error recovering (filename)'
>
> Symptom Recover operation fails and results in error
>
> Cause This problem will only happen when multiplexing immediate and
>non-immediate save streams onto the same tape drive.
>
>During backup, nsrmmd is updating mediaDB together while writing to tape.
>In this problem, the information written to tape is correct, but reference
>file and record numbers are not updated properly when immediate and non-
>immediate save are multiplexing onto the same file and record on tape,
>thereby causing NetWorker to have a discrepancy between the file and
record
>number reflecting physical data on tape and those recorded in mediaDB.
>
>This problem exists on all version, except the following which contains
the
>solution:
>(1) NetWorker 5.5.3, 5.5.4 and above (for the 5.5.x series)
>(2) NetWorker 6.1.1 and above (for all future releases)
>
> Fix Known issue: resolved in LGTpa30132. Fix expected to be in
>NetWorker 5.5.3, 5.5.4 , 6.1.1 and above. If these version are not
>available yet, please contact Legato Customer Support to get temporary
>hotfixes for the desired platform, hotfixes are available only for 6.0.1,
>6.0.2 and 6.1.
>
>[Hotfix binaries]
>nsrmmd
>scanner
>tapeexer
>
>NOTE #1: The above hotfix takes care of the problem in two parts:
>-- ensure all future entries into the media database is updated correctly
>from the day this hotfix is applied;
>-- ensure nsrmmd will try its best to recover from old media database
>entries (containing invalid file and record numbers); only in exceptions
>when the available information is not sufficient to recover the data, the
>end-user is prompted to run 'scanner -i (tape_device)' or 'scanner -m
>(tape_device)' in the daemon.log, which will definitely be able to restore
>the required data, except it takes extra time to run scanner.
>
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
