Shulou(Shulou.com)06/01 Report--

GBase8s remote disaster recovery Cluster deployment method

Tips:

a. A GBase8s remote disaster recovery cluster can have 0 to 255 remote disaster recovery secondary nodes.

b. The secondary node can read and write, undertake part of the business, and back up each other with the primary node. When a node fails, the service on that node is transferred to other nodes.

c. The distance between nodes is relatively long, usually hundreds of kilometers apart.

d. Communication between nodes only supports asynchronous mode, not synchronous mode.

e. When the remote disaster recovery cluster fails over, the DRAUTO value is invalid, and the node cannot be automatically upgraded to the primary node. It needs to be equipped with CM, which can be converted to a standard node or other nodes.

two。

3.

1. Database parameter configuration

one

two

three

3.1

1) modify the sqlhosts file so that the master-slave sqlhost file contains the connection information of the master-slave instance, respectively.

Lord:

[root@redhat25 sec _ 54] # cat etc/sqlhosts.ol_54_ sec _ pri

Ol_54_ sec onsoctcp 192.168.152.26 30608

Ol_54_ sec _ pri onsoctcp 192.168.152.25 22363

Dr_54_ sec _ pri drsoctcp redhat25 dr_54_ sec _ pri

Lo_54_ sec _ pri onsoctcp 127.0.0.1 lo_54_ sec _ pri

Auxiliary:

[root@redhat26 sec _ 54] # cat etc/sqlhosts.ol_54_ sec

Ol_54_ sec _ pri onsoctcp 192.168.152.25 22363

Ol_54_ sec onsoctcp 192.168.152.26 30608

Dr_54_ sec drsoctcp redhat26 dr_54_ sec

Lo_54_ sec onsoctcp 127.0.0.1 lo_54_ sec

2) the parameters of the two servers for R OOT D BS pace must be the same

ROOTNAME rootdbs

ROOTPATH / home/ sec _ 54/storage/rootdbs

ROOTOFFSET 0

ROOTSIZE 1024000

3) physical / logical log configuration parameters must be the same

PHYSFILE 15000000

PLOG_OVERFLOW_PATH $GBASEDBTDIR / tmp

PHYSBUFF 512

LOGFILES 28

LOGSIZE 6144

DYNAMIC_LOGS 2

LOGBUFF 256

4) the relevant parameters of cluster nodes must be the same.

LOG_INDEX_BUILDS 1 / / enable index page logging

two。 Configure nod

1) in the online state, the node executes onmode-d add rss ol_ 54_sec.

After successful execution, check that the current status of the host is On-Line.

Use onstat-g rss to view its Local server type: Priamry, rss Server information has no auxiliary information.

2) perform level 0 full backup on the master node: ontape-s-L 0, and remotely transfer the folder under the backup path to the backup path of the remote disaster recovery node. Folder name: HOSTNAME_SERVERNUM_L0 (redhat25_125_L0)

3) under the backup path of remote disaster recovery node, modify the folder name to native hostname and instance num:

[root@redhat26 sec _ 54] # mv redhat25_125_L0 redhat26_6_L0

[root@redhat26 sec _ 54] # chown gbasedbt: gbaedbt backups/redhat26_6_L0

[root@redhat26 sec _ 54] # chmod 660 backups/redhat26_6_L0

4) disable remote disaster recovery node service: onmode-ky

5) perform ontape-p for physical recovery. At the end of the trip, the secondary node status is Fast Recovery

6) execute onmode-d rss ol_54_ sec _ pri on the remote disaster recovery node

The state of the node changes to Fast Recovery (sec), and after a moment, the state of the auxiliary machine changes to Updatable (sec).

Note: if the secondary node configuration parameter UPDATABLE_SECONDARY is 1, the child node is Updatable (sec) state; if UPDATABLE_SECONDARY is 0, the child node is READ-ONLY (sec) state

7) execute onstat-g sec on the node to check its status On-Line, and you can also see the information of the auxiliary machine in the sec Server information:

3. Testing and monitoring

1) Test:

Create the database sec with log on the host, create the table sec _ 1 and insert the data, and view it on the auxiliary machine, you can successfully view the table data.

2) Monitoring, execute onstat-g rss verbose on the main and auxiliary machines respectively, and monitor its running status

4. Qyoga

If an error occurs when the master node executes onmode-d add rss ol_ 54_sec:

Sec Servers require that Index Page Logging be active.

Indicates that index page logging needs to be activated.

Solution:

-bash-4.1$ onmode-wf LOG_INDEX_BUILDS=1 / / enable

Value of LOG_INDEX_BUILDS has been changed to 1.

In addition

-bash-4.1$ onmode-wf LOG_INDEX_BUILDS=0 / / disabled

Value of LOG_INDEX_BUILDS has been changed to 0.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.