01 Define what must survive
List world saves, player data, configuration, access lists and the mod or plugin manifest. Record the server build and operating environment too. A world folder alone may not reproduce a modded server. Store passwords separately from public troubleshooting notes.
02 Take a consistent copy
Use the game’s documented save and backup procedure. If you cannot establish a consistent live backup, arrange downtime and stop cleanly before copying. Keep a dated copy outside the active server directory and, where practical, outside the same machine or provider account.
03 Restore somewhere separate
Create a separate test directory or isolated instance. Use compatible server software and restore the saved files there. Do not test by overwriting your only working world. Prevent the test instance from accepting public players until validation is complete.
04 Record the result
Check the world name, a known structure, player progress and permissions. Record the time needed to restore and the timestamp of the newest recovered change. Those observations tell you how long a recovery takes and how much progress could be lost. Repeat after changing save formats or major versions.