Hyper-V uptime mismatch
-
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup mechanism. Backups shouldn't reset uptime counters for VM's.
A paused VM isn't executing anything. It's in a freezed state. I would compare that to something like a hibernated computer maybe (that's not correct, but you could think like that).
-
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened. I never stopped running. (the whole point of paused/saved state... running memory gets saved)
-
The technicality of it is, a paused VM doesn't equate to being an off or restarted VM, because the VM can track these changes, shutdown, power up, reboot etc. The VM is blind to the backup operation, it wholly "believes" that it is operating continuously.
-
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
-
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
Yeah, the VM is not running. THE VM... is not running. It's paused or in a saved state. Why would hyper-v show the uptime of a VM that is not running as being running? That doesn't make sense.
If you want guest OS uptime, look at the guest OS. If hte guest OS is paused (at the VM level), the guest OS never goes down. Think about it...
-
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
Yeah, the VM is not running. THE VM... is not running. It's paused or in a saved state. Why would hyper-v show the uptime of a VM that is not running as being running? That doesn't make sense.
If you want guest OS uptime, look at the guest OS. If hte guest OS is paused (at the VM level), the guest OS never goes down. Think about it...
I am thinking about it.
Let me ask you this, when you're in Hyper-V manager, and looking at the Uptime of all of your VM's are you assuming the Uptime is "these VM's rebooted X time ago" or "These VMs were unpaused X time ago".
I understand what you're saying, there is a place to find the information. I on the other hand see this as tampering.
-
@dustinb3403 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:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
Yeah, the VM is not running. THE VM... is not running. It's paused or in a saved state. Why would hyper-v show the uptime of a VM that is not running as being running? That doesn't make sense.
If you want guest OS uptime, look at the guest OS. If hte guest OS is paused (at the VM level), the guest OS never goes down. Think about it...
I am thinking about it.
Let me ask you this, when you're in Hyper-V manager, and looking at the Uptime of all of your VM's are you assuming the Uptime is "these VM's rebooted X time ago" or "These VMs were backed up X time ago".
I understand what you're saying, there is a place to find the information. I on the other hand see this as tampering.
No, when I look at Hyper-V Manager Uptime, I see when the VM was last in a state other than "running".
-
@tim_g said in Hyper-V uptime mismatch:
@dustinb3403 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:
@dustinb3403 said in Hyper-V uptime mismatch:
@thwr said in Hyper-V uptime mismatch:
@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?
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.
No it's not. The VM never stops working, it's simply paused, active connections to the VM are paused etc. It's not a shutdown and start or a hard stop.
It's just a flaw in the backup/hyper-v mechanism. Backups shouldn't reset uptime counters for VM's.
There's no flaw. It's working as designed.
Hyper-V sees this: VM is not running
Guest OS sees this: Nothing happened.
But this is where the issue lies. The uptime of the VM is the thing that matters to most people. Not the "unpaused timer" as displayed in Hyper-V.
Yeah, the VM is not running. THE VM... is not running. It's paused or in a saved state. Why would hyper-v show the uptime of a VM that is not running as being running? That doesn't make sense.
If you want guest OS uptime, look at the guest OS. If hte guest OS is paused (at the VM level), the guest OS never goes down. Think about it...
I am thinking about it.
Let me ask you this, when you're in Hyper-V manager, and looking at the Uptime of all of your VM's are you assuming the Uptime is "these VM's rebooted X time ago" or "These VMs were backed up X time ago".
I understand what you're saying, there is a place to find the information. I on the other hand see this as tampering.
No, when I look at Hyper-V Manager Uptime, I see when the VM was last in a state other than "running".
So you're reading into what is there, that's fine if you know that is the information being displayed. But what this is clearly showing here is that at least @JaredBusch thinks it should be reflecting the total time the VM has been operational. And that a backup shouldn't reset the counter.
-
Which means the information as described is vague at best.
-
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.
-
@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.
-
@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?
Edit: I obviously see the part about the services being refreshed, my question was this a manual operation?
-
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.
