TDP for Domino schedule fails, but backup completed successfully

[bonobos]

Hi there,

this is my first question in this forum. I found answers to many questions here, but now I have a problem, where I seem to find no answer so far.

I have TSM 5.4.0 on Windows Server 2003 SP1, and I have 4 Lotus Domino Clients (Lotus Notes 6.5) and Data Protection for Mail 5.3.0.2. The backup runs via the TSM scheduler that points to the dominc.cmd file, that I configured. When I execute the cmd file directly, backup works fine, over the GUI, it works fine, but via the scheduler the backup works as well fine, nevertheless I get an error message that the backup failed with return code 1. Even more strange is, that this error isn't coming every day, sometimes it completes succesfully, but most of the time not.

It's not really critcal, because the backup of ALL nsf databases works, just the daily report tells me, backup failed.

Any idea? I already opened a call at IBM, but they seem to have no answer to this problem.

Is it possible that the "schedule failed" message appears before the backup even starts?

Thank you for any help.

Regards, bonobos

dominc.log (I deleted most of the entries, but the backup of ALL .nsf database files completed successfully)


Total Domino databases inspected: 294
Total Domino databases backed up: 71
Total Domino databases excluded: 2
Total Domino backup objects expired: 0

Throughput rate: 5,728.11 Kb/Sec
Total bytes transferred: 39,706,084,814
Elapsed processing time: 6,769.33 Secs



Current date is:
Mi 19.09.2007
Current time is:
0:57

IBM Tivoli Storage Manager for Mail:
Data Protection for Lotus Domino
Version 5, Release 3, Level 0.02
(C) Copyright IBM Corporation 1999, 2005. All rights reserved.

ACD5221I The C:\Programme\Tivoli\TSM\domino\domisch1.log log file has been pruned successfully.

Starting Domino database backup...
Initializing Domino connection...
Querying Domino for a list of databases, please wait...
Logging on to the Tivoli Storage Manager server, please wait...
Querying Tivoli Storage Manager server for a list of database backups, please wait...


Backing up database admin4.nsf, 1 of 66.
Full: 3 Read: 11534336 Written: 8388608 Rate: 8,070.94 Kb/Sec
Full: 0 Read: 12058624 Written: 12058624 Rate: 7,772.94 Kb/Sec

Backup of admin4.nsf completed successfully.

Backing up database AppLog.nsf, 2 of 66.
Full: 3 Read: 7602176 Written: 5242880 Rate: 5,069.31 Kb/Sec
Full: 0 Read: 7602176 Written: 7602176 Rate: 4,916.56 Kb/Sec

Backup of AppLog.nsf completed successfully.

Backing up database catalog.nsf, 3 of 66.
Full: 3 Read: 6553600 Written: 5242880 Rate: 5,109.78 Kb/Sec
Full: 0 Read: 6553600 Written: 6553600 Rate: 4,260.99 Kb/Sec

Backup of catalog.nsf completed successfully.

Backing up database dbdirman.nsf, 4 of 66.
Full: 3 Read: 9699328 Written: 8388608 Rate: 8,023.51 Kb/Sec
Full: 0 Read: 9699328 Written: 9699328 Rate: 6,227.48 Kb/Sec

Backup of dbdirman.nsf completed successfully.

Backing up database names.nsf, 66 of 66.
Full: 3 Read: 11534336 Written: 8388608 Rate: 8,078.90 Kb/Sec
Full: 3 Read: 18874368 Written: 15728640 Rate: 7,626.61 Kb/Sec
Full: 3 Read: 24117248 Written: 20971520 Rate: 6,794.96 Kb/Sec
Full: 3 Read: 29360128 Written: 26214400 Rate: 6,377.68 Kb/Sec
Full: 3 Read: 35651584 Written: 32505856 Rate: 6,331.07 Kb/Sec
Full: 3 Read: 40894464 Written: 37748736 Rate: 6,129.70 Kb/Sec
Full: 3 Read: 46137344 Written: 42991616 Rate: 5,985.74 Kb/Sec
Full: 3 Read: 51380224 Written: 48234496 Rate: 5,877.71 Kb/Sec
Full: 0 Read: 51380224 Written: 51380224 Rate: 5,893.35 Kb/Sec

Backup of names.nsf completed successfully.


Total Domino databases inspected: 294
Total Domino databases backed up: 66
Total Domino databases excluded: 2
Total Domino backup objects expired: 0

Throughput rate: 8,164.60 Kb/Sec
Total bytes transferred: 40,486,711,788
Elapsed processing time: 4,842.59 Secs


And the error message:

09/19/2007 01:04:32 ANS1909E The scheduled command failed.
09/19/2007 01:04:32 ANS1512E Scheduled event 'DAILY_DOMINO' failed. Return code = 1.

 

[cheffern]

So you are sure that all 66 databases backed up without error?

If you find no errors, check this post out:

http://adsm.org/forum/showthread.php?t=10319

I have had a similar issue in the past for a couple of servers...
Things have since magically cleared up and are working now though...

-Chef.

 

[bonobos]

Hi,

thanks for that, I'm perfectly sure there are no error messages in the log file, and the link didn't really help ...

Any other suggestions? Should I post more log file entries?

Thank you!

 

[cheffern]

Like I said & mentioned in the link, and as far as I can see, TSM has still not reported it as an issue, but it seems to be with codes reporting wrongly.
If there are no errors in the log, guess that won't help to post it.

Can you upgrade to TDP Domino - v5.4.2 is out (assuming 32-bit here):
ftp://ftp.software.ibm.com/storage/...ivoli-data-protection/domino/Windows/x32/v542

Also, TSM Client version 5.4.1.0 is out, you may try upgrading that too:
ftp://ftp.software.ibm.com/storage/...ment/maintenance/client/v5r4/Windows/x32/v541

-Chef.

 

[bonobos]

I forgot to mention that Lotus Notes runs on Windows 2000 server, with B/A client versoin 5.3.4.

What is the latest supported TDP version for Notes 6.5 and Windows 2000?

Thank you!

 

[cheffern]

Oh - I see - your *server* is the 5.4.0 one.

Well, now, for windows 2000, I know 5.3.3 TDP for Domino would work...
Not sure if you are running windows 2003...
Check the readme in the link above to see if you can get the info from there (it will probably redirect you a few times, but keep clicking until you get what you need).

Or - check here:
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforMail.html

I would also upgrade your client though -
that is the very one I had this issue on before as well.

-Chef.

 

[Pamoramone]

Hi,

i had the sam issue using TDP for MSSQL. It seemed that TSM server established connection to TDP node, disconnected and connected the session immediately back...q ev reported that schedule failed, although backups of databases completed sucessfully. Somehow event queries couldn't be updated in activity log of TSM server. The solution to my problem was to increase the duration parameter to specified schedule.

Hope it helps.

 

[bonobos]

Aha! Thanks, I will give it a try.