11-20-2013 06:50 AM
I know there are many posts similar to this, but we're currently running Backup Exec 2012 SP2 and Exchange 2010 SP2. So AOFO should definitely be disabled when backing up the information stores? I've came across several suggestions, but I dont see this documented anywhere. Thanks for your help.
Solved! Go to Solution.
01-09-2014 06:54 AM
Thanks for the insight everyone; I made several changes. I disabled AOFO, changed the location of the GRT temp directory, and made the registry changed here - http://www.symantec.com/business/support/index?page=content&id=TECH180039. Also, I did slightly modify (lowered) the retention time on the backup job in question. All in all, the backups have been pretty smooth since. However, I'm not sure if there was one specific solution. Thanks again.
11-20-2013 07:05 AM
You are correct. It is recommended to disable AOFO for database backup jobs.
Here are a couple of technotes which outlines job failure if AOFO is used for database backup jobs:
11-20-2013 07:08 AM
Hi,
Please find the following article about AOFO:
About the Advanced Open File Option:
http://www.symantec.com/docs/HOWTO24184
Regards,
S
11-20-2013 08:10 AM
I see. I've been getting an intermittent error, but its not an error listed in those docs. Anyways, if this is best practice, I guess I'll disable it and go from there. Thanks.
11-20-2013 08:16 AM
what were the error messages you were getting?
can you please list few of those, may be i can explain the cause of it.
Regards,
S
11-20-2013 09:45 AM
About once a week I get the following errors on my mailstore backups -
Unable to complete the operation for the following reason: VFF Open Failure. This can be caused by low memory or disk resources
and then
Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information.
However, I've gotten this error the past two nights. Seems to be really random. Thanks.
11-20-2013 06:32 PM
To resolve your problem, see this document
http://www.symantec.com/docs/TECH66427
11-22-2013 01:24 PM
Hmm.. resources appear to be suficient. I did enable logging and found the following error -
CheckVirtOpen:Unable to see I/O in GRT directory :C:\TEMP\Backup Exec\IMG33\vdb_2013_11_21_2356_37\ExchangeDB.edb.Virt___0
The most likely cause of this problem is that the path is on a DFS share. Suggest using a local drive or non-DFS share.
I'm doing B2D and then duplicate to tape. The errors I mentioned before have been appearing on B2D backups primarily, but I have gotten the same error durng the duplicate job a couple of times. I came across this article http://www.symantec.com/business/support/index?page=content&id=TECH180039, but it doesnt have BE2012 in the affected products list. Is there another registry fix that may apply? Could it be an issue with the TEMP directory for GRT? Thanks again.
11-22-2013 05:02 PM
There is no harm in putting in the registry entry and then trying again.
You can also try to change the temp directory used in the GRT process. See this comment on how to do so.
https://www-secure.symantec.com/connect/forums/backup-exec-creating-temp-folders#comment-5953381
11-27-2013 08:59 AM
Ok, will do. As far as the temp directory for GRT, is there a recommended amount of free space needed during a backup to disk operation? Thanks in advance.
11-27-2013 09:32 AM
...the temp location needs to be at least as big as the biggest restore. For example, if you're restoring an Exchange item and the Information Store is 100GB, then you need at least 100GB free.
Thanks!
01-09-2014 06:54 AM
Thanks for the insight everyone; I made several changes. I disabled AOFO, changed the location of the GRT temp directory, and made the registry changed here - http://www.symantec.com/business/support/index?page=content&id=TECH180039. Also, I did slightly modify (lowered) the retention time on the backup job in question. All in all, the backups have been pretty smooth since. However, I'm not sure if there was one specific solution. Thanks again.