Forum Discussion

GNeil's avatar
GNeil
Level 4
4 years ago

6 Steps for installing NetBackup in the AWS Cloud

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.

Let’s Begin

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.

Prepare for Launch!

Check to make sure you the selections you’ve chosen are correct.  Click Launch.

Check the prerequisites and click Next.

Primary Server

  1. Give the Stack a name that will identify it. 

Next, we’ll enter the configurations for the NetBackup Primary Server.

  1. Give your NetBackup Primary server a name.
  2. Choose the Server Instance Type.
  3. Select the NetBackup Primary Server installation volume size.

Media Server

Here we enter information for the Media Server:

  1. Give the NetBackup Media server a name.
  2. Choose the Server Instance Type.
  3. Select the NetBackup Media Server installation volume size.

CloudPoint - Configurations

Next, we’ll enter information for the NetBackup CloudPoint Instance.

  1. Select the OS type you’d like for the CloudPoint server.
  2. Select the Instance Type.
  3. Enter in the size of the CloudPoint Volume.
  4. Enter an Elastic IP if you need one.
  5. Enter the HTTP Proxy if one is use.
  6. Enter the HTTPS Proxy if one will be used.
  7. Enter a NO Proxy if one will be needed.

Common Configurations

Now enter the Common Instance Configuration Parameters.

  1. Select an SSH Key Pair so you can SSH to the new environment.  This step needs to be completed prior to this point.
  2. Choose if you will be using an existing Virtual Private Cloud (VPC) or if you’d like the template to create one for you.

VPC, Subnet and Domain

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.

  1. Enter the VPC ID you’d like to deploy the NetBackup stack in.
  2. Enter the Subnet ID for the new stack.

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.

  1. Select the Availability Zone the stack will be installed in.
  2. Choose the VPC CIDR block the stack will use.
  3. Choose whether or not the stack should create a new DHCP Option Set for the VPC.  If you already have one associated with your Route 53 Domain, choose false.
  4. Enter the name of the Domain you wish to use.  This domain must be associated with the Route 53 you plan to use with this stack.
  5. Select if there is a Route 53 Hosted Zone associated with the domain in step 6.

 

If you’ve chosen to have the stack create your VPC, CIDR Blocks and Domain, enter the information here.

NetBackup Installation Parameters

Next enter the NetBackup Installation Parameters.

  1. Enter a username for the NetBackup service.  This user will NOT be used to login to the instances, it will only be used to start and stop NetBackup processes.
  2. Enter your NetBackup License Key.
  3. Paste the contents of your NetBackup Usage Insights Customer Registration Key here.

CloudPoint – Installation Parameters

From here we’ll enter in the NetBackup CloudPoint Parameter.

  1. Enter the username for CloudPoint.
  2. Give the user a password.
  3. Enter any additional names you’d like to be added to the TLS certificate.
  4. The default CloudPoint port is 443, customize if desired.
  5. Give the name of the Cloudpoint Instance IAM.  If you don’t enter one, the stack will create one for you.

Note:  This role is required for NetBackup to properly work with AWS.  For more information, see the Veritas NetBackup Cloud Administrator’s Guide.

https://www.veritas.com/content/support/en_US/doc/58500769-150013608-0/v125433652-150013608

  1. Enter the NetBackup Cloud SNS Topic ARN.  This is only required if you wish to receive notifications.
  2. Enter the NetBackup CloudPoint CMK ID.  This is only necessary if you are using a Key Management Service (KMS).
  3. Enter the NetBackup CloudPoint CMK Region.  This is only necessary if you are using a KMS.
  4. Click Next when the above information is correct for your environment.

Final Inputs

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.

Review Time

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. 

Your Deployment is Complete

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.

Create WebUI User and Login to WebUI

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.

  1. Log into the Primary server using the ec2-user and create a new user on the Primary server to log into the new NetBackup infrastructure.

sudo useradd -m newusername

sudo passwd newusername

sudo /usr/openv/netbackup/bin/admincmd/bpnbaz -AddRBACPrincipal -user typeofpassword:FullyQualifiedDomainName:username

Example:

sudo useradd -m netbkadmin

sudo passwd netbkadmin

sudo /usr/openv/netbackup/bin/admincmd/bpnbaz -AddRBACPrincipal -user unixpwd:ng-nbu-primary1.vrts.tme.io:netbkadmin

  1. Next open a web browser and type this into the URL bar:

https://FQDN/webui

Example:

https://ng-nbu-primary1.vrts.tme.io/webui 

  1. Enter the username and password created in step 1. 

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.

 

 

  • A couple items items I noted during my install related to this guide:

    1. SSH (TCP 22) is not allowed by the security group created during the cloudformation deployment.  You will need to modify the security group settings to allow port 22 to speak to the primary server from the source subnet you are connecting from.
    2. The current CFT uses a legacy gp2 EBS volume as the root drive for the servers.  It is recommended that everyone utilize a gp3 EBS volume unless you have a specific reason to use gp2.
  • Boa tarde. tentei fazer o deployment e deu erro.

     was not successfully created: The following resource(s) failed to create: [PrimaryDNSRecordSet