It seems that you've got friendly names because you're using multipath configuration files: /etc/multipath.conf or/and /etc/multipath/bindings
I'm not sure but it can be some issues creating LVM on GPT disk or some issues with LVM filtering.
You could try to remove partitions from disk and...
I think you should do following steps:
In the console of PREF33-S-PMOX1 or PREF33-S-PMOX2:
pvcreate /dev/mapper/3600c0ff0001ae601d4d8b05a01000000
vgcreate vmstore1 /dev/mapper/3600c0ff0001ae601d4d8b05a01000000
In the PVE GUI:
Datacenter --> Storage --> Add --> LVM
Id: your friendly name eg...
I tried to run, but it failed with following errors:
tar: 3367: Child returned status 127
/bin/sh: 1: ./xva_conv.sh: not found
UPDATE: Weird, I changed filename (xva_conv.sh) to the one without "con" and it helped.
Thank you Alessandro - great job!
I mean:
- If you browse backup from vm menu you will see only backups of this vm.
- If you browse contents of storage (VZ dump) device you will see all of backups.
Vasu, your answer is apparently proper one.
What is the point of restoring vm to newly created vm if restoring process can create vm itself? Parameters?
Yeah, your restoring policy is safer but also one step longer.
When you create new virtual machine, you will not see backup of other vm.
The one and only way to restore existing vm (without removing it) to the new one is to restore from nfs storage contents view.
You don't have to remove NIC - change the MAC address only.
Hi Proxmoxers!
Several days ago I've started to test Proxmox VE in order to have some let say balanced alternative to expensive VMware and hardcore virsh-managed KVM environment on the other side. First impression was so promising - very intuitive interface and easy to backup vm capability...