In a few minutes you can have an encrypted copy of your folders leaving your server on a schedule. This guide covers both destinations: a buddy's server, which needs the buddy to accept a request, and another server you own, which starts straight away.
Requirement: A folder cannot be encrypted after it is created. If a folder you want to send to a buddy is not encrypted, create a new encrypted folder and move the files into it first. See Folder encryption.


The first question is where the copy should go: On a buddy's server or On another server you own.


The panel then shows "Request created. Ask your buddy to open Backups on their HexOS Deck and accept."
Warning: HexOS does not email your buddy about the request. It appears only under Requests in their Backups panel. Message them yourself and ask them to accept it.
Info: A request sent to an email address with no HexOS account simply waits. There is no error and no expiry. Check the spelling before you send. You can withdraw a pending request at any time from your side.
Nothing is copied until your buddy accepts. When they do, HexOS reserves the space on their pool and provisioning starts automatically. See Host a buddy's backup for what they see.

No request is needed because you own both servers. Provisioning starts straight away.
Info: Servers that are offline do not appear in the destination list. If a server you expected is missing, wake it and try again.
Provisioning builds the encrypted tunnel between the two servers, reserves the space on the destination pool, and prepares each folder for replication. It usually takes a few minutes. The connection card shows "Setting up…" while this happens, or "Waiting for the other server to come online…" if the destination is offline. You can close the panel; progress continues in the activity center.
If a step fails, the card shows "Setup failed" and HexOS retries on its own. Open the activity item to retry now or cancel. Cancelling deletes nothing, because nothing has been stored yet. Only the side that owns the folders can retry; a host who sees "Setup hasn't finished. Ask the sender to retry from their side" should ask the sender to retry.
The first backup copies everything in the chosen folders, so it takes the longest. The card shows "Backing up…" with a percentage. Every later run sends only what changed since the last restore point.
When the first run finishes, the card reads "Up to date". Open the connection to see each folder's latest backup, the Quota card with the compressed space in use, and the next scheduled run.
By default backups run daily and restore points are kept for 2 weeks. Change either from the connection's Schedule & Retention tile. See Manage your backups.
Help: Setup stuck, or a status you do not recognise? See Backup troubleshooting or ask in the HexOS Discord Community.
Contribute: to help to improve HexOS documentation join the #Docs channel on Discord today! Send feedback, suggestions or contribute a guide.