达梦8数据守护集群备库故障恢复

最新推荐文章于 2024-11-17 16:30:03 发布

二两面

最新推荐文章于 2024-11-17 16:30:03 发布

阅读量371

点赞数 2

CC 4.0 BY-SA版权

文章标签：数据库

本文链接：https://blog.csdn.net/qq_36192280/article/details/129649337

文章描述了一种在主备集群环境中，当备库因磁盘问题损坏时的恢复步骤。首先，通过主库进行在线备份，然后将备份文件拷贝到备库并使用RMAN进行数据库的还原和日志应用，接着更新数据库状态并切换为备库模式，最后启动备库守护进程，观察备库自动加入集群的过程。整个过程中，主库服务未受影响。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

一、环境描述

两节点主备集群+普通监视器，因磁盘原因备库损坏，监视器、守护进程正常主库正常对外提供服务，现需要修复磁盘恢复备库
存在监视器情况下，备库故障在守护进程、数据库进程异常情况下，故障后主库会短暂suspend后open，确认监视器优先级较高，建议部署确认监视器。

二、恢复步骤

因主库是primary模式，可以通过主库在线备份后，拷贝到备库还原，备库恢复完成，且启动守护进程后会自动加入集群当中，不影响主库服务。

2.1、主库在线备份

SQL> backup database backupset '/dm8/backup/full.bak1';
操作已执行
已用时间: 00:00:04.923. 执行号:601.
拷贝至备库
[dmdba@210 backup]$ scp -r full.bak1/ 192.168.0.200:/tmp

2.2、备库还原

一共三步：还原数据库、应用备份期间产生的日志、更新魔术

[dmdba@200 bin]$ dmrman 
dmrman V8
RMAN> restore database '/dm8/data/DM01/dm.ini'  from backupset '/tmp/full.bak1';
restore database '/dm8/data/DM01/dm.ini' from backupset '/tmp/full.bak1';
file dm.key not found, use default license!
Normal of FAST
Normal of DEFAULT
Normal of RECYCLE
Normal of KEEP
Normal of ROLL
[Percent:100.00%][Speed:0.00M/s][Cost:00:00:03][Remaining:00:00:00]                                 
restore successfully.
time used: 00:00:03.861
RMAN> recover database '/dm8/data/DM01/dm.ini'  from backupset '/tmp/full.bak1';
recover database '/dm8/data/DM01/dm.ini' from backupset '/tmp/full.bak1';
Database mode = 1, oguid = 453331
Normal of FAST
Normal of DEFAULT
Normal of RECYCLE
Normal of KEEP
Normal of ROLL
EP[0]'s cur_lsn[492723], file_lsn[492723]
[Percent:100.00%][Speed:0.00PKG/s][Cost:00:00:00][Remaining:00:00:00]                               
recover successfully!
time used: 00:00:02.613
RMAN> recover database '/dm8/data/DM01/dm.ini'  update db_magic;
recover database '/dm8/data/DM01/dm.ini' update db_magic;
Database mode = 1, oguid = 453331
Normal of FAST
Normal of DEFAULT
Normal of RECYCLE
Normal of KEEP
Normal of ROLL
EP[0]'s cur_lsn[494458], file_lsn[494458]
recover successfully!
time used: 990.640(ms)

2.3、mount模式启动更改数据库模式为备库模式

SQL> sp_set_para_value(1,'ALTER_MODE_STATUS',1);
DMSQL executed successfully
used time: 3.263(ms). Execute id is 2.
SQL> alter database standby;
executed successfully
used time: 4.260(ms). Execute id is 0.
SQL> sp_set_para_value(1,'ALTER_MODE_STATUS',0);
DMSQL executed successfully
used time: 3.376(ms). Execute id is 3.
SQL> exit

2.4、启动备库守护进程

[dmdba@200 bin]$ ./DmWatcherServiceDM  start 
Starting DmWatcherServiceDM: [ OK ]

三、观察监视器备库自动加入集群当中，恢复完成

[monitor]         2023-03-19 13:26:26: 守护进程(DMSVR01)状态切换 [NONE-->STARTUP]
[monitor]         2023-03-19 13:26:27: 守护进程(DMSVR01)状态切换 [STARTUP-->OPEN]
                  WTIME                WSTATUS        INST_OK   INAME            ISTATUS     IMODE     RSTAT    N_OPEN   FLSN            CLSN            
                  2023-03-19 13:26:27  OPEN           OK        DMSVR01          OPEN        STANDBY   INVALID  11       494458          494458          

[monitor]         2023-03-19 13:26:28: 守护进程(DMSVR02)状态切换 [OPEN-->RECOVERY]
                  WTIME                WSTATUS        INST_OK   INAME            ISTATUS     IMODE     RSTAT    N_OPEN   FLSN            CLSN            
                  2023-03-19 13:26:27  RECOVERY       OK        DMSVR02          OPEN        PRIMARY   VALID    11       494608          494609          

[monitor]         2023-03-19 13:26:30: 守护进程(DMSVR02)状态切换 [RECOVERY-->OPEN]
                  WTIME                WSTATUS        INST_OK   INAME            ISTATUS     IMODE     RSTAT    N_OPEN   FLSN            CLSN            
                  2023-03-19 13:26:30  OPEN           OK        DMSVR02          OPEN        PRIMARY   VALID    11       494609          494609