Kent,
Is there any type of Domino maintenance activity that might be
happening during the entire backup window? We have seen some
similar things when the Domino server was doing some maintenance
tasks during the backup window. DP for Domino scans all of the
databases, and gets the information (like pathnames, etc.)
at the beginning. It could be that something prevented
getting the path information at the beginning, or something
has changed it by the time DP for Domino opens it for backup.
I would look at that first. If you see this continue and do
not see anything else that could be getting in the way,
please call IBM support. A trace of the problem recreation
may help determine what is going on.
Thanks,
Del
----------------------------------------------------
Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com
- Remember that the best job security is
doing a job well and doing it cheerfully.
=====================================================================
> We have a TDP-Domino incremental backup schedule on our TSM Server that
> occasionally produces this message in the client log:
>
> > Tivoli Data Protection for Lotus Domino - Version 1, Release
1,
> Level 1.0
> .
> .
> > Backing up database mail\WXY12345.nsf, 1 of 1.
> > Full: 0 Read: 0 Written: 0 Rate: 0.00 Kb/Sec
> > Backup of mail\WXY12345.nsf failed.
> > ACD0200E File (<NULL>) could not be opened for reading.
> .
> .
> This has been occurring sporadically on 3 different Domino Servers. Each
> server has several hundred active mail databases, all in the same
> subdirectory, most of which TDP backs up just fine. We see this message
> on a very small, random subset - typically just 1-3 databases on 1 of the
> 3 servers on any given night. Sometimes all 3 server backups succeed
with
> no reported errors. The subset of affected databases is somewhat random,
> except that they always seem to be near (not at) the end of the mail
> subdirectory.
>
> We perform follow-up incremental backups on any that fail, and the
> follow-up backups always work fine.
>
> We haven't been able to correlate occurrences to any client-side or
> server-side events. Does anyone know what might be causing this, and
> (hopefully) how to resolve it?
|
