in many large enterprises, in order to avoid the loss of mailbox data and the impact on user use, will establish a cross-site Dags, for example, place MBX1 and MBX2 in the Guangzhou headquarters,Place Disaster recovery server MBX3 in Shenzhen , but in some special cases if the database active copy switches to MBX3 will give the user experience and administrator management a very annoying.
The database switching logic can be referenced below:
Https://technet.microsoft.com/zh-cn/library/dd776123 (v=exchg.150). aspx
Prevent the database copy of the backup site from being automatically activated by configuring an activation policy for the server to restrict the database from switching to the same site only or to prevent the database from switching to a specific database copy.
Server level:
Set-mailboxserver-identity Mbx3-databasecopyautoactivationpolicy Blocked
Set-mailboxserver-identity Mbx2-databasecopyautoactivationpolicy intrasiteonly
Note: The above two methods are consistent, choose one.
Set-mailboxserver-identity Mbx3-databasecopyautoactivationpolicy Unrestricted
2. Database level:
Suspend-mailboxdatabasecopy-identity db1\mbx3-activationonly
Resume-mailboxdatabasecopy-identity db1\mbx2
Note: At the database level and at the server level, you only need to select one item to operate on.
This article is from the "Essence of the" blog, please be sure to keep this source http://simy88.blog.51cto.com/7370552/1684379
Cross-site DAG prevents database active replicas from switching to the backup server