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

    Hyper-V uptime mismatch

    Scheduled Pinned Locked Moved IT Discussion
    hyperv
    47 Posts 6 Posters 4.3k Views
    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 @brianlittlejohn
      last edited by

      @brianlittlejohn said in Hyper-V uptime mismatch:

      I've noticed sometimes when I take a backup of my Hyper-V guests it resets the uptime that is displayed in the manager. It is real sporadic when it happens so I haven't been able to pin it down to what exactly is happening.

      This system does a backup (with Veeam B&R) every 4 hours and this time is not exactly on that mark but close.

      I will monitor this.

      The non Windows VM's show the correct uptime.
      0_1516052457010_3aef97c9-b751-44fb-9cf2-261ef06a4c72-image.png

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

        Here is additional proof of the backup process causing this issue. Using Veeam of course. .

        1 Reply Last reply Reply Quote 1
        • dbeatoD
          dbeato
          last edited by

          @jaredbusch said in Hyper-V uptime mismatch:

          m, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

          Do your VMs go to Saved State when you reboot the host?

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

            @dbeato said in Hyper-V uptime mismatch:

            @jaredbusch said in Hyper-V uptime mismatch:

            m, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

            Do your VMs go to Saved State when you reboot the host?

            Host was also rebooted 15 days ago.. SO not relevant. But to answer the question, no, the Windows ones do not.

            dbeatoD 1 Reply Last reply Reply Quote 1
            • DustinB3403D
              DustinB3403
              last edited by

              @JaredBusch "If you go inside of the Windows VM navigate to Task Manager -> Performance -> Check CPU, then you will see it correct or if it is linux vm run the uptime command."

              Can you confirm if the time is accurate within the windows vm under the above settings?

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

                @jaredbusch said in Hyper-V uptime mismatch:

                @dbeato said in Hyper-V uptime mismatch:

                @jaredbusch said in Hyper-V uptime mismatch:

                m, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                Do your VMs go to Saved State when you reboot the host?

                Host was also rebooted 15 days ago.. SO not relevant. But to answer the question, no, the Windows ones do not.

                Yes, it is not relevant. But Example below of my VMs:
                0_1516052680005_2018-01-15_1644.png

                For the same VM Hyperv Manager shows this:
                0_1516052722936_2018-01-15_1645.png

                I upgraded the Agents on the VMs but you probably did that already.

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

                  @dustinb3403 said in Hyper-V uptime mismatch:

                  @JaredBusch "If you go inside of the Windows VM navigate to Task Manager -> Performance -> Check CPU, then you will see it correct or if it is linux vm run the uptime command."

                  Can you confirm if the time is accurate within the windows vm under the above settings?

                  That screenshot was showing the uptime on the performance tab, which shows the same as you are driving towards. But yes, the 15 day mark is the correct uptime and everything is correct inside the VMs

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

                    So the simple thing here is to just watch the timer reset at the next backup and count the time. I bet that is what is happening.

                    Of course this is annoying as all hell. . . . and means you can't trust the hypervisor for the appropriate information. You have to dig into each VM. . .

                    I wonder if this same issue occurs on different hypervisors as well. . .

                    1 Reply Last reply Reply Quote 0
                    • dbeatoD
                      dbeato
                      last edited by

                      I also would look at this:
                      https://support.microsoft.com/en-us/help/2981479/the-uptime-value-of-the-hyper-v-management-console-changes-to-the-resu

                      1 Reply Last reply Reply Quote 1
                      • thwrT
                        thwr
                        last edited by

                        @jaredbusch said in Hyper-V uptime mismatch:

                        Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                        Is the VM getting paused or something like that?

                        DustinB3403D dbeatoD 2 Replies Last reply Reply Quote 0
                        • DustinB3403D
                          DustinB3403 @thwr
                          last edited by

                          @thwr said in Hyper-V uptime mismatch:

                          @jaredbusch said in Hyper-V uptime mismatch:

                          Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                          Is the VM getting paused or something like that?

                          Essentially yes.

                          1 Reply Last reply Reply Quote 1
                          • dbeatoD
                            dbeato @thwr
                            last edited by

                            @thwr said in Hyper-V uptime mismatch:

                            @jaredbusch said in Hyper-V uptime mismatch:

                            Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                            Is the VM getting paused or something like that?

                            That's what the article shows.

                            thwrT 1 Reply Last reply Reply Quote 0
                            • dbeatoD
                              dbeato
                              last edited by

                              Another article
                              https://www.veeam.com/kb1896

                              1 Reply Last reply Reply Quote 0
                              • thwrT
                                thwr @dbeato
                                last edited by

                                @dbeato said in Hyper-V uptime mismatch:

                                @thwr said in Hyper-V uptime mismatch:

                                @jaredbusch said in Hyper-V uptime mismatch:

                                Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                                Is the VM getting paused or something like that?

                                That's what the article shows.

                                Missed it, sorry

                                dbeatoD 1 Reply Last reply Reply Quote 0
                                • dbeatoD
                                  dbeato @thwr
                                  last edited by

                                  @thwr said in Hyper-V uptime mismatch:

                                  @dbeato said in Hyper-V uptime mismatch:

                                  @thwr said in Hyper-V uptime mismatch:

                                  @jaredbusch said in Hyper-V uptime mismatch:

                                  Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                                  Is the VM getting paused or something like that?

                                  That's what the article shows.

                                  Missed it, sorry

                                  Oh no! I didn't mean it that way. Just agreeing with you 🙂

                                  thwrT 1 Reply Last reply Reply Quote 0
                                  • thwrT
                                    thwr @dbeato
                                    last edited by

                                    @dbeato said in Hyper-V uptime mismatch:

                                    @thwr said in Hyper-V uptime mismatch:

                                    @dbeato said in Hyper-V uptime mismatch:

                                    @thwr said in Hyper-V uptime mismatch:

                                    @jaredbusch said in Hyper-V uptime mismatch:

                                    Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                                    Is the VM getting paused or something like that?

                                    That's what the article shows.

                                    Missed it, sorry

                                    Oh no! I didn't mean it that way. Just agreeing with you 🙂

                                    Easy 😉 I just haven't read the article (or even noticed the link) before posting. Was just the first thing coming to mind.

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

                                      The VM doesn't know what is happening, so when a backup kicks off, Veeam (with the hypervisor) pauses the VM for a moment, takes a snapshot and then resumes the VM.

                                      The issue is that the VM doesn't and shouldn't count this as downtime as it's planned and thus the "uptime" counter remains.

                                      Of course this throws a wrench into looking at the VM's because when you see X days (or hours depending on what you are looking at) of uptime when you know you've had backups completed you'll assume something is broken.

                                      Restarting the drivers within the VM would likely fix the issue, but I honestly wouldn't think it's worth the effort.

                                      1 Reply Last reply Reply Quote 1
                                      • DustinB3403D
                                        DustinB3403
                                        last edited by DustinB3403

                                        @JaredBusch can you restart the Veeam drivers on one of these VM's and see if the issue is "corrected".

                                        On a side thought I would think you want to keep the VM uptime as accurate as possible, since the VM isn't being rebooted or shutdown changing this time could effect your troubleshooting strategy (reboot first) sort of issues. . .

                                        I think the better option would be to have the host pull in the actual uptime of the VM from the VM it's self . . . why should it think the VM has been rebooted because of a backup . .

                                        1 Reply Last reply Reply Quote 1
                                        • ObsolesceO
                                          Obsolesce @JaredBusch
                                          last edited by

                                          @jaredbusch said in Hyper-V uptime mismatch:

                                          Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                                          Any ideas?

                                          0_1516052232041_c3f5dafb-2b3f-4a7e-bc82-ac0b5baf824b-image.png

                                          Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.

                                          thwrT 1 Reply Last reply Reply Quote 2
                                          • thwrT
                                            thwr @Obsolesce
                                            last edited by

                                            @tim_g said in Hyper-V uptime mismatch:

                                            @jaredbusch said in Hyper-V uptime mismatch:

                                            Client has a Hyper-V system, but the Hyper-V Manager shows the guest uptime as 3 hours while the guest shows an uptime of 15 days (last time I rebooted it).

                                            Any ideas?

                                            0_1516052232041_c3f5dafb-2b3f-4a7e-bc82-ac0b5baf824b-image.png

                                            Didn't read any replies yet so may have been mentioned... if a VM is put into a saved state, Hyper-V resets the uptime counter, but the OS has no idea it went "down". Because technically, it didn't. It was paused. So from Hyper-V's view, it was off.

                                            Which it is, from a technical point of view.

                                            DustinB3403D 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 1 / 3
                                            • First post
                                              Last post