
01 · Back up before a big change
Before changing your world, software or plugins, create a copy and wait for it to finish. An automatic schedule is optional and starts off. A queued request is not a saved backup.
02 · Use Manage and your Google Drive
New customer backups are saved in your personal Google Drive, rather than new shared ChunkArc backup slots. Previous ChunkArc copies remain available to download or restore. Internal backups of Panel, website and database are separate.
03 · Create a copy in Drive
Connect once, then choose manual or scheduled copies
- Open Backups in Manage and connect Google Drive. Complete Google sign-in and consent yourself.
- Stop the server normally when convenient, then choose Back up to Drive. Requests wait for the server to be off; they never stop players. A request that has not started expires after 15 minutes.
- Wait for Saved in Drive and open the verified copy. The limit is 5 GiB per copy; your Google storage and service transfer limits apply.
- For automatic copies, select 6, 12 or 24 hours and save the schedule. Pause it at any time. A running server can delay the copy beyond its due time.
No fixed limit on the number of copies in your personal Google Drive, within your available storage and service limits.
Keep all copies by default, or explicitly keep 3, 7 or 14 new automatic copies. Retention excludes manual and previous ChunkArc copies. Older automatic copies go to Google Trash: they still use storage and are normally permanently deleted after 30 days. Disconnecting does not delete completed copies.
ChunkArc requests access only to files used with this integration, not your whole Drive. Keep a separate copy of important progress and label it with the server version.
04 · Restore carefully
Stop the server, select a verified Drive copy, review the restore and explicitly confirm replacing the current files. A restore replaces the complete saved server file set, including worlds, settings and plugins. Newer progress can be lost.
The service checks the copy and prepares a temporary rollback image before applying it. A failed or interrupted operation may require operator recovery; do not remove a safety block manually. After a completed restore, start the server yourself and check the expected world before inviting players back.