Hi Bob, The excludes for DFS come from VSS, which TSM queries upon startup. This is why using PRESCHEDULECMD to stop DFS before the backup begins does not help: because by the time the client runs the PRESCHEDULECMD command, the exclude has already been set (hence my suggestion to use a separate schedule that runs prior to the backup, and to use the CAD-managed scheduler rather than the old-style scheduler service).
Adjusting the service startup order is a form of circumvention, but as you noticed, if you stop and restart the scheduler, the exclude will kick in again. One thing you could try is to use an INCLUDE in a client option set (not in the client options file) for the affected directories. I haven't tested it myself, though, so I cannot say from experience how well that will work. And depending on the number of directories involved, maintaining the INCLUDE statements might be cumbersome. But that is the only other thing I can think of. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development 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" <[email protected]> wrote on 01/16/2007 03:30:23 PM: > Andy et al: > Ironically, missed this exchange because I've been dealing with the > same problem Chris reported, > though I didn't know it at the time. > > In our situation, the user reported seeing 2.8 million files expired > after a manual backup. > > Upon much further investigaion, as best as we can determine, the user > had installed the > TSM software, and started the schedule service, before configuring the > DFS Replication. > Thus, TSM backed up the replicated file systems without issue until the > user bounced the > service (for reasons beyond this email); the subsequent backup then > honored the same > type of "Operating System" excludes Chris reported. > > Before reading Richard Sim's reply to this thread, our working > hypothesis had > been that the DFS Replication service created registry entries that the > TSM client > converts to "Operating System" excludes...which seems to be reinforced > by Richard's > reply. > > As such, the users rebooted the server in question, starting the TSM > service and > then the DFS replication without success (at least, as the Query INCLEXCL > output would indicate) > > It seems to us that what your workaround does is, by shutting down the > DFS service, > is to remove these registry entries so that the TSM scheduler, when > started by the CAD, > doesn't add the "Operating System" excludes, and thus backup the file > services. > (Our experience illustrates why the CAD has to be used to start the > scheduler, btw) > > As such, is there another way to tell the TSM client (v5.3.4.4 btw) to > ignore the > registry entries? > > (BTW, the news that a fix is possibly available soon is welcome news indeed) > > Andrew Raibeck wrote: > > Hi Chris, > > > > This is described in APAR IC50148 (searchable on the web by doing a search > > from the link in my sig). > > > > The workaround is to shut down the DFS replicator service before starting > > the scheduler (you can't use PRESCHEDULECMD for this), then run the > > backup; after the backup completes, you can restart DFS (for this you CAN > > use POSTSCHEDULECMD). > > > > One method to accomplish this would be: > > > > 1. You need to use the CAD to manage the scheduler. > > > > 2. Define a schedule on the TSM server to execute a batch script that > > shuts down the DFS service. This schedule should run at the same time or > > before the scheduled backup. Give that schedule a high priority so it runs > > FIRST. For example, if you define this schedule and the backup to run at > > 20:00, but give the batch script schedule a higher priority, it will run > > first. Then the backup will run, and you can configure a POSTSCHEDULECMD > > operation to restart DFS. > > > > The good news is that after the APAR was initially closed, further > > investigation yielded that we could fix it in the defect stream. > > Availability is currently targeted for end of this month or early next > > (subject to change at our discretion). > > > > Regards, > > > > Andy > > > > Andy Raibeck > > IBM Software Group > > Tivoli Storage Manager Client Development > > 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" <[email protected]> wrote on 01/12/2007 > > 06:49:54 AM: > > > > > >> Hi all, > >> > >> Just having problems backing up my Win2003 Server (TSM-Client 5.3.4.0, > >> TSM-Server 5.2.4.3) : > >> > >> First on this Server was DFS-Service started and the DFS-Replication > >> > > Service > > > >> (only local volumes). > >> While running normal incremental backup, all files in that replicated > >> > > area > > > >> were expired !! > >> Looking on servers include/exclude list ( dsmc q inclexcl ), I see that > >> > > those > > > >> areas are excluded by operating system (source file). > >> --> "Exclude all d:\user\...\* Operating System" > >> > >> First question : Does the operating system mark those files as system > >> > > files > > > >> or where does tsm get that information from ?? > >> Second question : Is there a possibility to remove that > >> > > exclude-statement or > > > >> to backup those areas matching the same directory-tree as former backups > >> (restore and versions). > >> > >> With stopped replication service and option "dfsbackupmntpnt no", I see > >> those files not excluded (im GUI) and can back them up. > >> (But I don't want to stop replication each time and don't know which > >> > > other > > > >> effects happen) > >> > >> Thanks for help > >> > >> Chris > >> > > > >
