Andy,

Thanks for the tips/suggestion.  I will pass it on.

Unfortunately, folks around here don't seem to want to use OFS/low-level
drivers,  especially since it usually requires a reboot when
installing/updating.

Do you know if this filename will be consistent so that I can exclude it
from this and future systems?  Or is this some recent voodoo that M$ has
pushed down in "black Tuesday" updates?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
[email protected] - 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:
Andrew Raibeck <[email protected]>
To:
[email protected]
Date:
07/20/2011 09:20 AM
Subject:
Re: [ADSM-L] How do you deal with the
7B296FB0-376B-497e-B012--9C450E1B7327-2P-1.C7483456-A289-439d-8115-601632D005A0
file
Sent by:
"ADSM: Dist Stor Manager" <[email protected]>



Hi Zoltan,

I recommend using OFS to back up Windows systems, with VSS as snapshot
provider. Add the following to your dsm.opt file:

SNAPSHOTPROVIDERFS VSS

That will ensure that all "in-use" files are backed up, as well as ensure
a
"crash-consistent" backup of the drive.

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: [email protected]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager


"ADSM: Dist Stor Manager" <[email protected]> wrote on 2011-07-20
08:59:43:

> From: Zoltan Forray/AC/VCU <[email protected]>
> To: [email protected]
> Date: 2011-07-20 09:09
> Subject: How do you deal with the 7B296FB0-376B-497e-
> B012--9C450E1B7327-2P-1.C7483456-A289-439d-8115-601632D005A0 file
> Sent by: "ADSM: Dist Stor Manager" <[email protected]>
>
> This is more for Andy R but all suggestions/feedback are appreciated.
>
> I have a new Windows 2K8 node that is having heartburn with these
errors:
>
> 07/11/2011 14:50:40 ANS1228E Sending of object
> '\\domino37\c$\Windows\System32\7B296FB0-376B-497e-
> B012-9C450E1B7327-2P-0.C7483456-A289-439d-8115-601632D005A0'
> failed
> 07/11/2011 14:50:40 ANS4987E Error processing
> '\\domino37\c$\Windows\System32\7B296FB0-376B-497e-
> B012-9C450E1B7327-2P-0.C7483456-A289-439d-8115-601632D005A0':
> the object is in use by another process
> 07/11/2011 14:50:40 ANS1228E Sending of object
> '\\domino37\c$\Windows\System32\7B296FB0-376B-497e-
> B012-9C450E1B7327-2P-1.C7483456-A289-439d-8115-601632D005A0'
> failed
> 07/11/2011 14:50:40 ANS4987E Error processing
> '\\domino37\c$\Windows\System32\7B296FB0-376B-497e-
> B012-9C450E1B7327-2P-1.C7483456-A289-439d-8115-601632D005A0':
> the object is in use by another process
> 07/11/2011 14:53:29 ANS1802E Incremental backup of '\\domino37\c$'
> finished with 2 failure
>
> Googling I found this (thank you M$ for finding a new way to screw up
TSM
> backups)
>
> http://answers.microsoft.com/en-us/windows/forum/windows_vista-
> security/where-do-the-files7b296fb0-376b-497e-b012/
> f16b2a1e-5136-408b-a792-fc25c3eb358a
>
> If I read this correctly and since I was able to Google
> \7B296FB0-376B-497e-B012--9C450E1B7327-2P-1.C7483456-
> A289-439d-8115-601632D005A0
>  and find specific entries,  this new file is going to be somewhat
> persistent?
>
> How do I not try to backup this file?   Should I just add that long
string
> into the CLOPTSET that I push down to all Windows clients?
> Zoltan Forray
> TSM Software & Hardware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> [email protected] - 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

Reply via email to