??? Export/
import, whether in its original form or in the Oracle Data Pump, provides a simple and
proven method, but the time lag involved with this method typically leaves larger time
periods where data is lost in the event of a failure. Transportable tablespaces can provide
the same functionality with better performance, but are less granular. A physical
standby database typically leaves smaller data gaps or, in the case since introduction of
Oracle9i zero-data loss, no data gap; however, this solution does require the expense
of redundant hardware. More recent database releases somewhat mitigate this as the
standby database can be used for queries. Streams replication also requires redundant
hardware and ensures consistent and complete data on both the primary and backup
server, but this solution is the most resource-intensive of the three.
You should carefully balance the cost, both in extra hardware and performance, of
each of these solutions, and balance them against the potential cost of a database or
server failure.
Pages:
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634