Earlier quoted context omitted.
Not every business can afford to go one month without income. What's the best thing for customers? Have the business go bankrupt and irremediably lose access to the service?
It's 400 clients, not all their user base. They can handle the lost income from a small slice of their customers for one month. And if they can't sustain that, then it's even more imperative that those customers migrate away.
Inside the longest Atlassian outage
751–760 of 772 posts
Re: Inside the longest Atlassian outage
#752Earlier quoted context omitted.
A Jira backup blob isn't especially useful. Confluence could be if it's essentially HTML dumps that you could host internally read-only. Bitbucket clearly has backups and a migration path.
Why is it not useful? From eyeballing it it looked like the same file I built from our Fogbugz data to import our historic cases into Jira. I'll carve out some time to try doing an import into a new project to see if it loads properly.
Re: Inside the longest Atlassian outage
#753Earlier quoted context omitted.
I agree. Customer success is a support role, this was an engineering mistake. Can't blame support for something an engineer did.
Seems like you're still assigning blame. Incidents are rarely if ever monocausal. The fantastic and accurate point the GP made is that fingerpointing is pointless. Much better to seek to learn and understand, which is always difficult but definitely can't be done from the sidelines without speaking to those involved.
Re: Inside the longest Atlassian outage
#754Regarding the backup restores: I once worked a company that had a data loss issue. There was nothing else we could do, we had exhausted every option we had over almost 40 hours. At the end of the second day, it was decided to restore from backup. We had done this before, as a test. It took about 12 hours to restore the data and another 12 hours to import the data and get back up and running. One small thing was diffe…
This is why I love GCP Cloud Storage. The "colder" tiers are cheaper, and reads simply cost a lot more from there, but they don't slow them down and take days to restore. You pay with dollars, not time for restoring those GCS backups. e.g. Coldline [1] simply has reduced availability in exchange for being cheaper (99.9-99.95% availability, so 43min/mo, way less than "two days"). [1] https://cloud.google.com/storage/d…
Re: Inside the longest Atlassian outage
#755Engineering mistakes happen. The most inexcusable thing is not communicating with the paying customers who have been affected for over a week. Atlassian's Global Head of Customer Success probably should have been fired but here she is promoting Atlassian Cloud on LinkedIn three days ago: https://www.linkedin.com/mwlite/in/gertie-rizzo-5b70061 Actually reading a bit more, it seems like their customer team was partying…
Re: Inside the longest Atlassian outage
#756I guess this is wake call for the people rushing to SaaS solutions.
Re: Inside the longest Atlassian outage
#757We use on-premises setups for almost everything (we generally avoid cloud solutions to have full control of our data), sometimes (approximately once a month) it goes down for a few minutes which already feels like a torture because all our processes depend on it, I can't imagine having no access to it for several weeks, all our work would stop to a halt... The office of the guy who administers on-premise servers is l…
Re: Inside the longest Atlassian outage
#758Do anyone seriously consider changing Jira/confluence to some alternative after this? I personally stopped using Jira a couple of years ago in projects I lead.
Some PMs at my company have been agitating for a switch from Asana to Jira, and now I (as VP Engineering) can guarantee that will never, ever happen.
Re: Inside the longest Atlassian outage
#759We use on-premises setups for almost everything (we generally avoid cloud solutions to have full control of our data), sometimes (approximately once a month) it goes down for a few minutes which already feels like a torture because all our processes depend on it, I can't imagine having no access to it for several weeks, all our work would stop to a halt... The office of the guy who administers on-premise servers is l…
We migrated from Slack to self-hosted Mattermost so we avoid being down. (And I guess money.) Mattermost is so much worse that the slowness and general issues are not worth it. And in the end it is more down than Slack ever was, because it has performance issues. I am not sure if it is Mattermost fault or our fault; but my friend from other corporation has similar experience with it. But maybe in general just don't k…
I swear if IRC just implemented emojis.
Re: Inside the longest Atlassian outage
#760Earlier quoted context omitted.
As I understood it is not "Cloud or Nothing" but "Cloud or Data Center" - is this wrong?
We're a team with effectively is Cloud or nothing, and we weren't very keen on going Cloud even before this current clusterf...