Advertise at FreeMegaZone

Give tremendous boost to your business by advertising at FreeMegaZone. Contact webmaster@freemegazone.com

Operate with Reversed Primary and Secondary Roles

• After restoring both packs, you can continue to operate with primary and secondary roles that are reversed from the initial state.
• For sites with symmetric configurations, there is no need to return to the original state.
• Returning to the original roles requires a planned outage and can be avoided.
• Some users intentionally operate with role reversal on a fixed schedule (such as every three months), in order to test the capabilities of the system.

Return to the Original Primary/Secondary Configuration

• Returning to the original primary/secondary configuration requires a planned outage while the primary role is moved.
• Plan it for a less busy part of your business cycle and give advance notice to users. Execute it as

# pfsctl
PFSCTL> switchover

Choose a Less Critical Application to Restore

• If there is more than one uniquely identified database on each node, then performance will be degraded after a failover, under most conditions.
• If a two-node cluster is in a primary/secondary configuration and an unrelated database is running on the secondary node, then the secondary node runs the primary services, as well as the unrelated database, after failover and may be overloaded. In this situation, move the less critical service to the other node when it is restored.
• Perform the following steps for each of the services that are moved to the restored node
• Set the oracle_service and db_name environment variables.

$ export ORACSLE_SERVICE=SALES
$ export DB_NAME=sales

• Restore the instance with secondary role

# pfsctl
PFSCTL> restore

• Move the primary role to the original primary node

PFSCTL> switchover