Chinaunix首页 | 论坛 | 博客

x86

  • 博客访问: 61451
  • 博文数量: 14
  • 博客积分: 10
  • 博客等级: 民兵
  • 技术积分: 140
  • 用 户 组: 普通用户
  • 注册时间: 2011-01-28 14:12
个人简介

虚拟化和分布式文件系统交流群239539006

文章分类

全部博文(14)

文章存档

2015年(14)

我的朋友

分类: 虚拟化

2015-04-23 23:00:08


Recovery

If you have major problems with your Proxmox VE host, e.g. hardware issues, it could be helpful to just copy the pmxcfs database file /var/lib/pve-cluster/config.db and move it to a new Proxmox VE host. On the new host (with nothing running), you need to stop the pve-cluster service and replace the config.db file (needed permissions : 600). Second, adapt /etc/hostname and /etc/hosts according to the lost Proxmox VE host, then reboot and check. (And don?t forget your VM/CT data)

Remove Cluster configuration

The recommended way is to reinstall the node after you removed it from your cluster. This makes sure that all secret cluster/ssh keys and any shared configuration data is destroyed.

I some cases, you might prefer to put a node back to local mode without reinstall, which is described here:

  • stop the cluster file system in /etc/pve/
# service pve-cluster stop
  • start it again but forcing local mode
# pmxcfs -l
  • remove the cluster config
# rm /etc/pve/cluster.conf
# rm /etc/cluster/cluster.conf
# rm /var/lib/pve-cluster/corosync.authkey
  • stop the cluster file system again
# service pve-cluster stop
  • restart pve services (or reboot)
# service pve-cluster start
# service pvedaemon restart
# service pveproxy restart
# service pvestatd restart
阅读(1818) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~