Server is back online, CoreProtect logs lost

Hi all,

The main server is back online and open to all. The CoreProtect fix did complete after about 60 hours, but unfortunately it was not successful. With the fix, CoreProtect was able to track further block changes, but it was not able to do any rollbacks. The only way to make this fix work would be to change the CoreProtect code, which we are not able to do given our time and resources. Therefore, I have dropped the CoreProtect database, clearing all block logging data since September 2016. CoreProtect will now continue logging new block changes as normal starting from this point.

I sincerely apologize to everyone for all of this inconvenience. I thought that this fix was the best possible approach to try to keep our block logging data, but I thoroughly underestimated the time that it would take. At the very least, we now know that this fix doesn’t work, and to prevent this from happening in the future, we will need to make sure to purge old records from the CoreProtect database periodically, probably at least once a year. Each purging of these records would likely require server downtime lasting for at least a day, but hopefully not as long as the downtime of almost 3 days that we just experienced.

If you have any further questions about this, please feel free to ask me and discuss this in our Discord #general chat. Thank you everyone once again for your patience.