---
title: "Aerospike Backup CR"
description: "Learn how to trigger on-demand and scheduled Aerospike backups using the Aerospike Backup Custom Resource (CR)."
---

# Aerospike Backup CR

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

::: caution
AKO version 4.x or later does not support Aerospike Backup Service version 2.x. Upgrade to Aerospike Backup Service v3.0.0 or later. See [Upgrade ABS](https://aerospike.com/docs/kubernetes/tools/backup/upgrade-backup-service) for more information.
:::

AKO watches an `AerospikeBackup` custom resource (CR) that describes a backup configuration for an Aerospike cluster. When you create or update that CR, AKO reconciles it and uses Aerospike Backup Service (ABS) to run the backup. We refer to this object as an Aerospike Backup CR.

You can trigger both on-demand and scheduled backups using `kubectl` or `helm`.

## Requirements

Before creating backups, deploy the ABS on your Kubernetes cluster using either:

-   [kubectl](https://aerospike.com/docs/kubernetes/4.4.x/tools/backup/backup-service)
-   [Helm](https://aerospike.com/docs/kubernetes/4.4.x/tools/backup/backup-service-helm)

Once ABS is running, apply or update the Aerospike Backup CR; AKO reconciles the CR and drives the backup through ABS.

## Create a backup

1.  Create your YAML-formatted backup CR file with the backup configuration you want to perform.
    
    See [backup configuration settings](https://aerospike.com/docs/kubernetes/4.4.x/tools/backup/backup-configuration) for details on the parameters available in the backup CR file. You can find a sample backup CR file in [the main Aerospike Kubernetes Operator repository](https://github.com/aerospike/aerospike-kubernetes-operator/tree/v4.4.1/config/samples).
    
    You can edit the CR file at any time to make changes and manage the backup.
    
2.  Use `kubectl` to apply the CR file you created. AKO reconciles the CR and performs the backup through ABS using your defined settings.
    
    ```plaintext
    kubectl apply -f aerospikebackup.yaml -n aerospike
    ```
    
3.  Verify that the `AerospikeBackup` CR exists and points to the intended backup service.
    
    Terminal window
    
    ```bash
    kubectl -n aerospike get aerospikebackup
    
    kubectl -n aerospike describe aerospikebackup AEROSPIKE_BACKUP_NAME
    ```