Thanks for the reply.

Looks like I am going to need 13-schedules, 1-OS, 6-incremental, 6-weeklys
(incremental and weeklys have different nodenames, dsm.opts, etc).

Do you (or someone else) have an example of how to code the
/etc/init.d/dsmcad scripts for multiple schedules (I am very new to
Solaris) ?   I did find a webpage that says I need to code an EXPORT
statement to set the DSM_CONFIG variable to point to the proper DSM.OPT
files (which are already defined). Do I just create 13-files (domsched1-12
+ dsmcad)  in /etc/init.d and each has the export statement ?




Eduardo Esteban <eesteban AT US.IBM DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/21/2005 05:56 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] Multiple Schedules for Multiple Partitions on
Solaris/Domino/TDP






Here are two options:

1)  start six schedulers each one associated with the TSM
    NODE for each partition. Just point them to the
    appropriate dsm.opt file. Then, the schedules for all
    partitions will kick-off.

2)  use one scheduler associated with anyone of the TSM
    nodes. Inside the schedule invoke domdsmc for each
    partition using the appropiate dsm.opt file
(-adsmoptfile=/partition.opt)
    and the appropriate notes user.

Note that for each scheduler only one schedule can run a time.
So if you want to run multiple domdsmc instances in parallel
from a schedule, you need to run each invocation of domdsmc in
the background.

Eduardo




"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/21/2005
11:46:14 AM:

> 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 ?