ARK: Survival Ascended save loss: lost dinos, rollbacks and what backups actually recover
If a dino, a base or a day of progress has just vanished from your ARK: Survival Ascended server, the next ten minutes decide whether you get it back. Most permanent ASA losses are not caused by the original fault. They are caused by what the admin did after noticing it.
Do these two things first, in this order
- Stop the server. A running ASA server holds the world in memory and writes it to disk on a timer.
AutoSavePeriodMinutesdefaults to 15, so you are at most fifteen minutes from the damaged state being written over the last intact save. - Read the log before you restart. The server log is
ShooterGame/Saved/Logs/ShooterGame.log, and it rotates on restart. Restarting to "see what happens" destroys the fullest record of what already happened, so copy it elsewhere first and then read it.crashcallstack.txtand the datedServerGamelogs usually survive a restart, but they carry far less than the main log.
| What you do | What it costs you |
|---|---|
| Stop, copy the save tree, copy the log, then investigate | Ten minutes of downtime |
| Restart to see if it fixes itself | The log, and possibly the last good save |
| Leave it running while you ask around | One autosave every fifteen minutes, each writing the damage down |
Read the log properly rather than skimming it. ASA stamps a timestamped line for every player join and leave, so it tells you when the server last started, which is usually the moment your missing world stopped existing.
Why a dino disappears: seven different causes
These get conflated constantly, and they share nothing but the symptom. Work out which one you have before touching a backup: the remedy for one is actively harmful for another.
| Cause | How to tell it apart | What recovery looks like |
|---|---|---|
| The server rolled back to an earlier save | More than the dino is gone, and more than one player is affected. Structures, levels and inventories from the same window are also back. | A backup helps only if it is newer than the save the server loaded. Usually there is not one. |
| The dino died | The tribe log has a death entry. That is the authoritative record, and the first thing to check before any theory about corruption. | Nothing to restore. A backup from before the death takes everything else back too. |
| It wandered or was dragged out of render and starved | A starvation entry in the tribe log, often hours after you last saw it. Common with wandering on, with tames left on a raft, and after a base move. | Same as death. Preventable, not recoverable. |
| It was uploaded at an obelisk and expired | Nothing in the tribe log at all. The upload happened, the download never did. Governed by TributeDinoExpirationSeconds, short by default. | Expired uploads are deleted, not archived. Same failure as ASA character transfer deleted. |
| A mod that added the creature was removed or broke | Every creature from that mod is gone at once, and only those. Modded structures and items usually go with them. | Reinstalling the exact mod version can bring them back. See workshop mod broke after auto-update. |
| Tribe ownership changed | The creature still exists and admin dino listing commands will find it. It is just not yours: a tribe merge, a demotion, a rank change, a claimed tame. | An admin hands it back. Restoring a save here undoes unrelated progress for nothing. |
| Genuine save corruption | The world fails to load, or loads with sections nulled: whole tribes, whole regions, not one creature. The log shows the failure during map load. | This is what backups exist for. Restore the newest save that loads cleanly. |
An intact tribe log that shows nothing is itself information: the loss happened outside the log's reach, which points at a rollback, an expiry or a mod change rather than an in-world event.
What a rollback actually is
A rollback is not the server undoing your work. It is the server loading an older world file than the one you were playing in. Nothing was reversed, because the missing progress was never written to the file that got loaded.
Three things produce that:
- A crash before the next autosave. The server died between saves, and everything since the last one existed only in memory. At the default fifteen minute interval that is up to fifteen minutes of play for everyone online.
- A restore. Someone, possibly automation, put an older save in place deliberately. The one case where a rollback is a decision rather than an accident.
- A corrupted write. The save was interrupted mid-write, the file would not load, and the server fell back to an earlier copy. Storage filling up during a save is a common trigger.
The diagnostic is the shape of the loss. A rollback takes a clean slice of time from everybody. If one player lost one creature and nobody else lost anything, restoring a backup hurts six people to help one.
How ARK's save files are organised
Saves live under ShooterGame/Saved: world files in SavedArks, server settings in Config. On our platform the install sits at /home/<user>/arksa/, where bin/ holds the game binaries and data/Saved is symlinked in. That separation is why upgrading or reinstalling the dedicated server build, Steam app id 2430930, does not take the world with it.
| File | What it holds | What a mismatch looks like |
|---|---|---|
The map save, a .ark file named after the map | The world: terrain state, structures, tamed creatures, inventories | Restored alone, the base is there but nobody owns it |
.arkprofile files | One survivor each: level, engrams, stats, appearance | From the wrong point, a reverted survivor stands next to a level 100 base |
.arktribe files | Tribe membership, ranks, ownership, the tribe log | From the wrong point, ownership and permissions do not match the world |
| Server backup copies | Rotating copies written alongside the live save. How many are kept is MaxNumOfSaveBackups, default 20. The community wiki documents .bak copies written when the server last started. | Restored piecemeal, you get the flavours of loss above |
Config | Not world data, but rates, multipliers and rules | A world restored onto the wrong config reads to players as a settings wipe |
The rule that follows: restore the set, not the file. Pull the world, the profiles and the tribe data from the same moment, or you trade one loss for a stranger one.
One caveat. The community wiki documents a storage mode in which player and tribe data lives inside the map save rather than in separate files. If your save directory holds no .arkprofile files at all, that is the likely explanation, and the world file is the whole restore. The full reference is the official ARK Community Wiki server configuration page.
Restoring a backup without making it worse
- Stop the server and confirm it is actually stopped. Not restarting. Gone. A process still holding the save directory will overwrite whatever you put there.
- Copy the current broken state somewhere else before touching anything. The whole
Savedtree, not just the world file, named with today's date. This is the step people skip and the step that makes failure survivable: a restore that turns out worse than the damage is reversible only if this copy exists. - Pick the restore point by timestamp, not by filename. Check modification times and take the newest one comfortably before the event you are undoing, not the newest overall, which may already hold the damage.
- Put the matching set in place. World, profiles and tribe files from that same point. Copy them in, do not merge selectively.
- Match the build and the mod list to the restore point. A save from before a mod change will not load correctly against your current mod set.
- Start the server and connect as an admin, alone, before anyone else.
- Verify against something specific you know should exist. A named creature, a structure, a player level. "It loaded" is not verification. If it is wrong, stop and go back to the step 2 copy.
What a backup actually protects, honestly
A backup is a point in time. It cannot give back the period between that point and the failure, and no schedule ever will. The useful question is not whether you have backups, but how much progress you are willing to lose. That answer sets the interval.
Two limits before you rely on one:
- A backup taken from a running server can capture a half-written save. If the copy starts while the server is flushing the world to disk, the archive holds a file the game cannot load. Stopping the server, or taking a storage-level snapshot that captures the disk in one consistent instant, matters more than the schedule does.
- Retention is a deadline. Damage you do not notice inside the retention window is not recoverable from that set. Slow corruption and quiet griefing both work this way, which is why the tribe log is worth a weekly look.
We take daily snapshots on managed ASA servers. That is a real safety net and a real limit at once: daily means up to a day of progress at risk. Before a long breeding session or a significant change, take your own copy too.
Prevention, in three items
- Know where your saves are. Find the
Saveddirectory once, while nothing is wrong. Ten minutes now is worth an hour during an incident. - Take a copy before any mod change, settings change, or game update you can see coming. Those three events produce most of the losses in the table above, and all three are things you chose to do.
- Restore one before you need to. Stand up a throwaway server, restore a backup into it, confirm it loads and the tribes are intact. An untested backup is a guess.
Related reading
- ASA unofficial server backup strategy, the layered model
- ARK backup and restore guide
- ASA server will not start or crashes, when the world does not load
- Console save corruption recovery, single player and non-dedicated
- ASA server settings reference, save interval and backup count keys
- ASA dino commands, for finding tames that are no longer yours
- ASA breeding and taming rates
- ARK cluster setup, cluster transfer data lives outside the map save
Managed ARK: Survival Ascended server hosting. Supercraft runs ASA dedicated servers on AMD EPYC hardware with CurseForge mods, every released map, raw INI access, daily snapshots and four regions. Still on Survival Evolved? We run ARK: Survival Evolved servers too.