Before you start
- A backup vault that reads Ready on Infrastructure → Backups and storage. See Backups and restore points.
- Two clusters connected to Ankra and online:
my-cluster, where the drill runs, anddrill-target, where the clone goes. Each needs a default StorageClass. A cluster whose menu shows Set up backups instead of Backups does not have backups turned on; see Not enabled yet?. - Permissions:
backups.manageto protect the Stack andbackups.operateto take and restore restore points (organisation admins hold both), and a role that may create and deploy Stacks. See Permissions. - The
ankraCLI, signed in, to read and write the test file.
1. Create the drill Stack
The Stack holds a namespace, a 1 GiB volume and a small pod that mounts it.1
Start the draft
Open Infrastructure → Clusters → <your cluster>, then Stacks under Technical details. Click Create a stack, keep Compose a stack, enter
drill as the Stack name, and click Start the draft.2
Add the three manifests
Click Add → Manifest three times, with these Resource name and Manifest source values, clicking Add to draft after each:
drill-namespace:drill-data:drill-app:3
Order and deploy
Select
drill-data, open Parents and tick drill-namespace under Depends on. Select drill-app and tick drill-data. Click Review changes, then Create and deploy stack.The editor reads “Deployment accepted. Follow the operation for its outcome.”4
Write the proof
Find the pod, then write a known line to the volume:The last command prints
saved-before-the-drill.2. Protect the Stack
1
Open the Stack's backups
Open Infrastructure → Clusters → <your cluster> → Backups. In the Protection table, the
drill row reads Unprotected. Click drill.The page is now drill backups, with Backup policy and Restore points.2
Configure protection
Click Configure protection. Choose your Backup vault, keep
daily as the Schedule, and enter drill/data under Persistent volumes to include. Volumes not listed there are not backed up. Type drill into Type drill to confirm and click Save policy.The page reads Backup policy saved, and Backup policy names your vault and drill/data.3. Take a restore point
1
Take it
Click Take restore point, enter
drill as the Note (optional), type drill to confirm and click Take restore point.The page reads “Taking a restore point of drill. It shows in Restore points below when it is ready.” The new row under Restore points reads Being taken, then Complete.2
Read what it carries
Click the restore point. Selected restore point lists what it carries: the
data volume must be there. Read Left out of this restore point: anything listed there is not in the copy, with the reason.4. Break the data
Overwrite the proof, as a bad deploy or a mistaken command would:broken.
5. Restore in place
1
Restore
Click the Complete restore point, then Restore in place. Type
drill into Type drill to confirm and click Replace the data.The page reads “Restoring drill. The stack’s apps stop while their data is replaced, then start again.” The progress reads Running, then Finished.2
Check the data is back
The pod was replaced, so look up its new name, then read the file:It prints
saved-before-the-drill. The restore worked.6. Clone the Stack with its data
The second half of the drill is the disaster case: the data comes back on another cluster.1
Clone with data
On the drill backups page, click Clone with data. Choose
drill-target as the Target cluster, choose Take a new restore point now as the Data source, type drill to confirm and click Clone with data. Do not choose Use the newest complete restore point here: the newest one is the safety copy the restore took, which holds the line broken.The progress shows Draft created on drill-target (“Not deployed yet”), then Copying the data until it reads Finished, then Deploy the draft: “Ready: open the draft and deploy it”. The source Stack keeps running and is not changed.2
Deploy the copy
Open Infrastructure → Clusters and the cluster
drill-target, then Stacks under Technical details, and open drill. Click Review changes, then Create and deploy stack.3
Check the data on the copy
saved-before-the-drill: the data reached the other cluster.ankra cluster stacks clone drill --to drill-target --with-data; see Clone Stacks.
Verify
You have now seen the same line come back twice: in place onmy-cluster, and on drill-target. To keep the evidence, list the restore points and the runs that moved the data:
Clean up
-
On drill backups, click Stop future backups, type
drilland click Stop backups. Restore points already taken stay in the vault until you delete them. -
Delete the drill Stack on both clusters: open it in the stack editor and choose Delete stack from More, or from the CLI:
What can go wrong
Next steps
- Backups and restore points - schedules, retention, what each restore point carries.
- Protect persistent data - before you rename or remove a manifest that owns a volume.
- Clone Stacks - copy whole clusters’ Stacks, with or without data.