10-04-2011 06:28 AM
Hello,
We've been backing up our one of our DCs for the last 9 months without issue and received the error noted above for the first time last night. All of the information that I'm finding regarding that error related to Exchange. Does anyone have any insight into this issue?
I'd be inclined to let it go another night to see if it sorts itself out, but I'd rather not miss another backup.
We are running Backup Exec 2010 R3 on Server 2008 R2. The DC that is being backed up is also running Server 2008 R2.
Thanks for any help you can offer!
Solved! Go to Solution.
10-04-2011 06:41 AM
That error relates to our GRT capability so can affect Exchange, Active Directory AND SQL, admittedly we see it more often with Exchange.
It should not directly affect the ability to restore a complete VM. However do a test with Application GRT disabled and see if the error stops.
At this current time we know one cause for that error - if you have mounted a disk against a subfolder as a mount point (in such a way that the disk in question does not have an actual drive lettter) and then located the GRT supported database files in this mount point .
However in your case as you were working, unless you ran out of space and moved the NTDS.DIT etc files off the C: drive to a mount point that looked like the original path then I doubt you have this configuration.
Unfortunately we are trying to identify other causes for this error so encourage customers to log formal support cases for the issue.
EDIT: For completeness - a couple of links relating to my above statements:
http://www.symantec.com/docs/TECH152703
http://www.symantec.com/docs/TECH154707
10-04-2011 06:34 AM
Do you have all available patches installed on Backup Exec 2010R3 ?
Specific this one:
http://www.symantec.com/business/support/index?page=content&id=TECH128831
10-04-2011 06:39 AM
All available updates are installed except for SP1
10-04-2011 06:41 AM
That error relates to our GRT capability so can affect Exchange, Active Directory AND SQL, admittedly we see it more often with Exchange.
It should not directly affect the ability to restore a complete VM. However do a test with Application GRT disabled and see if the error stops.
At this current time we know one cause for that error - if you have mounted a disk against a subfolder as a mount point (in such a way that the disk in question does not have an actual drive lettter) and then located the GRT supported database files in this mount point .
However in your case as you were working, unless you ran out of space and moved the NTDS.DIT etc files off the C: drive to a mount point that looked like the original path then I doubt you have this configuration.
Unfortunately we are trying to identify other causes for this error so encourage customers to log formal support cases for the issue.
EDIT: For completeness - a couple of links relating to my above statements:
http://www.symantec.com/docs/TECH152703
http://www.symantec.com/docs/TECH154707
10-04-2011 06:53 AM
I'll give that a try and see how it goes.
Thanks!