SeeDk
asked on
Backup Exec 2012 - Incremental Exchange Backup fails
This backup has been working fine for months but started failing over the weekend.
The error given has been consistently with the same mailbox database.
The first failure had this error message:
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-1811 The file was not found. '
After that, it has continued to fail daily and all the subsequent error messages are:
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-530 There is a bad signature for a log file. '
Checking online, I have found suggestion to disable consistency checks (this was already disabled) and to disable GRT, test, then re-enable again.
I haven't tried the GRT recommendation yet.
Is there anything else I should check?
The error given has been consistently with the same mailbox database.
The first failure had this error message:
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-1811 The file was not found. '
After that, it has continued to fail daily and all the subsequent error messages are:
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-530 There is a bad signature for a log file. '
Checking online, I have found suggestion to disable consistency checks (this was already disabled) and to disable GRT, test, then re-enable again.
I haven't tried the GRT recommendation yet.
Is there anything else I should check?
Hi,
did you try backuping the ACTIVE exchange database? Have a look at this :
http://www.veritas.com/community/forums/v-79-57344-759-unable-complete-operation-selected-resource-using-specified-options-following-
And look at the last post :
Go to the job properties - Microsoft Exchange - High Availability Server (Exch 2007 or later):
set this to "Backup from the active copy only".
That gave me success on the GRT job.
did you try backuping the ACTIVE exchange database? Have a look at this :
http://www.veritas.com/community/forums/v-79-57344-759-unable-complete-operation-selected-resource-using-specified-options-following-
And look at the last post :
Go to the job properties - Microsoft Exchange - High Availability Server (Exch 2007 or later):
set this to "Backup from the active copy only".
That gave me success on the GRT job.
The database has 1 megabytes of free space after online defragmentation has terminated.No I don't think that it will dismount. But I am no exchange nor DB expert.
Could this be related?
If the free space is filled up; will the database dismount automatically? What are my options to prevent this?
I suppose it is about 1 MB free space inside the DB space/files.
ASKER
Thanks, mrtortur.
I can give this a try but I'm wondering if this is the issue why would this just start happening now?
If the job is successful, can I revert back to the default setting?
It has been running fine for months, can it be certain there is nothing on Exchange side which needs to be checked?
I can give this a try but I'm wondering if this is the issue why would this just start happening now?
If the job is successful, can I revert back to the default setting?
It has been running fine for months, can it be certain there is nothing on Exchange side which needs to be checked?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
HI Arka,
So you are suggesting disabling the GRT but leaving the Microsoft Exchange - High Availability Server (Exch 2007 or later) setting at:
Back up from the passive copy and if not available, try the active copy (recommended)?
Then when that succeeds, re-enable the GRT?
Just want to confirm because mrtortur's suggestion was only to change that High Availability server and he did not mention anything about disabling the GRT.
So you are suggesting disabling the GRT but leaving the Microsoft Exchange - High Availability Server (Exch 2007 or later) setting at:
Back up from the passive copy and if not available, try the active copy (recommended)?
Then when that succeeds, re-enable the GRT?
Just want to confirm because mrtortur's suggestion was only to change that High Availability server and he did not mention anything about disabling the GRT.
ASKER
I tried both suggestions. Neither worked.
Backing up from active copy failed with the same error.
Turning off GRT worked but that's no good to leave like that so I turned it back and ran incremental again.
Backup failed with even more errors.
V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-528 The current log file is missing. '
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-4001 A read was issued to a location beyond the EOF (writes will expand the file). '
V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-528 The current log file is missing. '
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-4001 A read was issued to a location beyond the EOF (writes will expand the file). '
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-530 There is a bad signature for a log file. '
The last error was for the same database as before (even same error). The others before that are for the other Exchange databases this job is backing up.
So now I guess I should try running a full backup and see if that will work?
Maybe turning off GRT and turning it back on for an incremental is not a good solution?
Backing up from active copy failed with the same error.
Turning off GRT worked but that's no good to leave like that so I turned it back and ran incremental again.
Backup failed with even more errors.
V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-528 The current log file is missing. '
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-4001 A read was issued to a location beyond the EOF (writes will expand the file). '
V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-528 The current log file is missing. '
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-4001 A read was issued to a location beyond the EOF (writes will expand the file). '
V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-530 There is a bad signature for a log file. '
The last error was for the same database as before (even same error). The others before that are for the other Exchange databases this job is backing up.
So now I guess I should try running a full backup and see if that will work?
Maybe turning off GRT and turning it back on for an incremental is not a good solution?
ASKER
So I ran a full backup with the original settings:
"GRT enabled" and "Back up from the passive copy and if not available, try the active copy (recommended)" both selected.
It succeeded. Right after, the scheduled incremental started and succeeded. So that looks good.
Since the incremental ran so soon after the full, I'm thinking this isn't definitive proof that everything is fine.
I will check again tomorrow morning what the status of the incremental is.
"GRT enabled" and "Back up from the passive copy and if not available, try the active copy (recommended)" both selected.
It succeeded. Right after, the scheduled incremental started and succeeded. So that looks good.
Since the incremental ran so soon after the full, I'm thinking this isn't definitive proof that everything is fine.
I will check again tomorrow morning what the status of the incremental is.
Yes, log files corruption is the main culprit here. So once the full is complete and the logs are flushed everything should be OK.
Also what is the Full backup schedule? Run a full GRT-enabled backup job periodically if your backup strategy uses frequent incremental GRT-enabled jobs. If this data amount increases too much, it can negatively affect your system resources.
In ideal case, you should always run full backup for GRT backups.
Regards,
Arka
Also what is the Full backup schedule? Run a full GRT-enabled backup job periodically if your backup strategy uses frequent incremental GRT-enabled jobs. If this data amount increases too much, it can negatively affect your system resources.
In ideal case, you should always run full backup for GRT backups.
Regards,
Arka
ASKER
We run a full backup every Saturday.
Incrementals daily throughout the week until the next full backup.
It has been working fine for months. Not sure why it had this error this time.
Incrementals daily throughout the week until the next full backup.
It has been working fine for months. Not sure why it had this error this time.
ASKER
The database has 1 megabytes of free space after online defragmentation has terminated.
Could this be related?
If the free space is filled up; will the database dismount automatically? What are my options to prevent this?