System State Fails to Backup

[galienpl]

I have Windows Server 2008 R2 with all current updates

I have Backup Exec 2010 R2  Version 13.0 Rev. 4164 (x64) with all current updates per liveupdate.

I started getting System State backup failures after we had a power outage.  The server was shutdown "nicely" with the power backup software.  I uninstalled the backup software and reinstalled it applying all updates. I then created a new job exactly as I had before.  The backup job failed to complete again. I modified my backup job to exclude the System State and the backup job completed successfully.  I believe it is failing when trying to back up system files portion of the System State since when I view the properteis of the job when it is running it seems to halt at that stage.  I do not receive any error messages.  I am getting Information VSS messages in my event log. 

VSS, ID 8219, Ran out of time while expanding file specification \\?\GLOBALROOT\Device

\HarddiskVolumeShadowCopy5\Windows\softwaredistribution\Download

\c23c8d8487ee93fe08da78354d82ef2e\*.*. This was being done for the WUA subscriber.

VSS, ID 8219, Ran out of time while expanding file specification \\?\GLOBALROOT\Device

\HarddiskVolumeShadowCopy5\Windows\softwaredistribution\Download\*.*. This was being done for

the WUA subscriber.

VSS, ID 8219, Ran out of time while expanding file specification \\?\GLOBALROOT\Device

\HarddiskVolumeShadowCopy5\Windows\softwaredistribution\*.*. This was being done for the WUA

subscriber.

VSS, ID 8220, Ran out of time while deleting files.

If you have any suggestions it would be greatly appreciated.

Sincerely,

Michael

[galienpl]

I forgot to mention that I also tried to backup to disk and I received the same result.  I used Windows Sever Backup and I backuped only the System State and it completed fully at 10.24 GB to disk.

[sksujeet]

On the server for which system state if failing try below steps:

1> go to cmd promtp and type vssadmin list writers and check the output. If all are in stable state then go to step 2. If it doesn't display the vssadmin list writers then we have some issues with VSS. If it shows some of the writers as unstable then please try to restart the system and see if all of them are in stable state. If still some issues its MS issue.

2> If the vss writers are all showing fine then please try the system state backup of your machine.

In ws 2008 make sure you have the backup role installed on the server and then type this command on the cmd prompt

C:\>WBADMIN START SYSTEMSTATEBACKUP -backuptarget:E:

It will put the backup on E drive you can change the drive letter as per your system.

[galienpl]

All VSS was in stable state.  I ran the backup command you suggested and it completed sucessfully.  I then ran the vssadmin list writers again after it was finished and they were in stable state.  I opened Backup Exec and attempted to run just a System State backup to disk drive but it has stalled again on the System Files from what I can determine.  I ran the vssadmin list writers command at this point these are the results:

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {55b0cf82-675a-4714-8869-2fb112bd1463}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {9605effa-0049-4fa1-b606-d67e006a3d5d}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {20a880f6-a2f0-438a-9de9-0dcd754dcf84}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {88f3bb57-7f28-4ec7-b279-c832f993c6d6}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {dd3069a3-f242-4996-ae00-3a952f2b6552}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {d26a24b4-2c4e-48b1-8107-d2b33edce790}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {39acdc58-eb1b-4a20-a9c0-ae562fa31d64}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {1f8786fb-c238-4eb9-bda1-fb3817bb7ac1}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e0bf6ef9-7c52-47ce-bff5-d842592f9a3c}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {2bcfb82e-fb87-40f3-978c-aa4b87c45136}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {d491900c-77f7-47b8-aeee-6fc646643d77}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {280df45f-1b45-4849-85d7-936db427cdff}
   State: [5] Waiting for completion
   Last error: No error

I do not understand why if the System State completed with the windows backup that is it not working correctly in Backup Exec.  The job at this point won't cancel properly so I have to stop the services to make it fail.

Any other suggestions would be much appreciated.

[sksujeet]

Please update the 2010 R3, Symantec fixed couple of system state issues that we had on ws 2008 on this and hopefully it will help.