The web UI at a glance
Everything in Asternodis is driven from the web console. The left navigation groups the work by task:
| Page | What you do there |
|---|---|
| Overview | Health and scale across your estate at a glance. |
| Inventory | Connect Proxmox clusters; see nodes, guests, storage, CPU/RAM. |
| Site Pairs | Create and manage DR Site Pairs with peer sites. |
| Replication | Protect guests, watch RPO, and run recovery operations. |
| Alerts | Every firing alert from this site and its paired sites, and every silence. Dismiss an alert, silence it, or lift a silence. |
| Shadows | Every recovery replica across your sites. Reclaim storage from orphaned ones. |
| Recovery Plans | Group guests into ordered runbooks for failover and DR tests. |
| Operations | Watch running work step by step, and read the history of past runs. |
| Networking | Bridge/VLAN mapping, re-IP defaults, and DR DNS for each pair. |
| Settings | Controller configuration and the tabs below. |
Settings is a tabbed page, and every role has it: the tabs you see follow your role. Viewers and operators get Compliance and License, admins get all six.
| Settings tab | What you do there |
|---|---|
| General | Topology, dual-control, console URL, backup, and more (admin only). |
| Users & access | Operator accounts and their roles (admin only). |
| Automation | Webhooks before and after failovers and DR tests (admin only). |
| Compliance | DR-test evidence, RTO/RPO reports, and the control-framework coverage they support. |
| License | Trial status, activation, and your entitlement. |
| Audit log | The attributable, tamper-evident event history (admin only). |
The Overview dashboard
Overview is the landing page. On a fresh install it prompts you to connect the Proxmox cluster this instance manages.
Once you’re set up, Protection, the question this product exists to answer, sits at the top, before any infrastructure counts:
- Posture now: every protected guest by state in one donut, with the states that need you (RPO breached, last sync failed, at risk, never synced) listed ahead of the rest, so “how many need me” is one glance.
- Closest to breaching: each guest’s replica age against its own RPO target, worst first, for the six guests closest to their limit. A fleet-wide average would be meaningless when targets differ per guest: one guest at 300% of a one-minute target is the emergency, not the average.
- Replication activity: data shipped per hour over the last 24 hours, with full seeds distinguished from incrementals and failures marked on the axis. A spike that is a seed is routine; a spike that is not is worth looking at.
On a site that protects no guests of its own and is the recovery half of an active pair, the same three figures are read across the pair from the site that protects those guests, so both Overviews show the same picture. Any site that holds DR copies also gets Copies held here: how many DR copies it stores, how many guests are failed over to it right now, the age of the stalest, and how much of its recovery-point catalogue each integrity check has covered (see Fleet coverage), which only it can measure.
Below that: site health, cluster inventory, and anything that needs attention.
Search
Press the search box in the navigation to jump anywhere: it matches pages and in-page sections, grouping results under their page so you can land directly on, say, Controller backup & restore inside Settings.
Roles
What you can see and do depends on your role: viewer, operator, or admin. See Users & security.
Start with Inventory.