NetBackup™ Web UI Cloud Administrator's Guide
- Managing and protecting cloud assets
- Configure Snapshot Manager in NetBackup
- Managing intelligent groups for cloud assets
- Protecting cloud assets or intelligent groups for cloud assets
- About storage lifecycle policies
- Managing policies for cloud assets
- Configuring the Start window
- Managing cloud policies
- Scan for malware
- Protecting Microsoft Azure resources using resource groups
- NetBackup Accelerator for cloud workloads
- AWS Snapshot replication
- Protecting PaaS assets
- Protecting RDS Custom instances
- Protecting Azure Managed Instance databases
- Limitation and considerations
- Installing the native client utilities
- Configuring storage for different deployments
- Managing PaaS credentials
- Add protection to PaaS assets
- Recovering cloud assets
- Recovering cloud assets
- Recovering AWS or Azure VMs to VMware
- Recovering PaaS assets
- Recovering cloud assets
- Performing granular restore
- Troubleshooting protection and recovery of cloud assets
- Troubleshoot PaaS workload protection and recovery issues
Prerequisites for protecting Azure Managed Instance databases
These prerequisites are required to protect Azure Managed Instance databases without creating a temporary database.
Note:
Managed Instances use Azure SAS tokens to securely put the data in the form of a .bak
file in the Azure Blob.
Create a storage account name, using the following example:
Calculate the hash of the string formed by combining the Subscription ID and Region. Follow this example command:
echo -n "aaaaaaa-bbb-ccc-dd11-aabbccdd11223344eastus" | sha256sum 2e5fb564552100a6060794937fedc33aefe4d01eb7e27971c1a0ed52c3f78b6c
Take only the first 16 chars of the hash, and prefix the characters nbu.
Your string becomes: nbu + 2e5fb564552100a6.
So, the Azure storage account name is: nbu2e5fb564552100a6
For containers, use the following name format:
azure-netbackup-<region>
If the container does not exist, the NetBackup agent creates it depending on the availability of permissions.
Management of encryption keys can be according to your organization.