Inventory the moving pieces
Record the game version, server implementation, plugins or mods and the configuration that connects them. Read the relevant release and compatibility notes before changing versions. A successful download says nothing about whether the full combination will work.
Keep the current release identifiable. If a problem appears later, the administrator should be able to say exactly which version was installed, rather than describing it as whatever was newest at the time.
Protect the world before the change
Use the backup method recommended for the server and storage you operate. Stop writes or follow the platform’s documented consistent-backup procedure. Keep the backup outside the live working directory so replacing the installation does not remove your recovery copy.
Restore a sample into an isolated test instance when practical. Check a known build, player data and any plugin-specific information. A backup file existing on disk is only the starting point of the recovery check.
Test the complete release
Start the updated server with a copy of the data and review its output. Exercise the functions players rely on: joining, permissions, travel and any important plugin features. Keep the test server from accidentally replacing or writing to live data.
Schedule the production change with a clear message to players. Confirm the post-update checks and retain the previous release. PaperMC’s updating documentation gives platform-specific guidance; other server software can have different requirements, especially when world data changes format.
Keep in mind
- Record versions and dependencies
- Make a consistent backup
- Test on a separate instance
- Keep a clear rollback decision