
Did your Rust backup finish copying over a slow connection?
Keep the source archive while the transfer finishes. Confirm the copy matches the finished source. Then open or extract it separately and check a file you need for recovery.
Match the bytes before you start over
Wait for the transfer tool to say it finished. Check the exact byte count of the source and destination if both are accessible. If they differ, check whether the tool can resume the same transfer. Keep an incomplete download under a name or in a folder that nobody will mistake for a finished backup.
Equal sizes do not prove the files match. If you can compute a SHA-256 value on each side, compare the complete value for the finished archives using the same algorithm. PowerShell's Get-FileHash can compute that value. If the host only offers a downloadable file, ask whether it provides a trusted value for that exact archive. If you cannot verify against the original, keep that uncertainty and do the extraction check.
Open the copy away from the live game
Use the archive tool’s integrity check if available, or extract to an empty location with room for the contents. Find the save for the world and one other item you expect, such as the matching custom map or plugin configuration. A successful file comparison tells you the transfer preserved the archive. A test restore shows whether the archive can bring the game back.
If the copy fails verification, leave any previous good copy alone and try a fresh transfer. Write the source date, copy location and last successful check in your recovery notes.