Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Preparing the GCP service account for plug-in configuration
To prepare for the CloudPoint GCP plug-in configuration
- Gather the GCP configuration parameters that CloudPoint requires.
See Google Cloud Platform plug-in configuration notes.
Do the following:
From the Google Cloud console, navigate to IAM & admin > Service accounts.
Click the assigned service account. Click the three vertical buttons on the right side and select Create key.
Select JSON and click CREATE.
In the dialog box, click to save the file. This file contains the parameters you need to configure the Google Cloud plug-in. The following is a sample JSON file showing each parameter in context. The private-key is truncated for readability.
{ "type": "service_account", "project_id": "some-product", "private_key": "-----BEGIN PRIVATE KEY-----\n N11EvA18ADAN89kq4k199w08AQEFAA5C8KYw9951A9EAAo18AQCnvpuJ3oK974z4\n . . . weT9odE4ryl81tNU\nV3q1XNX4fK55QTpd6CNu+f7QjEw5x8+5ft05DU8ayQcNkX\n 4pXJoDol54N52+T4qV4WkoFD5uL4NLPz5wxf1y\nNWcNfru8K8a2q1/9o0U+99==\n -----END PRIVATE KEY-----\n", "client_email": "email@xyz-product.iam.gserviceaccount.com", "auth_uri": "https://accounts.google.com/o/oauth2/auth", "token_uri": "https://accounts.google.com/o/oauth2/token", "auth_provider_x509_cert_url": "https://www.googleapis.com \ /oauth2/v1/certs", "client_x509_cert_url": "https://www.googleapis.com/robot/v1 \ /metadata/x509/ email%40xyz-product.iam.gserviceaccount.com" }
- Using a text editor, reformat the private_key so it can be entered in the CloudPoint user interface. When you look in the file you created, each line of the private key ends with \n. You must replace each instance of \n with an actual carriage return. Do one of the following:
If you are a UNIX administrator, enter the following command in vi. In the following example, the ^ indicates the Ctrl key. Note that only the ^M is visible on the command line.
:g/\\n/s//^V^M/g
If you are a Windows administrator, use WordPad or a similar editor to search on \n and manually replace each instance.
- When you configure the plug-in from the CloudPoint user interface, copy and paste the reformatted private key into the Private Key field. The reformatted private_key should look similar to the following:
-----BEGIN PRIVATE KEY-----\ N11EvA18ADAN89kq4k199w08AQEFAA5C8KYw9951A9EAAo18AQCnvpuJ3oK974z4 . . . weT9odE4ryl81tNU\nV3q1XNX4fK55QTpd6CNu+f7QjEw5x8+5ft05DU8ayQcNkX 4pXJoDol54N52+T4qV4WkoFD5uL4NLPz5wxf1y\nNWcNfru8K8a2q1/9o0U+99== -----END PRIVATE KEY-----