E2K7 Migrating Mailbox to E2K13 and move back to E2K7

I found only one post where someone was having an issue moving an E2K7 mailbox back from an E2K13 move

My Migration log has the following as to why the mailbox will not move back to E2K7:

2015-04-20T15:56:57.348Z,41,New-MigrationBatch,Information,",,",Creating a new attachment with name Errors.csv
2015-04-20T15:56:57.535Z,41,New-MigrationBatch,Information,",,",Saved attachment with id EABHtR0Afgf4RL7kRG3HZUp9

I have searched for both errors.csv and the saved attachment with the avoe ID and I cannot find these files.

Can someone please help me out.

many thanks

April 20th, 2015 12:20pm

Hi,

How many mailboxes you want to move back?

If just a few, I recommend you try to move each mailbox individually via EMS on exchange 2013 server.

Best regards,

Free Windows Admin Tool Kit Click here and download it now
April 20th, 2015 10:25pm

If you are trying to migrate from Exchange 007 to 2013, what problem you faces ?

You may follow the instruction given above.

Exchange server deployment assistant would also be a good approach that is available from Microsoft team and provides step-wise instructions by covering all the required prerequisites to accomplish this job. Here you go : https://technet.microsoft.com/en-us/office/dn756393.aspx

Moreover, if you wish to achieve the migration task automatically, this automated solution (http://www.exchangemigrationtool.com/) could also be a nice alternative approach for you.

April 21st, 2015 3:01am

Hi,

Moving of mailboxes in Exchange 2013 is different than the earlier versions of Exchange as it run under Migration Batches and a name must be supplied for the same.

So in your case if you want to move any mailbox which already moved to Exchange 2013 from earlier versions of Exchange, then first you have to check that particular users migration status and run the re-move command as shown below in Exchange Management Shell. hope this will help you.

To move a mailbox:
New-MoveRequest -Identity 'test@domain.com' -BadItemLimit '100' -TargetDatabase "databasename"

To check the moving status(Completed or Failed and percentComplete):
Get-MoveRequestStatistics Identity test@saudioger.com

To re-move again to another database:
1-    Remove-MoveRequest -Identity 'test@domain.com'
2-    New-MoveRequest -Identity 'test@domain.com' -BadItemLimit '100' -TargetDatabase "databasename"

Thanks & Regards,

MB Shaikh.

  • Marked as answer by -eee 15 hours 23 minutes ago
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2015 3:51am

MB Shaikh

When I did a Remove-MoveRequest -identity 'test@domain.com' it actually moved the mailbox back to E2K7 DB where it previsouly resided

I did not realize this until I then did 2- and it PS returned when an item can't be read from the source database or it can't be written to the destination database and it pointed to the -baditemlimit

With all my migrations, I just want to insure if I have to I can move the mailbox back in case there is an issue. Users are unforgiving and do not want any issues after a mailbox move.  

My install of 2013 is very good and I have followed every technote I could find to insure but you never know.

Many thanks

April 21st, 2015 12:05pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics