Hello everyone.
We have a very very bad situation.
In one of our new customers we get the following configuraion.
Organisations AD was corrupted and lost
there are Hyper-v nodes WinSrv2012 in failover cluster hosted on 8x HP c7000 blade system
there is HP P2000 datastore 49.5 Tb full size.
there isn't VMM (please don't ask me "Why"
2 CSV volumes pesented to cluster (i suppose via Failover cluster services)
And the worst thing we actually don't have any backups. I suppose previous local administrators were irresponsible.
So we have the following behavior of system
We don't able to move Virtual machines between nodes even manually.
DAtastore is full. We cannot create new LUN because All disks are used.
There are too many critical VM's which couldn't be stopped for a long time.
I have new AD but i can not rejoin nodes to the new domain because almost all node contain critical machines and as i told i can not move ones to another node as well. Also i cannot do it because in this case moved node will deleted from Failover cluster so in this case i can damage csv volumes.
Actually i can turn off each VM for a little time.
So i have a question. What is the best solution in this situation. can i use for migrate all hyper-v infrastructure to new AD but keep all most part VHD's in place.
Sorry for my EN. And Thank you in advance.
We have a very very bad situation.
In one of our new customers we get the following configuraion.
Organisations AD was corrupted and lost
there are Hyper-v nodes WinSrv2012 in failover cluster hosted on 8x HP c7000 blade system
there is HP P2000 datastore 49.5 Tb full size.
there isn't VMM (please don't ask me "Why"
2 CSV volumes pesented to cluster (i suppose via Failover cluster services)
And the worst thing we actually don't have any backups. I suppose previous local administrators were irresponsible.
So we have the following behavior of system
We don't able to move Virtual machines between nodes even manually.
DAtastore is full. We cannot create new LUN because All disks are used.
There are too many critical VM's which couldn't be stopped for a long time.
I have new AD but i can not rejoin nodes to the new domain because almost all node contain critical machines and as i told i can not move ones to another node as well. Also i cannot do it because in this case moved node will deleted from Failover cluster so in this case i can damage csv volumes.
Actually i can turn off each VM for a little time.
So i have a question. What is the best solution in this situation. can i use for migrate all hyper-v infrastructure to new AD but keep all most part VHD's in place.
Sorry for my EN. And Thank you in advance.