ADSM-L

Re: [ADSM-L] Backing up SystemState issues on Windows 2008 x32 SP2 box

2014-12-12 07:19:47
Subject: Re: [ADSM-L] Backing up SystemState issues on Windows 2008 x32 SP2 box
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 12 Dec 2014 07:18:12 -0500
Hi Zoltan,

Some random thoughts:

* Check the Windows OS application and system event logs for more details.
If something is going haywire in VSS, it is possible some clues could be
found there.

* Run the command:

   vssadmin list providers

On my Windows 7 system, for example, output looks like this:

   C:\>vssadmin list providers
   vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
tool
   (C) Copyright 2001-2005 Microsoft Corp.

   Provider name: 'Microsoft Software Shadow Copy provider 1.0'
      Provider type: System
      Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
      Version: 1.0.0.7

This is the "system" provider that comes with all Windows operating systems
and, generally speaking, is the one that should be used to back up system
state. If you have more than one provider installed -- a hardware provider
or maybe another software provider -- then maybe that provider is
configured as the default provider but does not work well for system state.
In that case, you can try adding this option to dsm.opt:

   vssusesystemprovider yes

This would force TSM to use the Microsoft system provider even if the OS is
configured to use a different provider as the default.

* Run the command:

   vssadmin list shadowstorage

And make sure there is sufficient space for shadow copy creation.

* Check if you have any other products installed that might be taking
snapshots at the same time, as this could cause conflicts in the OS that
prevent successful snapshot creation.

* If all else fails, open a PMR with support so we can explore this in more
depth.

Regards,

- Andy

____________________________________________________________________________

Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
storman AT us.ibm DOT com

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

Online documentation:
http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome
Product Wiki:
https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2014-12-11
16:16:06:

> From: Zoltan Forray <zforray AT VCU DOT EDU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 2014-12-11 16:17
> Subject: Backing up SystemState issues on Windows 2008 x32 SP2 box
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> The OS owner sent me this.  Any suggestions on how to narrow down /
resolve
> this?  My thought was to have them push for W2K8 R2  but I know there are
> some applications that have issues with R2.
>
> *The PentanaPAWS servers are both having issues with backing up the
system
> data.  Restarting the VSS services sometimes fixes the issue but it’s
never
> a finalize solution.  Do you have any insight on what can be done to fix
> this problem?  I have attached the dsmerror.log.  To temporary fix the
> issue, I have been restarting the VSS services having issues but it’s
only
> a temporary fix.  Upgrading the TSM client to 7.1.1.0 didn’t fix the
> problem.*
>
>
>
> *PENTANAPAWS8VM*
>
> *12/10/2014 00:51:52 ANS5250E An unexpected error was encountered.*
>
> *   TSM function name : BaStartSnapshot*
>
> *   TSM function      : failed to start the snapshot*
>
> *   TSM return code   : -1*
>
> *   TSM file          : ..\..\common\ba\backsnap.cpp (6730)*
>
> *12/10/2014 00:51:53 ANS5283E The operation was unsuccessful.*
>
> *12/10/2014 00:51:53 ANS1327W The snapshot operation for
> 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed with
> error code: -1.*
>
> *12/10/2014 00:51:54 ANS1228E Sending of object
> 'PENTANAPAWS8VM\SystemState\NULL\System State\SystemState' failed.*
>
> *12/10/2014 00:51:54 ANS5283E The operation was unsuccessful.*
>
>
>
> *12/10/2014 00:52:20 ANS1512E Scheduled event 'ADMINSYSTEMS' failed.
> Return code = 12.*
>
>
>
>
>
> *PENTANAPAWS8VMDEV*
>
> *12/09/2014 14:44:17 ANS2250W  A TSM core file or crash report was found:
> C:\Program Files\Tivoli\TSM\baclient\dsmcrash.dmp*
>
> *12/10/2014 00:35:16 ANS5250E An unexpected error was encountered.*
>
> *   TSM function name : BaStartSnapshot*
>
> *   TSM function      : failed to start the snapshot*
>
> *   TSM return code   : -1*
>
> *   TSM file          : ..\..\common\ba\backsnap.cpp (6730)*
>
> *12/10/2014 00:35:17 ANS5283E The operation was unsuccessful.*
>
> *12/10/2014 00:35:17 ANS1327W The snapshot operation for
> 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed with
> error code: -1.*
>
> *12/10/2014 00:35:18 ANS1228E Sending of object
> 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed.*
>
> *12/10/2014 00:35:18 ANS5283E The operation was unsuccessful.*
>
>
>
> *12/10/2014 00:36:24 ANS1512E Scheduled event 'ADMINSYSTEMS' failed.
> Return code = 12.*
>
> *12/10/2014 23:47:19 ANS5250E An unexpected error was encountered.*
>
> *   TSM function name : BaStartSnapshot*
>
> *   TSM function      : failed to start the snapshot*
>
> *   TSM return code   : -1*
>
> *   TSM file          : ..\..\common\ba\backsnap.cpp (6730)*
>
> *12/10/2014 23:47:20 ANS5283E The operation was unsuccessful.*
>
> *12/10/2014 23:47:20 ANS1327W The snapshot operation for
> 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed with
> error code: -1.*
>
> *12/10/2014 23:47:21 ANS1228E Sending of object
> 'PENTANAPAWS8VMD\SystemState\NULL\System State\SystemState' failed.*
>
> *12/10/2014 23:47:21 ANS5283E The operation was unsuccessful.*
>
>
>
> *12/10/2014 23:47:56 ANS1512E Scheduled event 'ADMINSYSTEMS' failed.
> Return code = 12.*
>
>
> --
> *Zoltan Forray*
> TSM Software & Hardware Administrator
> BigBro / Hobbit / Xymon 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
>