Recently we added new drives to our 2008 R2 64 bit SQL cluster to replace old ones. The process went well and we were able to bring everything back online fairly quickly using the new drives. However, one thing that we noticed that when we try and do a manual backup using use the SQL Server Management Studio (SSMS), when it came time to select a backup destination, which in this case, would be one of the newly added drives, we get the following error:
Locate Database Files - [SQLSERVERNAME]
------------------------------
V:\BACKUPS
Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists.
If you know that the service account can access a specific file, type in the full path for the file in the File Name control in the Locate dialog box.
We did some Googling and came across this article that states that when you add drives to a SQL cluster you need to add them as a dependency which is something we did not do:
http://www.sqlcoffee.com/troubleshooting069.htm
This article describes a 2005 SQL Cluster, but we suspect that this is the cause of our issue as well. Also, please note that the SQL instance service account has full effective rights to the drives in question.
So my question is, should the new drives have been added to the cluster as a dependency or not? Could this be an explanation to the error we are seeing?