Symantec Netbackup SQL Database in Cluster backup issue
Hi,
Let me explain the infrastructure which we have
- Windows 2008 R2 x64 two node cluster
- SQL 2008 cluster (We have SQL cluster with two different cluster instance running on each host)
- Netbackup 5220 Appliance
- Netbackup 7.5.0.4
We are having issue backing up one of the SQL server, where as we are able to backup the one SQL cluster instance which is running one of the cluster node.
The SQL cluster vitual hostnames
On node1 - we are running the cluster virtual1.domain.com
On node 2 - we are running the cluster virtual2.domain.com
But when we connect to the SQL cluster via SQL Management Studio for node1 we use the server name - virtual1
whereas for the second node we use the server name as - virtual2\instance
When we connect to create the NBU SQL script, the NBu SQL client will connect to virtual2\instance name and also when we create a .bch script the hostname within the script file is listed as virtual2\instance name.
While we create the NBU SQL policy we have mentioned the virtual2 name in the client list and the script, but the backup fail with, client couldnt able to connect.
Appreciate if any of you have come across same setup and resolved the problem of SQL backup using Netbackup 7.5.x.x
Regards
Shreeram
Comments 7 Comments • Jump to latest comment
Is the 5220 the master/media server?
Is the appliance on DNS or using local hosts file?
Have you confirmed successful forward and reverse lookup at OS level between master and both virtual names?
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
The NBU 5220 Appliance is a Master & Meida Server
DNS is configured and the hostnames are resolved. All forward and reverse lookups are working fine as well.
As mentioned the SQL hostname in the NBU SQL script is mentioned as SPSINTRADBCLUSTER\SPSINTERNET name which the NBU Master/media Server is not able to resolve. We have another SQL Server Instance within same cluster with SPSINTERDBCLUSTER which we are backing up without any issue as we connect to the client using client name SPSINTERDBCLUSTER, whereas another SQL cluster in same two nodes cluster we connect using SPSINTRADBCLUSTER\SPSINTERNET name and which is not getting resolved when we initiate a backup. I was worried, how this will be resolved. But I am able to connect to the Database using NBU SQL client and able to create a NBU SQL script.
Regards
Shreeram Rane
SPSINTRADBCLUSTER\SPSINTERNET is virtual-hostname\instance-name, right?
You only need the virtual hostname in the script and the policy: SPSINTRADBCLUSTER.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
Please also see :
http://www.symantec.com/docs/HOWTO69673 -
Performing backups in a cluster with a multi-NIC connection
http://www.symantec.com/docs/HOWTO69837 -
Performing restores in a cluster with a multi-NIC connection
Only use of default instance name is supported in cluster. If you configured SQL instance without defalt instance name, this is not supprted by NetBackup.
Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan
I read the reference to <default> as an example, not as a requirement.
I have always asked SQL dba's to install SQL with named instances when we had to configure their clusters.
At one customer we have clustered about 10 named instances spread across 3 nodes, each instance in own Service Group with unique virtual name.
SQLHOST <virtual-name>
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links
It s been resolved. Only changes which we need to do in the SQL backup script. Below are the details.
When we create a NBU SQL script from NBU SQL client will look like below
OPERATION BACKUP
DATABASE $ALL
OPERATION BACKUP
DATABASE $ALL
Thanks for all of your support and solutions.
Regards
Shreeram Rane
Would you like to reply?
Login or Register to post your comment.