Adding an Instance for Google Cloud SQL for PostgreSQL

To manage a database, you can either use an existing instance or add a new instance.

Before You Begin

• To discover database instances, enable the Cloud SQL Admin and Cloud Resource Manager APIs in the project where service account is hosted.

• On the GCP VM, under API and Identity Management > Cloud API access scopes, enable the Cloud SQL and Cloud Platform scopes.

• Your Google account must contain the following permissions to access the Google resources:

  Role	Title	Description	Permissions	Lowest Resource
  roles/cloudsql.viewer	Cloud SQL Viewer	Provides read-only access of Cloud SQL resource.	cloudsql.backupRuns.get cloudsql.backupRuns.list cloudsql.databases.get cloudsql.databases.list cloudsql.instances.export cloudsql.instances.get cloudsql.instances.list cloudsql.instances.listServerCas cloudsql.sslCerts.get cloudsql.sslCerts.list cloudsql.users.list resourcemanager.projects.get resourcemanager.projects.list serviceusage.quotas.get serviceusage.services.get serviceusage.services.list	Project
  roles/alloydb.viewer	Cloud AlloyDB Viewer	Provides read-only access to Cloud AlloyDB all resources.	alloydb.clusters.list alloydb.instances.list resourcemanager.projects.get	Project

Procedure

1. From the Command Center navigation pane, go to Protect > Databases.

   The Instances page appears.

2. Click Add instance, and then select Cloud database service.

   The Add Cloud DB instance dialog box appears.

3. From the Select vendor list, select Google Cloud.

4. From the Database service list, select PostgreSQL or AlloyDB PostgreSQL.

5. From the Cloud account list, select an existing cloud account or create a new cloud account.

   The cloud account is represented in Commvault as a hypervisor. For instructions to create a Google Cloud hypervisor, see Configuring Backups for Google Cloud.

6. In the Plan section, select a backup plan to use for the instance, and then click NEXT.

   The Cloud Account page appears.

7. Beside the Cloud account list, click +.

   The Add cloud account dialog box appears.

8. In the Name box, type the name for the account.

9. From the Credential list, select a saved credential or add a new Google account credential. To add a new credential, do the following:

   1. From the Credential Vault list, select a credential vault.

   2. In the Credential name box, enter a credential name for the Google cloud account.

   3. Click Save.

10. From the Access node list, select access nodes that have both the Virtual Server and Cloud Apps packages installed.

    Note

    If you configure this cloud account to use managed identity authentication, select only Azure access nodes that use managed identity authentication so that backups and restores will be successful. The access node must be an Azure virtual machine in the same subscription that contains the Cosmos DB account that you want to back up.

11. Click SAVE.

12. Click NEXT.

    The Instance details page appears.

13. From the Instance name list, select an instance.

14. Under the Connection details section, section, enter the following details:

    1. From the Credential list, select a saved credential. You can also add a new credential.

    2. In the Maintenance DB box, type the name of the system database that is used as the maintenance database.

    3. In the Endpoint box, type the name of the endpoint to connect to the database instance.

15. In the Maintenance DB box, type the name of the system database that is used as the maintenance database.

16. In the Endpoint box, type the name of the endpoint to connect to the database instance.

17. Click NEXT.

    The Backup Content page appears.

18. To filter the content that is backed up, click EDIT, select or clear the tables, and then click SAVE.

    A summary page is displayed.

19. Review the summary, and then click FINISH.

Results

• The new instance contains a dump-based backup set and a default subclient.

• When you add an instance, a default database group is automatically created. The default database group includes all the data in the PostgreSQL database. You cannot delete the default database group.