Solved

Destroy Failover cluster Windows 2008 R2

Posted on 2014-09-25
3
136 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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

803 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