I have a question about setting up multiple TDP backup schedules for
multiple partitions on Solaris systems.

Here is the scenario:

Solaris 5.9 - TSM 5.3.1.12
6-partitions - each running their own instance of Domino/Notes.
Each partition has 6-Domino usermail filesystems.

Through testing, we determined that Domino is toooo slow to attempt to
backup each partition, in toto (takes multiple hours just to interrogate
the Domino server to determine what to backup).

So, each partition has a script that initiates the "domdsmc_partitionname"
command, 6-times, once for each usermail directory (yes, that is 25-backup
runs per server per day, not counting weekly full backups).

The DSM.SYS for each partition has 13-stanzas (6-daily, 6-weekly, 1-OS).

So, I created 7-backup schedules, 1-COMMAND for each Domino partition and
1-INCREMENTAL for the OS.  I associated all of these with the base-system
TSM node.

When I bounce the scheduler (dsmcad), the dsmsched.log only shows the
backup schedule for the first partition.  I am assuming this is because it
is the next/soonest schedule.

Once this backup schedule kicks-off, what happens with the next schedule
for the next partition ?

Is TSM going to not run/look for the next schedule until the first backup
cycle completes or will it get the next schedule as soon as the first one
kicks off ?

Or is there a way to run multiple schedulers and then associate the
individual schedules with each partition/node ?