CoreProtect 2.00 Upgrade Guide
Ready to upgrade from CoreProtect 1.# to 2.#? Here's some information you should know.
Only CoreProtect versions prior to v2.1.0 support upgrading from v1.#
If you wish to upgrade from CoreProtect 1.# to v2.1 or higher, you'll first need to run an older version of CoreProtect first.
The upgrade is one-way
Once upgraded, you can't downgrade, unless you have a backup of your CoreProtect data.
The upgrade will start automatically
As soon as CoreProtect 2.00 is loaded on your server, it'll start importing old data. Old CoreProtect data will be automatically deleted.
You can use your server during the upgrade
However, CoreProtect commands won't be usable until it completes.
The upgrade can take several hours
If you have a large amount of CoreProtect data, the upgrade will take some time. Please be patient.
Please don't interrupt the upgrade
If you do, any block changes that happened since the upgrade started won't be logged in CoreProtect. During the upgrade, it queues up data, and saves it when the upgrade completes.
If your data is important, back it up
Although upgrades currently have a high success rate, data loss can happen if your CoreProtect data was previously corrupted.
WorldEdit logging now requires WorldEdit 5.5+
If you rely on WorldEdit logging, upgrade WorldEdit before upgrading to CoreProtect 2.0
The configuration files are now located in "plugins/CoreProtect"
Your old configuration files will automatically be copied over from the "CoreData" folder when upgrading.
haha thats so helpful :) so, no more flat files? YYYEEEESSSS haha!!!! i love coreprotect, just keeps getting better and better ;)
Tried to run the update, the upgrade gets to 100% in about ten seconds then keeps going, it got to over 1001% before I stopped it because it had consumed over 10 GB of ram. Any ideas?
Could someone tell me if this seems right? My coreprotect DB is 20GB with 378 million rows. It looks like the upgrade is doing about 50k rows every 8 minutes. At this rate it'll be done in 40+ days. I really can't be without block logging for that long.. I'm thinking I'll have to start with a new DB and just query the old one manually if we really need to check block history.. Does anyone else have a DB comparable with this issue?
is this safe for MySQL users ???
Hoping this works for MySQL?
@jaggy80
Uum, you should use /co purge [Amount of months] to clear data (I use it every month) otherwise you will fill up to... 20 GB
wow... upgrade took 37 hours on our server. but all is well and it completed without issue :)
Nice upgrade for tekkit but in description it says that it only logs world edit changs of world edit 5.5 and higher but wat for tekkit players the version from 5.5 and abouve are not supported with tekkit :(
@arnofrutos
I second this question. The last one that is claimed to work with Tekkit Classic (1.2.5) is WorldEdit 5.4.5. Though, I heard somewhere that 5.5 may still work with 1.2.5.
2 really useful features:
Can you please add support for VoxelSniperAdd * to select all users/entities/everything else, like u:*
@arnofrutos
Well, then this is just goin' to be like the same as the old CoreProtect
[email protected]
Source code please!!!