Hello,
I have a VM which need drastically different backup retention. Is there currently a good way to setup retention per VM?
I found some old threads (~2 year old) regarding this but it looked like this feature was not implemented. I guess one can leverage namespaces feature to workaround...
When I migrate a machine, the backups for that machine is left on the local storage of the source node. How can one migrate the backups to the target node also?
Thanks, I have set votes of pve1 to 2. Things seem to be fine so far :)
If I can't login to pve2 when it is only node up, I can set expected to 1 manually with SSH.
I am still curious about what will happen when pve2 comes up after adding more VMs to pve1. I will assume that pve2 will get...
In a 2 node cluster, is it possible to shutdown one of the nodes to conserve energy without having quorum issues?
I have setup the nodes so that they can wake up with the WOL packet.
The problem is that when one node is off, the other does not accept changes anymore due to quorum.
I checked...
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...
Yes, there is no problem if I consciously do not use same VMID ever again. But human errors occur.
But it does not quite answer my question. I was wondering if any steps are taken to eventually solve this problem to some degree? Eg. is there a bug report, issue ticket or similar? Is it on...
I have found several posts related to this. For example:
https://forum.proxmox.com/threads/questions-about-backup-names-and-vm-ids.24813/
https://lists.proxmox.com/pipermail/pve-devel/2018-April/031526.html
It feels strange that backups are shared between a deleted machine and a new one which...
Dec 15 01:30:48 blah systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Dec 15 01:30:49 blah networkd-dispatcher[114]: No valid path found for iwconfig
Dec 15 01:30:49 blah networkd-dispatcher[114]: No valid path found for iw
Dec 15 01:30:49...
I am using Proxmox 7.1 and Ubuntu 20.04 in the CT
I found: https://forum.proxmox.com/threads/ubuntu-snaps-inside-lxc-container-on-proxmox.36463/#post-230060
and I have installed LXD in Proxmox CT. It mostly seems to work fine.
But the services do not completely start with Ubuntu 20.04 CT...
In meantime I found this blog entry:
https://lucatnt.com/2020/05/grub-unknown-filesystem-on-zfs-based-proxmox/
But I couldn't get it to work with zstd_compression....
@avw thanks, it is a good idea. Although I re-installed the effected machine with RAID1(adm) and EXT4 on it.
But I tried to test your idea in a VM now. There is an EFI partition of size 512MB created by proxmox installer. I converted that partition into EXT4 but grub-install still was saying...
SSDs can be just be easily slided into the SFF slots on this machine if needed and this problem was not related to SSD/HDD. So I do not understand your point. But.. like I said, there iis no point in arguing abut this. I agreed already that with BIOS, the /boot in ZFS seems to be a bad idea...
@tom I do not want to start an argument but your comment is not productive. The hardware did not fail and a hardware is not "totally outdated" because it does not support UEFI. It is a backup server, it should not have to be latest high end machine either.
Yes sure, I was trying to re-purpose...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.