This may be the problem that took us a few months to unravel (with local
Veritas support). Our problem, as indicated by Veritas, has to do with the
Notes API when it encounters a "corrupted" database on the client (will
block until NBU times out). Turn on logging on the affected Notes server
to locate the bad file (1st pass is all the files to be backed up, the
last file in the 2nd pass will be the bad file).
We're still waiting on the official patch (the number is at work and I
won't be back until Jan07/02) but I'm sure you'll be able to get
instructions etc from Veritas support.
On Mon, 24 Dec 2001, P.Govindaraju wrote:
> Your time and help is highly appreciated!
> I am using Netbackup 3.4.1 GA for lotus notes backup.
> Windows NT 4.0 SP 6 lotus notes mail server R 5.0.6 three
> Master and media server Windows NT 4.0 SP 6 No lotus notes running.
> All three nodes NT class backup works fine with OTM enabled.
> With Lotus notes agent installed and lotus notes class backup fails with
> error 41 network timed out.
> My network is 100fdx
> I tried making lotus notes machine itself a master and mdiaserver the same
> error 41.
> IT works for 1 to 2 GB backup ends with 41 error code suddenly.
> Any guess?