First, you need to share the disks--that your database files will
reside--among the two servers. This can be done either through a common SCSI
bus or a SAN. Not many people use a shared SCSI bus in a cluster these days.

If you make your thee disks into one RAID5 set, you basically have one disk
as far as clustering is concerned. Ideally, you should have at least another
RAID-protected disk for your quorum.

Yes, you can cluster the two servers, install SQL Server, and migrate your
databases to the new clustered SQL instance. Ideally, you should start to
cluster two servers with them in a clean state rather than from their current
state.

You don't need to copy the databases to the second server. You should save
your databases just as when you need to rebuild these servers.

Many people have bad experience with clustering because they don't follow
the documentation and don't devote enough time to gain sufficient experience
in a test environment first. Then, they complain that failover clustering
itself seems to be causing more down time that it is supposed to prevent. I'd
strongly suggest that you allocate sufficient time to planning, learning, and
testing. Don't start with the prod right away.

Linchi

"Armando" wrote: