Restore
Overview
The Aerospike Backup Service (ABS) on Aerospike Kubernetes Operator (AKO) can trigger a restore from a Custom Resource (CR) file that represents a restore configuration for an Aerospike cluster. We refer to this as an Aerospike Restore CR.
It supports Full, Incremental and Timestamp based restores.
You can trigger the restore using kubectl or helm.
Requirements
Before triggering a restore, deploy the ABS on your Kubernetes cluster using one of the following methods:
Once running, the ABS reads the CR file to trigger a restore.
1. Prepare Aerospike restore CR
Create your YAML-formatted CR file with the restore configuration you want to perform. See restore configuration settings for details on the parameters available in the restore CR file.
You can find a sample restore CR file in the main Aerospike Kubernetes Operator repository.
Restore is a one-time operation, so the restore CR cannot be updated. If you need to update the restore configuration, you must create a new restore CR.
2. Perform the Aerospike restore
Use the CR YAML file you created to trigger a restore. If you don't have a CR file, you can choose one of the restore sample files in the main Aerospike Kubernetes Operator repository.
kubectl apply -f aerospikerestore.yaml -n aerospike
3. Verify restore status
To verify the status of the restore, use the following command:
kubectl get aerospikerestore RESTORE_NAME -n aerospike -oyaml
The status field in the output then shows the status of the restore operation.
status:
job-id: 6893789046818082912
phase: Completed
restoreResult:
status: Done