Rollback & Backup Tools

When a player destroys a build, the fix is not to restore yesterday's world, which would also undo everyone else's work. The fix is to reverse exactly what that player did. A rollback plugin logs every block placed or broken, container changes and some entity actions, and lets staff reverse them by player, area and time. CoreProtect does this and keeps its log in a database, so staff can inspect what happened before they undo it.

A backup protects against what the log cannot: a corrupted world, a crashed disk, a bad update or a plugin that changed files directly. DriveBackupV2 creates backups on a schedule and uploads them to cloud storage or a file server, so the copy survives the death of the machine the server runs on.

Use both and test them. Practise a rollback on a test world before you need one, and restore a backup to a fresh server at least once, because a backup that has never been restored is an assumption.

Decide how long you keep each. Logs grow quickly on busy servers, so set a purge schedule, and keep several generations of backups, not just the latest one.

Does a rollback plugin replace backups? No. It reverses logged actions. A backup restores files, including damage that was never logged.

Where should backups be stored? Off the machine that runs the server. A backup on the same disk is lost with the disk.