2155348129 오류코드

자동 백업 처리를 걸려고 하는대 트러블슈팅이 일어 난다

VSS 이슈로 보이는대.... 아직 해결 방법은 찾지를 못하고

개발기 서버라 MS-SQL ,  Oracle  , My-SQL 돌고 있고 에러 코드는 다음과 같다.

백업되는 볼륨의 섀도 복사본을 만들기 위한 볼륨 섀도 복사 서비스 작업에 실패하여 '‎2012‎-‎09‎-‎14T02:42:51.189000000Z'에서 시작된 백업 작업에 오류가 발생했습니다. 오류 코드는 '2155348129'입니다. 이벤트 세부 정보에서 해결 방법을 확인하고 문제를 해결한 후 백업 작업을 다시 실행하십시오.

0x800423f4, 작성자에게 임시 오류가 발생했습니다. 백업 프로세스를 다시 시도하면

오류가 다시 발생할 수 있습니다.

 오류로 인해 VSS 기록기가 이벤트를 거부했습니다 . 이벤트 처리 중 기록기 구성 요소에 대한 변경 내용은 요청자가 사용할 수 없습니다. VSS 기록기를 호스트하는 응용 프로그램 이벤트 로그에서 관련 이벤트가 있는지 확인하십시오. 

작업:

   PrepareForBackup 이벤트

컨텍스트:

   실행 컨텍스트: Writer

   작성기 클래스 ID: {26d02976-b909-43ad-af7e-62a4f625e372}

   작성기 이름: Oracle VSS Writer - ORCL

   작성기 인스턴스 이름: ORCL

   작성기 인스턴스 ID: {83f2ede9-bcea-4be0-b83f-3cbee537fcb5}

   명령줄: D:\app\Administrator\product\11.1.0\db_1\bin\OraVSSW.exe ORCL

   프로세스 ID: 2700

VSS-00044: Database in NOARCHIVELOG mode must be in a consistent state for backup.  

Cause : The database was open read/write or mounted after a SHUTDOWN IMMEDIATE or SHUTDOWN ABORT.  

Action : Either mount the database in a consistent state or open it read-only to back up the database files.  

Additional info :

Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production

Oracle VSS writer version 11.1.0.6.0 Production

Error at line : 4561

Failure on PrepareForBackup event

.

This article applies to the following operating systems:

• Windows Server® 2008 
  
  
• Windows Server® 2008 R2 

Troubleshooting

---

Below are the steps that you should follow to troubleshoot errors where the cause is reported by an underlying layer of Windows Server Backup. Typically this involves using Event Viewer.

General troubleshooting

---

1. Check the event log for failure events logged by Windows Server Backup by opening the Event Viewer and review the logs: Windows Logs\Application where the source is Backup.

2. Identify which application or layer caused the issue. The event in the previous step will usually indicate which layer or application caused the failure. For example, where VSS is the cause, you may see the following message:

   Check VSS event log for details
   

   Check the event log for the problematic application reported in the failure event.

3. Analyze the events belonging to the application to understand the root cause. The events may point to issues in a different application. To do so, search for the events logged by the application found in step 2. For example, for errors caused by VSS, search for all events where the value in the Source column is VSS.

4. Repeat step 2 and step 3 until you get to the root cause of the problem and then correct the problem.

Sample Issue:

When running Windows Server Backup, you receive the following error: A Volume Shadow Copy Service operation failed. 
C:\TEMP>wbadmin start backup -include:d:,i: -backuptarget:f: -quiet
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.


Retrieving volume information...
This will back up volume NTFSTest(D:),Local Disk(I:) to f:.
The backup operation to F: is starting.
Creating a shadow copy of the volumes specified for backup...
The backup operation stopped before completing.
Summary of the backup operation:
------------------


The backup operation stopped before completing.
Detailed error: A Volume Shadow Copy Service operation failed.

More in-depth troubleshooting steps

---

1. Check the event log for failure events logged by Windows Server Backup. Upon checking the Backup application event log, the following message is found:The backup operation that started at '?2009?-?07?-?09T06:30:12.721000000Z' 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'. Review the event details for a solution. Rerun the backup operation once the issue is resolved.

2. Identify which application or layer caused the issue. From the backup event it is evident that the issue is caused by a VSS error.

3. Analyze events belonging to the application to understand the root cause. Upon checking the VSS application event logs, the following warning event is found:

   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.
   

   If the backup process is retried, the error may not reoccur.

Changes that the writer made to its 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: {25785983-e057-4b58-8d90-d0a7ef6c1a22}
   Command Line: C:\Windows\system32\vmms.exe
   Process ID: 10632

Continued troubleshooting steps

---

1. Identify which application or layer caused the issue. From the VSS event it is evident that the issue is caused by Hyper-V error.

2. Analyze events belonging to the application to understand the root cause. Upon checking the Hyper-V application event logs found atApplications and Services Logs\Microsoft\Windows\Hyper-V-VMMS, the following warning event is present:

   Failed to create the backup of virtual machine 'TestVM'. (Virtual machine ID XXXX)
   

3. Identify which application or layer caused the issue. From the Hyper-V event it is evident that the issue is caused by a virtual machine named TestVM.

4. Analyze events belonging to the application to understand the root cause. Upon checking the application event logs inside the guest,TestVM, the following VSS event is found: There is not enough disk space to create the volume shadow copy on the storage location. Make sure that, for all volumes to be backup up, the minimum required disk space for shadow copy creation is available. This applies to both the backup storage destination and volumes included in the backup. If this occurs, besure that the following minimum requirements are met:

   For volumes less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more than 500 megabytes, the minimum is 320 megabytes of free space. It is recommended that least 1 gigabyte of free disk space on each volume if the volume size is more than 1 gigabyte.

5. Correct the problem. The above error indicates that freeing up space on the physical volume hosting TestVM will solve the issue.

Error List Tables

---

Windows Server Backup Error List

 

HRESULT	HRESULT (in hex)	Error Message
2155348129	0x807800A1	A Volume Shadow Copy Service operation failed. Please check "VSS" and "SPP" application event logs for more information.
2155347999	0x8078001F	Windows Backup cannot find the shared protection point.
2155348000	0x80780020	Windows Backup cannot find the shadow copy of the source volume.
2155348001	0x80780021	Windows Backup timed-out before the shared protection point was created.
2155348002	0x80780022	Windows Backup failed to create the shared protection point.
2155348003	0x80780023	The on-disk writer metadata file is corrupted.
2155348004	0x80780024	The specified Windows installation point does not contain a system ID file.
2155348005	0x80780025	The operation to create the shared protection point was canceled.
2155348075	0x8078006b	Windows Backup failed to create the shared protection point on the source volumes.
2155348106	0x8078008a	Error: The read operation from the volume shadow copy on one of the source volumes failed. Make sure all the volumes included in the backup operation are available and accessible, and then retry the operation.

VSS Error List

 

HRESULT	HRESULT (in hex)	Error Message
2147754996	0x800423F4	The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur.
2147754806	0x80042336	The writer experienced a partial failure. Check the component level error state for more information.
2147754995	0x800423F3	The writer experienced a transient error. If the backup process is retried, the error may not reoccur.
2147754992	0x800423F0	The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer.
2147754754	0x80042302	A Volume Shadow Copy Service component encountered an unexpected error.  Check the Application event log for more information.
2147754796	0x8004232C	The specified volume is nested too deeply to participate in the VSS operation.
2147754777	0x80042319	A writer did not respond to a GatherWriterStatus call. The writer may either have terminated or it may be stuck. Check the System and Application event logs for more information.
2147754769	0x80042311	The given XML document is invalid. It is either incorrectly-formed XML or it does not match the schema.

SPP Error List

 

HRESULT	HRESULT (in hex)	Error Message
2164261121	0x81000101	The creation of a shadow copy has timed out. Try this operation again.
2164261126	0x81000106	The backup process failed due to an internal error. For more information view the event log.
2164261128	0x81000108	Windows cannot create a shadow copy on the specified disk. Please choose another disk.