TSM TDP BACKUP !!! fails again Need Help

[zolagbr]

Hi All,

I am now getting the error message below and will appreciate any comments or advice on resolving this.

'VSS_E_OBJECT_NOT_FOUND'
TSM return code : 131
TSM file : vssreq.cpp (3819)
05/11/2012 12:42:28 ANS5250E An unexpected error was encountered.
TSM function name : vssDeleteSnapshot
TSM function : deleteSnapshot() failed
TSM return code : 131
TSM file : vssback.cpp (2605)
05/11/2012 12:42:28 ANS1449W A non-critical, unexpected error was encountered.
Deletion of a snapshot(Set/Volume) failed. Probable cause, snapshot does not exists anymore. Continuing Process...
TSM snapShot ID : {570d2431-74d0-493e-bce6-4bd4c82e3135}
TSM function name : vssDeleteSnapshot()
TSM function : Deletion of Snapshot failed, Continuing...
TSM return code : 0
TSM file : vssback.cpp (6405)
05/11/2012 12:43:27 ANS0361I DIAG: Error starting schedule service: CadSchedName registry value is empty
05/11/2012 12:43:27 ANS1977E Dsmcad schedule invocation was unsuccessful. This command will be tried again in 10 minutes.
05/11/2012 12:45:08 ANS5252E TSM attempted to execute a system command which failed.
command : "C:\Tivoli\TSM\baclient\excvssic.exe"

C:\adsm.sys\vss_staging\DLY_LONEXCH01\XXX.XXX.XXX.42\20120511124226\30a3e687-2260-4375-8ff8-34213eb31857_Audit.txt
rc : -1032
05/11/2012 12:45:08 ANS5250E An unexpected error was encountered.
TSM function name : baHandleSnapshot
TSM function : BaHandleSystemPostSnapshotCmd() failed.
TSM return code : -1032
TSM file : backsnap.cpp (4167)
05/11/2012 12:45:08 ANS1327W The snapshot operation for '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\' failed with

error code: -1032.
05/11/2012 12:45:08 Return code -1032 unknown


Regards

 

[Mita201]

what TDP you are using (what are you backuping)?
What command you use to do it?

 

[zolagbr]

Hey Mita,

TDP and BA Client are 6.3 and i am using the excfull command script below

"tdpexcc backup * full /tsmoptfile=dsm.opt /logfile=excsch.log >> excfull.log"

Thanks for your assistance

Regards

 

[Trident]

Hi,

Read the file C:\adsm.sys\vss_staging\DLY_LONEXCH01\XXX.XXX.XXX. 42\20120511124226\30a3e687-2260-4375-8ff8-34213eb31857_Audit.txt

It will give you a clue where to start.

 

[tariq.kaifi]

Are all system state writers in good condition?

 

[zolagbr]

Hey Tarik,

All the system state writers are in good condition....any other ideas pls


Regards

 

[tariq.kaifi]

Trident's post.

Btw, it appears the logs are from scheduled backup. What happens when you take a manual backup?

 

[Trident]

The logs will indicate if there is something wrong with the exchange db.

 

[zolagbr]

So far I have only been successful in running manual backup of the local drive and system state. I just ran the vssadmin list writer and I got this error message on one

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {8ea18b24-4e64-417c-837d-92ec773319d4}
State: [1] Stable
Last error: Retryable error

 

[tariq.kaifi]

Sorry, just realised I asked you to check "system writer" instead of VSS writers.

Trigger a manual TDP backup and keep checking VSS writers status during the run. Is all writers stable all along or something happens in between?

 

[vayala]

Hi, I'm facing the same issue with the VSS writers, I've rebooted the server, then the backup ran good. I leave the backup to run normally with the scheduler and then it fails again with the VSS errors, any solution for this?

Regards,