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.
Announcing Veritas CloudPoint 2.0
Earlier this week we launched Veritas CloudPoint 2.0. Two press releases, one with Google and one with Microsoft kick-started the launch activities on Tuesday. We also posted a VOX blog on the CloudPoint 2.0 announcement - highlighting the new features and the availability of CloudPoint in Google's Cloud Launcher. Make sure you check out the blog as it also gives you links to more information. Read the blog With CloudPoint, we've created a disruptive technology. But for us to advance the disruption, we need your valuable feedback. So, I would like to ask you to continue sharing your feedback and questions in this forum. Thank you for all you do to help support Veritas CloudPoint. Thanks, Arjan
Forecast: Backup Exec with Increasing Cloudiness
A weather report that includes "cloudy" can bum you out, and IT designers may feel the same way when the term is applied to evolving infrastructure. Let’s lift the fog around Cloud and highlight how Backup Exec can help you today and in the near future.Thoughts and takeaways from Vision 2017
Wow. The second Veritas Vision conference is over. And what a week it was. Press conferences, technology announcements, great keynotes, surprising demos, valuable breakout sessions, and a list of sponsors that any conference would be lucky to have. To name a few: Microsoft, Google, IBM, and Oracle. So, what was the takeaway? -that Veritas is maniacally focused on helping organizations better utilize this asset that exists in each of their environments known as secondary data. As Veritas CPO, Mike Palmer iterated on stage, “secondary data is not only the most under-utilized asset in the enterprise, it’s also the biggest opportunity.” For more than two decades Veritas has lead the market in the areas of enterprise backup and recovery, software-defined storage, and eDiscovery/archiving. However, as the world continues to both create and depend on more and more data, a better way to harness the power of their information is clearly needed. The largest data estate in our customers' environments is their secondary data. By eliminating complexity from point products,making storage smarter and more scalable, and by giving customers unprecedented levels of visibility into their data, they can not only protect it better, reduce risk more effectively and lower the total costs of managing it all, but they can unlock the value that lies therein to uncover new insights that drive business forward. And as our customers continue to embrace new architectures like cloud, OpenStack, and containers, or new workloads likeNoSQL, or Big Data, the continued commitment to support them with the kind of industry leading technology, innovation, and engineering prowess was also clear. I’m proud of what I both saw and helped create this year at Veritas vision. There was a lot of excitement and optimism regarding Veritas’ outlook and vision for the future. The Cube was onsite hosting a number of interesting conversations, one with me and Ian below on what we aim to solve for customers with 360 data management for the multi-cloud: The Challenges We Aim To Solve: As part of a community give-back, we got to make Capes for Heros: http://capes4heroes.com, which was very special. And we got some great coverage on our announcements as well: CRN:Veritas Vision: Veritas Enhances Multi-Cloud Data Management, Strengthens Ties With Microsoft Azure Cloud TechTarget:Veritas 360 data management embraces cloud, dedupe, NoSQL Also great to see the positive comments on social from our AR/PR community as well: The simple truth about public cloud: In the end, it is still your responsibility for the app and data, not the provider.#vtasvision—@edwinyuen Kudos@Lylucason very smart keynote - strong narrative, clear news, competitive digs clever/tasteful, showed momentum#VTASvision—jbuff Most clever monologue on#dataprotectionever by Mike Palmer#VTASvision—jbuff Still a good crowd at day 2#vtasvision.—@krmarko Veritas senior execs take questions. Useful perspectives on selling the new strategy: focused on particular biz data problems.#vtasvision—@krmarko With#Veritasin#LasVegasto resolve the '#Information'#Techconundrum to drive value and avert risk.#MultiCloud#GDPR#DX#VtasVision—@sabhari_idc Yes, we're closer to#Hollywoodand it had a part it the dramatic#BackToTheFuturetheme intro into#datamanagement.#NoFate#VtasVision—@sabhari_idc The modern#dataprotection capability matrix demonstrated by#Veritasat#VtasVision.#BaaS#DRaaS#Containers#MultiCloud#BigData#DX—@sabhari_idc Veritas can reach APAC customers via GDPR zd.net/2fBezbU by@eileenscyu— @ZDNet Vision was a success. But now it’s back to the grind in helping customers solve real challenges with comprehensive solutions, and a vision to help them better utilize their secondary data. Keep a pulse on what’s going on with Veritas by following us on twitter at: @veritastechllc. Alex
