phil435
asked on
Backup Exec 12.5 and Exchange 2007
I am receiving the following error when trying to backup my exchange 2007 store with backup exec 12.5:
Backup Exec Alert: Job Failed
(Server: "BACKUPSERVER") (Job: "Exchange0714") Exchange0714 -- The job failed with the following error: Using the job settings, Backup Exec attempted to back up the passive copy of the Exchange database. However, the passive copy was not available after the Microsoft Volume Shadow Copy Service (VSS) snapshot was performed. Try to run the job again.
This appears to be a common error but I havent tracked down the root cause of this yet. It will successfully truncate all of my log files and it appears that all the data is on the backup server. This error always occurs at the end of the process after the verify operation. I have looked at the following Symantec article and have trapped the error messages as stated in http://seer.entsupport.symantec.com/docs/305815.htm I have also patched backup exec with sp2 and all of the available hotfixes. Any suggestions?
Backup Exec Alert: Job Failed
(Server: "BACKUPSERVER") (Job: "Exchange0714") Exchange0714 -- The job failed with the following error: Using the job settings, Backup Exec attempted to back up the passive copy of the Exchange database. However, the passive copy was not available after the Microsoft Volume Shadow Copy Service (VSS) snapshot was performed. Try to run the job again.
This appears to be a common error but I havent tracked down the root cause of this yet. It will successfully truncate all of my log files and it appears that all the data is on the backup server. This error always occurs at the end of the process after the verify operation. I have looked at the following Symantec article and have trapped the error messages as stated in http://seer.entsupport.symantec.com/docs/305815.htm I have also patched backup exec with sp2 and all of the available hotfixes. Any suggestions?
Are you doing this to tape or to disk? Is there anything else included with this backup job?
ASKER
I am currently doing this to external disk. I have done a test by changing the backup type to active only and it immediately fails. On the Windows server 2008 box if I run the command vssadmin list writers I receive:
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8 e1acb462fb 7}
Writer Instance Id: {9a8b01ad-e2be-4ad4-a099-d af7474e024 6}
State: [1] Stable
Last error: Retryable error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8 e1acb462fb 7}
Writer Instance Id: {8f2b3976-b513-4506-a70a-8 361606f971 7}
State: [7] Failed
Last error: No error
BE media server is running Windows server 2003 sp2 and I have both the OS and BE patched with the latest updates. The exchange 07 x86 management tools on the media server has also been updated to rollup 8 which is what my exchange 07 server is running. On the exchange server the OS is Windows server 2008 and has been patched along with exchange itself.
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {9a8b01ad-e2be-4ad4-a099-d
State: [1] Stable
Last error: Retryable error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {8f2b3976-b513-4506-a70a-8
State: [7] Failed
Last error: No error
BE media server is running Windows server 2003 sp2 and I have both the OS and BE patched with the latest updates. The exchange 07 x86 management tools on the media server has also been updated to rollup 8 which is what my exchange 07 server is running. On the exchange server the OS is Windows server 2008 and has been patched along with exchange itself.
ASKER
Sorry meant to answer second question also. There is currently no other jobs defined besides the exchange backup on the media server. I am only running this one time only just to see if it works.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It's both sad and funny how many problems are fixed with a reboot... I should have asked if you had already done that..!