Hyper-v Cluster and new AD organisation.


hello everyone.

have very bad situation.

in 1 of our new customers following configuraion.

organisations ad corrupted , lost 

there hyper-v nodes winsrv2012 in failover cluster hosted on  8x hp c7000 blade system

there hp p2000 datastore 49.5 tb full size. 

there isn't vmm (please don't ask me "why"

2 csv volumes pesented cluster (i suppose via failover cluster services)

, worst thing don't have backups. suppose previous local administrators irresponsible.



so have following behavior of system

don't able move virtual machines between nodes manually.
datastore full. cannot create  new lun because disks used.
there many critical vm's couldn't stopped long time.

have new ad can not rejoin nodes new domain because node contain critical machines , told can not move ones node well. cannot because in case moved node deleted failover cluster in case can damage csv volumes.
can turn off each vm little time. 

have question. best solution in situation. can use migrate hyper-v infrastructure new ad keep part vhd's in place.

sorry en. , thank in advance.



ouch, horrible situation.

my advice you

1. connect new hyper-v host new domain (you can disconnect 1 old cluster, format , connect new domain).

2. configure new cluster, can performed 1 node.

3. copy vm's old cluster new cluster. going need work out way have enough free space perfrom this. try using local disk space free lun assign lun new cluster. continue copying untill lun free's , on.

4. after vm's copied , imported new hyper-v can format second cluster node , join new cluster.

5. going have re-join every vm manually new domain.

hope gives insight on solution problem.

good luck!


gil gross | technical lead | g-net network solutions | www.g-net.co.il | plz visit blog - gilgrossblog.wordpress.com



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL