5.3 will not address this issue. The information is displayed in the TDP
log
and the console. It is strange that the backup stopped after a database
backup
failed. The TDP is designed to continue to the next database. (Could it be
that the failure occurred on the last database to backup?).

Eduardo

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/10/2005
06:14:02 AM:

> We have a situation where a Domino TDP backup failure of a "database"
> caused the entire backup to die/end prematurely !   Yet there is nothing
> in the final "ending statistics" to indicate this !

> Here are the messages from the TSM server log.

> 01/08/2005 06:06:09  ANE4991I (Session: 2917, Node: ASPEN.WEEKLY)  TDP
> Domino
> ACD5200 Data Protection for Domino: Starting backup
> of database usermail12\jshepher.nsf from server ASPEN.
> (SESSION: 2917)
> 01/08/2005 06:06:35  ANE4993E (Session: 2917, Node: ASPEN.WEEKLY)  TDP
> Domino
> ACD5202 Data Protection for Domino: Backup of
> database usermail12\jshepher.nsf from server ASPEN failed.
> (SESSION: 2917)
> 01/08/2005 06:06:35  ANE4991I (Session: 2917, Node: ASPEN.WEEKLY)  TDP
> Domino
> ACD5209 Data Protection for Domino: Selective
> database backup from server ASPEN complete.   Total Domino
> databases backed up: 1045   Total bytes transferred:
> 102636627615   Elapsed processing time: 14391.53 Secs
> Throughput rate: 6964.59 Kb/Sec (SESSION: 2917)

> This server is still using the 5.1.5.1 TDP.

> Does anyone know if this issue is addressed in the 5.3 TDP ?