How to backup Google Workspace data to Google Cloud Storage.
CubeBackup supports backing up Google Workspace data to either on-premises storage or multiple cloud storage options including AWS S3, Azure Blob storage, Google Cloud storage, S3 compatible storage like Wasabi and Backblaze B2.
In order to backup Google Workspace data to Google Cloud storage, first you will need to create a Google Cloud storage bucket using the following instructions.
Tip: If you plan to back up your Google Workspace to Google Cloud Storage (GCP storage), we strongly recommend running CubeBackup on a Google Compute Engine VM (e.g. e2-standard-2 VM) instead of a local server. Hosting both the backup server and storage on Google Cloud will avoid the bottleneck of all data moving through your local server and significantly improve backup speeds.
Before you begin
- Install CubeBackup on your server/VM/container.
- Start the initial configuration in your web browser.
Create a Google Cloud Storage bucket
Before you can backup data to Google Cloud storage, you will first need to create and configure a private Google Cloud Storage bucket using the following steps:
Log in to Google Cloud Platform.
Google Cloud Platform (GCP) is a place to manage applications/projects based on Google APIs or Google Cloud Services. It does not require an administrator account. A personal Google account, such as myname@mycompany.com is just fine.Create a new project.
If you are an experienced GCP user, you may select an active project and create a Google Cloud Storage bucket directly. If you are new to Google Cloud Platform, begin by creating a new project:Go to the Projects page in the Google Cloud Console.
Tip: This page can be opened by either clicking the above link or selecting IAM & admin > Manage resources in the navigation menu.
Click CREATE PROJECT.
In the New Project page, enter a project name, e.g.“CubeBackup”, and click CREATE.
You can leave the Location and Organisation fields unchanged. They have no effect on this project.
Create a Google Cloud Storage bucket.
Select STORAGE > Cloud Storage > Browser from the navigation menu.
Tip: The navigation menu slides out from the left of the screen when you click the
icon in the upper left corner of the page.In the Cloud Storage Browser page, click CREATE BUCKET.
In the Create a bucket page, input a name for the bucket, and click CONTINUE.
Choose a location type for the bucket (Region or Dual-region is recommended), then select a location for the bucket, and then click CONTINUE.
Tips:
1. Please select the location based on the security & privacy policy of your organizations. For example, for EU organizations, you may need to select Europe to be in accordance with GDPR.
2. Select a location the same as or near to the location of your Google Compute Engine VM.Choose a default storage class for the backup data, Coldline is recommended, then click CONTINUE.
Select Uniform as the Access control type, and click CONTINUE.
Additional options should be left as default. Then click CREATE.
Tip: Since CubeBackup constantly overwrites the SQLite files during each backup, enabling the Object versioning or Retention policy would lead to unnecessary files duplication and extra costs.
Setup CubeBackup with a Google Cloud Storage
After creating the cloud bucket and the Access key, go back to CubeBackup setup wizard:
- Select “Google Cloud storage” for the Storage type.
- Select a local directory for data index path. Data index acts as cache for backup data, and a local SSD is strongly recommended for storing data index. For more information about the data index, please visit here.
- Enter the name of the bucket you just created in the Bucket field.
- Specify the storage class for the backup data. Coldline is recommended. You can see more information about Google Cloud Storage class and find the pricing details for the different Google Cloud storage classes at Cloud Storage Pricing.
- If you want your backups to be encrypted, make sure the Encrypt backups option is checked.
- Click Next and go through the following steps in reference to initial configurations.
