Database files list on one drive in master.sys.master_files, but show on another in the file system

We have a one node cluster sql server instance where the machine was patched/updated and re-booted this past weekend.  The machine came up, but the SQL Server did not because it could not locate RestoreCheckpointDB24.ckp on an
M drive.  If I RESTOREFILELISTONLY on my backups everything was clearly on an N drive previously.  To get by the error, our network team changed a registry key pointing to
N drive to M drive and everything magically came up.  The file system and failover cluster manager are now showing all files to be on an
M drive, but if you query master.sys.master_files everything is showing on the
N drive.  Anyone know how this is possible and how to resolve???
As well, a log shipping session is now broken because it's copying to a missing
N drive and my Management->SQL Server Logs folder is empty as well. 
Any ideas?  I'm completely baffled as well as our network guys. 
Thanks!

I'm thinking your problem is:
"To get by the error, our network team changed a registry key pointing to N drive
to M drive
and everything magically came up."
That's called a hack and hacks usually have unexpected and adverse consequences.
And in more than 15 years of working with SQL Server I've never had to use a registry change to make SQL Server work.  As a personal best practice I avoid making manual changes to the registry at all costs.

Similar Messages

Maybe you are looking for