Skip to main content

Should two Rust worlds share one host?

Start with what you want players to be able to do when one host is unavailable. If the event world is your fallback during a main-world outage, keep it somewhere that can stay up independently. If both worlds can close together for maintenance, running them on one suitable host may be simpler.

Name the event that would take both out

Restarting a host interrupts every Rust process it runs. Two separate services on that host still depend on its power, storage and connection. Two rentals could also be on the same physical host or in the same location. Ask the provider what the two services share if the second one needs to stay reachable when the first fails.

Agree what you mean by a fallback. For an ordinary scheduled reboot, a second host may be enough. To keep an event running during an outage of one location, check the dependence on that location too.

Name the event that would take both out
WorldsReasonable decision
Main world and private practice worldShare a host if neither needs to stay available during the other's host work.
Main world and the world advertised as its fallbackChoose a separate host and check the particular outage you need it to survive.
Worlds for different groups with independent maintenanceDecide whether both groups can accept the same downtime before sharing a host.

Rehearse the route players would use

With spare instances, keep the intended fallback running while the primary test world is closed. Have a player follow your fallback join instructions from another network and confirm the expected world. Make any separate backups reachable without the primary host. Record the rehearsed condition. A stopped game demonstrates the join route, and provider information is needed to confirm the services do not share a host or location.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details