GuidesOnly show guides for your app
GuidesGuidesBackups are simple until one won't create, won't delete, or restores the wrong thing. Here's each snag — the cooldown, locks, the free-plan Google Drive step, and the one restore toggle everyone gets wrong.
Backups on Falix are one button — right up until one won't create, refuses to delete, or restores something other than what you expected. Every one of those has a specific setting behind it. This guide is the short list, symptom first.
| At a glance | |
|---|---|
| You need | The server's Backups page |
| The gotcha | Most "it didn't work" restores are the Delete all files toggle — jump to Restore below |
| Symptom | Cause | Fix |
|---|---|---|
| Free plan: it asks you to connect Google | Free-plan backups store in your own Google Drive | Connect a Google account when the page prompts — that's where free backups live (and they don't count against a limit) |
| "Please wait before creating another backup" | Cooldown: at most 2 backups per 10 minutes | Wait out the cooldown |
| Premium: it won't make a new one | Your backup limit is full and every backup is locked | A new backup auto-deletes the oldest unlocked one — if all are locked, unlock one or delete manually |
🎯 Good to know: Free and premium store backups in different places. Free → your Google Drive (no limit, but you must connect it). Premium → the node, counted against your plan's backup limit (typically 5). When a premium limit is full, creating a new backup removes the oldest unlocked one to make room.
This is where nearly all restore confusion lives, and it's one toggle:
"Delete all files before restoring."
Pick based on what you want: merge the backup in (off) or rewind completely (on).
Other restore facts worth knowing:
RESTORE to confirm — a restore overwrites live files, so it's deliberately hard to trigger by accident.💡 Tip: Stop the server before a full restore. Restoring over files an app is actively writing can leave you with a half-old, half-new mess; a quick Stop → Restore → Start avoids it.
If a restored backup is missing files, they were probably excluded when the backup was made. Backup creation takes optional exclude patterns (one per line) — a pattern like logs/ or *.tmp keeps those out of the backup, so they can't come back in a restore. Check what the backup actually contains before assuming the restore dropped them.
| Free | Premium | |
|---|---|---|
| Where backups live | Your Google Drive (connect first) | On the node |
| Counted against a limit? | No | Yes (plan-dependent, e.g. 5) |
| When full | n/a | Oldest unlocked backup is auto-deleted |
| Cooldown | 2 per 10 minutes | 2 per 10 minutes |