Issue with Server 12 Hyper V replica
Hi,
I have two Windows Server 2012 with the Hyper-V role installed. I am replicating the DC and a member server. I have the replica failover working fine. But when I run the failback, I need to power down the DC. The two Hyper-V servers then cannot contact each other as DNS is also powered down. So I created local host entries for each other and now they can ping FQDN and resolve each other names. However, it still failed, with RPC errors, then once the DC is back up all is okay.
But of course I need the DC VM off.
This is the only DNS/DC server on the Domain.
What can I do to resolve this?
- GNS.
I have two Windows Server 2012 with the Hyper-V role installed. I am replicating the DC and a member server. I have the replica failover working fine. But when I run the failback, I need to power down the DC. The two Hyper-V servers then cannot contact each other as DNS is also powered down. So I created local host entries for each other and now they can ping FQDN and resolve each other names. However, it still failed, with RPC errors, then once the DC is back up all is okay.
But of course I need the DC VM off.
This is the only DNS/DC server on the Domain.
What can I do to resolve this?
- GNS.
David Johnson, CD
Best practices is to always have at minimum 2 DC's
ASKER
Any other suggestions/workarounds? the constraint I'm faced with is that there is just one DC right now, it is also a file server so replication for DR is required. Thanks for your help, any other insights into how to get this to work would be greatly appreciated
1 you need two DC's
2. in the dns settings on the adapters you need to have both dc's ip addresses this way if one DC goes down, then the 2nd one will take up the slack, or if the 1st primary DC is overloaded the 2nd one will again take up the slack. Active directory requires a DC to be available or you will have problems.
3. you will have replica errors when a machine goes offline. These can be safely ignored since you know the cause of them. What do you suggest we recommend. Best practices are there for a reason as they are tried and tested from the beginnings of Active Directory. AD is the one trump card that Microsoft holds over the competition.
2. in the dns settings on the adapters you need to have both dc's ip addresses this way if one DC goes down, then the 2nd one will take up the slack, or if the 1st primary DC is overloaded the 2nd one will again take up the slack. Active directory requires a DC to be available or you will have problems.
3. you will have replica errors when a machine goes offline. These can be safely ignored since you know the cause of them. What do you suggest we recommend. Best practices are there for a reason as they are tried and tested from the beginnings of Active Directory. AD is the one trump card that Microsoft holds over the competition.
ASKER
Ok thanks for that. We can review with tech team tomorrow, appreciate the input
ASKER
Seeing that we are not using best practices, I think I will add the dns role to the primary Hyper-V server and include that IP as the second DNS, so when the dc/primary dns server is off line the secondary DNS can kick in. I shall test that in the morning and revert.
Thanks.
Thanks.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
There was no other solution provided.