SeeDk
asked on
Exchange 2007 - Backup Exec 2010 incremental backup errors after Full Backup
This configuration has been running for several months with no issue.
Last month, after a scheduled full backup of Exchange this sequence of events occured:
1. The Scheduled Full Backup is Successful.
2. Later that same day the Incremental Backup is Successful.
3. The day after, the Incremental Backup fails and produces this error:
Backup- \\exchange.domain.com\Micr
V-79-57344-759 - Unable to complete the operation for the following reason: VFF Open Failure. This can be caused by low memory or disk resources.
4. The day after that, the Incremental fails again with this error:
Backup- \\exchange.domain.com\Micr
V-79-57344-862 - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. You must use the Exchange Agent to run a full backup before you run a differential or incremental backup.
I let it run one more day after this and same error at #4 re-occurred.
I fixed it by running a Full Backup manually, and the Incrementals have been successful since then.
Now, one month later, I am at step 3 again.
The Scheduled Full Backup has run with no issues. That night, an Incremental ran with no issues. The day after, I have again received the error at #3.
I think if I leave it alone, I will probably get the error at #4 again.
Running a Full Backup manually may fix it again but I would like to know what could be causing this.
There aren't any storage or memory issues on either server. I'm not seeing anything in the Event logs and there is no other backup software running on the Exchange server.
Symantec offers some solutions for these errors but all those solutions are for treating these errors in isolation. Not when they occur one after the other.
Last month, after a scheduled full backup of Exchange this sequence of events occured:
1. The Scheduled Full Backup is Successful.
2. Later that same day the Incremental Backup is Successful.
3. The day after, the Incremental Backup fails and produces this error:
Backup- \\exchange.domain.com\Micr
V-79-57344-759 - Unable to complete the operation for the following reason: VFF Open Failure. This can be caused by low memory or disk resources.
4. The day after that, the Incremental fails again with this error:
Backup- \\exchange.domain.com\Micr
V-79-57344-862 - The Backup Exec Agent for Microsoft Exchange was not used to create the last full backup of this database. You must use the Exchange Agent to run a full backup before you run a differential or incremental backup.
I let it run one more day after this and same error at #4 re-occurred.
I fixed it by running a Full Backup manually, and the Incrementals have been successful since then.
Now, one month later, I am at step 3 again.
The Scheduled Full Backup has run with no issues. That night, an Incremental ran with no issues. The day after, I have again received the error at #3.
I think if I leave it alone, I will probably get the error at #4 again.
Running a Full Backup manually may fix it again but I would like to know what could be causing this.
There aren't any storage or memory issues on either server. I'm not seeing anything in the Event logs and there is no other backup software running on the Exchange server.
Symantec offers some solutions for these errors but all those solutions are for treating these errors in isolation. Not when they occur one after the other.
Sunil
Have you configured the DAG backup with GRT?
ASKER
DAG's are an Exchange 2010 and higher feature, aren't they?
These backups do have GRT enabled.
These backups do have GRT enabled.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I didn't because both Backup Exec and Exchange are installed on 64 bit servers.
Last time, the issue was resolved by doing another Full Backup, so this wasn't needed.
Also, the error " V-79-57344-862" occurred the day after, which that article doesn't mention at all.
For today, I will probably let the incremental run again on it's own and see if I do get V-79-57344-862 again.
Last time, the issue was resolved by doing another Full Backup, so this wasn't needed.
Also, the error " V-79-57344-862" occurred the day after, which that article doesn't mention at all.
For today, I will probably let the incremental run again on it's own and see if I do get V-79-57344-862 again.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There are updates, I am wary of installing them in case they cause something else to break though.
I did remove AV temporarily to rule that out. The issue still re-occured.
I opened a ticket with Veritas, will see if they can shed some more light on this.
I did remove AV temporarily to rule that out. The issue still re-occured.
I opened a ticket with Veritas, will see if they can shed some more light on this.
Hi,
Okay. Do you know what is you current Backup Exec release ?
The closer you are to the target version (R3 SP2) the lesser probability of another issue..
But I understand you. Good to launch a support case, we'll see their answer, please share it if possible.
Okay. Do you know what is you current Backup Exec release ?
The closer you are to the target version (R3 SP2) the lesser probability of another issue..
But I understand you. Good to launch a support case, we'll see their answer, please share it if possible.
ASKER
This appears to be a very old version of 2010 (13.0).
Support did reach back to me but they lived up to their reputation of not being very helpful.
After an hour long call in which the tech decided JUST THEN was a good time to review the logs I sent, she could only suggest the registry fixes which are already mentioned here.
I just ran another full back for now and may make those changes if this keeps happening.
Support did reach back to me but they lived up to their reputation of not being very helpful.
After an hour long call in which the tech decided JUST THEN was a good time to review the logs I sent, she could only suggest the registry fixes which are already mentioned here.
I just ran another full back for now and may make those changes if this keeps happening.