Forum Discussion

Khue's avatar
Khue
Level 4
15 years ago

Restoring from Decommissioned Exchange Servers

A few months back we decommissioned our old mail server (Call it mail1). We now have an identically setup mail server. Same permissions/storage groups/etc. We do nightly full backups of the mail stores. I am currently trying to restore data from the old mail server to the new mail server (call it mail2). I am able to retrieve some of the data, but when restoring the information, I eventually get a failure. I have so far had 2 separate attempts to restore data. The first time I restored a few emails to the mailbox but not all and got the following error:

"Error : e000fe2d - The backup of the item is bad."

The second time I attempted to restore the mailbox was from a different evening/date all together and again I got:

"Error : e000fe2d - The backup of the item is bad."

Is it not possible to restore data from mail1 to mail2 even though the mailboxes/permissions/set up of the server is the same? This seems like a massive caveat to the restore process. I am currently running BE 12.5 (one of the issues maybe that the exchange server is still running an agent from 12.0).

Any help is appreciated! Thanks!
12.x and Earlier
Backup and Recovery
Backup Exec
Restore
Tip-How to
Troubleshooting
  • Khue's avatar
    Khue
    15 years ago
    I just wanted to follow up with what I did to resolve the issue. I worked with Symantec Support who assisted me in reviewing my process and updating the BE Agent from 12.0 to 12.5. When I updated the agent I simply copied the RAWS32 folder to the desktop of the exchange server. I then stopped the service and ran the setupaa.cmd file. The agent updated without a hitch and it did not ask to be rebooted. I verified that the BERemote.exe was running (BE Remote Agent Service). While the Symantec Support rep maintained that this was the reason the restore was failing, I have another theory that is far simpler.

    The user that I was attempting to restore, is a corporate Vice President. As such, they are entitled to a very large mailstore. We stage our restores and then dump the restores into a Test User mailbox. The Test User mailbox is setup as a typical user and has a small inbox (about 100 megs). When I was attempting to restore the VP's mailstore to the Test User mailstore, some emails would be restored before the restore failed. Putting 2 and 2 together, I realized that the VPs mailstore was 300 megs and the Test User's mailstore was only 100. The failure was occurring because BE attempted to dump more data then the Exchange server would allow. 

    I resolved the issue after I emptied the Test User account and only restored the required emails from the VP. Symantec will claim that it's the agent that was the issue. I claim that it's me not realizing size constraints between two accounts. 
  • Khue's avatar
    Khue
    Level 4
    15 years ago
    I just wanted to follow up with what I did to resolve the issue. I worked with Symantec Support who assisted me in reviewing my process and updating the BE Agent from 12.0 to 12.5. When I updated the agent I simply copied the RAWS32 folder to the desktop of the exchange server. I then stopped the service and ran the setupaa.cmd file. The agent updated without a hitch and it did not ask to be rebooted. I verified that the BERemote.exe was running (BE Remote Agent Service). While the Symantec Support rep maintained that this was the reason the restore was failing, I have another theory that is far simpler.

    The user that I was attempting to restore, is a corporate Vice President. As such, they are entitled to a very large mailstore. We stage our restores and then dump the restores into a Test User mailbox. The Test User mailbox is setup as a typical user and has a small inbox (about 100 megs). When I was attempting to restore the VP's mailstore to the Test User mailstore, some emails would be restored before the restore failed. Putting 2 and 2 together, I realized that the VPs mailstore was 300 megs and the Test User's mailstore was only 100. The failure was occurring because BE attempted to dump more data then the Exchange server would allow. 

    I resolved the issue after I emptied the Test User account and only restored the required emails from the VP. Symantec will claim that it's the agent that was the issue. I claim that it's me not realizing size constraints between two accounts.