
What to bring when restoring a Rust backup from Windows to Linux
Use a clean Linux game install and move the backed-up server data into it. Recreate the launch settings for Linux so the game opens the correct Rust server identity and can write its next save.
Separate data from the old host's setup
Keep a private copy of the Windows launch file or panel settings. It tells you the identity, map settings and other startup values. Install a compatible Rust dedicated server build and matching framework for Linux. Use their Linux startup method. Review the old plugin versions and instructions for any dependencies that also need a Linux version.
| From the Windows backup | What to check on Linux |
|---|---|
| Active identity folder | Use the same identity name and capitalization. Preserve the matching map and save file names. |
| Custom map and plugin paths | Use paths on the new host. Keep the filename capitalization exact, including plugin config and data references. |
| Files the game writes | Make sure the account running Rust on Linux can read its settings and write in its save and plugin data folders. |
Check the first save as well as the first start
If the old identity folder is Coast but you pass +server.identity coast, Linux can treat those as separate folders. Fix the launch setting in a test install before copying more data. If the game opens the old world but cannot save, check access to the restored folders for the account running it. Recheck with the same account that will run the real service.
Keep the Windows data untouched. Start the Linux copy with ports reachable only by testers, Rust+ disabled and any shared plugin databases or webhooks pointed at test services. Join the Linux copy and check a known landmark. Make one small change in the test world. Let the game save and confirm the change survives a restart and that the updated save is in the intended identity folder.
Move the last live save when the test passes
If the Windows server stayed open during testing, it now holds newer play. Arrange a clean stop and take a final backup after the game and other writers exit. Stop the Linux test server and move its test data aside. Restore the final Windows data into an empty destination for the active identity and any plugin data you are moving, so files created during rehearsal stay out of the real world.
Keep the Linux launch settings you tested. Set the production connection details and reconnect the integrations you intend to use. Keep the Windows server off and its files intact. On Linux, verify the latest known world change, any affected plugin records and the next save before inviting players to the replacement.