Import and restore worlds
Move a Java save into Nova, or recover a verified backup without overwriting the original volume.
These actions require an approved hosting account, a connected runtime and private backup storage. They do not bypass the pilot's capacity limit. Start with a disposable world: a successful build is not a successful restore drill.
Import an existing world
First create a world with the same Minecraft version and server type as the save.
In its Settings, open the import/restore section and choose your ZIP archive.
The initial upload limit is 50 MiB compressed. The archive must contain a Java
world save, including level.dat, at the root or inside one wrapping folder.
Upload save files, not a whole server installation. Executable files, plugins, server settings, credentials, symbolic links, traversal paths and oversized archives are rejected. Configure required Fabric mods through Nova before importing. Forge/Bedrock worlds and arbitrary modpack uploads are not supported. Keep your own copy; converting to a newer Minecraft version is not a reversible migration service.
Review the operation before confirming. Nova backs up the current save, extracts into a fresh volume, then switches the server to that volume. It retains the old volume; it does not overwrite the only copy. Extra storage quota is required for both volumes, and a quota failure must be resolved by the operator.
Restore a backup
Settings lists verified backup records for that world. Select the intended snapshot and confirm the restore. Restoring changes world progress and may restore an older saved configuration; players should disconnect first. Nova checks archive integrity and restores into fresh storage, retaining the previous volume. A failed startup is not automatically rolled back.
Backups containing datapacks or unsupported mod-specific save files require operator-assisted restore. Nova fails that restore rather than silently omitting those files and presenting a partial world as recovered.
Only backups associated with your world are accepted. There is no arbitrary download URL, bucket path or public backup link to paste. A retained volume is not a browsable backup or an unlimited retention promise. Operators must define and monitor S3 retention and remove obsolete upload objects, completed Jobs and unused recovery volumes according to their published policy.
After importing or restoring
Wait for the operation to settle, inspect the console, and join with a real Minecraft client. Confirm important builds, inventories and dimensions before resuming play. Keep the original until this check succeeds. If an operation is interrupted, use its explicit recovery action; never delete mutation locks or storage manually while a worker may still be active.