Adding Node to upgraded SQL 2019 Failovercluster

Marcel-1650 26 Reputation points
2021-03-31T09:43:30.643+00:00

Hi,

I've got an SQL Failovercluster running with Windows Server 2016 and SQL 2019. That Cluster was recently updated from SQL 2016 and worked without issues.
But now I've noticed that when adding a new Node to an previously upgraded SQL Failover instance (over 2019 installer) I'm unable to move the database to that new Node.
Problem seems to be that the cluster is trying to access the database files with the wrong folder path. On the new Node he is trying to access MSSQL15.DATABASENAME folder while it's actually MSSQL13.DATABASENAME since this database was upgraded from 2016.
Has someone an idea how to fix this?

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,488 questions
SQL Server Migration Assistant
SQL Server Migration Assistant
A Microsoft tool designed to automate database migration to SQL Server from Access, DB2, MySQL, Oracle, and SAP ASE.
485 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
950 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Olaf Helper 40,246 Reputation points
    2021-03-31T10:29:01.763+00:00

    During installation SQL Server uses MSSQL + version number for default installation folders; that name remains after upgrade.
    The new node is a fresh installation? That's why the default name is different.

    No DBA use default folder for the system & user databases, especially not for a cluster installation.

    One option is to move the databases from default folder to a different user defined folder.

    0 comments No comments

  2. Cris Zhan-MSFT 6,601 Reputation points
    2021-04-01T10:14:20.63+00:00

    Hi @Marcel-1650 ,

    >But now I've noticed that when adding a new Node to an previously upgraded SQL Failover instance (over 2019 installer) I'm unable to move the database to that new Node.

    Do you mean that you cannot add a new node to the upgraded SQL Server failover cluster?

    Or you have successfully added a new node to the failover cluster, but it failed when you manual failover SQL Server to the new node?

    Can you show specific error messages. You can check the data path(Advanced) in the properties of the SQL Server cluster instance in SQL Server configuration manager on the new node.

    You may need to modify the startup parameters of the SQL Server cluster instance on the new node.

    0 comments No comments