July 13, 2009 at 6:47 pm
The common scenarios as follow
In the windows cluster environment, generally C and D drives will be local where SQL dictionaries will be copied while installation. The system and user databases will be pointed to Shared Network Drives (common for both cluster nodes).
Eg.
Node1: C$, D$
Node2: C$, D$
Shared NetworkDrives: E$ F$ (accessible by both Node1 and Node2)
In your case if C$ drive is accessible by both Node1 and Node2 then you can install your SQL else you've to configure your drives according to Windows Cluster environment.
Hope this helps.
Thanks
Jay
http://www.sqldbops.com
July 14, 2009 at 7:25 am
We have only one local drive i.e C drive and the rest are shared drives. So if we have any other local drive other than C drive, we can select that drive to install sql server. Correct me if I understood wrong..
I've been able to configure SQL Server install to the D drive, however there were some files that were located on the C drive. This may have to do with the fact that you have only C drive attached to the the servers.
July 14, 2009 at 8:51 am
rambilla4 (7/13/2009)
We have only one local drive i.e C drive and the rest are shared drives. So if we have any other local drive other than C drive, we can select that drive to install sql server. Correct me if I understood wrong..
...and I believe that is the problem. You can only install the binaries on LOCAL drives, not shared network drives....... AND the same drive (letter) needs to be available on all clustered nodes, as Jayakumar pointed out above. So if the LOCAL D: drive is available on all nodes, then you can use it.
As written here:
Program files and data files cannot be installed on a removable disk drive, cannot be installed on a file system that uses compression, and cannot be installed on shared drives on a failover cluster instance.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply