Disk Remove from 2008R2 Failover Cluster

I have a two node Windows 2008 R2 Failover Cluster with only the File Services Role. There are multiple disks on this server, presented by an EMC storage array via FC. I would like to remove one disk that is no longer in use. The disk is currently in available
storage in the cluster and is in an offline state. The dependency report for the disk shows no required dependencies, no 'AND' relationship, no child resources, and no 'OR' relationship.
When I attempt to remove the disk from available storage I receive the warning "This resource has other resources which depend on it. Deleting it will cause those resource to go offline. Are you sure you want to delete Cluster Disk #?"
How can I determine what resources are dependent upon this disk when the report shows no dependencies? And, since the disk is in an offline state and in available storage, if there are dependencies how are they not in a failed or offline state as well?

Hi,
If the disk resource is offline for some time and you make sure it’s no longer in use. You may remove the disk resource in cluster. You may try below command:
Launch command prompt with elevated privilege.
cluster resource
>> Display the status of a cluster resource
cluster resource “resource name” /listdep
>> list the dependencies for a resource
cluster resource “resource name” /fail
>> initiate resource failure
cluster resource “resource name” /delete
>> delete a resource
Try above command and give us feedback for further tourbleshooting.
For more information please refer to following MS articles:
Cluster resource
http://technet.microsoft.com/en-us/library/cc785087(v=WS.10).aspx
MS Cluster Server Troubleshooting and Maintenance
http://technet.microsoft.com/en-us/library/cc723248.aspx
Adding Disk to Cluster
http://blogs.msdn.com/b/clustering/archive/2008/03/19/8324538.aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

Similar Messages

Windows 2008R2 Failover Cluster node

I am new to this company and have been asked to take over a task that the previous employee left unfinished. I am "familiar" with Failover clustering but have not done any recently. It looks like the previous employee evicted one
of the 2 node cluster servers to replace the hardware. I've setup the new hardware with Failover cluster but now need to setup the iSCSI volumes on this new node. I have not done this before. All I've done before was create NEW failover
disks and those were Fibre Channel disks. Can anyone give me advice or a link to a tutorial to setup these existing iSCSI volumes on the second node? One more note: the iSCSI volumes are on a Dell EqualLogic system and I've never worked
on EqualLogic before either.

Hi,
If I doesn’t misunderstand it seems you are finding how to setup the fiber channel storage to the node, you can refer your hardware manual to setup the hardware connection,
or call your hardware vendor for the more help, you can refer the following support scenario to configure your fiber channel storage:
The Cluster service allows you to reconnect or replace a cable between the HBA and the switch, and then allows for the node to take ownership of the physical disk resource.
The HBA driver must consider several issues for a Plug and Play rescan to occur. The HBA miniport driver must issue a "BusChangeDetected" notification when the cable is reconnected (an HBA port driver issues an "IoInvalidateDeviceRelations" notification) so
that Windows is notified that a change has been made to the shared bus.
The related KB:
Removing the HBA cable on a server cluster
http://support.microsoft.com/kb/294173/en-us
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Transactional replication from a failover cluster instance to a SQL Server Express DB

Hello,
I have been poking around on Google trying to understand if there are any gotchas in configuring transactional replication on a instance DB of a failover cluster, to a SQL Server Express DB. Also, this client would like to replicate a set of tables between
two instances DB's which both reside on nodes of the cluster.
Everything I've read suggests there is no problem using transactional replication on clustered instance as long as you use a shared snapshot folder. I still have some concerns:
1) Should the distributor need to live on a separate instance?
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber.
There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Thanks in advance.

1) Should the distributor need to live on a separate instance?
Answer: It is recommended to configure the distributor on the different server, but it also be configured on Publisher/subscriber server. (Subscriber in our case is not possible as its a Express edition)
2) What happens in the event of an automatic, or manual failover of a publisher, especially if the distributor does not need to live on a separate instance? I know that when a failover occurs, all jobs in progress are stopped and this seems like a recipe for
inconsistency between the publisher and subscriber. There is a paramount concern, that this particular client won't have staff on hand to troubleshoot replication if there are problems, hence my hesitancy to implement a solution that relies on it.
Answer: If you configure both publisher and distributor on the same server and the SQL instance is failed over, the data synchronization/replication is suspended till the instance comes online.
Once the instance is up,all the replication jobs will start again and it will continue to synchronize the data to subscriber. No manual intervention is required.

"Services and Applications" is missing from the Failover cluster manager menu

Hi,
I am not sure this is the right group for my question, but I couldn't find anything else more suitable.
In my Hyper-V installation (Windows 2012 Data Center), I am missing "Services and Applications". I am using Windows 8 to manage the cluster and I need this menu to import an existing VM into the cluster. How can I get this option or is there a
software that I need to install?
Thanks

Repost here: http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/threads
in the Hyper-V forum. You'll get a lot more help there.
This forum is for Virtual Server 2005.

In a Sharepoint 2013 Server farm how far away can the backup of failover cluster servers be located away from the primary servers

Hello Community
    When you setup a Sharepoint 2013 Server farm
if you want to provide failover clustering, can
the servers that the Sharepoint 2013 Server farm
failover to be located off-site in a different
location (i.e. how far away can the servers the
the primary server in the Sharepoint 2013 Server
farm be away from the failover cluster of backup
Sharepoint 2013 Server farm servers in distance?
    Thank you
    Shabeaut

Hiya,
this article describes in detail the different aspects of creating a highly available SharePoint 2013 server farm.
Create a high availability architecture and strategy for SharePoint 2013
http://technet.microsoft.com/en-us/library/cc748824%28v=office.15%29.aspx

Failover Cluster Network Name Failed and Can't be Repaired

I have an issue that seem to be a different problem than any others have encountered.
I've scoured everything I can find and nothing has fixed my problem.
The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster. The computer object was still in AD and appeared to be fine so it was not the common problem of the object
getting deleted somehow. At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
Since it was in the failed state, I tried to do the repair on the object to no avail.
We run a "locked down" DC environment so all computer objects have to be pre-provisioned. They were all pre-provisioned successfully and successfully assigned during cluster creation. The cluster was running with no issues for a month
or so before this problem came up.
When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
I believe this is what is causing the repair failure. All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain. I can't seem to find
a way to do this with the cluster network name. If there's a way please let me know.
I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster? I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
Any help would be appreciated

Hi,
I don’t find out the similar issue with yours, base on my experience, the 4096 error
often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started. I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
repetitive, could you explain further?
The cluster validates successfully with a few warnings:
Validating cluster resource Name: DT-FileCluster.
This resource is marked with a state of 'Failed' instead of
'Online'. This failed state indicates that the resource had a problem either
coming online or had a failure while it was online. The event logs and cluster
logs may have information that is helpful in identifying the cause of the
failure.
- This is because the cluster name is in the failed state
Validating the service principal names for Name:
DT-FileCluster.
The network name Name: DT-FileCluster does not have a valid
value for the read-only property 'ObjectGUID'. To validate the service principal
name the read-only private property 'ObjectGuid' must have a valid value. To
correct this issue make sure that the network name has been brought online at
least once. If this does not correct this issue you will need to delete the
network name and re-create it.
- This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
The user running validate, does not have permissions to create
computer objects in the 'ad.unlv.edu' domain.
- This is correct, we run a restricted domain. I have a delegated OU that I can pre-provision accounts in. The account was pro-provisioned successfully and was at one point setup and working just fine.
There are no other errors nor warnings.

Failover cluster for BizTalk 2010

Hi friends,
I need to understand step by step configuration for failover for biztalk 2010.
use of failover cluster manager from windows os and how its working from biztalk.
Please do share with me the right url.
Thanks all.

Similar question was asked recently in our forum:
http://social.msdn.microsoft.com/Forums/en-US/18239da7-74f2-45a7-b984-15f1b3f27535/biztalk-clustering?forum=biztalkgeneral#4074a082-8459-420f-8e99-8bab19c8fba2
White paper from Microsoft on this context shall you with step-by-step guidance of failover cluster for BizTalk 2010.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=2290
Also refer this blog where authors in series of his post guides with the steps required:
Part 1: BizTalk High Availability Server Environment – Preparations
Part 2: BizTalk High Availability Server Environment–Domain Controller Installation
Part 3: BizTalk High Availability Server Environment – SQL & BizTalk Active Directory Accounts
Part 4: BizTalk High Availability Server Environment – Prepping our SQL & BizTalk Failover Clusters
Part 5: BizTalk High Availability Server Environment – SQL Server 2008r2 Failover Cluster
Part 6: BizTalk High Availability Server Environment–BizTalk 2010 Failover Cluster Creation
Part 7 – BizTalk High Availability Server Environment –BizTalk 2010 Installation, Configuration
and Clustering
Par 8 - Adding Network Load balancing to our High Availability Environment
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Cold failover cluster for repository ?

Hi,
We have Box A (infra and mid) and B(mid),
we want to use Box B for cold failover claster
Any suggestion on how to do this?
TIA

Similar question was asked recently in our forum:
http://social.msdn.microsoft.com/Forums/en-US/18239da7-74f2-45a7-b984-15f1b3f27535/biztalk-clustering?forum=biztalkgeneral#4074a082-8459-420f-8e99-8bab19c8fba2
White paper from Microsoft on this context shall you with step-by-step guidance of failover cluster for BizTalk 2010.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=2290
Also refer this blog where authors in series of his post guides with the steps required:
Part 1: BizTalk High Availability Server Environment – Preparations
Part 2: BizTalk High Availability Server Environment–Domain Controller Installation
Part 3: BizTalk High Availability Server Environment – SQL & BizTalk Active Directory Accounts
Part 4: BizTalk High Availability Server Environment – Prepping our SQL & BizTalk Failover Clusters
Part 5: BizTalk High Availability Server Environment – SQL Server 2008r2 Failover Cluster
Part 6: BizTalk High Availability Server Environment–BizTalk 2010 Failover Cluster Creation
Part 7 – BizTalk High Availability Server Environment –BizTalk 2010 Installation, Configuration
and Clustering
Par 8 - Adding Network Load balancing to our High Availability Environment
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

DFS-R folder resources Failed in Failover Cluster on Server 2008 R2

Maybe a week ago, 7 of our DFS-R Folder failover cluster resources lost their configuration data. In the resource list, they just show up as "()".
I've seen suggestions online that disabling the replicated folder will remove it from the Failover Cluster, and then re-enabling it will automatically add it back to the cluster. So, I've disabled it via the Connections tab, and that does nothing. The other
option is to disable it under the Memberships tab...but that has consequences, and I would rather not do that if it isn't necessary.
I'm also now seeing event ID 5012's popping up in the DFS Replication logs every hour or so.
The DFS Replication service failed to communicate with partner etc etc. The partner did not recognize the connection or the
replication group configuration.
Error: 9026 (The connection is invalid)
Now, "dfsrdiag pollad /verbose" or "dfsrdiag pollad /mem:<dc name>" both come back as successful. And a DFS Diagnostic Report brings back nothing apparently relevant to this issue, other than one error concerning the same event
ID 5012's.
Also, I've verified that it's not a DNS issue, pinging the home office DFS server from the site server resolves correctly, and vice versa. And the windows firewall is disabled on both servers. It's POSSIBLE that there is a network issue. Replication works
fine between the site server and the 2nd cluster server service, just not between the site server and the 1st cluster server service. However, via netstat I see active connections between the site server and the cluster server, as well as the active cluster
host (although, just a single connection to the clustered DFS server, but ~6 to the cluster host itself).
So, I'm completely at a loss here. Any recommendations?

Hi,
This error usually occurs when one partner attempts to establish an RPC connection with another member, but is unable to.
You could refer to the thread below to troubleshoot the issue:
DFSR Event ID 5012 when other DFS folder working
https://social.technet.microsoft.com/Forums/en-US/9748cb08-858d-454e-93cd-233c98cb2ee8/dfsr-event-id-5012-when-other-dfs-folder-working?forum=winserverfiles
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2. I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster. After upgrading the cluster I am unable to migrate some VMs from one node to another. When trying to do
a live migration, I get the following notifications under the Rating Explanation tab:
Warning: There currently are not network adapters with network optimization available on host Node7.
Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue.
I get this error for 3 out of the 4 nodes in the cluster. I do not get this error for Node10 and I can live migrate to that node in VMM. It has a green check for Network optimization. The others do not. These errors only affect
VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues. In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to. I've checked the network
adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM. I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
queue" and Enable IPsec task offloading" checked. I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1. Why is this an issue now but it wasn't before
running on the new cluster? How do I resolve the issue? VMM is useless if I can't migrate all my VMs with it.

I checked the settings on the physical nics on each node and here is what I found:
Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading". I unchecked those
2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
It seems to me that if I could adjust those VM settings from VMM that it might fix the problem. Why isn't that an option to do so in VMM?
Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager? That would be a lot of unnecessary work but I don't know what else to do at this point.

LUN can't be accessed after move it to another Hyper-V Failover Cluster without "remove from cluster shared volumes" on the original cluster

Hi all,
I have a old cluster, let's call it cluster01, and a new cluster, cluster02. There is a LUN attach to cluster01 as a CSV volume. I forgot to "remove from cluster shared volumes" in Failover Cluster console, then power off the cluster01 and
attach the LUN to the cluster02. Now the LUN can't be accessed in cluster02, it show as a RAW disk. I tried to attach the LUN to it's original cluster cluster01 but can't read it too.
Is there any way to get it back?

Hi Zephyrhu,
Can you run Clear-ClusterDiskReservation powershell cmdlet and see that helps?
http://technet.microsoft.com/en-us/library/ee461016(WS.10).aspx
Thanks,
Umesh.S.K

Removal of Node from Hyper-V Failover Cluster

Hello All....................I have a 8 node Hyper-V Failover Cluster based on Windows Server 2012 R2. I am facing some issues with one of the servers, so I have decided to take that node out of the Hyper-V Failover cluster. I would appreciate if someone
could share the steps that I should take to ensure smooth removal of node especially with respect to CSV Volume and Quorum. THanks.

Hi Sir ,
Please try the following command (before you do this please live migrate VMs to another nodes ):
Remove-ClusterNode –Name node4 -Force
For this command please refer to :
http://technet.microsoft.com/en-us/library/hh847251.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to recover from accidental VM role removal in Hyper-V Failover Cluster Manager?

Hello
My VMs are still available in Hyper-V Manager but they are no longer available in Cluster Manager. I am curious if there's a way to move them back into the Failover Cluster Manager while retaining their GUIDs?
I know I can manually create a new VM and add the existing VHD but that process recreates a new GUID causing the VM to regard the stuff I wanted as old.
I have tried to follow
http://blogs.technet.com/b/heyscriptingguy/archive/2013/10/14/recovering-virtual-machines-in-hyper-v-server-2012-r2-part-1.aspx but I am curious if there's a faster way to do this without becoming a scripting genius overnight.
Thanks,
Prince

Thanks for the reply but that does not help.
I am not looking to move my VMs to a remote Host but rather looking to repopulate the fail-over cluster manager with the existing VMs in Hyper-V Manager. In a sense, I am looking to reuse the existing GUID without creating new ones.
Again, my VMs are alive in Hyper-V Manager but are currently not available in Failover Cluster Manager.
Any scripting assistance will be greatly appreciated.
Thanks,
Prince

2008R2 to 2012R2 = Failover Cluster Manager not found ..gray out feature.

Hello everyone,
I just upgraded from our Hyper-V host running Windows Server 2008R2 to 2012R2,
I didn't get any errors during the upgrade and everything looked fine except that the failover cluster manager is no longer exist ..I went to add it from the server manager and found that the feature already exist but it is grayed out, I can not remove it and
add it again!
how to get the failover manager cluster working again ?
Thanks
Misbah

ok, the fix seems simple,
I needed to go from server manager and select remove role/features and then re-add it.
going to add roles/feature will not allow me to remove any feature ..it is just for adding features.

VM will not boot after moving using Failover Cluster Manager - "a disk read error occurred......"

My current Configuration:
3 node cluster, using clustered shared storage and about 22 VM's.   The Host servers are running 2012 Data Center while all guest are running 2012 Standard. The SAN is EqualLogic and we are using HIT Kit 4.5.
I have a CSV that is running out of space, so I created another CSV so that I could move some of the VM's to a new home.    I tested this by creating a test VM, and moved it successfully 3 times.     I then moved an actual
LIVE VM and while it seemed to move ok, it will now not start.   The message is "a disk read error occurred Press ctrl+alt+del to restart".     I moved the test VM and it failed as well.
I have read several things about this, but nothing seems to relate to my specific issue.   I have verified that VSS is working and free of errors as well.    From the Settings menu for the VM, if I select "Inspect" the drive,
the properties all look fine.    It is a VHDX and both the current file size and maximum disk size seem correct.
The VM's were moved using the "move - virtual machine storage" option within Failover Cluster Manager.
Suggestions?
Thanks.

Lets see if I can answer all of those and I appreciate the brain storming.   This really needs to work, correctly.
1. The Storage is moving.
2.   VM's and SAN are on same device.
3. No, my Clustered Shared Volume, CSV, is out of room, (more one that later)
4. No, I actually have 2 sans grouped together.   However, I'm moving the VM', form one CSV to another CSV on the Same san. EqualLogic PS 6110 is the one I am trying to move VMS around on, and the other SAN not involved in any way except
for it is in a SAN group is an EqualLogic PS6010.
5. No error During move, it took about 5-10 minutes, no error messages.   Note, I did a test and it worked GREAT 3 times.   Now both a live VM, and the test VM are doing the same thing.
6. No, the machine is not to large.   The test making was a 50 gig drive, just 2012 standard installed with updates.   The live VM was a 75 gig VM that was my Trend Micro Server, or anti-virus host.
7. Expand the existing SCV?   Yes I should be able to, but there is an issue there.   The volume was expanded correctly, Equallogic sees the added space, Fail Over cluster manager sees the added space, however disk manager only
sort of does.    When looking at disk manager, there are 2 areas that tell you a little bit about the drive.   The top part and then the bottom part.   The top part only shows 500G, the original size, while the bottom part
says that it is 1 TB in size.   I call Dell's technical support and after they looked at it I was told by the technician that they had seen this a couple of times and the only way to fix it was to move all the VM's to another CSV and delete the troubled
CSV.   I thought about adding more space to the troubled CSV, but its on a production server with about 12 VM's running on it and I did not want to take a chance.   The Trend VM was running on CSV-1 and working fine.
I must admit that the test VM, was on CSV-2.    I moved the Test VM from csv-2 to csv-3 back and forth several times with no errors.   The Trend Server was on CSV-1 and was moved to CSV-3, however it failed. Again, I then moved
the test VM from CSV-2 to CSV-3 and it failed the same way.   I could not test the "TEST - VM" on csv-1 due to csv-1 not having enough space.
8.   I did disable the network from the VM to see if that mattered it did not.
9.   I have not yet had a chance to connect the VHDX to a new VM, but I will do that in about an hour, hopefully.    Once I am able to test that suggestion I will post the results as well.
Again, thanks for all the suggestions and comments, as I had rather have lots to look at and try.   I hope I answered them well enough.
Kenny

Disk Remove from 2008R2 Failover Cluster

Similar Messages

Maybe you are looking for