Hyper-V uptime mismatch
-
If the state of the VM was something other than "running" for whatever reason (in this case to back up the VM), then it will reset the Uptime counter. This is completely independent and not related to the Guest OS uptime.
That your backup software is causing the VM to be put into a saved state is the issue.
-
@tim_g said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Correct, A backup should not reset the counter. it does not for all other systems., and as you can see here, once the services refreshed inside the VM, it went back to the proper time for the exchange server.
The DC has currently just finished backing up again.
This means that it's running an OS or integration tools that doesn't support the backup method you want.
That VM is being put into a saved state because of this, whereas the others are not.
So you're stating the the Hyper-V drivers and or Veeam are out of date (possible) but quite the conclusion when there is nothing that states "update yo stuff to correct this" in anything I can find.
-
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
@jaredbusch said in Hyper-V uptime mismatch:
Correct, A backup should not reset the counter. it does not for all other systems., and as you can see here, once the services refreshed inside the VM, it went back to the proper time for the exchange server.
The DC has currently just finished backing up again.
This means that it's running an OS or integration tools that doesn't support the backup method you want.
That VM is being put into a saved state because of this, whereas the others are not.
So you're stating the the Hyper-V drivers and or Veeam are out of date (possible) but quite the conclusion when there is nothing that states "update yo stuff to correct this" in anything I can find.
No, I'm saying:
@tim_g said in Hyper-V uptime mismatch:
If the state of the VM was something other than "running" for whatever reason (in this case to back up the VM), then it will reset the Uptime counter. This is completely independent and not related to the Guest OS uptime.
That your backup software is causing the VM to be put into a saved state is the issue.
-
@tim_g said in Hyper-V uptime mismatch:
If the state of the VM was something other than "running" for whatever reason (in this case to back up the VM), then it will reset the Uptime counter. This is completely independent and not related to the Guest OS uptime.
That your backup software is causing the VM to be put into a saved state is the issue.
Your arguing to stop using Live Backups, just reboot the VM at every backup then.. Rather than "fix the damn uptime counter Hyper-V / Veeam"
-
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
If the state of the VM was something other than "running" for whatever reason (in this case to back up the VM), then it will reset the Uptime counter. This is completely independent and not related to the Guest OS uptime.
That your backup software is causing the VM to be put into a saved state is the issue.
Your arguing to stop using Live Backups, just reboot the VM at every backup then.. Rather than "fix the damn uptime counter Hyper-V / Veeam"
I don't see the counter as the issue.
I see the issue as the VM being put into a saved state when it should not be.
-
@dustinb3403 said in Hyper-V uptime mismatch:
@jaredbusch In your last screenshot the ACIEXCH01 had a 3 hour uptime. Was that screenshot old or did you do something within the VM to correct the time?
No, the backup runs every 4 hours. and just ran at 4PM CST.
Edit: I obviously see the part about the services being refreshed, my question was this a manual operation?
No. I did not refresh anything manually.
-
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
If the state of the VM was something other than "running" for whatever reason (in this case to back up the VM), then it will reset the Uptime counter. This is completely independent and not related to the Guest OS uptime.
That your backup software is causing the VM to be put into a saved state is the issue.
Your arguing to stop using Live Backups, just reboot the VM at every backup then.. Rather than "fix the damn uptime counter Hyper-V / Veeam"
I don't see the counter as the issue.
I see the issue as the VM being put into a saved state when it should not be.
But it isn't. And after this last backup, the Exchange server is not showing the incorrect value even though the backups have completed.
-
@jaredbusch said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
If the state of the VM was something other than "running" for whatever reason (in this case to back up the VM), then it will reset the Uptime counter. This is completely independent and not related to the Guest OS uptime.
That your backup software is causing the VM to be put into a saved state is the issue.
Your arguing to stop using Live Backups, just reboot the VM at every backup then.. Rather than "fix the damn uptime counter Hyper-V / Veeam"
I don't see the counter as the issue.
I see the issue as the VM being put into a saved state when it should not be.
But it isn't. And after this last backup, the Exchange server is not showing the incorrect value even though the backups have completed.
Do a manual backup so you can watch Hyper-V Manager to see if it gets put into a quick saved state. Does the Hyper-V logs show it was put into a saved state?
If it's not changing state from running to something else, then Veeam needs to fix their shit to stop fucking with the Hyper-V VM uptime timer.
-
it never goes into a saved state.
The only thing ever in the log is this
-
@jaredbusch said in Hyper-V uptime mismatch:
it never goes into a saved state.
The only thing ever in the log is this
No idea then. I back up VMs all the time and their Uptime never resets regardless of guest OS.
If this is specific to Veeam, they need to fix it then.
The GuestOS logs will tell you of any shutdowns/reboots. If those are clean, and the state of the VM is indeed NOT changing from running to anything else, then that leaves Veeam's backup process screwing with it.
-
Is the HyperV Integration tools up to date?
