Restore points on uniz.host — getting last night's world back
Last updated November 13, 2026
A restore point is all the server's data at one moment — world, plugins, mods and settings. Take one from the server's Restore points tab, on a running or a stopped server of any game. To go back, stop the server, press Restore on the point and leave "Take a restore point of the current state first (recommended)" ticked; all the server's data returns to that moment, newer points stay, and the server stays stopped until you start it. A server keeps up to 10 points, each for 30 days, and loses them all when it is archived, made smaller or moved to a machine whose move also moves its storage. To keep one longer, export it and download the file within 3 days. A restore point is kept in the server's own storage, so it is not protection against failed storage hardware, and it does not include the server's databases.
- Stop the server first
- Pick the restore point by its date and time
- Leave the safety restore point ticked
- Start the server yourself once the restore finishes
On this page · 9 sections
Something has eaten your world: a mod update, a griefer, a build that was there last night and is not there now. The Restore points tab on a uniz.host server can put the server back the way it was. A restore point is all the server's data at one moment, so going back to one brings back the world, the plugins, the mods and the settings together. Read the first section before clicking anything.
Going back to a restore point
Open the server from /dashboard/servers, then its restore points tab. The list shows every point, newest first. Each row carries its name, how it was made (by you, automatically, or before a platform step such as a world trim), when it was made, how much the server stored then ("Server data": the world with the server jar, its libraries and plugins), and how many days it has left.
Stop the server first
A restore replaces all the server's data, and the game has the server's files open while it runs, so restoring is only allowed on a stopped server. Press Stop on the Overview tab and let the state settle. While the server is running the restore dialog says you must stop it first. While the platform itself is using the server's files, a restore cannot go through: during a world scan or trim, or while a file is being exported from it, it is refused straight away, and during a world import it fails after about a minute with the reason on the page. Try again once that job is done.
Pick the restore point by its date and time
Every row shows when it was made. That time, not the name, tells you whether you are going back to last night or last week. Naming a point when you take it, such as "before installing CoreProtect", makes this step much less nerve-racking.
Leave the safety restore point ticked
The confirm dialog has a box, "Take a restore point of the current state first (recommended)", ticked every time it opens. With it on, the platform takes a restore point of the server as it is right now and only then goes back. That is your way back if the older world turns out to be the wrong one. Restore points newer than the one you go back to are not removed either.
Start the server yourself once the restore finishes
When the restore is done the server stays stopped. Nothing starts it for you. Press Start when you are ready. If the restore fails, the server stays stopped with the error on the page. The restore point you made first is on the list, so you can go back to it.
Taking a restore point
Press "Create a restore point" on the tab. A name is optional. A restore point takes seconds, and it can be taken while the server is online, on every game. A point taken while the server runs holds what the game had saved at that moment, so anything that only existed in memory is not in it. Because a point holds all the server's data, on Palworld it also holds the mod .pak files you placed in the mods folder. If the point is not ready straight away, its row reads as being made, and the platform finishes it within about a minute.
A server holds up to 10 restore points. With 10 already there, the dialog tells you which one goes: the oldest is removed once the new one exists.
How long a restore point lasts, and what ends it
A restore point is removed:
- 30 days after it was made;
- when the server already has 10 and a new one is made (the oldest goes);
- when the restore points' space is full: the server's data and its restore points together may use at most twice the storage of its plan, and past that points are removed, usually the oldest first, until it fits. The newest point is never removed for space;
- when the server is archived, made smaller, or moved to another machine whose move also moves its storage. The confirm dialog of a size change or a move says so before you press it;
- when you delete it, or delete the server.
A restore point is kept on the server's own storage. It is a way back after something that happened in the game, not protection against failed storage hardware. It also does not include the server's databases (the MySQL or MariaDB databases you create for a Minecraft server). For a copy that is off the platform, export a file.
Keeping a copy longer: exporting a file
Download needs a file, so on a restore point you first press "Export". The platform creates a .tar.zst archive from that point, the same format a backup always had. It takes a while, depending on the size of the server's data, and the server can be played meanwhile. You can close the page: the file waits on the tab. Its row goes from queued to "Creating file…" to "Ready to download", or to "Could not create the file" with the reason and a retry.
A server has one exported file at a time; exporting a new one replaces the old one. While the platform's file store is more than 90% full, exporting is refused for a while; try again later. An exported file is kept 3 days, then removed. When it reads ready to download, press Download. The link is the credential, so do not share it; if the download drops, resume it in your browser or press Download again.
An exported file is for downloading. To put the server back to that moment while the point still exists, restore the point itself.
Bringing a file in: import
"Import file" takes a .tar.zst archive you hold: a world exported from elsewhere, or a file you exported here earlier. It may not be larger than the server's own storage. Importing needs the server's owner to have topped up with real money at least once. A server has one imported file at a time; a new import replaces the old one. An import is also refused for a while when the platform's file store is more than 90% full. An imported file is kept 3 days, and "Restore from file" replaces the server's current data with the data in the file, with the same safety option as a restore point. Restoring from a file also needs the server stopped.
Old backups
Backups made before restore points started stay on the tab under "Old backup". They still restore, download and delete as before, they do not count toward the 10 restore points, and they are deleted 30 days after they were made. No new backup of the old kind is made.
The automatic schedule
The schedule card is off until you turn it on, and it now makes restore points. Its times and options are the same as before: every few hours or once a day at a Thai-time hour, skip when nobody has played since the last point, make one when the last player leaves, or wait until the server is empty. There is no "how many to keep" setting: automatic points share the server's 10 with the ones you take.
Who is allowed to do all this
The tab is visible to the server's owner and to team members with the Backups permission, which covers taking, restoring, exporting, downloading, importing and deleting, and the schedule. Restoring needs the server stopped, and stopping it needs the Power permission, so a member with backups alone cannot finish a restore.
Read next
- Archived servers — what happens to restore points when a server is archived, and how to download its archive
- Dashboard tour — what every tab on the server page is for
- Running a Minecraft server — where the files a restore point holds come from
Frequently asked questions
Can I undo a restore?
Yes, as long as the safety option was ticked. It makes a restore point of the server as it is right now before going back, and restore points newer than the one you went back to also stay. To return to where you were, stop the server and restore that safety point.
Why can't I press Restore while the server is running?
A restore puts all the server's data back, and the game has the server's files open while it runs. Stop the server from the Overview tab, wait for it to read stopped, then restore. Taking a restore point does not need a stop.
Is a restore point a backup I can rely on if the hardware fails?
No. It is kept on the server's own storage, so it protects you from what happens in the game (a griefer, a bad mod, a mistake), not from failed storage hardware. For a copy that is off the platform, export a file and download it.
Are my MySQL or MariaDB databases in a restore point?
No. The databases you create for a Minecraft server live outside the server's storage, so a restore point does not hold them and a restore does not change them. Keep your own copies of anything in them that matters.
What happened to my old backups?
Backups made before restore points started stay on the tab marked "Old backup". You can still restore, download and delete them. They do not count toward the 10 points and are deleted 30 days after they were made.
Related guides
Would you rather skip all of this?
A server on uniz.host is up in minutes. You pay by the hour only while it is online, and the smallest top-up is ฿20.