Beard

the taunting honestly helped....honestly...

Wait a nano second...

Yeah, we have plenty of G5s in service here...

It's common Centos....

lol, take red hats for everyone to wear, that should sort it out!

Just to clarify, the mighty @Ric_ has provided some sound advice there, but he does mean just one snapshot of the original server build. You may or may not know this, snapshots can be harmful to a virtual env. It can cause performance issues if you store multiple snapshots or store them over a long period of time. Good luck guys!

Sorry, misread the setup you have. If you aren't using CSVs then you can just use the iSCSI initiator to point at the current LUN. Even Easier!

Yes that is possible. You can use the iSCSI initiator to connect to LUNs on different SANs, assuming they are on the correct network/VLAN and the hosts can see them. This would need to be a fresh LUN though as you'd need to format it for the CSV process to work.

As @Ric_ has just explained AD uses replication for resilience and DCs can also point at themselves. The fact that M$ have said that it is not best practice would make me question my design. Also, if as you say "From the list of downsides at least half of those would still apply if you had two separate DCs with no clustering" doesn't that mean that you'd reduce the risk by 50% if you did have two separate DCs using replication? Anyway, the genius that is @Ric_ has provided you with a good idea of how to fix the issues you are seeing. He's good with this stuff, I'd go with what he's suggested. If you decide to go this way, open a thread if you get issues and we can help.

Also, here's a link that will tell you why clustering DCs is a bad idea. Domain Controllers as Cluster Nodes - Bad Idea - Cluster Help

^^ Maybe clustering these together needs to be viewed as the original issue?

@Ric_ Also, that was about a homophobic penguin. Is there something about penguins as well as cats??

@Ric_ Like this?

@Ric_ Avril.....grrrrr