We have a cluster setup using 5 servers and 3 environments
(PRD, QAT and DEV): PRD1, PRD2, QAT1, QAT2, DEV1. All
servers are running Windows 2003. We are connecting all
of these nodes to a NAS (Network Attached Storage) drive
system (Microsoft Certified). We currently have 260 GB of
available space and we want to carve out partitions for
the servers. Our backup solution requires that we have
separate drives for the data and log files, so is this
configuration correct, or is it not recommended to
separate the data and log files for clustering on Windows
2003?

PRD1 DATA-40GB[G:] LOG-20GB[L:]
PRD2 DATA-40GB[H:] LOG-20GB[M:]
QAT1 DATA-25GB[I:] LOG-20GB[N:]
QAT2 DATA-25GB[J:] LOG-20GB[O:]
DEV1 DATA-25GB[K:] LOG-20GB[P:]

Please let us know if you have alternate suggestions.
Thank you.

Separete Log file from Data File is always recommended in
all cases, clustered systems and non-clustered systems.

Cesar Kubo

That is the best way - separate log and data drives,
however, you have what appears to be an unsupported
hardware config. NAS is not supported for SQL Server
failover clustering as noted in:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;304261
"Note that SQL Server only provides support for network-
based files that use trace flag 1807 for non-failover
clustered installations of SQL Server. Failover clustered
installations of SQL Server do not work with network-based
files because SQL Server 2000 requires that storage
devices be recognized and registered by the Microsoft
Cluster Service (MSCS) Cluster Administrator. "

The entire cluster solution must be in the Windows Catalog
as such.