Backup Restore - Blank Email Body
- Hi,
i am running exchange server 2003 enterprise edition with 4 stores, on windows server 2003 standard Sp2 fully updated.
i am using Backup Exec 12.5 to backup the information stores with GRT.
when i try to restore messages from backup, many of the restored messages have the body of the email missing! there seems to be nothing common to these messages, some have attachments and some do not.
Symantec have been working with me for weeks and can not fix the problem.
could this be a problem with the information stores or the exchange server? or will it definitely be a backup exec problem?
I can export to a PST in outlook from a mailbox and all the body is there, no problem.
Any suggestions would be greatly appreciated.
Thanks
Shazz
Respuestas
- HI,
Seem your problem bounded to specific Storage Group. So move all mailboxes to newly created database and remove old database as well.
regads- Propuesto como respuestaGayanWIc miércoles, 18 de noviembre de 2009 6:29
- Marcado como respuestaJames-LuoMSFT, Moderadorlunes, 23 de noviembre de 2009 2:09
- Hi,
i figured this one out. i had to be logged into ESM not as the administrator. i logged onto the exchange server as another member of the domain admins group and moved the mailbox successfully.
thanks
shazz- Marcado como respuestaJames-LuoMSFT, Moderadormartes, 01 de diciembre de 2009 1:16
Todas las respuestas
- Note:
I have 4 information stores, and this is only occuring on the first default information store where the majority of my mailboxes reside (same store where public folders are located). when i run restore from any of the other stores the body is in the emails!
Any Suggestions?
Thanks
Shazz
HI,
Did you try with windows NT backup ? if you able to restore using NTbackup that error would be backupExec issuse.
Also
Check event viewer and run EXBPA whether see any error or warnings. .
Regards
Chinthaka Shameera | MCITP: EA | MCSE: M | http://howtoexchange.wordpress.com/- Propuesto como respuestaJames-LuoMSFT, Moderadormiércoles, 18 de noviembre de 2009 5:41
- Hi,
thanks for the reply,
there are no errors in event viewer.
the strange thing is that the issue does not occur in the other stores (each mail store is a member of it's own storage group also), the issue only occurs in the first storage group.
i had run EXBPA in the past to troubleshoot another problem and the only issue it found was with the logs and database on the same volume.
Symantec support are saying they believe there is a curruption in the first storage group and to move all mailboxes to the other 3 stores where the issue does not occur. and just leave the faulty store empty apart from the system attendant mailbox etc.
thanks
shazz - Note: when I move a mailbox to one of the other stores the issue is no longer there for that mailbox, so there appears to be no corruption in the mailbox's as the data is still there, it's rather a problem with BE 12.5 backing up the body of individual mail items only in the first storage group.
I just ran the EXBPA health check again and the only issue were
*storage drive more than 2 years old
*NIC driver more than 2 years old
*logs on same volume as database
thanks
shazz
- HI,
Seem your problem bounded to specific Storage Group. So move all mailboxes to newly created database and remove old database as well.
regads- Propuesto como respuestaGayanWIc miércoles, 18 de noviembre de 2009 6:29
- Marcado como respuestaJames-LuoMSFT, Moderadorlunes, 23 de noviembre de 2009 2:09
- Hi GayanwIc,
Yes i think that is what i will do, i will move all mailboxes to one of the other three stores.
what about the system attendant mailbox? should i just leave this in the first store by itself once all the user mailboxes are gone?
its is a very strange issue, would be nice to know what the root cause is.
thanks
shazz “If the store is then deleted, the System Attendant mailbox will be moved automatically into another mailbox store on the server, that is, the HomeMDB value on the directory object will be updated”
---------Refer to <Overview of Exchange 2000 Server and Exchange Server 2003 Special Mailboxes>
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com- Thanks James,
have you ever heard of anything like this before? For the message body invisible in one store but appear in another store after restored? No, I haven’t
According to description, the most possible cause is indeed the problematic store. One integrity check can be run on the store, see if there’s any relevant error info
Move the mailboxes, and then recreate a new store would be the option as suggested above
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com- Thanks James,
I have been looking through the “information” events in the application logs on the exchange server and it appears that the ESE online defrag is failing (not completing due to interruption) everyday with the this store "priv1.edb" file! logging event 704.
There are some of these 704 events relating to the other stores, but they are always followed with a 701 event stating that the defrag was resumed and completed successfully. But not with this store.
Do you think this could have something to do with the issue?
I will change the ESE maintenance interval in exchange system manager for that store and see if it runs the online defrag. then i will move the mailboxes to one of the other 3 stores before doing some integrity checks and offline defrag with ESEutil (just incase) . then if errors found or repaired i will move some mailboxes back and then test again.
sound like a good idea?
Thanks
Shazz - Yes, that's a plan :)
James Luo
TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
If you have any feedback on our support, please contact tngfb@microsoft.com - Hi,
during the move the mailboxes seem to be a fair bit smaller. e.g. when a mailbox is in the original store its is 760mb but then when moved to the new store it is 670mb! there are no failures reported in the move process however.
is this something to be concerned about? or is this typical as the mailbox is effectivly defragmented whilst being moved?
many thanks
shazz - Hi,
I have managed to move all mailboxes (100+) without error, except for the "administrator" account.
for some reason when trying to move this account the move fails with the following error -
<progress code="0" milliseconds="12765">Opening destination mailbox.</progress>The information store could not be opened. The MAPI provider failed. MAPI 1.0 ID no: 8004011d-0289-00000000
this occurs no matter which store i try to move it to!
there is also the following events listed in the application error log -
9175
The MAPI call 'OpenMsgStore' failed with the following error:
The information store could not be opened.
The MAPI provider failed.
MAPI 1.0
ID no: 8004011d-0289-00000000
9168
Failed to open mailbox '/o=company name Retail Group/ou=First Administrative Group/cn=Recipients/cn=Administrator' in mailbox store '/o=company name Retail Group/ou=First Administrative Group/cn=Configuration/cn=Servers/cn=EXCHANGESERVER/cn=Microsoft Private MDB' on server 'EXCHANGESERVER'. Error: The information store could not be opened.
1008
The MAPI provider failed.
MAPI 1.0
ID no: 8004011d-0289-00000000
Unable to move mailbox 'Administrator'.
Error: The information store could not be opened.
The MAPI provider failed.
MAPI 1.0
ID no: 8004011d-0289-00000000
any ideas?
many thanks
shazz - Hi,
i figured this one out. i had to be logged into ESM not as the administrator. i logged onto the exchange server as another member of the domain admins group and moved the mailbox successfully.
thanks
shazz- Marcado como respuestaJames-LuoMSFT, Moderadormartes, 01 de diciembre de 2009 1:16
