As part of the increased need for collaboration applications, more businesses and organizations have turned to Google and adopted Google Workspace (formerly the G-Suite for Business) to fill this need.
Amongst individuals I know, the mobile version of Google Drive has become our go to app for syncing and sharing files. It’s easy to use and everyone can get access to a free account.
Enterprises, on the other hand, are looking for a solution that is more robust, secure, and capable of working with a higher volume of data than the mobile app, and many have adopted Google Workspace. With that, I’m happy to say that today we’ve announced backup and archive support for Google Drive.
Extending our support to include Google Drive was an easy choice for the expansion of HubStor’s SaaS backup capabilities for collaboration and data sharing applications. HubStor’s Backup-as-a-Service (BaaS) solution provides organizations with a streamlined approach to help ensure that their data is protected. With more and more employees working remotely, enterprises are relying on collaboration applications, and full data protection for them is essential.
The thing that I, personally, like about our support for Google Drive is how we perform backups for the Google applications like Google Docs, Sheets, and Slides.
If you’ve ever used any of those, you know that they store your files in Google Drive. Well, sort of. If you look at the files themselves, you see that every one of them is a zero-byte file, even when you’re certain that you typed more than 0 characters. Those aren’t actual files, but are instead pointers that Google uses for the real location of the files.
So where are the actual files? They’re somewhere inside the Google Cloud where each application stores its files. What happens if you lose those pointers? You lose access to the files that they pointed to. What happens if you back the pointers up by copying them to a different location? Since, from the filesystem level, the pointers don’t really provide information on where the data from the file actually lives, you end up with unusable zero-byte files, just in a different location.
HubStor’s backup for Google Drive takes a different approach. Instead of copying those files at the filesystem level, HubStor connects to the Google Workspace API and extracts a copy of the entire file’s data. These are then saved as files that you can use with either the Google or Microsoft suite of tools. Google Docs files are saved as DOCX, Sheets as XLSX, and Slides as PPTX. These files will still be a complete useable copy whether they’re restored back on Google Drive, or to another location.
The second-coolest thing – again, in my opinion – is how we handle files deleted from Google Drive. If you’re not aware of it, when you delete a file from Google Drive it isn’t actually deleted immediately. Instead it’s moved to the Trash. If a file remains in the Trash for 30 days, it will be permanently deleted at that time. HubStor’s backup allows for point-in-time recovery and versioning, so as long as you’ve retained backup data from a previous time you are able to restore the version of the file as it was at that time. This means that in addition to having access to previous versions of documents, you can also recover files that Google has permanently deleted.
As with all the services supported by HubStor’s BaaS, you can monitor and manage all your Google Drive backup and recovery jobs from the same single unified management console you use for your other services. Enterprises using Google Workspace in multiple regions can be in compliance with any data sovereignty regulations and still manage all backup and recovery from a single console.
If you’d like to learn more about HubStor’s support for Google Drive, the datasheet is a good place to start. If that doesn’t give you all the answers you’re looking for, please contact us. If HubStor is a solution you want to evaluate, we can easily arrange a demo for you.