Log Shipping In Exchange 2010 DAG…

by Rajith Jose Enchiparambil on January 25, 2010

In Exchange 2010 DAG, the asynchronous replication no longer uses SMB like it used to be in 2007. Exchange 2007 uses Server Message Blocks (SMB) for log shipping and port 445 has to be opened across datacentres if you have multi-site CCRs or SCRs.

Exchange 2010 uses TCP/IP for copying of log files and seeding. The DAG uses 64327 port for replication by default, but you can change the port. Check my previous article on how to change the replication port used by the DAG.

SUBSCRIBE FOR DAILY ARTICLE UPDATES VIA EMAIL

Get the published articles delivered straight to your inbox. Your details will not be passed to any third party company.

Rajith Jose Enchiparambil

Exchange Architect, Blogger, Husband & Dad. I have been in IT for the last 11 years, with Exchange Server becoming the prime area in the last few years. I am active on TechNet forums & Experts Exchange.

View all contributions by Rajith Jose Enchiparambil

Exchange 2013 Server Roles Calculator Moves To Version 5.6

Exchange Team has updated the calculator for Exchange 2013 & 2010. The 2013 calculator v5.1 was only released 10 days ago and the team has been quick to fix the issues & the latest version is 5.6 Fixes in v5.6 are the following. Optimized Volume Design Architecture Formula. Fixed Recommended Min Number of GC Cores [...]
Read More
Using Get-SetupLog.ps1 To Analyze Setup Logs In Exchange 2013

A handy script for analyzing Exchange setup logs, Get-SetupLogs.ps1 has not been shipped with Exchange 2013. This excellent script parses through the setup log file in C:\ExchangeSetupLogs folder and displays an easy to read output in the shell with different colours for warnings and error. This has been around since Exchange 2007, but is missing [...]
Read More
The Migration Mailbox For The Organization Is Either Missing Or Invalid Error During Exchange 2013 Mailbox Move

You get the following error while trying to move mailbox locally in Exchange 2013. The Migration mailbox for the organization is either missing or invalid. I was contacted about this error by one of my blog readers after posting Cannot Open Microsoft System Attendant Mailbox Error During Exchange 2013 Mailbox Move. In this case, the [...]
Read More
Cannot Open Microsoft System Attendant Mailbox Error During Exchange 2013 Mailbox Move

A local mailbox move in Exchange 2013 fails with the error that the System Attendant Mailbox cannot be opened. I thought System Attendant was a thing of the past! Exchange 2013 doesn’t have system attendant mailbox or even the System Attendant service (mad.exe). But, the error clearly mentions about the failure to open the [...]
Read More
How To Find Which Store Worker Process Is Responsible For A Mailbox Database In Exchange 2013

Exchange 2013 has a new store named the Managed Store. In order to provide failure isolation in the database level in 2013, Microsoft has introduced two new processes as part of the managed store concept. First is the Store Worker Process(Microsoft.Exchange.Store.Worker.Exe) which does the same job that store.exe handled in previous versions. The only difference [...]
Read More

1 comment… add one

One IT Ltd - NZ Cloud Hosting January 17, 2011 at 7:40 pm

Great post thanks for the port information.

Reply edit

Log Shipping In Exchange 2010 DAG…

Rajith Jose Enchiparambil

Exchange 2013 Server Roles Calculator Moves To Version 5.6

Using Get-SetupLog.ps1 To Analyze Setup Logs In Exchange 2013

The Migration Mailbox For The Organization Is Either Missing Or Invalid Error During Exchange 2013 Mailbox Move

Cannot Open Microsoft System Attendant Mailbox Error During Exchange 2013 Mailbox Move

How To Find Which Store Worker Process Is Responsible For A Mailbox Database In Exchange 2013

Website Hits

Recent Comments

Archives