Recent Discussions
Netbackup KMS
hi Guys, kindly educate me - At one of remote site our NBU server was short circuit. Rebuild done after 6 months and handover to backup guys on friday(27sept). We need to install NBU on it, it had tape backups with KMS encryption (i had documentation available). In 2019 -- NBU 8.1 was installed on window OS (hardware) + HP tape TL, KMS was configured( this encryption feature is free) then in year 2020 we upgraded NBU to 8.3.1. Cut to 27sept 2024 - i have to reinstall NBU - rebuild KMS and try to restore finance data. What NBU version should be installed --- 8.1 or 8.3.1 -- kindly educate me. [i cannot go to netbackup support]
Getting ms-windows assets via api
Hey guys and girls, I want to write a local check for my monitoring system (checkmk), so I can monitor if backups are running and if my servers are protected. I don't have much experience with Netbackup, a supplier set up the system for us, I'm just a backup admin (amongst many other things). I'm quite competent with python and api's, but haven't played around with netbackup's api until yesterday. For my checkmk 'local check' I want an overview of all machines that I make backups of, and when the last succesful backup was run. Now I have two different workloads: vmware and ms-windows. For the vmware workload, it's quite easy, I found there's an assetservice api endpoint, where I can get info on all my vm's, and when the last succesful backup was. Easy peasy! But for the ms-windows workload, it seems like it's a bit more complex. The assetservice api does not seem to recognize the ms-windows workload? I can get a list of all the recent jobs, look for the WINDOWS_NT type, and massage the data the way I want it, but then I have to aggregate all streams for a specific host, do manual stuff on it, etc. You guys know if there's an easier endpoint to use for this?
Inquiry regarding using Netbackup appliances across domain
We are currently managing two separate Netbackup domains, each with its own unique setup, and we are looking to make some changes to streamline our infrastructure. Below is a summary of current configuration. Domain one configuration: Master server with two Netbackup appliances( serving as media servers) Domain two configuration: Master server with two BYO servers( serving as media servers). LUN is assigned to these media servers from HP3par storage and configured as MSDP. We are trying to get rid off HP3par storage for future backups so, Is it possible to use the Netbackup appliances from Domain 1 as a media servers for domain 2 as well to manage future backups? If not, could you kindly suggest alternative approach to achieve this while eliminating the HP3par storage from domain 2.
BMR: Could not read saved configuration file=X:\bmrcli.xml
I am testing Bare Metal Recovery. Test environment is virtual (VMware).The recovered system is booted from boot ISO. It connects to the master server but during the step "Establishing restore environment" this error message is shown: The restore has stopped due to the following error: Could not read saved configuration file, file=X:\bmrcli.xml NetBackup servers and client version is 10.3. Any ideas? Thank you.Cross Provider Restore - Azure to AWS and Vice Versa!!
Hi Friends, Happy NetBackup 10.5 GA Day!! I've got a ton of new features I want to share with you, but this one is SUPER cool! At Veritas, we know that your enterprise cloud environments are heterogenous and need the ability to backup and restore your enterprise cloud virtual machines easily from AWS to Azure and vice versa. Veritas NetBackup continues to un-complicate the cloud by now offering cross cloud provider restore capabilities. Requirements Veritas NetBackup Snapshot Manager with connection credentials for your AWS and Azure environments. Note: A backup from snapshot copy must be present to restore the virtual machine to an alternate cloud provider. Cloud Snapshots can continue to be used for restores at the same cloud provider. How to Use – Azure to AWS After a backup has been completed of a cloud virtual machine, navigate to Workloads > Cloud and find the virtual machine you wish to restore to an alternate cloud service provider (CSP). Click on the virtual machine to proceed. Find the backup you wish to restore and click on Restore Virtual Machine. On the Restore Virtual Machine page, select the AWS equivalents for Azure. Target CSP Configuration Name Region to restore to Your AWS Account Number The name the VM will have in AWS. The instance machine type The AMI ID. Note: The two attached Azure volumes at the bottom of the screen image will be restored into two volume on AWS. On the next screen continue to select the AWS equivalents of the Azure VM. AWS Zone Network configuration Network security group Advanced options After the restore, log into AWS and the virtual machine will be available for use. How to Use – AWS to Azure After a backup has been completed of a cloud virtual machine, navigate to Workloads > Cloud and find the virtual machine you wish to restore to an alternate cloud service provider (CSP). Click on the virtual machine to proceed. Find the backup you wish to restore and click on Restore Virtual Machine. On the Restore Virtual Machine page, select the Azure equivalents for AWS. Target CSP Configuration Name Region to restore to Your Azure subscription Resource group in Azure to restore to The name the VM will have in Azure. The instance machine type Note: The two attached AWS volumes at the bottom of the screen image will be restored into two volume on Azure. On the next screen continue to select the Azure equivalents of the AWS VM. Azure Zone Network configuration Security group Advanced options After the restore, log into Azure and the virtual machine will be available for use.
Netbackup disk storage replacement
Hi, We are replacing the existing Netbackup disk storage with different storage model and would like to understand how to migrate data from old storage to new? Has anyone tried storage level block migration? would it really work? The only option I know is to connect the new storage to media server and configure storage units Either setup SLP or manually duplicate all images from existing storage to new storage. Retire the existing storage once migration is completed and point backups to new storage unit. But this approach might take lot of time depending on the amount of data on existing disk. Any other thoughts or advises on this please? ThanksVMware backup failures with status code 200
Having a heck of a time trying to figure this out. 14 of my 21 VMware policies are failing with a status code 200 for some reason. Credentials are good and we can do a test query with no issues. Windows 2012 VMware Backup Host 5.5 Update 2 7.6.0.2 and I verified the VDDK is 5.5.0 I have attached all of the logs that would actually run. I cranked VXMS up to 5, but no log was created as I am guessing it just doesnt get that far into the process. Detailed Job Status: 07/22/2015 11:00:59 - Info nbjm (pid=1310) starting backup job (jobid=3391315) for client MEDIA_SERVER, policy Omaha_VMware_INFOBLOX, schedule Full_Daily 07/22/2015 11:00:59 - Info nbjm (pid=1310) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=3391315, request id:{D84F647C-308A-11E5-9F49-002128A6F97C}) 07/22/2015 11:00:59 - requesting resource XP53TAPE009 07/22/2015 11:00:59 - requesting resource xp53tape001.NBU_POLICY.MAXJOBS.Omaha_VMware_INFOBLOX 07/22/2015 11:00:59 - granted resource xp53tape001.NBU_POLICY.MAXJOBS.Omaha_VMware_INFOBLOX 07/22/2015 11:00:59 - estimated 11832060 kbytes needed 07/22/2015 11:00:59 - begin Parent Job 07/22/2015 11:00:59 - begin Application Resolver: Start Notify Script 07/22/2015 11:01:00 - Info RUNCMD (pid=15674) started 07/22/2015 11:01:00 - Info RUNCMD (pid=15674) exiting with status: 0 Operation Status: 0 07/22/2015 11:01:00 - end Application Resolver: Start Notify Script; elapsed time 0:00:01 07/22/2015 11:01:00 - begin Application Resolver: Step By Condition Operation Status: 0 07/22/2015 11:01:00 - end Application Resolver: Step By Condition; elapsed time 0:00:00 07/22/2015 11:01:00 - begin Application Resolver: Resolver Discovery Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: Resolver Discovery; elapsed time 1:30:04 07/22/2015 12:31:04 - begin Application Resolver: Policy Execution Manager Preprocessed 07/22/2015 12:31:04 - Warning nbpem (pid=1367) VM retrieval failed, server = [53apps178vm]. Operation Status: 200 07/22/2015 12:31:04 - end Application Resolver: Policy Execution Manager Preprocessed; elapsed time 0:00:00 07/22/2015 12:31:04 - begin Application Resolver: Stop On Error Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: Stop On Error; elapsed time 0:00:00 07/22/2015 12:31:04 - begin Application Resolver: End Notify Script 07/22/2015 12:31:04 - Info RUNCMD (pid=27555) started 07/22/2015 12:31:04 - Info RUNCMD (pid=27555) exiting with status: 0 Operation Status: 0 07/22/2015 12:31:04 - end Application Resolver: End Notify Script; elapsed time 0:00:00 Operation Status: 200 07/22/2015 12:31:04 - end Parent Job; elapsed time 1:30:05 scheduler found no backups due to run (200)How Does netbackup store credentials?
Hi guys, I´m being trying to find information about this but no success, does anyone know how NetBackup stores credentials? For example, when we register an Oracle instance or add a Vmware Vcenter, we add credentials, but where or how are those credentials saved6 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.
