Several Servers: Groups and Migrate
When you run more than one Rust server, the Groups and Migrate tabs of the Game servers page help you keep them consistent.
Groups
- Server groups: tag your servers (by region, by mode…). A group filters the network view, receives announcements and commands, and can be the target of a copy or an automation. A server can also join a group (or create one) from the Groups tab of its own page.
- Copy settings to other servers: pick a server, what to copy (wipe schedule, listing, or the automations of that server) and the target servers or a group. Each target shows what will change before you copy. The server name is never copied. For a wipe schedule, you can keep each server's own time zone and offset.
Migrate
Migrate copies what you choose from one server (From, A) onto another (To, B), for example to set up a new server like an existing one.
Migrating overwrites data on the target server. Plugin configs, settings, the wipe schedule and automations of B are replaced and cannot be restored afterwards. Replaced plugin files are kept in
plugins/backups. Nothing that only B has is removed, and B's name, map, connection, players and bans are never touched.
Pick the two servers, then tick what to copy. Only what differs is on by default; Tick every difference selects everything that can be copied.
| Section | What you see | What a tick copies onto B |
|---|---|---|
| Plugins | Every plugin of both servers with its version and state | The same .cs file as A (also works for Codefling and private plugins), then the plugin is loaded |
| Plugin configs | After Check configs: the plugins whose config differs (Show keys lists the keys) | A's config file, then the plugin is reloaded |
| Settings | Name, map, framework, identity, max players, PvE, save interval, FPS limit, listing (description, website, images, tags) | Max players, PvE, save interval, FPS limit and the listing: sent over RCON and saved in the server config. Name, map, identity and ports stay each server's own. |
| Wipe schedule | The fields that differ | A's wipe schedule |
| Automations | A's own automations that B lacks or has differently | A's automations, added or replacing B's automation of the same kind |
| Linking commands | A's linking commands that B does not have (needs the right to edit the project) | The missing commands, added next to B's own (B's are kept). Linked players get them at their next connection to B. A command for Oxide (oxide.) copied to a Carbon server is flagged: Carbon does not run it. |
Migrate asks for confirmation, then shows the result of each item. Items that failed stay ticked so you can retry.
Good to know:
- Settings come from what the Control Center reads every few minutes. A server it has not read yet (offline, never connected) shows Not read yet, and nothing is copied from it.
- Plugins and configs need Oxide or Carbon on both servers, and host access (Pterodactyl, Pelican, WISP, AMP or SFTP / FTP).
- A copied wipe schedule keeps the auto-wipe system on only on servers with RCON and a Pterodactyl, Pelican, WISP or AMP panel; elsewhere it arrives turned off.
- Each item checks your role on the target server (plugins, files, settings, wipes or automations) and your plan. Every migration is written in the Activity log.
Related Articles
Auto-wipe system
Schedule your wipes with rules, follow the forced wipe, skip or change one wipe, simulate,...
Plugins and Files
See loaded and failed plugins, search, install and update uMod and Codefling plugins in on...
Automations
Scheduled tasks, chat answers, rules on players and events, restarts with countdown, VIP t...