Database Infrastructure
Settings → DATABASE INFRA (Admin, Business Hub) shows storage health and optional Fleet Engine Assistant migration. This tab does not replace local appliance LiteDB on Nodes.
Who sees what
| Appliance type | DATABASE STATUS | Fleet Engine Assistant |
|---|---|---|
| Standalone / Node | Single APPLIANCE store (StacksAtlas.db) | Hidden: no fleet DB on Node. |
| Central Hub | APPLIANCE + FLEET dual-store summary | Shown when fleet DB can be configured. |
DATABASE STATUS panel
Read-only health for encrypted storage:
| Display | Meaning |
|---|---|
| APPLIANCE · LITEDB | Local StacksAtlas.db: users, settings, Hub-local state. Always LiteDB on the appliance. |
| FLEET · SQLITE (default) | StacksAtlas.Hub.db: enrolled nodes, fleet devices, federated telemetry. |
| FLEET · POSTGRESQL / SQL SERVER | External relational store after migration (Enterprise deployments). |
| Size (MB) | On-disk or reported size per store. |
| Next scheduled maintenance | Automatic cleanup window when exposed by health API. |
Fleet Engine Assistant
Available on Hubs when
canConfigureFleetEngine is true.FLEET DATABASE PROVIDER
| Provider | Use when |
|---|---|
| SQLite file (StacksAtlas.Hub.db) | Default. Single-file fleet store on the Hub host. Suitable for most Business fleets. |
| PostgreSQL (Enterprise) | External HA database, DBA-managed backups, large fleet inventories. |
| Microsoft SQL Server (Enterprise) | Same as PostgreSQL for Windows-centric data centers. |
Connection fields (external engines)
When PostgreSQL or SQL Server is selected:
| Field | Notes |
|---|---|
| HOST / ENDPOINT | Database server hostname or IP. |
| PORT | 5432 (PostgreSQL) or 1433 (SQL Server) by default. |
| DATABASE NAME | Target database (e.g. stacksatlas_hub). Must exist or be creatable per your DBA policy. |
| USERNAME / PASSWORD | Credentials with DDL/DML rights for migration. |
| Migrate existing fleet SQLite data | When checked, copies current StacksAtlas.Hub.db contents into the new engine during apply. |
Workflow
- Choose FLEET DATABASE PROVIDER.
- Fill connection details (external engines only).
- Click TEST CONNECTION to verify reachability before migration.
- Click APPLY & MIGRATE and confirm the critical-operation dialog.
During migration, node communications are buffered in memory. On failure, ingestion rolls back to the previous fleet engine.
Backups & snapshots
| Store | Backup via |
|---|---|
| Appliance LiteDB | DATA GOVERNANCE → snapshot with APPLIANCE chip |
| Fleet SQLite / external | DATA GOVERNANCE → snapshot with FLEET chip (Hub) |
Download snapshots for off-site archival. External PostgreSQL/SQL Server backups follow your DBA runbooks in addition to StacksAtlas snapshots.
Related guides
- Data governance & backups: snapshots, Fresh Start, portable export
- Hub & fleet federation: enrollment and fleet lifecycle
- Architecture: stack overview