Hi,
We have many servers that are in a clustered configuration (2 servers in an Active/Passive cluster) with TSM 5.5.1 installed. Each server has Veritas Storage Foundation 5.0 RP1a installed.
I've noticed that after the install of Veritas that TSM during backups will fail with VSS issues. Veritas does install it's own VSS provider.
Below are some of the issues we are seeing:
__________________________________________________________
Server1:
07/28/2009 04:10:44 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0--153097984
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : vssQuerySnapshot
TSM function : VSS[Query] VSS_OBJECT_SNAPSHOT failed, rc=0x800706be
TSM return code : 4353
TSM file : vssComUtils.cpp (308)
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : vssQuerySnapshots
TSM function : deleteSnapshot() failed
TSM return code : 102
TSM file : vssback.cpp (2414)
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : vssQuerySnapshots()
TSM function : Query Snapshots failed
TSM return code : 102
TSM file : vssback.cpp (6437)
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Verifying Local Backups Failed!
TSM return code : 102
TSM file : vssback.cpp (5736)
07/28/2009 04:11:23 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::checkWriterStatus
TSM function : GetWriterStatusCount() returned VSS_E_BAD_STATE
TSM return code : -1
TSM file : vssreq.cpp (3199)
07/28/2009 04:11:23 ANS5271E A Microsoft Volume Shadow Copy Services writer is in an invalid state before snapshot initialization.
07/28/2009 04:11:23 ANS1327W The snapshot operation for 'Server1\SystemState\NULL\System State\SystemState' failed with error code: 4353.
07/28/2009 04:11:23 ANS1228E Sending of object 'Server1\SystemState\NULL\System State\SystemState' failed
07/28/2009 04:11:23 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 04:11:23 ANS1375E The snapshot operation failed.
07/28/2009 04:11:23 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 04:11:23 ANS1512E Scheduled event 'STANDARD_0300' failed. Return code = 12.
_____________________________________________________________
Server2:
07/28/2009 00:24:23 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0--1396204094
07/28/2009 00:24:31 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE
07/28/2009 00:24:31 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'.
07/28/2009 00:24:31 ANS5271E A Microsoft Volume Shadow Copy Services writer is in an invalid state before snapshot initialization.
07/28/2009 00:24:32 ANS1327W The snapshot operation for 'Server2\SystemState\NULL\System State\SystemState' failed with error code: 4353.
07/28/2009 00:24:32 ANS1228E Sending of object 'Server2\SystemState\NULL\System State\SystemState' failed
07/28/2009 00:24:32 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 00:24:32 ANS1375E The snapshot operation failed.
07/28/2009 00:24:32 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 00:24:32 ANS1512E Scheduled event 'STANDARD_0000' failed. Return code = 12.
______________________________________________________________
Server3:
This server displays a bunch of these every night-
07/28/2009 06:57:49 ANS5250E An unexpected error was encountered.
TSM function name : fioStatFs
TSM function : Invalid file system '\\?\symantecsnapshot0\' drive type '6'
TSM return code : 131
TSM file : psfsinfo.cpp (1595)
Thanks for your help
-Jeff
We have many servers that are in a clustered configuration (2 servers in an Active/Passive cluster) with TSM 5.5.1 installed. Each server has Veritas Storage Foundation 5.0 RP1a installed.
I've noticed that after the install of Veritas that TSM during backups will fail with VSS issues. Veritas does install it's own VSS provider.
Below are some of the issues we are seeing:
__________________________________________________________
Server1:
07/28/2009 04:10:44 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0--153097984
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : vssQuerySnapshot
TSM function : VSS[Query] VSS_OBJECT_SNAPSHOT failed, rc=0x800706be
TSM return code : 4353
TSM file : vssComUtils.cpp (308)
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : vssQuerySnapshots
TSM function : deleteSnapshot() failed
TSM return code : 102
TSM file : vssback.cpp (2414)
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : vssQuerySnapshots()
TSM function : Query Snapshots failed
TSM return code : 102
TSM file : vssback.cpp (6437)
07/28/2009 04:11:06 ANS5250E An unexpected error was encountered.
TSM function name : verifyLocalBackups()
TSM function : Verifying Local Backups Failed!
TSM return code : 102
TSM file : vssback.cpp (5736)
07/28/2009 04:11:23 ANS5250E An unexpected error was encountered.
TSM function name : VssRequestor::checkWriterStatus
TSM function : GetWriterStatusCount() returned VSS_E_BAD_STATE
TSM return code : -1
TSM file : vssreq.cpp (3199)
07/28/2009 04:11:23 ANS5271E A Microsoft Volume Shadow Copy Services writer is in an invalid state before snapshot initialization.
07/28/2009 04:11:23 ANS1327W The snapshot operation for 'Server1\SystemState\NULL\System State\SystemState' failed with error code: 4353.
07/28/2009 04:11:23 ANS1228E Sending of object 'Server1\SystemState\NULL\System State\SystemState' failed
07/28/2009 04:11:23 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 04:11:23 ANS1375E The snapshot operation failed.
07/28/2009 04:11:23 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 04:11:23 ANS1512E Scheduled event 'STANDARD_0300' failed. Return code = 12.
_____________________________________________________________
Server2:
07/28/2009 00:24:23 ANS1959W Removing previous incomplete group '\System State\0\SystemState' Id:0--1396204094
07/28/2009 00:24:31 VssRequestor::checkWriterStatus: VssRequestor::checkWriterStatus() failed with hr=VSS_E_WRITERERROR_NONRETRYABLE
07/28/2009 00:24:31 ANS5269E The Microsoft Volume Shadow Copy Services writer 'Cluster Service Writer' current state (VSS_WS_STABLE) is not valid for the current operation or cannot be determined. The last error reported is '800423f4'.
07/28/2009 00:24:31 ANS5271E A Microsoft Volume Shadow Copy Services writer is in an invalid state before snapshot initialization.
07/28/2009 00:24:32 ANS1327W The snapshot operation for 'Server2\SystemState\NULL\System State\SystemState' failed with error code: 4353.
07/28/2009 00:24:32 ANS1228E Sending of object 'Server2\SystemState\NULL\System State\SystemState' failed
07/28/2009 00:24:32 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 00:24:32 ANS1375E The snapshot operation failed.
07/28/2009 00:24:32 ANS5258E An error occurred initializing a VSS request. For more information, see the TSM client error log.
07/28/2009 00:24:32 ANS1512E Scheduled event 'STANDARD_0000' failed. Return code = 12.
______________________________________________________________
Server3:
This server displays a bunch of these every night-
07/28/2009 06:57:49 ANS5250E An unexpected error was encountered.
TSM function name : fioStatFs
TSM function : Invalid file system '\\?\symantecsnapshot0\' drive type '6'
TSM return code : 131
TSM file : psfsinfo.cpp (1595)
Thanks for your help
-Jeff