Riddle Me This: Final error: 0xfffffea9 - 0xa000fea9 (2684419753)

[sujump]

Hello,
An ex-employee was taking care of these backup jobs and never really shared the info on this backup process. Basiclly he dropped it in my lap & left. And, unfortunaly I am not very experianced on this software or on what he was doing. I needed help with this issue and looked everywhere for a solution with no luck. Basiclly I've been getting this error (below) every time the back job runs. I think I pretty much tried every solution that I can think of but have not had very much luck in trying to resolve it. Please help.

Using:
Microsoft Windows Server 2003 R2
Enterprise Edition
Service Pack 2

Exchange 2003

Backup Exec. 10d
Media Server: Version 10.1 Rev. 5629
Administrattion Counsole: Version 10.1 Rev. 5629

Not using AOFO for the backup job.

--------------------------------------------------------
Job Completion Status
Job ended: Wednesday, May 09, 2007 at 9:07:17 PM
Completed status: Failed
Final error: 0xfffffea9 - 0xa000fea9 (2684419753)
Final error category: Other Errors

For additional information regarding this error refer to link V-79-65535-65193

Exceptions
Click an exception below to locate it in the job log
Backup- \\MEXCHANGE\Microsoft Information Store\First Storage Group WARNING: "\\MEXCHANGE\Microsoft Information Store\First Storage Group\CS" is a corrupt file.
This file cannot verify.
WARNING: "\\MEXCHANGE\Microsoft Information Store\First Storage Group\Ipt" is a corrupt file.
This file cannot verify.
WARNING: "\\MEXCHANGE\Microsoft Information Store\First Storage Group\Mailbox Store (MEXCHANGE)" is a corrupt file.
This file cannot verify.
WARNING: "\\MEXCHANGE\Microsoft Information Store\First Storage Group\Pn" is a corrupt file.
This file cannot verify.
WARNING: "\\MEXCHANGE\Microsoft Information Store\First Storage Group\Pc Folder Store (MEXCHANGE)" is a corrupt file.
This file cannot verify.
WARNING: "\\MEXCHANGE\Microsoft Information Store\First Storage Group\Log files" is a corrupt file.
This file cannot verify.Verify- \\MEXCHANGE\Microsoft Information Store\First Storage Group WARNING: "CS" is a corrupt file.
This file cannot verify.
WARNING: "Ipt" is a corrupt file.
This file cannot verify.
WARNING: "Mailbox Store (MEXCHANGE)" is a corrupt file.
This file cannot verify.
WARNING: "Pn" is a corrupt file.
This file cannot verify.
WARNING: "Pc Folder Store (MEXCHANGE)" is a corrupt file.
This file cannot verify.
WARNING: "Log files" is a corrupt file.
This file cannot verify.

 

[steveot]

Check the selection list and expand MEXCHANGE\shadow copy components. If you see a User Data folder under shadow copy components uncheck it.

Otherwise there are some serious problem with exchange. A quick check of the application log on MEXCHANGE would report that when the backup is taking place.

 

[sujump]

steveot,
Thanks for the reply,I've checked the selection list like you seggested and none of the shadow copy components or anything under that is checked. I've also checked the application logs and their are no errors going on....now you see why I'm confused. Still scratching my head over this one. Any more ideas?

Thanks again

 

[steveot]

Hmm I still think its exchange. On the exchange server in application log do you see "ESE" or "ESEbackup" events when Backup Exec is calling on the server?

First think I would do it run NTBACKUP on the exchange server and backup the information store to disk or a remote disk/share. Then review the events in the application log. My gut feeling is you will see exchange reporting some problems with the logs or database. I could be wrong but if you just create a job from scratch and just selection the information store for backup does it work?

 

[MacGyverNeedsHelp]

I understand from veritas that this is not a real error, and a registry entry can be made to where it is not recognized as an error.

 

[sujump]

Guys,
Thank you very much for the time and effort that you put into these replies. I think I figured out (99% sure) why this was happening. We have two Exchange servers which are supposed to be replicated for backup incase we have a data disaster. On those two servers we are running software called Neverfail. This software is suppose to keep the other server looking exactly the same incase of a primary server failure, if that primary server goes down Neverfail “fails over” to the replicated (cloned) server. Neverfail has what’s called a heartbeat which pings the cloned server constantly replicating data 24/7 and uses Volume Shadow Copy Service (VSS). Well, as it turns out every time Backup Exec would run a backup job the Neverfail processes would trip Backup Exec all up. There is a work around to integrate Backup Exec with Neverfail and I think that is going to resolve the very elusive problem that I've had.

Again, Thanks very much.

 

[chrislip]

Hi sujump. You mention a workaround to integrate neverfail with backup Exec. can you please let me know what this is or post a link to an info page

Thanks

 

[sujump]

Chrislip,
Neverfail is very touchy, as I've found out, what problem are you haveing and maybe I can help you work it out.

Thanks, sujump