
What to keep for Rust+ when restoring the same server
For a manual move of the same server, keep its Rust+ identity and pairing data with the world. An independent test or new server should have its own Rust+ identity.
Keep the Rust+ files with their own server
Facepunch identifies companion.id as the file Rust+ uses to identify the server. The player.tokens files hold players' pairing tokens. Keep them private. When restoring the same server, check that the backup includes these files and that they are from that server. A point from before a player paired may lack that player's current token.
Rehearse the move with Rust+ disabled before the test copy first starts. If you edit the test copy’s server.cfg yourself, add app.port -1 or replace the existing value. Confirm the test client’s Rust+ menu shows it is disabled. Keep the original pairing files in your backup. Bring the restored identity online only when the original instance is stopped and you are bringing the same server back.
Check the app after the real cutover
If the game works but Rust+ shows the server as offline, check the companion address and port reported by app.info. A move can change where the app needs to connect. Check that the new host exposes the intended Rust+ port and that the app can reach it before you change any saved pairing files.
Try the existing pairing with one player. If their pairing is gone after an older restore, ask that player to pair again and check the app can connect. Keep the recovery copy and the original pairing files while diagnosing the issue.