Oracle Database Hot Standby Solution

The Oracle Database Hot Standby solution monitors the database in real time, backs up the changed data in the database to the standby database in seconds, and backs up only the successful transactions of the primary database.

The Oracle Database Hot Standby solution monitors the database in real time, backs up the changed data in the database to the standby database in seconds, and backs up only the successful transactions of the primary database.

Related indicators

1. Database Hot Backup in seconds and transactions (cross-operating system platform supported)

Monitors the database in real time and backs up the changed data to the standby database in seconds. At the same time, only the successful transactions of the primary database are backed up.

2. the standby database is online and can be operated

During synchronization, the Standby database is in the online read/write status. During the backup, you can connect to the standby database to query and analyze data.

3. Support resumable Data Transfer

When a network connection failure occurs during Database Synchronization and replication, the synchronization program automatically records the status when the network is disconnected. After the network is reconnected, the synchronization program continues to transmit data. Data backed up will not be lost due to network and other communication faults. This ensures reliable hot data backup in unreliable networks.

4. actiontrail records all data operation logs of the master database

A powerful Operation Audit function must be provided during synchronization to record all the data operation logs backed up from the primary database to the standby database in detail.

5. Integrated backup database creation tool

It not only supports Backup recovery, import and export, and third-party backup software for backup database initialization, but also provides powerful database migration tools to create backup databases, you can ensure that the database is not stopped during the creation of the slave database.

6. flexible and simple backup Management

The hot standby system must be simple to start. During database backup, Hot Standby can be suspended, you can quickly stop hot standby tasks without affecting the normal operation of production databases.

7. Program robustness and strong error handling capability

At any time, the synchronization program must be able to directly stop or shut down the test. It cannot put a lot of pressure on the administrator, and Initialization is not required at will, you Cannot initialize the entire database because of data problems in a table.

Procedure

First, install and prepare the database, disable all the foreign keys and triggers of the slave database, and perform Physical partitioning and table creation in the slave database.

1. Install the LINUX operating system, the Oracle database client, and the PAC synchronization software.

2. Configure the PAC synchronization software, which contains files such as tnsnames. ora and config. xml.

3. Start the non-stop initialization process and start importing initialization data

4. Start the database synchronization software PAC, check whether the management process, data extraction process, and data analysis process are normal, and pause the loading process.

5. Start the loading process after initialization.

6. Start the monitoring client, check the Process Synchronization status, and perform a query test after data synchronization.

7. Regularly check processes and synchronize log files

Advantages of hot disaster recovery Solutions

Unlike traditional hot standby systems, Hot Standby maintains data consistency between the backup database and the master database through data synchronization. Backup databases can be set in different buildings, different cities, or even disaster recovery sites thousands of kilometers away. When the primary database becomes unavailable due to planned or unexpected interruptions, you can switch the standby database to the production role to ensure the normal operation of the system.

The synchronization software synchronizes data between two databases in seconds to ensure real-time consistency between the two databases. If the primary production database fails, the backup database server can be enabled as the primary database server at any time. Media restoration is no longer required.

1. Dual-node storage Redundancy System

The Hot Standby solution requires a dual-copy database, which not only crashes the production database, but also crashes the disk hardware, resulting in database unavailability. dual-copy data sources are the real Redundancy System, which eliminates the worry of database system administrators for storing spof!

2. There is no physical media recovery time problem

Because dual-Database Synchronization in seconds ensures the consistency of the dual-database, if the master production database fails, the backup database server can be enabled as the master database server at any time. media recovery time does not exist. compared with Hot Standby, this completely eliminates the backup and recovery process.

3. Synchronization time can reach the second level

There is no transaction mechanism for data synchronization in the traditional Mirror or volume replication mode. Its replication is performed on the file and disk layers. Therefore, the data may be incomplete, which poses a great risk to users. The synchronization program can synchronize data between the primary database and the standby database in seconds and transactions, eliminating the number of backup loss at intervals in the backup software.

4. solved the problem of database load balancing or database isolation

The backup database can be used in Read mode for REPORT query, internal and external database isolation, and data warehouse. Standby database tables use the redo data received from the primary database for updates and can be used for other tasks such as backup operations, reports, totals, and queries, this reduces the primary database workload required to execute these tasks and saves valuable CPU and I/O cycles. The standby database can be enabled when updating a table from the primary database, and read/write access to the table at the same time. You can even create additional indexes and materialized views on maintained tables to achieve better query performance and adapt to specific business requirements.

5. Database Remote Disaster Recovery

Supports remote data synchronization, resumable data transfer, and data consistency check. This allows you to smoothly process network connection issues that temporarily disconnect the backup database from the primary database. When the standby database becomes unavailable, local transactions are captured in the primary database. When you re-establish a connection with the standby database, the accumulated logs are automatically transmitted and applied to the standby database until the standby database has been re-synchronized with the primary database.

For more information about Oracle, see the Oracle topic page? Tid = 12