GuidesOnly show guides for your app
GuidesGuidesHow Falix backups work on free and premium plans — creating, locking, restoring, downloading, and automating them so a bad change never costs you your world or project.
A backup is a full snapshot of your server's files that you can roll back to later. Take one before any change you're unsure about, and a broken world, a bad plugin update, or a fat-fingered delete turns into a two-minute fix instead of a disaster. Open Backups from your server menu to get started.
| At a glance | |
|---|---|
| You need | Any Falix server |
| Plan | Free saves to your own Google Drive; premium stores backups for you |
| Time | Five minutes to make your first one |
This is the one big difference between plans, so it's worth knowing up front.
| Free | Premium | |
|---|---|---|
| Where they live | Your own Google Drive | On the node, alongside your server |
| Setup | Connect a Google account the first time you open the page | None — stored for you |
| Counts against a limit? | No — they're your own files | Yes, typically around 5 |
| When the limit is full | No limit | Oldest unlocked backup is auto-deleted; locked ones never are |
Press Create and you'll see a few optional fields:
🎯 Good to know: There's a light cooldown — at most 2 backups every 10 minutes, so you can't accidentally spam them.
How long it takes depends entirely on how much data you have: a small bot project is done in seconds, a large modded world with gigabytes of files takes a few minutes. The server keeps running the whole time, so there's nothing to wait around for.
Restoring puts the saved files back onto your server. You get two modes:
One toggle changes everything: Delete all files before restoring.
⚠️ Heads up: A restore overwrites live data, so you have to type
RESTOREto confirm. Take a fresh backup first if the current state has anything worth keeping.
You can start a restore whether the server is up or down, with one condition: it can't already be busy with another job — an install, a transfer, or another restore. If it is, the panel tells you the server "is not currently in a state that allows for a backup to be restored"; wait for the other job to finish and try again. While the restore runs, the server drops into a restoring state and isn't usable, then returns to normal on its own when it's done. For a clean restore of a live world or database, stop the server first so nothing is writing files as they're swapped out.
⚠️ Heads up: Do backups survive deleting the server? It depends on where they live. Free-plan backups sit in your own Google Drive, so deleting the server doesn't touch them — they're yours to keep. Premium backups are stored on the node alongside the server, so deleting the server takes them with it. Before you delete a premium server, download anything you want to keep, or restore it onto another server first.
You don't have to remember to do this by hand. The Backups page has an Auto tab for scheduled snapshots, and the Backup task on the Schedules page can fold a backup into any routine — take one every night at 4 AM, or right before a scheduled restart. Set it once and you always have a recent snapshot.
Make a backup before anything that touches a lot of files at once: