Hi Zoltan, A couple of things:
1. If your TSM clients use multiple nodes or options files, make sure that the "q inclexcl" you do is for the same node and options file that are used during the backup; and that the scheduled backup is using the intended node name and options file. 2. Check the order in which the include/exclude statements appear. Once a given file matches an include or exclude statement, then the file is included or excluded as appropriate. Subsequent include or exclude statements are not considered. The excerpts you posted don't show the non-temp include and exclude statements, so we can't tell if there might be some other statement overriding your excludes. For example, if you this in dsm.opt: ... EXCLUDE *:\...\Temp\...\* INCLUDE *:\Documents and Settings\...\* ... Then with bottom-up processing, a temp file in the "Documents and Settings" directory will match the INCLUDE statement, at which time the file will be backed up. Best regards, Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Hartford/IBM@IBMUS Internet e-mail: stor...@us.ibm.com IBM Tivoli Storage Manager support web page: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 2012-04-17 14:43:11: > From: Zoltan Forray/AC/VCU <zfor...@vcu.edu> > To: ADSM-L@vm.marist.edu, > Date: 2012-04-17 14:46 > Subject: Re: Why are my "temp" files being backed up? > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > I should have mentioned that nothing has changed on this server for a long > time, including the cloptset. My thought is if it is "expiring" it, then > it must have backed it up. > > I was simply researching the memory problems (see bottom of my initial > post) when I saw these in the dsmsched.log. > > I am wondering if the journaling process overrides/ignores the exclusion > process. > > > Zoltan Forray > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > zfor...@vcu.edu - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html > > > > From: "Clark, Margaret" <mcl...@sddpc.org> > To: ADSM-L@VM.MARIST.EDU > Date: 04/17/2012 02:32 PM > Subject: Re: [ADSM-L] Why are my "temp" files being backed up? > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > What you show here is not a log of files being backed up, but being > expired. If you had just modified the options file to add the exclusion, > you'd see a log like this. > If that's the case, then check the log again tomorrow. > - Margaret > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Zoltan Forray/AC/VCU > Sent: Tuesday, April 17, 2012 11:00 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Why are my "temp" files being backed up? > > Windows 2003 server - 6.3 client. This machine is very memory > constrained. 43M files. Using journaling and MEMORYEFFICIENT > DISKCACHEMETHOD. > > When I use the CLI and do a "q inclexcl", I see: > > <snippage> > Exclude All *\temp\* Server > <more snippage> > Exclude All *\...\Temp\...\* Server > > So I know the cloptset is working. > > Nothing in the dsm.opt: > > NODENAME ACIPENSER.VCU.EDU > TCPSERVERADDRESS TSMLINUX8.UCC.VCU.EDU > PASSWORDACCESS GENERATE > SCHEDLOGR 30 D > ERRORLOGR 30 D > *MEMORYEFFICIENT YES > MEMORYEFFICIENT DISKCACHEMETHOD > diskcachelocation g:\tsm_cache > *SNAPSHOTPROVIDER VSS > VERBOSE > > Yet I see entries like: > > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26194-1656.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26195-1656.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26196-4900.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26197-1656.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26198-4900.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26199-4900.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26200-1656.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26201-4900.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26202-1656.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26203-1656.mem [Sent] > 04/17/2012 04:20:18 Retry # 1 Expiring--> 0 > \\acipenser\c$\Documents and Settings\wshuart\Local > Settings\Temp\list26204-1656.mem [Sent] > > in the dsmsched.log file? > > What am I missing? > > I am also dealing with some kind of "memory" issue eventhough I am using > memoryefficient: > > > 04/15/2012 18:24:54 ANS1030E The operating system refused a TSM request > for memory allocation. > 04/15/2012 18:24:54 ANS1512E Scheduled event 'RESEARCH-COMPUTING' failed. > Return code = 12. > 04/16/2012 17:08:01 ANS1814E Unable to start the scheduled event > 'ACIPENSER.SQL.DAILY' > 04/16/2012 17:08:01 ANS1815E Either the window has elapsed or the schedule > has been deleted > 04/16/2012 18:29:55 ANS1999E Incremental processing of '\\acipenser\i$' > stopped. > > 04/16/2012 18:29:56 ANS1030E The operating system refused a TSM request > for memory allocation. > 04/16/2012 18:29:56 ANS1512E Scheduled event 'RESEARCH-COMPUTING' failed. > Return code = 12. > > Any thoughts on this? >
