Restore of Microsoft Exchange Mailstore(s) fail with 0xe000fe7a error in the job log
| Article:TECH47784 | | | Created: 2006-01-10 | | | Updated: 2009-01-10 | | | Article URL http://www.symantec.com/docs/TECH47784 |
Problem
Restore of Microsoft Exchange Mailstore(s) fail with 0xe000fe7a error in the job log
Error
Final error: 0xe000fe7a - An error occurred while accessing Microsoft Exchange Server. Check the application event log on the Exchange Server for more
details.
Information Store (272) , Unable to read the header of logfile , Error -530.
Solution
Instead of
writing to the defined temp folder using \storagegroupname\logfile.log
path it misses out on the \ and writes storagegroupnamelogfile.log
to the root of the path. This will happen for a random selection of the log
files. This causes the restore to fail when a hard recovery is performed and the
log files from the tape is being committed. This is because the incorrectly
named log files will be missing in the sequence for the log files that are
written to the correct path.
This will
typically just happen on cross domain restores.
Directory of
C:\Temp
11/05/2006 09:17 <DIR> .
11/05/2006 09:17 <DIR> ..
11/05/2006 09:19 <DIR> First
Storage Group
31/01/2006 16:41
5,242,880 First Storage GroupE0200037.log
31/01/2006 16:34
5,242,880 First Storage GroupE0200038.log
Error in the
job log.
Restore-
\\<Exchange server name>\Microsoft Information Store\First Storage Group
V-79-57344-65146 - An error occurred with Exchange Server.
Please use
the Event Viewer to examine the event log for details.
This error is
presented in the event log at the time the restore job fails.
Event
Type: Error
Event
Source: ESE
Event
Category: Logging/Recovery
Event
ID: 412
Date: <date>
Time: <time>
User: N/A
Computer: Exchange
server name
Description:
Information
Store (272) First Storage Group: Unable to read the header of logfile
<drive>:\<temp path>\<logilename>.log. Error
-530.
Workaround:
1. Run the
restore job without the commit option selected and then rename the logfiles to
be of the correct name and move them to the \Storeagegroup name temp folder.
Note:
The files you will need to rename and move is located at the root of
temporary folder specified in Tools ¦ Options ¦ Exchange ¦
"Temporary location for patch and log files".
2. Then run
eseutil /cc to commit the restored log files and then mount the store(s).
Note:
Make sure to follow Microsoft's documentation on how to run the eseutil
tool.
If it fails to
write all the needed log files during the restore process to the temporary path,
this workaround will not work.
OR
Another
possibility is to use a Backup Exec for Windows Media server in the same domain
as the Exchange server being restored to for the restore job.
The hotfix
for this issue is included in SP4 for Backup Exec for Windows version
10d.
|
|
| Source | ETrack |
| Value | 521483 |
| Description | XCH :Restore to recovery server puts the log file in temp dir without \ for each 2nd log file |
| Source | Error Code |
| Value | 0xe000fe7a |
| Description | An error occurred while accessing Microsoft Exchange Server. |
| Source | UMI |
| Value | V-79-57344-65146 |
| Description | An error occurred while accessing Microsoft Exchange Server. |
| Source | Event ID |
| Value | 412 |
| Description | Information Store (272) First Storage Group: Unable to read the header of logfile |
Related Articles
Legacy ID
283335
Article URL http://www.symantec.com/docs/TECH47784
Terms of use for this information are found in Legal Notices
Thank you.