Backups & Recovery

Arctickey automatically backs up your data. Never lose your cache, sessions, or queue data.

Automatic Backups#

Backups run automatically every day at 3:00 AM UTC. Each backup captures a complete snapshot of your data.

Retention by Plan#

PlanRetentionFrequency
Free1 dayDaily
Starter7 daysDaily
Growth30 daysDaily

Viewing Backups#

  1. Go to your Dashboard
  2. Click on your instance
  3. Open the Backups tab

You'll see a list of available backups with:

  • Backup date and time
  • Size
  • Status (completed, in progress, failed)

Restoring from Backup#

Warning: Restoring replaces ALL current data with the backup. This cannot be undone.

Steps to Restore#

  1. Open the Backups tab
  2. Find the backup you want to restore
  3. Click Restore
  4. Confirm the restore

During restore:

  • Your instance will briefly stop (1-2 minutes)
  • All current data is replaced
  • Instance automatically restarts

What Gets Restored#

  • All keys and values
  • TTL (expiration) settings
  • Data structures (lists, sets, hashes, etc.)

What Doesn't Get Restored#

  • Connection settings (host, port, password) — these stay the same
  • Instance configuration
  • IP whitelist rules

Backup Storage#

Backups are stored in Cloudflare R2 (S3-compatible) in European data centers:

  • 🇩🇪 Germany (primary)
  • 🇱🇹 Lithuania (replica)

Your backup data never leaves the EU.

Manual Backups#

Currently, backups are automatic only. If you need an immediate backup before a risky operation:

  1. Use redis-cli to export your data:
Terminal
redis-cli --tls -h YOUR_INSTANCE.eu.arctickey.com -p 6379 -a YOUR_PASSWORD \ --rdb /path/to/backup.rdb
  1. Or export specific keys:
Terminal
redis-cli --tls -h YOUR_INSTANCE.eu.arctickey.com -p 6379 -a YOUR_PASSWORD \ --scan --pattern 'user:*' | xargs redis-cli GET > users.txt

Best Practices#

  1. Don't rely solely on backups for critical data — use Redis as a cache, not primary storage
  2. Test restores periodically — make sure you know the process before you need it
  3. Monitor backup status — check that backups complete successfully
  4. Consider data export for truly critical data

Disaster Recovery#

In the unlikely event of a data center failure:

  1. We automatically failover to backup infrastructure
  2. Your data is restored from the most recent backup
  3. Maximum data loss: up to 24 hours (last backup)

For higher durability requirements, consider:

  • Exporting critical data to your own storage
  • Using Redis as a cache layer, with your database as source of truth

FAQ#

Q: Can I download my backups? A: Not directly from the dashboard. Use redis-cli --rdb to create a local backup.

Q: What if a backup fails? A: We retry automatically. If backups fail repeatedly, we'll alert you.

Q: Can I restore to a different instance? A: Not currently. Contact support if you need this.

Q: Are backups encrypted? A: Yes, backups are encrypted at rest using AES-256.