** 응용 프로그램 로그
이벤트 ID 8193
볼륨 섀도 복사본 서비스 오류 : RegSaveKeyExW 루틴을 호출하는 중 예기치 못한 오류가 발생했습니다. hr = 0x800708f8
뒤에 해당 헥사코드 이벤트 이유가 시스템 이벤트랑 동일하다. (레지스트리 I/O 문제, 이벤트 ID 333)
** 시스템 로그
이벤트 ID 333
레지스트리에서 초기화된 I/O 작업에 복구할 수 없는 오류가 발생했습니다.
레지스트리의 시스템 이미지를 포함하는 파일 중의 하나를 읽거나 쓰거나 내용을 지울 수 없습니다.
Hi,
Latest error code according to the events ahred indicates following:
Hex Code (hr)= 0x800703f8
An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.
It looks like registry went into some bad state. Is it possible for you to restart the machine and retry backup. Restart should put registry in the clean state.
Let me know the results.
Thanks,
Neha-MSFT
------------------------------
VSS - backup failed - RegSaveKeyExW. hr = 0x800703f8. 
-
Hi all,
My server now has a problem cannot take full backup and found below event logs.
vssadmin version: 5.2.3790.3959
please take a look.
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 8193
Date: 26/09/2011
Time: 9:17:38 AM
User: N/A
Computer: VMKLCU3AUMQ601
Description:
Volume Shadow Copy Service error: Unexpected error calling routine RegSaveKeyExW. hr = 0x800703f8.Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12289
Date: 26/09/2011
Time: 9:17:39 AM
User: N/A
Computer: VMKLCU3AUMQ601
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy59 - 0000016C,0x00090020,00AD3060,0,00ADC040,4096,[0]). hr = 0x80070005.
Regards, Wee YangWednesday, September 28, 2011 6:34 AM
Question
Answers
-
Hi ,
According to the description, firstly, please try the following solutions:
1) Reboot the server,It may be supposed to solve your issue.
2) See if you get event log issues before you start the backup.Secondly, if the problem continues , I want to know the info as bellows:
What kinds of OS of your server?windows2003? if it is, take the following steps to troubleshoot your issue:
Would you please view and request hotfixs that is mentioned in the following Microsoft KB article and apply on the problematic server to check if it is helpful?
The backup application stops responding when you perform a backup that uses a volume snapshot in Windows Server 2003 with SP1
http://support.microsoft.com/kb/923628A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
http://support.microsoft.com/kb/833167
A new Volume Shadow Copy Service update is now available that fixes various Volume Shadow Copy Service problems in Windows Server 2003
http://support.microsoft.com/kb/913648
Please reboot the problematic server after applying these updates.Best Regards,
Jeff Ren
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by Jeff RenModerator Friday, September 30, 2011 9:05 AM
- Edited by Jeff RenModerator Friday, September 30, 2011 9:06 AM
Wednesday, September 28, 2011 9:52 AMJeff RenJeff Ren
wicresoft
Recent AchievementsForums Replies IV First Helpful Vote Forums Curator IIIwicresoft10,505 Points
All replies
-
Hi,
Latest error code according to the events ahred indicates following:
Hex Code (hr)= 0x800703f8
An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry.
It looks like registry went into some bad state. Is it possible for you to restart the machine and retry backup. Restart should put registry in the clean state.
Let me know the results.
Thanks,
Neha-MSFT
Wednesday, September 28, 2011 9:24 AMNeha.AgrawalNeha.Agrawal
Microsoft
MSFT
Recent AchievementsForums Answerer II First Answer Confirmed Forums Replies IMicrosoft(MSFT)355 Points -
Hi ,
According to the description, firstly, please try the following solutions:
1) Reboot the server,It may be supposed to solve your issue.
2) See if you get event log issues before you start the backup.Secondly, if the problem continues , I want to know the info as bellows:
What kinds of OS of your server?windows2003? if it is, take the following steps to troubleshoot your issue:
Would you please view and request hotfixs that is mentioned in the following Microsoft KB article and apply on the problematic server to check if it is helpful?
The backup application stops responding when you perform a backup that uses a volume snapshot in Windows Server 2003 with SP1
http://support.microsoft.com/kb/923628A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003
http://support.microsoft.com/kb/833167
A new Volume Shadow Copy Service update is now available that fixes various Volume Shadow Copy Service problems in Windows Server 2003
http://support.microsoft.com/kb/913648
Please reboot the problematic server after applying these updates.Best Regards,
Jeff Ren
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked as answer by Jeff RenModerator Friday, September 30, 2011 9:05 AM
- Edited by Jeff RenModerator Friday, September 30, 2011 9:06 AM
Wednesday, September 28, 2011 9:52 AMJeff RenJeff Ren
wicresoft
Recent AchievementsForums Replies IV First Helpful Vote Forums Curator IIIwicresoft10,505 Points -
the file version in the KB923628 is 5.2.3790.2762 but compare to the server 5.2.3790.3790 which is up to date in the server.
so i believe this KB is not compatible in my server
however i will try a reboot and see if the error gone.
Regards, Wee YangThursday, September 29, 2011 1:23 AM -
whether you have rebooted your server? any update for your issue?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Edited by Jeff RenModerator Friday, September 30, 2011 2:14 AM
Thursday, September 29, 2011 3:56 AMJeff RenJeff Ren
wicresoft
Recent AchievementsForums Replies IV First Helpful Vote Forums Curator IIIwicresoft10,505 Points -
server after reboot, error gone until now. backup running fine now. thanks!
Regards, Wee YangFriday, September 30, 2011 3:31 PM -
you're welcome.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.Friday, September 30, 2011 11:44 PMJeff RenJeff Ren
wicresoft
Recent AchievementsForums Replies IV First Helpful Vote Forums Curator IIIwicresoft10,505 Points -
Dear jeff i have 2 problems ..Frequently Backup exec failed Exchange Jobs. always we need tu restart the services or restart the server please give me a permanent solution.
Backup Exec errors... Final error: 0xe000fed1 - A failure occurred querying the Writer status. Final error category: Resource Errors.V-79-57344-65233 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer failed. The operation cannot be retried (0x800423f4), State: Failed during prepare snapshot operation (8).
Event Viewer errors.. Volume Shadow Copy Service error: Unexpected error calling routine RegSaveKeyExW. hr = 0x800703f8.Backup Exec error during Exchange backup.. Final error: 0xe000037b - Using the job settings, Backup Exec attempted to back up the passive copy of the Exchange database. However, the passive copy was not available after the Microsoft Volume Shadow Copy Service (VSS) snapshot was performed. Try to run the job again. Final error category: Resource Errors..
Environment. Windows Server 2003 SP2, Backup Exec 12.5, Exchange Server 2007Please Help !!!
Monday, October 03, 2011 8:16 AM
----------------------------------------------------------------------
https://community.emc.com/thread/147350
I have to say that I have never been more frustrated by a problem as I have been with VSS and Disaster Recovery backups. As they all seem to be a little different from one another and there seem to be precious few answers. 
That said, i am hoping somebody can give me some advice. I have a handful of x64 Server 2008 R2 (SQL Cluster) servers that I am backing up. Not using the Microsoft module for backup just going after the .bak files (politics). When i try to back these servers up the DISASTER RECOVERY fails with this error:
savegrp: suppressed 4 lines of output.
77777:save: Added writer Registry Writer to disaster recover backup.
77777:save: Added writer Task Scheduler Writer to disaster recover backup.
77777:save: Added writer VSS Metadata Store Writer to disaster recover backup.
77777:save: Added writer Performance Counters Writer to disaster recover backup.
77776:save: ERROR: Failed to add writer System Writer to disaster recover backup, error=0x80070002.
77774:save: ERROR: Error adding writer to the snapshot set. ERROR=0x80070002.
77775:save: Processing completed for disaster recover backup.
80520:save: ASR Backup..Critical error creating snapshot of ASR critical volumes and cannot continue.
83449:save: Error occured while saving critical volumes.
<ERROR> : Failed with error(s)
I am running Networker 7.6.3.7 both server and client side. I have tried a half a dozen or more microsoft KB article fixes with no success. Anyone have any ideas?
Thank you in advance,
Jim
This is the error from the drsave.log
VSS .. GetVolumeMountPoint failed for p:\usr\sap\piu\scs02\exe – 2
And the only file that is failing from disk shadow output
File List: Path = p:\usr\sap\piu\scs02\exe, Filespec = sapstartsrv.exe
To resolve this error you need to create a registry entry to exclude this file from this node’s backup.
- 1. Click Start, type regedit in the Search programs and files box, and then press ENTER. If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
- 2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SystemWriter
Note If this registry subkey does not exist, please create it manually.
- 3. on the Edit menu, point to New, and then click Multi-String Value.
- 4. Type ExcludedBinaryPaths, and then press ENTER. Note
- 5. Right-click ExcludedBinaryPaths, and then click Modify.
- 6. In the Value data box, type all binary paths that should be excluded from the system state backup operation, and then click OK.
Note The binary paths should be absolute paths. They should not include environment variables (such as %windir%) and should not be enclosed in double or single quotation marks.
- 7. Exit Registry Editor.
You must provide all system state binaries that are on the unavailable drive. You must provide the full path to the binary,
such as, p:\usr\sap\piu\scs02\exe\sapstartsrv.exe
NB: Please note the drives are case sensitive and no spaces anywhere. The client will need a reboot to kick in the registry entries.
-
1.Re: More VSS Writer Errors:
Hi Jim,
I appreciate your frustration, but I think we would need some more information/logs to get to know the root cause of the issue.
Do you have the output of the /nsr/tmp/sg/group_name_folder/
Have you seen any error in Application and/or System event logs If so which ones?
What is the output of running the backup from the client?
Have you run the backup with any debug options?
Have you enabled VSS Traces to find out what is going on with VSS?
This VSS traces can be really big (even 2-3GB), but with good text processor you can easily find out the error messages.
Thank you.
Carlos.
-
2.Re: More VSS Writer Errors:
If you just backup certain data from that machine, then you do not need DISASTER RECOVERY save set at all and you can disable it. Usually, that code is associated with something missing or failing to be found. Right now it is just a pure guess what it could be and it could be loads of things. Last time I saw it I had it on bizztalk server and Winblows guys found some patch for it (which by title had nothing to do with it, but either that or reboot after did a trick). If using MS VSS provider, your best bet is debug output of VSS itself to see where it really fails.
-
3.Re: More VSS Writer Errors:
Can somebpody temm me how to enabled VSS Traces to find out what is going on with VSS, as even in our environment there are many Backups that fail for VSS Filesets or any other VSS related save set, with writers being in stable state.
-
5.Re: More VSS Writer Errors:
Hello,
I have not seen this on the Disaster Recovery save sets, but we have had problems with backing up the passive cluster nodes several times due to services are being installed on shared cluster disks. There is an article at MS that we have used to solve the ERROR=0x80070002 several times. Take a look at it and see if it applies to your environment:
http://support.microsoft.com/kb/980794
/Rickard
-
6.Re: More VSS Writer Errors:
Hi all,
The "workaround" from Microsoft is a well known one, and once again this is a VSS limitation.
NetWorker introduces time ago a save command to skip those "missing system files", however I didn't want to mention it here as we are talking about DISASTER_RECOVERY:\ saveset.
That workaround is only for clusters when, for instance, you try to backup a file system of a SQL cluster passive node, and VSS when tryi9ng to backup the registry (System Writer) finds out that the pointer to the file xxx is in fact residing on a shared disk.
As this is the passive node, it doesn't have access to the shared disk, so doesn't have access to that file.
In this particular case I would suggest to run a save -D3 to find out what is the "missing file" or what is the problem with ASR.
Anyway the save command to be set on the client configuration is as follows (note the single quote, double quote):
save -a '"ignore-all-missing-system-files=yes"'
Thank you.
Carlos.
-
7.Re: More VSS Writer Errors:
Hey Carlos,
I am assuming you put this into the "Backup command:" field on the Apps & Modules? I tried that and still am getting:
savegrp: suppressed 3 lines of output.
77777:save: Added writer Registry Writer to disaster recover backup.
77777:save: Added writer Task Scheduler Writer to disaster recover backup.
77777:save: Added writer VSS Metadata Store Writer to disaster recover backup.
77777:save: Added writer Performance Counters Writer to disaster recover backup.
77776:save: ERROR: Failed to add writer System Writer to disaster recover backup, error=0x80070002.
77774:save: ERROR: Error adding writer to the snapshot set. ERROR=0x80070002.
77775:save: Processing completed for disaster recover backup.
80520:save: ASR Backup..Critical error creating snapshot of ASR critical volumes and cannot continue.
83449:save: Error occured while saving critical volumes.
-
8.Re: More VSS Writer Errors:
Hi Jim,
We would need more information about the error, found in the tmp files /nsr/tmp/sg/group_name, also found in Application and/or system event logs and also running debug mode manual save from client.
Also, did you enable VSS traces?
Some times the reboot fixes these kind of errors where some files/folder required for ASR are not created, or it could be for some other reasons but again, to know it we need more information.
Thank you.
Carlos.
-
9.Re: More VSS Writer Errors:
Hi,
From the client machine, run the following command :
save -D9 -vvv -s nw_server -b Poolname DISASTER_RECOVERY:\ > drsave.log 2>&1
Where:
nw_server = hostname of your NetWorker server
Pool = Pool you want to send the data. It is case sensitive and must be enclosed between "quotes" if it contain any spaces.
- Open the drsave.log and go to the last 10 to 15 lines
- You will see a similar error as GetVolumeMountPoint failed for some directorypath – 2
- Now get the diskshadow output for that client
- Search for the directory path in that output
You will get something like this : File List: Path = p:\usr\sap\piu\scs02\exe, Filespec = sapstartsrv.exe
- Now in the registry entry add the entry directorypath\filename
- Restart the client machine
Thanks
-
10.Re: More VSS Writer Errors:
This is the error from the drsave.log
VSS .. GetVolumeMountPoint failed for p:\usr\sap\piu\scs02\exe – 2
And the only file that is failing from disk shadow output
File List: Path = p:\usr\sap\piu\scs02\exe, Filespec = sapstartsrv.exe
To resolve this error you need to create a registry entry to exclude this file from this node’s backup.
- 1. Click Start, type regedit in the Search programs and files box, and then press ENTER. If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
- 2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SystemWriter
Note If this registry subkey does not exist, please create it manually.
- 3. on the Edit menu, point to New, and then click Multi-String Value.
- 4. Type ExcludedBinaryPaths, and then press ENTER. Note
- 5. Right-click ExcludedBinaryPaths, and then click Modify.
- 6. In the Value data box, type all binary paths that should be excluded from the system state backup operation, and then click OK.
Note The binary paths should be absolute paths. They should not include environment variables (such as %windir%) and should not be enclosed in double or single quotation marks.
- 7. Exit Registry Editor.
You must provide all system state binaries that are on the unavailable drive. You must provide the full path to the binary,
such as, p:\usr\sap\piu\scs02\exe\sapstartsrv.exe
NB: Please note the drives are case sensitive and no spaces anywhere. The client will need a reboot to kick in the registry entries.
'Windows > 2003' 카테고리의 다른 글
| [스크랩] 윈도우2003 heap memory 설정 (COM+ 컴포넌트 에러) (0) | 2014.08.27 |
|---|---|
| [스크랩] 로그온 화면 검정색 (0) | 2014.08.27 |
| [스크랩] 볼륨 섀도우 카피 (VSS) (0) | 2014.06.18 |
| [스크랩] Paged, NonPaged 커널 메모리의 최대 크기 확인 (0) | 2014.04.03 |
| 2003 에서 FTP 설치 (0) | 2014.02.18 |