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.
@Liger_XT5
Server Specs: Win 2008 R2, Quad i5 @3.1 Ghz; 16gb ram (4 dedicated to Minecraft), 60gb SSD (minecraft & OS Pagefile), 4TB raid5 (backups & dynmap).
I will try running a second server using only the backup plugin with only this world to see what results I get.
Thanks for all your assistance thus far.
EDIT: After running tests on across multiple machines with multiple plugin combinations I was NOT able to reproduce the issue elsewhere. After transferring one of the ZIP files locally for testing when I discovered that I was able to open it. This led me to the conclusion that the issue is not with bukkit, plugins or the HW but instead an issue with Server 2008 opening a 10gb zip. Note to others, try opening the zip file elsewhere first :).
@Razoul_05
That is a bit weird. I'll admit I'm not using a large 1.7.x world, and it's not currently the main world, at least not yet, but I'll look at it's backups later and see if I can do an extract and use test. Only difference between yours and mine is file size (also using large biomes).
Curious, are you using Linux or Windows?
@Liger_XT5
AutoSave is set to 0 in the bukkit.yml and there are no other plugins doing backups. All the plugins I am using have been active on the server for over a year with no additions or changes.
Its odd that its only 1 world (the new one) that is encountering this issue. The only things different in this world are 'large biome', large map (13,000 radius); 10GB size, and 1.7 worldgen.
@Razoul_05
Make sure you don't have any other plugin doing saves, including in your bukkit.yml.
My main world is little over 9GB and works just fine.
I recently updated my server to 1.7.2.R.02 added a new world (Multiverse) for the 1.7 content. For the most part the plugin continues to work perfectly except for my new 1.7 world. The configuration is set such that a save occurs every 15m and a compress every 6hr.
For only my new 1.7 world the zip created by the compress action is corrupt and unable to be opened. There are no errors being thrown by ANY of my plugins. My only thought is that the world is too large and the zip is failing to create successfully (world is 10gb uncompressed).
Hello,
I have a problem. When I enable "compress: 1d" on a map it works in _nether and _the_end. But no in the main world.
When I type "minebackup status" the world_nether and _the_end are "dirty=false" and world is true.
EDIT: It only seem to happen with compress, copy works
EDIT2: Ok forget this question. Solved it by deleting persist.dat
gr,
Maxim
Got this error what is wrong?
http://pastebin.com/MJqdDgRW
Here is my config setup
http://pastebin.com/YcDYAqi8
Finally one that is updated! yay!
Can you give me a config that can work for my server so it compresses EVERYTHING, and throws it in my dropbox, and then deletes the zips it had in the server
I'm not sure if this has been asked, but is it possible to use Minebackup on a Tekkit Server? I have it running flawlessly on Tekkit Classic, but thus far have been unsuccessful with Tekkit. Any advice or links to forums would be great. Thanks!
I have this issue with one of my world, all other worlds work perfetly fine:
@BucketFreak
It works, I do not have any issues.
@DanielMuhlig
Might check your config. I have mine pretty basic. All I have mine to do is compress. No copy, no save, nothing besides compress and cleanup.
What about compatibility with 1.6.4?
Hi,
After updating to 1.6.4 MineBackup seem to somehow lock the server causing players to be kicked. Here's an excerpt from the log:
2013-10-27 18:13:55 [INFO] [MineBackup] * saving worlds\plotworld55
2013-10-27 18:13:55 [INFO] [MineBackup] | unloaded 1014 of 2064 chunks @ 99.87ms
2013-10-27 18:14:44 [INFO] [MineBackup] \ done 49020.92ms
Everything freezes for the 49 secs and some/most/all players are kicked.
I have the same timings from before the update (i.e. 25-50 secs) , but it didn't cause players to be kicked prior to 1.6.4.
(At other times the save takes only a few hundred ms.)
Does anyone else experience the same behaviour? Any solutions?
EDIT: Before the 1.6.4 update, a save (like the one from the log excerpt above), took only 50-200 ms. After the update, at save (even with unloading zero chunks) takes loooong and makes server kick players (compress is not an issue as it only increases CPU usage and does not cause players to be kicked). The problem showed up on THE FIRST SAVE on the 1.6.4 version, so I'm 100% sure, that it is somehow connected with the update! I don't think that MineBackup is the source of the problem though. Probably somthing with the server.
/Daniel
Please update this :)
Anyone out there able to edit the dropbox code to use the newer chunk uploader API rather than the old /upload API???
@therennon
Check the Clean Up time setup. Basically, it will keep how many copies you want, then if it reaches over that number when the cleanup setup kicks in, it deletes the oldest.
I'm thinking of installing this "plugin" but I have a question for you.
It is possible that the "scheduled backup" to replace the "old copy" and thus does not consume much space on the hard drive?
Thanks!
@Liger_XT5
Dropbox have away of doing this, but ltguide has to put the code in to the plugin. I asked awhile ago but he never done it.
EDIT - This is what needs to be put in there. https://www.dropbox.com/developers/core/docs#chunked-upload
@Plyskeen
That message means that the process of the step it's working on is taking over a minute to do. Such has compressing a large file (such as your main world) just ignore it.
I'm still using this, works great. I have it set to upload all my backups to my dropbox. Only problem I have is related to Dropbox. My main world, when compressed (level 9 compression) it's too large for dropbox to take in one go. If I could some how set it up to split the backup into parts, that would do it.