Microsoft hyper v vss writer непредвиденная ошибка

Recently started having a few problems backup up one of my Hyper-V servers. Its a server 2008 R2 box running pretty much just the hyper-v roll.

There are 4 VM’s:

* SBS01 = Small Business Server 2011 Standard

* APP01 = Server 2008 R2 Standard

* W7E01/W7E02 = 2x Win 7 for testing/etc

Backups on SBS01/APP01 run without issue. The Win 7 VM’s dont backup. The problem is with the hosts (HVS01) backups, they always fail with the below error in event log.

vssadmin list writers also shows up an error for the «Microsoft Hyper-V VSS Writer» (also included below).

I’ve noticed that when I try to run a backup maunally, APP01 will go into a saved state, then SBS01/W7E0* will «Create VSS snapshop set» (and stay running), then APP01 will come back up. The reason I mention this as being a bit strange is because all 4 VM’s
have the ‘Backup (Volume snapshot)’ option selected under integration services. So I would expect none of them to be entering a saved state.

On the subject on IS… I have checked the version number on the host and VM’s and they are all the same (6.0.7601.17514)

I’ve also tried the usual delete/recreate backups, backup to different location, etc. All with no result.

If anyone is able to point me in the right direction it would be much appreciated.

Thanks.

========== EVENT LOG ==========

Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          27/03/2012 4:09:33 AM
Event ID:      521
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      HVS01.domain.local
Description:
The backup operation that started at ‘‎2012‎-‎03‎-‎26T17:00:39.891000000Z’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code ‘2155348129’. Please review the event
details for a solution, and then rerun the backup operation once the issue is resolved.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
  <System>
    <Provider Name=»Microsoft-Windows-Backup» Guid=»{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}» />
    <EventID>521</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime=»2012-03-26T17:09:33.208964000Z» />
    <EventRecordID>5240</EventRecordID>
    <Correlation />
    <Execution ProcessID=»5992″ ThreadID=»5184″ />
    <Channel>Application</Channel>
    <Computer>HVS01.domain.local</Computer>
    <Security UserID=»S-1-5-18″ />
  </System>
  <EventData>
    <Data Name=»BackupTime»>2012-03-26T17:00:39.891000000Z</Data>
    <Data Name=»ErrorCode»>2155348129</Data>
    <Data Name=»ErrorMessage»>%%2155348129</Data>
  </EventData>
</Event>

========== VSSADMIN LIST WRITERS ==========

vssadmin 1.1 — Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 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: ‘Microsoft Hyper-V VSS Writer’
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {a26a4279-edf8-40b0-8987-292f26b0e2d6}
   State: [5] Waiting for completion
   Last error: Unexpected error

Writer name: ‘System Writer’
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {82d1a0a5-a2c9-411c-9220-ee646d8c572e}
   State: [5] Waiting for completion
   Last error: No error

Writer name: ‘ASR Writer’
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {3e731784-6b46-4533-b6ec-bfc9c2632e05}
   State: [1] Stable
   Last error: No error

Writer name: ‘Shadow Copy Optimization Writer’
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {ff42ee3f-5ee8-4123-b8d9-595f52b6eb6e}
   State: [1] Stable
   Last error: No error

Writer name: ‘Registry Writer’
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {51bc7f59-417a-4f4d-82bf-58aa022cb964}
   State: [1] Stable
   Last error: No error

Writer name: ‘COM+ REGDB Writer’
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c834063a-5d07-44d8-a214-d2be1c6b4f57}
   State: [1] Stable
   Last error: No error

Writer name: ‘BITS Writer’
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {38bcc839-eed0-44d8-a64f-c79a32746a0b}
   State: [1] Stable
   Last error: No error

Writer name: ‘WMI Writer’
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {143ee2f9-c44d-4f9f-83cc-34f2ab989b6a}
   State: [5] Waiting for completion
   Last error: No error

Are you stuck with hyper-v VSS writer failed? We can help you fix it.

This error occurs when the VSS writer service failed.

At Bobcares, we often get requests regarding Hyper-V as a part of our Server Management Services.

Today let’s discuss how our Support Engineers resolve Hyper-v VSS writer failed for our customers.

Causes for Hyper-v VSS writer failed

Volume Shadow Copy is a windows service that helps capture and creates snapshots. The VSS writer tells the backup tool how to back up the data.

Causes for the error is when VSS writers fail. There are multiple reasons for the VSS writer to fail.

One of the common reason is when two or more resources try to use the writer at the same time.

Thus, to resolve the error we restart the service or reset the VSS WMI writer.

Let’s discuss how our Support Engineers resolve this error for our customers.

How to fix Hyper-v VSS writer failed

Recently one of our customers contacted us regarding writer failure error. Let’s now discuss how our Support Engineers resolve the error for our customers.

Restarting failed writer service

First, we open the command prompt with administrative privilege.

Then we find out the failed writers using the command

vssadmin list writers

Then we find the service corresponding to the VSS writer.

After that, restart windows service corresponding to the writer. After restarting the service we check the writers.

The VSS writers were all stable.

Thus, it resolves the error.

Re-register the writers

Recently one of the customer contacted us regarding the same error. We restarted the service but still, the error was occurring. The available option is to reset the WMI Writers. Let’s discuss how our Support Engineers resolve the error for our customer.

To re-register the VSS WMI Writer we open the command prompt with administrator privileges.

We move to the directory wbem using the command

cd %windir%system32wbem

And we use the below commands to reset the WMI writer.

for /f %s in ('dir /b *.dll') do regsvr32 /s %s

wmiprvse /regserver

winmgmt /regserver

Thus, we reset the VSS WMI writer to resolve the error.

Service not running in the client-server

One of the common reasons for this error to occur is that the service might be not running. Thus, our Support Engineers start the service from the Hyper-V manager.

To restart the service from Hyper-V Manager. We Open Hyper-V Manager.

Then we click on the name of the server. In the Actions pane, we click Start Service.

Thus, it resolves the error.

[Need assistance with Hyper-V error – We can help you fix it]

Conclusion

In short, we have discussed the causes for the ‘Hyper-V VSS writer failed’ error to occur. Also, we have discussed how our Support Engineers resolve the error for our customers.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Большинство решений для резервного копирования данных под Windows в том или ином виде используют возможности службы теневых копий (VSS — Volume Shadow Copy Service) для создания копий данных приложений или сервисов. В некоторых случаях, служба VSS или один из ее модулей записей начинают работать некорректно, в результате чего не удается выполнить нормальную процедуру резервное копирования данных. Я сталкивался с такой ошибкой на Exchange, MSSQL и Hyper-V серверах. Для быстрого восстановления службы VSS и ее компонентов я использую следующую инструкцию.

Чтобы определить сбойный модуль VSS, выведем список зарегистрированных в системе модулей записи VSS (Writers) с помощью команды vssadmin.

vssadmin list writers

В списке компонентов ищем те, которые находятся в состоянии Failed (для нормально работающих компонентов статус должен быть State: [1] Stable)

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-6ded-4f4b-8f17-fd23f8ddcfb7}
Writer Instance Id: {31b56ab0-9588-412f-ae7b-cdc375347158}
State: [7] Failed
Last error: Retryable error

Как вы видите, в нашем случае модуль записи Microsoft Exchange Writer находится в сбойном состоянии (State: [8] Failed), поэтому резервное копирование Exchange выполнить не удастся. Как правило, чтобы исправить состояние такого компонента, достаточно перезагрузить сервер (что не всегда возможно по производственным причинам).

Чтобы починить модуль записи, нужно попробовать перезапустить связанную с ним службу (в таблице ниже содержится список соответствия типовых VSS Writer и связанных с ними служб Windows). Помимо остановки службы, иногда приходится руками завершать процесс зависшей службы.

Еще раз выполните команду

vssadmin list writers

Проверьте статус проблемного модуля записи. Если он не изменился на Stable и проблема не исправлена, можно попробовать перерегистрировать компоненты и библиотеки службы VSS.

Перейдите в каталог:

cd c:windowssystem32

Остановите службы Volume Shadow Copy и Microsoft Software Shadow Copy Provider

Net Stop VSS
Net Stop SWPRV

Перерегистрируйте компоненты VSS:

regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register

Теперь осталось запустить остановленные службы:
Net Start SWPRV
Net Start VSS

Проверьте, пропала ли ошибка у проблемного модуля записи VSS.

Данный метод перезапуска и перерегистрации компонентов VSS эффективен, как на Windows Server 2008 / 2012/ R2, так и на Windows Server 2016.