KingbaseES R6 集群修改ssh端口执行sys_backup.sh备份案例

最新推荐文章于 2024-05-17 14:37:05 发布
最新推荐文章于 2024-05-17 14:37:05 发布
阅读量884 收藏
点赞数
文章标签： 数据库 linux centos nginx mysql
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/lyu1026/article/details/124465010
版权

数据库环境：**

test=# select version();
                                                       version                                                    
    ------------------------------------------------------------------------------------------------------------------
 KingbaseES V008R006C003B0010 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-46), 64-bit
(1 row)

操作系统：

[kingbase@node1 bin]$ cat /etc/centos-release
CentOS Linux release 7.2.1511 (Core)

集群架构：

案例说明：

1)本案例在通用机环境下执行。sys_backup.sh是调用sys_rman做物理备份，对于集群环境需要用到ssh端口做远程连接，当修改ssh端口，会影响sys_backup.sh正常执行。
2)修改ssh端口对于集群的运行，只需要修改repmgr.conf文件中变量即可。
3)对于修改ssh端口后，用sys_backup.sh作物理备份，需要在sys_backup.sh脚本中修改所有ssh语句的连接端口，修改的位置较多。
4)建议如果对ssh修改端口后，需要用sys_backup.sh作备份的应用较多的情况下，在sys_backup.sh脚本中用变量来指定ssh端口号。

一、查看当前集群状态

[kingbase@node2 bin]$ ./repmgr cluster show
 ID | Name    | Role    | Status    | Upstream | Location | Priority | Timeline | Connection string                                                                                                                                
----+---------+---------+-----------+----------+----------+----------+----------+----------------
 1  | node248 | standby |   running | node249  | default  | 100      | 6        | host=192.168.7.248 user=esrep dbname=esrep port=54321 connect_timeout=10 keepalives=1 keepalives_idle=10 keepalives_interval=1 keepalives_count=3
 2  | node249 | primary | * running |          | default  | 100      | 6        | host=192.168.7.249 user=esrep dbname=esrep port=54321 connect_timeout=10 keepalives=1 keepalives_idle=10 keepalives_interval=1 keepalives_count

二、修改操作系统和集群配置文件ssh端口号(所有节点)

1)查看系统原ssh端口号(默认22)

[kingbase@node2 bin]$ netstat -antlp |grep 22
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 192.168.122.1:53        0.0.0.0:*               LISTEN      -                   
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      -                   
tcp        0      0 192.168.7.249:22        192.168.7.116:55883     ESTABLISHED -                   
tcp6       0      0 :::22                   :::*                    LISTEN      -

2)查看集群repmgr.conf应用ssh端口号

[kingbase@node2 bin]$ cat ../etc/repmgr.conf|grep ssh
ssh_options='-q -o ConnectTimeout=10 -o StrictHostKeyChecking=no -o ServerAliveInterval=2 -o ServerAliveCountMax=5 -p 22'

=== 默认用-p 22 指定集群ssh通讯端口===

3)修改操作系统端口

[root@node1 ~]# cat /etc/ssh/sshd_config|grep -i Port
# If you want to change the port on a SELinux system, you have to tell
# semanage port -a -t ssh_port_t -p tcp #PORTNUMBER
Port 2222

4)修改集群ssh通讯端口(改为2222)

[kingbase@node1 bin]$ cat ../etc/repmgr.conf |grep sshssh_options='-q -o ConnectTimeout=10 -o StrictHostKeyChecking=no -o ServerAliveInterval=2 -o ServerAliveCountMax=5 -p 2222'

5)重启sshd服务

[root@node1 ~]# systemctl restart sshd[root@node1 ~]# netstat -an |grep 22tcp        0      0 0.0.0.0:2222            0.0.0.0:*               LISTEN

6)通过非默认端口ssh连接测试

[root@node1 ~]# ssh -p 2222 node2Last failed login: Mon Mar  1 17:06:07 CST 2021 from 192.168.7.116 on ssh:nottyThere were 2 failed login attempts since the last successful login.Last login: Mon Mar  1 16:43:29 2021 from 192.168.7.249

=== 从以上可知，修改端口后ssh信任关系正常===

7)sys_monitor.sh重启集群测试

[kingbase@node1 bin]$ ./sys_monitor.sh restart
2021-03-01 17:29:55 Ready to stop all DB ...
Service process "node_export" was killed at process 11833
Service process "postgres_ex" was killed at process 11834
Service process "node_export" was killed at process 9343
Service process "postgres_ex" was killed at process 9344
2021-03-01 17:30:00 begin to stop repmgrd on "[192.168.7.248]".
2021-03-01 17:30:01 repmgrd on "[192.168.7.248]" stop success.
2021-03-01 17:30:01 begin to stop repmgrd on "[192.168.7.249]".
2021-03-01 17:30:02 repmgrd on "[192.168.7.249]" stop success.
2021-03-01 17:30:02 begin to stop DB on "[192.168.7.249]".waiting for server to shut down..... done
server stopped
2021-03-01 17:30:04 DB on "[192.168.7.249]" stop success.
2021-03-01 17:30:04 begin to stop DB on "[192.168.7.248]".waiting for server to shut down......... done
server stopped
2021-03-01 17:30:11 DB on "[192.168.7.248]" stop success.
2021-03-01 17:30:11 Done.2021-03-01 17:30:11 Ready to start all DB ...
2021-03-01 17:30:11 begin to start DB on "[192.168.7.248]".waiting for server to start.... done
server started
2021-03-01 17:30:12 execute to start DB on "[192.168.7.248]" success, connect to check it.
2021-03-01 17:30:13 DB on "[192.168.7.248]" start success.
2021-03-01 17:30:13 Try to ping trusted_servers on host 192.168.7.248 ...
2021-03-01 17:30:16 Try to ping trusted_servers on host 192.168.7.249 ...
2021-03-01 17:30:18 begin to start DB on "[192.168.7.249]".waiting for server to start.... done
server started
2021-03-01 17:30:20 execute to start DB on "[192.168.7.249]" success, connect to check it.
2021-03-01 17:30:21 DB on "[192.168.7.249]" start success. 
ID | Name    | Role    | Status    | Upstream  | Location | Priority | Timeline | Connection string                                                                                                                                ----+---------+---------+-----------+-----------+----------+----------+----------+--------------------------------------------------------------------------------------------------------------------------------------------------- 
1  | node248 | standby |   running | ! node249 | default  | 100      | 6        | host=192.168.7.248 user=esrep dbname=esrep port=54321 connect_timeout=10 keepalives=1 keepalives_idle=10 keepalives_interval=1 keepalives_count=3 
2  | node249 | primary | * running |           | default  | 100      | 6        | host=192.168.7.249 user=esrep dbname=esrep port=54321 connect_timeout=10 keepalives=1 keepalives_idle=10 keepalives_interval=1 keepalives_count=3

WARNING: following issues were detected  - node "node248" (ID: 1) is not attached to its upstream node "node249" (ID: 2)
2021-03-01 17:30:21 The primary DB is started.
2021-03-01 17:30:25 Success to load virtual ip [192.168.7.240/24] on primary host [192.168.7.249].
2021-03-01 17:30:25 Try to ping vip on host 192.168.7.248 ...
2021-03-01 17:30:28 Try to ping vip on host 192.168.7.249 ...
2021-03-01 17:30:30 begin to start repmgrd on "[192.168.7.248]".
[2021-03-01 17:30:31] [NOTICE] using provided configuration file "/home/kingbase/cluster/R6HA/KHA/kingbase/bin/../etc/repmgr.conf"
[2021-03-01 17:30:31] [NOTICE] redirecting logging output to "/home/kingbase/cluster/R6HA/KHA/kingbase/hamgr.log"2021-03-01 17:30:31 repmgrd on "[192.168.7.248]" start success.
2021-03-01 17:30:31 begin to start repmgrd on "[192.168.7.249]".
[2021-03-01 17:29:25] [NOTICE] using provided configuration file "/home/kingbase/cluster/R6HA/KHA/kingbase/bin/../etc/repmgr.conf"[2021-03-01 17:29:25] 
[NOTICE] redirecting logging output to "/home/kingbase/cluster/R6HA/KHA/kingbase/hamgr.log"2021-03-01 17:30:32 repmgrd on "[192.168.7.249]" 
start success. 
ID | Name    | Role    | Status    | Upstream | repmgrd | PID   | Paused? | Upstream last seen
----+---------+---------+-----------+----------+---------+-------+---------+-------------------- 
1  | node248 | standby |   running | node249  | running | 16767 | no      | 0 second(s) ago     
2  | node249 | primary | * running |          | running | 17865 | no      | n/a                2021-03-01 17:30:38 Done.

8)查看集群节点状态

[kingbase@node1 bin]$ ./repmgr cluster show
 ID | Name    | Role    | Status    | Upstream | Location | Priority | Timeline | Connection string                                                                                                                                ----+---------+---------+-----------+----------+----------+----------+----------+---------------- 
1  | node248 | standby |   running | node249  | default  | 100      | 6        | host=192.168.7.248 user=esrep dbname=esrep port=54321 connect_timeout=10 keepalives=1 keepalives_idle=10 keepalives_interval=1 keepalives_count=3 
2  | node249 | primary | * running |          | default  | 100      | 6        | host=192.168.7.249 user=esrep dbname=esrep port=54321 connect_timeout=10 keepalives=1 keepalives_idle=10 keepalives_interval=1 keepalives_count

=== 从以上可知，修改ssh端口后，集群通讯正常===

二、修改ssh端口后执行sys_backup.sh备份(所有节点)

1)在修改ssh端口前备份基础上停止备份测试

[kingbase@node1 bin]$ ./sys_backup.sh stop
Disable all sys_rman in crontab-daemon
ssh: connect to host 192.168.7.248 port 22: Connection refused
ssh: connect to host 192.168.7.248 port 22: Connection refused
ssh: connect to host 192.168.7.248 port 22: Connection refused

=== 如上所示，在通过sys_backup.sh基于集群环境做备份时，会通过ssh做远程节点的连接，修改端口后，无法通过ssh连接===

2)修改sys_backup.sh脚本中ssh端口

=== 修改”ssh_cmd“变量===

# local function_ssh_cmd_="ssh -p 2222 -n -o ConnectTimeout=30 -o StrictHostKeyChecking=no -o PreferredAuthentications=publickey -- "
function _log () {
        echo "$*" >> /tmp/sys_backup.sh.log
} # end of _log

=修改”_gene_ssh_pwd_less“中ssh通讯端口=

function _gene_ssh_pwd_less() {
        _ip="${1}"
        _user="${2}"
        # 1. check whether pwd-less work
        ssh -p 2222 -t -o ConnectTimeout=30 -o PreferredAuthentications=publickey ${_user}@${_ip} date 1>/dev/null 2>/dev/null
        _local2remote_rt=$?
        ssh -p 2222 -t -o ConnectTimeout=30 -o PreferredAuthentications=publickey ${_user}@${_ip} "ssh -p 2222 ${_user}@${_repo_ip} date>/dev/null 2>/dev/null" 2>/dev/null

=== 配置ssh免密中ssh端口===

# set local.pub to remote, get remote.pub to local        _remote_pub_buf=` ssh -p 2222 -q -o StrictHostKeyChecking=no -o ConnectTimeout=30 -o PreferredAuthentications=password -- ${_user}@${_ip} \                "if [ ! -f \\${HOME}/.ssh/id_rsa.pub ] ; then echo -e '\ny' | ssh-keygen -t rsa -N '' >/dev/null 2>/dev/null ; fi;echo ${_t_buf_pub} >> \\${HOME}/.ssh/authorized_keys;chmod 600 \\${HOME}/.ssh/authorized_keys;cat  \\${HOME}/.ssh/id_rsa.pub;" `

三、执行sys_backup.sh备份

1)执行init备份初始化

[kingbase@node2 bin]$ ./sys_backup.sh init
# generate local sys_rman.conf...DONE
# update all node: sys_rman.conf and archive_command with sys_rman.archive-push...
# update all node: sys_rman.conf and archive_command with sys_rman.archive-push...DONE
# create stanza and check...(maybe 60+ seconds)ERROR: check stanza failed, check log file /tmp/sys_rman_check.log

=== 脚本执行报错，在check stanza失败===

查看日志：

[kingbase@node2 bin]$ cat /tmp/sys_rman_check.log
2021-03-01 12:38:56.011 P00   INFO: check command begin 2.27: --config=/home/kingbase/kbbr_repo/sys_rman.conf --log-level-console=info --log-level-file=info --log-path=/tmp --log-subprocess --kb2-host=192.168.7.248 --kb2-host-user=kingbase --kb1-path=/home/kingbase/cluster/R6HA/KHA/kingbase/data --kb2-path=/home/kingbase/cluster/R6HA/KHA/kingbase/data --kb1-port=54321 --kb2-port=54321 --kb1-user=esrep --kb2-user=esrep --repo1-path=/home/kingbase/kbbr_repo --stanza=kingbaseWARN: unable to check kb-2: [UnknownError] remote-0 process on '192.168.7.248' terminated unexpectedly [255]: ssh: connect to host 192.168.7.248 port 22: Connection refusedERROR: [125]: remote-0 process on '192.168.7.248' terminated unexpectedly [255]: ssh: connect to host 192.168.7.248 port 22: Connection refused2021-03-01 12:38:56.529 P00   INFO: check command end: aborted with exception [125]

=== 从日志可可知，在执行check stanza时，需要通过ssh连接备库；但是使用ssh连接时，仍然使用修改前的22端口，无法使用修改后的2222端口，导致连接备库失败，check stanza失败===

3)在sys_backup.sh脚本注释stanza检测(跳过check stanza)

371 #${_rman_bin} --config=${_rman_conf_file} --stanza=${_stanza_name} --log-level-console=info check >>/tmp/sys_rm    an_check.log 2>&1372 #if [ "X0" != "X$?" ] ; then
373 #        echo "ERROR: check stanza failed, check log file /tmp/sys_rman_check.log"374 #        exit 3
375 #fi
376 echo "# create stanza and check...DONE"

4)再次执行sys_backup.sh备份

# init 初始化

[kingbase@node2 bin]$ ./sys_backup.sh init
# generate local sys_rman.conf...DONE
# update all node: sys_rman.conf and archive_command with sys_rman.archive-push...
# update all node: sys_rman.conf and archive_command with sys_rman.archive-push...DONE
# create stanza and check...(maybe 60+ seconds)# create stanza and check...DONE# initial first full backup...(maybe several minutes)
# initial first full backup...DONE# Initial sys_rman OK.'sys_backup.sh start' should be executed when need back-rest feature.

# start 开始备份

[kingbase@node2 bin]$ ./sys_backup.sh start
Enable some sys_rman in crontab-daemonSet full-backup in 7 daysSet incr-backup in 1 days
0 2 */7 * * kingbase /home/kingbase/cluster/R6HA/KHA/kingbase/bin/sys_rman --config=/home/kingbase/kbbr_repo/sys_rman.conf --stanza=kingbase --archive-copy --type=full backup >>/tmp/sys_rman_backup_full.log 2>&1
0 4 */1 * * kingbase /home/kingbase/cluster/R6HA/KHA/kingbase/bin/sys_rman --config=/home/kingbase/kbbr_repo/sys_rman.conf --stanza=kingbase --archive-copy --type=incr backup >>/tmp/sys_rman_backup_incr.log 2>&1

# pause 备份暂停

[kingbase@node2 bin]$ ./sys_backup.sh pause
Puase the sys_rman...DONE

# unpause 停止暂停

[kingbase@node2 bin]$ ./sys_backup.sh unpause
Un-Puase the sys_rman...DONE

# stop 停止备份

[kingbase@node2 bin]$ ./sys_backup.sh stop
Disable all sys_rman in crontab-daemon
[kingbase@node2 bin]$ cat /etc/cron.d/KINGBASECRON 
*/1 * * * * kingbase . /etc/profile;/home/kingbase/cluster/R6HA/KHA/kingbase/bin/kbha -A daemon -f /home/kingbase/cluster/R6HA/KHA/kingbase/bin/../etc/repmgr.conf >> /home/kingbase/cluster/R6HA/KHA/kingbase/bin/../kbha.log 2>&1
#*/1 * * * * kingbase  /home/kingbase/cluster/kha/db/bin/network_rewind.sh#*/1 * * * * root  /home/kingbase/cluster/kha/kingbasecluster/bin/restartcluster.sh

=== 从以上信息获知，修改系统ssh端口后，通过sys_backup.sh备份成功===

Kingbase 研究院
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
KingbaseES V8R6C5单实例sys_backup.sh备份案例
lyu1026的博客
04-21 1252
​ 案例说明： KingbaseES V8R6C5版本中使用了securecmdd工具，用于主机节点间的通讯，默认端口8890。备份工具sys_backup.sh默认使用了securecmdd工具，对于通用机单实例环境，在执行“sys_backup.sh init”后，会调用securecmd工具连接主机节点备份，导致在执行“sys_backup.sh start”启动备份时，无法创建KINGB...
KingbaseES使用sys_backup.sh脚本init初始化配置文件常见错误处理
lyu1026的博客
02-28 1094
KingbaseES使用sys_backup.sh脚本init初始化配置文件常见错误处理: sys_backup.sh脚本按照如下顺序寻找初始化配置文件: [kingbase@postgres ~]$ sh -x sys_backup.sh init +++ readlink -f sys_backup.sh ++ dirname /home/kingbase/sys_backup.sh + s...
人大金仓数据库KingbaseES 基础备份之sys_start_backup、sys_stop_backup
最新发布
arthemis_14的博客
05-17 591
返回值：排他模式所有节点号及其stoppoint，非排他模式分为三部分第一部分为所有节点号及其stoppoint，第二部分为labelfile中的内容，第三部分为tablespacemapfile文件中的内容。基础备份从并发的角度可以分为排他模式和非排他模式，排他模式只允许系统中有一个备份过程存在，非排他模式允许多个备份过程同时存在于系统中。第三个参数：true 执行排他模式物理备份、false执行非排他模式物理备份。第一个参数：true结束排他模式物理备份，false结束非排他模式的物理备份。
KingbaseES R3集群备库执行sys_backup.sh物理备份案例
lyu1026的博客
03-18 895
案例说明： KingbaseES R3的后期版本支持通过sys_backup.sh执行sys_rman的物理备份，实际上是调用了sys_rman_v6的工具做物理备份。本案例是在备库上执行集群的备份，repo目录在备库上，采用cluster模式备份。 数据库版本： TEST=# select version(); ...
ssh启动zookeeper失败的集群修改后的启动脚本
qq_43662627的博客
10-25 104
不知道用ssh命令启动不了zookeeper集群所以我干脆改用两个脚本启动zookeeper 在此处使用启动脚本a启动zookeeper的启动脚本b #!/bin/sh for host in hadoop01 hadoop02 hadoop03 do ssh $host "source /etc/profile; sh /root/xcall1.sh" done 此处是zookeeper的启动脚本的启动脚本b #!/bin/sh for host in hadoop01 hadoop02 hadoo
SSH修改远程端口后无法登录的解决办法
User_bie的博客
10-14 4945
ssh centos linux
KingbaseES_V008R003C002B0160_Win64_install.exe
11-24
kingbase客户端工具
KingbaseES_V008R003C002B0160_Win64_install.tar
05-26
版本：V008R003C002B0160 针对于有些用户客户端和服务端版本不一致，服务端版本是V008R003C002B0160 即可以使用此工具
KingbaseES JDBC 接口简介 2019_2.pptx
09-19
KingbaseES JDBC 接口简介 2019_2.pptx
KingbaseES-V8_manual.pdf
10-13
kingbase sql教程
人大金仓KingbaseES V8R6完整文档
04-27
其次，"[高可用]KingbaseES集群使用手册(Linux版本).pdf"深入解析了KingbaseES在Linux环境下的集群配置和管理，包括高可用性解决方案，如主备切换和负载均衡，确保数据库服务的连续性和稳定性。 "[应用开发及迁移]...
kingbaseV8R6读写分离集群主备库时间线不同问题解决
weixin_44583303的博客
01-19 1266
kingbaseV8R6读写分离集群主备库时间线不同问题解决方法主备时间线不同问题方法一：提升主库时间线时间线的确定确定集群状态关闭集群提升主库时间线检查主备库时间线备库执行执行rejoin 操作，将备库重新加入集群确定集群状态方法二：降低备库时间线查看时间线修复备库启动备库查看集群状态将备机加入集群查看集群状态注：数据有风险，操作需谨慎！ 主备时间线不同问题 方法一：提升主库时间线 描述：主库时间线小于备库时间线，主库有物理备份，在不重做备机的情况下恢复集群 时间线的确定 #node1：(主库) n
kingbaseV8物理备份恢复常见异常处理（三）
weixin_45105073的博客
01-03 454
解决：在所有节点的 _repo_path/ sys_rman.conf 文件内的 [global] 下新增一行“archivetimeout=600”，增大超时时间。解决：要求管理员在数据库节点与外部备份节点之间，以相应的 OS 用户，互相进行 SSH 登录，以验证SSH 登录场景。原因之二：可能此时数据库业务量较大，造成的 WAL 日志文件很多，导致 WAL 日志文件归档超时（默认 60s）原因：因为上一次备份被意外中断，导致上一次备份的某些文件没有正常规整。解决：检查本信息给出的日志文件。
金仓数据库KingbaseES备份与恢复工具手册（附录A：备份管理与优化操作）
arthemis_14的博客
10-20 1250
KingbaseES备份与恢复工具手册 --备份管理与优化操作
KingbaseES V8R6备份恢复案例之--删除test数据库后sys_backup.sh备份
lyu1026的博客
07-09 1128
案例说明： KingbaseES V8R6通过sys_backup.sh执行物理备份，默认sys_backup.sh执行备份初始化时，需要连接test数据库进行身份的认证；在一些生产环境为了安全需求，会删除test库或被误删除，导致sys_rman连接数据库失败 。如果是误删除，比较容易解决，重新创建一个test库即可。如果是安全需求删除，不能重建test库，则需要修改sys_backup.sh...
KingbaseES V8R6C5B041 sys_backup.sh单实例备份案例
lyu1026的博客
03-24 841
​数据库版本： test=# select version(); version -----------------------------------------------...
解决金仓数据库KingbaseES表空间备份时报错的问题
arthemis_14的博客
03-01 1243
解决金仓数据库KingbaseES表空间备份时报错的问题
SHELL/SSH基础知识（入门篇）-包含 shell 脚本语言的基本用法、 shell 脚本语言的基本用法、流程控制、函数 function、其它脚本相关工具、数组 array(欢迎留言交流)
m0_65617010的博客
11-14 1476
包含 shell 脚本语言的基本用法、 shell 脚本语言的基本用法、流程控制、函数 function、其它脚本相关工具、数组 arra，欢迎大家交流讨论。
test=# SELECT * FROM pg_catalog.pg_backup_history; ERROR: relation "pg_catalog.pg_backup_history" does not exist LINE 1: SELECT * FROM pg_catalog.pg_backup_history;
05-31
如果您执行 `SELECT * FROM pg_catalog.pg_backup_history;` 命令时遇到 "relation does not exist" 的错误，可能是因为 Kingbase 数据库并没有这个表。 在 Kingbase 中，备份历史记录是存储在 `pg_stat_backup` ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值