Link to home
Start Free TrialLog in
Avatar of isdirect
isdirectFlag for United States of America

asked on

Restore Mailbox from Exchange 2003 to Exchange 2010 using Backup Exec

I need some help!  I am in the final stages of a migration from Exchange 2003 to Exchange 2010 in same domain.  I have one user who has an extremely large mailbox on Exchange 2003; I would prefer to restore it from Symantec Backup Exec to a temporary mailbox on the new server rather than to submit a "move request" using Exchange 2010 console (to allow the user to take her time pulling only the data she truly wishes to retain from the temp mailbox.)

I have a clean full backup of her Exchange 2003 mailbox, but when I try to re-direct the restore job to the temporary mailbox on Exchange 2010, the restore job fails with error V-79-57344-765, implying a problem with credentials.  However, I am using my account both for the backup and the restore jobs, and my account has full access permissions on both her Exchange 2003 mailbox and on the temporary Exchange 2010 mailbox.  The restore job creates the correct folder structure on the target mailbox, but fails when populating items in those folders, and logs this exact error for each item:

V-79-57344-765 - Cannot set one or more properties for [e-mail subject line].

I am truly stumped by this one and will greatly appreciate any help you can provide!!
SOLUTION
Avatar of Manpreet SIngh Khatra
Manpreet SIngh Khatra
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I moved 90 GB mailbox without any issue, is that bigger then this also. Just move it to Exchange 2010, rest Exchange will take care. However it will be a offline move so user cannot access the mailbox until it is moved fully. Make sure to skip the bad items.

Or else cut down to pst's , empty the mailbox, move and then merge the mailbox again.
Avatar of isdirect

ASKER

shaiksaj - thank you for that link from Symantec support, but I had read through that already earlier today.  Not a solution, I'm afraid, because it addresses only public folders and not an individual user's mailbox.

amitkulshrestha - you moved a 90 GB MAILBOX???  Seriously??  I thought 11 GB was bad, and because it's so much larger than the "supported" size for Exchange 2003, I was not ready to attempt that.

For all experts - am I really looking for an answer with respect to the apparent credentials / permissions problem, and obviously Symantec's online help is no help.  Do any Exchange experts have ideas for workarounds, other than PST files...?
I have moved mailboxes even up to 25GB with the Mailbox Move request.  However as a common practice for those migrations where the customer requires quick access to the mailbox.  Another option is to use ExMerge on your Exchange 2003 box, and just reduce the size of the mailbox down to a manageable level.  Now remember Exchange 2003 PST limit was what 2GB I think, so for an 11GB mailbox your going to have 5 or 6 separate PST file's.  But that is no biggie since you can just import at the Server level when finished or worst case import at the Outlook level.

I have used this method numerous times, and once you get the mailbox down around 1gb it moves very fast to Exchange 2010.
11GB you can move directly.
Avatar of mirifexmso
mirifexmso

I have exported the mailbox to a PST from Exchange 2003 and imported the PST into Office 365 Microsoft's Exchange Cloud services using Outlook client. The mailbox was about 10gb and took forever.  Best to do it on after hours of course.
I received interesting suggestions about moving the mailbox from one server to another, and one reference to the same Symantec KB article that I had already found useless.  No answer to the actual question I posted, so I am closing this without awarding any points.
Mailbox move is the only solution, you cannot restore 2003 db to a 2010 exchange server. It is a design limitation.
I've requested that this question be deleted for the following reason:

I just provided my reason in a comment on the question, and in light of the instructions above, I think this is redundant, so I will write a variant...  I am deleting this question without awarding points because none of the experts who responded actually answered the question.  Since I pay for this subscription, I don't think I should be limited to one question at a time.  God knows that EE has paid for itself many times over in my case, but the site administrators would do well to consider allowing members - especially long-term members like me - to have a little more leeway about open questions.
You asked question about restoring Exchange 2003 db to 2010 and Experts answered it correctly, what can be done and how to do it.
For this question, first post by Rancy is the correct answer, rest were all suggestion. So, I suggest to mark Post 38752185 as the answer for this question.

Exchange 2003 data cant be restored to Exchange 2010 due to different build and Structures

- Rancy
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Your simply speaking about i guess a redirection of Files that can be done with a file server (Non-Exchange) as well .... but Exchange 2010 architecture cant understand Exchange 2003 files cause of the difference in their builds

- Rancy