THE GOOD NEWS:
The Hosting-Company die of things is now fully 100% configured properly. OVH (the big guys with the warehouse full of machines) are happy with our settings, we are no longer taking cheap-shortcuts to make things work (end therefore not working properly), and we fully configured to be 1-click scaleable. we'll never have near this level of downtime again for upgrades should we ever need them (we shouldn't), and we are much much more stable than before. This means less downtime!
MORE GOOD NEWS:
In conjunction with all that, we can now VPS our multiple servers. This means no longer will the MS server affect the FTB server, or vice versa (the main issue in causing what rob mentioned above, getting to that). This also means better performance, and more stability and less problems like rhinox's lag.
SOME SEMI GOOD NEWS:
We can now have bukkit on the FTB server SAFELY! We will instal it before anything else so there is nothing for it to fuck up! This means things like /home, /tpaing, /warps, /fly for admins, lockable chests (no more looting!), as well as possible lockable barrels and IC2 machinery due to custom configs (MAYBE WE'LL LOOK AND SEE), and much more!
The nowhere near good news:
In relation to above, and rob's post, we have lost the FTB server. The total cause of this: I assume most of oyu know what .zip/.rar filetypes are, they are a compressed, shrunk down copy of a directory that saves as a single file, making transferring them easier. When doing things, like all the server maintenance we have done for the past month and a half, the easiest way to transfer all the files in the servers back and forth is to use a process like .zipping, using .tars. Unfortunately, apparently .tar can have some troubles moving large massive files (say, 100Gigs) and might corrupt them. This is what happened. While dealign wit hthe massive number of backups the MS MineBackup plugin has created, the files became corrupted ( we lost all MS backups older than february 14th, the Essentials folder (meaning your /home locations, /warps, and a few other non-issue items), and the entire FTB server). This means
We have to restart the entire FTB server from scratch unfortunately
. Some of you at this point may be at the point you think this is going to be a normal occurrence and an issue. I promise you it won't be. We now have the infrastructure in place to have the entire MACHINE backed up better, as well as keeping this type of stuff from happening again, as well as this amount of downtime. We should never see downtime due to me/corin again.
What this all means:
We need to decide what we're going to do at this point. First: what modpack we all want collectively (I suggest DW20 still).
Second: We're going to need to find a new seed we like, unless one of those who did the seedhunting originally have the seed from before that we can use.
Third: We need to decide what we're going to do as a server now. Start over from scratch, give everyone an hour with admin-monitored creative mode, give nice big chests full of supplies out, or what. We also need to hash out some more permanent-type things, such as how to handle mystcraft, what rules need to be put in place in-game wise on mods that cause any forms of lag, and what to do as admins to stop some of our past mistakes happening again.
@Claus, Rhinox, Maestro, IzakTheGoomba, MME: I would highly suggest you all register at
http://multicraft.ms-hosting.org/ (as soon as it is back up again), and them N can give all of you FTP access to the server if he so chooses to allow Claus to run his scripted backups, and rhinox his as well.