Upgrade 11d - 12.5 now Exchange 2007sp1 backup fails
I have upgraded our BE from 11d to 12.5 this weekend.
After upgrading the media server and input all of the 12.5 licences (including Exchange agent, Enterprise Vault agent, SQL agent and remote windows licences).
I have then upgraded the remote agents on all of the servers, all of these servers have then successfully backed up (Enterprise Vault is still backing up as it takes 14 hours but has done 150gb so far).
However I am unable to get two Mailbox servers (running Exchange 2007 SP1, rollup 2) to work properly.
We are using Microsoft Clustering and both servers are active with a passive node available for them both.
The original jobs that were setup never let me see the selection list as the INFORMATION STORE opened up and listed the cluster node again and none of the databases. I created a new job and could see all databases and selected one of them and ran a backup which was successful.
I have then created a two new jobs (one to backup the 4 Exchange databases on server1 and one to backup the 3 EXchange databases on server2).
No matter which of the two jobs I run they start and begin to backup a database even to the point of verifying and moving on to snap shot processing the next one before they fail with this error (this appears for each database):
V-79-57344-65055 - AOFO: Initialization failure on: "\\RESEXEVS2\Microsoft Information Store\Performance and Strategy Storage Group". Advanced Open File Option used: No.
Snapshot provider error (0xE000FE1F): The device cannot be found.
I've checked all of the documents on Symantec and even tried adding the cluster registry (even though we are using full clustering and not the LCR or CCR.
Both Exchange servers are experiencing errors on the console and in the log file which are:
The console states their was an error with the "Backup Exec Powershell execution engine"
The System log file states:
Faulting application monad.exe, version 12.5.2213.0, faulting module user32.dll, version 5.2.3790.4033, fault address 0x0000000000021854.
I've checked and the Exchange server has the CDO 1.2 and the latest RAWS client. I've tried removing, rebooting and re-install the client via browsing to the server AND then doing the same put pushing the client out from the media server. Also rebooted after the install.
I've tried running the backup with the GRT turned off and on.
Any help or ideas would be greatly appreciated.
Mark
Comments
Forgot to mention our servers are running Windows 2003 R2 SP2 - the media server is a 32bit box but the Mailbox servers are AMD x64 boxes.
These have been in place for over 12 months and backing up (most of the time) using BE 11d.
Hi, I have the same issue with backing up Exchange 2007 SP1 in a SCC since upgrading from 12 to 12.5. The backups function correctly 90% of the time but usually about once a week we get exactly the same error regarding monad.exe.
I'm glad to hear that someone else running basically the same enviroment is also experiencing this problem as I haven't been able to find any info about it on the web.
If you get a solution please let me know...I'll also keep looking into it.
I've run out of ideas and have emailed our support company (who have a contract in place with Symantec) so if I get a fix I'll post it up.
I've now noticed that my new selection list doesn't display the information stores at all now either and is why my backup fails. Any time I try to create a new one or view the existing one my Exchange MB server displays the Backup Exec Powershell execution engine error and the monad error.
Mark
Why only rollup 2 on Exchange 2007 sp1? I only ask because a couple of the BE hotfixes over the last few months included fixes for Exchange issues and it gets harder to troubleshoot when the Exchange server isn't fully patched.
I was seeing the Monad errors/BE agent crashes this weekend after my rollup 5 update this weekend; reboots seemed to fix them.
Did you remove the old backup agents before installing the 12.5 agents? This is something that Symantec support will typically ask.
I'd restart all your BE services with the "-debug" switch and run the debug monitor and see if you can spot what happens: http://seer.entsupport.symantec.com/docs/309683.htm
Remote agents will dump their debug logs in the logs folder within the agent folder; for BE it puts them in the logs folder of the program itself (assuming you have the debug monitor save them).
The debug logs can be helpful even if you aren't a Symantec engineer; I've found some things in them in the past that pointed me in the right direction when troubleshooting.
Jason
One of the Mailbox server backups started working but the other continually failed. The backup exec powershell execution error is still displayed (referring to MONAD.EXE).
We have now upgraded to Ex 2007 SP1 ROLLUP 5.
We have also upgraded Backup Exec to 12.5 SP1 and replaced the agent againithe the latest version.
I have also now failed my cluster server to the passive node and it appears to be working fine.
I have also tried to set up my Server 1 backup to use GRT again and this now displays the powershell engine error but the job continues to work albeit a lot slower than usual (we have seen speeds in excess of 1,000GB a minute but its now running at 250mb/min)
I am experiencing exactly the
I am experiencing exactly the same issues.
Were you ever able to get a solution?
Thanks
Would you like to reply?
Login or Register to post your comment.