I have two full installed SQL2000 Enterprise Servers.
The first (SQL1) is the big machine, which takes the workload. The second one (SQL2) is a smaller computer which only should get a live backup of the big one.
It (SQL2) should also be capable to serve as the backup-machine --> SQL1 fails, Users can work with SQL2.
The database is about 8Gig large so snapshot-replication would produce too much traffic on the net.
Not only SQL1 should backup itself to SQL2! If SQL1 fails and users continue to work on SQL2, SQL1 should synchronize itself (when it's repaired and online) with SQL2.
Has anybody a solution for this problem?
Big thanks in advance