Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Exchange 2010 DAG shutdown

Posted on 2014-09-12
2
Medium Priority
?
1,179 Views
Last Modified: 2014-09-15
We are moving one of our datacenters to a new facility.  In order to complete the move, we will need to completely shutdown our active messaging system, which is hosted in that site.  I'm trying to verify that I have all the steps needs for successful shutdown and also to bring everything back online.  I've searched around and I'm seeing some mixed feedback on all the steps required to do this.

Environment details:
Primary site has 2 mailbox servers, 2 HUBCAS servers, 2 UM servers, 1 TMG server.  We have 2 databases and this site has HA for the mailbox servers with active and passive copies of each other's database.  One of the HUBCAS servers is the primary File Share Witness.

DR site has one mailbox server, one HUBCAS server, one UM server, one TMG server.  This site is DR only and has only passive copies of the databases in the primary site.  However, we do not want to failover to the DR site for this event.

The steps I'm planning to follow are:


1. Shutdown MB servers by doing the following:
StartDagServerMaintenance.ps1 -Server1
(This script should move all active DB to other DAG member, pause the node in cluster, suspend replication, set DatabaseCopyAutoActivationPolicy to block, and cluster core resource moved to other server in DAG)
Power off the server

StartDagServerMaintenance.ps1 -DR Mailbox Server
(This should prevent the DR server at the other site from becoming the PAM, activating databases, etc.)
Question:  Is this step necessary since this server is in our DR site?

Here is where some additional confusion comes in:
Shutdown the last remaining mailbox server at the primary site
Question:  Before I shut down the final mailbox server, do I need to run the StartDagServerMaintenance.ps1 -Final Mailbox Server script?  Since it is hosting the active databases, PAM, etc. I'm assuming it will fail if I run that script.  I've also seen some recommendations to dismount the databases on the active server at this point.  Other recommendations are to just shut the server down without running any commands.

2. Shutdown disk enclosure for both mailbox servers at primary site

3. Shutdown HUBCAS servers
Shutdown the one serving as the FSW last
Question:  Do I also need to shutdown the HUBCAS server in the DR site since it is the Alternate FSW

4. Shutdown UM servers

5. Shutdown TMG server

6. Shutdown domain controller in the site that is relocating

Move the datacenter.  
When bringing everything back online follow in this order:

Power on Domain controller in the site, then:

1. Power on TMG server

2. Power on HUBCAS servers
Make sure FSW is back online before powering MBX servers back on

3. Power on UM servers

4. Power on disk enclosures for mailbox servers

5. Power on mailbox servers
Run StopDagServerMaintenance.ps1 script for the last mailbox server to be shutdown prior to move
Verify health of the databases

Run StopDagServerMaintenance.ps1 for second mailbox server at primary site and redistribute the databases accordingly

Run StopDagServerMaintenance.ps1 for DR mailbox server at the secondary site

6. Verify that replication has resumed for the database copies on all servers
Test-ReplicationHealth and Get-MailboxDatabaseCopyStatus to verify the DAG health

7. Test all Exchange related services:
Test using microsoft remote connectivity anlayer
Test using microsoft remote connectivity anlayer autodiscover
Test using your script http://exchangeserverpro.com/health-...mailbox-server
Send inbound / outbound emails to verify routing
Also test basic stuff like opening Outlook and booking a meeting with a meeting room, or checking free/busy information for a meeting invitee.
Check the event logs on the servers for any unusual errors



If anyone is able to validate the steps I have listed and also make recommendations on anything I may have overlooked, as well as answer the questions above, I would greatly appreciate it.
0
Comment
Question by:junior049
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 37

Accepted Solution

by:
Jamie McKillop earned 2000 total points
ID: 40322989
Hello,

Put one of the DAG members at the primary site and the DAG member at the secondary site in maintenance mode. Just power down the last DAG member at the primary site.

You do not need to shut down the HAB/CAS in the DR site. The FSW would not active in that site unless you performed a manual failover.

The rest of you steps look good, except you have not addresses IPs and DNS. Will your internal IPs remain the same in the new datacenter? What about your external IPs? If your internal IPs are going to change, you will need to make sure you setup the new subnets for the DAG and change your internal DNS records. If the external IPs are going to change, you need to modify your public DNS records.

-JJ
0
 

Author Comment

by:junior049
ID: 40323535
Thanks for validating and answering my questions.  Yes, the IP addresses, DNS, etc. will all remain the same.  The only thing changing is the physical location of the equipment.
Thanks!
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
how to add IIS SMTP to handle application/Scanner relays into office 365.
Many of my clients call in with monstrous Gmail overloading issues with Outlook. A quick tip is to turn off the All Mail and Important folders from synching. Here is a quick video I made to show you how to turn off these and other folders in Gmail s…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question