1 Star 7 Fork 0

dbother / MySQLDeploy

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
AGPL-3.0

概述

环境

脚本基于 CentOS 7.9 测试执行,需要部署到其他版本需要更新soft目录下资源包

功能

部署生产环境可使用的MySQL高可用集群

  • 支持单机部署
  • 支持主从部署
    • 主从使用增强半同步模式,防止数据丢失
  • 支持基于 orchestrator + vip 的高可用集群部署(3台服务器)
    • orchestrator 组件3台的话会自建 raft集群
    • 发生切换可发送钉钉消息
  • 支持基于 replication-manager +vip 的高可用集群部署(支持2台服务器部署)
    • 这个模式 replication-manager高可用组件是单点的
    • 发生切换可发送钉钉消息
  • 支持先部署主从,后期加高可用组件
  • 支持部署备份脚本
    • 可远程备份
    • 可发送钉钉消息

限制

  • 当前仅支持2层 VIP 模式
  • 高可用模式需要配置免密(为了调用切换VIP)
  • 对于 event ,高可用切换时候会关闭原主的 event_scheduler,切换后不会打开新主的event置为 enable,因为原生时间定时器不能保证主备event状态一致。功能看需求再去实现,也可自行实现,思路基本是:
    • 1.定时记录主库event的状态,如在某文件或某个库内
    • 2.同步event状态到备库
    • 3.高可用切换时读取文件设置状态
  • 脚本基于CentOS 7.9 测试,理论上RedHat系的都能支持(需要更换对应安装包)

MySQL部署

脚本帮助信息:

# ./deploy.sh 
Usage:  
    ./deploy.sh single                                   单机部署
    ./deploy.sh master                                   部署master节点
    ./deploy.sh slave                                    部署slave节点,会自动建立主从关系
    ./deploy.sh orchestrator                             部署高可用中间件orchestrator
    ./deploy.sh ha_orch_with_vip                         部署基于 orchestrator+VIP 的MySQL集群
    ./deploy.sh ha_replication_manager_with_vip          部署基于 replication-manager+VIP 的MySQL集群
    ./deploy.sh master_alone                             单独部署master节点
    ./deploy.sh slave_alone                              单独部署slave节点,不会自动建立主从
    ./deploy.sh orchestrator                             仅部署 orchestrator 高可用组件
    ./deploy.sh replication_manager                      仅部署 replication-manager 高可用组件
    ./deploy.sh check_ssh                                检查ssh是否已正常配置
    ./deploy.sh vip_add                                  根据配置文件信息添加VIP
    ./deploy.sh vip_del                                  根据配置文件信息删除VIP

    ## 卸载
    ./deploy.sh uninstall_mysql  [3306]                  卸载当前服务器上的 MySQL
    ./deploy.sh uninstall_orchestrator                   卸载当前服务器上的 Orchestrator
    ./deploy.sh uninstall_replication_manager            卸载当前服务器上的 replication-manager
    ./deploy.sh uninstall_all    [3306]                  卸载当前服务器上的所有相关的,包括高可用中间件与MySQL

相关路径

路径 用途
/usr/local/mysql MySQL解压路径软链
${MYSQL_DIR}/mysql${MYSQL_PORT}/data 数据路径,会根据配置文件中MYSQL_DIR参数创建,如MYSQL_PORT=/app,MYSQL_PORT=3306,则安装后的MySQL数据路径为 /app/mysql3306/data
/tmp/mysql.sock Mysql socket软链,若不存在则连接是需要指定sock路径
/usr/local/orchestrator Orch 高可用组件,其中会包含切换使用的hook脚本
/etc/orchestrator.json Orch 高可用组件配置文件信息
/etc/replication-manager/ Replication-manager 高可用组件配置与脚本相关信息

1.下载并上传安装包

MySQL下载地址:https://dev.mysql.com/downloads/mysql/ 将安装包放入指定路径

mv mysql-8.0.34-linux-glibc2.17-x86_64.tar.gz Deploy_MySQL/soft

2.单机模式

2.1 修改配置文件

cd Deploy_MySQL/install/
vi conf_mysql.cnf

# 根据实际情况修改如下参数
# 本机IP
IPADDR=192.168.60.155
# 8.0/5.7
MYSQL_VERSION='8.0'
MYSQL_PKG=mysql-8.0.34-linux-glibc2.17-x86_64.tar.gz
MYSQL_DIR=/data
# 数据文件所在磁盘名称
## 可使用  df -h /data 和  ll /sys/block 判断出,主要用于判断并修改磁盘调度策略
DISK_DEVICE_NAME=sda
# 自定义端口
MYSQL_PORT=3306
# 默认获取服务器物理内存,可自定义
MEMORY_ALLLOW_GB=`free -g|grep Mem|awk '{print $2}'`
# 密码不能使用双引号包裹,root@localhost的密码
INIT_PASSWORD='Yq@test#123'
# 创建一个超级用户
SUPER_USER='super_admin'
SUPER_PASSWORD='Yq@Test$MySQL#123'

2.2 执行安装

./deploy.sh single

2.3 加载环境变量

若不执行的话,可重新打开下shell窗口

# 安装后会有提示,执行
source /etc/profile.d/mysql_set_env.sh

2.4 启动关闭MySQL

systemctl start mysqld${port}

systemctl start mysqld3306
systemctl stop mysqld3306
systemctl status mysqld3306

3.主从模式

可部署为一主多从

3.1 环境

  • 192.168.60.155 主
  • 192.168.60.156/192.168.60.157 从

3.2 修改配置文件

vim Deploy_MySQL/install/config_mysql.cnf

cd Deploy_MySQL/install/
vi conf_mysql.cnf

# 根据实际情况修改如下参数
# 本机IP
IPADDR=192.168.60.155
# 8.0/5.7
MYSQL_VERSION='8.0'
MYSQL_PKG=mysql-8.0.34-linux-glibc2.17-x86_64.tar.gz
MYSQL_DIR=/data
# 数据文件所在磁盘名称
## 可使用  df -h /data 和  ll /sys/block 判断出,主要用于判断并修改磁盘调度策略
DISK_DEVICE_NAME=sda
# 自定义端口
MYSQL_PORT=3306
# 默认获取服务器物理内存,可自定义
MEMORY_ALLLOW_GB=`free -g|grep Mem|awk '{print $2}'`
# 密码不能使用双引号包裹,root@localhost的密码
INIT_PASSWORD='Yq@test#123'
# 创建一个超级用户
SUPER_USER='super_admin'
SUPER_PASSWORD='Yq@Test$MySQL#123'

######################## 主从模式配置 ###########################
# 服务器组
SERVER_GROUP='192.168.60.155,192.168.60.156,192.168.60.157'
MASTER_IP='192.168.60.155'
REPL_USER='repl'
REPL_PASSWORD='Yq@Repl#123'
# 用户默认host,类似于 create user ... 'repl'@'%'
REPL_IP_SEGMENT='%'

3.3 传入安装文件与配置文件

scp -P22 -r Deploy_MySQL root@192.168.60.156:/opt
scp -P22 -r Deploy_MySQL root@192.168.60.157:/opt

3.4 修改从库配置文件

从库上配置文件由于主库已修改过,仅需要修改参数 ipaddr,将值改为自身服务器ip

vim /opt/Deploy_MySQL/install/config_mysql.cnf

# 156
IPADDR=192.168.60.156

# 157
IPADDR=192.168.60.157

3.5 执行安装

未使用跳转一键安装,因此需要分表在3台机器上执行

# 155 ,需要先安装主
./deploy.sh master

# 156/157 主安装完成后,可同时从服务器上执行
./deploy.sh slave

3.6 加载环境变量

若不执行的话,可重新打开下shell窗口

# 安装后会有提示,每台服务端执行
source /etc/profile.d/mysql_set_env.sh

1主2从架构就部署好了

4.orch高可用模式

4.1 环境

ORCH + VIP 模式需要有同网段的 VIP,用于切换后漂移

服务器 描述
192.168.60.111 VIP
192.168.60.155
192.168.60.156
192.168.60.157

4.2 修改配置文件

vim Deploy_MySQL/install/config_mysql.cnf

已配置上面的单机与主从相关参数,这里省略了...

###################### 高可用模式(依赖主从模式参数) ###############################
# VIP,必须要有VIP
VIP="192.168.60.111"
# 网卡名称,可使用 [ip -4 a] 查看
NET_WORK_CARD_NAME='ens33'
# ssh 端口,默认使用免密使用的是 root 用户,而端口一般默认都是 22
SSH_PORT=22

# 高可用组件使用的用户,会在主库创建
HA_USER='ha_monitor'
HA_PASSWORD='yq@ABC^123#forha'
# 高可用组件web界面登陆用户名密码,一般不用改
HA_HTTP_USER='admin'
HA_HTTP_PASSWORD='repman'
# Orch高可用组件的web端口,默认3000,replication 使用了默认端口,若需要更改端口请安装完成后更改配置文件后重启下
HA_PORT=3000
# 逗号分割,高可用组件自身高可用,若设置为空,则仅单机部署,组件自身没有高可用,若orch组件挂掉则无法支持数据库切换
# 默认和MySQL部署在一起
HA_NODES=${SERVER_GROUP}

########################  dingding通知配置[可选修改]  ##########################
DINGDING_SWITCH=0
WEBHOOK_URL='https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
SECRET='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
# 支持 text/markdown
SEND_TYPE="markdown"
# IS_AT_ALL 中设置任何值代表执行 true ,默认为false
IS_AT_ALL=""
# 设置电话号码会@那个人,这个设置值的话 -at_all 参数不能配置"
AT_MOBILES=""

4.3 同步安装文件与配置文件

scp -P22 -r Deploy_MySQL root@192.168.60.156:/opt
scp -P22 -r Deploy_MySQL root@192.168.60.157:/opt

4.4 修改从库配置文件

从库上配置文件由于主库已修改过,仅需要修改参数 ipaddr,将值改为自身服务器ip

# 156
IPADDR=192.168.60.156

# 157
IPADDR=192.168.60.157

4.5 执行安装

# 155 首先安装设定的主服务器
./deploy.sh ha_orch_with_vip

# 156/157 MySQL 主安装完成后,可同时在从服务器执行
./deploy.sh ha_orch_with_vip

4.6 加载环境变量

# 安装后会有提示,每台服务端执行
source /etc/profile.d/mysql_set_env.sh 
source /etc/profile.d/orchestrator_set_env.sh

4.7 执行拓扑发现

4.7.1 方法1:WEB端发现

地址:http://192.168.60.155:3000 ,可任意一台安装orchestrator的地址 用户名/密码:配置文件中配置的,默认 admin/repman

image-20240122162255780

image.png

点击Submit 后

image.png

点击Clusters-->Dashboard刷新几次

image.png

点击进去发现拓扑已完成

image.png

可拖动执行切换操作

image.png

4.7.1 方法2:使用命令发现

1.加载环境变量

# 需要加载环境变量,可 echo打印下环境变量看下
# source /etc/profile.d/orchestrator_set_env.sh
# echo $ORCHESTRATOR_API
192.168.60.155:3000/api 192.168.60.156:3000/api 192.168.60.157:3000/api

2.使用命令行操作

# 拓扑发现
## 首先确认orch集群组是否正常
# orchestrator-client -b admin:repman -c which-api
192.168.60.155:3000/api

## 执行发现拓扑
# orchestrator-client -b admin:repman -c discover -i 192.168.60.155:3312
test01:3312

其他命令:https://github.com/openark/orchestrator/blob/master/docs/orchestrator-client.md

# 查看已知集群
# orchestrator-client -b admin:repman -c clusters
test01:3312

# 查看当前拓扑
# orchestrator-client -b admin:repman -c topology -i test01:3312
test01:3312   [0s,ok,8.0.34,rw,ROW,>>,GTID]
+ test02:3312 [0s,ok,8.0.34,ro,ROW,>>,GTID]
+ test03:3312 [0s,ok,8.0.34,ro,ROW,>>,GTID]

# 忘记拓扑
orchestrator-client -b admin:repman -c forget -i test01:3312

4.8 启停

systemctl start orchestrator
systemctl stop orchestrator
systemctl status orchestrator

4.9 发生切换处理

1.若存在钉钉告警,则会发送类似如下告警信息:

image.png

2.可能会有被提出集群的服务器存在(如MySQL异常挂掉,或断电等异常问题),可以使用下面脚本将此MySQL实例作为从库重新加入集群

# ./rejoin_as_slave.sh 
Usage: bash rejoin_as_slave.sh 主节点IP
       如:./rejoin_as_slave.sh 192.168.66.155

5.Replication-manager 高可用模式

5.1 环境

  • Replication-manager + VIP 模式需要有同网段的 VIP,用于切换后漂移
  • 如果是2台服务器的话同样的安装方式,只不过少安装一台从库
  • 默认会设置配置文件中的前两个IP作为优先切换选择服务器,如 IP1,IP2,IP3 ,则切换时会优先选择IP1,IP2 | 服务器 | 描述 | | --- | --- | | 192.168.60.111 | VIP | | 192.168.60.155 | 主 | | 192.168.60.156 | 从 | | 192.168.60.157 | 从 |

5.2 修改配置文件

这里配置信息与 orch高可用模式一样的 vim Deploy_MySQL/install/config_mysql.cnf

已配置上面的单机与主从相关参数,这里省略了...

###################### 高可用模式(依赖主从模式参数) ###############################
# VIP,必须要有VIP
VIP="192.168.60.111"
# 网卡名称,可使用 [ip -4 a] 查看
NET_WORK_CARD_NAME='ens33'
# ssh 端口,默认使用免密使用的是 root 用户,而端口一般默认都是 22
SSH_PORT=22

# 高可用组件使用的用户,会在主库创建
HA_USER='ha_monitor'
HA_PASSWORD='yq@ABC^123#forha'
# 高可用组件web界面登陆用户名密码,一般不用改
HA_HTTP_USER='admin'
HA_HTTP_PASSWORD='repman'
# Orch高可用组件的web端口,默认3000,replication 使用了默认端口,若需要更改端口请安装完成后更改配置文件后重启下
HA_PORT=3000
# 逗号分割,高可用组件自身高可用,若设置为空,则仅单机部署,组件自身没有高可用,若orch组件挂掉则无法支持数据库切换
# 默认和MySQL部署在一起
HA_NODES=${SERVER_GROUP}

########################  dingding通知配置[可选修改]  ##########################
DINGDING_SWITCH=0
WEBHOOK_URL='https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
SECRET='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
# 支持 text/markdown
SEND_TYPE="markdown"
# IS_AT_ALL 中设置任何值代表执行 true ,默认为false
IS_AT_ALL=""
# 设置电话号码会@那个人,这个设置值的话 -at_all 参数不能配置"
AT_MOBILES=""

5.3 同步安装文件与配置文件

scp -P22 -r Deploy_MySQL root@192.168.60.156:/opt
scp -P22 -r Deploy_MySQL root@192.168.60.157:/opt

5.4 修改从库配置文件

从库上配置文件由于主库已修改过,仅需要修改参数 ipaddr,将值改为自身服务器ip

# 156
IPADDR=192.168.60.156

# 157
IPADDR=192.168.60.157

5.5 执行安装

  • 先部署一个主从
  • 选一个从库安装高可用组件,建议最后一个从库IP地址
# 155 ,需要先安装主
./deploy.sh ha_replication_manager_with_vip

# 156/157 主安装完成后,可同时从服务器上执行
./deploy.sh ha_replication_manager_with_vip

# 157 安装 replication 高可用组件
./deploy.sh replication_manager

5.6 加载环境变量

# 安装后会有提示,每台服务端执行
source /etc/profile.d/mysql_set_env.sh

5.7 确认拓扑

5.7.1 方式1:web界面

地址:http://192.168.60.155:10001 用户名/密码:配置文件中配置的,默认 admin/repman

image.png

注意:确认下 ALTER 模块与下方日志模块有没有错误,若有错误,请排查 /var/log/replication-manager.log HA 这个按钮点击的话可测试高可用切换

image.png

5.7.2 方式2:使用命令行

# 查看拓扑
# replication-manager-cli topology
| Group: cluster1 |  Mode: Manual 
                 Id            Host   Port          Status   Failures   Using GTID         Current GTID           Slave GTID             Replication Health  Delay  RO
db2586268195480129671  192.168.60.155   3312          Master          0          Yes 0-3424622915634688266-2,0-5865390189271014773-12                                                          0 OFF
db14381080583893135461  192.168.60.156   3312           Slave          0          Yes 0-3424622915634688266-2,0-5865390189271014773-12       0-0-0,0-5856-0                                     0  ON
db11222596407304359995  192.168.60.157   3312           Slave          0          Yes 0-3424622915634688266-2,0-5865390189271014773-12       0-0-0,0-5856-0  

# 执行switchover切换
replication-manager-cli switchover

5.8 启停

systemctl start replication-manager
systemctl stop replication-manager
systemctl status replication-manager

6.先部署主从,后添加高可用

1.部署主从,参考上面 [3.主从模式] 2.对已有主从添加高可用(默认配置文件已配置,不清楚查看上述高可用部署节点文档)

############# orch模式 ###############
# 服务器分别执行
./deploy.sh orchestrator
# 主节点执行添加VIP
./deploy.sh vip_add


########## replication 模式######################
# 选择一台从服务器
./deploy.sh replication_manager

7.卸载

# 卸载所有
./deploy.sh uninstall_all 3306

# 卸载MySQl
./deploy.sh uninstall_mysql 3306

# 卸载orchestrator
./deploy.sh uninstall_orchestrator

# 卸载 replication-manager
./deploy.sh uninstall_replication_manager

备份部署

Xtrabackup部署

1.下载并安装xtrabackup

下载地址:https://www.percona.com/downloads#percona-xtrabackup 5.7 版本下载:Percona XtraBackup 2.4 8.0 版本下载对应的小版本:如MySQL 8.0.34 下载对应的 Percona XtraBackup 8.0.34

yum install -y percona-xtrabackup-80-8.0.34-29.1.el7.x86_64.rpm

2.创建备份用户

脚本使用 socket 方式连接进行备份,因此创建为 '用户'@'localhost' 的用户

5.7 版本

# 用户名/密码可自行修改
CREATE USER 'databak'@'localhost' IDENTIFIED BY 'Yq@BackUP!321';
GRANT RELOAD, LOCK TABLES, PROCESS, REPLICATION CLIENT ON *.* TO 'databak'@'localhost';

8.0 版本

# 用户名/密码可自行修改
CREATE USER 'databak'@'localhost' IDENTIFIED BY 'Yq@BackUP!321';
GRANT BACKUP_ADMIN, PROCESS, RELOAD, LOCK TABLES, REPLICATION CLIENT ON *.* TO 'databak'@'localhost';
GRANT SELECT ON performance_schema.log_status TO 'databak'@'localhost';
GRANT SELECT ON performance_schema.keyring_component_status TO'databak'@'localhost';
GRANT SELECT ON performance_schema.replication_group_members TO databak@'localhost';

3.修改配置文件

选择一台从库用于备份,选择从库原因为不影响主库写入

  • 如果需要远程备份
    • 需要备份服务器与远程服务器做好ssh免密
    • 远程备份目录已创建
    • REMOTE_BACKUP_SWITCH 设置为 1
  • 如需钉钉发送每日备份信息
    • DINGDING_SWITCH 设置为 1
    • WEBHOOK_URL / SECRET 设置钉钉机器人对应值即可
cd Deploy_MySQL/backup/
vim conf_xtrabackup.conf

########################  xtraback信息配置[必须根据环境修改]  ##########################
BACKUP_SAVE_DAYS=7
BACKUP_DIR=/data/backup
BACKUP_PREFIX_NAME="xtra_full"
## 压缩并发进程与备份并发进程数,默认都为2
COMPRESS_THREADS=2
PARALLEL=2

########################  Mysql备份用户信息[必须根据环境修改]  ##########################
BACKUP_USER=databak
BACKUP_PWD='Yq@BackUP!321'
MYSQL_CNF_DIR=/data/mysql3306/my3306.cnf
MYSQL_SOCK_DIR=/data/mysql3306/data/mysql.sock
LOCAL_HOST_IP=192.168.60.155

########################  远程传输配置,使用远程需要配置免密[可选修改]  ##########################
## 远程备份开关,默认0,设置为 1 开启
REMOTE_BACKUP_SWITCH=0
REMOTE_TITLE="数据库远程备份"
REMOTE_USER=root
REMOTE_HOST=192.168.60.156
REMOTE_PORT=22
REMOTE_BACKUP_DIR=/data/backup
########################  dingding通知配置[可选修改]  ##########################
DINGDING_SWITCH=0
MSG_TITLE="数据库备份"
WEBHOOK_URL='https://oapi.dingtalk.com/robot/send?access_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
SECRET='xxxxxxxxxxxxxxxxxxxxxxxxxxxx'
# 支持 text/markdown
SEND_TYPE="markdown"
# IS_AT_ALL 中设置任何值代表执行 true ,默认为false
IS_AT_ALL=""
# 设置电话号码会@那个人,这个设置值的话 -at_all 参数不能配置"
AT_MOBILES=""

3.执行备份

3.1 创建备份文件

mkdir -p /data/backup

3.2 执行备份

# ./backup_xtrabackup.sh backup
2023-09-22 15:07:26 [Note] 进行备份前预检查
2023-09-22 15:07:26 [Note] 预检查完成
2023-09-22 15:07:26 [Note] 开始清理历史备份
2023-09-22 15:07:26 [Note] 清理历史备份清理完成
2023-09-22 15:07:26 [Note] 2023-09-22 15:07:26 开始进行本地备份
2023-09-22 15:07:41 [Note] 备份[xtra_full_20230922150726.xb]成功
2023-09-22 15:07:41 [Note] 本地备份完成

3.3 设置每日定时备份

# ./backup_xtrabackup.sh addcron
 *****add crontab success***** 
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root

# For details see man 4 crontabs

# Example of job definition:
# .---------------- minute (0 - 59)
# |  .------------- hour (0 - 23)
# |  |  .---------- day of month (1 - 31)
# |  |  |  .------- month (1 - 12) OR jan,feb,mar,apr ...
# |  |  |  |  .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
# |  |  |  |  |
# *  *  *  *  * user-name  command to be executed

# 每天凌晨2点55分执行备份
55 02 * * * root /bin/bash /root/Deploy_MySQL/backup/backup_xtrabackup.sh backup > /data/backup/log/xtra_full_`date '+\%Y\%m\%d\%H\%M\%S'`_script.log 2>&1

定时任务配置在 /etc/crontab 下

mysqldump

修改脚本 backup_mysqldump.sh 内对应配置参数

clone

使用 8.0版本自带的clone插件进行备份,建议版本 8.0.27+

修改配置文件 backup_clone.conf 
执行 backup_clone.sh

恢复

cd recovery

xtrabackup 恢复

1.修改配置文件:

  • full_rec.conf 全量恢复配置文件
  • gtid_rec.conf 基于指定GTID的恢复
  • pos_rec.conf 基于指定POS点的恢复
  • time_rec.conf 基于指定时间点的恢复

2.执行恢复

./xtra_recover.sh 
Usage: bash 
        xtra_recover.sh full     仅全量恢复(配置文件full_rec.conf)
        xtra_recover.sh time     增量恢复到某个时间点(配置文件time_rec.conf)
        xtra_recover.sh pos      增量恢复到某个POS点(配置文件pos_rec.conf)
        xtra_recover.sh gtid     增量恢复到某个GTID(配置文件gtid_rec.conf)

clone 恢复

1.修改配置文件:

  • full_rec.conf 全量恢复配置文件
  • gtid_rec.conf 基于指定GTID的恢复
  • pos_rec.conf 基于指定POS点的恢复
  • time_rec.conf 基于指定时间点的恢复

2.执行恢复

./clone_recover.sh 
Usage: bash 
        clone_recover.sh full     仅全量恢复(配置文件full_rec.conf)
        clone_recover.sh time     增量恢复到某个时间点(配置文件time_rec.conf)
        clone_recover.sh pos      增量恢复到某个POS点(配置文件pos_rec.conf)
        clone_recover.sh gtid     增量恢复到某个GTID(配置文件gtid_rec.conf

误更改数据闪回

1.更改配置信息 vim do_my2sql.sh

host='192.168.60.156'
user='testa'
password='testa@123'
port=3306
database='demo_test'
tables='demo01'
start_binlog_file='mysql-bin.002419'
end_binlog_file='mysql-bin.002420'
start_time='2023-06-27 15:50:00'
end_time='2023-06-27 16:00:00'

2.执行生成执行SQL或回滚SQL

./do_my2sql.sh 

      ./do_my2sql.sh [param] 
        2sql       Previously executed SQL
        rollback   Rollback statements for previously executed SQL

3.整理获取到的SQL进行回滚操作

MySQL版本升级

注意: 1.升级会进行重启 2.如果配置开启了备份原有数据,请注意磁盘空间是否足够 3.不建议跨版本直接升级,若跨版本升级请了解清楚版本差异

# 修改相关配置参数
vim upgrade_mysql.sh

#执行升级操作
./upgrade_mysql.sh

其他处理

添加/删除VIP

1.修改配置文件VIP相关信息 2.执行

# 添加vip
./deploy.sh vip_add

# 删除vip
./deploy.sh vip_del

或可直接执行

# 此脚本无需依赖配置文件信息
## 帮助信息
# ../common/vip_manager.sh 
Usage:  
    ../common/vip_manager.sh  [add/del] [vip] [interface]      添加或删除VIP
    示例:
        添加:../common/vip_manager.sh 10.10.10.111 eth0 add 
        删除:../common/vip_manager.sh 10.10.10.111 eth0 del

备份恢复出来的节点重新加入到集群

在短时间中断的节点,可作为从库加入到集群中去

# ./rejoin_as_slave.sh 
Usage: bash rejoin_as_slave.sh 主节点IP
       如:./rejoin_as_slave.sh 192.168.66.161

检查本机与配置的其他服务器的SSH

./deploy.sh check_ssh

脚本可单独执行

./deploy_master_slave.sh 
Usage:  
    ./deploy_master_slave.sh master                             部署master节点
    ./deploy_master_slave.sh slave                              部署slave节点
    ./deploy_master_slave.sh tobe_slave_with_reset [master_ip]  将当前节点作为从加入到指定主节点上去,注意:会在当前服务器执行 reset master ,仅适合刚安装完成的slave

./install_mysql.sh 
Usage: 单独部署的master/slave,默认开启read_only参数的,需要自行配置read_only与复制rpl_semi_sync_replica_enabled开关
    ./install_mysql.sh [./template/[5.7/8.0]/my.cnf.single]                             部署单机节点 
    ./install_mysql.sh [./template/[5.7/8.0]/my.cnf.master]                             部署master节点
    ./install_mysql.sh [./template/[5.7/8.0]/my.cnf.slave]                              部署slave节点,不会自动建立主从

等...
GNU AFFERO GENERAL PUBLIC LICENSE Version 3, 19 November 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU Affero General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Remote Network Interaction; Use with the GNU General Public License. Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. You should have received a copy of the GNU Affero General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.

简介

一键部署MySQL,支持部署单机、基于VIP的高可用 支持一键备份、恢复、闪回等 展开 收起
Shell
AGPL-3.0
取消

发行版 (5)

全部

贡献者

全部

近期动态

加载更多
不能加载更多了
1
https://gitee.com/dbother/mysql_deploy.git
git@gitee.com:dbother/mysql_deploy.git
dbother
mysql_deploy
MySQLDeploy
master

搜索帮助