2:BACKUP_STGPOOL_TP01
3:BACKUP_TP01_ARCH
5:DBBACKUP_FULL
1:BACKUP_DEVCONFIG
4:BACKUP_VOLHISTORY
6:EXPIRE_INVENTORY
11:START_STG_DP01_MIGRATION
9:START_COTP01_RECLAIM
12:STOP_COTP01_RECLAIM
10:START_LTO3_RECLAIM
13:STOP_LTO3_RECLAIM

With only 10 drives you may need to cut down the number of instances,
and thereby increase the number of available drives per instance.  The
real question is, how big is your DB per instance, and how large are
your disk/tape pools.  Those will determine which instances will need to
be trusted with more drives.

I like to setup dynamic scheduling by using if statements after looking
for remnants of previous processes.  This allows the next step to start
as soon as possible after the previous step.  However, with 6 instances
sharing 10 drives you may need to do static schedules.

See Ya'
Howard

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of ashish sharma
> Sent: Monday, February 23, 2009 7:39 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] numbering of Admin schedules
> 
> Hello,
> 
> Can anybody suggest me the best possible numbering of following
> schedules:
> 
> 1:BACKUP_DEVCONFIG
> 2:BACKUP_STGPOOL_TP01
> 3:BACKUP_TP01_ARCH
> 4:BACKUP_VOLHISTORY
> 5:DBBACKUP_FULL
> 6:EXPIRE_INVENTORY
> 7:PURGE_DB_VOLHISTORY - Not needed with DRM settings properly
configured.
> 8:PURGE_VOLHISTORY - Also may not be needed or wanted depending on
what you're deleting.
> 9:START_COTP01_RECLAIM
> 10:START_LTO3_RECLAIM
> 11:START_STG_DP01_MIGRATION
> 12:STOP_COTP01_RECLAIM
> 13:STOP_LTO3_RECLAIM
> 14:STOP_STG_DP01_MIGRATION - Hopefully you're letting it go down to 0,
and have enough drives / time to do this.
> 
> All the schedules must complete in the daytime only between 6 AM and 8
> PM.
> 
> I have 10 drives and 6 TSM instances and all schedules must run on all
> instances.I want that at anytime i have 2 drives free.Please let me
> know if
> i have missed some required information.
> 
> 
> Best Regards
> Ashish