As you all probably know already, ClassiCube.net and all related services had a downtime lasting 34 hours.
Here is a brief explanation of the process of how the site was saved and brought back to life.
It started with expected maintenance on the host systems. No downtime was expected.
This maintenance, although, caused a safety check to be run on every running system.
If a system had a valid source image, it was fine, if it did not, it would be not be allowed to boot in an unfixable way.
We, unfortunately, did not have a source image. And thus was the start of the inevitable downtime.
We were not the only ones affected by this, yet we were lucky to be the first of the few to get assistance from the host.
We did have a backup of the full database, but none of the skins or client builds were backed up.
The host, not knowing how to fix the problem, began looking through every Virtual Disk on the system to find our files.
The virtual disk was manually edited to be able to be mounted to a new virtual machine.
Thus begins the process of reinstalling everything to a new virtual machine and copying over the files.
ClassiCube is in a working state now and we hope to never go through that again.
We are currently at ~98% functionality, and there may be a few very short website outages here and there until all the kinks are ironed out.
We are sorry for any inconveniences this downtime may have caused you.
Posted a week ago by CC.Joseph