ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved Windows DC reverted to old snapshot trying to finalize replica failover

    IT Discussion
    kerberos windows server hyper-v replica
    3
    13
    726
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch @DustinB3403
      last edited by

      @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.

      DustinB3403D 1 Reply Last reply Reply Quote 0
      • DustinB3403D
        DustinB3403 @JaredBusch
        last edited by

        @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?

        JaredBuschJ 1 Reply Last reply Reply Quote 0
        • JaredBuschJ
          JaredBusch @DustinB3403
          last edited by

          @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.

          1 1 Reply Last reply Reply Quote 0
          • 1
            1337 @JaredBusch
            last edited by 1337

            @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.

            1 JaredBuschJ 3 Replies Last reply Reply Quote 0
            • 1
              1337 @1337
              last edited by

              @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?

              JaredBuschJ 1 Reply Last reply Reply Quote 0
              • JaredBuschJ
                JaredBusch @1337
                last edited by

                @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.

                1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @1337
                  last edited by

                  @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.

                  1 1 Reply Last reply Reply Quote 1
                  • JaredBuschJ
                    JaredBusch @1337
                    last edited by

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • 1
                      1337 @JaredBusch
                      last edited by 1337

                      @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.

                      1 Reply Last reply Reply Quote 1
                      • JaredBuschJ
                        JaredBusch
                        last edited by JaredBusch

                        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.

                        1 Reply Last reply Reply Quote 1
                        • 1 / 1
                        • First post
                          Last post