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.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.
Update on Microsoft SharePoint platform support (Online and Server)
Microsoft continues to evolve the SharePoint collaboration platform. SharePoint is now available both online as part of the Microsoft Office 365 service and as a standalone server. For Microsoft Office 365 Veritas recently introduced Veritas SaaS Backup with support for Microsoft Office 365, Google G-Suite and SalesForce. Veritas SaaS Backup support for Microsoft Office 365 includes support for Email, SharePoint and OneDrive with more information available athttps://www.veritas.com/product/backup-and-recovery/saas-backup/preview. Microsoft SharePoint platform continues to be an important part of Veritas Backup Exec customer’s on-premises environments. Microsoft SharePoint 2016 is the latest server-version of the platform and continues to be on our radar. Please keep monitoring this forum for additional information and latest updates on Microsoft SharePoint platform support. BackupMikko
Veritas Appliances Inspire at Microsoft Partner Event
Just recently back from Las Vegas and an inspiring week meeting with numerous Microsoft and Veritas partners and forging new business partnership relationships for Veritas' data protection and Long-Term Data Retention Appliances. Some of the conversations I had here started with question on how Veritas hardware-based solutions align with Microsoft’s offerings, particularly Azure, and as an MS partner, how does it benefit my customers’? Interestingly enough, Microsoft has apparently started their own hardware division. I’d speculate it’s a consolidation of resources to develop hardware to power their Azure services. Back to the question at hand on Veritas Appliances. The answer is really pretty simple the Veritas family of data protection and LTR solutions all seamlessly integrate with Azure, protecting an organizations most critical assets on premises and in the cloud. Rather than spilling more ink on the value of Veritas Appliances here in the VOXosphere, you can watch my Wikibon TheCubeinterview on this topic and more. Thenand come back to VOX to continue the conversation.
Video guidance: How to configure Backup Exec to use Microsoft Azure cloud storage
Do you haveBackup Exec deployed in the Azure cloud? Please watch the latest video by the Veritas Backup Exec engineering team, demonstrating how to configureBackup Exec to use Azure cloud storage. In this video, we guide you through creating cloud storage for a Backup Exec server deployed in Azure, then take a backup and carry out a restore to confirm functionality.Video guidance: How to deploy Backup Exec from Microsoft Azure Marketplace
Are you seekingto run Backup Exec in Azure, but unsure of how to do so? Please watch our video, How to deploy Backup Exec from Azure Marketplace, where we guide you through creating a Backup Exec server running in the Microsoft Azure Cloud.
