if you press the shutdown button via proxmox gui it will shut down and stay turned off, however if it is done via the guest OS it will turn back on (with HA enabled) - i also noticed this coming from vmware and its annoying, proxmox has some...
just to add a bit of context and hopefully make things a bit more clear for future readers
not quite - the output comes from listing the entry in the `debian/NEWS` file from the Debian Upstream zfs-linux source package...
and the retention settings
The only write once read many (WORM) I know are the identically named LTO tapes. As long as you secure your PBS properly, e.g. not attaching it to any AD/LDAP/OID to keep the attach surface small, you're safe. PBS acts...
That's the idea of replication, isn't it? If you migrate the vm, the replication direction is turned around, meaning the node owning the vm replicates the disks to the other one.
before migration: node1 -> node2
after migration: node2 -> node1...
Hey guys!
I'm still getting used to Proxmox, but so far it's been amazing!
Since I'm still getting hands-on learning about the product, naturally I've been playing around with storage configurations. I've created some lvm/lvm-thin volume...
Yes, PBS uses this technique, Veeam implemented it's own. Therefore you need the worker VMs. Hoepfully they'll adapt to the correct API PVE provides in order to have a better integration.
Yes, I believe you should simply be able to rename it in the config by editing both the remotes.cfg and remotes.shadow manually.
Regarding the lock file: this file is in place to get "locked", it is an empty file which tells other...
One can change settings ahead of time. PVE shows that unapplied setting in orange as I recall, in the hardware settings page.
If one restarts the OS inside the VM, the VM "hardware" doesn't ever stop, so PVE never applies the change. The...
Aren't there any parameters of a VM hosted by a PVE (I mean parameters not inside of VM's OS) which require stopping the VM first?
For instance, at least in Vmware, when you need to disable Secure Boot in EFI boot settings, the VM must be shut...
That's the idea of replication, isn't it? If you migrate the vm, the replication direction is turned around, meaning the node owning the vm replicates the disks to the other one.
before migration: node1 -> node2
after migration: node2 -> node1...
Thanks for testing it out and for the additional info. :)
Right now, I'm testing it with a single Remote that contains a single node, so there's not really an alternative path to a second node if the first one becomes unreachable. I have...
Moving the config file doesn't stop the VM; nothing watches /etc/pve and kills a running kvm process when its config moves away. All you've changed is which node PVE thinks owns the guest, so the process on vm1 carries on running and writing to...
Thats what it should do if the vm is configured for HA (HA replicates the vm disks from PVE node vm0 to PVE node vm1 with ZFS replicas) if you migrate a vm to different PVE node the replication is automaticaly reversed and it replicates from PVE...
and the retention settings
The only write once read many (WORM) I know are the identically named LTO tapes. As long as you secure your PBS properly, e.g. not attaching it to any AD/LDAP/OID to keep the attach surface small, you're safe. PBS acts...
One thing that may happen during the first 30 minutes is that caches are warmed up, ARC may fill, other processes start and consume memory.
Let memtest86+ run for multiple rounds, at least over night - or longer.
Yes, PBS uses this technique, Veeam implemented it's own. Therefore you need the worker VMs. Hoepfully they'll adapt to the correct API PVE provides in order to have a better integration.
and the retention settings
The only write once read many (WORM) I know are the identically named LTO tapes. As long as you secure your PBS properly, e.g. not attaching it to any AD/LDAP/OID to keep the attach surface small, you're safe. PBS acts...