Prerequisites for protecting PaaS assets
NetBackup lets you discover, protect, and restore PaaS assets across different cloud platforms for a variety of assets. This section details the supported platforms and databases.
NetBackup enables you to protect PaaS assets with the following cloud providers:
Microsoft Azure
AWS
GCP
The following table lists the supported databases for each cloud provider.
Table: Supported databases by PaaS
Providers | Supported databases |
|---|---|
Microsoft Azure | PostgreSQL, SQL Managed Instance, SQL, MariaDB, Azure Cosmos DB for NoSQL, Azure Cosmos DB for MongoDB, and MySQL. The following components are not supported: Azure SQL - Elastic pool Azure SQL Managed Instance - Azure Arc Azure Cosmos DB for MongoDB vCore Azure PostgreSQL - Hyperscale (Citus) server group and Azure Arc enabled PostgreSQL Hyperscale |
AWS | RDS SQL, RDS PostgreSQL, RDS MySQL, RDS MariaDB, RDS Aurora MySQL, RDS Aurora PostgreSQL, Amazon RDS for Oracle, Amazon Redshift, and DynamoDB. |
GCP | Cloud SQL for PostgreSQL, Cloud SQL for SQL Server, and Cloud SQL for MySQL |
This section details the supported platforms for primary and media servers.
Table: Supported platforms for PaaS
NetBackup server | Supported platform |
|---|---|
Primary | RHEL, SUSE, and Windows |
Media | RHEL |
Storage server | Universal share on underlying MSDP block storage or MSDP-Cloud storage STU |
The credential that you use to add the cloud providers must have the required permissions and privileges assigned, as mentioned in the NetBackup Snapshot Manager Installation and Upgrade Guide.
Here are the supported ports for different PaaS databases. Note that the AWS RDS workloads support custom ports along with the default port.
Table: Supported ports for PaaS
Database PaaS workload | Supported ports |
|---|---|
Azure SQL Server | 1433 |
Azure SQL Managed Instance | 1433 |
Azure MySQL | 3306 |
Azure PostgreSQL | 5432 |
Azure MariaDB | 3306 |
GCP PostgreSQL | 5432 |
GCP MySQL | 3306 |
AWS DynamoDB | NA |
AWS RDS PostgreSQL | 5432 |
AWS RDS MySQL | 3306 |
AWS MariaDB | 3306 |
AWS RDS AuroraDB Postgres | 5432 |
AWS RDS AuroraDB MySQL | 3306 |
AWS RDS SQL server | 1433 |
Amazon RDS for Oracle | 1521 |
Azure Cosmos DB for NoSQL | 443 |
Azure Cosmos DB for MongoDB | 10255 |
GCP SQL Server port | 1433 |
Amazon Redshift | 5439 |
For AWS, see https://aws.amazon.com/premiumsupport/knowledge-center/rds-mysql-functions/
For Azure, set the value of the parameter
log_bin_trust_function_creatorsas 1, as described in the link:https://learn.microsoft.com/en-us/azure/mysql/single-server/how-to-server-parameters
For GCP, do the following:
Open the instance and click Edit.
Scroll down to the Flags section.
To set a flag, click Add item, select log_bin_trust_function_creators flag from the drop-down menu, and set its value to on.
Click Save to save your changes. You can confirm your changes under Flags in the Overview page.
Before performing backup and restore operations on AKS and EKS deployments, you need to configure the parameter MEDIA_SERVER_POD_CIDR in the bp.conf file in the primary server pod. Specify its value as the subnets on which the media server pod is deployed. You can use comma-separated values. For example:
MEDIA_SERVER_POD_CIDR=10.0.0.0/8, 10.0.0.0/16