Backup Strategy

Hello

We are looking to implement a backup strategy for our client. There are 2
servers (1 for the site and 1 for the SQL Server 2000 database)

The live site is build in asp.net 1.1 (c#) and uses Commerce Server 2002
(Developer Edition).

Our backup plan involves replicating the live setup on 2 other servers. In
the event of a problem with the current live servers we could then switch the
site to point to our backup servers.

We would like to know the best approach to taking a copy of the live site
and setting it up on another server. Obviously with Commerce Server it is not
as simple as copying the site files to the backup server.

What is the best approach to generating a pup file on the live server to set
up the site on the backup server?

We would like the backup site to point to the current live database but, if
required, be able change the database connection strings to point to the
database backup server. So in the event of both live servers failing, we
could run the site off our backup servers.

We had previously attempted to set up a backup on our test server. This was
done using a previously generated pup file. There were a number of connection
strings that were changed to point to a local database. When we removed this
backup site from our test server, some tables in the live database were also
removed, so obviously we missed some existing database connection strings.

Any advice would be greatly appreciated.