Few questions and problems.

My config:
2x HP DL380 Servers with local c: and d:
EMC SAN providing 3 disks to me (100gig, 150gig, 4gig)
4 gig is configured a the quarum drive.
4 gigs of ram

My Goal:
Active/Active configuration of SQL Server
1st node running SQL Server Ent Ed. (2 gigs assigned ram)
2nd node running SQL Server Ent Ed. (1 gig assigned ram)

Backround info:
Installation of cluster services went smooth and without error.
Failover of cluster drives and cluster IP works well through Custer
Administrator. This is the first time I have done a installation
using EMC storage. All past implementations I have done were with
compaq fiber storage arrays.

Problems:
1.) I can failover drives, however, they can only be accessed by unc
and not by drive letter?
2.) SQL Server Ent Ed. fails (displays something like: Error during
instal. Installation Failed). I am not sure if this problem is
related to 1.) ?

Any help or tips for my config would be greatly appreciated.

Thanks
Darin Seng

If the drives can only be accessed by UNCs and not the drive letters on the
node that owns the drives then there is a fundamental problem with the
cluster. I would get this resolved before even attempting to install SQL
Server on this cluster.

Rand
This posting is provided "as is" with no warranties and confers no rights.

[quoted text, click to view]

Problem resolved.

Fist off, Cluster drive failover when connected via Terminal Services
is a bit messed up. The Terminal Service Client never recieves the
PNP trigger that makes the drives appear when you move a group/disk
over.

Second issue (my bad), When doing the install I mapped a to the SQL
ENT ED cd that I had in my notebook PC. This required me to issue a
login username. All apears fine during the installation until SQL
starts to get installed on the other node(s). The other node is
unable to authenticate the mapping to the CD and thus fails.

Live and learn I guess. Anyhow it works and I am happy.

[quoted text, click to view]

Problem resolved.

Fist off, Cluster drive failover when connected via Terminal Services
is a bit messed up. The Terminal Service Client never recieves the
PNP trigger that makes the drives appear when you move a group/disk
over.

Second issue (my bad), When doing the install I mapped a to the SQL
ENT ED cd that I had in my notebook PC. This required me to issue a
login username. All apears fine during the installation until SQL
starts to get installed on the other node(s). The other node is
unable to authenticate the mapping to the CD and thus fails.

Live and learn I guess. Anyhow it works and I am happy.