MineBackup
MineBackup - Automatically save and backup your server!
Features
- Numerous backup actions: Save (default); Copy and/or Compress. The copy action creates a copy of files in backup folder while the compress action creates a zip of files in backup folder. You do not need to enable both for compress to work.
- Numerous upload actions: Dropbox; FTP. These actions will upload the latest compressed version, so you will need to be using compression.
- Maintenance action: Cleanup. With this action enabled, old backups will only be deleted as scheduled (otherwise they will be deleted after a copy/compress action).
- Each action has a configurable interval. You can even set a specific time that an action should trigger (only once per day). Every action supports either method.
- You can either enable actions globally (default for all worlds) or enable/disable actions for specific worlds. Specific worlds can even have different time intervals for each action!
- Global or per world configurable amount of backups to be kept on disc. So a world that is rarely used can be compressed every few hours and set to have less copies retained.
- Global or per world configurable broadcast of backup status.
- Setting to enable an immediate backup on server restart/reload with configurable delay. With this disabled (default), scheduled actions will occur at their proper time, but if the server was stopped during that time, then it will run as soon as possible.
- Backup actions are staggered to try to prevent low-powered servers from getting overloaded. Instead of checking every world at one time and in order, a queue is checked once a minute to see if it needs to do a backup action.
- If no one has used the world since the last backup ("not dirty") then its actions are skipped.
- Able to backup plugins/other directories with a list of excluded paths (like dynmap's /tiles) and file types.
- Customizable messages. Everything sent to players is able to be translated or changed. Including broadcast groups.
- Configuration migration with a backup copy of the original configuration.
Caution
Does your server have a single-core processor or a low amount of memory (512mb and several plugins)?
Do NOT enable compression! Only enable copy.
Does your server operate over a typical home internet connection?
Do NOT enable dropbox or ftp!
Failure to understand this will almost certainly result in all of your players being disconnected.
Notes
[v0.5+] Due to changes to the old backup deletion code, the plugin will not automatically delete any v0.4 backups. You will need to manually delete them at an appropriate time.
[v5.9.2+] If you still have the old map format (world height 128) files in your world folders, it's going to yell at you on server startup. Once you have a backup of the world, delete level.dat_mcr and the *.mcr files in the region folder. They aren't needed after the conversion and double the size/time of the backup.
[v5.9.3+] Enable 'debug' in config.yml for a detailed list of the settings that are being used as each world/plugins is loaded. (Exact times are seconds from midnight, but stored as a negative number.)
Setup & Usage
Only save is enabled by default. You need to enable either 'copy' or 'compress'.
Download
MineBackup.jar (for auto-updaters)
Source
Default Config (created first start)
Default Strings (created first start)
Dropbox Linker (Google App Engine)
Credits
ThisIsAreku for the original MineBackup. This plugin has now been completely re-imagined and rewritten. The only thing untouched and unchanged is the name itself.
@Doctacosa: Looking at the config that you pasted you are only backing up 3 worlds that have the name of "yourworldname", "yourworldname_nether" and "yourworldname_the_end"
Unless you world is called "yourworldname" (default of world) it will not be saved. Try updating these labels to match your server configuration.
Is the save feature essentially the /save-all command?
@ltguide: Yes, 1 backup is correct. I don't have enough room on the server to store more than one copy, as the world is getting quite large. I'd expect that backup copy to stick around right up to the point where the next one would be generated, right?
As for the server restart, I don't send a manual "stop" command but I see in the console that all plugins are shutting themselves down properly. However, sending that command directly (without having MineBackup installed) does provide me with a "Saving chunks" message that I didn't notice before. I'll have to try this again with the plugin installed, perhaps the restart was happening too fast for it to do it's job properly...
EDIT: I figured out the save loss problem. It turns out that the control panel's restart button works too fast: the server is restarted before it had time to write everything to disk, so recent changes were lost. Issuing a /save-all followed by a /stop, THEN a restart does the trick. Hopefully, I'll be good to go from there. I've re-enabled the plugin, and will see how it behaves from now on. :)
@ltguide
thats my problem. i have already set prepend-world to false and the root of the zip ist still not the folder, but the files. worldedit is conifgured fine. it worked before and when i set copy to true, i can backup my files ingame, but i really need it with the compressed ones.
@Doctacosa You have it set to only keep 1 backup in the default_settings section. Regarding saving on server restart: Are you sending 'stop' to the server when you restart it?
@Wondrej I'd be really cautious about having two plugins trying to unload chunks (which really means 'save' world). There's a chance that the other plugin might save while a backup is in progress. (You should actually see a warning if this occurs.)
@number1Master Okay. So, from what you've got in that config: keep 48 backups (30min intervals, if the world was used. So if world was in constant use for a day... that's 48 backups) then cleanup once every 5 days. SO technically, you could have 5 days worth of backups on disk, but based on world usage it would fluctuate (I guess that's why you see 2-3 days.). "cleanup" is best when used at a specific time, say early in the morning, otherwise leave it as false.
@crussell52 You are absolutely correct except "dirty" is purposely set if there is no future backups actions queued for that world. Hmmm, I had a reason for it but in hindsight, it might have been the wrong thing to do. The purpose was to get a fresh backup if the server had been stopped for a while but it would backup everything regardless. I'll change it.
@turbotas What are your 'save' times set to? Chunks are not unloaded unless it can save.
@Chrome11 'minebackup' folder, next to 'plugins' and the craftbukkit.jar
@dagundi prepend-world should be false. The map files would then be at the root of the zip file. Is your worldedit configured to look at 'minebackup' for snapshots? Your structure should look like explained here: http://wiki.sk89q.com/wiki/WorldEdit/Snapshots
I've made new attempts based on what I could read here, but I unfortunately didn't get it to work properly either. Once the plugin is enabled, whatever changes are done aren't saved, so they get all lost as soon as the server is restarted. This is really inconvenient if I need to restart to install new plugins, or if it crashes!
The plugin is currently set to save every 10 minutes, but once that time expires, running "/minebackup status" will show the command to be "over" by some time, and doesn't seem to execute. It also created a compressed copy, as expected, but it decided to delete the main world backup as soon as it was done compressing. Maybe I just ran out of disk space or something, yet the compressed versions of the Nether and End made it through properly.
I've posted my config here: http://pastebin.com/FTrz7SUC
Any help would be appreciated. I want to have this in working order, but I'm at a loss right now.
@number1Master
But how do I setup configs for nolagg and minebackup properly? sorry to bother you with this, but Iam lost, realy. Should I set the save in both, or only in one of them?
@dagundi
For me, setting compression true will put it into a .zip .
@Wondrej
I understand. NoLagg and Minebackup seem to work together fine, at least for me. Ya, but I don't want to force you when it comes into developing.
Any1 got help for my Problem @comment 112?
@number1Master
you got me backwards... but anyway its not important...
important is this: what do if you have minebackup (managing world saves) and nolagg (alsomanaging world saving) I have huge problems with this. I would like to know how to optimize minebackup and nolagg together.
@Wondrej
Yes, you can. To restore from a backup you take one of the backups, then replace it with the "wrong world." But, you don't have to replace it. You can always make your own backup of it or move it someplace else. Then you can use a backup.
if iam restoring my world do I need to delete the wrong world file or overwrite is sufficient?
I find the config slightly too confusing. At first, I thought I understood it, but then it turned out I don't (the configuration page is a little confusing too). It's either I'm not seeing the answer, or I'm right. I liked the configuration in the past where you set how many weeks until the plugin deletes backups, and how often they will backup. No matter what I do, the 5.5 MineBackup deletes backups every 2-3 days, and backups, um, at random? Ya, if you want, heres my config, but all I really ask for is just a slightly simpler config. http://pastebin.com/6ZiWjrt4
@ltguide
I run a nightly maintenance script which shuts down my server, does some stuff (like roll logs) and brings the server back up.
it seems like every time the server comes become queued - even if there has been no activity since the last backup.
e.g.
If I had to guess (have not looked at your code yet), I would say that the persisted "dirty" flag is not honored on server start.
The result of this is that a backup "slot" gets unnecessarily used with each server reboot.
Hi, just updated from the 0.4.8.4 to 0.5.5 - 0.4.8.4 has been working perfect (except for not backing up plugins) for months.
The new version causes the server to go titsup about every 4 hours. It looks like maybe it's not managing to start writing block changes to disk after the backup finishes as it crashes faster then more block changes there are. The error is a Java heap space error.
From the caution section, I see that there is an issue with enabling compression on single core (yep, thats me) or low memory (thats not me) servers, but compression was no problem with previous version.
For now I've gone back to 0.4.8.4, but would be usefult to get the new features of this great plugin!
Do the java heap space errors tie in with compression on single thread CPUs?
Does anyone know where the backups are saved? Appart from that it is a great plugin.
Since the new Version i have the problem that i can't restore my Backups any more with WorldEdit.
I get the error Message:
When i manually create a folder with the world name and move the files the backup works. But how can i configure the plugin to zip the folder with the world name in it?
It doesent work with the "prepend-world" option. I have tried it on true and on false (should be false, at least according to doku)
Any help please?
@gwebb417
it does support multiple worlds... even with my world.. I use both myself
I have this plugin and it looks like a great peace of work, but I have a slight issue. I have the plugin MyWorlds and this bakcup program does not look like it supports multiple worlds. If there is anyway to fix that please let me know!