Solved

Restore Mailbox from Exchange 2003 to Exchange 2010 using Backup Exec

Posted on 2013-01-07
17
1,119 Views
Last Modified: 2013-02-02
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!!
0
Comment
Question by:isdirect
  • 5
  • 4
  • 2
  • +3
17 Comments
 
LVL 52

Assisted Solution

by:Manpreet SIngh Khatra
Manpreet SIngh Khatra earned 500 total points
ID: 38752185
Exchange 2003 data cant be restored to Exchange 2010 due to different build and Structures

- Rancy
0
 
LVL 16

Expert Comment

by:Shaik M. Sajid
ID: 38752306
0
 
LVL 42

Expert Comment

by:Amit
ID: 38752530
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.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 

Author Comment

by:isdirect
ID: 38752563
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...?
0
 
LVL 3

Expert Comment

by:jodiddy
ID: 38753388
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.
0
 
LVL 42

Expert Comment

by:Amit
ID: 38753557
11GB you can move directly.
0
 

Expert Comment

by:mirifexmso
ID: 38754669
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.
0
 

Author Comment

by:isdirect
ID: 38809792
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.
0
 
LVL 42

Expert Comment

by:Amit
ID: 38809812
Mailbox move is the only solution, you cannot restore 2003 db to a 2010 exchange server. It is a design limitation.
0
 

Author Comment

by:isdirect
ID: 38809859
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.
0
 
LVL 42

Expert Comment

by:Amit
ID: 38809860
You asked question about restoring Exchange 2003 db to 2010 and Experts answered it correctly, what can be done and how to do it.
0
 
LVL 42

Expert Comment

by:Amit
ID: 38814093
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
0
 

Accepted Solution

by:
isdirect earned 0 total points
ID: 38827636
Experts:

When I am wrong, I admit it.  And when I have overlooked something, then I will accept suggestions and move forward.  HOWEVER.........

It is entirely possible to restore data from Exchange 2003 to Exchange 2010, and I can prove it.  Please note in the job log below the SUCCESSFUL RESTORE of Exchange 2003 data to an Exchange 2010 server!!!!  I cannot account for my magical ability to perform this impossible feat, but I will gladly demonstrate it for anyone who wishes to see it happen "live."

I have made two alterations in the data from this log file:  I deleted extraneous line feeds, and I renamed the target mailbox.  The source was another user's 2003 Inbox, but the target actually was my own mailbox; I merely have substituted my Experts Exchange screenname (isdirect) for my real username in this log.  Otherwise, this log demonstrates that I can restore data from an Exchange 2003 server (stjcomm.stjnet.local) to an Exchange 2010 server (stjcomm2010.stjnet.local) using Symantec Backup Exec 2012 (STJBESSY2).  We use a NAS (STJNAS4) as the remote storage device for our Exchange Backups so you will note that in the log.

PLEASE ALSO NOTE that my original question was very specifically about the error messages that are occurring when I attempt this action for data from ANOTHER user's mailbox.  I cannot account for those error messages, and clearly neither can any other experts, but I remain hopeful.  I love this forum, and I greatly respect the experts who participate, but I AM AN EXPERT, TOO, in my own way, and I don't believe that I should be subjected to anything less than a respectful response.  I asked a legitimate question which has yet to be answered.

Here's the job log.  Can anyone account for the fact that I can successfully perform this restore?

-----------------------------------------------------------------------------------

Job Log: BEX_STJBESSY2_07271.xmlJob Log for stjcomm.stjnet.local Restore 00145

      Completed status: Successful
      Expand AllCollapse All

      Job Information
Job server: STJBESSY2
Job name: stjcomm.stjnet.local Restore 00145
Job started: Monday, January 28, 2013 at 12:00:48 PM
Job type: Restore
Job Log: BEX_STJBESSY2_07271.xml

      Job Operation - Restore
            Server - stjcomm2010.stjnet.local
Drive and media information from media mount: 1/28/2013 12:00:50 PM
Drive Name: NAS4_STJCOMM (\\stjnas4\bemedia\stjcomm\IMG001544)
Media Label: IMG001544
Media GUID: {ba3df03f-dc4f-4c37-91d7-efbe7992969d}

All Media Used
 IMG001544

Set Information - \\STJCOMM2010\Microsoft Information
                  Store\Mailbox Database 1833558609 STJCOMM2010
                        Restore Set Information
Restoring data to \\STJCOMM2010\Microsoft Information Store\Mailbox Database 1833558609¿isdirect.

Storage Media #1: " Media created 1/27/2013 1:00:08 AM "
Backup performed on 1/27/2013 at 1:01 AM
Backup set #1: " stjcomm.stjnet.local Backup 00219-Full "

Restore started on 1/28/2013 at 12:01:22 PM.
Restore completed on 1/28/2013 at 12:01:45 PM.
Restore Set Summary
Restored 0 Exchange Server stores
Processed 40,463 bytes in  23 seconds.
Throughput rate: 0.101 MB/min

      Job Completion Status
Job ended: Monday, January 28, 2013 at 12:01:45 PM
Completed status: Successful
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38828040
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
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In-place Upgrading Dirsync to Azure AD Connect
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question