Skip to main content

ankra runs

Read the organisation’s run history and act on the runs that move data. A backup, restore or clone run also carries the plan it was given and every attempt of every step, which is what explains a restore that took an hour.

ankra runs cancel

Stop a run that is still going. A run that has already finished is refused rather than reported as cancelled.
Flags

ankra runs get

Describe one run. A backup, restore or clone also shows the plan it was given and every attempt of every step, with the status, the agent job and the failure excerpt of each.
Flags

ankra runs list

List the organisation’s runs, newest first. Naming a cluster or a stack asks the backup lane’s own listing, which carries each run’s data-movement payload; without one, the listing covers every kind of run the organisation has. Examples: ankra runs list —kind backup ankra runs list —cluster production —status failed ankra runs list —kind restore —stack shop
Flags

ankra runs retry

Open a fresh run that resumes a failed backup, restore or clone from the step that failed. The answer is the new run, not the old one: the failed row will never move again, so anything watching it would wait forever.
Flags