Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide
  3. Section I. NetBackup Snapshot Manager for Cloud installation and configuration
  4. NetBackup Snapshot Manager for cloud providers
  5. Google Cloud Platform plug-in configuration notes
  6. Prerequisites for configuring the GCP plug-in using Credential and Service Account option
NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide

Prerequisites for configuring the GCP plug-in using Credential and Service Account option

  • Before you configure the Google Cloud Platform plug-in, enable the following APIs under APIs & Services from Google Cloud console:

    • Cloud Resource Manager API

    • Compute Engine API

    • Cloud Key Management Service (KMS) API

    • Google OAuth2 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 NetBackup Snapshot Manager host and node-pool should be same.

  • For backup from snapshot use case, NetBackup Snapshot Manager should be installed in cloud only. A provider must be configured for the region in which NetBackup Snapshot Manager is installed. If NetBackup 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 NetBackup Snapshot Manager, disable auto-activation of LVM's LV. This can be achieved by setting auto_activation_volume_list parameter to empty list or list of specific volume group names which must be auto activated. The auto_activation_volume_list parameter can be set in lvm.conf configuration file.

Feedback

Was this page helpful?
Previous

Google Cloud Platform plug-in configuration notes

Next

Additional prerequisites for configuring the GCP plug-in using Service Account option

Feedback

Was this page helpful?