Solved Windows DC reverted to old snapshot trying to finalize replica failover
-
I have a system that was running in a failover state to a replica VM.
The only VM running on the replica failover was the DC.
While attempting to reverse the replica back to the primary server, the snapshot was applied as the last replica from 2 months ago, not as the live server is today.
But because this is the DC, I can now not manage anything. I assume because kerberos is all out of sync.
Suggestions or recommendations?
I have a full backup from an hour ago (I waited until that ran before doing anything).
-
So, because Veeam reapplied the old snapshot, everything between then and now was lost.
If I keep the old snaphot as current, all the systems have domain trust failure.
I have a backup and there is only a single shared folder on here that will need restored.Because this site is only 20 Windows computers, and I wanted to stop wasting time after 2 hours, I went brute force.
I disjoined everything from the domain and rejoined them.
With that resolved, I restored the C:\shares folder on the DC from the last Veeam backup.
Site is now working again.
Veeam's replication is now also in the correct state to fall back the replica to the main hyper-v server.Not fucking touching that tonight.. I R DUN.
Edit: Maybe not the perfectly correct answer, but the answer I went with.
-
Trying a reboot of HV02.
The only thing running on it is the DC replica that has been running everything.
-
I'd just restore from backup. It's the fastest approach
-
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
I'd just restore from backup. It's the fastest approach
You can't do that "simply" when you are on Hyper-V with a single DC being the thing that got fucked.
-
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
I'd just restore from backup. It's the fastest approach
You can't do that "simply" when you are on Hyper-V with a single DC being the thing that got fucked.
You don't have the original admin creds for the server?
-
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
I'd just restore from backup. It's the fastest approach
You can't do that "simply" when you are on Hyper-V with a single DC being the thing that got fucked.
You don't have the original admin creds for the server?
Of course. I have all of the creds, but that's not how anything works with Hyper-V.
-
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
I'd just restore from backup. It's the fastest approach
You can't do that "simply" when you are on Hyper-V with a single DC being the thing that got fucked.
You don't have the original admin creds for the server?
Of course. I have all of the creds, but that's not how anything works with Hyper-V.
So the VM on the Hyper-V server is the domain controller that Hyper-V is using?
So you need to revert to a newer snapshot on the VM but can't because you can't login until you have reverted to a newer snapshot on the VM?
A recursive loop of failure so to speak. -
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@DustinB3403 said in Windows DC reverted to old snapshot trying to finalize replica failover:
I'd just restore from backup. It's the fastest approach
You can't do that "simply" when you are on Hyper-V with a single DC being the thing that got fucked.
You don't have the original admin creds for the server?
Of course. I have all of the creds, but that's not how anything works with Hyper-V.
So the VM on the Hyper-V server is the domain controller that Hyper-V is using?
So you need to revert to a newer snapshot on the VM but can't because you can't login until you have reverted to a newer snapshot on the VM?
A recursive loop of failure so to speak.I know nothing about hyper-v but don't you have a local admin account you can use?
-
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
So you need to revert to a newer snapshot on the VM
It turns out I have to restore because there was no subsequent snapshot. It was running against the most recent snapshot.
Sadly, if I only had to revert to a different snapshot, I could have done that from powershell.
-
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
I know nothing about hyper-v
This is obvious, based on this next bit.
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
but don't you have a local admin account
Yes
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
you can use?
No
FYI, a bit jealous of you not even needing to know this.
-
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
but can't because you can't login
I have the local log in an it works fine.
-
@JaredBusch said in Windows DC reverted to old snapshot trying to finalize replica failover:
@Pete-S said in Windows DC reverted to old snapshot trying to finalize replica failover:
FYI, a bit jealous of you not even needing to know this.Yeah, I have deep knowledge of some things and know almost nothing about other things.
Luckily I'm in the process of cleansing all windows server knowledge from my brain. -
So, because Veeam reapplied the old snapshot, everything between then and now was lost.
If I keep the old snaphot as current, all the systems have domain trust failure.
I have a backup and there is only a single shared folder on here that will need restored.Because this site is only 20 Windows computers, and I wanted to stop wasting time after 2 hours, I went brute force.
I disjoined everything from the domain and rejoined them.
With that resolved, I restored the C:\shares folder on the DC from the last Veeam backup.
Site is now working again.
Veeam's replication is now also in the correct state to fall back the replica to the main hyper-v server.Not fucking touching that tonight.. I R DUN.
Edit: Maybe not the perfectly correct answer, but the answer I went with.
