We're running into a pretty major issue after an upgrade to BackupExec 2015 and we're pretty much at our wits end and hoping for a solution.
We were successfully using BackupExec 2010 to backup our Exchange 2010 configuration to tape. We were sold BackupExec 2015 and we've been attempting to implement it to simplify our backup configuration.
We built a new server and then started running our backups to BackupExec 2015. We have not been able to successfully backup our Exchange configuration since then and we're getting very frustrated.
We've had a ticket open with Symantec for weeks and the agents haven't been able to provide a resolution. They just had us run a debug and came back to us that our network drivers need to be updated. I checked the network drivers on both servers and they're both running the newest available driver. And again, we didn't have an issue with BackupExec 2010.
Here is what happens:
We have 3 datastores. One about 900GBs, one about 400GBs, and a new one that I created as part of this troubleshooting that's about 45GBs.
We've attempted to run a full backup against all three datastores and in every instance it fails at the "Consistency Check" phase for all three databases.
The error that we get is:
Job Completion Status
Job ended: Tuesday, June 30, 2015 at 7:05:23 AM
Completed status: Failed
Final error: 0xe000ff12 - A communications failure has occurred with an Exchange Store resource.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-65298
GRT backup set folder: \\.pdvfs\SERVERNAME\2\BEData\IMG000009
The consistency check of the snapshot for the Microsoft Exchange database Database was successful.
V-79-57344-65298 - The Exchange Store service is not responding. Backup set canceled.
V-79-57344-65072 - An error occurred while connecting to the Backup Exec Remote Agent on the Backup Exec server. Ensure that the job options are correct, and then submit the job again. The backup set was not created.
So it backs up all of the data, passes the consistency check, and then fails on the step right after that, clears all of the data off.
This issue has literally been going on for weeks. Our Exchange setup is running on older hardware and I'm getting very nervous about this issue.
We've attempted disabling GRT. We've tried disk storage, deduplication disk storage, virtual tape storage, etc.
We're successfully backing up Oracle, SQL server, and flat files to this new BackupExec server without issues.
Any help would be GREATLY appreciated.
Do you backup these 3 datastores in parallel (so 3 jobs starting at the same time) if you do and they are on teh same Exchnage server, then suggest you stagger the start times of the jobs slightly so they are maybe 5-10mins appart on start times.
We have seen issues in the past where the Consistency check cannot run at the same time against multiple stores on the same Exchange server.