Link to home
Start Free TrialLog in
Avatar of Albert Widjaja
Albert WidjajaFlag for Australia

asked on

Exchange Server 2013 IP-less DAG mailbox migration and replication implication ?

People,

Using IP-less DAG on Exchange Server 2013 Standard edition with just one vNIC on each mailbox VM,

I'd like to know if the mailbox migration from the stand-alone Mailbox to the DAG replicated mailbox can have a significant impact on the email flow during the business hours?

I've got two mailbox server in two different AD sites that I'm about to set as DAG from the existing stand-alone setup, I just need to know what's the steps that I need to do in order to avoid network congestion or email outage when I migrated the mailbox DB from the old mailbox DB into the new mailbox DB that is configured in DAG setup.
ASKER CERTIFIED SOLUTION
Avatar of Amit
Amit
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
Avatar of Albert Widjaja

ASKER

Hi Amit,

So in this case, After hours: Do I need to stop the DAG replication in the new mailbox DB while migrating the mailboxes from the old DB or Can I just leave the DAG-replication running while migrating one mailbox DB at a time?
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
Hi Amit,

why not turn on the circular logging during the migration ?
Hi Amit,

I assume that configuring IP-less DAG during the business hours is not going to cause any outage.
based on this step-by-steps: http://msexchangeguru.com/2014/03/21/e2013sp1-ip-less-dag/
Hi Amit,

I've enabled the circular logging on for all mailbox DBs to prevent the transaction logs growing bigger daily.
so when I create the DAG today, do I need to disable the circular logging or keep it enable during the DAG replication and then turn it off later after fully synchronized.
Thanks !