meta data for this page
  •  
Book Creator
 Add this page to your book
Book Creator
 Remove this page from your book  

 Manage book(0 page(s))
 Help

This is an old revision of the document!

Disaster recovery

Migrate VM from dead node

Simply move config file: 

mv ./nodes/pve3/qemu-server/366.conf ./nodes/pve5/qemu-server/

If move is not possible (no quorum in cluster), simply reduce expected votes to 1: 

pvecm e 1

Transfer needed storage. From source storage node pve3 send volume to pve5: 

zfs send rpool2/data/vm-366-disk-0 | ssh pve5 zfs recv -d rpool
zfs send rpool2/data/vm-366-disk-2 | ssh pve5 zfs recv -d rpool

reinstall node

Install fresh Proxmox. Create common cluster-wide mountpoints to local storage. Try to join to cluster. From existing node pve5 add new node 192.168.28.233: 

root@pve5:~# pvecm add 192.168.28.233
 
Please enter superuser (root) password for '192.168.28.233': ************
detected the following error(s):
* authentication key '/etc/corosync/authkey' already exists
* cluster config '/etc/pve/corosync.conf' already exists
* this host already contains virtual guests
* corosync is already running, is this node already in a cluster?!
Check if node may join a cluster failed!