Hacker News new | past | comments | ask | show | jobs | submit login

Number 1 lesson from this: ALWAYS HAVE A BACKUP OF YOUR DATA AT A DIFFERENT PLACE ON DIFFERENT MEDIA.

For google, to do this, use https://takeout.google.com/ . Download a copy of your data. Now.

Number 2 lesson to learn from this, which is very painful for many, is that there is a significant operational risk surface added by using cloud services, in that you may not actually have control or access to long historical records of data and metadata. Which means, despite clouds simplifying your life with respect to owning/operating/standing up your own kit/capabilities, depending upon how good/bad they are at being helpful in events like these, you massively increase operational risk by using them, as you lack control over the access to your data and history. If their policies and procedures run counter to what you need ... well ... think smelly creek, canoe, and no paddle or oar.

This is on the provider, and Google's "customer service" is known to be horrible for paying customers. I had used them at $dayjob-1, and found that depite paying them ~$100/month for my companies users of Google Apps/GSuite, I could never reach a person to help with a problem. I couldn't find contact points for asking for help. They had an email alias that took a while for them to answer, and it was as bad as the half-way-around-the-world tech support call centers, but in email form.

So, yeah. Back up your documents, emails, etc. Ask yourself what happens if they go away. If you are a small business person as I was, ask yourself what happens if one of your customers is late paying you, so you are late paying them. Kinda sucks to operate without your email and your documents ...

Call this one of the the down sides to *aaS.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: