OPERATIONS

Backups & restore

Keep a recoverable copy of the workspace you built.

Choose what to protect

Backups include the database, configuration reference, uploaded wallpapers and personal homes, including desktop files and trash. Select application data separately. Arbitrary host directories and the Linux operating system are not included automatically. Files waiting on the Pulse shelf are excluded.

Create and verify

Open Backups or use the authenticated CLI. Verify the archive and download a copy. With a backup passphrase, send encrypted copies to another disk, S3-compatible storage or Google Drive. Store the passphrase safely: an encrypted copy includes the server secret and can restore to a new machine with that passphrase.

Bash
everyos backup

Restore deliberately

Upload the archive, inspect the preview and choose the data to restore. Restoring the database requires administrator confirmation and a password, creates a safety backup and restarts the API. Sign in again afterwards. Configuration files are included for reference and are not restored automatically.

Schedules, retention and backup boundaries

Schedule backups with Tasks and select app data explicitly. Desktop app packages, data and grants are covered by the documented backup workflow. Off-site retention removes only EveryOS-owned older copies; a failed off-site copy does not invalidate the local backup. Local archives are unencrypted, while passphrase-protected .eosbak copies and downloads are encrypted. Arbitrary host directories, Linux home directories and volume-based app data are not automatically captured.

Based on EveryOS v0.1.38

View source · backups.md