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 Give the Stack a name that will identify it. Next, we’ll enter the configurations for the NetBackup Primary Server. Give your NetBackup Primary server a name. Choose the Server Instance Type. Select the NetBackup Primary Server installation volume size. Media Server Here we enter information for the Media Server: Give the NetBackup Media server a name. Choose the Server Instance Type. Select the NetBackup Media Server installation volume size. CloudPoint - Configurations Next, we’ll enter information for the NetBackup CloudPoint Instance. Select the OS type you’d like for the CloudPoint server. Select the Instance Type. Enter in the size of the CloudPoint Volume. Enter an Elastic IP if you need one. Enter the HTTP Proxy if one is use. Enter the HTTPS Proxy if one will be used. Enter a NO Proxy if one will be needed. Common Configurations Now enter the Common Instance Configuration Parameters. Select an SSH Key Pair so you can SSH to the new environment. This step needs to be completed prior to this point. 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. Enter the VPC ID you’d like to deploy the NetBackup stack in. 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. Select the Availability Zone the stack will be installed in. Choose the VPC CIDR block the stack will use. 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. 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. 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. 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. Enter your NetBackup License Key. 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. Enter the username for CloudPoint. Give the user a password. Enter any additional names you’d like to be added to the TLS certificate. The default CloudPoint port is 443, customize if desired. 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 Enter the NetBackup Cloud SNS Topic ARN. This is only required if you wish to receive notifications. Enter the NetBackup CloudPoint CMK ID. This is only necessary if you are using a Key Management Service (KMS). Enter the NetBackup CloudPoint CMK Region. This is only necessary if you are using a KMS. 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. 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 Next open a web browser and type this into the URL bar: https://FQDN/webui Example: https://ng-nbu-primary1.vrts.tme.io/webui 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.
[Snapshot Manager] Inconsistency between Cloud and Storage sections
Hello! Looking for help, please. My situation is the following: I was faced with an enviroment with an old CloudPoint server that failed on upgrading, resulting in the loss of the images and configuration. Upon fresh installation of a new VM of the Snapshot Manager 10.3, i promptly configured the Cloud Section of the Web UI Primary server and added the provider configuration (Azure). All the permissions have been granted to the Snapshot Manager regarding Azure. Protection Plans created, protected assets selected. Problem is, even thou the jobs are coming through with status 0, i am unable to find any recovery points for the assets. Also, upon investigation, i found on the Storage -> Snapshot Manager section, that the Primary Server is configured as a Snapshot Server, with the old version (10.0). This was done on the old configuration and i have no idea as to why it is present there. Trying to connect does not work, error code 25 as well as retrieving version information. Trying to add the new Snapshot Manager will result in Entity alredy exists error message. Could this storage configuration be related? If so, any suggestions as how to fix it? (I am also unable to delete the old Cloudpoint from the Web UI, but it is disabled) Primary server version is 10.3 New Snapshot Manager is 10.3 Old Cloudpoint was 10.0, already decomissioned. Thank you!
NBU in Azure - Snapshot Manager
Hello, I would like to know if users have tested and installed the Snapshot Manager solution in the cloud (Azure or other) and their feedback on this solution? Did you encounter any problems with the configuration? Do you manage to backup many workloads (VMs)? How is your configuration approximately? Personally I have installed a complete environment (Primary, Media with MSDP-C and Snapshot Manager) and I have a lot of stability problems with the Backup... This topic is more about discussing the product. Thanks for your feedback!Snapshot Manager - Someone use it on production?
Hello, I would like to know if users have tested and installed the Snapshot Manager solution in the cloud (Azure or other) and their feedback on this solution? Did you encounter any problems with the configuration? Do you manage to backup many workloads (VMs)? How is your configuration approximately? This topic is more about discussing the product. Thanks for your feedback!Part 1: Deploying NetBackup in the Google Cloud Platform (GCP)
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 GCP portal and search for Veritas NetBackup in the GCP navigation bar and select “Veritas NetBackup 9.1”. 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 Enter a deployment name to identify it. Choose which Google Zone you’d like your deployment installed in. 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 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 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 Adjust the default network interface and/or add an additional network interface. Enter the source IP or range that can access the new server for SSH. Enter the source IP or range that can access the new server for HTTPS. Enter the source IP or range that can access the new server for VNETD. Enter the source IP or range that can access the new server for RESTful. Enter the source IP or range that can access the new server for VERITAS_PBX. 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. Select “primary” to deploy the Primary server. Give the Primary a hostname. Ignore the Media Server Hostname for now. 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. Enter in a domain the new Primary will live in. 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. Next we need to provide the new hosted zone name or the name of the existing hosted zone. Enter in your NetBackup license key. Ignore the Media Server Token for now. Enter in your NetBackup Usage Insights Key. Lastly, before we deploy, select if you’d like Stackdriver logging and monitoring. Accept the Terms of Service and click Deploy. 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. 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. 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 Next open a web browser and type this into the URL bar: https://FQDN/webui Example: https://ng-nbu-primary1.vrts.tme.io/webui Enter the username and password created in step 1. On successful login you will be greeted with the following banner. Click the X in the upper right corner. 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. Copy the Token Value and save it for later. 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 Enter a deployment name to identify it. This will be different from the Primary server deployment name. Choose which Google Zone you’d like your deployment to installed in. 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 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 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 Adjust the default network interface and/or add an additional network interface. Enter the source IP or range that can access the new server for SSH. Enter the source IP or range that can access the new server for HTTPS. Enter the source IP or range that can access the new server for VNETD. Enter the source IP or range that can access the new server for RESTful. Enter the source IP or range that can access the new server for VERITAS_PBX. Next we’ll enter the installation parameters for our Media server. Select “media” to deploy the Media server. Enter the Primary name given in the previous deployment. Enter a name for the Media server. 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. Enter the domain we used for the Primary. Select true since we created the zone previously or with the Primary deployment. Provide the existing hosted zone name. Enter in your NetBackup license key. Put in the media server token generated from the Primary server in Media Server Pre-Requirements, step 6. Enter in your NetBackup Usage Insights Key. Lastly, before we deploy, select if you’d like Stackdriver logging and monitoring. Accept the Terms of Service and click Deploy. 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.Part 2: Deploying NetBackup in the Google Cloud Platform (GCP)
Validate Primary and Media Servers in NetBackup Now that the Primary and Media servers have been created, we will log into NetBackup to check on the status of the Primary and Media. In the NetBackup WebUI, click on Security > Hosts in the left navigation panel. Ensure the Primary and Media are listed. CloudPoint Server Deployment After the Primary and Media servers have been deployed and validated that they are listed in Hosts, it’s time to deploy the CloudPoint Sever. Search for Veritas NetBackup Cloudpoint and select Veritas NetBackup CloudPoint 9.1. Click on Launch to launch the NetBackup CloudPoint 9.1 deployment. Give the CloudPoint deployment a name and select the OS Image. Choose the Machine Type CloudPoint will run on. For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide and Veritas NetBackup CloudPoint Install and Upgrade Guide. https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073 https://www.veritas.com/content/support/en_US/doc/140789355-148057836-0/v141580670-148057836 Select the type and size of the Boot Disk CloudPoint will run on. For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide and Veritas NetBackup CloudPoint Install and Upgrade Guide. https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073 https://www.veritas.com/content/support/en_US/doc/140789355-148057836-0/v141580670-148057836 Enter the size of the CloudPoint Data Disk. If you are doing an upgrade, the “Cloudpoint Data Disk” is where your existing CloudPoint Data Disk is located. For Example: /cloudpoint For more information on sizing your NetBackup environment, see NetBackup Backup Planning and Performance Tuning Guide and Veritas NetBackup CloudPoint Install and Upgrade Guide. https://www.veritas.com/content/support/en_US/doc/21414900-146141073-0/v146020053-146141073 https://www.veritas.com/content/support/en_US/doc/140789355-148057836-0/v141580670-148057836 Select the Zone that CloudPoint will be installed in. Choose the Network interfaces for your CloudPoint deployment. Enter the source IP address range that will be able to access the CloudPoint server. This is needed for RabbitMQ traffic. Enter the source IP address range that will be able to access the CloudPoint server. This is needed for HTTPS traffic. Enter in the service account ID that has Editor and Secret Manager Secret Accessor roles attached to it. These are needed during the CloudPoint creation. If no name is entered, the default GCP account user will be used. Enter in an SSH public key to this instance if one exists. Enter in the username for NetBackup CloudPoint. Note - This will be used later to add CloudPoint to the Primary server. Note - The password for this user can be retrieved on the CloudPoint deployment page. Enter in any other names or aliases that need to be part of the TLS certificate. Enter the port CloudPoint will use. If you would like regular snapshots of CloudPoint, click the checkbox. A client email address must be entered to enable regular snapshots. The Private Key Secret is a secret name which stores the service account private key. Confirm that the Secret Manager API has been enabled, accept the Terms of Service and click on Deploy. NetBackup CloudPoint has been successfully deployed; these warnings can be ignored. Add CloudPoint Server to Primary After a successful CloudPoint server deployment, we need to add the CloudPoint server to the NetBackup Primary server. Retrieve the name of your newly created CloudPoint server from the VM instance in GCP. Log into the WebUI of the Primary server created earlier in the document. Navigate to Workloads > Cloud > CloudPoint servers. Click on the + Add button to add the newly created CloudPoint server. Enter the name of the server collected in Step 1. Enter the port selected during the CloudPoint install. Click on the Validate button. Click on the Accept button. Enter in the username for CloudPoint created earlier in this document. Enter in the password for this user and click on the Add button in the lower right corner. Note – The link to the password can be found on the deployment page for the CloudPoint server. Navigate to Security > Hosts and we can see all three of the created components successfully registered with the Primary.Deploying NetBackup in Azure Cloud: Complete steps
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 Azure portal and navigate to the Marketplace. Search for “veritas” in the Marketplace search bar. When the Veritas products appear, select “Veritas NetBackup”. A similar screen should appear to the image above. Here we choose Veritas NetBackup 9.1 and click on the Create button. Basics The first screen to appear asks for some basic information regarding the NetBackup environment you’d like to create. Enter the Subscription you’d like to deploy in. Either select an existing Resource group or create a new one. In the below example a new resource group is created. Select the region to build your NetBackup environment. Installation Type allows you to deploy a Primary, Media, and/or CloudPoint servers. This step creates a user that can log into the new environment. This is NOT the user that will start and stop NetBackup processes, unless chosen to do so in Primary Server Details – Step 4. Note – If the user is not root, that user must be given security administrator and backup administrator permissions to log into the webui. See Logging In, later in this document, for steps on how to do this. How the user administrative user will login to the new environment. This is the password the new administrative user will use to log into the new environment. Enter your license key. Enter the DNS zone the new environment will live in. In this step, enter either the new DNS zone name or the existing zone you will use. Click next when the following information has been entered. Primary Server Details In this screen, put in the information regarding the primary server. Name the primary server. Enter the size of the primary server. This will greatly depend on your environmental needs. Enter in your “usage insights registration key”. Enter the name of the user that will start and stop NetBackup processes. This is NOT the user that will be used to login to the environment. Enter the name of the virtual environment the primary host will connect to. Note – Duplicate virtual network names are not allowed. Enter the subnet information the primary will reside on. Here you can give the Public IP address a name to identify it. Note – Duplicate Public IP names are not allowed. Enter the name the primary server will be known by in DNS. When all of the information has been entered, clicked Next. CloudPoint Server Details If you’ve chosen to create a CloudPoint server, the image above will appear. Enter in the following information as it pertains to your deployment. Enter the virtual machine name for the CloudPoint server. Choose the machine type, CPU and memory and the data disk size. These will vary greatly depending on the size of your environment. Specify if the Primary and CloudPoint servers will be on the same virtual network. Enter in a name for the CloudPoint public IP. Note – Duplicate public IP names are not allowed. Enter the name the CloudPoint server will be known in DNS. If CloudPoint is on a different network than the Primary server. This is the network CloudPoint will access NetBackup. Enter any proxy values needed to configure CloudPoint with a proxy server. Select Yes, if you want to take a snapshot of the CloudPoint server once daily and store it in the same resource group, the stored snapshots can be used for recovering or upgrading CloudPoint. If you select yes, you will need to provide tenantId, ClientID, SecretKey values of the subscription where CloudPoint is being deployed. Enter in a name for the CloudPoint user and the password associated with the account. If the CloudPoint server will be known by any other names than given in step 1, enter them here. These names will be used to generate a server certificate for the CloudPoint host. Enter the port number used by CloudPoint. Default is 443. Media Server Details If you’ve chosen to create a Media server, the image above will appear. Enter in the following information as it pertains to your deployment. Enter the host name for the Media server. Choose the CPU and memory size. These will vary greatly depending on the size of your environment. Specify if the Primary and Media servers will be on the same virtual network. Enter in a name for the Media server public IP if desired. Note – Duplicate public IP names are not allowed. Enter the name the Media server will be known in DNS. Review + Create After the validation has passed, review your choices and select Create. Deployment is in Progress Once the deployment has been started, you will see a similar image to the one above. At this point, no more manual intervention is needed until the deployment is complete. Your Deployment is Complete Azure will automatically bring up the above page when the deployment is complete. Go to the resource group where the new machines have been created to log into the new NetBackup 9.1 environment. Logging In Note – If the user that was created is not root, that user must be given security administrator and backup administrator permissions to log into the webui. Log into the NetBackup Primary server using the newly created user from Basics – Step 5. Type the following command: sudo /usr/openv/netbackup/bin/admincmd/bpnbaz -AddRBACPrincipal -user typeofpassword:FullyQualifiedDomainName:username Example: sudo /usr/openv/netbackup/bin/admincmd/bpnbaz -AddRBACPrincipal -user unixpwd:ng-nbu-primary1.eastus2.cloudapp.azure.com:bkadmin Next open a web browser and type this into the URL bar: https://FQDN/webui Example: https://ng-nbu-primary1.eastus2.cloudapp.azure.com/webui Enter the username and password created in Basics – Step 5 and 7 and click Sign in. 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.
CloudPoint Admin guide query
The CloudPoint Admin guide states the following... CloudPoint does not support disk-based protection for applications that store data on virtual disks or storage spaces that are created from a storage pool. While taking snapshots of such applications, the disk-based option is not available. Our NBU servers in Azure have MSDP pools to store backups that are built using 16 locally attached virtual drives configured in a Microsoft storage pool. Does the above mean we would be unable to snapshot these virtual machines?
