Technology

60033 readers

2990 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 2 years ago

MODERATORS

[email protected]

131

Google Cloud explains how it accidentally deleted a customer account (arstechnica.com)

submitted 6 months ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

Earlier this month, Google Cloud experienced one of its biggest blunders ever when UniSuper, a $135 billion Australian pension fund, had its Google Cloud account wiped out due to some kind of mistake on Google's end. At the time, UniSuper indicated it had lost everything it had stored with Google, even its backups, and that caused two weeks of downtime for its 647,000 members. There were joint statements from the Google Cloud CEO and UniSuper CEO on the matter, a lot of apologies, and presumably a lot of worried customers who wondered if their retirement fund had disappeared.

UniSuper's mistake was relying too much on Google Cloud even for critical backups.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 26 points 6 months ago (1 children)

During the initial deployment of a Google Cloud VMware Engine (GCVE) Private Cloud for the customer using an internal tool, there was an inadvertent misconfiguration of the GCVE service by Google operators due to leaving a parameter blank. This had the unintended and then unknown consequence of defaulting the customer’s GCVE Private Cloud to a fixed term, with automatic deletion at the end of that period. The incident trigger and the downstream system behavior have both been corrected to ensure that this cannot happen again.

Your data is safe in the cloud with multiple redundant backups, unless your account is marked as delinquent which will be deleted immediately and irrevocably.

[–] [email protected] 5 points 6 months ago (2 children)

That's not what I got out of that at all. It looks more like an errant setting made the account expire automatically after some amount of time, triggering the wipe.

[–] [email protected] 14 points 6 months ago* (last edited 6 months ago) (1 children)

Errant settings that marked the account as delinquent/unpaid at the end of the month, triggering immediate and irrecoverable account deletion. Basically, the scariest part of the google cloud is if they think you can't pay anymore, even if it's a mistake, your account will be wiped along with the backups. They did say they'll have more safeguard after this, but finger crossed.

[–] [email protected] 3 points 6 months ago (1 children)

"Fixed Term" does not mean "delinquent". It just means there's a hard cut off. All I know is the snippet you posted, though, so maybe there's more to the situation.

[–] [email protected] 0 points 6 months ago* (last edited 6 months ago) (1 children)

When the account is marked as missed the assigned fixed payment term, it's basically a delinquent account, right?

[–] [email protected] 1 points 6 months ago

Unless I'm misunderstanding it myself, fixed term means they had a set period of time that's not up for renewal. Ergo, when the term runs out, that's it. There's no chance of delinquency because there's no additional payments.

[–] [email protected] 3 points 6 months ago

What I got out of that is that gcp is not a stable product and should be avoided.