# Compare Rust server managers with one real job

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md)

Pick the job you would buy a tool to make easier. Run it from start to finish on your own spare server. If the job is ‘get a stopped Rust server back online from my phone,’ opening the console or seeing the server’s name only gets you part of the way.

## Write down the start and the finish

For a Sunday morning recovery, start with a spare Rust world deliberately stopped, the host online, and you away from the desktop. Finish when a second person can load into the right world. Use the same account role, phone and starting conditions in each test, including a run with your existing tools.

The game’s remote console only answers while Rust can receive the connection. If you need to start a stopped game, check what access the candidate needs to reach the host or rental panel. A demo only counts once you can give the tool the access it needs.

## Mark the steps you cannot leave to someone else

Write a single must-have before starting. For example, “I must be able to start the stopped world and confirm a player can join without calling someone at home.” Keep optional conveniences, such as viewing more of the startup log on the same screen, in a separate column.

| Phone recovery test | Must-have result | Extra steps |
| --- | --- | --- |
| Current dashboard | Started and Mo joined | Opened console on a separate screen |
| Tool A | Started and Mo joined | Read startup output in the same screen |
| Tool B | Could see that Rust was stopped | Needed a second person to start it |

## Decide from the missing step

In this example the current dashboard and Tool A both pass the must-have. If the extra console screen is hard to use on your phone, repeat that part at the next rehearsal and decide whether Tool A saves enough effort to change tools. Tool B may work for a different job, such as reading the console while Rust is running.

Leave one line for each test with the server type, connection you used and a visible result. If you move hosts or change a required account role later, repeat the same job and compare with that record.

## Sources

- [Facepunch Rust server startup and remote console settings](https://wiki.facepunch.com/rust/Creating-a-server)
- [Google Cloud guidance on testing recovery scenarios](https://docs.cloud.google.com/architecture/framework/reliability/perform-testing-for-recovery-from-failures)

## Related resources

- [Will a Rust management tool do the same jobs on both your hosts?](https://rustsc.com/learn/hosting/test-a-rust-management-tool-on-different-hosts/index.html.md)
- [What can you still do when your Rust dashboard is unavailable?](https://rustsc.com/learn/management/manage-rust-without-the-usual-dashboard/index.html.md)

---

HTML version: https://rustsc.com/learn/management/compare-rust-server-managers-with-one-workflow/
