Google Cloud Platform plug-in configuration notes
The Google Cloud Platform plug-in lets you create, delete, and restore disk and host-based snapshots in all regions where Google Cloud is present.
Before you configure the Google Cloud Platform plug-in, enable the following APIs under from Google Cloud console:
Cloud Resource Manager API
Compute Engine API
The node pool provided while configuring Kubernetes cluster extension must have all nodes from same region, that is, the node-pool should be single zonal.
The region of the Snapshot Manager host and node-pool should be same.
For backup from snapshot use case, Snapshot Manager should be installed in cloud only. A provider must be configured for the zone in which Snapshot Manager is installed. If Snapshot Manager is installed in us-west1-b zone then a provider for us-west1 region must be configured.
For manual installation (non marketplace) of Snapshot Manager, disable auto-activation of LVM's LV. This can be achieved by setting parameter to empty list or list of specific VG names which must be auto activated. The parameter can be set in
lvm.confconfiguration file.
The following parameters are required for configuring the Google Cloud Platform plug-in:
Table: Google Cloud Platform plug-in configuration parameters
Snapshot Manager configuration parameter | Google equivalent term and description |
|---|---|
Project ID | The ID of the project from which the resources are managed. Listed as project_id in the JSON file. |
Client Email | The email address of the Client ID. Listed as client_email in the JSON file. |
Private Key | The private key. Listed as private_key in the JSON file. Note: You must enter this key without quotes (neither single quotes nor double quotes). Do not enter any spaces or return characters at the beginning or end of the key. |
Region | A list of regions in which the plug-in operates. |
Snapshot Manager supports the following GCP regions:
Table: GCP regions supported by Snapshot Manager
GCP regions |
|---|
|
|
|
|
|
|
If you are creating multiple configurations for the same plug-in, ensure that they manage assets from different Regions. Two or more plug-in configurations should not manage the same set of cloud assets simultaneously.
When multiple accounts are all managed with a single Snapshot Manager, the number of assets being managed by a single Snapshot Manager instance might get too large and it would be better to space them out.
To achieve application consistent snapshots, we would require agent/agentless network connections between the remote VM instance and Snapshot Manager. This would require setting up cross account/subscription/project networking.
Consider the following before you configure this plug-in:
If a region is removed from the GCP plug-in configuration, then all the discovered assets from that region are also removed from the Snapshot Manager assets database. If there are any active snapshots that are associated with the assets that get removed, then you may not be able perform any operations on those snapshots.
Once you add that region back into the plug-in configuration, Snapshot Manager discovers all the assets again and you can resume operations on the associated snapshots. However, you cannot perform any restore operations on the associated snapshots.
The maximum attachment points on GCP instances are 128 and Snapshot Manager host uses 2 attachment points, which leaves 126 attachment point for backup/restore jobs. So at any point in time Snapshot Manager can backup/restore instance as long as attachment points are available (which is 126 attachment points). If all the attachment points are used, backup/restore jobs start failing with following error message:
Failed to attach disk.
The maximum number of labels that can be attached to GCP instances are 64 and Snapshot Manager uses 2 labels. If any instance has more than 62 labels, backup/restore may fail