Zoltan,
In this case, the vssadmin list shadowstorage results are not
deterministic; I am guessing that maybe successful shadows have not been
created, else I'd have expected it to show something (even there are no
current shadow copies).
If you haven't examined the windows event logs, it would be good to do
that. Normally with VSS related operations, I would expect the event logs
(application and / or system) to show some kind of errors besides just TSM
generated messages, around the time of the backup.
You can also try to use the diskshadow utility to test basic shadow copy
creation functionality. This might help further isolate the problem, e.g.,
remove TSM from the equation if it is an issue with the OS:
1. Create a plain text file (I called mine "script.ds") with this content:
set metadata testshadow.cab
set verbose on
begin backup
add volume c: alias testshadow
create
list shadows all
end backup
list shadows all
2. Run the script like this, from an OS prompt (cmd.exe):
diskshadow /s script.ds /l script.out
On screen you will see the diskshadow output, and it will also be saved to
script.out. The shadow copy will be only temporary, it will be deleted
(just the test shadow copy) when the script completes, as the second "list
shadows all" in the script will show.
In my case, the output is shown below. Does this work for you?
Note: When you are done, you can delete the testshadow.cab file. It is
created in the same directory from which you launched the diskshadow
command.
Note: If this is a production system, consider running the test off-hours,
or doing it on a test system that exhibits the same problem.
---------- BEGIN OUTPUT ----------
C:\>diskshadow /s script.ds /l script.out
Microsoft DiskShadow version 1.0
Copyright (C) 2007 Microsoft Corporation
On computer: WIN2008R2ENT, 12/12/2014 9:34:08 AM
-> set metadata testshadow.cab
-> set verbose on
-> begin backup
-> add volume c: alias testshadow
-> create
Excluding writer "Shadow Copy Optimization Writer", because all of its
components have been excluded.
Excluding writer "SqlServerWriter", because all of its components have been
excluded.
* Including writer "Task Scheduler Writer":
+ Adding component: \TasksStore
* Including writer "VSS Metadata Store Writer":
+ Adding component: \WriterMetadataStore
* Including writer "Performance Counters Writer":
+ Adding component: \PerformanceCounters
* Including writer "WMI Writer":
+ Adding component: \WMI
* Including writer "COM+ REGDB Writer":
+ Adding component: \COM+ REGDB
* Including writer "System Writer":
+ Adding component: \System Files
* Including writer "ASR Writer":
+ Adding component: \ASR\ASR
+ Adding component: \Volumes\Volume
{d1e1e243-2cb2-11e4-bf09-806e6f6e6963}
+ Adding component: \Disks\harddisk0
+ Adding component: \BCD\BCD
* Including writer "Registry Writer":
+ Adding component: \Registry
Alias testshadow for shadow ID {745d60db-07a6-46e3-8c16-a11810b5e682} set
as environment variable.
Alias VSS_SHADOW_SET for shadow set ID
{ad4ab0df-225a-4c7f-9b33-af7da466bda8} set as environment variable.
Inserted file Manifest.xml into .cab file testshadow.cab
Inserted file BCDocument.xml into .cab file testshadow.cab
Inserted file WM0.xml into .cab file testshadow.cab
Inserted file WM1.xml into .cab file testshadow.cab
Inserted file WM2.xml into .cab file testshadow.cab
Inserted file WM3.xml into .cab file testshadow.cab
Inserted file WM4.xml into .cab file testshadow.cab
Inserted file WM5.xml into .cab file testshadow.cab
Inserted file WM6.xml into .cab file testshadow.cab
Inserted file WM7.xml into .cab file testshadow.cab
Inserted file WM8.xml into .cab file testshadow.cab
Inserted file WM9.xml into .cab file testshadow.cab
Inserted file script.out into .cab file testshadow.cab
Querying all shadow copies with the shadow copy set ID
{ad4ab0df-225a-4c7f-9b33-af7da466bda8}
* Shadow copy ID = {745d60db-07a6-46e3-8c16-a11810b5e682}
%testshadow%
- Shadow copy set: {ad4ab0df-225a-4c7f-9b33-af7da466bda8}
%VSS_SHADOW_SET%
- Original count of shadow copies = 1
- Original volume name: \\?\Volume
{d1e1e243-2cb2-11e4-bf09-806e6f6e6963}\ [C:\]
- Creation time: 12/12/2014 9:34:20 AM
- Shadow copy device name: \\?\GLOBALROOT\Device
\HarddiskVolumeShadowCopy6
- Originating machine: WIN2008R2ENT
- Service machine: WIN2008R2ENT
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential
Number of shadow copies listed: 1
-> list shadows all
Querying all shadow copies on the computer ...
* Shadow copy ID = {745d60db-07a6-46e3-8c16-a11810b5e682}
%testshadow%
- Shadow copy set: {ad4ab0df-225a-4c7f-9b33-af7da466bda8}
%VSS_SHADOW_SET%
- Original count of shadow copies = 1
- Original volume name: \\?\Volume
{d1e1e243-2cb2-11e4-bf09-806e6f6e6963}\ [C:\]
- Creation time: 12/12/2014 9:34:20 AM
- Shadow copy device name: \\?\GLOBALROOT\Device
\HarddiskVolumeShadowCopy6
- Originating machine: WIN2008R2ENT
- Service machine: WIN2008R2ENT
- Not exposed
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential
Number of shadow copies listed: 1
-> end backup
-> list shadows all
Querying all shadow copies on the computer ...
No shadow copies found in system.
->
C:\>
---------- END OUTPUT ----------
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-12
08:40:07:
> From: Zoltan Forray <zforray AT VCU DOT EDU>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 2014-12-12 08:41
> Subject: Re: Backing up SystemState issues on Windows 2008 x32 SP2 box
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Andy,
>
> As always, we greatly appreciate your Windows expertise.
>
> The OS owner says running the "vssadmin list shadowstorage" results in
"No
> items found that satisfy the query" - Shadow Copies is disabled on both
> servers
>
> So, I gather that Shadow Copies is required to perform SystemState
backups?
>
> On Fri, Dec 12, 2014 at 7:18 AM, Andrew Raibeck <storman AT us.ibm DOT com>
wrote:
>
> > 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
> > >
> >
>
>
>
> --
> *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
>
|
