Problem with shadow copy - please help

littlepuppi

ADSM.ORG Member
Joined
Feb 21, 2008
Messages
32
Reaction score
0
Points
0
Hi all, this is taken from the client which is a windows box. The box has been failing its backup for the last 3 days with this error

04/01/2008 03:21:20 ANS1999E Incremental processing of '\\hmuk00s010\c$' stopped.

04/01/2008 03:21:20 ANS1950E Backup using Microsoft volume shadow copy failed.

04/01/2008 03:21:21 ANS1512E Scheduled event 'INCR_NT' failed. Return code = 12.
04/01/2008 15:21:31 ANS1520E Failure writing to the Tivoli Storage Manager error log: errno = 28, ??????4????e????????????????????????????????????????????????????
04/01/2008 18:36:35 ANS1577I The Windows console event handler received a 'Logoff' console event.
04/01/2008 18:37:41 ANS1577I The Windows console event handler received a 'Logoff' console event.
04/02/2008 03:24:12 GatherWriterStatus(): GatherWriterStatus(...pHrResultFailure )() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE
04/02/2008 03:24:12 GatherWriterStatus(): GetWriterStatus() returns VSS_WS_FAILED_AT_PREPARE_SNAPSHOT failure for writer 'Event Log Writer'. Writer error code: [0x800423f4]
, rc=4343
04/02/2008 03:24:12 ANS1950E Backup using Microsoft volume shadow copy failed.

04/02/2008 03:24:13 ANS1512E Scheduled event 'INCR_NT' failed. Return code = 12.
04/02/2008 15:24:26 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'VssQuerySystemWriters()' returned VSS_E_WRITER_INFRASTRUCTURE
TSM return code : -1
TSM file : vssreq.cpp (8270)
04/03/2008 03:24:36 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::QueryStatus
TSM function : pAsync->QueryStatus() for caller 'VssQuerySystemWriters()' returned VSS_E_WRITER_INFRASTRUCTURE
TSM return code : -1
TSM file : vssreq.cpp (8270)
04/03/2008 04:40:25 GatherWriterStatus(): GatherWriterStatus(...pHrResultFailure )() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE
04/03/2008 04:40:25 GatherWriterStatus(): GetWriterStatus() returns VSS_WS_FAILED_AT_PREPARE_SNAPSHOT failure for writer 'Event Log Writer'. Writer error code: [0x800423f4]
, rc=4343
04/03/2008 04:40:25 ANS1950E Backup using Microsoft volume shadow copy failed.

04/03/2008 04:40:25 ANS1512E Scheduled event 'INCR_NT' failed. Return code = 12.





It looks like a client problem to me but I am unsure what to suggest..

we are on 5.3.4 clients....

Has anyone else seen this problem?
 
I believe this has been asked and answered before. Please search the Forum for an answer and explanation.
 
I had this problem two weeks ago for one of my client and it's cause by the C: drive was full. the client delete some file to make space available on the C: drive and the problem was resolve. i don't known if is the same for you but maybe check that.
 
Hi there,

It was the c:, there are other articles on it but it seems problems with shadowcopy can be caused by a variety of things and fixed in a variety of ways... Found the c: fix this morning worked here..

Thanks for the replies..
 
Me too facing the same kind of problem past few days. Better you try to update your os level(SP2).
 
hey selec

we didnt implement it. We dont have the time at this moment... but i'll post the result when it will be done... Our if you do it before me.. let me know the result..

cheers!
 
the MS patch works

we've had this problem on Win 2003 SP2, with TSM 5.4 clients. Applied this fix - http://support.microsoft.com/kb/940349 - a week ago and haven't seen the problem again since on that system. We're now planning to roll this out to the 100+ systems where we have seen this error.

Hope you have the same results!

DB
 
Hi Toxy13
after almost a month without any errors we've had the issue come back! I need to try and translate to our Windows guys what the benefit of this COM+ package is before they will install it, any idea how VSS & COM+ interact?


Cheers,
 
Yorkshire,

I haven't eliminated this error in my environment completely regardless of what TSM client version is running and what MS patch is on the node. From time to time you will see such error.

I feel that VSS is not one of the good add ons that MS introduced on their servers.
 
Last edited:
Hi ,Are the above said 2 patches do fix all of the Vss errors ?

Hi All,
Thanks for your comments.

There is a query from me.

Are the above said 2 patches do fix all of the Vss errors ? And aslo,do they cause any problem to the servers ?

Pavankumar..
 
Back
Top