Unsolved
This post is more than 5 years old
2 Posts
0
2728
February 14th, 2017 04:00
MS SQL failover cluster backup not using NMM
Hello everyone,
I am having an issue trying to backup Microsoft SQL agent created *.bak and *.trn files from our 2 node failover cluster.
Current setup
We have a windows 2012r2 2 node failover cluster running SQL 2012. There are currently 7 SQL server roles installed.
I have configured, on NMC, 3 clients - one each for the physical nodes and one for the cluster. There are 7 different cluster backup clients configured, one for each of the different backup folders for each SQL server role.
So
Node1 - C: and D:
Node2 - C: and D:
clusterName - G:\backup
clusterName - H:\backup
clusterName - I:\backup
...
Currently Node1 is the owning/current host server for the cluster.
Networker has no issues backing up node1 and node2.
Networker has no issues backing up a failover cluster client as long as it is running on the node that owns the cluster.
Networker fails to backup a failover cluster client if it is running on the node that does not own the cluster.
When I try to browse the savesets for the clusterName client in NMC I can only see the filesytems/drives mounted on the owning node.
The clusterName client configuration includes remote access - *@* and save -c clusterName as the backup command.
The error reported for the failing clusterName clients is 6999:save.... No such file or directory.
Can anyone offer any advice or helpful diagnostic techniques to help resolve this problem.
Many thanks
ble1
2 Intern
•
14.3K Posts
0
February 14th, 2017 05:00
I'm a bit confused with this:
You have two nodes and it doesn't matter on which node (1 or 2) cluster is running as backup of virtual client will be always executed by accessing virtual IP/name assigned to cluster package. Is it possible that you used cluster name instead of name/IP assigned to failover group?
StuartHowarth
2 Posts
0
February 14th, 2017 07:00
Hi,
Thanks for the quick response.
I have configured the clients to use the clustername, rather than the instance name.
The clustername is sqlclus03, the cluster SQL roles are sqlclus03v01, sqlclus03v02....
The clustername, and SQL roles all have different IP addresses.
I thought you had to have the cluster instance clients configured against the clustername!
When I create a client using the cluster instance name, networker performs a full each time a backup runs - disregarding the schedule requesting an incremental.
ble1
2 Intern
•
14.3K Posts
0
February 14th, 2017 12:00
In backup command place save -c and it will work just fine after that.