Move existing Windows Server 2008 R2 (Enterprise) Failover Cluster to a new IP subnet

-

hello,

i have existing 3 node windows server 2008 r2 failover cluster.  the node servers host numerous virtual servers (hyper-v) sql server 2008 r2 failover cluster.

we host cluster in our own in-house "datacenter" have full class c address space.  our in-house "datacenter" has limited redundancy regards power, cooling , internet access so, going move our production cluster full service third party datacenter (colocation).  the third party datacenter providing new class c address space our domain necessitate changing of ip addresses associated our failover cluster.  i looking guidance on how best accomplish change.  i have been researching issue on own , have found following recommend steps:

first, via failover cluster gui, take cluster resources offline (services , applications) , shut down virtual servers.

next, stop cluster service on each of 3 node servers.  once done, physically shut down 3 node servers.

next, move our production rack new datacenter.

once production rack in place in new datacenter, restart 3 node servers.  once servers , running, assign them static ip addresses have on our new class c subnet.

start server running failover cluster interface (which standalone server not part of cluster) , assign new static ip address on new subnet it.  after done, start failover cluster gui on server.

the cluster service on each of node servers should see new ip subnet servers on , automatically create new cluster network , bring online.  

once new cluster network object , running, can start each virtual server , assign static ip address have on new subnet.  next, assign new ip addresses each “service , application” (which objects associated sql cluster) on new subnet.

finally, assign new ip address new subnet actual failover cluster object (the fqdn failover cluster).

do above steps sound correct?  if not, best steps accomplish move?  hoping there others out there have had move failover cluster new ip subnet can offer guidance , roadmap on how best accomplish this.  thanks!

hi,

similar questions have been discussed before; may refer these articles:

moving cluster network segment
http://social.technet.microsoft.com/forums/en-us/winserverclustering/thread/28165ecd-22e8-463d-95e3-bc10dd843f20

1.take cluster resources offline

in failover cluster management, right click each of 4 resources , select take service or application offline
wait resources being offline.

2.shut down cluster service on both nodes

in failover cluster management, right click cluster node , select more actions. click on shutdown cluster
wait cluster services being shut down.

3.shut down windows on both physical nodes

4.physically move cluster , storage new data center

5.startup both cluster nodes , verify physical nics on public network got new ip address (dhcp)

start network connections in control panel , verify correct ip addresses has been assigned.
start failover cluster management console , verify if network online. if not, shutdown , restart cluster service using shutdown cluster function.

6.configure new cluster virtual ip address on node 1

start failover cluster management console, open cluster core resources, expand cluster name container, right click ip address entry , select properties.
change static address entry new virtual ip address of cluster.

7.verify cluster core resources on node 2

start failover cluster management on node 2. open cluster core resource , verify node see correct virtual cluster ip.

8.verify cluster storage (node 1)

in failover cluster management open storage container , verify disks online.

9.configure ip addresses of cluster resources

click on service entry in services , applications
expand the  name entry. right click on ip address , click properties. change static ip address of resource new virtual ip address. verify correct network displayed.
right click on service entry , select bring service or application online

10.verify cluster resources node 2

start failover cluster management on node 2. verify cluster resources

for more information please refer following ms articles:

how to: change ip address of sql server failover cluster
http://technet.microsoft.com/en-us/library/ms190460(v=sql.100).aspx
changing ip address of network adapters in cluster server
http://support.microsoft.com/kb/230356
how change network ip addresses of sql server failover cluster instances
http://support.microsoft.com/kb/244980

lawrence

technet community support




Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

CRL Revocation always failed

-
hi all, i try configure radius server nps, somehow certificate authentication client failed with reason: reason = revocation function unable check revocation because revocation server offline. then check certificate client, certutil -f -urlfetch -verify client7.cer, result follow: issuer:     cn=entca     dc=intra     dc=domain     dc=co     dc=sg subject:     cn=computer.intra.domain.co.sg cert serial number: 1c5b00de000000000041 dwflags = ca_verify_flags_allow_untrusted_root (0x1) dwflags = ca_verify_flags_ignore_offline (0x2) dwflags = ca_verify_flags_full_chain_revocation (0x8) dwflags = ca_verify_flags_console_trace (0x20000000) dwflags = ca_verify_flags_dump_chain (0x40000000) chainflags = cert_chain_revocation_check_chain (0x20000000) hcce_local_machine cert_chain_policy_base -------- cert_chain_context -------- chaincontext.dwinfostatus = ce...
Read more

Failed to query the results of bpa xpath

-
Image
i have new server installed hyper v, iis , domain services roles on it.  i checking event log , see warning multiple times, idea how rid of it?? failed query results of bpa xpath: microsoft/windows/fileservices:$reports$\*\result.xml:/resultdatabase/result. error: device attached system not functioning., last error: system cannot find path specified.. follow me on twitter <<< levalencia blog <<< hi, similar issue discussed in forum: to rid of warnings: 1. go dashboard 2. click on add roles , features 3. click next "before begin step" 4. select "role based or feature based installation" , click next 5. select given server server pool , click next 6. in server roles step make sure following checked:   file , storage services > file , iscsi services > file server, click next 7.click next through rest of steps , install server role 8. rerun bpa scan described earlier for more information please refer foll...
Read more

0x300000d errors in Microsoft Remote Desktop client

-
we use rd connect home users office. @ server side remote desktop gateway configured on 2008r2 server. experience following:   for years worked fine, starting last year users apple macbook experienced connection errors after new version of microsoft remote desktop in app store , automatic update. after couple of weeks error disappaered when new updates released. since 6 8 weeks problem again. because don’t have macbook cannot reproduce problem.   starting couple of weeks samsung s6 experiencing problems, here version 8.1.37.135 installed, error displayed is: can’t connect tot remote pc because remote desktop gateway server temporaraily unavailable. try connecting later or contact network administrator assistance. error code  0x300000d   because has worked fine years expect issues on client can configuration error on gateway server.   who pin point real cause?   however, testing other rd gateway server works ok settings identically....
Read more