Search results

I have a second PVE server that also has PBS (1.0.8) installed. This second server shall backup the VMs/CTs from the first one. Most of the disk space is in LVM-thin as this will be used for VMs. Is it possible to use lvm-thin as a datastorage? I don't know what kind of information would be...

Sure, no problem. I understand that =) temp-pbs:~# ll /dev/loop* ls: cannot access '/dev/loop*': No such file or directory temp-pbs:~# temp-pbs:~# cat /boot/config-$(uname -r) | grep DEV_LOOP cat: /boot/config-5.4.98-1-pve: No such file or directory temp-pbs:~# lsmod | grep loop temp-pbs:~#...

There is no such device in my VM. Should I still open a bug report?

proxmox-backup-client catalog dump vm/104/2021-02-23T13:45:03Z --repository root@pam@localhost:8007:mydatastore You're correct. The documentation seems to be missing that part. I was able to get this working (had to install ntfs-3g): proxmox-backup-client list --repository...

Hello, I understand that it is possible to restore a single file from a backup when using the proxmox-backup-client but not when using PVE/PBS, is that correct? Tried the following ways and had the following problems: 1) https://pbs.proxmox.com/docs/backup-client.html#restoring-data Error...

Not sure if this is related: "Configuration > Network Interfaces" line 10: unable to parse netmask '255.255.255.255' - invalid digit found in string

Sounds like this problem: https://forum.proxmox.com/threads/again-proxmox-backup-server-doesnt-accept-connection-after-install-reboot.79449

I recently installed PBS 1.0-8 (via apt; Debian Buster) in a testing VM on a PVE host, and noticed that my network was gone as ifupdown2 was being installed. Could login via noVNC console and "ifup eth0". No problem with connecting to the GUI afterwards. Today, I installed PBS on an external...

Yes, but I meant the underlying problem. This is just a workaround, but still copying e.g. 300 GB when only 5 GB would be needed.

Any solution to this problem, yet?

Thanks a lot! For documentation in case anyone else needs this: lvcreate -V 1T --thin -n backup pve/data && \ mkdir -p /mnt/backup && \ mkfs.ext4 /dev/pve/backup cat <<EOF > /etc/systemd/system/mnt-backup.mount [Unit] Description=Thin-volume for Proxmox-Backup [Mount] What=/dev/pve/backup...

I have now created the thin-volume and it's mounted via systemd, but when I want to "Create: Directory" I get "No Disks unused".

Hello, as far as I understand from other threads (https://forum.proxmox.com/threads/resizing-pve-data.30506/ and https://forum.proxmox.com/threads/reduce-local-lvm-pve-data-and-extend-root.48499/), it is not possible to shrink a lvm-thin volume. As those threads are quite old, I wonder if this...

I have now added a second disk on lvm-thin and migrated the old disk with PartedMagic/Clonezilla.

Problem persists with Proxmox 6.2-4. Any ideas?

Did this while the migration was at 7% (still running right now). Didn't produce any output. Should it? Edit: Still getting the same error: WARNING: Device /dev/dm-6 not initialized in udev database even after waiting 10000000 microseconds. Logical volume "vm-108-disk-0" successfully...

I have a VM that is using a local qcow2 disk (virtual 465 GB, physical 55 GB) that is stored on a local directory (100 GB). The VM has recently been migrated from another node to the new, second node in a cluster. It's running fine, only the disk needs to be moved to a lvmthin storage (7 TB)...

Will open another thread for the last problem as the original thread topic has been resolved with comment #7

Migration was fine, but I get an error when I try to "Move disk" to switch from local storage to lvmthin (using GUI on first node; VM is on second node): Virtual Environment 6.1-8 Search Virtual Machine 108 (atl) on node 'atl-vm03' Server View () scsi0 lvmthin Raw disk image (raw) create full...

Would I start this migration on a specific node?