To get started, you need to configure the following clients in the CommCell Console:
-
A MediaAgent
-
A proxy server
-
An Azure virtualization client
Step 1: Before You Begin
-
This page assumes you have already installed CommServe software. If not, refer to the CommCell Quick Start Guide.
-
Review possible deployment scenarios.
-
To learn more about the requirements of the Virtual Server Agent, see System Requirements
Step 2: Install the MediaAgent
You must install a MediaAgent. For more information, see MediaAgent Installations.
Step 3: Create a Proxy Client
-
Create a Windows or a UNIX client. For more information, see Creating a Proxy Client for Azure Data Protection.
Note
If you configure a Linux client computer, the Mono package is required on the client computer.
For SP17 and more recent service packs, after you install the Virtual Server Agent on a Linux machine and start services, the software checks to see whether Mono is installed and, if necessary, installs the required version of the Mono package. You do not need to install the Mono package manually.
-
For enhanced performance, configure an Azure database instance on the proxy server. For more information, see Performing the Azure Configuration for the Azure Proxy Server.
-
Install, and then configure the PostgreSQL Agent software on the proxy client computer.
The software also installs the PostgreSQL database application versions 9.6, 10, 11, 12, 13, 14 and 15 on the proxy client computer.
Note
The PostgreSQL version 15.x support is added with Commvault V11 Service Pack 32 and Hot Fix Pack 16 (or a more recent version).
The database application must be of the same major version as the PostgreSQL server instance in the cloud and does not need to be in a running state.
Installation path for PostgreSQL binaries for Linux is software_installation_directory/CVCloudAddOns/PostgreSQL/postgres_version, and for Windows is software_installation_directory\CVCloudAddOns\PostgreSQL\postgres_version.
Step 4: Initial CommCell Console Configuration
-
Optional: Decide whether to add the following functionality:
-
To be notified of events that require attention, see Alerts and Notifications - Overview.
-
To report and analyze critical data about your CommCell operations, see Reports Overview.
-
To manage security, see User Account and Password Management - Getting Started.
-
Step 5: Configure the Azure Virtualization Client
-
Add the PostgreSQL Agent software to the virtualization client. For more information, see Adding the Commvault Database Agent to the Azure Virtualization Client.
-
Configure a PostgreSQL instance. For more information, see Configuring a PostgreSQL Server Instance for an Azure Database.
-
If you want to include a subset of the databases in the backup, then create a subclient for the data. For more information, see Creating PostgreSQL Subclient for an Azure Database.
Note
The supported TLS versions to create Azure SSL encrypted PostgreSQL instances are TLS 1.0, 1.1 and 1.2.
Step 6: Run the First Backup Operation and Restore Operation
-
Perform a backup operation. For more information, see Performing a PostgreSQL Database Backup Operation for an Azure Database.
-
Perform a restore operation. For more information, see Azure Database for PostgreSQL Restore Operations.
Note
-
For Azure database for PostgreSQL Flexible Servers, by default, the pg_cron extension is enabled and the schema that is named as cron is created in the postgres database where the pg_cron metadata is saved. Since the Azure Server administrator will not have the privilege to dump/drop/restore the schema, the postgres database backups fail. Hence, the postgres database backup will be skipped from the backups of Azure PostgreSQL Flexible Servers.
-
If cron.database_name is set to a different database, you must create a new subclient in order to skip the database from backups.