Basilisk extended downtime 08/09/2017

[Jervin]

There is no acceptable answer in this day and age. The concept of losing your DB backup is where I'd laugh someone out of an interview.

Then again funding for the project is in the toilet. Be glad this project is still on its feet. Everyone should take this opportunity to cough up $20-50.

[Peak]

Then again funding for the project is in the toilet. Be glad this project is still on its feet. Everyone should take this opportunity to cough up $20-50.

Agreed

[bigevil]

Then again funding for the project is in the toilet. Be glad this project is still on its feet. Everyone should take this opportunity to cough up $20-50.

I have no issue coughing up a few more space bucks if we need it. Need to increase my gold bar count anyway.

[zazano]

Then again funding for the project is in the toilet. Be glad this project is still on its feet. Everyone should take this opportunity to cough up $20-50.

Why is donating more money the answer? I'm asking why this patch was pushed without purchasing a new HDD drive.

[Vlada]

Why is donating more money the answer? I'm asking why this patch was pushed without purchasing a new HDD drive.

Had we known we would have replaced it. This isn't a situation where we made a conscious decision to ignore a broken HDD.

**** happens, in our case its a massive amount of ****, but oh well, what's done is done. Instead of throwing blame, which btw will change absolutely nothing, we need to roll up our sleeves and start shoveling it.

[zazano]

Had we known we would have replaced it. This isn't a situation where we made a conscious decision to ignore a broken HDD.

**** happens, in our case its a massive amount of ****, but oh well, what's done is done. Instead of throwing blame, which btw will change absolutely nothing, we need to roll up our sleeves and start shoveling it.

I'm not blaming anyone.

"While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks."

This leads me to believe a new HDD could have been purchased prior to this merge but it wasn't. I'm not against the wipe, I'm asking why the HDD drive that died weeks ago was not replaced before arguably the most significant patch to date. Which in my mind is a perfectly reasonable question to ask.

[PigGeneral]

I'm not blaming anyone.

"While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks."

This leads me to believe a new HDD could have been purchased prior to this merge but it wasn't. I'm not against the wipe, I'm asking why the HDD drive that died weeks ago was not replaced before arguably the most significant patch to date. Which in my mind is a perfectly reasonable question to ask.

I agree. A wipe on purpose is one thing, a wipe because of mismanaged data is quite another.

Once is never, twice is always. Is there going to be a next time?

[Vlada]

I agree. A wipe on purpose is one thing, a wipe because of mismanaged data is quite another.

Once is never, twice is always. Is there going to be a next time?

You're gonna have to stick around to find out.

[PigGeneral]

You're gonna have to stick around to find out.

If I purchase the AWS disk on annual basis to have a weekly backup schedule, will you use it?

[Duloh]

I'm not blaming anyone.

"While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks."

This leads me to believe a new HDD could have been purchased prior to this merge but it wasn't. I'm not against the wipe, I'm asking why the HDD drive that died weeks ago was not replaced before arguably the most significant patch to date. Which in my mind is a perfectly reasonable question to ask.

Hindsight is always 20/20, if they were going into this merger thinking something is going to mess up I'm pretty sure they would replace it. But I'm sure they thought it would be a routine merge and all would go well.

But it didn't and now they get to hear from all you guys, which I'm sure is one thing they don't ever look forward to

[Vlada]

Hindsight is always 20/20, if they were going into this merger thinking something is going to mess up I'm pretty sure they would replace it. But I'm sure they thought it would be a routine merge and all would go well.

But it didn't and now they get to hear from all you guys, which I'm sure is one thing they don't ever look forward to

Oh we do. That is always the highlight of any hardware failure.

[plainolewhitey]

Oh we do. That is always the highlight of any hardware failure.

Vlada haha, you crack me up.

I can only imagine how frustrating this is for you volunteers who have worked so hard on the project. Hang in there. I'll all up for a wipe or whatever! Sounds like most of us are Glad to see most coming together and not complaining here.
If you want me to kick someone's a$$ as Softlayer (I'm assuming that's the host) It's right down the road. One of my ex-wives works there, could always make her day worse by calling her lol.

Looking forward to kicking up the dust on Tat again soon! Thank you all again for all your hard work!

[GiStaak]

I'm not blaming anyone.

"While doing a routine backup before the merge one of the HDD's died, unfortunately that was the second one we lost in a matter of weeks."

This leads me to believe a new HDD could have been purchased prior to this merge but it wasn't. I'm not against the wipe, I'm asking why the HDD drive that died weeks ago was not replaced before arguably the most significant patch to date. Which in my mind is a perfectly reasonable question to ask.

Because HDD wipes aren't predictable. HDD failure rates are quoted as MTBFs - Mean Time Between Failures - which means that statistically, there's a 50% chance the disk will last longer and a 50% chance it will already have failed. I've had HDDs last for over a decade and some start to fail within their warranty.

This is a volunteer project that is focused on development and Basilisk is essentially a live test server; there's no guarantee of continuous service and we know that once the project is complete it will be wiped anyway. If this was a business, I'd totally be with you, but it isn't. I guess what it comes down to is this: you're getting alpha access to a game in development and you can choose to donate or you can choose not to donate. Either way, the development goes on and until a golden master/release candidate is ready the devs really don't have an obligation to make user progress ironclad. It's no different to installing a beta OS on your computer, there's always a disclaimer that says "if it ****s up your system, tough ****."

I'm kinda bummed, I was hoping to get home tonight and see the old man. But the more I think about it, it'll be kinda cool to see a hell of a lot more activity and people grinding again.

[PigGeneral]

Then again funding for the project is in the toilet. Be glad this project is still on its feet. Everyone should take this opportunity to cough up $20-50.

Would it go to an infrastructure engineer that has worked in the real world in the last 20 years? Is there a price breakdown of how donations are spent? This is a pretty big "whoopsie" for me to open my wallet on the heels of.