Search results

Right, just set Discard = True.

Datacenter Datacenter > Backup: Used for create a Backup Schedule for selected or all VMs. Since you just need to backup 1 VM then use Node > VM > Backup instead. Also VM > Backup > Snapshot = make a FULL BACKUP for File System that support Snapshot feature.

Suggestion for PDM: We now can see the remote node IPs, better if we can add some note, like: - 10.10.10.2 (automatically get the Hostname or extra text)

I have not clear about this: Should I use Dataset or just create a new Folder inside mounted pool? When we need is_mountpoint option? NB: The backup feature in this case only for faster migration purpose, of course backup server was used.

Suggestion for PDM: By default PDM Migrate "Delete Source" is True. I think better set it to False. So any VPS that can not run correctly in new server still has its original VPS.

Hi Johannes, I think you misunderstanding the issue. Proxmox DM now already support PVE 6 (except PVE 5 because has no Token feature, so I agree with you to ignore this PVE 5 version), you can see PDM has option to use manual API Token in this case, what is missing is: Migration feature. Another...

Thanks for best effort to release PVE 9. But ... ZFS still not able to store backup files, we must manually add "is_mountpoint" option to storage.cfg. Will you add this option to the GUI?

If you manually install Debian and Proxmox, the you can choose certain partition.

Because we need PDM to make migration to PVE 8 easier. Updating to PVE 5/6/7 to 8 sometime is not an option, sometime better to install PVE 8/9 from scratch then migrate old VM, at least in my case :) Currently, I must manually backup, copy to new server, then restore it.

If "is_mountpoint yes" then error: unable to activate storage 'local-backup' - directory is expected to be a mount point but is not mounted: '/local-data/backup' (500) If I remove "is_mountpoint" option then error gone. NB: hope this feature, use ZFS as a backup available in Proxmox by...

Hope PDM also support PVE 7. We can Start and Stop VM, but PVE 7 Migration still error: api error (status = 400: api returned unexpected data - failed to parse api response) This will very useful since I have many PVE 6 and 7 which allready has API Token feature.

There are no reason to disable it in the GUI while a CLI able to do it. The security reason has no impact while using a mounting disk as NFS share to create a CT/VM, because Permisions/ACL inside the CT/VM storage.

We can mount a disk to CT using CLI like this: pct set 100 -mp0 /mnt/mydisk,mp=/mydisk But why this feature not available on GUI?

I know this is old thread but show up when googling about nfs error. The solution is enable NFS features in CT - Options - Features. In my case I enable all Features except "Create Device Nodes (experimental)" feature. I am using Priviledged Container.

To change expected value another node must be off/shutdown. Since you still have 2 node then when you reboot qdevice then nodes will not reboot. Proxmox still run well with 2 nodes because minimum quorum is 2, but when 1 node fail then you lost the Cluster.

Doing so for ../hooks/fsck and voila the apt update finally working, thanks!

# dpkg -l initramfs-tools root@poweredge:~# dpkg -l initramfs-tools Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture...

Just enable ceph-quincy repo update then run apt upgrade again: root@poweredge:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 5 not fully...

There is no .../hooks/btrfs file root@poweredge:~# ls /usr/share/initramfs-tools/hooks/ dmsetup fsck fuse iscsi keymap klibc-utils kmod lvm2 ntfs_3g resume thermal thin-provisioning-tools udev xfs zdev zfs zfsunlock zz-busybox root@poweredge:~#

No, just use EXT4 for Proxmox OS. root@poweredge:~# lsblk -fs NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT loop0 ext4 1.0 50a8034e-47b5-4b3e-acf1-2df78b321e15 loop1 ext4 1.0...