Solved

Destroy Failover cluster Windows 2008 R2

Posted on 2014-09-25
3
123 Views
Last Modified: 2015-03-05
I have a failover cluster running Windows Server 2008 R2 with an iSCSI target attached directly to the servers.  We are going to move this infrastructure to a virtual environment, but I first need to break/destroy the cluster.  

There are two servers in the cluster.  I would like completely remove the cluster from the network and take the second server offline.  I've found a lot of documentation out there about destroying the cluster, evicting nodes, etc, but can't get a good feeling on the best way to approach this.

The servers have two NIC ports in them.  Port 1 on both servers have static IPs assigned to the Local LAN and are plugged into the switches.  Port 2 on both servers is plugged into a storage server.  These ports have a separate subnet from the LAN and utilize the storage server as an iSCSI target.

My main question and concern is if I choose the option in Failover Cluster Manger to "Destroy Cluster" will that completely remove the cluster AND the iSCSI target containing the data?  Ideally I would like to detroy the cluster and disjoin the second server from the domain.
0
Comment
Question by:jplagens
  • 2
3 Comments
 
LVL 3

Expert Comment

by:TropicalBound
ID: 40345932
It sounds like there is data on the cluster that you need to access during this transition.  Correct?

Move all the cluster resources to one host, making it the active node.  Remove the passive node from the cluster making it a stand alone server.  Prepare the stand alone server for the data that needs to be accessed.  Once the stand alone server is functioning properly, the cluster should no longer be in use and can be destroyed without fear of losing data or production time.
0
 
LVL 4

Author Comment

by:jplagens
ID: 40369342
Sorry for the long delay.  We are only onsite every other week at this location.  When you say "remove the passive node", do you mean to evict the node?

The main server is currently the active node.  The quorum and iSCSI share is sitting on the main server.
0
 
LVL 3

Accepted Solution

by:
TropicalBound earned 500 total points
ID: 40370545
Correct.  Evict the passive node.  This will allow you to make whatever changes are necessary to this server without affecting production.
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Join & Write a Comment

Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

708 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now