# A backup needs a life beyond its server.

> Understand local archives and offsite copies, separate encryption-key access from the source server, and test recovery without relying on the original machine.

Canonical page: https://www.calmbackup.com/guides/offsite-backups

Understand the different roles of local encrypted archives, uploaded copies and a recovery key you can reach after a machine is lost.

[Start free trial](https://app.calmbackup.com/register)

## Think about what can fail together.

A local archive is useful when the machine and its disk remain available. It is less useful when the server is lost, the disk fails or access to that environment disappears. An offsite copy gives you another place to retrieve the archive.

CalmBackup creates an encrypted local file and uploads an encrypted copy. Confirm the remote backup has reached its confirmation step; the existence of a local file alone does not establish that it is available offsite.

[Follow the upload workflow](https://www.calmbackup.com/how-it-works)

## Keep access separate from the thing you protect.

An offsite archive still needs its encryption key. If the only copy of that key is on the lost server, the remote copy cannot solve the recovery problem. Keep a secure, recoverable key copy in a location your authorized operators can access.

Think through account access as well. Document who can retrieve the backup, how they obtain the key and how they prepare a replacement destination. Test that process without using the original machine.

**Encryption and availability solve different problems**

Encryption protects archive contents. It does not make a backup immune to deletion, guarantee that an account is accessible, or keep an encryption key from being lost.

[Understand the security boundary](https://www.calmbackup.com/security)

## Test the copy you expect to depend on.

A restore rehearsal can be quick when the encrypted archive is already cached locally. Also rehearse retrieving a remote archive into a separate environment, so your runbook covers the situation where the original server is unavailable.

Review local and remote backup history separately. Confirm that the recovery points you need are retained, that you have their keys, and that the recovered application works. Keep the result with your recovery instructions.

[Plan your retention window](https://www.calmbackup.com/guides/backup-retention)
