Microsoft Shadow Copy Failure???

[mricca]

I have a windows 2003 client running TSM v5.3.4. My backup fails every night with the following errors. I have researched this error online and have attempted all suggested resolutions. The server has been rebooted, Cleaned out c:adsm.sys. One suggestion was to Del the filespaces on the TSM server for ASR, system state and system services.
I deleted the files and then went into the Windows services and stop the client acceptor, scheduler and the VSC. Backup still failed with same error.
The Microsoft Volume Shadow Software Provider service is set to manual.
I do see the VSS fails right before TSM fails. Is this not a TSM issue but a mircosoft issue? Any one out there no how to resolve this???? Really has become a thorn in my side!


04/03/2007 23:37:02 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'CreateSnapshotSet()' returned VSS_E_UNEXPECTED_PROVIDER_ERROR
TSM return code : -1
TSM file : vssreq.cpp (8270)
04/03/2007 23:37:02 ANS1802E Incremental backup of '\\shodmsdb130\c$' finished with 1 failure

04/03/2007 23:37:02 ANS1802E Incremental backup of '\\shodmsdb130\c$' finished with 1 failure

04/03/2007 23:37:02 ANS1950E Backup using Microsoft volume shadow copy failed.

04/03/2007 23:37:02 ANS1512E Scheduled event 'DAILY4' failed. Return code = 12.

 

[steinweo]

Hi,

Here is what I found in TSM knowledge base (IBM website):

If this service is set to manual and TSM Systemstate backups still receive the VSS_E_UNEXPECTED_PROVIDER_ERROR message please contact TSM Customer Support.

From my experience, I would guess this is a bug in the code. Therefore, I would encourage you to open a case with IBM support.

Regards, Olivier.

 

[mit2493]

VSS Issue.

I am having similar issue, I apply the fix it help some what.

Microsoft recommends the installation of hotfixes (QFEs) 833167 and 887827 for Windows 2003 VSS problems. Customers must contact Microsoft directly and request these fixes

 

[mricca]

Vss_e_unexpected_provider_error

Thanks for the information. I did log a call with IBM. Havent heard anything back yet.

 

[ubruns]

Set service to startmode "manual" at minimum

I had the same problem a time ago.

Check the "Microsoft Software Shadowing" service (or something like that, i use a german version of Win-OS) in the control panel.

The startuptype of the service must be "manual" at minimum!

If starttype is "deactivated" TSM can't start the service and will fail with an error like that you described!

You can also try to start the service in a command line:
Net Start swprv <Enter>

If you get an error 1058, the service will be deaktivated.


Greets from Germany

Ulrich Bruns

 

[blagrange]

Yeah , VSS errors are fun.

We have a script that stops the VSS services everynight through post sched. Yes, post schedule, I think the main issue is sometime the service remains running after a backup and TSM errors out when it is in this condition the next night.

Seems to work for us..

 

[mricca]

Update

Thanks for all the posts. I have been working with IBM. They had me run some test thinking that this could be a problem with the Microsoft Volume Shadowcopy Services. Below is the link to the document and test I ran
http://www-1.ibm.com/support/docview.wss?uid=swg21246748

I ran this and it looked like it completed fine.
In the meantime I changed the dsm.opt for for the client with:
DOMAIN ALL-LOCAL -systemstate -systemservices

The backups have ran fine since.

IBM now wants me to verify that the following service pack has been applied to the server.
Windows 2003 Volume Shadow Copy Service (VSS) Hotfixes for Systemstate Backup.

http://www-1.ibm.com/support/docview.wss?uid=swg21242128

I am working with our system specialist to verify this has been applied. Once it has I will remove the -systemstate -systemservices from the dsm.opt file and see what happens.

I will post the results as soon as I know anything.

 

[cheffern]

Hello

I know I provided some info on how to get around this before -
and by some miracle my issue magically went away...
only to resurface today.

I just ran the ntbackup utility as specified in the post above -
It failed right off the bat.
My C:\adsm.sys folder is mia, and there is no data on the TSM server for this node at all.

We are on Windows 2003, SP1 -
also thinking of applying the VSS Post SP1 fix packages.

Curious as to what you find for this -
Please do post.

Thanks & sorry my previous posts on this before didn't help!
-Chef.

 

[may]

it is dangerous to exclude ths System files, except you have a BMR agent in place.

so i will recommand you to, have you datas backuped, even if you get the VSS error, to just spcify the DOmain options in the rihgt order

for example,

DOMAIN systemstate
DOMAIn systemservices
DOMAIN G:
DOMAIN D:
DOMAIN C:

soit will fisrt backup the C, D and G drive before attempt the Ssistem objects backup,

nowadays i got a VSS error once a week (maximum)
here what i use to do to get ride,
Just delete (or rename then delete) the node Filespaces:
SYSTEM Services
SYSTEM STATE
ASR

and just backup them manually

it will fix yuor problem

 

[cheffern]

Now see, I would try that method you mention, May -
but I don't have any filespaces on the TSM server to delete...

 

[METRAINEE]

I get this from time to time with some of my nodes too. I have noticed no one had replied to this in a long time but normally I just reboot the node and like magic it clears? Try using the 'vssadmin list writers' command from the windows cmd to make sure all the vss writers are working properly.

 

[badbob001]

so i will recommand you to, have you datas backuped, even if you get the VSS error, to just spcify the DOmain options in the rihgt order

for example,

DOMAIN systemstate
DOMAIn systemservices
DOMAIN G:
DOMAIN D:
DOMAIN C:

soit will fisrt backup the C, D and G drive before attempt the Ssistem objects backup,

This is an interesting suggestion. Can I do this instead since all our systems have different number of drives?

DOMAIN ALL-LOCAL
DOMAIN ALL-LOCAL  -systemstate -systemservices

So that all local drives are backed up and then the system state?