배포 KB: Avamar: Hyper-V VM 백업이 VSS 기록기 오류와 함께 실패함
本文适用于
本文不适用于
本文并非针对某种特定的产品。
本文并非包含所有产品版本。
症状
"다른 이름으로 로그인"이 로컬 시스템 계정으로 설정됩니다(Windows의 LocalSystem 계정은 로컬 리소스에 대한 완전 무제한 액세스 권한이 있음).
Source - VSS
Event -
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: {6XXX1cd4-6ded-4f4b-8f17-fdXXf8XXc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {bXXX2dc4-972d-4c8c-9008-95XXXbe724ba}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 240
======================
게스트 VM 백업이 VSS 기록기 오류와 함께 실패합니다.
아래 다양한 구성 요소의 로그에서 메시지를 확인합니다.
아래 다양한 구성 요소의 로그에서 메시지를 확인합니다.
- Avtar 로그:
avhypervvss Info <12587>: 'Cluster Shared Volume VSS Writer' reported partial failure, checking individual components for failure
avhypervvss Error <12588>: Writer component '139FAABC-9EC2-4886-B571-9AC6EDA30864<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:b20d28ce-768a-4bd4-91fa-ae8554e6639e:<Hostname-guestVM></CSV>' ( <Hostname-guestVM><139FAABC-9EC2-4886-B571-9AC6EDA30864<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:b20d28ce-768a-4bd4-91fa-ae8554e6639e:<Hyper-vHostname></CSV>> ) reported an error!
Failure code: 0x800423f4 : The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
Error Description: Unknown
avhypervvss Warning <41746>: Vss snapshot failed for VM GuestVMHostname<139FAABC-9EC2-4886-B571-9AC6EDA30864>. Skipping from backup target list
======================
avhypervvss Error <12588>: Writer component '139FAABC-9EC2-4886-B571-9AC6EDA30864<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:b20d28ce-768a-4bd4-91fa-ae8554e6639e:<Hostname-guestVM></CSV>' ( <Hostname-guestVM><139FAABC-9EC2-4886-B571-9AC6EDA30864<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:b20d28ce-768a-4bd4-91fa-ae8554e6639e:<Hyper-vHostname></CSV>> ) reported an error!
Failure code: 0x800423f4 : The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
Error Description: Unknown
avhypervvss Warning <41746>: Vss snapshot failed for VM GuestVMHostname<139FAABC-9EC2-4886-B571-9AC6EDA30864>. Skipping from backup target list
======================
- Hyper-V 시스템 이벤트 로그:
Source - VDS Basic Provider
Event - Unexpected failure. Error code: 48F@01000003
Event - Unexpected failure. Error code: 48F@01000003
Hyper-v Application Event Log-
Source - VSS
Event -
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: {6XXX1cd4-6ded-4f4b-8f17-fdXXf8XXc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {bXXX2dc4-972d-4c8c-9008-95XXXbe724ba}
Command Line: C:\Windows\system32\vmms.exe
Process ID: 240
======================
- 게스트 VM 애플리케이션 이벤트 로그:
Source - VSS
Event-
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3XXX620c-e180-44f3-b154-24XXX46e4cb8} [0x80040154, Class not registered].
Operation:
Obtain a callable interface for this provider
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set
Context:
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Class ID: {00000000-0000-0000-0000-000000000000}
Snapshot Context: 0
Execution Context: Coordinator
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Volume Name: \\?\Volume{23663f2d-d539-11e3-8c32-00155df54207}\
Execution Context: Coordinator
------------------------------------
Source - VSS
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 {3XXX620c-e180-44f3-b154-24XXX46e4cb8} and Name SW_PROV is [0x80040154], Class not registered
Operation:
Obtain a callable interface for this provider
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set
Context:
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Class ID: {00000000-0000-0000-0000-000000000000}
Snapshot Context: 0
Execution Context: Coordinator
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Volume Name: \\?\Volume{23663f2d-d539-11e3-8c32-00155df54207}\
Execution Context: Coordinator
======================
Event-
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {3XXX620c-e180-44f3-b154-24XXX46e4cb8} [0x80040154, Class not registered].
Operation:
Obtain a callable interface for this provider
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set
Context:
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Class ID: {00000000-0000-0000-0000-000000000000}
Snapshot Context: 0
Execution Context: Coordinator
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Volume Name: \\?\Volume{23663f2d-d539-11e3-8c32-00155df54207}\
Execution Context: Coordinator
------------------------------------
Source - VSS
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 {3XXX620c-e180-44f3-b154-24XXX46e4cb8} and Name SW_PROV is [0x80040154], Class not registered
Operation:
Obtain a callable interface for this provider
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set
Context:
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Class ID: {00000000-0000-0000-0000-000000000000}
Snapshot Context: 0
Execution Context: Coordinator
Provider ID: {7XXX0e39-7dc5-4567-a03b-f0XXX6c7b092}
Volume Name: \\?\Volume{23663f2d-d539-11e3-8c32-00155df54207}\
Execution Context: Coordinator
======================
原因
이전 백업 소프트웨어에는 AD 계정으로 설정된 게스트 VM에 볼륨 섀도 복사본 서비스에 대한 서비스 계정이 있었습니다.
解决方案
절차
- 게스트 VM에서 services.msc 콘솔을 엽니다.
- "볼륨 섀도 복사본" 서비스 > 속성 > 로그온 > "이 계정"에서 "로컬 시스템 계정"으로 변경을 찾습니다.
受影响的产品
Avamar产品
Avamar, Avamar Plug-in for Hyper-V VSS文章属性
文章编号: 000058312
文章类型: Solution
上次修改时间: 14 4月 2021
版本: 3
从其他戴尔用户那里查找问题的答案
支持服务
检查您的设备是否在支持服务涵盖的范围内。