Can database server's transaction-log-based replication help?
MSSQLServer had this since 1995, and I expect Oracle has this too for
a long.

How aggressively is your data updated?

I would prefer the database-server-based solution, not the
RAID-box-based. It will preserve the transaction boundaries at least.

An array based Snapshot integrated with the host OS & applications will
also
accomplish this, i.e. quiesce the DB, flush any uncommited writes and
issue
the snapshot. A good example of this approach would be W2K03 and SQLServer
along with a VSS aware storage array.

Be aware that the snapshot function will still put load on your original
LUNs. The Snaphot is just a bunch of pointers to the original data blocks.
As a result, reading from a snapshot will have cache and performance
implications on your production environment.

Also be aware there are some serious bugs in Power Path 3.0.5 on Win2K3.

--T




----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! 100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---