NetBackup™ Marketplace Deployment on Azure Cloud
- NetBackup marketplace deployment on Microsoft Azure
- Deploying NetBackup on Azure Cloud using the marketplace offer
- Deploying NetBackup on Azure Cloud using the marketplace offer
- Installation type 1: Primary, Media, and Snapshot Manager servers
- Installation type 2: Primary and Media servers
- Installation type 3: Primary server only
- Installation type 4: Media server only
- Installation type 5: Snapshot Manager server only
- Installation type 6: Cloud Recovery server only
- Installation type 7: Malware Scan Host only
- NetBackup configuration parameters
- Additional steps on CRS if encryption is enabled NetBackup primary server
- Accessing the NetBackup Web UI
- Deploying NetBackup on Azure Cloud using the marketplace offer
- Managing Snapshot Manager deployment
- Troubleshooting NetBackup Deployment
Basics tab
On the Basics tab, provide the following details as required:
Table: Basics tab parameters
Parameter | Description |
|---|---|
Project Details | |
Subscription | Select the subscription ID using which you want to deploy NetBackup. |
Resource group | Select from the existing resource groups under that subscription or create a new resource group |
Instance Details | |
Region | Select the region for the deployment. |
Installation type | Select the type or a combination of NetBackup servers you want to deploy, based on the requirement. |
Username | Provide the username that will be used for logging into the virtual instance. Same username will be used to log into the NetBackup primary server Web UI. |
Authentication type | Either select Password or SSH public key as the type of authentication. While deploying the primary server, you should use password authentication. If you have selected Authentication type as SSH while configuring the primary server, you need to access the primary server using SSH key and then set the password for the user to login to Web UI. |
If Password is selected:
| Provide and confirm the password for the username previously provided. |
SSH public key (if SSH public key is selected) | Provide a public SSH key to be used for authenticating the connection with the instance. |
Use existing DNS zone | Select whether you want to use an existing DNS zone or create a new one to resolve hostnames of the deployment components. Note: This deployment uses/creates a private Azure DNS zone. So, to make the hostnames contained within the virtual networks inside a private DNS zone resolvable from the Internet, you must create a link between a private DNS zone and a virtual network. See About Virtual Network links |
|
|