10-23-2008 12:41 AM
Hi,
We currently use Backup Exec 12.5 and Exchange 2007. We did not do an upgrade from 11D but a fresh install and brand new config.
During week days de backup job ends every with this error:
V-79-57344-759 - Unable to complete the operation for the selected resource using the specified opti...
The strange thing is that during backup jobs in the weekend the job ends with: Completed succesfully.
It looks like the error during week days is caused by heavy usage of the Exchange server. We have about 500 users and mailboxes.
Can anyone help me resolve this issue?
10-23-2008 05:38 AM
11-24-2008 10:06 PM
Hi Anup,
We only take full backup's every day? Why should we use incremental?
The problem is still bugging us.
12-01-2008 12:22 PM
Hi,
It is essential to install MAPI CDO 1.2.1 on Exchange Server
Best Regards
12-01-2008 10:02 PM
HI,
MAPI CDO 1.2.1 was already installed on exchange server but nog yet on backup server .
So, i installed it on Backup server.
12-02-2008 01:31 AM
Hi,
Yes on my backup Server, Exchnage Tools and MAPI CDO are installed
12-02-2008 10:27 PM
Hi,
Yesterday we installed MAPI CDO. On the Backup server.
Still the Job fails.
We are getting frustrated.
12-06-2008 04:14 PM
Tough one to troubleshoot as there could be a number of causes.
First of all make sure that your Exchange maint window is long enough that the offline defrags (one per database) actually complete. You should see event log entries when the offline defrags start and stop. The text of the entries varies depending on what version of Exchange you are running but once you learn to spot them it is simple (look for "ese" as the message source).
Most important: Make sure that your backup job never conflicts with your Exchange maint windows OR that the maint windows conflict with one another.
If you learn that your backup job has been overlapping with your maint window change it asap and (if possible) run an offline defrag and isinteg (after a backup of course).
Also, there is an update rollup for VSS that is not available via Windows update: http://support.microsoft.com/kb/940349
There is more stuff that can be done but these seem to be key based on the troubleshooting I have been doing over the last few months.
Jason