Force NBSERVER setting in an MSSQL Intelligent policy batch file
Hello I have a new Netbackup 5250 appliance that is taking backups for a Production and Lab environment. The Management Interface of the Appliance is configured in the Production environment. The Appliance has different NICs configured on the Prod and Lab networks for backup payload data. I have a problem with Lab MSSQL intelligent policies that wants to use the Production Management Interface for backups. Since the Lab network does not have access to the Prod network, the Lab MSSQL client cannot be backed up using the Management Interface of the Appliance. I was able to grab the .bch file that is auto-generated on the client to see the NBSERVER setting and it is the Appliance Prod hostname. So my question is, is it possible to force/override the NBSERVER setting in the autogenerated .bch file for Intelligent MSSQL Policies? The same client is able to be backed-up in a regular Windows policy since it is using the right hostname of the Appliance. Example in the auto-generated .bch file: Instead of, NBSERVER = "Prod5250hostname" (this is the autogenerated config right now) I want NBSERVER = "Lab5250hostname" (same appliance but different network interface) I could create a DNS entry in the Lab DNS server to point to the IP of the Appliance Lab interface, but I would like to avoid that. Thank you.983Views0likes3CommentsSQL Metadata DB job
Hello All, this is really driving me crazy. I recently noticed some extra jobs under SQL SIP backups with file list as *md.<DBname>* which runs in the end . I thinks its a Metadata job which tracks of all DBs ranunder tht policy schd but i couild not find any documentation which explains its working. I see md.master md.msdb and on many servers i can see md.(any application DB). so how does it woks, any one please share some insight1.2KViews0likes4CommentsMSSQL Policy - how to configure an exclude list
I am trying to figure out how to add an exclude list to an MS-SQL-Server Policy. The Backup Selection List is WHOLE_DATABASE with multiple instances and the Database Name directive of $ALL (I know I can manually select which databases to backup but I don't want to be responsible if a new database is added to the environment and it isn't added to the selection list). Any help will be greatly appreciated. The master server is running 7.7.3 on Solaris 11, the media server is also 7.7.3 running on Solaris 11 and the client is running 7.7.3 on Windows 2012 and the Windows 2016 edition of MSSQL.Solved1.9KViews0likes4Commentsservice account for mssql
how do you use a diffrent user account for sql vs the rest of the backup? the ui shows the sql is using the servers logon account the question, i am unsure how to ungrey out the mssql option to choose an alternate account. I have also attempted to change the account in the actual backup configuration but that does not seem to work either. anyone have thoughts?1.3KViews0likes2CommentsSQL 2014 Mirror on VMware
Backing up SQL 2014 Mirrored VMs on VMware. Netbackup 7.7.1. The backups are always partially successful with a status 1. The Application State Capture job on the passive node returns the following results: Warning ascc (pid=29156) MSSQL: Skipping database MSSQLSERVER\DB_NAME. The database is in the RESTORING state and cannot be protected. Just want to confirm this is normal behaviour since it's the secondary node. I find it odd that it would return a status 1 for this reason. I would think that the parent job would be able to determine whether the DBs that are in a "restoring state" were picked up in the child job that runs on the primary node.Solved2.1KViews0likes8Comments