# Clock Drift Warning and the effects on the tags after initialization

**URL:** <https://forum.inductiveautomation.com/t/clock-drift-warning-and-the-effects-on-the-tags-after-initialization/64109>\
**Category:** Ignition\
**Created:** [September 15, 2022, 11:45am UTC](https://forum.inductiveautomation.com/t/clock-drift-warning-and-the-effects-on-the-tags-after-initialization/64109 "2022-09-15T11:45:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mohammed\_Ben\_Larbi](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@Mohammed\_Ben\_Larbi](https://forum.inductiveautomation.com/u/Mohammed_Ben_Larbi)\
**Post date:** [September 15, 2022, 11:45am UTC](https://forum.inductiveautomation.com/t/clock-drift-warning-and-the-effects-on-the-tags-after-initialization/64109/1 "2022-09-15T11:45:59Z")

</div>

Hello

We had a 42 s Clock Drift warning due to a vmware Backup last night.  
We would like to know what’s gonna be the effects on the tags and the script related after initialization

Thanks

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 15, 2022, 12:40pm UTC](https://forum.inductiveautomation.com/t/clock-drift-warning-and-the-effects-on-the-tags-after-initialization/64109/2 "2022-09-15T12:40:33Z")

</div>

> [@Mohammed\_Ben\_Larbi](#):
>
> had a 42 s Clock Drift warning

That's pretty extreme. Long enough for tag subscriptions to time out all over the place. Expect a great deal of bad data in your history as a result. And missed events.

I didn't realize VMware's backup tech was so outdated. Linux KVM can snapshot a volume in a fraction of a second, allowing the VM to continue running while the rest of the backup process runs off the snapshot.

---

<div class="post-metadata">

**Author:** ![Mohammed\_Ben\_Larbi](https://avatars.discourse-cdn.com/v4/letter/m/bb73d2/32.png) [@Mohammed\_Ben\_Larbi](https://forum.inductiveautomation.com/u/Mohammed_Ben_Larbi)\
**Post date:** [September 15, 2022, 12:57pm UTC](https://forum.inductiveautomation.com/t/clock-drift-warning-and-the-effects-on-the-tags-after-initialization/64109/3 "2022-09-15T12:57:11Z")

</div>

@pturmel ,Is there a way that some tag come back to their default value when the gateway started?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 15, 2022, 1:41pm UTC](https://forum.inductiveautomation.com/t/clock-drift-warning-and-the-effects-on-the-tags-after-initialization/64109/4 "2022-09-15T13:41:12Z")

</div>

> [@Mohammed\_Ben\_Larbi](#):
>
> when the gateway started?

ClockDrift warnings don't mean the gateway restarted.

> [@Mohammed\_Ben\_Larbi](#):
>
> tag come back to their default value

So, I don't think so.