none
Backup of SQL DB using vsnap/SQL VSS writer fails if SQL2005 is installed in VM (Host OS win2k8 shared disk cluster ) RRS feed

  • Question

  • We have SQL 2005 (Clustered instance) installed on a shared-disk Win2K8 VM cluster. This is a test lab environment and not a production environment.

    Backups taken using the SQL VSS writer fails. We tried taking backups with vsnap tool and it failed too with error message:
    ERROR: Selected writer 'SqlServerWriter' is in failed state!
       - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
       - Writer Failure code: 0x800423f4 (<Unknown error code>)
       - Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       - Instance ID: {7f331874-f4a2-4a80-b041-a3cd9f8ec337}

    Is there some known reasons like 'not enough resources ...' etc? Please help.

    Host OS:- windows server 2008
    Configuration: Shared-Disk Cluster.
    RAM: 1 GB


    The detailed output from the command prompt is as follows:

    G:\>\\idlsstore\v2writable\hisharma\vsnap.exe G:

    VSNAP.EXE 2.0 - Volume Shadow Copy sample client
    Copyright (C) 2004 Microsoft Corporation. All rights reserved.


    (Option: Create shadow copy set)
    (Gathering writer metadata...)
    (Waiting for the asynchronous operation to finish...)
    Initialize writer metadata ...
    Discover directly excluded components ...
    - Component '\System Files' from writer 'System Writer' is excluded from backup
    (it requires C:\ in the shadow set)
    - Component '\BCD\BCD' from writer 'ASR Writer' is excluded from backup (it requ
    ires C:\ in the shadow set)
    - Component '\WMI' from writer 'WMI Writer' is excluded from backup (it requires
     C:\ in the shadow set)
    - Component '\Registry' from writer 'Registry Writer' is excluded from backup (i
    t requires C:\ in the shadow set)
    - Component '\IISMETABASE' from writer 'IIS Metabase Writer' is excluded from ba
    ckup (it requires C:\ in the shadow set)
    - Component '\COM+ REGDB' from writer 'COM+ REGDB Writer' is excluded from backu
    p (it requires C:\ in the shadow set)
    - Component '\IISCONFIG' from writer 'IIS Config Writer' is excluded from backup
     (it requires C:\ in the shadow set)
    - Component '\Cluster Database' from writer 'Cluster Database' is excluded from
    backup (it requires C:\ in the shadow set)
    Discover all excluded components ...
    Discover excluded writers ...
    - The writer 'System Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'ASR Writer' is now entirely excluded from the backup:
      (the top-level non-selectable component '\BCD\BCD' is an excluded component)
    - The writer 'BITS Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'WMI Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'Shadow Copy Optimization Writer' is now entirely excluded from the
     backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'Registry Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'IIS Metabase Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'COM+ REGDB Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'IIS Config Writer' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    - The writer 'Cluster Database' is now entirely excluded from the backup:
      (it does not contain any components that can be potentially included in the ba
    ckup)
    Discover explicitly included components ...
    Verifying explicitly specified writers/components ...
    Select explicitly included components ...
     * Writer 'SqlServerWriter':
       - Add component \LHSQLCLUSTER\SQL2005INSTANCE\master
       - Add component \LHSQLCLUSTER\SQL2005INSTANCE\model
       - Add component \LHSQLCLUSTER\SQL2005INSTANCE\msdb
       - Add component \LHSQLCLUSTER\SQL2005INSTANCE\TrialDB
       - Add component \LHSQLCLUSTER\SQL2005INSTANCE\TrialDB-2
       - Add component \LHSQLCLUSTER\SQL2005INSTANCE\TrialDB_FT
     * Writer 'Microsoft Exchange Writer':
       - Add component \Microsoft Exchange Server\Microsoft Information Store\E12SDM
    BOX\e818ad0c-f179-441d-96ca-557dbec29b3d
    Creating shadow set {0cd259e9-745f-4869-a2cc-d4a3ce6e8343} ...
    - Adding volume \\?\Volume{bf64034f-c91b-11dc-a2df-0003ff99935f}\ [G:\] to the s
    hadow set...
    Preparing for backup ...
    (Waiting for the asynchronous operation to finish...)
    (Waiting for the asynchronous operation to finish...)
    Creating the shadow (DoSnapshotSet) ...
    (Waiting for the asynchronous operation to finish...)
    (Waiting for the asynchronous operation to finish...)

    ERROR: Selected writer 'SqlServerWriter' is in failed state!
       - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
       - Writer Failure code: 0x800423f4 (<Unknown error code>)
       - Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       - Instance ID: {88445a5b-5bb1-4ba8-af6e-69c0c29022b0}


    The Event viewer logs are as follows:

    1. SQLVDI: Loc=SVDS:Surprisepen. Desc=OpenProcess. ErrorCode=(5)Access is denied.
    . Process=4960. Thread=2632. Server. Instance=SQL2005INSTANCE. VD=Global\{2340CC39-07A7-4E36-ACA9-1432E810A5FB}1.

    2. Cannot open backup device '{2340CC39-07A7-4E36-ACA9-1432E810A5FB}1'. Operating system error 0x80070005(Access is denied.).

    3. BACKUP failed to complete the command BACKUP DATABASE TrialDB. Check the backup application log for detailed messages.

    4. Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
    Error state: 1, Severity: 16
    Source: Microsoft SQL Native Client
    Error message: BACKUP DATABASE is terminating abnormally.
    SQLSTATE: 42000, Native Error: 3201
    Error state: 7, Severity: 16
    Source: Microsoft SQL Native Client
    Error message: Cannot open backup device '{2340CC39-07A7-4E36-ACA9-1432E810A5FB}1'. Operating system error 0x80070005(Access is denied.).


    5. SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1488. Thread=3996. Client. Instance=SQL2005INSTANCE. VD=Global\{2340CC39-07A7-4E36-ACA9-1432E810A5FB}1.

    thanks in advance,
    Hitesh.




    Monday, February 4, 2008 10:12 AM

Answers

All replies

  • This is a known issue that we are currently investigating.

     

    Cheers,

    Ben

    Monday, February 4, 2008 7:34 PM
  • We have the same problem with official Web Server 2008 and SQL 2005. Backup medium is a single HDD. There has been the problem already solved? Thx for response. RN
    Thursday, March 20, 2008 12:59 PM
  • I beleive this is fixed in the RC build.

     

    Cheers,

    Ben

     

    Thursday, March 20, 2008 7:21 PM
  • I am having the same issue with 2008 Server and SQL Server 2005 sp2.

     

    Key to the issue is the "Access is denied" for SQL Writer.  When it connects to SQL server for the backup, it connects as a client.  Even though my SQL server instance has the SYSTEM account as a system administrator, it seems to fail the security audit.

     

    Work-around:  I temporarily changed the account used to start the SQLWriter Service to the Active Directory Administrator account (this is a test box).  This worked, and I was able to create the backup with no errors.

     

    So it's a security problem.  Just need to find out how/where it is failing and why the SYSTEM account, running the SQLWriter Service, was unable to log in to the SQL Server instance.

     

    Hope this helps, at least temporarily.  Let me know if you find out anything more.

    • Proposed as answer by Ted.Lambert Monday, June 18, 2012 6:07 PM
    Friday, May 9, 2008 8:28 PM
  • Hi,

    Well were are seeing this happen on a fairly regular basis on our production systems.

    They are all

    Windows 2003 with SP2
    MS SQL Server 2005 SP2

    Message Text - in order of occurance in the event log

    SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=2992. Thread=5064. Client. Instance=METIS. VD=Global\VDI_585DBB67-19E7-4FC2-8FAF-1DD9AF2ACFBD_0_SQLVDIMemoryName_0.


    SQLVDI: Loc=CVDS::Close. Desc=Abnormal termination state. ErrorCode=(0). Process=2992. Thread=5064. Client. Instance=METIS. VD=Global\VDI_585DBB67-19E7-4FC2-8FAF-1DD9AF2ACFBD_0_SQLVDIMemoryName_0. 

    SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=5020. Thread=4592. Client. Instance=METIS. VD=Global\VDI_A5EA7805-F8C1-4856-B2F7-07436CEE8742_0_SQLVDIMemoryName_0. 

    SQLVDI: Loc=CVDS::Close. Desc=Abnormal termination state. ErrorCode=(0). Process=5020. Thread=4592. Client. Instance=METIS. VD=Global\VDI_A5EA7805-F8C1-4856-B2F7-07436CEE8742_0_SQLVDIMemoryName_0.

    This seems to happen on a regular 7-8 day period.

    Any help would be appreciated.

    Thanks!

    David

    Tuesday, August 5, 2008 5:58 PM
  • What is the RC build - a little more detail would be helpful.

     

    Thanks,


    DBASQL,Informix,Oracle
    Thursday, May 12, 2011 2:34 PM
  • Was having failures using DPM2010 for the SQL databases, but not the local filesystem protection. Server is Server2003, SQL2005. Tacked down to VSS permissions error as above.

    Using the local Admin account worked for me.

    Thanks for the answer.

    Monday, June 18, 2012 6:00 PM