NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- About protecting cloud assets
- Limitations and considerations
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- Cloud asset cleanup
- Cloud asset filtering
- AWS and Azure government cloud support
- About protecting Microsoft Azure resources using resource groups
- About the NetBackup Accelerator for cloud workloads
- Configuring backup schedules for cloud workloads
- Backup options for cloud workloads
- Snapshot replication
- Configure AWS snapshot replication
- Using AWS snapshot replication
- Support matrix for account replication
- Protect applications in-cloud with application-consistent snapshots
- Protecting AWS or Azure VMs for recovering to VMware
- Protecting PaaS assets
- Prerequisites for protecting PaaS assets
- Installing the native client utilities
- Configuring the storage server for instant access
- Prerequisites for protecting Amazon RDS SQL Server database assets
- Configuring storage for different deployments
- About incremental backup for PaaS workloads
- About archive redo log backup for PaaS workloads
- Limitations and considerations
- Discovering PaaS assets
- Viewing PaaS assets
- Managing PaaS credentials
- View the credential name that is applied to a database
- Add credentials to a database
- Add protection to PaaS assets
- Perform backup now
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot cloud workload protection issues
- Error Code 9855: Error occurred while exporting snapshot for the asset: <asset_name>
- Backup from snapshot jobs take longer time than expected
- Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
- Error disambiguation in NetBackup UI
- Troubleshoot PaaS workload protection and recovery issues
Configuring permissions for the database user
For MySQL
Create a database user with a master login and grant these permissions:
mysql --protocol=tcp --host=instance_fqdn --user=admin -p --port=3306
CREATE USER dbuser IDENTIFIED BY '<password>';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, RELOAD, PROCESS, REFERENCES, INDEX, ALTER, SHOW DATABASES, LOCK TABLES, CREATE VIEW, SHOW VIEW, CREATE ROUTINE, ALTER ROUTINE, EVENT, TRIGGER ON *.* TO `dbuser`@'%' WITH GRANT OPTION;
For PostgreSQL
Create a database user under the server and grant the following permissions:
psql -h instance_fqdn -U postgres
CREATE USER dbuser WITH PASSWORD '<password>' CREATEDB;
(For AWS RDS PostgreSQL) GRANT rds_superuser TO dbuser;
(For AZURE PostgreSQL) GRANT azure_pg_admin TO dbuser;
(For GCP PostgreSQL) GRANT cloudsqlsuperuser TO dbuser;
For SQL Server
Create a database user under the server and grant the following permission:
Create a login on the server:
CREATE LOGIN dbuser WITH PASSWORD='<password>'
Create a user for the database in the server:
CREATE USER [dbuser] FOR LOGIN [dbuser]
ALTER ROLE [db_owner] ADD MEMBER [dbuser]
Note:
The database user must not be part of any database deny role. For example: db_denydatareader and db_denydatawriter.