ADSM-L

Re: [ADSM-L] How do you deal with the 7B296FB0-376B-497e-B012--9C450E1B7327-2P-1.C7483456-A289-439d-8115-601632D005A0 file

2011-07-20 10:30:32
Subject: Re: [ADSM-L] How do you deal with the 7B296FB0-376B-497e-B012--9C450E1B7327-2P-1.C7483456-A289-439d-8115-601632D005A0 file
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 20 Jul 2011 10:21:59 -0400
Andy,

FYI - the client is 6.2.3.0

Here are the messages from last nights backup:

07/19/2011 22:38:19  ANR0406I Session 26460 started for node DOGWOOD
(WinNT)
                      (Tcp/Ip 192.168.21.132(5278)). (SESSION: 26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'ASR Writer' component 'ASR' using shadow
                      copy.(SESSION: 26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'ASR Writer' component 'This is the path to
the
                      boot BCD store and the boot managers.All the files
in
                      this directory need to be backed up.' using shadow

                      copy.(SESSION: 26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'ASR Writer' component 'Select this volume
(C:) if
                      it is a critical volume.Critical volumes are those
which
                      ASR must restore.' using shadow copy.(SESSION:
26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'ASR Writer' component 'Select to include
disk #0
                      (of signature 0x5748a536) for ASR restore.' using
shadow
                      copy.(SESSION: 26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'COM+ REGDB Writer' component 'COM+ REGDB'
using
                      shadow copy.(SESSION: 26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'Registry Writer' component 'Registry' using

                      shadow copy.(SESSION: 26460)
07/19/2011 22:38:30  ANE4940I (Session: 26460, Node: DOGWOOD)  Backing up

                      object 'WMI Writer' component 'Windows Managment
                      Instrumentation' using shadow copy.(SESSION: 26460)

07/19/2011 22:38:30  ANR0406I Session 26461 started for node DOGWOOD
(WinNT)
                      (Tcp/Ip 192.168.21.132(5286)). (SESSION: 26461)
07/19/2011 22:50:28  ANE4987E (Session: 26461, Node: DOGWOOD)  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 (SESSION:
26461)
07/19/2011 22:50:28  ANE4987E (Session: 26461, Node: DOGWOOD)  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 (SESSION:
26461)



From:
Andrew Raibeck <storman AT US.IBM DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
07/20/2011 10:09 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" <ADSM-L AT VM.MARIST DOT EDU>



Hi Zoltan,

Your questions are somewhat timely. We are actually reviewing the need to
back up and/or restore these files at all, but for now, it is probably
best
to at least back them up.

The Microsoft VSS, including the Microsoft VSS snapshot provider, is
installed and enabled with all Windows OSes from Windows 2003 and up.
System state backup uses VSS. So enabling OFS with VSS as the snapshot
provider, as I suggested, doesn't require anything more than:

1. Updating the client options file

2. Restarting the client scheduler if you do not use the CAD to manage the
scheduler

Having said that, these files are part of the system state, and since
system state is backed up using VSS, I'm surprised to see them processed
as
part of the C: drive. Are there any other warning or error messages
appearing in the dsmerror.log file during system state backup?

Best regards,

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Hartford/[email protected]
Internet e-mail: storman AT us.ibm DOT 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 AT vm.marist DOT edu> wrote on 2011-07-20
09:33:20:

> From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-07-20 09:35
> Subject: Re: 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" <ADSM-L AT vm.marist DOT edu>
>
> 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
> zforray AT vcu DOT 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:
> Andrew Raibeck <storman AT US.IBM DOT COM>
> To:
> ADSM-L AT VM.MARIST DOT EDU
> 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" <ADSM-L AT VM.MARIST DOT EDU>
>
>
>
> 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/[email protected]
> Internet e-mail: storman AT us.ibm DOT 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 AT vm.marist DOT edu> wrote on 2011-07-20
> 08:59:43:
>
> > From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
> > To: ADSM-L AT vm.marist DOT edu
> > 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" <ADSM-L AT vm.marist DOT edu>
> >
> > 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
> > zforray AT vcu DOT 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

<Prev in Thread] Current Thread [Next in Thread>