Cloning

Cloning creates a new server from an existing one: a second deployment of the same setup, or a duplicate of a configured world.

Prerequisites

The server.clone permission (legacy server.create grants still work) and access to the source server.
To clone onto another node, server.transfer and access to that node.
For a full clone, the source server stopped — the dialog offers Stop source and continue if it is running.

Choose a clone mode

Both modes copy the panel configuration: template, variables, startup command, resource limits, network mode, backup policy and restart policy. They differ in what happens to the files.

	Full clone	Configuration clone
Panel configuration	Copied	Copied
Server files (world, plugins, configs)	Copied	Not copied
Install after cloning	No — files are already there	Yes — the template installer runs
Source server must be stopped	Yes	No

Use a full clone to duplicate a live world or a hand-configured modpack. Use a configuration clone for another server with the same settings but a clean installation.

Clone a server

Open the server, then Settings, and find the Maintenance row.
Select Clone.
Choose the mode — the dialog starts on Configuration clone.
Give the new server a name (it defaults to the source name plus Copy).
Choose the node it will be created on.
Choose the network mode. For host or bridge networking, optionally pick a Network Allocation; otherwise leave it on Auto-assign.
Adjust memory, CPU and disk if the clone should differ. Panel administrators can also set the clone’s Server Owner; otherwise you own it.
Tick what else to copy under Also copy — Sub-users, Role grants, Scheduled tasks, Databases and Installed mods. Tasks, databases and installed-mod records are off by default: two servers running the same task can conflict, a copied database is provisioned empty rather than shared, and a full clone already copies the mod files.
Select Review changes, review the change list, tick any warnings, then confirm.

Confirm the node-specific changes

Cloning onto a different node re-resolves everything tied to the node, and the panel creates nothing until you have reviewed and accepted those changes:

Node and location.
IP address — a fresh IP from the new node’s pool, or the allocation you chose.
Primary port and port mappings — host ports are reassigned so the clone cannot collide with a server already on the node.
Data directory — the new node stores server data under its own path.
SFTP endpoint — the clone is reachable on the target node’s hostname and port.

If something blocks the clone — the node is offline, it does not support the network mode, it lacks memory, CPU or free disk space, or no allocation is free — the panel lists it as a blocker and will not continue until it is resolved.

The confirmation is bound to the changes you reviewed: if the options change between the review and the confirmation (for example someone else claims the allocation you picked), the panel discards the review and asks you to review again.

While the clone is created

A configuration clone starts installing immediately. Watch progress in the console, exactly like a new server.
A full clone sits in a Cloning state while its files are copied and cannot be started until the copy finishes. Large servers and cross-node clones take longer.

If a file copy fails, the new server is left in place and stopped, with the reason in its console log. Delete it and run the clone again.

What is not copied

Backup archives and the backup list — backups belong to the source server.
Database contents. A clone can create a new, empty database when you tick Databases; it never points at the source database.
Logs, metrics and crash history. Every clone starts with a clean history.
Backup storage credentials. The clone falls back to local backup storage instead of inheriting S3 or SFTP credentials.

After cloning

Start the new server and confirm it boots.
Check the connection details — the address and port are node-specific, so they may differ from the source (networking).
If you copied databases, reconnect the application inside the server to its new database and credentials.

Networking — the clone’s address and ports
Backups — the clone never inherits the source’s backups
Tasks — tasks are not copied unless you tick them