Basilisk extended downtime 08/09/2017

[Miztah]

Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to monday when we know for sure.

In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

[nasher1984]

Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to monday when we know for sure.

In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

First, thank you so much for your hard work and your team. Second, NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO! WIPE THE DANG SERVER!

[Jaws]

Thanks for the update guys. Keep up the good work.

First, thank you so much for your hard work and your team. Second, NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO! WIPE THE DANG SERVER!

They have repeatedly said it is NOT in the interests of the dev team to wipe at this point - it was a worst case scenario.

[jharmison]

Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

Great work regardless, everyone involved. It's nice to know that we probably won't be running around with sticks when Pub9 drops.

[Skoimich]

Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to monday when we know for sure.

In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

Good work, very much appreciated, I work in IT myself and I know how much backup and restores are tricky things!

[IxeStarwind]

Alright folks, update time. We've managed a recovery of the database and we've got everything copied over to our new SSD's. We're letting Bas run for the weekend as a stress test on the database to ensure there is no corruption that didn't pop up initially. This means that for this weekend, Basilisk is going to remain on Publish 8. We're looking to give the Publish 9 merge another shot on Monday, assuming all goes well over the next 48 hours. We'll update regarding Pub9 closer to monday when we know for sure.

In the meantime, continue on Basilisk as you normally would. We'll be keeping an eye out on our side for any potential stability issues.

Keep in mind that we're still doing integrity checks on the database, if we run into any database corruption between now and then it's very likely that any progress you make this weekend will be lost when we revert to a backup. This is not guaranteed to occur, but be aware that it is definitely a possibility.

That's great news! so , whats the new back-up disaster recovery plan for the long term? were new drives purchased? Amazon S3 50$ for 2TB monthly? some other plan in place? I would hope there is some cloud option. it would be good to know if this has been discussed so we don't have a repeat of the situation . thanks for all your hard work.

[TheAnswer]

That's great news! so , whats the new back-up disaster recovery plan for the long term? were new drives purchased? Amazon S3 50$ for 2TB monthly? some other plan in place? I would hope there is some cloud option. it would be good to know if this has been discussed so we don't have a repeat of the situation . thanks for all your hard work.

There will be a post mortem post with solutions when the dust settles.

[Dbrock]

So probably no Wipe then...

[Vlada]

So probably no Wipe then...

Oh there still is gonna be at least one, just later.

[Fissile]

Oh there still is gonna be at least one, just later.

we can all delay our sip from the poison cult chalice. for now.

[Chui]

we can all delay our sip from the poison cult chalice. for now.

Does the chalice from the palace still hold the brew that is true?


"The Court Jester"
https://www.youtube.com/watch?v=q4Ow69QWJmo

[wren]

That's great news! so , whats the new back-up disaster recovery plan for the long term? were new drives purchased? Amazon S3 50$ for 2TB monthly? some other plan in place? I would hope there is some cloud option. it would be good to know if this has been discussed so we don't have a repeat of the situation . thanks for all your hard work.

Using object storage like S3 for a live databases is not a good idea. Read up on the differences between object storage and block storage. Object storage is great for things that need to be read frequently and written infrequently. A live data base is being written to often, this makes it a horrible choice for a data base.

[Jhunta]

great job guys. you are truly a cut above the rest. thank you for all of your hard work and dedication.