Operations
Operations is the single place to answer “what is Asternodis doing right now, and what did it do earlier?” Failovers, failbacks, DR tests, reseeds and recovery-plan runs all report here.
Active & recent
The live feed. It merges in-flight guest operations and recovery-plan runs from both sides of the pair — so an operation you started from the primary but which actually executes on the recovery side still appears here. You don’t have to log into the other site to watch your own failover.
Each row deep-links to that operation’s own progress page, which streams the steps as they happen: bytes moved, timings, warnings, and the exact error if a step fails.
Any DR test currently running is surfaced here too, with the test VMID and the site it’s running on, so a forgotten test bubble is never invisible.
Earlier operations
The durable journal. Where the live feed is in-memory, this is persisted, so it survives a controller restart — the history doesn’t vanish because you rebooted the box. It merges the local and peer journals and tags each row with the site that actually executed it, so the page reads the same from either end of a pair.
It’s paged, because a busy estate produces a lot of operations and an unbounded list stops being scannable.
Why operations are durable
A DR operation is exactly the kind of work you cannot afford to lose track of halfway through. Asternodis writes each one to a journal as it goes, so:
- closing the tab doesn’t cancel or hide anything — the work runs on the server
- a controller restart mid-failover leaves a record you can pick up
- “did that reseed ever finish?” has an answer weeks later
Related
- Recovery Plans — the runbooks whose runs appear here.
- Replication & recovery operations — starting the work in the first place.
- Compliance & reporting — DR-test evidence built from these runs.