Fresh VE cluster installation, backup restore doesn't work

[Kimmo H]

Hi,
coming from xenserver and testing proxmox, i installed two proxmox VE 5.3-8 servers, made cluster of them, added remote NFS to share backup, made backup of VM 101 from cluster node 1 and try to restore it to cluster node 2 with this error.

Servers and NFS are in same network. Did i do something wrong ? I didn't find any mention @ documentation that i should make some group ?

----------------
restore vma archive: lzop -d -c /mnt/pve/backups/dump/vzdump-qemu-101-2019_03_25-10_17_33.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp19756.fifo - /var/tmp/vzdumptmp19756
CFG: size: 361 name: qemu-server.conf
CFG: size: 236 name: qemu-server.fw
DEV: dev_id=1 size: 137438953472 devname: drive-scsi0
CTIME: Mon Mar 25 10:17:34 2019
no lock found trying to remove 'create' lock
TASK ERROR: command 'set -o pipefail && lzop -d -c /mnt/pve/backups/dump/vzdump-qemu-101-2019_03_25-10_17_33.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp19756.fifo - /var/tmp/vzdumptmp19756' failed: no such volume group 'pve'
------------------

 

[Chris]

Hi,
can you please post the storage config as well as the config of the VM? `cat /etc/pve/storage.cfg` and `qm config VMID`. It seems that you have no VG named pve on node 2? What is the output of `vgs`?

 

[Kimmo H]

I used only GUI to do everything, but here:

root@px-ve1:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content backup,vztmpl,iso

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

nfs: backups
export /USBDisk1
path /mnt/pve/backups
server nfs1.XXXXX.fi
content backup
maxfiles 1
options vers=3

nfs: iso-images
export /NFS
path /mnt/pve/iso-images
server nfs1.XXXXXX.fi
content iso
options vers=3

root@px-ve1:~#

-------------------------------------------------

root@px-ve1:~# qm config 101
bootdisk: scsi0
cores: 1
ide2: none,media=cdrom
memory: 4096
name: web4.XXXXX.fi
net0: virtio=4E:E2:CD:6E:EA:7E,bridge=vmbr0
numa: 0
ostype: l26
scsi0: local-lvm:vm-101-disk-0,size=128G
scsihw: virtio-scsi-pci
smbios1: uuid=deefb6f6-0ccc-4c91-a561-3379c2cfdf86
sockets: 2
vmgenid: b313571c-6530-4b4a-baa9-8776f98a5d9d
root@px-ve1:~#

-------------------------------------------------------

root@px-ve1:~# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 5 0 wz--n- 930.98g 15.99g
root@px-ve1:~#

 

[Chris]

What about the vgs/lvs on node 2?

 

[Kimmo H]

Note, these both servers have VM's at local disks, Just Backup .lzo files and .iso images are shared via NFS.

root@px-ve2:~# cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content backup,vztmpl,iso

lvmthin: local-lvm
thinpool data
vgname pve
content images,rootdir

nfs: backups
export /USBDisk1
path /mnt/pve/backups
server nfs1-XXXXX.fi
content backup
maxfiles 1
options vers=3

nfs: iso-images
export /NFS
path /mnt/pve/iso-images
server nfs1.XXXXX.fi
content iso
options vers=3

root@px-ve2:~#

-------------------------------------------

root@px-ve2:~# qm config 101
Configuration file 'nodes/px-ve2/qemu-server/101.conf' does not exist
root@px-ve2:~#

-------------------------------------------

root@px-ve2:~# vgs
VG #PV #LV #SN Attr VSize VFree
lisalevy 1 0 0 wz--n- 3.64t 3.64t
root@px-ve2:~#

-------------------------------------------

root@px-ve2:~# lvs
root@px-ve2:~#

 

[Chris]

You have no VG named 'pve' on node 2. As you try to restore the VM presumably to the local-lvm, it expects the VG 'pve' to be present as declared in the config. Did you change the LVs on node 2?
You can try to specify a different storage with `qmrestore <archive> <vmid> --storage <string>`. If you do not pass the string, it will try to restore to the default storage, which in your case does not exist on node 2.

 

[Kimmo H]

Yes problem solved and learned.

OK, so when building clusters it would be wise to have same kind of hardware with same kind of installation (here first server was from proxmox .iso , second was thru debian9 + proxmox apt repositories.

You can close this.