Migration and copying

Moving a server to another Node

Move to another Node… in a server’s actions menu moves its data and keeps everything else: its name, history, backups and, where possible, its port. The target Node must be enabled, connected and healthy, with room for the server.

The server stops, its data travels from the old Node to the new one through the Controller (Nodes never connect to each other), and it starts on the new Node. If the move fails, the server goes back to the old Node as it was. If the port is taken on the new Node, it gets a new one, shown when the move starts.

Servers in the network need nothing else: the proxy follows them. Servers joined directly have a new address: the new Node’s.

Copying to another server

Copy to another server… in a server’s actions menu copies chosen parts of one server into another: the world, player data, settings (except those Shardkeep manages), configuration, plugin configuration, player lists (whitelist, operators, bans) and schedules. The source keeps running. Use it to build a test copy, or to start a new server from an existing world.

A world from a newer Minecraft version cannot be cloned into an older server.