name

Hello, newbie here. Excited to learn more about Proxmox. So! Hey, I get it, you guys are xNIX guys and you love to number things and "that's just the way it is." I get it, I do. But... My company is about to dump VMware due to all Broadcom's changes, but I'm sorry guys, there's no way in hell...

Hi, I'm wondering if there is a way to give backups more readable names? In deafault the have type/id - thats all. I know i can use comments but the comment is just visible when i expand a backup by the plus icon. When i do have there many backups, i am searching a while to find the backup...

I was wondering if this feature was ever implemented? Because I could not find it? https://forum.proxmox.com/threads/feature-request-enable-aliases-for-vlans.4213/ While entering the number directly works fine. It would be much nicer to be able to select from a predefined list. It could even be...

Hello, We have a backup schedule for PBS that run at 23:00 EST everyday. The issue we have is that the naming scheme for the snapshot seems to be built using a different timezone. An exemple would be if we backup a VM the 21 of May at 23:00 EST, the snapshot name would be 22 of May 3:00 This...

Hello. For example, I have 3 containers are logically belongs to one service "service1". Proxmox create all disk at root zfs storage, so it looks like this: mega/subvol-100-disk-0 mega/subvol-101-disk-0 mega/subvol-102-disk-0 I want to see them this way: mega/service1/subvol-100-disk-0...

Hey all, I have been running a somewhat complex network setup on my server for some time: 2x Copper Gigabit Ethernet on Server Board 4x Copper Gigabit Ethernet (Intel 4x PRO/1000 NIC) 1x 10GBaseT Intel 82598EB I'm not going to go into the details of what they are used for, as it is not...

I have an idea for an enhancement of vzdump: when creating a backup job, it would be great to have an option to store the guest's NAME in the backup filename (in addition to the VM ID). So with the option disabled the filenames would look unchanged: vzdump-qemu-240-2016_09_02-01_27_32.log...