Jump to content


Failover Cluster Manger - Add HyperV machine (VM) issue

Recommended Posts



I am in need of urgent assistance.


The problem briefly:


A virtual machine that is used for file system crached, let's call it FILESRV01.

FILESRV02 Was created and put into Failover Cluster Manager properly.

FILESRV02 Also crashed and FILESRV02 was recreated.

The old FILESRV02 is still stuck in Failover Cluster Manager

Giving status: Stopped / Failed.

The new FILESRV02 is not in Failover Cluster Manager.


They both point to the same .vhd locations/disks.


What and how can i implement the new FILESRV02 into Failover Cluster Manager?

* What happends if i add the new FILESRV02 while the old is still there?

* I've read that if you try to remove a machine from Failover Cluster Manager it will also try to delete the .VHD (which would be very bad)


This is in production environment and all help is appriciated!


// Sincerely Kimmyel

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...