Hi!
We are in the process of replacing our old 6-node MSSQL cluster with a new 4-node cluster that will be using Always On Availability Groups.
The existing cluster and it’s backups was configured many years ago by someone else who is no longer working here, and I am not a Windows Cluster, or MS-SQL person, but more of a storage person :-)
Now, i’m trying to wrap my head around what would/should be the “best practice” way of configuring this for backups & restore.
What i have done so far is of course to install the mssql-agent on all 4 physical nodes.
And from what i can figure out from reading through documentation, it seems i should create a “MSSQL AG Client” pseudo-client for each “ms sql availability group”, which would add up to around 15-20 different pseudo-clients.
However, when looking at the current existing configuration for the old MSSQL-cluster, it is only a single “pseudo-client” that contains all “ms sql availability groups”…. so i guess the question is, how did they make that happen ?
Have they used a different kind of pseudo-client, like the Windows Cluster client, that i have seen mentioned in this post: Mssql always on Failover Cluster Instances configuration | Community (commvault.com)
And what would be the recommended and “Best Practise” way of doing this ?
