The lack of coherence due to OS cave not being flushed should still be a concern.
OTOH I saw a storage level replication system propagate corruption to the remote site's copy of the Production DBMS ... So it perfectly replicated the primary's failure. Oops. Easiest recovery was restoring a nightly backup to the test system since both Prod nodes were so hosed. This is bit one reason I like best-effort (asynchronous) dbms level transaction replication. The remote is 30s behind but is in a consistent state. Most users can handle checking if their last txn before crash survived; most will even if not instructed to! (Even if asked not to!)
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
