cancel
Showing results for 
Search instead for 
Did you mean: 

How to Backup a Two Node Windows SQL Cluster

Brian78
Level 3

Hola, 

All experts over here, I am newbie when it comes to Netbackup. I want to backup my SQL 2-Node cluster on Windows 2016 Machines. I want to know what exactly i need to do to make sure the backup won't fail when the cluster failover. I tried reading up the SQL NBU guide but i didn't quite understand that being a new to NBU world. 

My Environment:-

1. 2-Node SQL cluster running on Windows 

2. I have a Seperate 10G connection to run my Backups

What needs to be exactly put into Netbackup policy to backup the Windows SQL cluster ??

 

Thanks in Advance,

Brian

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Brian78

Not sure how else to explain....


Configuring backups of clustered SQL Server instances (legacy SQL Server policies): https://www.veritas.com/content/support/en_US/doc/17221771-126559330-0/v14764142-126559330 
uses examples that shows the virtual hostname for SQL on the Production interface - VIRTUALSERVER. Your example: SQLSERVER
This is the the virtual IP address that is configured in DNS and in the SQL Cluster Resource group and used for 'normal' SQL operations.

What I was trying to explain, was that an additional IP address is needed on the backup network. :
Each node should already have a base IP on the backup network (10G), right?
You now need another virtual IP on the backup network.
This IP address will need to be defined in DNS and linked to a virtual hostname (SQLSERVER-BK). 
This virtual IP address also needs to be defined in the same cluster resource group as the SQL instance so that it can fail over along with all other resources in the SQL resource
 group. 

This means that the SQL cluster resource group will have TWO IP resources -
- one for normal SQL operations on the production network: IP link to SQLSERVER.

- 2nd IP resource for the backup network: SQLSERVER-BK.

View solution in original post

11 REPLIES 11

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

See this section in NBU for SQL manual:

Configuring backups of a SQL Server cluster when you have multiple NICs (SQL Server Intelligent Policies)

https://www.veritas.com/support/en_US/doc/17221771-126559330-0/v115886395-126559330

 

Hi Maria,

Thanks for responding. I am using RDM so my backup is script based. 

May i know which virtual name i need to choose in the client selections ?

Mouse
Moderator
Moderator
Partner    VIP    Accredited Certified

I think the technote is not being very clear, but I'll try to explain. You may need to have another virtual IP bound to the 10GbE backup interface on top of the access interface/primary virtual IP of the SQL server, this is to make sure NBU will follow the required interface/IP settings. You need to configure also a different hostname in DNS for that IP and use that hostname in the SQL backup script. As the virtual IP will failover along with SQL resources, you should be able to always back up SQL through the backup interface IP.

Thanks for your reply. The technote doesn't speak about creating a virtual name maybe my DBA should know ill check with and feedback.

It would be much easier if you have a pictorial representation of how to configure the SQL cluster backup. (Apologies if desire is too much but being new to NBU i really feel that) Sigh... Struggling time :( 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
@Brian78
This is not a SQL 'thing'. Rather networking an cluster config.

The NBU for SQL manual unfortunately assumes that you would know all of this:
The 10G interface will have its own virtual IP address (probably base IPs as well for each node). This IP address will need to be defined in DNS and linked to a virtual hostname.
Furthermore, this virtual IP address will need to be defined in the same cluster resource group as the SQL instance so that it can fail over along with all other resources in the SQL resource group.
(Not sure about MS terminology. In Veritas Cluster, it is called a Service Group.)

DPeaco
Moderator
Moderator
   VIP   

Dude, I feel your pain.

My team and I are data protection and disaster recovery specialists(engineers) and we aren't allowed to be involved in O/S installs, configs, storage setups, and the like. We are responsible for backing up hosts and we would like to do exactly as you are asking. I've read the docs/manuals and they are about as clear as "mud" to someone who doesn't and cannot have access to look and do as needed. We don't have access to the Windows servers without a special security request being approved for each host we need access to and that's only good for 48 hours.

We are a very strong Linux/Unix shop and have been for decades. Solairs, AIX, HP-UX, RedHat, CentOS, and etc. We used to support Tru64 before it got retired.

Thanks,
Dennis

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello Brian,

RDM is not restriction for SQL Intelligent policies. It is a restriction for VMware-based SQL policies. So I think you can use the guide mentioned above.

regards

Michal

Mike, 

Sorry for not describing my enviroenment in detail. Ours is VMware based shop with windows 2K6 running.

Master Server/Media Server and clients --> Windows 2016 

We have SQL cluster nodes which are running on RDM 

We do have Stanalone SQL running on VMDISK and we are planning to deploy SQL Intelligent policies.

Thanks,

Nayab

 

 

 

 

@Marianne

To link the IP to the SQL virtual hostname do i need to do anything on the cluster ? I mean create the DNS record as SQLSERVER-BK ? because i already have an production IP associated with my SQLSERVER if i go head and link another IP to it will it cause any issue ? Else if i create DNS record as SQLSERVER-BK and link my Backup IP and configure my policy pointing to SQLSERVER-BK it makes sense ? And backup run as normal during failover as well ?

I have 3 Network Interface in 2-Node cluster 

1. Heartbeat

2. Production/Management

4.Backup

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@Brian78

Not sure how else to explain....


Configuring backups of clustered SQL Server instances (legacy SQL Server policies): https://www.veritas.com/content/support/en_US/doc/17221771-126559330-0/v14764142-126559330 
uses examples that shows the virtual hostname for SQL on the Production interface - VIRTUALSERVER. Your example: SQLSERVER
This is the the virtual IP address that is configured in DNS and in the SQL Cluster Resource group and used for 'normal' SQL operations.

What I was trying to explain, was that an additional IP address is needed on the backup network. :
Each node should already have a base IP on the backup network (10G), right?
You now need another virtual IP on the backup network.
This IP address will need to be defined in DNS and linked to a virtual hostname (SQLSERVER-BK). 
This virtual IP address also needs to be defined in the same cluster resource group as the SQL instance so that it can fail over along with all other resources in the SQL resource
 group. 

This means that the SQL cluster resource group will have TWO IP resources -
- one for normal SQL operations on the production network: IP link to SQLSERVER.

- 2nd IP resource for the backup network: SQLSERVER-BK.

@Marianne Thank you so much there is still hope in the forums/communities. This is really great place.