Добрый день!
Есть кластер Hyper-V 2012 R2 из двух узлов. Физический DPM 2012 R2, агенты которого стоят на хостах Hyper-V.
При попытке забекапить виртуальную машину (Win2008R2 + Exchange 2010) падает VSS, как на хосте гипервизора (Microsoft Hyper-V VSS Writer) так и на самой виртуальной машине (System Writer).
На гипервизоре появляется ошибка 8229:
Событие отклонено модулем записи VSS с ошибкой 0x800423f4, Повторяющаяся ошибка средства записи. Эта ошибка вероятно будет
возникать снова при повторении попытки архивации.
. Изменения компонентов модуля записи, выполненные модулем при обработке события, будут недоступны запрашивающей стороне. Связанные события, поступающие от приложения, в котором размещен модуль записи VSS, см. в журнале событий.
Операция:
Событие PrepareForSnapshot
Контекст:
Контекст выполнения: Writer
Код класса модуля записи: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Имя модуля записи: Microsoft Hyper-V VSS Writer
Код экземпляра модуля записи: {5ac30ac2-f61e-4e65-a879-715e64384fa3}
Командная строка: C:Windowssystem32vmms.exe
Идентификатор процесса: 8384
В ВМ появляется две ошибки:
22
Ошибка службы теневого копирования томов: не зарегистрирован критический компонент, необходимый для службы теневого копирования томов. Это может быть следствием ошибки при установке Windows или при установке поставщика теневого копирования. Ошибка возвращена функцией CoCreateInstance для класса с CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} и именем SW_PROV: [0x80040154, Класс не зарегистрирован
].
Операция:
Получение интерфейса с возможностью вызова для данного поставщика
Перечисление интерфейсов всех поставщиков, поддерживающих данный контекст
Удаление теневых копий
Контекст:
Код поставщика: {74600e39-7dc5-4567-a03b-f091d6c7b092}
Код класса: {3e02620c-e180-44f3-b154-2473646e4cb8}
Контекст моментального снимка: -1
Контекст моментального снимка: -1
Контекст выполнения: Coordinator
и 12292
Ошибка теневого копирования тома: Ошибка при создании класса поставщика теневого копирования COM с CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} [0x80040154, Класс не зарегистрирован
].
Операция:
Получение интерфейса с возможностью вызова для данного поставщика
Перечисление интерфейсов всех поставщиков, поддерживающих данный контекст
Получение свойств теневой копии
Удаление теневых копий
Контекст:
Код поставщика: {74600e39-7dc5-4567-a03b-f091d6c7b092}
Код класса: {3e02620c-e180-44f3-b154-2473646e4cb8}
Контекст моментального снимка: -1
Контекст моментального снимка: -1
Контекст выполнения: Coordinator
Контекст выполнения: Coordinator
Служба интеграции установлена самая свежая. Перенос ВМ на другой узел, рестарт ВМ и хостов не меняет ситуации.
Остальные ВМ различных ОС бэкапятся без ошибок, так же внутри проблемной ВМ стоит агент DPM и так же успешно бэкапит базы Exchange.
Пробовал отключать архивацию (контрольные точки тома) в службах интеграции проблемной ВМ — так же не помогло, только перестал падать VSS внутри ВМ.
Чтение кучи веток на английском течнете так же не привели к положительным результатам.
-
Изменен тип
16 июня 2014 г. 7:28
Event ID 8229 — VSS Writer Operations
Updated: January 27, 2011
Applies To: Windows Server 2008 R2
Volume Shadow Copy Service (VSS) writers are applications or services that store persistent information in files on disk and that provide the names and locations of these files to requesters by using the shadow copy interface.
Event Details
| Product: | Windows Operating System |
| ID: | 8229 |
| Source: | VSS |
| Version: | 6.1 |
| Symbolic Name: | VSS_WARNING_WRITER_EVENT_FAILED |
| Message: | A VSS writer has rejected an event with error %1. 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. %2 |
Resolve
Retry the operation and restart the writer if necessary
This event indicates a problem with a Volume Shadow Copy Service (VSS) writer.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Retry the operation and restart the writer
To retry the operation and restart the writer:
- Retry the backup or restore operation that caused the error condition.
- If this does not resolve the issue, restart the service or process that hosts the writer, and retry the operation.
- If this does not resolve the issue, open Event Viewer as described in the “Open Event Viewer and view events related to VSS” section and look for events related to the service or process that hosts the writer. If necessary, restart the service or process, and retry the operation.
- If this does not resolve the issue, restart the computer, and retry the operation.
- If restarting the computer does not resolve the issue, provide the Event Viewer information to the vendor whose application is indicated in the event text.
Open Event Viewer and view events related to VSS
To open Event Viewer and view events related to VSS:
- Click Start, click Run, type eventvwr.msc, and then click OK. If the User Account Control dialog box appears, ensure that the action it displays is what you want, and then click Continue.
- In Event Viewer, expand Windows Logs, and then click Application.
- To filter the events so that only events with a Source of VSS are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources drop-down list, select the checkbox for VSS. Select other options as appropriate, and then click OK.
- To sort the displayed events by date and time, in the center pane, click the Date and Time heading.
Verify
To verify that the Volume Shadow Copy Service (VSS) writers are operating correctly, perform the following procedure, and then retry the previous VSS operation.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To verify that the Volume Shadow Copy Service (VSS) writers are operating correctly:
- Open an elevated Command Prompt window. Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
- Type vssadmin list writers, and then press Enter.
- Ensure that all writers are in the Stable state and are operating without errors.
For more information about the vssadmin command, see http://go.microsoft.com/fwlink/?LinkId=103401.
Related Management Information
VSS Writer Operations
File Services
Hopefully this is the right group to post this to. I’m trying to use a third party backup solution to backup our SQL databases using VSS but it has not been successful because we’re experiencing VSS issues. When running «vssadmin list writers» the ‘SqlServerWriter’ fails:
Writer name: ‘SqlServerWriter’
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {548b4a35-35fa-4f2f-b8c6-f5a285f696db}
State: [8] Failed
Last error: Non-retryable error
When looking the event viewer for VSS errors i see two repeatedly.
1. Event ID 8193
Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEMCurrentControlSetServicesVSSDiag,…). hr = 0x80070005, Access is denied.
.
Operation:
Initializing Writer
Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {e0c429a2-971e-491d-ad9c-3df3f8cb6ddc}
2. Event ID 8229
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to 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: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server Code-Named ‘Denali’ CTP2:SQLWriter
Writer Instance ID: {548b4a35-35fa-4f2f-b8c6-f5a285f696db}
Command Line: «C:Program FilesMicrosoft SQL Server90Sharedsqlwriter.exe»
Process ID: 1852
After contacting the vendor of the backup solution, they pointed out that those are the cause of the backups failing. So far I’ve tried restarting the «volume shadow copy service» and the «SQL Server VSS Writer» but hasn’t worked. Also I tried to re-register the VSS service buy running the script below but still no luck
cd /d %windir%system32
net stop vss
net stop swprv
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
They mentioned that the server may need a reboot to resolve the issue and it did resolve the 8193 error however 8229 persists along with a SQLVDI error. See blow:
SQL Server 2012 Developer SQL Server 2012 Enterprise SQL Server 2012 Standard More…Less
Symptoms
Assume that you have a database that has a case-sensitive collation in Microsoft SQL Server 2012 Service Pack 2 (SP2). When you try to back up AlwaysOn secondary databases by using Volume Shadow Copy Service (VSS), you may receive the following messages in the Windows Application log:
(VSS Source)
Source: VSS
EventID: 8229
EventType: 2
DateTime: 9-7-2014 14:22:46.000
Timestamp: 0x01cf9b707d6d6f00
Description:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to 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.
(From SQLVDI)
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=1584. Thread=7244. Client. Instance=. VD=Global{6483442C-256E-4F85-85C4-E5A611ED9A88}1_SQLVDIMemoryName_0.
…
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1940. Thread=1824. Server. Instance=MSSQLSERVER. VD=Global{6483442C-256E-4F85-85C4-E5A611ED9A88}1_SQLVDIMemoryName_0.
You also receive the following messages in the SQL Server ERRORLOG:
<Date> <Time> Backup Error: 3041, Severity: 16, State: 1.
<Date> <Time> Backup BACKUP failed to complete the command BACKUP DATABASE model. Check the backup application log for detailed messages.
<Date> <Time> spid<ID> Error: 18210, Severity: 16, State: 1.
<Date> <Time> spid<ID> BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device ‘{4E35DA4A-BAF7-4EC2-8421-EA7A3C0B7B31}1’. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Additionally, if you take a Profiler trace during running the VSS backup, when you run the following query:
SELECT 1 FROM SYS.AVAILABILITY_REPLICAS AS AR INNER JOIN SYS.DATABASES AS D ON DB_ID(N'TargetDatabase') = D.DATABASE_ID AND AR.REPLICA_ID = D.REPLICA_ID INNER JOIN SYS.DM_HADR_AVAILABILITY_REPLICA_STATES ST ON AR.REPLICA_ID = ST.REPLICA_ID AND ST.ROLE = 2
It fails, and you receive the following error message:
Error:208, Severity:16, State:1
Invalid object name ‘SYS.AVAILABILITY_REPLICAS’.
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 2 for SQL Server 2012 SP2 /en-us/help/2983175
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
-
Latest cumulative update for SQL Server 2012 SP2
Notes for this updateIf you apply this update to one of the localized versions of SQL Server such as Japanese version of SQL Server, you have to follow these additional steps to install SQL Server VSS Writer update:
-
Run SQLServer2012-KB2983175-x64.exe to install cumulative update 2 for SQL Server 2012 SP2.
-
Extract the package by using the following command line:
SQLServer2012-KB2983175-x64.exe /X:<target folder>
-
Prepare the original installation media.
-
Execute the following command to apply SQL Server VSS Writer related update:
msiexec /i <path to sqlwriter.msi file in the original installation media> /l*v<setup log file name> PATCH=<sqlwriter.msp file in the folder created in step 1>
For example:
msiexec /i «D:1041_JPN_LPx64Setupx64SqlWriter.msi» /l*v C:Tempsqlwriter.log PATCH=»C:SQL2012SP2CU21033_enu_lpx64setupx64sqlwriter.msp»
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.