Well, I'm stumped. There has to more going on here than meets the eye.
Some suggestions:
1. Check your dsmerror.log and dsmsched.log files for any warning or error
messages that might relate to this.
2. Is there any preschedulecmd script running that does something related
to this directory or the product(s) that use it?
3. What apps put data in C:\temp? Check to see what other activity
(outside of TSM) goes on with the files in that dir, to make sure that
they aren't being, say, moved at the time the TSM backup runs.
4. Implement pre- and postschedlecmd scripts to do a "dir" for c:\temp
before and after the TSM backup (just to make sure the files are really
there when the backup runs).
Best regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
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 AT VM.MARIST DOT EDU> wrote on 01/06/2009
02:53:13 PM:
> [image removed]
>
> Re: Windows temp directory inadvertently excluded..sort of
>
> Shawn Drew
>
> to:
>
> ADSM-L
>
> 01/06/2009 02:55 PM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Correct, just normal directories,
> Aside from the connectivity and log options, the following are the lines
> in the dsm.opt:
>
> DOMAIN ALL-LOCAL
> include.fs c: FILELEVEL=dynamic
> include.fs d: FILELEVEL=dynamic
>
>
> Also, remember, the directories get backed up and updated every night,
if
> applicable. But the files don't. It's behaving as if there was a
> "exclude c:\temp\...\*" somewhere.
>
> Regards,
> Shawn
> ________________________________________________
> Shawn Drew
>
>
>
>
> Internet
> Robert.Clark AT PROVIDENCE DOT ORG
>
> Sent by: ADSM-L AT VM.MARIST DOT EDU
> 01/06/2009 02:28 PM
> Please respond to
> ADSM-L AT VM.MARIST DOT EDU
>
>
> To
> ADSM-L
> cc
>
> Subject
> Re: [ADSM-L] Windows temp directory inadvertently excluded..sort of
>
>
>
>
>
>
> Silly question, but c:\Temp on both boxes are normal directories/folders
> on C:\ and not mounted file systems?
>
> What is your domain statement set to?
>
> Thanks, [RC]
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Shawn Drew
> Sent: Tuesday, January 06, 2009 9:02 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Windows temp directory inadvertently excluded..sort of
>
> I'm trying to track down exactly why the c:\temp directory wasn't backed
> up on 2 Windows servers, and only these 2 Windows servers
>
> OS: Win2003
> TSM: 5.3.4
>
> - When trying to restore some data in the C:\Temp directory (On both
> servers), we found that the directory structures were all backed up, but
> none of the files were.
> - The logs show the directories being updated/backed up, but no files
> - The q inclexcl doesn't show anything to indicate why these files might
> be excluded
> - The GUI backup doesn't have any "X's" or that
> "circle-with-line-through-it" symbol which typically denotes exclusions
> - running "dsmc i c:\temp" DOES back up the files, but then get expired
> when the scheduled nightly backup runs.
> - The only thing I noticed that makes this different from the other
> hosts.
> In the dsm.opt there are 2 options:
> include.fs c: FILELEVEL=dynamic
> include.fs d: FILELEVEL=dynamic
>
> I think these are remnants from trying to troubleshoot snapshot issues.
> I can't imagine why this would exclude the temp directory. I'm removing
> these lines tonight to see what happens.
>
> Any ideas?
>
> Regards,
> Shawn
> ________________________________________________
> Shawn Drew
>
>
> This message and any attachments (the "message") is intended solely for
> the addressees and is confidential. If you receive this message in
> error, please delete it and immediately notify the sender. Any use not
> in accord with its purpose, any dissemination or disclosure, either
> whole or partial, is prohibited except formal approval. The internet can
> not guarantee the integrity of this message. BNP PARIBAS (and its
> subsidiaries) shall (will) not therefore be liable for the message if
> modified. Please note that certain functions and services for BNP
> Paribas may be performed by BNP Paribas RCC, Inc.
>
>
> DISCLAIMER:
> This message is intended for the sole use of the addressee, and may
> contain information that is privileged, confidential and exempt from
> disclosure under applicable law. If you are not the addressee you are
> hereby notified that you may not use, copy, disclose, or distribute to
> anyone the message or any information contained in the message. If you
> have received this message in error, please immediately advise the
sender
> by reply email and delete this message.
|
