Here is a scenario that happens more often than anyone wants to admit.
Your server runs a scheduled backup. The backup completes. Green checkmark. Success.
Three weeks later, you restore that backup. The world loads. And then it does not. The save file is corrupted. Half the map is missing. The backup was "successful" in the same way that photographing a document mid-shred produces a "successful" photo.
This happens because most backup systems do not care what state your files are in when they grab them. If your game server is mid-save and the backup scoops up a file while it is being written, you get half a file. The backup tool did its job. The file was just garbage at the moment it was copied.
The insidious part is that you cannot tell by looking at the backup. It has the right file names. It has a reasonable file size. It compresses fine. Every system along the way reports success. You only find out the backup is broken when you try to use it, which is the worst possible time to find out.
Checkpoint™ is built into every backup on Pink Narwhal. It is not a setting. It is not a toggle. It is just how backups work here.
Before the backup starts, Checkpoint™ coordinates with your game server. It knows what game you are running through our Smart Profiles system and ensures everything is written to disk cleanly before a single file is touched. The server finishes what it is doing, flushes its state, and holds still. Different games need different coordination. Checkpoint™ handles this per game, automatically. You do not configure anything.
During the backup, Checkpoint™ independently verifies that the files it captured are consistent. If something unexpected happens, it catches it and handles it automatically. No manual intervention. No notification spam. It just resolves the issue and moves on.
After the backup, Checkpoint™ tells the game server to resume normal operations. Your players do not notice. The whole process adds a few seconds to your backup time.
The result: every backup that completes is a backup you can actually use.
Checkpoint™ does not stop at the archive.
Every backup is cryptographically verified as it streams to cloud storage. Before any restore, that verification is checked again. If the data in storage does not match what was originally uploaded, the restore will not proceed. You get a clear error instead of a silently broken server.
For large servers, backups are automatically split into smaller pieces. Each piece is independently verified. A single corrupted piece does not silently poison your entire restore. It gets caught and flagged before anything touches your server.
The integrity chain runs from the moment your files are captured to the moment they land back on your server. No gaps.
Smart Profiles cover the popular games out of the box. But if you are running something unusual or you have a custom setup, Checkpoint™ still protects your backups with the full integrity chain. Cryptographic verification, chunked backup support, and pre-restore validation all apply regardless of profile type.
For game-specific save coordination, Smart Profiles handle that automatically. Custom profiles can also use save commands if you have configured them in your game profile.
If a backup says it completed, it is clean. That is the whole point.
Was this article helpful?
On this page