This is the first time I will be installing 2005 Sql Server in an
Active/Passive Cluster as a result I have a few questions.

1.The Server cluster I need to install SQL 2005 on is currently acting
a file server. It has two nodes in active/passive mode and one virtual
server. Do I need to create a new virtual server and assign it a new
new IP address in order to cluster SQL 2005 server or can I use the
current virtual server name and IP address? As a reuslt using the same
virtual server name and IP address for both file services and SQL 2005
virtual server?

2.Can I install the SQL 2005 binaries in a directory other than C?

Thanks,

Javier

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote:

If you invest in HA, it's probably a good idea to make sure that you don't
have other factors there to compromise yuor HA (such as mixing teh SQL
instance up with some other apps whose failure/failover may adversely affect
the availability of SQL Server). Use a separate network name and IP just for
SQL Server and install SQL Server in a separate resource group.

You have to put the SQL binaries on a local drive (i.e. not a drive that you
can failover between the nodes.) Some files will insist on going to C, but
you can choose whether to put the SQL binaries.

Linchi

"Javier" wrote: