Oracle Cloud Infrastructure Documentation

Restoring an OCI Cache Cluster from a Backup

Restore an OCI Cache cluster by creating a new cluster from an existing backup. The new cluster must meet certain constraints to ensure compatibility with the backup data.

When restoring from a backup, consider the following:
  • Non-sharded backups:
    • Non-sharded backups cannot be restored as sharded clusters.
    • You can change the node count and memory per node, but memory must be equal to or greater than the backup value.
  • Sharded backups:
    • The shard count must match the original backup.
    • You can change the node count per shard (for example, reduce from 3 to 2 nodes per shard).
    • The minimum memory is 2 GB per node.

Example:

  • Backup: Non-sharded, 2 GB per node, Valkey 6
  • Restore: You can set 4 nodes at 4 GB per node. You cannot set 1 GB per node or change to sharded mode.

  • Before you begin, ensure the following prerequisites:

    • An active backup exists in the compartment.
    • You have the required permissions to create clusters and access backups.

    To restore a cluster from a backup:

    1. On the Clusters list page, select Create cluster. If you need help finding the list page, see Listing OCI Cache Clusters.
    2. For Creation type, select Create OCI Cache cluster from backup.
    3. Select the backup source:
      • Select Select from existing backups to view and choose an active backup in the compartment (filtered by status).
      • Alternatively, enter a backup from Object Storage. See Importing Backups.
    4. Configure cluster settings, nodes, networking using the create cluster workflow:
      • Cache Engine: This field is set automatically to match the backup and cannot be edited.
      • Cluster Mode:
        • For non-sharded backups, the new cluster must be non-sharded.
        • For sharded backups, the new cluster must remain sharded, and the shard count must match the backup.
      • Node Count: You can adjust this value without restriction.
      • Memory per Node: Must be equal to or greater than the value in the backup. For example, if the backup had 2 GB per node, the new cluster must have at least 2 GB per node. Setting a lower value results in an error.
      • Shard Count (for sharded clusters): This setting is locked to the value from the backup.
        Note

        After the cluster is created, you can modify the shard count if needed.
      • VCN and Subnet: Select a valid Virtual Cloud Network (VCN) and subnet for the new cluster.
    5. Review the settings to confirm that Creation type is set to create from backup and displays the selected backup.
    6. Select Create to start restoring the cluster.
    After restoration:
    • The cluster starts provisioning independently from the parent cluster.
    • After creation, you can later resize the cluster, such as changing the node count or shard count as allowed.
    • The cluster appears in the Clusters list with status Creating, and transitions to Active when ready.

  • This task can't be performed using the CLI.

    For a complete list of parameters and values for CLI commands, see the CLI Command Reference.

  • This task can't be performed using the API.