|
Has anyone ever seen this or know why this would happen?
I have a 5 year old windows 2003 cluster running a named instance of SQL Server 2005 enterprise.
During the install of SQL the log and data files were created on the H drive. (Making H:\\MSSQL.1\\MSSQL\\Data the default for both data and logs and H:\\MSSQL.1\\MSSQL\\Backup the default location for backups)
After the install we run a script to update the Reg to change the default locations as following:
Data = E:\\MSSQL.1\\MSSQL\\Data
LOG = F:\\MSSQL.1\\MSSQL\\Data
Backup = G:\\MSSQL.1\\MSSQL\\Backup
Script
Now last week the OS on the servers in the cluster were patched and after the reboot all of the default locations where changed back to:
Data = H:\\MSSQL.1\\MSSQL\\Data
LOG = H:\\MSSQL.1\\MSSQL\\Data
Backup = H:\\MSSQL.1\\MSSQL\\Backup
These servers have been patch several times throughout the years and this is the first time it has ever happened. We have seen it switch Server Authentication a few times from Mixed to Windows.
(comments are locked)
|
|
It sounds to me as though one of the servers in the cluster hasn't been set up the same way as the others. It might be worth checking the registry settings for all machines in the cluster. As I wrote elsewhere (http://thelonedba.wordpress.com/2010/11/09/on-master4idr-ckp-maintenance-plans-default-backup-directory-and-sql-server-configuration/),
Check that the appropriate directories are set up correctly across all cluster servers and their instances of SQL Server within the clusters.
(comments are locked)
|
|
Writing to the registry probably only did so on the node that was active at the time. On a failover it would be using the registry from a different node. Make sure that if you do registry work that all nodes are kept in synch.
(comments are locked)
|


Any updates...?