question

Marcel-1650 avatar image
0 Votes"
Marcel-1650 asked Criszhan-msft edited

Adding Node to upgraded SQL 2019 Failovercluster

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-generalwindows-server-clusteringsql-server-migration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

OlafHelper-2800 avatar image
0 Votes"
OlafHelper-2800 answered

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Criszhan-msft avatar image
0 Votes"
Criszhan-msft answered Criszhan-msft edited

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.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.