asked on

I need to move all Exchange 2013 databases to a new replacement mailbox server.

Production Environment: Exchange 2013, Windows Server 2012; 400 users.

Our original mailbox configuration is proving problematic. We are spinning up a replacement mailbox server to replace it entirely with.

What is the best option to do this and where can I find step-by-step instructions? Is creating a DAG with new mailbox server, creating a database copy on new mailbox server, then removing old mailbox server and removing DAG the way? Or just moving mailboxes? If this is the case, do we have to re-link mailboxes? I've looked for some time before asking this question. I couldn't find anything that gave me the confidence to pull the trigger yet. This is a new Exchange setup and I don't quite trust it or myself to make the decision on my own.

ASKER CERTIFIED SOLUTION

Hardik Desai

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Amit Kumar

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

FrankU09

ASKER

Thanks for your answers. The problematic part is only the HDD size and HA of the VM storage partitions. We are increasing the size of the mailbox volume and using HA storage instead of standard.

If I move the mailboxes, do I have to do any type of re-linking or anything else that would prevent the databases/mailboxes from being not reachable?

Hardik Desai

move mailboxes would be transparent to users. users would be able to work with their mailbox while the mailbox is in transit.

Amit Kumar

If you have less space, then enable Circular logging so your drive will not be filled up with logs.