• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 451
  • Last Modified:

CCR Mailbox server role migration

I need some guidance regarding what should I need to do before and after I migrate the Exchange Server Mailbox and HT-CAS role from one AD site into another one with different IP address (the domain is the same)?

Here’s what I’ve got:

PRODUCTION site

ADDomain.com
Site: HQ-City1

Mailbox Server 1:
PRODMBX1 (Active CCR Node)
Prod network: 192.168.1.115
Heart Beat Network: 10.1.1.1

HT-CAS Servers: PRODHT-CAS1 and PRODHT-CAS2 (Configured as IGMP Multicast cluster)

Into the new production site with different IP addressing class / VLAN but still routable

New PRODUCTION site

ADDomain.com (same)
Site: HQ-City2 (different)

Mailbox Server 1:
PRODMBX1 (Active CCR Node)
Prod network: 10.188.1.115
Heart Beat Network: 10.1.1.1

HT-CAS Servers: PRODHT-CAS1 and PRODHT-CAS2 (Configured as IGMP Multicast cluster), my assumption is that there shouldn’t be any other change apart from the IP addressing at the Windows OS level and the Virtual IP address on the NLB Manager.

There is nothing to touch in the DR / Recovery site below:

Recovery / Disaster Recovery site

ADDomain.com
Site: DR-City1

Mailbox Server 2:
RECOMBX1 (Passive CCR Node)
Prod network: 192.168.2.19
Heart Beat Network: 10.1.1.2

HT-CAS Servers: RECOHT-CAS1 (Configured as standalone)

Is there anything that I need to know apart from following the steps below?

1.      Failover the CCR mailbox to the Recovery site into RECOMBX1.
2.      Change the IP address
3.      Shutdown the Virtual Machine
4.      Make some necessary changes at the Hypervisor level and then storage migrate the VM
5.      Turn on the PRODMBX1 VM

Any kind of help and assistance would be greatly appreciated.

Thanks.
0
Senior IT System Engineer
Asked:
Senior IT System Engineer
  • 3
  • 2
3 Solutions
 
Will SzymkowskiSenior Solution ArchitectCommented:
You will also have to suspend the Stroage Group Copy if you are using Exchange 2007. See link below for further details. Aside from that everything looks good above.

http://technet.microsoft.com/en-us/library/bb124706(EXCHG.80).aspx

Will.
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Cool, i was wondering if I missed some steps in there, it seems that the IP change is straightforward.

And all service should all be resolved with DNS I assume.
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
That is correct. DNS will pick up the new IP's that are assigned to the servers in the environment. This should be automatic.

Will.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hope the DNS is updated properly and also try to restart the Server and check with Webmail\OWA access to ensure connection is there then go a step further

- Rancy
0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Cool, here's the summary then:

Preparation before the Migration day

1.      Failover to DR site by rebooting the current Mailbox server role.
2.      Take note of the entire Exchange Server services state and start-up mode.
3.      Stop and disable all Exchange Server services before the server shutdown.
4.      Shutdown the mailbox server role.
5.      Write down the VM RDM LUN configuration.

During the migration day

1.      Re-attach the RDM LUNs to the Exchange Server mailbox server.
2.      Start the Mailbox server VM.
3.      Verify the disk status in Disk Management Console and then for each of the drive letters.
4.      Change the IP address in the following location:

      DNS server console

      Hosts File

      Static Route for the replication links

5.      Verify the Exchange Server service in the.

0
 
Senior IT System EngineerIT ProfessionalAuthor Commented:
Ok, is there any reason why I need to Stop the CCR replication ? my understanding here is that CCR will take care of itself, and I do not need to worry about the replication.

<preover, DO I need to shutdown / stop both Cluster service to change the IP address ?
http://technet.microsoft.com/en-us/library/aa996336(v=exchg.80).aspx
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now