There are many ways to skin a cat.
So for partitioned servers I would prefer to have separate TSM node for
each Domino partition
- each partition/node can run its schedules independently from others -
both parallelism without losing the result codes
- you can very easily split one or more partitions to another server if
the load increases

Zlatko Krastev
IT Consultant






Richard Foster <Richard.Foster AT HYDRO DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
28.10.2003 13:29
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Antwort: Re: TDP for Lotus Domino 5.1.5.1



Hi Rainer

> I will ask IBM/Tivoli support for a solution about to suprress all these
> messages being sent to TSM activity log. Maybe they have an answer. If
they
> have and you are interested I will forward that to you.

Yes, I would be interested. If you can be bothered, please send me a copy
of the answer. But my experience with Tivoli support is that this will
take
time, so I won't hold my breath. Good luck.

With regard to your comment:
> In general it seems I have to ask them what's more important
for us there is no question about it. We *have* to clear the disk log
areas
to TSM, otherwise Domino (or SAP, or Oracle) just stops. And with our
largest Domino backup taking 30 hours (1+ TB), we *cannot* afford so long
a
stop in the scheduler.

Another good reason to put the jobs in the background is to get them to
run
in parallel. The TSM scheduler only does 1 backup at a time, but we run
many Domino partitions, and have lots of tape drives. It's much more
efficient to run several backups in parallel (we do up to 8 at a time). In
fact, in our installation we cannot get through the night's backups
without
running in parallel.

Another solution is to put some of the schedule jobs into crontab, but
it's
much easier to keep an overview if all jobs are in the TSM scheduler, and
you still lose the return code to TSM.

But as I said, we run scripts and do the return code checking ourselves.
It's the only way to go for us.

Regards
Richard Foster




***********************************************************************
NOTICE: This e-mail transmission, and any documents, files or previous
e-mail messages attached to it, may contain confidential or privileged
information. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are
hereby notified that any disclosure, copying, distribution or use of
any of the information contained in or attached to this message is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender and delete the e-mail and attached
documents. Thank you.
***********************************************************************