同机搭建DM8主备集群

  1. 架构

主 5236  DW_PORT 6236 MAL_INST_PORT

实例名

PORT_NUM

MAL_INST_DW_PORT

MAL_HOST

MAL_PORT

MAL_DW_PROT

DAMENG

5236

6236

127.0.0.1

7236

8236

DAMENGS

5237

6237

127.0.0.1

7237

8237

  1. 主库配置

1. dm.ini

INSTANCE_NAME = DAMENG

PORT_NUM = 5236 #数据库实例监听端口

DW_INACTIVE_INTERVAL = 60 #接收守护进程消息超时时间

ALTER_MODE_STATUS = 0 #不允许手工方式修改实例模式/状态/OGUID

ENABLE_OFFLINE_TS = 2 #不允许备库 OFFLINE 表空间

MAL_INI = 1 #打开 MAL 系统

ARCH_INI = 1 #打开归档配置

RLOG_SEND_APPLY_MON = 64 #统计最近 64 次的日志发送信息

  1. dmmal.in

MAL_CHECK_INTERVAL = 5 #MAL 链路检测时间间隔

MAL_CONN_FAIL_INTERVAL = 5 #判定 MAL 链路断开的时间

[MAL_INST1]

MAL_INST_NAME = DAMENG #实例名,和 dm.ini 中的 INSTANCE_NAME 一致

MAL_HOST = 127.0.0.1 #MAL 系统监听 TCP 连接的 IP 地址

MAL_PORT = 7236 #MAL 系统监听 TCP 连接的端口

MAL_INST_HOST = 127.0.0.1 #实例的对外服务 IP 地址

MAL_INST_PORT = 5236 #实例的对外服务端口,和 dm.ini 中的 PORT_NUM 一致

MAL_DW_PORT = 8236 #实例本地的守护进程监听 TCP 连接的端口

MAL_INST_DW_PORT = 6236 #实例监听守护进程 TCP 连接的端口

[MAL_INST2]

MAL_INST_NAME = DAMENGS

MAL_HOST = 127.0.0.1

MAL_PORT = 7237

MAL_INST_HOST = 127.0.0.1

MAL_INST_PORT = 5237

MAL_DW_PORT = 8237

MAL_INST_DW_PORT = 6237

  1. dm_arch.ini

[ARCHIVE_REALTIME]

ARCH_TYPE = REALTIME #实时归档类型

ARCH_DEST = DAMENGS #实时归档目标实例名

[ARCHIVE_LOCAL1]

ARCH_TYPE = LOCAL #本地归档类型

ARCH_DEST = /home/dmdba/dmdbms/data/DAMENG/arch #本地归档文件存放路径

ARCH_FILE_SIZE = 128 #单位 Mb,本地单个归档文件最大值

ARCH_SPACE_LIMIT = 0 #单位 Mb,0 表示无限制,范围 1024~2147483647M

  1. Dmwatch.ini

[GRP1]

DW_TYPE = GLOBAL #全局守护类型

DW_MODE = AUTO #自动切换模式

DW_ERROR_TIME = 10 #远程守护进程故障认定时间

INST_RECOVER_TIME = 60 #主库守护进程启动恢复的间隔时间

INST_ERROR_TIME = 10 #本地实例故障认定时间

INST_OGUID = 453331 #守护系统唯一 OGUID 值

INST_INI = /home/dmdba/dmdbms/data/DAMENG/dm.ini #dm.ini 配置文件路径

INST_AUTO_RESTART = 1 #打开实例的自动启动功能

INST_STARTUP_CMD = /dm/bin/dmserver #命令行方式启动

RLOG_SEND_THRESHOLD = 0 #指定主库发送日志到备库的时间阈值,默认关闭

RLOG_APPLY_THRESHOLD = 0 #指定备库重演日志的时间阈值,默认关闭

  1. 恢复备库
    1. 脱机备份、脱机还原方式

1.备份主库

dmrman CTLSTMT="BACKUP DATABASE '/home/dmdba/dmdbms/data/DAMENG/dm.ini' FULL TO BACKUP_FILE1 BACKUPSET '/home/dmdba/dmdbms/data/DAMENG/BACKUP_FILE_01'"

  1. 新建备库目录/home/dmdba/dmdbms/data/DAMENGS,复制主库的dm.ini并修改,主要是修改instance_name、port_num、ALTER_MODE_STATUS,要保证arch_ini=1,mal_init=1
  2. 复制主库的dm.ctl到备库目录,转化为文本格式后,对相应目录进行修改,再转化到控制文件格式

dmctlcvt c2t dm.ctl dm.ctl.txt

dmctlcvt t2c dm.ctl.txt dm.ctl

  1. 还原备库

dmrman CTLSTMT="RESTORE DATABASE '/home/dmdba/dmdbms/data/DAMENGS/dm.ini' FROM BACKUPSET '/home/dmdba/dmdbms/data/DAMENG/BACKUP_FILE_01'"

  1. 恢复备库

dmrman CTLSTMT="RECOVER DATABASE '/home/dmdba/dmdbms/data/DAMENGS/dm.ini' UPDATE DB_MAGIC"

    1. 联机备份、脱机还原方式

1.备份主库

SQL> BACKUP DATABASE BACKUPSET '/home/dmdba/dmdbms/data/DAMENG/BACKUP_FILE_01'"

2.新建备库目录/home/dmdba/dmdbms/data/DAMENGS,复制主库的dm.ini并修改,主要是修改instance_name、port_num、ALTER_MODE_STATUS,要保证arch_ini=1,mal_init=1

3.复制主库的dm.ctl到备库目录,转化为文本格式后,对相应目录进行修改,再转化到控制文件格式

dmctlcvt c2t dm.ctl dm.ctl.txt

dmctlcvt t2c dm.ctl.txt dm.ctl

4.还原备库

dmrman CTLSTMT="RESTORE DATABASE '/home/dmdba/dmdbms/data/DAMENGS/dm.ini' FROM BACKUPSET '/home/dmdba/dmdbms/data/DAMENG/BACKUP_FILE_01'"

5.恢复备库

dmrman CTLSTMT="RECOVER DATABASE '/home/dmdba/dmdbms/data/DAMENGS/dm.ini' UPDATE DB_MAGIC"

  1. 启动主库

以 Mount 方式启动主库

dmserver /home/dmdba/dmdbms/data/DAMENG/dm.ini mount

设置OGUID

SQL>SP_SET_PARA_VALUE(1, 'ALTER_MODE_STATUS', 1);

SQL>sp_set_oguid(453331);

SQL>SP_SET_PARA_VALUE(1, 'ALTER_MODE_STATUS', 0);

修改模式

SQL>alter database primary;

  1. 备库配置

1. dm.ini

INSTANCE_NAME = DAMENGS

PORT_NUM = 5237 #数据库实例监听端口

DW_INACTIVE_INTERVAL = 60 #接收守护进程消息超时时间

ALTER_MODE_STATUS = 0 #不允许手工方式修改实例模式/状态/OGUID

ENABLE_OFFLINE_TS = 2 #不允许备库 OFFLINE 表空间

MAL_INI = 1 #打开 MAL 系统

ARCH_INI = 1 #打开归档配置

RLOG_SEND_APPLY_MON = 64 #统计最近 64 次的日志发送信息

2. dmmal.in

MAL_CHECK_INTERVAL = 5 #MAL 链路检测时间间隔

MAL_CONN_FAIL_INTERVAL = 5 #判定 MAL 链路断开的时间

[MAL_INST1]

MAL_INST_NAME = DAMENG #实例名,和 dm.ini 中的 INSTANCE_NAME 一致

MAL_HOST = 127.0.0.1 #MAL 系统监听 TCP 连接的 IP 地址

MAL_PORT = 7236 #MAL 系统监听 TCP 连接的端口

MAL_INST_HOST = 127.0.0.1 #实例的对外服务 IP 地址

MAL_INST_PORT = 5236 #实例的对外服务端口,和 dm.ini 中的 PORT_NUM 一致

MAL_DW_PORT = 8236 #实例本地的守护进程监听 TCP 连接的端口

MAL_INST_DW_PORT = 6236 #实例监听守护进程 TCP 连接的端口

[MAL_INST2]

MAL_INST_NAME = DAMENGS

MAL_HOST = 127.0.0.1

MAL_PORT = 7237

MAL_INST_HOST = 127.0.0.1

MAL_INST_PORT = 5237

MAL_DW_PORT = 8237

MAL_INST_DW_PORT = 6237

3. dm_arch.ini

[ARCHIVE_REALTIME]

ARCH_TYPE = REALTIME #实时归档类型

ARCH_DEST = DAMENG #实时归档目标实例名

[ARCHIVE_LOCAL1]

ARCH_TYPE = LOCAL #本地归档类型

ARCH_DEST = /home/dmdba/dmdbms/data/DAMENGS/arch #本地归档文件存放路径

ARCH_FILE_SIZE = 128 #单位 Mb,本地单个归档文件最大值

ARCH_SPACE_LIMIT = 0 #单位 Mb,0 表示无限制,范围 1024~2147483647M

4. Dmwatch.ini

[GRP1]

DW_TYPE = GLOBAL #全局守护类型

DW_MODE = AUTO #自动切换模式

DW_ERROR_TIME = 10 #远程守护进程故障认定时间

INST_RECOVER_TIME = 60 #主库守护进程启动恢复的间隔时间

INST_ERROR_TIME = 10 #本地实例故障认定时间

INST_OGUID = 453331 #守护系统唯一 OGUID 值

INST_INI = /home/dmdba/dmdbms/data/DAMENGS/dm.ini #dm.ini 配置文件路径

INST_AUTO_RESTART = 1 #打开实例的自动启动功能

INST_STARTUP_CMD = /dm/bin/dmserver #命令行方式启动

--RLOG_SEND_THRESHOLD = 0 #指定主库发送日志到备库的时间阈值,默认关闭

RLOG_APPLY_THRESHOLD = 0 #指定备库重演日志的时间阈值,默认关闭

  1. 启动备库

以 Mount 方式启动备库

dmserver /home/dmdba/dmdbms/data/DAMENGS/dm.ini mount

设置OGUID

SQL>SP_SET_PARA_VALUE(1, 'ALTER_MODE_STATUS', 1);

SQL>sp_set_oguid(453331);

SQL>SP_SET_PARA_VALUE(1, 'ALTER_MODE_STATUS', 0);

修改模式

SQL>alter database standby;

注:

如果当前数据库不是 Normal 模式,需要先修改 dm.ini 中 ALTER_MODE_STATUS 值 为 1,允许修改数据库模式,修改 Standby 模式成功后再改回为 0

SQL>SP_SET_PARA_VALUE(1, 'ALTER_MODE_STATUS', 1); ----第 1 步

SQL>alter database standby; ----第 2 步

SQL>SP_SET_PARA_VALUE(1, 'ALTER_MODE_STATUS', 0); ----第 3 步

  1. 配置监视器

/home/dmdba/dmdbms/data/dmmonitor.ini

MON_DW_CONFIRM = 1 #确认监视器模式

MON_LOG_PATH = /home/dmdba/dmdbms/data/log #监视器日志文件存放路径

MON_LOG_INTERVAL = 60 #每隔 60s 定时记录系统信息到日志文件

MON_LOG_FILE_SIZE = 32 #每个日志文件最大 32M

MON_LOG_SPACE_LIMIT = 0 #不限定日志文件总占用空间

[GRP1]

MON_INST_OGUID = 453331 #组 GRP1 的唯一 OGUID 值 #以下配置为监视器到组 GRP1 的守护进程的连接信息,以―IP:PORT‖的形式配置

#IP 对应 dmmal.ini 中的 MAL_HOST,PORT 对应 dmmal.ini 中的 MAL_DW_PORT

MON_DW_IP = 127.0.0.1:8236

MON_DW_IP = 127.0.0.1:8237

  1. 启动守护进程

守护进程启动前,各实例处于 Mount 状态。

启动各个主备库上的守护进程:

dmwatcher /home/dmdba/dmdbms/data/DAMENG/dmwatcher.ini

dmwatcher /home/dmdba/dmdbms/data/DAMENGS/dmwatcher.ini

守护进程启动后,进入 Startup 状态,此时实例都处于 Mount 状态。守护进程开始 广播自身和其监控实例的状态信息,结合自身信息和远程守护进程的广播信息,守护进程将本地实例 Open,并切换为 Open 状态。

 

  1. 启动监视器

启动监视器:

dmmonitor /home/dmdba/dmdbms/data/dmmonitor.ini

 

 

  1. 手动切换

Login

username:sysdba

password:

[monitor]         2022-03-02 16:24:18: Login dmmonitor success!

switchover

[monitor]         2022-03-02 16:24:26: Start to switchover instance DAMENGS

[monitor]         2022-03-02 16:24:26: Notify dmwatcher(DAMENG) switch to SWITCHOVER status

[monitor]         2022-03-02 16:24:26: Dmwatcher process DAMENG status switching [OPEN-->SWITCHOVER]

[monitor]         2022-03-02 16:24:27: Switch dmwatcher DAMENG to SWITCHOVER status success

[monitor]         2022-03-02 16:24:27: Notify dmwatcher(DAMENGS) switch to SWITCHOVER status

[monitor]         2022-03-02 16:24:27: Dmwatcher process DAMENGS status switching [OPEN-->SWITCHOVER]

[monitor]         2022-03-02 16:24:28: Switch dmwatcher DAMENGS to SWITCHOVER status success

[monitor]         2022-03-02 16:24:28: Instance DAMENG start to execute sql SP_SET_GLOBAL_DW_STATUS(0, 6)

[monitor]         2022-03-02 16:24:28: Instance DAMENG execute sql SP_SET_GLOBAL_DW_STATUS(0, 6) success

[monitor]         2022-03-02 16:24:28: Instance DAMENGS start to execute sql SP_SET_GLOBAL_DW_STATUS(0, 6)

[monitor]         2022-03-02 16:24:28: Instance DAMENGS execute sql SP_SET_GLOBAL_DW_STATUS(0, 6) success

[monitor]         2022-03-02 16:24:28: Instance DAMENG start to execute sql ALTER DATABASE MOUNT

[monitor]         2022-03-02 16:24:28: Instance DAMENG execute sql ALTER DATABASE MOUNT success

[monitor]         2022-03-02 16:24:28: Instance DAMENGS start to execute sql SP_APPLY_KEEP_PKG()

[monitor]         2022-03-02 16:24:28: Instance DAMENGS execute sql SP_APPLY_KEEP_PKG() success

[monitor]         2022-03-02 16:24:28: Instance DAMENGS start to execute sql ALTER DATABASE MOUNT

[monitor]         2022-03-02 16:24:28: Instance DAMENGS execute sql ALTER DATABASE MOUNT success

[monitor]         2022-03-02 16:24:28: Instance DAMENG start to execute sql ALTER DATABASE STANDBY

[monitor]         2022-03-02 16:24:29: Instance DAMENG execute sql ALTER DATABASE STANDBY success

[monitor]         2022-03-02 16:24:29: Instance DAMENGS start to execute sql ALTER DATABASE PRIMARY

[monitor]         2022-03-02 16:24:30: Instance DAMENGS execute sql ALTER DATABASE PRIMARY success

[monitor]         2022-03-02 16:24:30: Notify instance DAMENGS to change all arch status to be invalid

[monitor]         2022-03-02 16:24:31: Succeed to change all instances arch status to be invalid

[monitor]         2022-03-02 16:24:31: Instance DAMENG start to execute sql ALTER DATABASE OPEN FORCE

[monitor]         2022-03-02 16:24:31: Instance DAMENG execute sql ALTER DATABASE OPEN FORCE success

[monitor]         2022-03-02 16:24:31: Instance DAMENGS start to execute sql ALTER DATABASE OPEN FORCE

[monitor]         2022-03-02 16:24:32: Instance DAMENGS execute sql ALTER DATABASE OPEN FORCE success

[monitor]         2022-03-02 16:24:32: Instance DAMENG start to execute sql SP_SET_GLOBAL_DW_STATUS(6, 0)

[monitor]         2022-03-02 16:24:33: Instance DAMENG execute sql SP_SET_GLOBAL_DW_STATUS(6, 0) success

[monitor]         2022-03-02 16:24:33: Instance DAMENGS start to execute sql SP_SET_GLOBAL_DW_STATUS(6, 0)

[monitor]         2022-03-02 16:24:33: Instance DAMENGS execute sql SP_SET_GLOBAL_DW_STATUS(6, 0) success

[monitor]         2022-03-02 16:24:33: Notify dmwatcher(DAMENG) switch to OPEN status

[monitor]         2022-03-02 16:24:33: Dmwatcher process DAMENG status switching [SWITCHOVER-->OPEN]

[monitor]         2022-03-02 16:24:33: Switch dmwatcher DAMENG to OPEN status success

[monitor]         2022-03-02 16:24:33: Notify dmwatcher(DAMENGS) switch to OPEN status

[monitor]         2022-03-02 16:24:33: Dmwatcher process DAMENGS status switching [SWITCHOVER-->OPEN]

[monitor]         2022-03-02 16:24:34: Switch dmwatcher DAMENGS to OPEN status success

[monitor]         2022-03-02 16:24:34: Notify group(GRP1)'s dmwatcher to do clear

[monitor]         2022-03-02 16:24:35: Clean request of dmwatcher processer DAMENG success

2022-03-02 16:24:35

#================================================================================#

GROUP            OGUID       MON_CONFIRM     MODE            MPP_FLAG

GRP1             453331      TRUE            AUTO            FALSE

<<DATABASE GLOBAL INFO:>>

DW_IP               MAL_DW_PORT  WTIME                WTYPE     WCTLSTAT  WSTATUS        INAME            INST_OK   N_EP  N_OK  ISTATUS     IMODE     DSC_STATUS     RTYPE     RSTAT

127.0.0.1           8237         2022-03-02 16:24:35  GLOBAL    VALID     OPEN           DAMENGS          OK        1     1     OPEN        PRIMARY   DSC_OPEN       REALTIME  VALID

EP INFO:

INST_IP             INST_PORT  INST_OK   INAME            ISTATUS     IMODE     DSC_SEQNO  DSC_CTL_NODE RTYPE     RSTAT    FSEQ            FLSN            CSEQ            CLSN            DW_STAT_FLAG

127.0.0.1           5237       OK        DAMENGS          OPEN        PRIMARY   0          0            REALTIME  VALID    4313            33536           4313            33536           NONE

<<DATABASE GLOBAL INFO:>>

DW_IP               MAL_DW_PORT  WTIME                WTYPE     WCTLSTAT  WSTATUS        INAME            INST_OK   N_EP  N_OK  ISTATUS     IMODE     DSC_STATUS     RTYPE     RSTAT

127.0.0.1           8236         2022-03-02 16:24:35  GLOBAL    VALID     OPEN           DAMENG           OK        1     1     OPEN        STANDBY   DSC_OPEN       REALTIME  INVALID

EP INFO:

INST_IP             INST_PORT  INST_OK   INAME            ISTATUS     IMODE     DSC_SEQNO  DSC_CTL_NODE RTYPE     RSTAT    FSEQ            FLSN            CSEQ            CLSN            DW_STAT_FLAG

127.0.0.1           5236       OK        DAMENG           OPEN        STANDBY   0          0            REALTIME  INVALID  4311            32178           4311            32178           NONE

DATABASE(DAMENG) APPLY INFO FROM (DAMENGS), REDOS_PARALLEL_NUM (1):

DSC_SEQNO[0], (RSEQ, SSEQ, KSEQ)[4311, 4311, 4311], (RLSN, SLSN, KLSN)[32178, 32178, 32178], N_TSK[0], TSK_MEM_USE[0]

REDO_LSN_ARR: (32178)

#================================================================================#

[monitor]         2022-03-02 16:24:35: Clean request of dmwatcher processer DAMENGS success

[monitor]         2022-03-02 16:24:35: Switchover instance DAMENGS success

[monitor]         2022-03-02 16:24:36: Dmwatcher process DAMENGS status switching [OPEN-->RECOVERY]

                  WTIME                WSTATUS        INST_OK   INAME            ISTATUS     IMODE     RSTAT    N_OPEN   FLSN            CLSN

                  2022-03-02 16:24:36  RECOVERY       OK        DAMENGS          OPEN        PRIMARY   VALID    7        33536           33536

[monitor]         2022-03-02 16:24:38: Dmwatcher process DAMENGS status switching [RECOVERY-->OPEN]

                  WTIME                WSTATUS        INST_OK   INAME            ISTATUS     IMODE     RSTAT    N_OPEN   FLSN            CLSN

                  2022-03-02 16:24:38  OPEN           OK        DAMENGS          OPEN        PRIMARY   VALID    7        33536           33536

  1. 与其它数据库的主备搭建方式比较
    1. oracle dataguard

配置:force logging、修改pfile、配listener.ora 配tnsnames.ora(从库要加 UR=A )、主从库配置standby logfile

搭建方式一 使用RMAN的DUPLICATE:

在备库上

rman target sys/oracle@orcl auxiliary sys/oracle@orcl_dg

duplicate taget database for standby from active database

Sql>alter database open read only ;

Sql>alter database recover managed standby database using current logfile disconnect from session;

搭建方式二 使用备份恢复的方式:

对主备做全备,在主库上

RMAN>backup current controlfile for standby;

在备库上:

Rman>restore standby contolfile from ‘xxxx’;

RMAN> sql 'alter database mount';

RMAN>restore database;

sql>shutdown immediate;

Sql>starup nomount

sql>alter database mount standby database;

Sql>alter database open read only;

sql>alter database recover managed standby database using current logfile disconnect from session;

实现方式:主库传输redo log 给从库,如果是物理从库则redo apply , 是块级的;如果是逻辑从库则是sql apply,是语句级的

搭建难度:4星,可以做到主库不停

    1. mysql master-slave

配置:主从的serverid要不同,如果开启gtid 要gtid_mode=on enforce-gtid-consistency=o

搭建方式:

1. 主库导出数据,从库导入数据

2. change master to masterhost='', master_user='',master_password='',master_port='',master_log_file='',master_log_pos=xxx 。如果是GTID模式 change master to masterhost='', master_user='',master_password='',master_port='',master_auto_position=1

实现方式:传输binlog到从库并重放

搭建难度:2星,可以做到主库不停

    1. DM8 实时主备

配置:主从都要配dm.ini、dmmal.ini、dmarch.in、dmwatch.ini,还需要单独配一个dmmonitor.ini

搭建方式:

  1. 通过联机或脱机对主库进行备份,然后在备库还原
  2. 将主备库mount
  3. 启动主备库的dmwatcher,由watcher来检测并open主备库
  4. 启动dmmonitor进行管理

实现方式:传输redo log到从库并重放

搭建难度:5星,由于数据库需要在dbwatch启动前置于mount状态,所以会对业务有影响 

参考:达梦技术丛书-DM8数据守护与读写分离集群

欢迎访问达梦社区:http://eco.dameng.com

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值