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.
>