Solved

Destroy Failover cluster Windows 2008 R2

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

[Webinar] Disaster Recovery and Cloud Management

Learn from Unigma and CloudBerry industry veterans which providers are best for certain use cases and how to lower cloud costs, how to grow your Managed Services practice in IaaS clouds, and how to utilize public cloud for Disaster Recovery

Question has a verified solution.

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

The Need In an Active Directory enviroment, the PDC emulator provide time synchronization for the domain. This is important since Active Directory uses Kerberos for authentication.  By default, if the time difference between systems is off by more …
We recently endured a series of broadcast storms that caused our ISP to shut us down for brief periods of time. After going through a multitude of tests, we determined that the issue was related to Intel NIC drivers on some new HP desktop computers …
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

867 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

21 Experts available now in Live!

Get 1:1 Help Now