---
title: Redis Recovery Backups
url: "/docs/backups/managed-cache/"
canonical_url: https://docs.blossom88.com/docs/backups/managed-cache/
markdown_url: https://docs.blossom88.com/docs/backups/managed-cache.md
summary: Protect and restore Redis Caches with encrypted recovery backups
categories:
- caches
- backups
- disaster-recovery
---

# Redis Recovery Backups

Redis Caches store encrypted recovery backups in Amazon S3, Cloudflare
R2, DigitalOcean Spaces, or other S3-compatible storage. Redis remains
available while Blossom creates each snapshot.

## Backup Storage

Choose **Managed by Blossom** to use Blossom's storage. To use your own bucket,
add a destination under **Integrations → Backup Storage**, then select it on the
Cache. PostgreSQL and Redis can share a destination.

    blossom backup_storage:create --data backup-storage.yml

Blossom creates a daily Redis recovery backup and retains 14 completed backups
by default. Open the Cache's **Backup → Edit settings** to change storage or
retention (minimum seven backups). Leave retention blank to use the storage
default.

## Local Recovery

Redis also uses append-only persistence for ordinary process recovery. Blossom
can restart Redis without discarding its local cache data.

Local persistence and recovery backups solve different failures. If local data
is lost, Blossom restores the latest completed backup. Writes newer than that
backup may be lost. Single-node Redis does not claim uninterrupted failover or
zero data loss.

## Create A Backup

    blossom backup:create --data '{"backup":{"cache_instance_id":"cache_instance-100"}}' --follow

`backup:show` reports the source node, encrypted object, size, checksum, and
completion time without exposing Redis or storage credentials.

## Restore A Backup

Restore creates a new Redis Cache instance. It does not overwrite the source.

In the dashboard, open a completed backup and choose **Restore**. On the
Restore page, choose **Shared** or **Dedicated**, review the destination name,
Location and size, then select
**Restore to new instance**. Opening the page does not start a restore.

restore.yml:

```yaml
restore:
  name: restored-redis
  location_id: location-100
  availability: shared
  size: medium
  backup_storage_id: backup_storage-100
  port: 6380
```

    blossom backup:restore --id backup-100 --data restore.yml --follow

Shared uses your Data Capacity; Dedicated runs on its own Server. Each restored
instance gets its own storage and endpoint. Shared is the default where the
Location supports it. Restore keeps the source's storage size and uses the same
capacity limits as creating an instance.

The restore defaults to the source Backup's Backup Storage; set
`backup_storage_id` to use another named destination. Choose the Account
region and an unused port. Blossom shows the price, creates a new Cache,
restores the snapshot, verifies Redis readiness, and gives the restored Cache
its own stable private endpoint.

## Memcached

Memcached contents are disposable. Blossom recreates a missing Memcached Cache
empty and does not present backup settings that imply otherwise.

## Related Documentation

- [Caches](/docs/caches/)
- [Backups Overview](/docs/backups/)