K8s Etcd备份与恢复

kubenetes使用Etcd数据库存储集群中的数据,安全起见,一定要备份.

kubeadm 方式部署:

备份

ETCDCTL_API=3 etcdctl snapshot save /opt/etcd.db \
--endpoints=https://127.0.0.1:2379 \
--cacert=/etc/kubernetes/pki/etcd/ca.crt \
--cert=/etc/kubernetes/pki/etcd/server.crt \
--key=/etc/kubernetes/pki/etcd/server.key

#### 演示:
[root@k8s-master-1 ~]# ETCDCTL_API=3 etcdctl snapshot save /opt/etcd.db \
> --endpoints=https://127.0.0.1:2379 \
> --cacert=/etc/kubernetes/pki/etcd/ca.crt \
> --cert=/etc/kubernetes/pki/etcd/server.crt \
> --key=/etc/kubernetes/pki/etcd/server.key
Snapshot saved at /opt/etcd.db

恢复

# 1 先暂停kube-apiserver和etcd容器:
mv /etc/kubernetes/manifests /etc/kubernetes/manifests.bak
mv /var/lib/etcd /var/lib/etcd.bak

# 2 恢复etcd数据
ETCDCTL_API=3 etcdctl snapshot restore \
/opt/etcd.db --data-dir=/var/lib/etcd 

# 3 启动kube-apiserver 和 etcd容器:
mv /etc/kubernetes/manifests.bak /etc/kubernetes/manifests


#### 演示:
[root@k8s-master-1 ~]# mv /etc/kubernetes/manifests /etc/kubernetes/manifests.bak
[root@k8s-master-1 ~]# mv /var/lib/etcd /var/lib/etcd.bak

[root@k8s-master-1 ~]# ETCDCTL_API=3 etcdctl snapshot restore /opt/etcd.db \
--data-dir=/var/lib/etcd 
2023-01-18 07:01:42.935583 I | mvcc: restore compact to 7026586
2023-01-18 07:01:42.942566 I | etcdserver/membership: added member 8e9e05c52164694d [http://localhost:2380] to cluster cdf818194e3a8c32

[root@k8s-master-1 ~]# mv /etc/kubernetes/manifests.bak /etc/kubernetes/manifests

验证

#### 验证(等待一会儿让容器启动):
[root@k8s-master-1 ~]# kubectl get node,deployment,svc,pod -o wide
NAME                STATUS   ROLES           AGE   VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION           CONTAINER-RUNTIME
node/k8s-master-1   Ready    control-plane   55d   v1.25.1   192.168.3.101   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.21
node/k8s-node-1     Ready    <none>          55d   v1.25.1   192.168.3.104   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.21
node/k8s-node-2     Ready    <none>          55d   v1.25.1   192.168.3.105   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.21
node/k8s-node-3     Ready    <none>          55d   v1.25.1   192.168.3.106   <none>        CentOS Linux 7 (Core)   3.10.0-1160.el7.x86_64   docker://20.10.21

NAME                      READY   UP-TO-DATE   AVAILABLE   AGE   CONTAINERS                          IMAGES                                              SELECTOR
deployment.apps/counter   3/3     3            3           21d   count,count-log-1,count-log-2,ngs   busybox:1.28,busybox:1.28,busybox:1.28,nginx:1.17   app=ng
deployment.apps/www       1/1     1            1           43m   nginx                               nginx                                               app=www

NAME                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)           AGE   SELECTOR
service/counter      NodePort    10.104.53.36     <none>        80:31946/TCP      21d   app=ng
service/java-demo    NodePort    10.97.29.88      <none>        8080:32390/TCP    45d   app=java-demo
service/kubernetes   ClusterIP   10.96.0.1        <none>        443/TCP           55d   <none>
service/memcached    NodePort    10.98.147.155    <none>        11211:32466/TCP   24d   app_env_stage=dev
service/nginx-d      NodePort    10.104.101.166   <none>        80:30280/TCP      24d   app_env_stage=dev
service/redis        NodePort    10.111.151.222   <none>        6379:32040/TCP    24d   app_env_stage=dev

NAME                           READY   STATUS    RESTARTS   AGE     IP               NODE         NOMINATED NODE   READINESS GATES
pod/counter-765fd887f9-4m9ml   4/4     Running   0          12d     10.244.140.104   k8s-node-2   <none>           <none>
pod/counter-765fd887f9-5qkz2   4/4     Running   0          7d22h   10.244.140.110   k8s-node-2   <none>           <none>
pod/counter-765fd887f9-qjlwz   4/4     Running   0          12d     10.244.140.106   k8s-node-2   <none>           <none>
pod/www-7d6cb45fbb-9zk2r       1/1     Running   0          43m     10.244.109.115   k8s-node-1   <none>           <none>
回答: 对于k8s etcd备份恢复,可以按照以下步骤进行操作。首先,确保已经有了备份文件。可以使用以下命令检查备份文件是否存在:\[1\] 如果备份文件不存在,则需要重新执行备份命令并输入正确的备份文件时间。接下来,可以使用etcdctl命令进行备份恢复。根据备份文件的位置和名称,使用以下命令进行恢复:\[3\] ``` ETCDCTL_API=3 etcdctl snapshot restore /path/to/etcd-snapshot.db \ --data-dir /path/to/etcd-data-dir \ --initial-cluster <etcd-cluster-endpoints> \ --initial-cluster-token <cluster-token> \ --initial-advertise-peer-urls <peer-urls> ``` 其中,`/path/to/etcd-snapshot.db`是备份文件的路径和名称,`/path/to/etcd-data-dir`是etcd数据目录的路径,`<etcd-cluster-endpoints>`是etcd集群的节点地址,`<cluster-token>`是集群的令牌,`<peer-urls>`是etcd节点的URL。根据实际情况替换这些参数。执行命令后,etcd将使用备份文件恢复数据到指定的数据目录。 需要注意的是,恢复过程可能需要一些时间,具体时间取决于备份文件的大小和系统性能。恢复完成后,可以启动etcd集群并验证数据是否成功恢复。 请注意,备份恢复是一个敏感的操作,务必谨慎执行,并确保备份文件的完整性和可用性。在执行恢复操作之前,建议先进行测试和验证,以确保备份文件可用并且可以成功恢复数据。 希望以上信息对您有所帮助。如果还有其他问题,请随时提问。 #### 引用[.reference_title] - *1* [k8s etcd 备份恢复](https://blog.youkuaiyun.com/liudongyang123/article/details/124145618)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^insertT0,239^v3^insert_chatgpt"}} ] [.reference_item] - *2* *3* [KubernetesETCD集群备份恢复](https://blog.youkuaiyun.com/heian_99/article/details/123398209)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v91^insertT0,239^v3^insert_chatgpt"}} ] [.reference_item] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值