Re: numbering of Admin schedules
On Feb 24, 2009, at 1:47 AM, ashish sharma wrote: one question Richard,if i dont make the schedule for backup devconfig and backup volhistory ,then when will be the files mentioned inhc server options will get updated and how?what i know is that,we have to specify location of these files in server options file and then make a schedule with just "backup devconfig " and "backup volhist" as command which will update the file daily at the time command runs.Am i right or is there some other side also for this? As the TSM documentation says, by virtue of employing the server options, the files are automatically (re)written when changes occur in the server, which means that the operating system environment files are always current with any changes in the server. No action is necessary on the part of any human or schedule. Richard Sims
Re: numbering of Admin schedules
one question Richard,if i dont make the schedule for backup devconfig and backup volhistory ,then when will be the files mentioned inhc server options will get updated and how?what i know is that,we have to specify location of these files in server options file and then make a schedule with just "backup devconfig " and "backup volhist" as command which will update the file daily at the time command runs.Am i right or is there some other side also for this? On Tue, Feb 24, 2009 at 4:01 AM, Richard Sims wrote: > On Feb 23, 2009, at 9:03 AM, ashish sharma wrote: > >> Hello Richard, >> >> I have these parameters in Server Options file but schedule is >> needed to rin >> it daily at a specified time. ... >> > > You don't say just what that schedule is doing. A scheduled Backup > Devconfig and Backup Volumehistory in addition to the DEVCONFig and > VOLUMEHistory server options only makes sense if the scheduled > commands were writing to files other than those specified in the > server options. Whereas your server options are already each writing > to two files and keeping them fully current, there would not seem to > be a need for a scheduled command execution to update yet another file. > > what we know from afar, Richard Sims > -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
Re: numbering of Admin schedules
On Feb 23, 2009, at 9:03 AM, ashish sharma wrote: Hello Richard, I have these parameters in Server Options file but schedule is needed to rin it daily at a specified time. ... You don't say just what that schedule is doing. A scheduled Backup Devconfig and Backup Volumehistory in addition to the DEVCONFig and VOLUMEHistory server options only makes sense if the scheduled commands were writing to files other than those specified in the server options. Whereas your server options are already each writing to two files and keeping them fully current, there would not seem to be a need for a scheduled command execution to update yet another file. what we know from afar, Richard Sims
Re: numbering of Admin schedules
Hello Richard, I have these parameters in Server Options file but schedule is needed to rin it daily at a specified time.My server option file looks like below: [r...@c2x121 server-CROTSM01]# more dsmserv.opt *** IBM TSM Server options file *** Refer to dsmserv.opt.smp for other options COMMMETHOD TCPIP TCPPORT 1500 BUFPOOLSIZE 1048576 DEVCONFIG /opt/tivoli/tsm/server-CROTSM01/devcnfg.out DEVCONFIG /tsmdata/CROTSM01/volh-dev/devcnfg.out VOLHISTORY /tsmdata/CROTSM01/volh-dev/volhistory.out VOLHIST /opt/tivoli/tsm/server-CROTSM01/volhistory.out MAXSESSIONS 60 IDLETIMEOUT 60 On 2/23/09, Richard Sims wrote: > > You can simplify your list by eliminating > > 1:BACKUP_DEVCONFIG >> > > and > > 4:BACKUP_VOLHISTORY >> > > in that having DEVCONFig and VOLUMEHistory in your server options file > will cause such backups to be automatic. > > Richard Sims > -- Best Regards Ashish Sharma ST Microelectronics Ltd. 919717003853
SV: SV: numbering of Admin schedules
Hi, We where looking at Backupsets, but are stop using it because it takes to long to generate and also not flexible, because we will not keep old hardware for 10 years because of SOX, JSOX or Basel-II. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Howard Coles [howard.co...@ardenthealth.com] Skickat: den 23 februari 2009 15:24 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: SV: numbering of Admin schedules The only potential problem I see with this set, is the last line "del volhist type=all". If you have any backupsets in your library you lose track of them if they are older than your "todate" option. Setting type= to the type you want to remove (leaving off db, dbs, and backupsets) is a safer route. See Ya' Howard > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf > Of Christian Svensson > Sent: Monday, February 23, 2009 8:20 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] SV: numbering of Admin schedules > > Hi Ashish, > Here is a copy of our Admin Script for daily rutins, > But remember we have only have 1,6 TB as maximum to migrate per TSM > Server and we have 3 TSM Servers with a library manager but only 5 > drives. I'm waiting for money to PO 3 more LTO4 drives. > This is a generic script we deploy via our Library manager. > > But I hope this helps you to get some ideas how you can setup your > scripts. > And Audit Lic is only run so we can pull out current information from > "q auditocc" > > * AUDIT BACKUP INFORMATION > audit lic > * BACKUP BCK STG POOLS > Backup STGpool BCKDISKPOOL COPYPOOL maxproc=2 wait=yes > Backup STGpool BCKDIRPOOL COPYPOOL maxproc=1 wait=yes > Backup STGpool BCKTAPEPOOL COPYPOOL maxproc=1 wait=yes > Backup STGpool COMMONDISK COPYPOOL maxproc=1 wait=yes > * Backup STGpool CMNTAPEPOOL COPYPOOL maxproc=1 wait=yes > * Backup STGpool ARCHTOCPOOL COPYPOOL maxproc=1 wait=yes > * BACKUP DB AND VOLHIST > Backup db devclass=LTO3CLASS type=full wait=yes > Backup devconfig filenames=D:\tsm\devcnfg.out > Backup volhistory filenames=D:\tsm\volhist.out > * EXPIRE INVENTORY > Expire Inventory wait=yes > * MIGRATION STG POOLS > * Migrate STGPool BCKDIRPOOL lowmig=0 wait=no > Migrate STGPool BCKDISKPOOL lowmig=0 wait=yes > * Migrate STGPool COMMONDISK lowmig=0 wait=yes > * Migrate STGPool CMNTAPEPOOL lowmig=0 wait=yes > * RECLAIMATION STG POOLS > Reclaim STGPool BCKTAPEPOOL threshold=30 du=120 wait=yes > Reclaim STGPool COPYPOOL threshold=80 du=120 wait=yes > Reclaim STGPool CMNTAPEPOOL threshold=80 du=120 wait=yes > * BACKUP DB AND VOLHIST > Backup db devclass=FILECLASS type=incr wait=yes > Backup devconfig filenames=D:\tsm\devcnfg.out > Backup volhistory filenames=D:\tsm\volhist.out > delete volhist todate=today-2 type=all > > > Best Regards > Christian Svensson > > Cell: +46-70-325 1577 > E-mail: christian.svens...@cristie.se > Skype: cristie.christian.svensson > ____________ > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för ashish > sharma [ashishsharm...@gmail.com] > Skickat: den 23 februari 2009 14:38 > Till: ADSM-L@VM.MARIST.EDU > Ämne: 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 > 8:PURGE_VOLHISTORY > 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 > > 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
Re: SV: numbering of Admin schedules
The only potential problem I see with this set, is the last line "del volhist type=all". If you have any backupsets in your library you lose track of them if they are older than your "todate" option. Setting type= to the type you want to remove (leaving off db, dbs, and backupsets) is a safer route. See Ya' Howard > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf > Of Christian Svensson > Sent: Monday, February 23, 2009 8:20 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] SV: numbering of Admin schedules > > Hi Ashish, > Here is a copy of our Admin Script for daily rutins, > But remember we have only have 1,6 TB as maximum to migrate per TSM > Server and we have 3 TSM Servers with a library manager but only 5 > drives. I'm waiting for money to PO 3 more LTO4 drives. > This is a generic script we deploy via our Library manager. > > But I hope this helps you to get some ideas how you can setup your > scripts. > And Audit Lic is only run so we can pull out current information from > "q auditocc" > > * AUDIT BACKUP INFORMATION > audit lic > * BACKUP BCK STG POOLS > Backup STGpool BCKDISKPOOL COPYPOOL maxproc=2 wait=yes > Backup STGpool BCKDIRPOOL COPYPOOL maxproc=1 wait=yes > Backup STGpool BCKTAPEPOOL COPYPOOL maxproc=1 wait=yes > Backup STGpool COMMONDISK COPYPOOL maxproc=1 wait=yes > * Backup STGpool CMNTAPEPOOL COPYPOOL maxproc=1 wait=yes > * Backup STGpool ARCHTOCPOOL COPYPOOL maxproc=1 wait=yes > * BACKUP DB AND VOLHIST > Backup db devclass=LTO3CLASS type=full wait=yes > Backup devconfig filenames=D:\tsm\devcnfg.out > Backup volhistory filenames=D:\tsm\volhist.out > * EXPIRE INVENTORY > Expire Inventory wait=yes > * MIGRATION STG POOLS > * Migrate STGPool BCKDIRPOOL lowmig=0 wait=no > Migrate STGPool BCKDISKPOOL lowmig=0 wait=yes > * Migrate STGPool COMMONDISK lowmig=0 wait=yes > * Migrate STGPool CMNTAPEPOOL lowmig=0 wait=yes > * RECLAIMATION STG POOLS > Reclaim STGPool BCKTAPEPOOL threshold=30 du=120 wait=yes > Reclaim STGPool COPYPOOL threshold=80 du=120 wait=yes > Reclaim STGPool CMNTAPEPOOL threshold=80 du=120 wait=yes > * BACKUP DB AND VOLHIST > Backup db devclass=FILECLASS type=incr wait=yes > Backup devconfig filenames=D:\tsm\devcnfg.out > Backup volhistory filenames=D:\tsm\volhist.out > delete volhist todate=today-2 type=all > > > Best Regards > Christian Svensson > > Cell: +46-70-325 1577 > E-mail: christian.svens...@cristie.se > Skype: cristie.christian.svensson > ____________ > Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för ashish > sharma [ashishsharm...@gmail.com] > Skickat: den 23 februari 2009 14:38 > Till: ADSM-L@VM.MARIST.EDU > Ämne: 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 > 8:PURGE_VOLHISTORY > 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 > > 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
Re: numbering of Admin schedules
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:ads...@vm.marist.edu] On Behalf > Of ashish sharma > Sent: Monday, February 23, 2009 7:39 AM > To: ADSM-L@VM.MARIST.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
SV: numbering of Admin schedules
Hi Ashish, Here is a copy of our Admin Script for daily rutins, But remember we have only have 1,6 TB as maximum to migrate per TSM Server and we have 3 TSM Servers with a library manager but only 5 drives. I'm waiting for money to PO 3 more LTO4 drives. This is a generic script we deploy via our Library manager. But I hope this helps you to get some ideas how you can setup your scripts. And Audit Lic is only run so we can pull out current information from "q auditocc" * AUDIT BACKUP INFORMATION audit lic * BACKUP BCK STG POOLS Backup STGpool BCKDISKPOOL COPYPOOL maxproc=2 wait=yes Backup STGpool BCKDIRPOOL COPYPOOL maxproc=1 wait=yes Backup STGpool BCKTAPEPOOL COPYPOOL maxproc=1 wait=yes Backup STGpool COMMONDISK COPYPOOL maxproc=1 wait=yes * Backup STGpool CMNTAPEPOOL COPYPOOL maxproc=1 wait=yes * Backup STGpool ARCHTOCPOOL COPYPOOL maxproc=1 wait=yes * BACKUP DB AND VOLHIST Backup db devclass=LTO3CLASS type=full wait=yes Backup devconfig filenames=D:\tsm\devcnfg.out Backup volhistory filenames=D:\tsm\volhist.out * EXPIRE INVENTORY Expire Inventory wait=yes * MIGRATION STG POOLS * Migrate STGPool BCKDIRPOOL lowmig=0 wait=no Migrate STGPool BCKDISKPOOL lowmig=0 wait=yes * Migrate STGPool COMMONDISK lowmig=0 wait=yes * Migrate STGPool CMNTAPEPOOL lowmig=0 wait=yes * RECLAIMATION STG POOLS Reclaim STGPool BCKTAPEPOOL threshold=30 du=120 wait=yes Reclaim STGPool COPYPOOL threshold=80 du=120 wait=yes Reclaim STGPool CMNTAPEPOOL threshold=80 du=120 wait=yes * BACKUP DB AND VOLHIST Backup db devclass=FILECLASS type=incr wait=yes Backup devconfig filenames=D:\tsm\devcnfg.out Backup volhistory filenames=D:\tsm\volhist.out delete volhist todate=today-2 type=all Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för ashish sharma [ashishsharm...@gmail.com] Skickat: den 23 februari 2009 14:38 Till: ADSM-L@VM.MARIST.EDU Ämne: 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 8:PURGE_VOLHISTORY 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 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
Re: numbering of Admin schedules
You can simplify your list by eliminating 1:BACKUP_DEVCONFIG and 4:BACKUP_VOLHISTORY in that having DEVCONFig and VOLUMEHistory in your server options file will cause such backups to be automatic. Richard Sims
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 8:PURGE_VOLHISTORY 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 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
