Error during backup of systemstate

Hi,

We encouter the following error at the end of the backup:

V-79-57344-850 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE0000352): The specified volume does not exist. Recreate the volume, and then try the job again.
Check the Windows Event Viewer for details.

The backup of other servers goes well, the software we use is Symantec Backup Exec 12.5 (fully updated) with a remote agent to a SQL server (MS 2008 R2 Standard) This SQL server (one of two) is the only one which fails.

The error just recently came up, before that no error was reported.

Anyone has tips or a solution to fix this issue?

When I use vssadmin list writers no errors are reported.

Greetings,

Joost

Diabolo-ICTAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

noxchoGlobal Support CoordinatorCommented:
The specified volume does not exist. Recreate the volume, and then try the job again. - can you take screen shot of Windows Disk Management and post it here?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mike ThomasConsultantCommented:
I would just restart the server or see if the next backup runs ok.

I deal with many many backups and these errors are not uncommon and  are often 1 off errors.
0
Mohammad Ishtyaq khatriSr. Systems EngineerCommented:
This was failed due to system state.
Firstly you have to check the vss writers, If they are not stable you need to reboot the server.
If the writers are stable, just run a test Ntbackup for only system state, then try the job on backup exec

Still the failure persist check for system32\vssadmin.exe, If you are having windows 2k3 with sp1 then the version should be 3959 if it is service pack 2 it should be 4143.

To update the vssadmin.exe refer the following artical.
http://support.microsoft.com/kb/940349

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

teichmeCommented:
Make sure the check box under advanced file options is checked sub menu microsoft vss
0
AxisFirstCommented:
Has anyone found a solution to this problem. I am experiencing the same issue on one of our DC's running Server 2008.

If I attempt to backup system state on it's own, it fails with the same error.
0
noxchoGlobal Support CoordinatorCommented:
The specified volume does not exist. Recreate the volume, and then try the job again. - can you take screen shot of Windows Disk Management and post it here?
0
AxisFirstCommented:
See attached. The unallocated disk won't have any bearing will it? I have only just become aware of this disk being installed (just trying to determine when) - this won't be causing the backup to fail like this will it?
computer-management.jpg
0
AxisFirstCommented:
The drive was an existing drive who's data was moved to another server. Drive was wiped on this server and awaiting a time to remove the physical disks.
0
AxisFirstCommented:
Huzzah! I just re-created a volume on that drive and I am now performing a test backup of system state which is as we speak going through!
0
noxchoGlobal Support CoordinatorCommented:
Yes, exactly. The drive order and number changed and thus your backup was pointing to wrong storage.
Let's see if it completes successfully.
0
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
This question has been classified as abandoned and is being closed as part of the Cleanup Program.  See my comment at the end of the question for more details.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.