Local media server backup issues - Backup Exec 11d

[Burton]

 All,

I'm getting the following errors everytime I attempt to perform a backup of files on my media server. The media server can successfully backup any other system that I target, just not files local to the system. I have been able to successfully perform a local backup & system state backup with NTBackup. I can also open any file the backup log notes is corrupt & it isn't always the same files that it claims are corrupt each time. Is this an issue with the Backup Exec remote agent that is installed on the media server? My antivirus software is Forefront 1.5.1996.0. The media server is Windows Server 2003 R2 SP2 (build 3790) and I'm currently using Backup Exec 11d. What's the best way to resolve this issue?

Thanks in advance for any suggestions!

-Greg

First example:

For additional information regarding this error refer to link V-79-57344-65247

Errors
Click an error below to locate it in the job log
Backup- System?State System?StateV-79-57344-65247 - A failure occurred reading an object.

Exceptions
Click an exception below to locate it in the job log
Backup- System?State System?StateWARNING: "System?State\System Files\System Files" is a corrupt file.
This file cannot verify.
Verify- System?State System?StateWARNING: "System Files" is a corrupt file.
This file cannot verify.

Another example:

Job Completion Status
Job ended: Sunday, July 10, 2011 at 7:43:14 PM
Completed status: Failed
Final error: 0xe000fe36 - Corrupt data encountered. See the job log for details.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-65078

Exceptions
Click an exception below to locate it in the job log
Backup- C: WARNING: "C:\filename.doc" is a corrupt file.
This file cannot verify.
WARNING: "C:\filename.doc" is a corrupt file.

[CraigV]

Hi,

Turn on AOFO and see if this helps you...

Thanks!

[Burton]

Turning off AOFO in the Tools menu results in Backup Exec still attempting to to use AOFO. Even with it deselected in the job as well! Is AOFO really my problem or something else? I was wondering if the Remote Agent wasn't corrupt in some way since this is only happening on the backup server itself & not any of the other servers I backup???

Running a Windows NT Backup of the server now, will report back with results of that job when it completes.

[pkh]

The other poster thought that you did not have AOFO ON and he asked you to turn it ON, not off.  In any case, you are using AOFO.

Try stopping your anti-virus during the backup run.  Sometimes, AV software can interfere with the backup.

[CraigV]

OK...does that filename.doc physically exist on the C:\ of the server? If not, it might be that the selection list is seeing a file that doesn't exist.

As for the System State, I have seen McAfee cause a similar sort of thing on a couple of my backup servers...just out of the blue!

[Burton]

Yes the files do exist. I actually went and opened several from my workstation w/o error, closed them and even saved some before existing. The files on the system are fine it's just Backup Exec & NTBackup that think the files have an issue. I guess I'll try uninstalling Forefront AV, reboot and try another backup with each of them. The only other thing I can image that is messing this up would be VSS?

[CraigV]

...easiest way to check that would be to open up a command prompt and type:

vssadmin list writers --> they should all be stable and running. If not, reboot the server and rerun the command. If they're still not stable, do a reregister of the VSS *.dlls using the Symantec TN below:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

You can also run: vssadmin list providers --> once you see the output here, make a note of which provider is being used and then change to that in your AOFO properties and see if it makes a difference.

Alternatively simply exclude that file...

[Burton]

While looking at this some more I rebooted the Backup Exec server, checked the status of the VSSWriters before and then again after a backup attempt with NTBackup. Here is the output of each. How do I fix this?

BEFORE:

C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {833dba1d-c192-47d1-9138-2f58f57b70e6}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3af73f15-f9c4-4db8-ab50-7d948594cb3f}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {14941038-9006-4f06-a1cf-324d6eae62fd}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {2a375737-4022-4bde-9892-88e03f5ff149}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {af7a4455-af73-453a-9ac6-699716fefc3e}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {9857f784-1ef2-462b-9b4f-961c8d83a177}
   State: [1] Stable
   Last error: No error

Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {a3f6ccc3-1a1c-42b5-a8ba-31550b379dc3}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {e7eb32bf-4289-4cc9-b872-df283988401a}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {d71cc8c3-e49b-4f62-bde5-9488531501b9}
   State: [1] Stable
   Last error: No error

C:\>

AFTER:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {833dba1d-c192-47d1-9138-2f58f57b70e6}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3af73f15-f9c4-4db8-ab50-7d948594cb3f}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {11b0318f-473f-41d5-b8e5-c2ce06645b89}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {f93bec76-6a8f-467b-8ba3-be9c05c8badd}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {4a606a55-2364-49fb-9f95-5b4af4c597ae}
   State: [1] Stable
   Last error: No error

Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {a3f6ccc3-1a1c-42b5-a8ba-31550b379dc3}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {245ba80a-5537-4161-89df-09258d34b23c}
   State: [1] Stable
   Last error: No error

Writer name: 'Removable Storage Manager'
   Writer Id: {5d3c3e01-0297-445b-aa81-a48d7151e235}
   Writer Instance Id: {ad91eded-4fc8-48c6-b788-f52ed20a2d5f}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {d71cc8c3-e49b-4f62-bde5-9488531501b9}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {948f23ff-8b5d-48db-a847-1e10182b2dff}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {e7eb32bf-4289-4cc9-b872-df283988401a}
   State: [5] Waiting for completion
   Last error: No error

[CraigV · Accepted solution]

Hi,

1 of 3 ways to do this:

1. Reboot your server if you are able too. Run the vssadmin list writers command again and check to see if the VSS writers are stable and running. If not...

2. Download and install the latest VSS ROllup Patch for Windows Server 2003. INstall and run the command again.

3. If this doesn't work, it migjt be worth your while to reregister the VSS *.dlls. Read the Symantec TN below on how to do this:

http://www.symantec.com/business/support/index?page=content&id=TECH70486

Thanks!

[Burton]

This looks like it *might* have solved my issue. I was able to get a successful System State backup just now. Scheduling a full system backup tonight to see how it goes. (Fingers crossed).

Thank you for the help!