Backrightup’s Post

Heard about the Unisuper-Google Cloud debacle?!? It's a classic case of putting all your eggs in one basket. 🧺💥 Unisuper thought they had it all figured out by migrating to Google Cloud Platform (GCP), but little did they know, they were in for a wild ride! The key takeaway? Don't underestimate the importance of a solid disaster recovery plan. Unisuper learned the hard way that relying solely on GCP's multi-region replication wasn't enough to prevent a major outage. Another lesson: communication is key! 🗣️✨ Unisuper's lack of transparency during the fiasco left customers frustrated and in the dark. In times of crisis, keeping stakeholders informed is crucial to maintaining trust!!! Lastly, always have a backup plan! 🔄💾 Unisuper's failure to implement a robust backup strategy cost them dearly. Don't be like Unisuper, folks! 😉 Invest in a comprehensive DRP. #Unisuper #GoogleCloud #TechFail #DisasterRecovery #CommunicationIsKey #BackupPlan

Unisuper outage incident, the Google cloud write-up has some interesting language. Specifically recovery "was assisted by the customer’s robust and resilient architectural approach to managing risk of outage or failure.     Data backups that were stored in Google Cloud Storage in the same region were not impacted by the deletion, and, along with third party backup software, were instrumental in aiding the rapid restoration." Instrumental does not equal sufficient. Then in the summary "Resilient and robust risk management with fail safes is essential to rapid recovery in case of unexpected incidents."    The language is particularly interesting given some earlier reports/comments in public forums that Unisuper were lucky they had a second copy outside google cloud. https://lnkd.in/g7cSSex7 read the full post for yourself.

https://lnkd.in/gXFa2NMu “Ultimately, trusting one's data – particularly data on which a business depends – to any sort of cloud storage should only be done after fully understanding the implications of the services' terms and conditions. Just because the files have been uploaded one day does not necessarily mean they will still be there – or recoverable – the next.”

To protect your orgs’ #desktops, #laptops, and mobile #devices, you need a centralized #cloud approach—whether you're at the office or in your home office. Tap the link to learn about scalable, secure data protection from #DellAPEX Backup Services. https://dell.to/3ZBXX7V #IWork4Dell

Come and have a laugh watching me and Martin Omander talk the principle of least privilege! Did you know when deploying to Cloud Run or indeed many services on Google Cloud that if you're creating the service for the first time, the default compute engine service account is used, and that account has a lot of power! Watch the video to learn about how you can apply good security techniques to your infrastructure. #GoogleCloud #serverless #CloudRun #Security

Good example of why there is a huge need & importance around 3d party data resilience/protection. Let’s not become complacent and put all of our trust in native cloud capabilities.

Cloud compute and disaster recovery are the future of data protection. With iBridge, you can rest easy knowing that your information is safe and accessible when you need it! #Cloud #Computing #DataProtection #DisasterRecovery #safedata

Today I have a potentially more controversial article in my "Google Cloud Adoption for the Enterprise Series". We're still in the strategy-setting section, and I'm talking about lift-and-shift (aka "rehost"). It's well-known that lift-and-shift is not the way to achieve value in cloud. You're still left with the overheads of managing and patching your operating systems. You still have to deploy your entire software stack. If you have commercially-licensed products on your VMs today, you might be in for a nasty shock. (See Part 1B!) And with lift-and-shift, you've failed to modernise your applications. So we know lift-and-shift should never be the strategic goal in cloud. All that being said, we know there are some use cases where lift-and-shift is useful. For example, if you have a short term data centre exit imperative, or maybe if you have a commercial product that can't be modernised. Nothing controversial so far. But in this article, I suggest that where you are forced to do lift-and-shift, you should try to avoid GCVE and go to GCE, if you can. There may be scenarios where GCVE is useful, but I think they're pretty rare. I'm interested in your thoughts! Do you agree? Can you think of any GCVE scenarios I haven't covered? https://lnkd.in/eu9dKkJ3 #cloudadoption #googlecloud #cloudstrategy #liftandshift #gcve #rehost

INCYMI - Google Cloud has released an incident summary of the recent deletion of Uni Supers’ “cloud”. It makes for an interesting read, and shows how a simple oversight a year ago, and have big consequences today. In summary: > it wasn’t a bug in terraform (or similar) > it wasn’t someone somewhere provisioning something new or making a change > it was multiple oversights by Google Engineers, using a manual method of provisioning resources that their console/apis couldn’t do previously (due to a requirement of Uni Super at the time) one year ago to the day of the deletion > more than likely, backups (seemingly stored within Google Cloud) + infra as code (most likely) saved the day and led to a speedy recovery

Imagine logging into your cloud storage to find months of work vanished – a scenario some Google Drive users faced when files disappeared without a trace. Don't let this be your business's reality. ACS's SaaS Backup safeguards your cloud data across various platforms, including Google Workplace, Microsoft 365, and Salesforce, ensuring what you store in the cloud stays retrievable, no matter what. Get in touch with ACS to discuss our SaaS backup solution 🔗 https://buff.ly/3h3npSK #CloudBackup #DataSecurity #ACSProtection Read the article 📖