Backup and restore

Account, Backup. Type your password in the Take a backup panel and press Download a backup. The file is named with the date and time, so several of them sit together without overwriting each other.

Your password is what encrypts the file, which is why it is asked for.

Sites, pools, zones and access lists, TCP and UDP services, error pages, certificates, paid authorities, settings and accounts, plus the certificate files themselves.

Left out on purpose: node names, cluster membership and each server's identity. Those belong to the machines rather than to the configuration.

• Not only on the load balancers. A backup that lives on the machine it protects is no help when that machine is what failed.
• Somewhere access is controlled, because the file is equivalent to your private keys.
• Somewhere you will still have access if you are locked out of this system, since restoring is how you get back in.

Delete old copies rather than letting them accumulate. Every one stays valid for as long as the keys inside it do.

1. Account, Backup, Restore panel. Choose the file and type the password it was made with.
2. Press See what is in it. This opens the archive and reports what it holds without changing anything.
3. Read the report, especially the addresses it came from.
4. Type restore in the confirmation box and press the button.

Take a backup of what is there now first, if there is any chance you will want it back.

Build one node as normal, restore the backup onto it, then join a second node to it. The restore repoints DNS failover answers to the new nodes automatically, matching the kind of address, and reports anything it could not match by name.

The management network allowlist is deliberately not restored, because restoring it is a good way to be locked out of the system you are in the middle of recovering.

The password is the one that was typed when the backup was taken, which is that person's login password at that time. If they have changed it since, the backup still wants the old one. A backup taken by somebody else needs their password, not yours.

Guard .env separately. Without it a restored database cannot read its own encrypted values.

The configuration does. Each machine still points at the old load balancers, so run the enrollment command again on each one from the Tunnel page of the new fleet.