Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Exchange 2016 remote disaster recovery Series-Exchange deployment (5)

2025-01-17 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/03 Report--

Before I could write this blog, the test environment was over, so I had to find other relevant pictures to update it.

Let's take a look at how to switch Exchange to the disaster recovery site after a catastrophic accident at the main site.

I. Environment information server name operating system IP address gateway DNS role BJAD01windows server 2012 R210.1.110.1.1.1010.1.1.1 Beijing domain control 01BJEX01windows server 2012 R210.1.210.1.1.1010.1.1.1 Beijing Exchange01BJEX02windows server 2012 R210.1.1.1010.1.1.1 Beijing Exchange02SHAD01windows server 2012 R2172.16.1.172.1.1010.1.1.1 Shanghai Control 01SHEX01windows server 2012 R2172.16.1.2172.16.1.10172.16.1.1 Shanghai Exchange01SHEX02windows server 2012 R2172.16.3172.16.1.10172.16.1.1 Shanghai Exchange02Routerwindows server 2012 R210.1.10 172.16.1.10\ Router 2, Disaster failover 1. All Exchange servers at the main site failed

At this time, in the SH site server, the Exchange server of the PING Beijing site can no longer communicate with ping.

two。 Mark the primary site mailbox server as STOP

Open Exchange powershell in any Exchange server server on the Shanghai site and execute

Stop-DatabaseAvailabilityGroup-Identity "DAG01"-ActiveDirectorySite "Default-First-Site-Name"-ConfigurationOnly:$true

Check the DAG server status. At this time, the Beijing site server status should be STOP, and the Shanghai site server status should be Start. Enter the following command:

Get-DatabaseAvailabilityGroup-Identity "DAG01" | FL name,start*,stop*

Stop the Cluster service on the mailbox server of the Shanghai site

Activate the Shanghai site disaster recovery Center and enter the command in Exchange powershell:

Restore-DatabaseAvailabilityGroup-Identity "DAG01"-ActiveDirectorySite "SH"

Execute the command to load the database from the Shanghai disaster recovery site

Move-ActiveMailboxDatabase EDB01-ActivateOnServer SHEX01-MountDialOverride:None-SkipClientExperienceChecks-SkipHealthChecks-SkipLagChecksMove-ActiveMailboxDatabase EDB02-ActivateOnServer SHEX01-MountDialOverride:None-SkipClientExperienceChecks-SkipHealthChecks-SkipLagChecksMove-ActiveMailboxDatabase EDB03-ActivateOnServer SHEX02-MountDialOverride:None-SkipClientExperienceChecks-SkipHealthChecks-SkipLagChecks

Check whether all databases have been loaded in the Shanghai disaster recovery site environment and confirm that the mail service is normal.

Modify A record on the intranet DNS server, mail.rrclouds.cn record to 172.16.1.2

Autodiscover.rrclouds.cn recorded to 172.16.1.2

Test mailbox function

3. Restore the function of Beijing main site

After the server failure at the Beijing site is resolved, observe whether the following conditions are met:

All Exchange services of the main site server are running normally

Whether the domain controller, witness directory, storage, and network are all back to normal

If these conditions are met, follow these steps to switch the database back to the Beijing main site to run.

Execute the command in the Beijing main site to merge the primary site server into the DAG group:

Start-DatabaseAvailabilityGroup-Identity "DAG01"-ActiveDirectorySite "Default-First-Site-Name"

Check the status of the DAG server. At this time, both the main site and the disaster recovery site server are Start, execute the command:

Get-DatabaseAvailabilityGroup-Identity "DAG-01" | FL name,start*,stop*

Check whether the main site Mailbox server cluster service status is automatic-running one by one, if you do not manually change the service status to automatic-running

Check whether the database synchronization status is normal and whether there is a high replication queue, and execute the command:

Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus

Note: the next step is not recommended when the copy status is abnormal or the queue is high!

Switch the database one by one to the Beijing main site server and execute the command:

Move-ActiveMailboxDatabase EDB01-ActivateOnServer BJEX01-MountDialOverride:None-SkipClientExperienceChecks-SkipHealthChecks-SkipLagChecksMove-ActiveMailboxDatabase EDB02-ActivateOnServer BJEX01-MountDialOverride:None-SkipClientExperienceChecks-SkipHealthChecks-SkipLagChecksMove-ActiveMailboxDatabase EDB03-ActivateOnServer BJEX02-MountDialOverride:None-SkipClientExperienceChecks-SkipHealthChecks-SkipLagChecks

Modify the A record on the intranet DNS server, and mail.rrclouds.cn record to 10.1.1.2

Autodiscover.rrclouds.cn logged to 10.1.1.2

Test mailbox function

The switch is complete.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report