How do I maintain the on-prem AIR host?

Category: FAQ → Installation & Maintenance Applies to: On-premises AIR Console and Database nodes

---

Overview

Customers can safely perform operating system upgrades, security patching, or hardware maintenance on their on-premises AIR environment, provided the system continues to meet the supported platform requirements and all Binalyze Docker containers remain healthy before and after maintenance.

---

Requirements and Recommendations

1. Supported Environment

Your AIR system must always run on one of the officially supported operating systems and Docker versions listed in the Supported Distributions (x64 only) section of the Console Installation Guide. Ensure the target OS version is compatible with Docker and remains within Binalyze’s supported list.

2. System Continuity

You can safely perform OS, security, or hardware upgrades as long as all Binalyze Docker containers are running and healthy before making changes. After completing the maintenance, verify that all containers show a healthy status by running docker ps and confirm that the AIR web interface is accessible.

3. Backup Recommendation

Before performing any maintenance, take a full backup or snapshot of the AIR system. See Backup by AIR Console UI for detailed steps. This allows the environment to be quickly restored in case of unexpected issues.

4. Customer Responsibility

All on-prem OS and hardware maintenance operations are the customer’s responsibility. Binalyze Support does not manage, validate, or assist with customer-initiated OS updates, patches, or migrations.

5. Post-Upgrade Validation Checklist

After completing OS or hardware maintenance, verify the following:

• Run docker ps and confirm all containers show healthy.

• Log in to the AIR Console and verify version, license, and system status.

• Check that all assets are connected and reporting.

• Review Settings → System Info for expected configuration values.

---

Disclaimer

As long as all Binalyze Docker containers are running and healthy before the change, and the environment remains within supported OS and Docker requirements, it is safe to proceed. Always back up the environment first. Binalyze cannot be held responsible for issues resulting from unsupported OS, Docker, or hardware configurations.