Using mirroring to effect data replication

My site has a critical system running on OnLine 5.07. Each night a level 0 archive is taken and archived to a contingency server in a remote location. Furthermore, every two hours a level 1 is taken and ftp'd to the contingency server (this could also be achieved by forcing a log back-up and ftp'ing the resultant back-up file to the contingency server). Thus, in the event of a disaster afflicting the primary site, the database can be recovered at the contingency site to its state at a point between 0-2 hours ago (leave aside the fact that the disaster may have killed or maimed those capable of doing the restore!). The users wish to upgrade this to "point of failure" disaster recovery. Either remote-site hardware mirroring, or Online v7 data replication, would address this requirement but these are a few months off. The following has been suggested as an interim solution. I hate it, but can't actually come up with a concrete reason why it shouldn't work: Mirror the log dbspace of the primary server on a disk at physically adjacent and connected to the contingency server. In the event of disastrous loss of the primary site, the database server can be recovered at the contingency site (using an ftd'd archive). Before this restore is effected the mirrored logs would have to be backed up. Once the restore is complete, apply the backed-up, mirrored, logs to give "point-of-failure" recovery. Aside from the probable performance degradation of remotely mirroring the log dbspace, can anyone think of a show-stopping reason against this? Thanks Neil Truby Chase Manhattan Bank Bournemouth, UK neil.truby@chase.com