Connect your Google Cloud Storage bucket

Now that you have checked the prerequisites, set up the required settings in the Google Cloud Platform and assigned Backup permissions in CloudM Automate, you will be able to access and configure the Backup feature in the CloudM Automate platform.

  1. Sign in to CloudM Automate (using a user / admin with the required Backup permissions) and select the Backup option that is now visible in the Function column (on the left side of the screen)
  2. In the Sub-option column, select Storage Configuration.
  3. Select Google Cloud Storage for the Cloud service provider field.
  4. Upload the Service Account JSON key into the Service Account for Google Cloud Storage field.
  5. Enter the bucket name (as created earlier) into the Bucket name field.
  6. Paste the Resource name into the Encryption key ID (optional) field (if you have set up a KMS Key).
  7. Select Test Connection to check that the connection details are valid.
    • If the credentials entered do not match the bucket name, you will be notified of the error and should rectify before testing the connection again.
    • If the connection test continues to fail, check all steps relating to setting up Google Cloud Storage, ensuring that all permissions are enabled and credentials have been properly configured and added to CloudM Automate without error.
  8. Select Save to confirm.
  9. Set How Long Do You Want to Keep Your Inactive Backups For. Decide how long Email and Drive data is retained after a User or Shared Drive no longer has a backup policy assigned to them. Select Edit to change the values. These values can be overridden on each policy.
    • Indefinite retention - The data is kept indefinitely and never purged from the storage bucket.
    • Retain for x days - Enter the number of days that the data will be kept after the user no longer has a backup policy assigned. After this time, the data will be purged from the storage bucket. The values can be different for Email and File data types.
  1. Select Save to confirm.


If a retention policy changes, any existing users or Shared Drives data in an existing retention period won't be affected. The "purge date" is stored at the time it is changed and CloudM Backup doesn't go back and change this if the retention policy is changed.

Also, ensure that you do not have a retention policy set for the storage bucket through the Google Admin Console as it will conflict with the policy set in CloudM Backup.  

Was this article helpful?
0 out of 0 found this helpful