Re: [ADSM-L] vss errors on tsm backup

As hinted in the messages, looking at the Windows Event logs (application
and system) might provide some useful clues.

Are there any hardware providers in the mix? If yes, it might be worth
trying to back up system state with this option in dsm.opt:

VSSUSESYSTEMPROVIDER YES

Best 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 2015-09-09
11:07:46:

> From: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Date: 2015-09-09 11:11
> Subject: Re: vss errors on tsm backup
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> The link has these instructions for 2008 / 2012.
> I use them all the time, they work. :-)
>
> *The "DISKSHADOW Prereq Test" (Windows 2008 and 2012)*
>
> VSS functionality can be validated with the Windows 2008 and/or Windows
> 2012 Server embedded command DISKSHADOW. The following are the DISKSHADOW
> tests recommended before any Tivoli Storage Manager components are
> installed.
> 1. Test Non-persistent shadow copy creation and deletion.
> a. Run "diskshadow" on a command window
> b. DISKSHADOW> add volume f: (Database volume)
> c. DISKSHADOW> add volume g: (Log volume)
> d. DISKSHADOW> create
> e. DISKSHADOW>list shadows all (This may take a few minutes)
> f. DISKSHADOW>delete shadows all
>
> Note: Volumes f: and g: represent the Exchange Database and log volumes.
> Repeat this 4 times. Verify the Windows Event Log contains no errors.
>
> 2. Test Persistent shadow copy creation and deletion.
> a. Run "diskshadow" on a command window
> b. DISKSHADOW>set context persistent
> c. DISKSHADOW> add volume f: (Database volume)
> d. DISKSHADOW> add volume g: (Log volume)
> e. DISKSHADOW> create
> f. DISKSHADOW>list shadows all (This may take a few minutes)
> g. DISKSHADOW>delete shadows all
>
> Note: Volumes f: and g: represent the Exchange Database and log volumes.
> Repeat this 4 times. Verify the Windows Event Log contains no errors.
>
> 3. Test Non-persistent transportable shadow copy creation and deletion
> a. Run "diskshadow" on a command window
> b. DISKSHADOW>set context persistent
> c. DISKSHADOW>set option transportable
> d. DISKSHADOW>begin backup
> e. DISKSHADOW> add volume f: (Database volume)
> f. DISKSHADOW> add volume g: (Log volume)
> g. DISKSHADOW>set metadata c:\metadata\exchangemeta.cab (specify the path
> where you want the metadata stored)
> h. DISKSHADOW> create
> i. DISKSHADOW>end backup
> j. Manually copy the exchangemeta.cab file from the source server to the
> offload server and run these two commands:
>
>    DISKSHADOW>LOAD METADATA <path to>exchangemeta.cab
>       DISKSHADOW>IMPORT
>
> k. DISKSHADOW>list shadows all (This may take a few minutes)
> l. DISKSHADOW>delete shadows all
>
>
> On Wed, Sep 9, 2015 at 5:03 PM, Lee, Gary <glee AT bsu DOT edu> wrote:
>
> > Great for 2003, but as stated, this is a win 2008-r2/64 machine.
> >
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
> > Stefan Folkerts
> > Sent: Wednesday, September 09, 2015 9:12 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: [ADSM-L] vss errors on tsm backup
> >
> > I would run this for the c: drive:
> >
> > Here is the VSHADOW pre-testing that is recommended BEFORE Tivoli
Storage
> > Manager is even installed:
> >
> > *The "VSHADOW Prereq Test" (Windows 2003)*
> >
> >    1. Test non-persistent shadow copy creation and deletion.
> >    Run "VSHADOW k: l:“ (where k: and l: are the Exchange Server
database
> >    and log volumes).
> >    Repeat this 4 times.
> >    Check the Windows Event Log to check to make sure things look good.
> >    2. Test persistent shadow copy creation and deletion.
> >    Run "VSHADOW -p k: l:“ (where k: and l: are the Exchange Server
database
> >    and log volumes).
> >    You may need to run "VSHADOW -da" to remove this if you don't have
> >    enough space.
> >    Repeat this 4 times.
> >    Check the Windows Event Log to check to make sure things look good.
> >    3. Note: This test is for VSS Hardware Provider environments only.
> >    Test non-persistent transportable shadow copy creation and deletion
(VSS
> >    Hardware Provider environments only).
> >    Run "VSHADOW -t=export.xml k: l:“ (where k: and l: are the Exchange
> >    Server database and log volumes).
> >    On the machine you have set aside for offload, run "VSHADOW
> >    -i=export.xml“.
> >    Check the Windows Event Log to check to make sure things look good.
> >
> >
> > Once all of these things are working perfectly, you are ready for the
> > Tivoli Storage Manager code to be installed and tested.
> >
> > it's from : https://www-304.ibm.com/support/docview.wss?uid=swg21403456
> >
> > You most likely have a VSS error that the TSM client can't work around,
it
> > needs to be fixed first, be sure to install all 2003 the hotfixes for
VSS.
> >
> >
> > On Wed, Sep 9, 2015 at 3:04 PM, Lee, Gary <glee AT bsu DOT edu> wrote:
> >
> > > Client machine running win 2008-r2 64 bit under hyper-v.
> > > Tsm client 6.4.2.
> > >
> > > Several errors all related to vss.  Extract from dsmerror.log
follows.
> > >
> > > 09/09/2015 06:30:20 ANS5250E An unexpected error was encountered.
> > >    TSM function name : AddToSnapshotSet
> > >    TSM function      : 'AddToSnapshotSet failed with error
> > > VSS_E_UNEXPECTED_PROVIDER_ERROR. 0X8004230F'
> > >    TSM return code   : -2147212529
> > >    TSM file          : ..\..\common\winnt\asrutil.cpp (2281)
> > > 09/09/2015 06:30:20 ANS5250E An unexpected error was encountered.
> > >    TSM function name : AddToSnapshotSet
> > >    TSM function      : 'AddToSnapshotSet failed with error
> > > VSS_E_UNEXPECTED_PROVIDER_ERROR. 0X8004230F'
> > >    TSM return code   : -2147212529
> > >    TSM file          : ..\..\common\winnt\asrutil.cpp (2281)
> > > 09/09/2015 06:30:21 ANS5250E An unexpected error was encountered.
> > >    TSM function name : BackupComplete()
> > >    TSM function      : 'BackupComplete() failed with error
> > > VSS_E_BAD_STATE. 0X80042301'
> > >    TSM return code   : -2147212543
> > >    TSM file          : ..\..\common\winnt\asrutil.cpp (2493)
> > > 09/09/2015 06:30:21 ANS1468E Backing up Automated System Recovery
(ASR)
> > > files failed.  No files will be backed up.
> > >
> > > 09/09/2015 06:30:22 ANS1327W The snapshot operation for 'C:' failed
with
> > > error code: -1.
> > > 09/09/2015 06:30:22 ANS5250E An unexpected error was encountered.
> > >    TSM function name : BaStartSnapshot
> > >    TSM function      : initializeSnapshotSet() failed, check
Microsoft
> > > Application event log for VSS errors
> > >    TSM return code   : -1
> > >    TSM file          : ..\..\common\ba\backsnap.cpp (6368)
> > > 09/09/2015 06:30:22 ANS5258E Microsoft volume shadow copy snapshot
> > > initialization failed.
> > > 09/09/2015 06:30:22 ANS5283E The operation was unsuccessful.
> > > 09/09/2015 06:30:22 ANS1377W The client was unable to obtain a
snapshot
> > of
> > > '\\libmysql\c$'. The operation will continue without snapshot
support.
> > >
> > > Not sure where to go from here.  Many articles on the web about win
2003,
> > > haven't found much for this.
> > >
> >
>