"Hulicat" <dennis_A_white@yahoo.com> wrote in message
news:1162242129.910915.61910@e3g2000cwe.googlegroups.com...
>I have been "tapped" to install a passive node on an instance of SQL
> that is not currently configured for clustering on a W2003. Can I
> simply install clustering services on the current production instance,
> then install a new instance on what would be the passive node? Then add
> it via cluster admin?
> Can I run cluster communications, heartbeat, etc on the public NICs..I
> do not have two interfaces on each server.
> Any information would be greatly appreciated as I have only done new
> deployments and this being a prod server I do not want to try the trial
> and error approach.
>
> Thanks,
> Hulicat
>

Geoff N. Hiten wrote:
> You can use the current active node as a cluster member. You can then
> install a clustered instance of SQL and migrate the databases. The final
> step is to turn off the original instance. Possible, Yes. Recommended, NO.
>
> This entire project sounds like a low-availability solution. You are
> reusing equipment instead of purchasing a certified cluster configuration.
> The one-NIC cluster is possible but falls into the "worst practices"
> category. Not having a test platform, even a virtual one, is asking for
> even more trouble.
>
> Clustering is a hardware and systems tool to help achieve increased system
> availability. Shortcutting the hardware and the procedures will result in
> lower availability rather than higher availability.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
>
>
> "Hulicat" <dennis_A_white@yahoo.com> wrote in message
> news:1162242129.910915.61910@e3g2000cwe.googlegroups.com...
> >I have been "tapped" to install a passive node on an instance of SQL
> > that is not currently configured for clustering on a W2003. Can I
> > simply install clustering services on the current production instance,
> > then install a new instance on what would be the passive node? Then add
> > it via cluster admin?
> > Can I run cluster communications, heartbeat, etc on the public NICs..I
> > do not have two interfaces on each server.
> > Any information would be greatly appreciated as I have only done new
> > deployments and this being a prod server I do not want to try the trial
> > and error approach.
> >
> > Thanks,
> > Hulicat
> >