cancel
Showing results for 
Search instead for 
Did you mean: 

Part 1: Deploying NetBackup in the Google Cloud Platform (GCP)

GNeil
Level 2
Employee

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

GNeil_4-1635877153850.png

To begin, log into your GCP portal and search for Veritas NetBackup in the GCP navigation bar and select “Veritas NetBackup 9.1”.

GNeil_5-1635877153850.png

You will be taken to the NetBackup 9.1 deployment page that gives an overview of the NetBackup software.  Click Launch to continue.

Primary Server Deployment

GNeil_6-1635877153850.png

  1. Enter a deployment name to identify it.
  2. Choose which Google Zone you’d like your deployment installed in.

 GNeil_7-1635877153851.png

  1. Next, we’ll choose the machine type we’d like for our NetBackup Primary server.  The size of your environment will vary greatly depending on your backup needs.  For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide.

https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073

GNeil_8-1635877153851.png

  1. Choose the type of boot disk and the size you’d like NetBackup to run on.

For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide.

https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073

GNeil_9-1635877153851.png

Now we’ll enter in the networking rules for our Primary server.  For more information regarding firewall port requirements for NetBackup, see the Veritas NetBackup Ports Reference Guide.

https://www.veritas.com/content/support/en_US/doc/80731497-149899093-0/v124789571-149899093

  1. Adjust the default network interface and/or add an additional network interface.
  2. Enter the source IP or range that can access the new server for SSH.
  3. Enter the source IP or range that can access the new server for HTTPS.
  4. Enter the source IP or range that can access the new server for VNETD.
  5. Enter the source IP or range that can access the new server for RESTful.
  6. Enter the source IP or range that can access the new server for VERITAS_PBX.

GNeil_10-1635877153852.png

Next, we’ll enter the installation parameters.  These steps determine if we’re deploying a Primary or Media server.  First, we’ll deploy a Primary server and then return to install our Media server.

  1. Select “primary” to deploy the Primary server.
  2. Give the Primary a hostname.
  3. Ignore the Media Server Hostname for now.
  4. Enter a service username.  This is not a user that will be able to log into the environment.  This user will only be used to start and stop NetBackup processes.
  5. Enter in a domain the new Primary will live in.
  6. Select true or false if there is a hosted zone created for the domain name in step 5.  If you select false, the deployment will create the hosted zone.
  7. Next we need to provide the new hosted zone name or the name of the existing hosted zone.
  8. Enter in your NetBackup license key.
  9. Ignore the Media Server Token for now.
  10. Enter in your NetBackup Usage Insights Key.

 

GNeil_11-1635877153852.png
Lastly, before we deploy, select if you’d like Stackdriver logging and monitoring.  Accept the Terms of Service and click Deploy.

GNeil_12-1635877153853.png
Now that the Primary has been deployed, we will deploy the Media server.

Media Server Pre- Requirements

To build our Media server and have it join the Primary, we need to generate a token from the Primary server.

GNeil_13-1635877153854.png

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 WebUI.  From Compute Engine > Instances use the remote access capability and log into the new Primary server.

  1. Create a new user that will 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

GNeil_14-1635877153854.png

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

GNeil_15-1635877153855.png

  1. On successful login you will be greeted with the following banner.  Click the X in the upper right corner.

GNeil_16-1635877153855.png

  1. Click on Tokens in the WebUI and create a new token and copy the Token Value.  We will need that value when we deploy our Media server.

GNeil_17-1635877153855.png

  1. Copy the Token Value and save it for later.

GNeil_18-1635877153856.png

  1. Go back to the GCP MarketPlace, search for Veritas NetBackup like we did for the Primary server deployment and Launch another NetBackup 9.1 deployment.

 

Media Server Deployment

GNeil_19-1635877153856.png

  1. Enter a deployment name to identify it.  This will be different from the Primary server deployment name.
  2. Choose which Google Zone you’d like your deployment to installed in.

 

GNeil_20-1635877153851.png

  1. Next, we’ll choose the machine type we’d like for our NetBackup Media server.  The size of your environment will vary greatly depending on your backup needs.  For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide.

https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073

 

GNeil_21-1635877153851.png

  1. Choose the type of boot disk and the size you’d like NetBackup to run on.

For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide.

https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073

GNeil_22-1635877153856.png

Now we’ll enter in the networking rules for our Media server.  For more information regarding firewall port requirements for NetBackup, see the Veritas NetBackup Ports Reference Guide.

https://www.veritas.com/content/support/en_US/doc/80731497-149899093-0/v124789571-149899093

  1. Adjust the default network interface and/or add an additional network interface.
  2. Enter the source IP or range that can access the new server for SSH.
  3. Enter the source IP or range that can access the new server for HTTPS.
  4. Enter the source IP or range that can access the new server for VNETD.
  5. Enter the source IP or range that can access the new server for RESTful.
  6. Enter the source IP or range that can access the new server for VERITAS_PBX.

GNeil_23-1635877153857.png 

Next we’ll enter the installation parameters for our Media server.

  1. Select “media” to deploy the Media server.
  2. Enter the Primary name given in the previous deployment.
  3. Enter a name for the Media server.
  4. Enter a service username.  This is not a user that will be able to log into the environment.  This user will only be used to start and stop NetBackup processes.
  5. Enter the domain we used for the Primary.
  6. Select true since we created the zone previously or with the Primary deployment.
  7. Provide the existing hosted zone name.
  8. Enter in your NetBackup license key.
  9. Put in the media server token generated from the Primary server in Media Server Pre-Requirements, step 6.
  10. Enter in your NetBackup Usage Insights Key.

GNeil_24-1635877153852.png

  1. Lastly, before we deploy, select if you’d like Stackdriver logging and monitoring.  Accept the Terms of Service and click Deploy.

GNeil_25-1635877153857.png

Now that the Media server has been deployed, we will validate the Media server has been added to the Primary server and deploy the CloudPoint server.

0 REPLIES 0