This post is more than 5 years old
4 Posts
0
32924
VSS Issues
Hi everybody,
I am facing an issue with VSS during the backup; I have a win 2008 entreprise x64 running NetWorker 7.5.1. Here's the error :
ERROR: Failed to initialize backup, error=0x80042301: VSS Backup or Restore is not in the correct state for the operation, or the writer is not in the correct state. 7154:save: Unable to set up VSS filesystem directives. Failed to back up G:\. : Failed with error(s)
savegrp: suppressed 22 lines of output. 53085 1340784234 1 0 0 2472 1964 0 sfatsbkp nsrsqlsv 27 Backing up of %s succeeded. 1 0 5 model 53085 1340784251 1 0 0 2472 1964 0 sfatsbkp nsrsqlsv 27 Backing up of %s succeeded. 1 0 4 msdb 29067 1340784252 1 0 0 2472 1964 0 sfatsbkp nsrsqlsv 113 Skip building named instance directory because there are no named instances installed or running on this machine. 0 43709 1340784252 1 0 0 2472 1964 0 sfatsbkp nsrsqlsv 13 Stop time: %s 1 35 25 Wed Jun 27 04:04:12 2012
After a couple of look ups I've found this hotfix from microsoft; however, it's for Win 2003..
Could you anyone please help me out?
Thank you,
Rajesh Sekar
26 Posts
0
June 27th, 2012 20:00
Please try the below methods:
Method 1:
Restart the follwoing windows services with out a reboot of the server.
COM+Event system
Microsoft software shadow copy provider
volume shadow copy
Note restarting "COM+Event system " service will restart System Event notification service and Background intelligent Transfer service due to the dependencies.
After restarting these services VSS will return to stable state.
Method 2:
faster but more disruptive in production enviornment.
Reboot the server.This will clean the incorrect status of the VSS writers and backup will now succeed.
Panwar
79 Posts
0
June 27th, 2012 08:00
Hi
Please run vssadmin list writers and check Writers status on the client machine. Make sure that all the writers should be in stable state and no errors.
Thanks
Panwar
zridet
4 Posts
0
June 27th, 2012 09:00
I did, and all the writers are in stable state with no errors.
CarlosRojas
1.7K Posts
0
June 27th, 2012 22:00
Hi Zridet,
I see 2 different backups running at the same time:
File System and also SQL:
Failed to back up G:\
sfatsbkp nsrsqlsv 113 Skip building named instance directory because there are no named instances installed or running on this machine
Can you please tell us what are you backing up?
Are you mixing File system and SQL backups for the same client in the same group?
Have you checked that all writers are present by running vssadmin list writers? Specially ensure that System Writer is in place.
What is the configuration of the client and what is the saveset you have configured?
Have you checked Application and System event logs on the client to see if there is any event ID 25 volsnap? If so then google it, as there are Microsoft fixes for that (you forgot to attach the fix you found, by the way)
Thank you.
Carlos.
zridet
4 Posts
0
June 28th, 2012 06:00
Thank you for your answers,
Unfortunately, I cannot reboot the server because it might affect the business since it's a physical server I would need an approval from the other teams and that could take a little while..
Actually I am backing up both file system as well as SQL, yes I have checked all the writers and they are all running with no errors; however, this is what I've found on the System event log as a warning ( the recent one):
The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer received an abort request.
Sorry for the Microsoft fixe here's the link: http://support.microsoft.com/kb/976461
Thank you,
zridet
4 Posts
0
June 28th, 2012 10:00
Hi sekaraj,
Your first method worked out, it was easy and fast the backup was completed successfully.
Thank you,
Aegh
1 Rookie
1 Rookie
•
82 Posts
0
October 4th, 2012 03:00
Guys,
I have the same problem as well. I've done the step provided by sekaraj and even rebooted the server but i'm still getting below error.
1 retry attempted
ERROR: Failed to initialize backup, error=0x80042301: VSS Backup or Restore is not in the correct state for the operation, or the writer is not in the correct state.
89668:save: Unable to set up VSS file system directives. Failed to back up G:\.
: Failed with error(s)
I used the hardcoded saveset which C and E drive completed succesfully but failed on F,G and H.
This is what I get from vssadmin list writers
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Waiting for responses.
These may be delayed if a shadow copy is being prepared.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {14642c79-7559-49f9-b0a2-bd2596ff8422}
State: [1] Stable
Last error: Non-retryable error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {8c2e150e-0fab-4091-bcc8-6ade0e39555a}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {89b2b0bb-8d0b-48ff-ad27-fcde7361c8b3}
State: [1] Stable
Last error: Non-retryable error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {f17606eb-2d62-4cb8-b90b-c0ef9d851fce}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {8bae8e6b-a0a6-4e91-bb2d-032651bc15cf}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {01fbc96f-cc3b-4444-90b4-eb9f79dc1772}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {a5533ff6-09ae-4f05-8b9a-718d94df1b6e}
State: [5] Waiting for completion
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {10ab8211-c917-4ff7-91bb-ab27b7e73379}
State: [1] Stable
Last error: No error
Any idea?
iimnordic
19 Posts
2
October 4th, 2012 04:00
I made a troubleshooting document for myself some time ago , I paste it here since it resolves and gives info regarding all strange VSS Errors you can encounter. (Try re-register writers in the section a bit down)
Check to see if there are any non-standard providers that are causing the problem when performing the VSS snapshot. To do this, go to the command-line and execute the following command "vssadmin list providers".
If there are any non-standard providers listed, consider uninstalling them. Note that the Microsoft default providers are generally very reliable, so uninstalling 3rd party providers may solve the problem.
If the "vssadmin list providers" command hangs, it is likely that a newly installed VSS provider is malfunctioning. We have seen this with certain imaging products. In this case, uninstall these products to resolve the issue.
Ensure that the backup is not running at the same time as another backup as the custom provider may only allow one snap-shot at a time.
Run CHKDSK on each drive with the /f switch to fix any errors on the disk.
*PLEASE NOTE THIS CAN CAUSE DATALOSS*
Check the status of the system by following these steps:
=======================
WINDOWS 2003 SERVER x86
Following are the suggested updates for vss and some basic troubleshooting for it:
http://support.microsoft.com/kb/940349
http://support.microsoft.com/kb/934016
http://support.microsoft.com/kb/951568
1 ) Re-register VSS writers if missing. From cmd promt:
2 ) Stop the Following services:
3 ) Take the backup of the "Subscriptions" key
4 ) Delete the "Subscriptions" key
5 ) Restart/Start the following services
6 ) Reboot the machine.
This will “re-build” the VSS Writers , Will fix most writers except “System Writer”
WINDOWS 2003 SERVER x64
1 ) Re-register VSS writers if missing. From admin-cmd promt:
2 ) Check and Stop the Following services:
3 ) Take the backup of the "Subscriptions" key
4 ) Delete the "Subscriptions" key. Delete just the Subscriptions subkey; leave the EventClasses key.
5 ) Restart/Start the following services:
WINDOWS 2008 SERVER
More VSS KB’s and troubleshooting for Win2008 can be found here:
http://support.microsoft.com/kb/940349Http://support.microsoft.com/kb/975928
6 ) COM+ needs to be re-installed. Re-install COM+ by following these steps:
Steps 3,4,5 and 6 have been obtained from http://forums.msrportal.com/showthread.php?t=5559
7 ) Destination drive is not formatted for NTFS. Check to make sure the backup destination is compatible with the NTFS format. Please view the following article on how to convert a drive to NTFS format: http://support.microsoft.com/kb/307881
Check for disk activity during the time of backup. High disk activity at the time of the snapshot can cause the snapshot manager to determine a cutoff point easily.
Make sure that you have at least 100MB (however the more the better) free space on all drives involved within your backup.
OTHER REFERENCES
• http://support.microsoft.com/kb/307881
• http://forums.msrportal.com/showthread.php?t=5559
Knowledge base articles - known Windows 2003 VSS issues:
A Volume Shadow Copy Service (VSS) update package is available for Windows Server 2003 - Last Review: July 2, 2010
http://support.microsoft.com/kb/833167
Exchange VSS backup fails on an Exchange Server 2003 server - February 20, 2010
http://support.microsoft.com/kb/924262
Various issues may occur on a Windows Server 2003-based computer that is running the Volume Shadow Copy Service - April 27, 2010 - April 27, 2010
http://support.microsoft.com/kb/940032
Exchange Server 2003 data backup and Volume Shadow Copy services
http://support.microsoft.com/kb/822896
Knowledge base articles - known Windows 2008 VSS issues:
VSS snapshot creation may fail after a LUN resynchronization on a computer that is running Windows 7 or Windows Server 2008 R2 - November 25, 2009
http://support.microsoft.com/kb/976099
Backup fails with VSS Event ID 12292 and 11 on Windows Server 2008 and Windows Server 2008 R2 - January 20, 2010
http://support.microsoft.com/kb/2009513
No VSS writers are listed when you run the “vssadmin list writers” command in Windows Server 2008 R2
http://support.microsoft.com/kb/2009550
http://support.microsoft.com/kb/2009533
Windows 2008 R2 64-bit backup failed
General VSS articles to review:
http://solutions.emc.com/emcsolutionview.asp?id=esg108377
http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/77862/VSS-Writer-errors-during-backup
http://support.microsoft.com/kb/930800
http://technet.microsoft.com/en-us/library/aa996004(EXCHG.65).aspx
http://support.microsoft.com/kb/106167
Windows 2008 R2 Action plan for VSS Trouble shooting (General)
Please apply the following resolution plan
Check first this solution to verify your NIC cards configurations :
http://solutions.emc.com/EMCSolutionView.asp?id=esg70774&usertype=C
Check the following solution
http://solutions.emc.com/EMCSolutionView.asp?id=esg50325&usertype=C
Try if you have firewall to configure TCP/IP address and name of the firewall to the client hosts file
JanEgil1
1 Message
0
March 24th, 2014 04:00
My experience on Windows Server 2012, is that
vssadmin list writers
).(I still need to figure out my real problem - why 'OSearch15 VSS Writer' is waiting for completion forever.)
Showkat Bhat
1 Message
0
October 20th, 2019 00:00
Do we need to restart the services on client-server from where we are taking the backup or the networker server.
bingo.1
2.4K Posts
0
October 20th, 2019 01:00
VSS is a Windows specific method which runs locally. Consequently you must 'repair' the system wherever you have the trouble - the NW client.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
October 20th, 2019 23:00
@Showkat Bhat
All the steps related to VSS are to be run on the problematic client machine. Also, no 2 issues might be the same even though the error on the backups are the same. Make sure you look at the event viewer and consult with your windows administrator before taking any steps.