<div>
The swing method using move mailbox is the safest method. As already outlined, it doesn't actually delete the source until it is confirmed at the other end. I have had power failures during a move and not lost anything (from the Exchange server anyway). <br />
<br />
By doing a swing you can back out of the operation at any point. If something goes wrong, simply move the mailboxes back. <br />
<br />
Simon.
</div>


The swing method using move mailbox is the safest method. As already outlined, it doesn't actually delete the source until it is confirmed at the other end. I have had power failures during a move and not lost anything (from the Exchange server anyway).

By doing a swing you can back out of the operation at any point. If something goes wrong, simply move the mailboxes back.

Simon.

<div>
<div class="content wysiwyg-content">
I am planning to move user mailboxes from one server to another in the same domain using the AD move mailbox feature. I am running Exchange 2003 on Windows server 2003 std on both servers and plan to decommision the first server if all goes well.<br />
<br />
What is the best disaster recorvery approach to this scenario giving the fact that things may not just work as expected after the move and users run the risk of losing new e-mails after the move is effected.<br />
<br />
I already have an up-to-date &nbsp;backup of the information store on the current server, but i am thinking of a seamless fall back solution with the minimum outage possible if indeed a problem occurs.<br />
<br />
Secondly is the AD move mailbox feature the best approach to this problem?<br />
<br />
Thanks for a quick response.
</div>
</div>


I am planning to move user mailboxes from one server to another in the same domain using the AD move mailbox feature. I am running Exchange 2003 on Windows server 2003 std on both servers and plan to decommision the first server if all goes well.

What is the best disaster recorvery approach to this scenario giving the fact that things may not just work as expected after the move and users run the risk of losing new e-mails after the move is effected.

I already have an up-to-date  backup of the information store on the current server, but i am thinking of a seamless fall back solution with the minimum outage possible if indeed a problem occurs.

Secondly is the AD move mailbox feature the best approach to this problem?

Thanks for a quick response.

Moving mailboxes from one server to another within the same domain

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.