
Did your Rust backup restore go into the wrong world?
If a second test world suddenly shows progress you meant to put somewhere else, stop changes to both affected worlds. Keep the original backup. Work out which location received the restored files and which location each running instance actually uses.
Record the selected target and the actual paths
Note the target shown in the restore result, its start time and which two worlds were set up. If players can still save to a suspect world, keep it closed using its normal stop process. With the worlds stopped, preserve a separate copy of the current folders before attempting repairs. Ask the host to preserve them if only the host can access those paths.
Facepunch documents that two Rust instances can share the installed game and use different server identities. Read the actual startup settings and install location for each instance. Record the identity folder and the game address beside each. The label you see in the browser can differ from the folder name.
Follow the time and one known piece of progress
For example, the panel shows the archive was written under the test identity at 18:40 UTC, and the folder under the practice identity was last written at 17:10 UTC. The timestamps are clues. Check each folder’s save and compare the intended checkpoint details with the archival contents before deciding which was replaced.
Verify in a further isolated target where you know the path, port and original source archive. Join that exact address and check a specific structure or blueprint from the dated backup. If two startup entries pointed to one folder, fix the test setup to use separate identities before diagnosing any other discrepancy. Leave the live world stopped until you can identify the correct recovery point and target without guessing.