# Syncing Server to NTP Source

**URL:** <https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [May 1, 2023, 5:52pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099 "2023-05-01T17:52:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [May 1, 2023, 5:52pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099/1 "2023-05-01T17:52:15Z")

</div>

Hello everyone,

I wanted to know what the ramifications of syncing a Primary and Backup gateway to a NTP source would be **if** the NTP time is about 10 minutes behind the current time of the primary and backup.

E.G. the NTP time is currently 1:50PM and the time on the gateways is 2:00PM.

I assume the database will find primary key conflicts with some of the inserts but are there other issues I need to look out for before syncing up the gateways?

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:** [May 1, 2023, 5:55pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099/2 "2023-05-01T17:55:18Z")

</div>

What kind of server OS?

If Linux, you can make it slew to the correct time instead of jumping.

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [May 1, 2023, 5:57pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099/3 "2023-05-01T17:57:45Z")

</div>

> [@pturmel](#):
>
> If Linux, you can make it slew to the correct time instead of jumping.

I was thinking about that.

It is Windows but we are using a tool called Meingburg to act as the NTP client/server instead of the built-in Windows NTP

---

<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:** [May 1, 2023, 5:58pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099/4 "2023-05-01T17:58:49Z")

</div>

> [@brandon1](#):
>
> a tool called Meingburg

No clue.

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [May 1, 2023, 6:00pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099/5 "2023-05-01T18:00:32Z")

</div>

oops. misspelled it: Meinburg

I'm going to see if I can make it do slow updates instead of a big jump as you suggested.

---

<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:** [May 1, 2023, 6:03pm UTC](https://forum.inductiveautomation.com/t/syncing-server-to-ntp-source/73099/6 "2023-05-01T18:03:47Z")

</div>

In Linux, the slewing is done by changing the kernel's clock constant so "realtime" runs faster or slower at the microseconds level--no discontinuities. If Meinburg can do that with Windows, that would be good to know. If it cannot, then even second by second jumps will produce conflicts.

{ Windows + Plant Floor Networks == Engineering malpractice, IMNSHO }