Was it Einstein who once said "Things should be as complex as they need to be, but no more ..."?
Dbvisit - The ultimate Oracle Standby Database solution
The best alternative to Oracle Data Guard
Dbvisit automatic Graceful Switchover
Graceful switchover (also referred to as role reversal or seamless switchover) can be used to switch back to original configuration
as it was before the disaster. This is a seamless operation done in a matter of minutes* with no dataloss.
Graceful switchover is also be used for planned outages (or scheduled maintenance)
to perform an upgrade on the primary site while keeping the system available for all users.
This is done by reversing the roles between the primary and standby database and switching the database users over to the standby site during the outage. It may also be used to test the Disaster Recovery (DR) scenario.
Dbvisit graceful switchover can now be used with RAC and ASM!
Version 5.2.16 or higher is required.
During a switchover, the primary database transitions to a standby role, and the standby database transitions to a primary role. There is no data loss during the transition and the standby database does not have to be rebuilt. Dbvisit Graceful switchover has been tested with Oracle 8i, 9i, 10g and 11g.
|
How the Dbvisit Graceful switchover process works after a disaster to switch back to the original (pre-disaster) configuration:
- The standby database has been activated to become the new primary database during the disaster.
- Users are using the new primary database on standby server which has become the main database.
- Standby database is rebuild on the original primary server (Users are not affected).
- Dbvisit Graceful switchover is initiated with a simple command on both servers.
- Users are temporarily disconnected from the primary database on the standby server.
- Primary database on standby server is temporarily shutdown during transition.
- Standby database on the original primary server is temporarily shutdown during transition.
- Standby database transitions to primary database on the original primary server in matter of minutes* in a seamless operation.
- Primary database transitions to standby database on standby server in matter of minutes* in a seamless operation.
- Users can re-connect after a few minutes to new primary database on the original primary server and continue working, with no data loss.
- Original configuration is restored (pre-disaster) in matter of minutes* with simple command!
- Dbvisit automatically keeps the original standby database on the standby server up to date. No configurational change required!
How the Dbvisit Graceful switchover process works for planned outages:
- Dbvisit Graceful switchover is initiated with a simple command on both servers.
- Users are temporarily disconnected from the main primary database.
- Main primary database is temporarily shutdown during transition.
- Standby database is temporarily shutdown during transition.
- Main primary database transitions to standby database on primary server in matter of minutes* in a seamless operation.
- Standby database transitions to primary database on standby server in matter of minutes* in a seamless operation.
- Users can re-connect to new primary database on standby server and continue working, with no data loss.
- Maintenance can proceed on primary server.
- Optionally Dbvisit can keep the standby database on the primary server up to date during the scheduled maintenance outage.
- At the end of the scheduled maintenance the databases are transitioned back to their original state in matter of minutes*.
Difference between Graceful switchover and Failover:
Graceful switchover is not used during a disaster where the primary database is no longer available.
The process that occurs during a disaster is called failover. During the failover the standby database is activated to become the primary database.
Activating the standby database so that it can take over instantly is done through a simple Dbvisit command:
dbv_oraStartStop activate database
Graceful switchover cannot be used together with Oracle RAC or where the redo logs or the archive logs are in Oracle ASM file system.
Note: This does not apply to Failover. Failover works with Oracle RAC and ASM.
*Depending on speed of network, the size of the redo logs and distance between primary and standby server.
Dbvisit is a registered trademark of Avisit Solutions Limited
Oracle is a registered trademark of Oracle Corporation
