Hi Lindsay,

The files in question are protected by Windows Resource Protection, and
thus are static by nature. They are not expected to change unless you
perform maintenance that causes them to be replaced; and even then, you
would need to reboot to effect the replacement. But having said that, I do
advocate as "best practice" that Open File Support with SNAPSHOTPROVIDERFS
VSS be used when backing up Windows systems.

I would also like to re-emphasize what I said earlier: the ANS1417W
messages are the result of a "safety net" -- not a "solution" -- that we
implemented for this problem. We felt it a better alternative than, for
example, doing nothing, issuing a message but doing nothing else, or
failing the backup outright. When your automobile's "check engine" (or
other warning) light comes on, you are ill advised to ignore it. The
ANS1417W message is one of TSM's "warning lights" that tells you something
needs to be addressed but TSM "has your back". The recommendation is that
you heed the advice of the warning message (for the general case) and the
flash (for the specific/known HP OpenView case).

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: 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-11-02
21:29:31:

> From: Lindsay Morris <lindsay AT TSMWORKS DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2011-11-02 21:38
> Subject: Re: Can you restore a SystemState backup when you have the
> HP OpenView problem?
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Andy, the whole point of VSS is to freeze the activity and get a
consistent
> SystemState backup.
> Right?
>
> So, if this HPOVO issue is going on, then certain files can't get
> "enumerated" to VSS.
> OK.  Then the safety-net feature backs them up to the drive instead of to
> some VSS writer.
> But aren't they still open and in use at that point?
> Thus potentially giving us an inconsistent SystemState backup?
>
> --------------------
> Lindsay Morris
> CEO, TSMworks
> Tel. 1-859-539-9900
> lindsay AT tsmworks DOT com
>
>
> On Fri, Oct 28, 2011 at 9:35 AM, Andrew Raibeck <storman AT us.ibm DOT com>
wrote:
>
> > Hi Lindsay,
> >
> > 1. The ANS1417W messages indicate that the system state files named in
> > those messages are being backed up as part of the drive they reside on,
> > which is a "safety net" we built into TSM to help ensure a viable
system
> > state backup; but they are not a "solution". The solution is to take
the
> > actions described in the flash
> > http://www.ibm.com/support/docview.wss?uid=swg21462430. The actions are
> > also described in the "local fix" section of the APAR text.
> >
> > 2. The RC 12 is an indication that some significant error occurred
during
> > the backup operation. It might be due to a problem in the system state
> > backup, or it might be due to some other problem occurring during a
> > different part of the backup. The dsmsched.log and dsmerror.log files
> > should be reviewed carefully to find out what is driving the RC 12. It
is
> > not due to the ANS1417W messages. Without knowing the cause, I would
have
> > to assume the backup is not good until proven otherwise. If indeed the
> > error occurs during system state backup, then the system state backup
is
> > NOT good.
> >
> > 3. If the backup is failing during system state backup, but the system
> > state backup indicates a completion date, then a PMR should be opened
with
> > IBM TSM support to assist in better understanding the reason.
> >
> > 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: 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-10-27
> > 21:28:34:
> >
> > > From: Lindsay Morris <lindsay AT TSMWORKS DOT COM>
> > > To: ADSM-L AT vm.marist DOT edu
> > > Date: 2011-10-27 21:30
> > > Subject: Can you restore a SystemState backup when you have the HP
> > > OpenView problem?
> > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
> > >
> > > Hi, all.
> > > I have a customer running the 6.2.2.2 client on Windows boxes that
have
> > HP
> > > OpenView installed.
> > > (See APAR IC72446,
> > http://www-01.ibm.com/support/docview.wss?uid=swg1IC72446
> > > .)
> > >
> > > As the APAR says, they see a lot of dsmsched.log messages like this:
> > >   ANS1417W Protected system state file <filename> is backed up to the
> > drive
> > > file space, not system state file space
> > > And they could ignore those.  But then the backup says it fails with
> > RC=12.
> > >
> > > On the other hand, query filespace shows the SystemState filespace as
> > backed
> > > up successfully at that time.
> > >
> > > So they don't know whether to believe the RC=12 failure, or the
> > last-backup
> > > date success indicator.
> > > And they can't easily find a test case.
> > > So, has anybody tested a SystemState restore after a similar backup
> > > "failure"?
> > > Or can Andy Raibeck say with authority that the SystemState restore
will
> > by
> > > golly work, regardless of the RC=12?
> > >
> > > Thanks for any wisdom.
> > >
> > > -- Lindsay Morris
> > > TSMworks, Inc.
> > > lindsay AT tsmworks DOT com
> > > 1-859-539-9900
> > >
> > > --
> > > --------------------
> > > Lindsay Morris
> > > CEO, TSMworks
> > > Tel. 1-859-539-9900
> > > lindsay AT tsmworks DOT com
> > >
> >
>