Results 1 to 6 of 6

Thread: VSS Errors

  1. #1
    Newcomer
    Join Date
    Mar 2009
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default VSS Errors

    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 (30
    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

  2. #2
    Member JeanSeb's Avatar
    Join Date
    Aug 2008
    Location
    Quebec City
    Posts
    181
    Thanks
    6
    Thanked 2 Times in 2 Posts

    Default

    Are you required to backup system states ?
    If not, just remove the associated stanza from dsm.opt, and you'll be good to go.

    The attitude of IBM regarding third party VSS provider, (understandably) is: "not our problem, we only support Microsoft VSS, check with your vendor".
    Last edited by JeanSeb; 07-29-2009 at 08:18 AM.

  3. #3
    Newcomer
    Join Date
    Mar 2009
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    What exactly does system state back up? I couldn't find a good article about what it does. I read some cryptic microsoft articles, but i'm new to VSS and backups.

    If the system state is not important, then I could comment it out, but as of right now, I would prefer to keep it in the dsm.opt file.

    So, you're saying this is more of a Veritas issue and not IBM?

  4. #4
    Member JeanSeb's Avatar
    Join Date
    Aug 2008
    Location
    Quebec City
    Posts
    181
    Thanks
    6
    Thanked 2 Times in 2 Posts

    Default

    System State include the following:

    • Active Directory (domain controller only)
    • System Volume
    • Certificate Server Database
    • COM+ database
    • Windows Registry
    • System and boot files


    • Background Intelligent Transfer Service (BITS)
    • Event logs
    • Removable Storage Management Database (RSM)
    • Cluster Database (cluster node only)
    • Remote Storage Service
    • Terminal Server Licensing
    • Windows Management Instrumentation (WMI)
    • Internet Information Services (IIS) metabase
    • Dynamic Host Configuration Protocol (DHCP)
    • Windows Internet Name Service (WINS)


    Look here for a full description of system state from the BAclient perspective:
    http://publib.boulder.ibm.com/infoce...61%74%65%22%20

    So it depends a lot on your strategy in case of bare metal recovery. If you plan on reinstalling all your Windows services from scratch (DHCP/IIS/certificates etc.) and only wants to backup user files, databases and such, you don't need system state. But if you want a quicker recovery (in theory), system state does no harm.

  5. #5
    Senior Member Jeff_Jeske's Avatar
    Join Date
    Jul 2006
    Location
    Stevens Point, WI
    Posts
    485
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Default

    I always try to test the backup of the system state using windows backup. If you can back it up with windows backup you should have no problem using TSM. However if it fails via windows backup then TSM is not responsible for the problem. Time to take a look at the VSS writers.

  6. #6
    Member tmmckinn's Avatar
    Join Date
    Jun 2006
    Location
    Wichita
    Posts
    39
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Windows Server 2003? Check hotfixes

    The readme available with the client download will have a link in the section describing Windows System Requirements. This link takes you to the IBM page where updated system requirements are posted.

    http://www-01.ibm.com/support/docvie...id=swg21197133

    There are hotfixes required for Windows Server 2003 on System State or Open File Support w/ VSS snapshot per below

    **NOTES on Windows 2003 requirements:
    if you plan to back up System State or use the Open File Support feature with the VSS snapshot provider, you must install SP1 or higher and Microsoft hotfix roll-up packages 934016 (for COM+) and 940349 (for VSS). These can be found at Microsoft's support page http://support.microsoft.com.
    if you plan to use a 64-bit machine, apply the Microsoft hotfix for knowledge base article 908675. The hotfix is included in Service Pack 2 for Microsoft Windows 2003. In case you cannot apply the entire Service Pack this particular hotfix can be provided by Microsoft upon request. See details at http://support.microsoft.com/kb/908675.
    Knowing is half the battle...
    Paying attention is the other half.

Similar Threads

  1. VSS errors on WS2003
    By Eps in forum Backup / Archive Discussion
    Replies: 1
    Last Post: 05-14-2009, 03:14 AM
  2. VSS errors
    By alia in forum Backup / Archive Discussion
    Replies: 9
    Last Post: 04-23-2009, 12:30 PM
  3. vss errors after client upgrade in a clustered envirnoment
    By tsmhelum in forum TSM Installation, Upgrade and Configuration
    Replies: 15
    Last Post: 01-28-2009, 01:26 PM
  4. VSS lockup
    By TSMTravis in forum TSM Client
    Replies: 15
    Last Post: 06-12-2008, 03:44 PM
  5. MS VSS errors - retry failed backups?
    By manofmilk in forum Backup / Archive Discussion
    Replies: 4
    Last Post: 03-08-2007, 11:47 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •