I just built a SQL 2005 Cluster (2 node, active/passive). The configuration of the cluster went smoothly, and during that process I configured a Cluster Group for SQL with two drives: Drive U: (for databases) and drive V: (for logs). Both drives are located on an iSCSI SAN. Everything failed over from one node to the other consistently during extensive testing, including the drives. In addition, each physcial node saw the drives and could access them each time they were the active node. I then installed SQL 2005 software with the cluster option and that went without a hitch.
Once everything was up, the next thing that I wanted to do was to change the default locations of the databases and logs. The databases were already defaulted to drive U:, which was fine. However, when I went to change the default location of the logs to drive V: through the SQL Server Management Studio, the only drive it could see was drive U: and not the other drive. As a result, all of the databases and logs are still on the same drive.
Does anyone have any idea why the SQL Server cannot see the drive, even though the node and the cluster see it just fine?
Thanks
Start Free Trial