In the following example, NetBackup 9.1 Primary, Media and CloudPoint servers are deployed with the result being able to log into the NetBackup Primary webui and viewing the Media and CloudPoint servers attached.
To begin, log into your AWS portal, search for Veritas NetBackup in the AWS navigation bar and select “Veritas NetBackup (BYOL)”.
You will be taken to the latest Veritas NetBackup (BYOL) in the AWS Marketplace. Click on Continue to Subscribe.
Once you’ve subscribed to the software, Click on Continue to Configuration.
The first step to configuring the software is choosing the Delivery Method. For this blog we’re going to deploy a NetBackup Primary, Media and CloudPoint servers.
After Delivery Method has been chosen, select the Software Version and the Region you’d like to deploy NetBackup in. Click on Continue to Launch.
Check to make sure you the selections you’ve chosen are correct. Click Launch.
Check the prerequisites and click Next.
Next, we’ll enter the configurations for the NetBackup Primary Server.
Here we enter information for the Media Server:
Next, we’ll enter information for the NetBackup CloudPoint Instance.
Now enter the Common Instance Configuration Parameters.
Next, we’ll enter the information of our existing VPC and Subnet. If you’d like the stack to create a new VPC and Subnet and Domain, ignore this step and go to the next step.
Note: The VPC CIDR block and the subnet block cannot be the same size. If the same range is given an error will occur during CloudPoint server creation.
If you’ve chosen to have the stack create your VPC, CIDR Blocks and Domain, enter the information here.
Next enter the NetBackup Installation Parameters.
From here we’ll enter in the NetBackup CloudPoint Parameter.
Note: This role is required for NetBackup to properly work with AWS. For more information, see the Veritas NetBackup Cloud Administrator’s Guide.
This page covers any Tags, Permissions or Advanced options you’d like to use with the Stack. When you are complete or if no changes are necessary, click Next.
It’s time to review the Stack and if everything looks good, go to Capabilities at the bottom of the screen. Acknowledge the two Capabilities and click on Create stack.
You will be taken to CloudFormation where the new NetBackup infrastructure will be created. When the stack has been successfully created, a similar message will appear.
If you choose not to use the root user to log into the WebUI, a user must be created and given privileges to login to the new webui.
sudo useradd -m newusername
sudo passwd newusername
sudo /usr/openv/netbackup/bin/admincmd/bpnbaz -AddRBACPrincipal -user typeofpassword:FullyQualifiedDomainName:username
sudo useradd -m netbkadmin
sudo passwd netbkadmin
sudo /usr/openv/netbackup/bin/admincmd/bpnbaz -AddRBACPrincipal -user unixpwd:ng-nbu-primary1.vrts.tme.io:netbkadmin
On successful login you will be greeted with the following banner. For this blog, we’ll jump into the GUI to see the other created NetBackup components.
Located under Security > Hosts in the NetBackup webui we can see the three newly created resources ready to be used.