Everything You Need to Know

Systems

NTP

Estimated reading: 4 minutes 5 views

The Time Synchronization Configuration page allows administrators to manage how the OneDB server handles system time.

Accurate system time is important for many operational areas, including audit logs, monitoring, troubleshooting, and time-based system activities.

In OneDB:

  • Time Zone controls how time is displayed.
  • NTP controls operating system clock accuracy.

OneDB also supports air-gapped environments, so NTP is optional and the system can continue using the local operating system time when needed.

Accessing the Page

To open this page, go to:

System → NTP

This page contains two main sections:

  • Time Synchronization Settings
  • Current System Time Status

Time Synchronization Settings

The Time Synchronization Settings section is used to configure how the OneDB server should handle time synchronization.

Time Mode

The Time Mode field determines how OneDB should manage time behavior.

Available options:

  • OS Managed / NTP
    Use this mode when the server clock should be synchronized through NTP.
  • Manual / Air-Gapped
    Use this mode when NTP is not available or the environment is isolated.

When Manual / Air-Gapped is selected, OneDB uses the local operating system time.

Enable NTP Synchronization

This option indicates whether NTP synchronization is enabled.

In the current UI, this option is managed automatically based on the selected Time Mode.

  • If OS Managed / NTP is selected, NTP synchronization can be enabled.
  • If Manual / Air-Gapped is selected, NTP synchronization remains disabled.

This makes the behavior simpler and helps avoid configuration conflicts.

NTP Servers

The NTP Servers field is used to define the primary time servers.

Enter one server per line.

Example:

10.10.10.20
ntp01.customer.local

This field supports internal IP addresses and internal hostnames, which is useful for customer-managed infrastructure.

Fallback NTP Servers

The Fallback NTP Servers field is optional.

These servers may be used if the primary NTP servers are unavailable.

Example:

ntp.ubuntu.com

In air-gapped environments, this field can usually be left empty.

OS Apply Status

The OS Apply Status field shows the current operating system apply status for the selected configuration.

Example:

Not applied yet

This helps administrators understand whether the saved OneDB time synchronization settings have already been applied at the operating system level.

Save

Click Save to store the current time synchronization settings.

After saving, OneDB keeps the selected configuration for future use and status tracking.

Current System Time Status

The Current System Time Status section displays the current status of the server time.

This information helps administrators verify the actual system time condition.

The following information may be shown:

Field Description
System Time The current server time reported by the operating system.
Time Zone The current time zone used by the server.
NTP Service The detected NTP service status, when available.
Synchronized Indicates whether the system clock is synchronized.
Time Mode The active OneDB time mode.
Last Known Valid Time The last valid system time recorded by OneDB.
Clock Rollback Protection Shows whether rollback protection is enabled.
Last Checked The last time OneDB checked the server time status.

Use Refresh Status to reload the latest status information.

Warning Message

If NTP is disabled or unavailable, OneDB may display a warning message such as:

NTP is disabled or unavailable. OneDB will use the local operating system time. Please ensure the server clock is maintained correctly.

This warning is informational and helps administrators understand that the server is running without active NTP synchronization.

Air-Gapped Support

OneDB is designed to support air-gapped and restricted environments.

If NTP is not available, OneDB can continue operating using the local operating system time.

This is useful for:

  • isolated networks
  • offline environments
  • highly restricted deployments
  • customers who do not allow public network time services

In this mode, administrators should make sure the server clock is maintained correctly through their own operational procedures.

Clock Rollback Protection

OneDB includes clock rollback protection status tracking.

This helps detect whether the server clock may have been moved backward unexpectedly.

Clock rollback detection is useful for improving visibility into time-related issues and can help administrators investigate incorrect server time settings.

Best Practices

For best results:

  • Use trusted internal NTP servers in production environments.
  • Use the same or equivalent time source across all OneDB nodes in a cluster.
  • Review the Current System Time Status after making configuration changes.
  • Use Manual / Air-Gapped mode only when NTP is not available or not allowed.
  • Ensure the operating system clock is maintained correctly if NTP is disabled.

Summary

The Time Synchronization Configuration page helps administrators manage server time behavior in a simple and flexible way.

OneDB supports both:

  • NTP-managed environments
  • Manual / Air-Gapped environments

This allows OneDB to operate in both connected and isolated deployments while still providing visibility into system time status.

Share this Doc

NTP

Or copy link

Table of Contents