Was it Einstein who once said "Things should be as complex as they need to be, but no more ..."?
Dbvisit - Oracle Disaster Recovery for RAC
The best alternative to Oracle Data Guard
Dbvisit can be used together with Oracle RAC (Real Application Cluster) and Oracle Standard Edition (SE) to manage your standby databases.
Dbvisit graceful switchover can now be used with RAC and ASM!
Version 5.2.16 or higher is required.
RAC allows multiple instances on different nodes to access a shared database on a cluster (or grid) system. RAC allows scalability and provides high availability. Oracle RAC together with Dbvisit standby databases provides high availability and disaster recovery.
Dbvisit supports archive logs in Oracle ASM file system.
Dbvisit setup with RAC is very easy and is similar to single instance database setup. RAC database does not have to be restarted or any Oracle parameters changed.
Dbvisit RAC Takeover
If a RAC node fails and is unavailable, then Dbvisit on another RAC node can take over the log shipment from the failed node automatically.
Standby node setup with RAC
The Oracle standby database can configured as a single instance database or as a RAC database with several instances on different standby nodes.
1) RAC primary and RAC standby database.
|
- All primary nodes need to send the archive logs to a shared location on the RAC standby cluster.
- Dbvisit only needs to be scheduled on one standby instance to apply the archives from all threads to the standby database.
2) RAC primary and single instance Oracle standby database.
|
- All primary nodes need to send the archive logs to the single standby node.
- Dbvisit will apply the archives from all threads to the single instance standby database.
Dbvisit is a registered trademark of Avisit Solutions Limited
Oracle is a registered trademark of Oracle Corporation
