VSS Errors

Hi Guys,
I got a problem with DPM. It should backup a fileserver, but on the server it's giving several VSS errors which I can't seem to resolve. I'm hoping to find so help here.
Errors:
Event 12293
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({bda01413-9eb7-4573-a8fd-4390e9f92016}) [hr = 0x80070015, The device is not ready.
Operation:
   Executing Asynchronous Operation
Context:
   Current State: DoSnapshotSet
And: 
Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-912261192-111631960-675849044-500.bak).  hr = 0x80070539, The security ID structure is invalid.
Operation:
   OnIdentify event
   Gathering Writer Data
Context:
   Execution Context: Shadow Copy Optimization Writer
   Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Name: Shadow Copy Optimization Writer
   Writer Instance ID: {ff342f52-88ab-4716-bf21-d281d6fb4b75}
Showing up several times in the event viewer.
As far as I know, i've tried every single solution on the internet. Registering VSS, changing MBR ID (Which makes the server unbootable).
If you guys can help me out that would be great!
Thanks.

Hi,
Have you ever tried this solution?
http://technet.microsoft.com/en-us/library/cc734302(v=ws.10).aspx
Hope it helps.
Thanks and Regards
Scorpio_Milo
MVP (File System Storage)
HP Enterprise Services: Solution Architect
Microsoft Storage Team - File Cabinet Blog
View my MCP Certifications
My Blog
Contact me

Similar Messages

  • Large number VSS errors "The specified network resource or device is no longer available."

    I have a 2 node Hyper V Cluster backed up via Veeam Off-Host Proxy. I've already logged, without answer, a thread about the Off-Host Proxy server randomly (I guess) creating new duplicate iSCSI connections.
    Today I have a single VM that won't backup. On inspection through the hosting servers Application Log I see a high amount of VSS errors being logged which I believe is possibly related to the iSCSI issue being logged by the SAN.
    I'm not sure how to "show" the issue without a giant wall of the events but there is like half a dozen different events being logged when whatever this is is happening. For instance as well last night 60/61 VMs backed up find, but these errors
    were logged constantly while the backup ran...
    The question as well is is this a Windows/VSS issue, a Veeam issue or a Equallogic issue?
    Also how do I find what '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'. actually is?
    In order of how they come I guess:
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:28:19 AM
    Event ID:      8229
    Task Category: None
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    Operation:
       PrepareForSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Name: Microsoft Hyper-V VSS Writer
       Writer Instance ID: {881f5207-f769-4b40-986a-c6bd56d8aa1e}
       Command Line: C:\Windows\system32\vmms.exe
       Process ID: 3268
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:31 AM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine Error calling CreateFile on volume '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'.  hr = 0x80070037, The specified network resource or device is no longer available.
    Operation:
       Check If Volume Is Supported by Provider
    Context:
       Execution Context: Coordinator
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\
    Log Name:      Application
    Source:        EqualLogic
    Date:          6/01/2015 7:29:43 AM
    Event ID:      4001
    Task Category: VSS
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    iSCSI logout error 0xEFFF0040 from target NULL.
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:43 AM
    Event ID:      12293
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details OnLunStateChange(\\?\mpio#disk&ven_eqlogic&prod_100e-00&rev_7.0_#1&7f6ac24&0&363846433631363644434545463233334146344141353632363038303136#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})
    failed with error 0xefff0040 [hr = 0xefff0040]. 
    Operation:
       Notifying hardware provider to free a drive
       Break with LUN mask
       Delete Shadow Copies
       Processing PostFinalCommitSnapshots
       Executing Asynchronous Operation
    Context:
       Volume Name: \\?\mpio#disk&ven_eqlogic&prod_100e-00&rev_7.0_#1&7f6ac24&0&363846433631363644434545463233334146344141353632363038303136#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}
       Snapshot ID: {3091377b-2e26-43ed-a11b-f31adbde0b1f}
       Execution Context: Provider
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Snapshot Context: 4194336
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Current State: DoSnapshotSet
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:43 AM
    Event ID:      12293
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}. Routine details could not free LUN [hr = 0x8004230f, The shadow copy provider had an unexpected error while trying to process the
    specified operation.
    Operation:
       Break with LUN mask
       Delete Shadow Copies
       Processing PostFinalCommitSnapshots
       Executing Asynchronous Operation
    Context:
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}
       Snapshot ID: {3091377b-2e26-43ed-a11b-f31adbde0b1f}
       Execution Context: Provider
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Snapshot Context: 4194336
       Provider Name: Dell EqualLogic VSS HW Provider
       Provider Version: 4.7.1
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Current State: DoSnapshotSet
    (Below logged 3 times)
    Log Name:      Application
    Source:        VSS
    Date:          6/01/2015 7:29:49 AM
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      HOST02.domain.private
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine Error calling CreateFile on volume '\\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\'.  hr = 0x80070037, The specified network resource or device is no longer available.
    Operation:
       Check If Volume Is Supported by Provider
    Context:
       Execution Context: Coordinator
       Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
       Volume Name: \\?\Volume{06fba49e-9519-11e4-80cc-000af75dc050}\

    This is the issue having with redundant iSCSI connections being created:
    Not sure this is a Veeam issue, just that it's occurring with Veeam backup process.
    We have a server configured as an Off-Host Proxy with Veeam; it connects to the SAN storage via iSCSI same as the other hosts but accesses the storage as read only.
    Randomly we will get alerts from the SAN as below:
    iSCSI login to target '172.16.0.50:3260, iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1-2015-01-03-14:13:37.2774.1' from initiator '172.16.0.44:64108, iqn.1991-05.com.microsoft:arcbackproxy.domain.local' failed for the following reason:
    Requested target not found.
    On inspection of the Off-Host Proxy's iSCSI configuration additional iSCSI connections are present as inactive, with an existing connections name amended with the date at the end. For instance (and in the example error above) there will be:
    iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1
    and
    iqn.2001-05.com.equallogic:8-661fc6-e612eedc6-32600005c9254a75-arcvmstore1-2015-01-03-14:13:37.2774.1
    Not really causing an issue, the backups are running OK, or any issues we have aren't related. But getting annoying getting the alerts from the SAN of the Off-Host Proxy trying to connect to an incorrect iSCSI target.
    Any ideas why this is occurring?
    Obvious is we delete the extra connection, which stops the alert, but the issue will reoccur within a day or two usually.
    Today I found twice the alert as above and sure enough the iSCSI on the Off-Host Proxy is as below:
    Maybe these redunandant connections being created is related? Maybe that's the where the "The specified network resource or device is no longer available." is coming from or something?

  • VSS Error in writer Hyper-V

    I have a cluster with CSV 5 and DPM can't perform backup on only a few machines in the cluster, it apesenta VSS the following error:
    The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\Máquina on MAQUINA.CLOUD04.dominio.local is inconsistent with the protected data source.
    All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent. 
    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency
    check on the farm. (ID 3106)
    DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
     (0x800423F3))
    Well investigating deeper into the Hyper-V server virtualization encounter the following errors:
    Eventvwr:
    SOURCE: VSS ID: 8229
    A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error.  If the backup process is retried,
    the error may not reoccur.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    Operation:
       PostSnapshot Event
    Context:
       Execution Context: Writer
       Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Name: Microsoft Hyper-V VSS Writer
       Writer Instance ID: {52a247b1-bd8e-499c-915d-314f9080e993}
       Command Line: C:\Windows\system32\vmms.exe
       Process ID: 2460
    SOURCE: HYPER-V-VMMS ID: 10143
    Failed to delete the shadow copy (VSS snapshot) set with id '3ED86740-3BFC-4FD5-B6B6-5ADD63E87DB0' in the running virtual machine 'MAQUINA': This operation returned because the timeout period expired. (0x800705B4). (Virtual machine ID E130C3C7-D2BC-4234-BD2A-766054A163F9)
    List Writers
    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {52a247b1-bd8e-499c-915d-314f9080e993}
       State: [11] Failed
       Last error: Retryable error
    Well, how did not get any results in searches, then checked the versions of the IC on client machines as clusters migrated from 2008 to 2012 some were outdated, updated them, even just to leave everything compliance. 
    So I decided to clear the "Backup (volume snapshot)" and now he backs up but does the same linux machines, saving the machine and causing downtime of it, and even if you are a linux machine with this option it can not perform the backup this because
    it tries utilizr VSS method (I think).
    Please, anyone help-me?
    thanks!

    Hi ,
    Please refer to following similar thread :
    http://social.technet.microsoft.com/Forums/en-US/be7fd80f-d2bc-4e1b-9bc2-a60af6e89e2a/dpm-faild-to-backup-hyperv-gest-vm-code-0x800423f3-id-30112?forum=dpmhypervbackup
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • VSS error 8193 and 22 by backup task (Windows server 2012)

    Hello,
    On the WinServer 2012 Std , I am facing VSS error when it starts "system state backup".
    The user account of this task is a member of "local Backup operators".
    how can I correct this error ?
    In the forum, I found a topic that had mentioned regsvr32.
    But Microsoft said it does not recommended/ supported for 2008 or later.
    http://social.technet.microsoft.com/Forums/office/en-US/2b1f44e0-725a-4fc5-bc1d-69437871fe90/wierd-volume-shadow-copy-service-errors?forum=winserverfiles
    -Quote [start]-
    Reregistering files was a common way to fix VSS issues back in Windows 2003.  However, due to the changes in Windows 2008 and 2008R2 servicing, reregistering files will either not work or actually damage Windows.
    Please discontinue using
    regsvr32.
    Robert Mitchell Senior Support Escalation Engineer Microsoft Corp.
    -Quote [End]-
    the detail of event logs are ;
    Log Name:      Application
    Source:        VSS
    Event ID:      22
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:     
    Description:
    Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance
    on class with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered ].
    Log Name:      Application
    Source:        VSS
    Event ID:      8193
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.
    hr = 0x80040154, Class not registered .
    Thank you for your support.

    Dear Sophia,
    Thank you for your instruction, the below is result of vssadmin.
    I am using CA Arcserve 16.5 for backing up system state.
    Writers
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Writer name: 'Task Scheduler Writer'
        Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
        Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
        State: [1] Stable
        Last error: No error
    Writer name: 'VSS Metadata Store Writer'
        Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
        Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
        State: [1] Stable
        Last error: No error
    Writer name: 'Performance Counters Writer'
        Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
        Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
        State: [1] Stable
        Last error: No error
    Writer name: 'System Writer'
        Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
        Writer Instance Id: {540ecfcf-7f41-43cc-9521-d73d1881b85f}
        State: [1] Stable
        Last error: No error
    Writer name: 'SqlServerWriter'
        Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
        Writer Instance Id: {1fe1e4af-26ab-4113-8079-2c853e1a32fc}
        State: [1] Stable
        Last error: No error
    Writer name: 'ASR Writer'
        Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
        Writer Instance Id: {8094a9a6-29e1-4276-a8b0-7f9bd34e7ad5}
        State: [1] Stable
        Last error: No error
    Writer name: 'WMI Writer'
        Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
        Writer Instance Id: {3812a483-5e46-4c06-a64d-4caa1184705e}
        State: [1] Stable
        Last error: No error
    Writer name: 'IIS Config Writer'
        Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
        Writer Instance Id: {094ddb56-3e9a-452f-951a-22da278d7666}
        State: [1] Stable
        Last error: No error
    Writer name: 'Registry Writer'
        Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
        Writer Instance Id: {4f57f2af-4a0e-443d-ac27-c9b858c50744}
        State: [1] Stable
        Last error: No error
    Writer name: 'Shadow Copy Optimization Writer'
        Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
        Writer Instance Id: {54fb8f5c-2dff-479d-8ed1-b7de3c7495c3}
        State: [1] Stable
        Last error: No error
    Writer name: 'COM+ REGDB Writer'
        Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
        Writer Instance Id: {901cd0a6-895a-4942-ac60-c8a6a7796583}
        State: [1] Stable
        Last error: No error
    Providers
    C:\Windows\system32>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Provider name: 'SmVssProvider'
        Provider type: Hardware
        Provider Id: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
        Version: 10.84.02
    Provider name: 'Microsoft File Share Shadow Copy provider'
        Provider type: Fileshare
        Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
        Version: 1.0.0.1
    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
        Provider type: System
        Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
        Version: 1.0.0.7
    Shadows
    C:\Windows\system32>vssadmin list shadows vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    ^C
    Since command prompt has no output for 5mins, I pressed CTRL+C
    Shadowstorage
    C:\Windows\system32>vssadmin list shadowstorage vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    No items found that satisfy the query.
    Volumes
    C:\Windows\system32>vssadmin list volumes vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2012 Microsoft Corp.
    Volume path:
    \\?\Volume{d2760d78-5868-11e3-93e7-806e6f6e6963}\
         Volume name:
    \\?\Volume{d2760d78-5868-11e3-93e7-806e6f6e6963}\
    Volume path: D:\
         Volume name:
    \\?\Volume{88a134c9-020e-4020-8697-dc44c8a3c89a}\
    Volume path: C:\
         Volume name:
    \\?\Volume{d2760d79-5868-11e3-93e7-806e6f6e6963}\
    C:\Windows\system32>

  • VSS error on host-level backups

    We have recently virtualized a Windows Server 2003 SP2 server into a Hyper-V 2008 R2 cluster, and as we're running DPM 2012 R2 we have to protect it on host-level as there's no agent support for W2003 in DPM 2012 R2. However, I keep getting the error below
    when running a consistency check on the server:
    DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error.  If the backup process is retried, the error may not reoccur (0x800423F3).
    There are a lot of VSS writers with "waiting for completion" status after a snapshot - System writer, NTDS, IIS, and FRS. The Hyper-V writer gets a retryable error on the host, but other VM's on the same host works just fine. We have
    also tried to move this VM to another Hyper-V host but with the same result. KB940349 is already installed on the server but it doesn't seem to help.
    Any ideas or suggestions are much appreciated!
    /Amir

    1. http://support.microsoft.com/kb/2460912 - volsnap.sys
    2. http://support.microsoft.com/kb/2263829 - hvboot.sys
    3. http://support.microsoft.com/kb/2541014 - diskdump.sys
    Can you upgrade (reinstall) cluster to Windows Server 2012 or R2?
    Protecting Windows 2003 Workload Hyper-V DPM 2012 R2
    also Looking in the VM there was 0 bytes free , leaving the VSS writer unable to do any work , so after expanding the drive the backup is successful
    http://flemmingriis.com/replica-is-inconsistent-hyper-v-2012-dpm-vm-backup/                                                                                                                                                  
    http://jeffgraves.me/2010/04/08/error-0x800423f3-backing-up-hyper-v-vm-with-dpm-2007/

  • VSS errors 8193, 22, and 12292

    We have a Windows 2012 standard server, and once we renamed the server, we started getting the following VSS errors - 8193, 22, and 12292.  How can I fix this?  The errors are listed below.  Thanks in advance!
    Error 8193 - Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x80040154, Class not registered
    Error 22 - Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned
    from CoCreateInstance on class with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and Name IVssCoordinatorEx2 is [0x80040154, Class not registered

    Hi,
    Please run "vssadmin list writers" to see if you can find System Writer?
    If no system writer, try to run the command in command prompt:
    SC.EXE SDSHOW EVENTSYETEM
    • If the output is like below, that means it is missing the Service Logon User (missing the entry (A;;CCLCSWLOCRRC;;;SU) )
    D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
    • Then you can reset the eventsystem permission:
    Sc.exe sdset eventsystem D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)
    • Restart both the COM+ Event System and Cryptographic Services
    • Run VSSADMIN LIST WRITERS again and see if system writer is back.
    NOTEs:If the problem on your side is indeed related to service permission, you can check the GPO setting on your side to see if there is any change on the COM+ Event System Service.
    If you have any feedback on our support, please send to [email protected]

  • DPM 2012 VSS Errors

    We have our DPM 2012 R2 installation on Windows 2008 R2 servers. We encounter failures some of the time on our Full Express Backups on Friday evenings where we get VSS errors in the event logs. 
    Event 12298
    Event 12289
    We haven't encountered these issues until recently. Is there any idea on how to remedy these. I just installed DPM 2012 R2 this week so I am hoping it helps. But does anyone know if there is a hotfix or something for this in case it does not. I read about
    these events having a hotfix for Windows 2003 servers but not Win2K8?

    Event 12289
    Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{XXXXXXX]).  hr = 0x80070057, The parameter is incorrect.
    Operation:
       Processing EndPrepareSnapshots
    Context:
       Execution Context: System Provider
    Event 12298
    Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{XXXXXXXXX}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000, The operation completed successfully.
    ], Flush[0x00000000, The operation completed successfully.
    ], Release[0x00000000, The operation completed successfully.
    ], OnRun[0x80042314, The shadow copy provider timed out while holding writes to the volume being shadow copied. This is probably due to excessive activity on the volume by an application or a system service. Try again later when activity on the volume is reduced.

  • Windows 2012 Server Backup Problems - VSS Error

          Our company uses Windows Server Backup to back up our Windows 2012 Server.  We back up the host component and the two virtual machines on the server.  Every time I install windows updates
    on our server my backup jobs stop working and I get a VSS error.  In order to get backup working again, I have to recreate my backup job.  In order to do this I have to attach all the backup drives to the computer at the same time. 
    This has been an issue all the way back to when the server was first installed.  At that time the person who installed Windows Server talked to Microsoft.  Microsoft said the problem would be fixed in the first service pack which they ended
    up never releasing.  I have looked online, but haven’t found any information on these issues.  Are there any fixes for these two problems?

    Hi,
    Sorry for the delay.
    Can you first do a backup then install windows updates? Please provide more detailed message about the VSS error.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • VSS Error Event id 8193 - 0x80070539

     I keep getting VSS Error with event id 8193 for several weeks now:
    ConvertStringSidToSid
    0x80070539
    Operation: OnIdentify event Gathering Writer Data Context:
    Execution Context: Shadow Copy Optimization Writer Writer Class Id:
    {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Name: Shadow Copy Optimization Writer Writer Instance ID:
    {bd32726a-3d40-4c27-9282-2af7d5cff0a5}
    Any ideas?

    Noting much just hoping somebody with the right knowledge is going to give me a light ...
    All public VSS resolutions relate to Server 2003 and hence do not work here.
    Also I have reformulated the issue slightly:
    Vista SP1 - VSSadmin List Writers reveals one writer missing:
    Shadow Copy Optimization Writer is not listed.
    Creating a restore point causes VSS Error with event id 8193
    >> ConvertStringSidToSid
    >> 0x80070539
    >> Operation: OnIdentify event Gathering Writer Data Context:
    >> Execution Context: Shadow Copy Optimization Writer Writer Class Id:
    >> {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    >> Writer Name: Shadow Copy Optimization Writer Writer Instance ID:
    >> {bd32726a-3d40-4c27-9282-2af7d5cff0a5}
    However, restore point creation is succesful.
    There must be another way but reinstalling the entire OS and everything else on top from scratch ...

  • Windows Server 2012 VSS error "The system writer is missing"

    Hello All,
    I have a HP server that I have just installed Server 2012 standard, SQL Server 2012 and Sharepoint 2013.
    When I try to take bare metal backup I get the error: "The system writer is missing", I have tried the backup as the local admin and domain admin.
    The backup will only work if I decide to back up C:, once I select "Bare Metal" or "System State" the backup fails.
    I have tried this solution: http://technet.microsoft.com/en-us/library/cc734021.aspx but have not had any luck yet.
    When I run the command "vssadmin list writers" I can not see "System Writer" listed.
    How can I add/turn on the System Writer?

    Hi,
    The system writer fails due to the fact that the trusted installer & system accounts are missing permissions to files in the directory %windir%\winsxs\filemaps\.
    To resolve this issue, please run the following commands from an administrative elevated Command Window:
    CD c:\windows\system32
    Takeown /f %windir%\winsxs\filemaps\* /a
    icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)"
    For more information, please also refer to the following links:
    Discussion Forum FAQ: VSS System Writer is missing. 
    http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/0b1eb10a-d666-4f5e-b657-c93b1d754a7f
    Failure during Windows Server 2008 System State Backup & System Writer Missing
    http://blogs.technet.com/b/chrad/archive/2009/11/18/failure-during-windows-server-2008-system-state-backup-system-writer-missing.aspx
    Regards,
    Arthur Li
    TechNet Community Support

  • Server 2003 R2 VSS error.

    I inherited a Windows Server 2003 R2 standard edition x86. After doing a bit of checking on it, I see it has not been backed up for some time. Drive C is handled by an Adaptec controller card and has 2 drives in Raid 1 configuration with total space of 68.2GB
    with 33GB free and fragmentation of 1%. Drive D is handled by a 3Ware controller card and has 9 drives in Raid 5 configuration (8 active, 1 spare) with total space of 7.27TB with 4.65TB free and fragmentation of 1%.
    When looking at either drive thru Windows explorer, properties, Shadow Copies tab it shows "Failed to retrieve volumes that are eligible for shadow copies. Error 0x8004230f: The shadow copy provider had an unexpected error while trying to process the
    specified operation."
    If I check thru command prompt and run vssadmin commands I get the following.
    C:\Documents and Settings\Administrator>vssadmin list providers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.
    Provider name: 'Symantec Software VSS Provider'
       Provider type: Software
       Provider Id: {262b716e-bb23-41b5-aaef-e2c15e767167}
       Version: 1.0
    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7
    C:\Documents and Settings\Administrator>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {0a076449-61f7-459b-8288-9684c8a6b860}
       State: [1] Stable
       Last error: No error
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {1f5f638e-3bc0-430b-849e-17bf69b42b64}
       State: [1] Stable
       Last error: No error
    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {1ee21ac2-2dd2-450b-87f9-e425b4ee599e}
       State: [1] Stable
       Last error: No error
    Writer name: 'MSDEWriter'
       Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
       Writer Instance Id: {c8b96527-9328-4ce3-92ac-6efc995dbef5}
       State: [1] Stable
       Last error: No error
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {c6e9592a-3a8a-4873-9589-4fb9072f045b}
       State: [1] Stable
       Last error: No error
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {0c50faba-aec4-4f76-96ad-d25c0b5066ca}
       State: [1] Stable
       Last error: No error
    Writer name: 'Event Log Writer'
       Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
       Writer Instance Id: {76fcde0f-d18b-4936-a3f6-1dd399630101}
       State: [1] Stable
       Last error: No error
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {5ea9ac74-036c-44f3-bf52-684784c03131}
       State: [1] Stable
       Last error: No error
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {f02d80c6-e208-4e9e-9076-3032677fe594}
       State: [1] Stable
       Last error: No error
    C:\Documents and Settings\Administrator>vssadmin list shadows
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.
    No items found that satisfy the query.
    C:\Documents and Settings\Administrator>vssadmin list volumes
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.
    Error: The shadow copy provider had an unexpected error while trying to process
    the specified command.
    Now if I look in the event log under Applications I see 2 errors showing.
    Error 1
    Source VSS. Event ID 12302. Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
    Error 2
    Source VSS. Event ID 12293. Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::QueryVolumesSupportedForSnapshots(ProviderId,29,...) [hr = 0x8000ffff].
    Checking error 1 event id 12302 is says to make sure COM + is set to Automatic.  It is set to automatic and is running. It also says to command prompt vssadmin list writers and verify none are reporting errors. None are reporting an error. It also
    says to check volume shadow copy in services. Start up set to manual, which it is and it will run with no problems.
    Checking error 2 event id 12293 it says to use vssadmin create shadow for each provider. If I do that I get the same errors.
    I have done a lot of research on this and found 3 hot fixes from Microsoft. None of the 3 apply to the error messages that I am getting. But to give it a good try, I have applied all 3 hot fixes and none made it better, and none made it worse (different
    error messages). I have also tried the following
     cd /d %windir%\\system32
    Net stop vss
    Net stop swprv
    regsvr32 ole32.dll
    regsvr32 vss_ps.dll
    Vssvc /Register
    regsvr32 /i swprv.dll
    regsvr32 /i eventcls.dll
    regsvr32 es.dll
    regsvr32 stdprov.dll
    regsvr32 vssui.dll
    regsvr32 msxml.dll
    regsvr32 msxml3.dll
    regsvr32 msxml4.dll
    regsvr32 Vssapi.dll
    regsvr32 Vssui.dll
    net start vss
    net start swprv
    The only errors I get when doing this is the following. 
    "msxml4.dll not found"  I understand this as my system now has msxml6 and in doing some research msxml6 and msxml4 are not compatible and msxml6 replaced msxml4, so I can live with that, I guess.
    "Vssapi.dll was loaded, but the DllRegisterServer entry point was not found. The file cannot be registered."
    I am at a loss. Does anyone have any suggestions

    Hi,
    Do you install Symantec on your server? If so, please try to remove the entries of Symantec from system to check the result.
    In the meantime, please try the steps listed in the following article to see if it can help:
    Error message when you run the "vssadmin list writers" command on a Windows Server 2003-based computer: "Error: 0x8000FFFF"
    http://support.microsoft.com/kb/940184
    Please note, you need to backup the registry before making any changes to it.
    Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Windows server backup crash vss errors

    We're having an issue where every other day the system state fails. We use a 3rd party piece of software that uses WSB for the system state. We get the following in the eevnt logs:
    Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
    Faulting module name: ntdll.dll, version: 6.1.7601.18229, time stamp: 0x51fb164a
    Exception code: 0xc0000005
    Fault offset: 0x0000000000055384
    Faulting process id: 0x3560
    Faulting application start time: 0x01d01197a2bdc7a1
    Faulting application path: C:\Windows\system32\wbengine.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: d6f0610d-7d8f-11e4-a8f7-5cf3fc557333
    and the following when running vssadmin list writers:
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {7655da00-923b-441b-bc40-d64e3d44aaa9}
       State: [1] Stable
       Last error: No error
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {0e9c9681-5e67-4748-900c-b32ff7ebd072}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {3e4d034d-b955-428e-952b-0581f8e05203}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {3ee8ab83-468c-4cfe-8613-6946976820fb}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {2975a331-2068-4a6e-a16f-4635f5ce2856}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {43188986-6573-45a8-b871-4be3d189a45f}
       State: [1] Stable
       Last error: No error
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {a9632f02-31e3-424c-8c87-69395dbf04e2}
       State: [1] Stable
       Last error: No error
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {180f4d03-93aa-4947-b874-c2d0d7546ca0}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {231ceb2e-3b8c-40f1-8d02-22a4f263802d}
       State: [1] Stable
       Last error: No error
    Writer name: 'TS Gateway Writer'
       Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
       Writer Instance Id: {60237974-e116-454e-b29c-6ffeffd1bd9d}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {440c5208-9d3a-4c84-884c-f9a3d8ad2c1e}
       State: [1] Stable
       Last error: No error
    Writer name: 'NPS VSS Writer'
       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
       Writer Instance Id: {d6ae39a4-2c8b-4e48-9f79-12247b9fac5b}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {c616d312-5e21-47df-9e59-100cf6ac6f0e}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {8f945f3b-d50b-47b8-9085-1416d0b094e1}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {50c005a1-35e8-4bc1-a0c1-1bcdc9351322}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {2bcebf65-9243-4ccd-bae2-6ae12efd9a51}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {4101713c-f207-431f-be52-1171f1227c0b}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {aa053355-2571-4e37-ba1d-501127ab2846}
       State: [5] Waiting for completion
       Last error: No error
    Writer name: 'Microsoft Exchange Writer'
       Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
       Writer Instance Id: {7645b18a-8aa4-49d3-abd1-5d7debd4b3f3}
       State: [1] Stable
       Last error: No error
    as i said - this happens every other day, the 3rd party software provider say this is a microsoft issue but this doesnt happen when running a system state directly from WSB

    Hi,
    What third party software do you use? There is a similar thread, please try to restart Block Level Backup Engine Service and VSS service to check if could resolve the issue. 
    For more detailed information, please refer to the thread below:
    Backup SystemState 2008 R2 failed - The RPC server is unavailable.
    https://social.technet.microsoft.com/Forums/en-US/f92c0a5b-2cfb-47f9-9ace-6028f5316a03/backup-systemstate-2008-r2-failed-the-rpc-server-is-unavailable
    Best Regards,
    Mandy 
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • VSS Error: "An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes."

    Hi all,
    at a customer’s site I’ve a problem with a fresh installation of Backup Exec 2014. Every backup (full or incremental) always reports the following
    error: “An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly re-synchronized with the original volumes.”.
    It’s not a Backup Exec problem itself, also backups using “Windows Server Backup” failing with the same error.
    On this site I have three servers; the error is only generated for one of them. Here’s a short overview:
    Server1: Windows Server 2012 R2, latest patchlevel, physical machine, Domain Controller and Fileserver. Backup Exec is installed on this machine,
    backup is written directly to SAS tape loader. There error is generated on this server.
    Server2: Windows Server 2008 R2, latest patchlevel, virtual machine, running on Citrix Xen Server 6.2. Used for remote desktop services, no errors
    on this server.
    Server3: Windows Server 2012 R2, latest patchlevel, virtual machine, database server with some SQL Instances, no errors on this server.
    As I said, error is reported only on server1, no matter if it is a full or an incremental backup. During the backup I found the following errors
    is the event log (translated from a german system):
    Event ID: 12293
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider. "{89300202-3cec-4981-9171-19f59559e0f2}" an error occured. Routinedetails Error calling Query(). [0x80042302] [hr = 0x80042302, unexpected component error of
    the Volume Shadow Copy Service.
    Process:
    Volume Shadow Copy polling
    Volume Shadow Copy delete
    Context:
       Executioncontext: Coordinator
       Executionkontext: Coordinator
    And
    Event ID: 8193
    Volume Shadow Copy Service error: Unexpected error calling Routine "IVssCoordinator::Query" hr = 0x8004230f, Unexpected error Volume Shadow Copy Service Provider
    Process:
    Volume Shadow Copy delete
    Context:
       Executioncontext: Coordinator
    There are some articles about this error in the knowledge base or web which does not help or do not apply to my environment for example:
    http://www.symantec.com/business/support/index?page=content&id=TECH38338&actp=search&viewlocale=en_US&searchid=1423724381707
    What I already have tried:
    Disabled Antivirus during the whole backup
    Installed latest Service Pack for Backup Exec
    Rebooted the server
    vssadmin list writers do not show any errors
    consult eventid.net for other possible solutions
    no limits set for vaa
    Anymore ideas from you guys?
    Best regards,

    Hi Shaon,
    vssadmin list providers gave the following output:
    vssadmin list providers
    vssadmin 1.1 - Verwaltungsbefehlszeilenprogramm des Volumeschattenkopie-Dienstes
    (C) Copyright 2001-2013 Microsoft Corp.
    Anbietername: "Microsoft File Share Shadow Copy provider"
       Anbietertyp: Dateifreigabe
       Anbieterkennung: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1
    Anbietername: "Microsoft Software Shadow Copy provider 1.0"
       Anbietertyp: System
       Anbieterkennung: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7
    Unfortunately theres not Symantec VSS Provider listed.
    Best regards,
    Christoph

  • Problem: VSS error with 'SQL Server Backup to Windows Azure Tool' installed

    When 'SQL Server Backup to Windows Azure Tool' is installed, shadow copies cannot be enable and backups fail.  When attempting to enable shadow copies, we get a "volsnap" error:  "The shadow copies of volume X were aborted because
    of a failed free space computation".  After uninstalling the "Tool", VSS works.  Reinstalling "Tool" causes the problem to return.
    While the error suggests a space issue, there is plenty of space on the server's two volumes.  Additionally, another 100GB volume was added and VSS storage was allocated to it; still received the error.
    Issue seems to point to 'SQL Server Backup to Windows Azure Tool'.
    Environment:  Hyper-V guest:  "Windows Server 2012 R2 Standard" with "SQL Server 2008 R2 Standard".  Using "Azure Storage" for SQL backups.
    Suggestions?

    Hello,
    Yes, we have a confirmed interference between the tool and the VSS Framework. This was identified very recently and is under investigation by the product group. Since the issue is within the filter driver shipped by the tool, that unfortunately means that
    you currently need to choose between the tool and a working VSS Framework. If the latter is more important, then uninstall the tool (that will require a restart).
    We apolologize for the inconvenience. I'm going to try to get the home page of the tool updated to avoid other situations like yours. Hopefully we should see a new version of the tool soon.
    As a side note, recent versions of SQL Server can directly use Azure Storage as backup target, see
    http://msdn.microsoft.com/en-us/library/jj919148(v=sql.110).aspx.
    Regards,
    Guillaume Fourrat - Microsoft France

  • Centos VM VSS errors

    Im finding below error with regards to Centos 6.4 VM  (Vmhost windows 2012 R2)
    Hyper-V failed to generate VSS snapshot set for virtual machine 'testcntos': The request is not supported. (0x80070032). VSS snapshot set generation can fail if backup operation is in progress.
    Note:-
    1. VSS snapshot freq. has been set to 6 hours.
    2. Linux integration services 3.5 installed in VM.
    3. Backupessentials 1.0 installed.
    What needs to b done to resolve this error ?

    Hi Newvm,
    Centos 6.4 has build-in IS .
    "Drivers: IDE, SCSI, networking, and mouse
    Services: Time synchronization, operating system shutdown, and heartbeat
    Integration services are built-in and do not require a separate download and installation."
    For details please refer to following link :
    http://technet.microsoft.com/en-us/library/dn531026.aspx
    "VSS snapshot set generation can fail if backup operation is in progress"
    Maybe there is conflict with backup operation .
    Please try to stop any other backup application , install "windows server backup" to backup the linux VM .
    Best Regards
    Elton Ji
    If it is not the answer please unmark it to continue
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

Maybe you are looking for