Hi John, As I said earlier, I needed to double-check that earlier statement I made about the behavior. After checking the code, I found that the DOMAIN should get picked up as part of incremental processing, which is initiated *after* PRESCHEDULECMD. A bit more research (I knew this sounded familiar) found APAR IC53628. The APAR is still open. Until the APAR is closed and a fix is available, try specifying DOMAIN ALL-LOCAL in your options file (I suspect you are using the default, with no DOMAIN coded at all) and see if that makes a difference. It is the workaround documented in the APAR.
Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 10/19/2007 02:50:20 PM: > Greetings, > With all due respect to the Software Group, I think this > behavior, assuming it is "working as designed", is nuts. The whole > reason the "-preschedulecmd" option exists is to permit the customer to > perform necessary setup on his client BEFORE the backup actually starts. > Establishing the Domain is certainly part of the backup, and something > the "-preschedulecmd" option ought to execute ahead of. > Is there some logic here eluding me? > > Best Regards, > > John D. Schneider > Lead Systems Administrator - Storage > Sisters of Mercy Health Systems > 3637 South Geyer Road > St. Louis, MO 63127 > Phone: 314-364-3150 > Cell: 314-486-2359 > Email: [EMAIL PROTECTED] > > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Andrew Raibeck > Sent: Friday, October 19, 2007 3:05 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] TSM client ignores filesystems mounted by TSM > preschedule command > > > > Yes, the domain is picked up before executing PRESCHEDULECMD... > > I need to double-check this. But to get the desired behavior, my earler > suggestion still stands. > > Regards, > > Andy > > Andy Raibeck > IBM Software Group > Tivoli Storage Manager Client Product Development > Level 3 Team Lead > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] > Internet e-mail: [EMAIL PROTECTED] > > IBM Tivoli Storage Manager support web page: > http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan > ager.html > > The only dumb question is the one that goes unasked. > The command line is your friend. > "Good enough" is the enemy of excellence. > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 10/19/2007 > 12:49:35 PM: > > > Hi John, > > > > Yes, the domain is picked up before executing PRESCHEDULECMD, hence > > the behavior you see. There is no TSM setting to change this. > > > > One alternative you could try is to define a schedule with > > > > ACTION=COMMAND OBJECTS="/opt/misd/bin/importPrdVg prdaok" PRIORITY=1 > > > > Set the start time for this schedule at the same time as your backup > > schedule. Due to the higher priority, the ACTION=COMMAND schedule will > run > > first, mounting the file systems. Then the incremental schedule will > run. > > > > Note that the above is just a sketch of the idea, I assume you can > > take > it > > from here (if you wish to go this route). > > > > Regards, > > > > Andy > > > > Andy Raibeck > > IBM Software Group > > Tivoli Storage Manager Client Product Development > > Level 3 Team Lead > > Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet > > e-mail: [EMAIL PROTECTED] > > > > IBM Tivoli Storage Manager support web page: > > http://www.ibm. > > com/software/sysmgmt/products/support/IBMTivoliStorageManager.html > > > > The only dumb question is the one that goes unasked. > > The command line is your friend. > > "Good enough" is the enemy of excellence. > > > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 10/19/2007 > > 11:59:43 AM: > > > > > Greetings, > > > I have a situation where the TSM client seems to be ignoring some > > > > mounted filesystems. > > > I have a need to have a TSM preschedule command which imports > > > some volume groups and mounts their filesystems. (This data is an > > > EMC disk clone of another system, but that is immaterial). > > > Once the preschedule command mounts the filesystems, I run an > > > incremental of the system which should back up only those > > > filesystems that are the ones I just mounted, which happen to all be > > > > mounts behind the same mount point /tsmprdaok. My include/exclude > > > file is extremely > > > simple: > > > > > > exclude /.../* > > > include /tsmprdaok/.../* > > > > > > ( I know this will need to exclude other filesystems eventually, but > for > > > the sake of keeping it simple this is how it is for now.) When the > > > backup runs, it produces: > > > > > > Executing scheduled command now. > > > 10/18/07 17:45:12 > > > Executing Operating System command or script: > > > /opt/misd/bin/importPrdVg prdaok > > > 10/18/07 17:45:29 Finished command. Return code is: 0 > > > 10/18/07 17:45:29 --- SCHEDULEREC OBJECT BEGIN @27 10/18/07 > 17:42:38 > > > 10/18/07 17:45:29 Incremental backup of volume '/' > > > 10/18/07 17:45:29 Incremental backup of volume '/usr' > > > 10/18/07 17:45:29 Incremental backup of volume '/var' > > > 10/18/07 17:45:29 Incremental backup of volume '/home' > > > 10/18/07 17:45:29 Incremental backup of volume '/opt' > > > 10/18/07 17:45:29 Incremental backup of volume '/opt/emctools' > > > > > > It does not list any of the filesystems (16 in all) that are mounted > by > > > the preschedule onto /tsmprdaok. Yes, I have verified that the > > > filesystems are really being mounted by issuing a 'df' while the > backup > > > is running. > > > > > > If I issue the preschedule command manually to mount the > > > filesystems, and then run a plain scheduled backup, it produces: > > > > > > Executing scheduled command now. > > > 10/19/07 13:50:42 --- SCHEDULEREC OBJECT BEGIN @28 10/19/07 > 13:49:05 > > > 10/19/07 13:50:42 Incremental backup of volume '/' > > > 10/19/07 13:50:42 Incremental backup of volume '/usr' > > > 10/19/07 13:50:43 Incremental backup of volume '/var' > > > 10/19/07 13:50:43 Incremental backup of volume '/home' > > > 10/19/07 13:50:43 Incremental backup of volume '/opt' > > > 10/19/07 13:50:43 Incremental backup of volume '/opt/emctools' > > > 10/19/07 13:50:43 Incremental backup of volume '/tsmprdaok/epic' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok/clarity' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok/xfile' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok03' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok04' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok05' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok06' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok07' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok08' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok09' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok10' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok01' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaok02' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaokwta' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaokjrn' > > > 10/19/07 13:50:43 Incremental backup of volume > > > '/tsmprdaok/epic/prdaokaltjrn' > > > > > > What gives? Why does it work when I mount the filesystems before I > run > > > the incremental, but when the filesystems are mounted from inside a > > > preschedule command TSM ignores them? > > > > > > Asked another way, when does the TSM scheduler look at the OS and > decide > > > what filesystems exist? Does this happen before or after the > > > preschedule runs? Is there any way to control this behavior? > > > > > > > > > Best Regards, > > > > > > John D. Schneider > > > Lead Systems Administrator - Storage > > > Sisters of Mercy Health Systems > > > 3637 South Geyer Road > > > St. Louis, MO 63127 > > > Phone: 314-364-3150 > > > Cell: 314-486-2359 > > > Email: [EMAIL PROTECTED]