# Backups and moving

## Backups

The forge copies itself every night: repositories, the database and settings. Open `/settings/backups` to see the last copy, send copies somewhere else (a destination you choose), take one now, and run a restore drill that proves a copy works. A copy that has not been proved is not counted as safe, and home says so when a backup is overdue.

What a copy does not hold is listed in [recovery](RECOVERY.md#what-a-snapshot-does-not-hold).

## Restore

Recovery is a printable guide, with two routes: the restore command, or the objects by hand. Read [recovery](RECOVERY.md) before you need it, and keep the key to your backup off the forge.

## Moving

- **To your machine**: `forge sync` clones the apps you pin (or, with none pinned, the ones you own), and work continues offline. See [on your machine](ON-YOUR-MACHINE.md).
- **Between forges**: connect another forge as an origin at `/settings/origins`, bring an app in, and send changes back. See [origins](ORIGINS.md).
- **To a new owner**: transfer an app from its Danger zone. Old links keep working ([transfer](features/repo-transfer.md)).

To keep your repositories mirrored on your machine, so you can work offline, run this after `forge login`:

```sh
forge sync
```

Next: [Every setting, by topic](guide-settings.md).

Every feature note, by topic: [the reference notes](features/README.md).
