Thanks for the reply.

You are saying exactly what I said/read and felt. We did go through IBM
and Notes support and they couldn't come up with anything tangible to
explain the hangs.

People were constantly complaining about the slow-downs/hangs. When we
tracked them for a while, we noticed they always occured during the
archlog dumps being performed, every 2-hours.

I think IBM was the one who suggested the MOUNTWAIT parm (the Domino
person handled this).  I told them that none of the management classes go
straight to tape. *ALL* backups (logs, daily, weekly) go to disk, first,
and this parm shouldn't make any difference.

When we added the MOUNTWAIT=NO, the complaints stopped and our monitoring
showed no more "seizures".

I too realize it doesn't make sense but it did make a noticible
difference.




Del Hoobler <hoobler AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/01/2006 03:37 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Domino TDP and MountWait parm






Hi Zoltan,

The "/MOUNTWAIT=NO" says that if the backups need
to be stored on offline media that would require a
tape mount, then don't proceed with the operation.

If what you say is correct... and all log backups are going
to disk and not tape, using the "/MOUNTWAIT=NO" parameter
should have absolutely no effect. I have a feeling that the
"accident and experimentation" are probably more of a
"coincidence"... but you never know.
I would recommend placing a call with the IBM Support Team
so they can help you can get this sorted out.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/01/2006
01:42:22 PM:

> Solaris 9 - TSM 5.3.0 client
> Domino TDP - 5.3.0
>
> We have been having lot of issues with Domino servers/processes
> hanging/stalling when the TDP backups kick off, especially when doing
> transaction log dumping.  Everything would seize up while the
transaction
> logs were dumped.  We also have been noticing slowdowns caused by the
> actual backups.
>
> Through accident and experimentation, we discovered this can
minimize/stop
> these hangups by adding the /MOUNTWAIT=NO parm to the DOMDSMC command.
>
> This makes no sense since the book describes this as "waiting for tape
> resources" when in fact, all backups to all Domino systems go directly
to
> a 2TB disk LZ.
>
> Can someone (Del ?) please explain this and what are the consequences of
> using this parm and why do I seem to need it ?