Is there a way to backup the OS through NetBackup?
I am curious if it is possible to back up the OS using only netbackup software without using bmr or vsr. There are system state and shadow copy components in the backup selection, and I am wondering if it is possible to backup and restore the server OS through these. If you know any ideas or technote addresses, please let me know.
VMware 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)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.Netbackup incorrectly assigning MediaIDs at first but corrects when deleted & re-scanned.
Netbackup v10.2.0.1 - We're importing & cataloging (P1/P2) 1000s of tapes and we've got a script that does inventory (vmupdate) when the tapes are loaded for multiple media agents. The MediaID generation rule are applied, for few random tapes it does not add the initials eg.: NS is not added for tape NS1234 but it is updated as 1234L6 (default inventory) which fails the import jobs as it cannot find the tape. The same tapes [updated as 1234L6] when deleted from console and re-scanned manually from console gets the correct barcode NS1234. It is random & intermittent (but happens atleast once in 2 days) so I was hoping to get more details from Logs when it happens. It will be good to know which logs are required apart from bptm on media agents and if there are any other robot/inventory specific logs with higher debug ? Thank you.
