NetBackup thinks secondary instance is the Primary

Question

We are using Veritas' NetBackup to take full and t-log backups of our MS SQL 2016 databases. The MSSQL instance and databases reside on a three node cluster and HA with Always ON replication has been set up so one of the instances is the Primary and the other two are secondary's. Currently, node 1, P1, is the primary. The Netbackup jobs are set up to use the virtual cluster name and ip address. Let's call it P0. When the job runs, it gives an error that the database primary is not P3 and the backup for the database is skipped. So, my question is why does the NetBackup Job think that the Primary should be P3 and not P1 which it actually is? One observation is that when I look in Failover Cluster Manager at the P0 cluster, it says that the Current Host Server is P3. So, is this the reason the NetBackup job thinks that P3 is the Primary? If Yes, can I safely change the Current Host Server without incurring a failover? Also, it woul be nice, if this is the case that the Current Host Server would follow whwere the Primary is set when a failover occurs.

Answer 1

Hi,
Based on my understanding, this issue seems related to NetBackup configuration. I tried to do some test in my environment but I don’t have NetBackup in my system.
Since NetBackup is actually a 3rd party product, and we’re not very familiar with its detailed settings, I would suggest that you contact its vendor for their advice.
For your reference:
http://itdoc.hitachi.co.jp/manuals/oem/veritas/JP1V115VERINBU02300/NetBackup81_Troubleshooting_Guide_e.PDF
Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

Thanks for your understanding.
Best regards,
Danny

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.