Search results

When using a "classic" .vma backup from the same VM, restore to the same Ceph storage works fine. So the problem is definitly PBS related here in some way. So that is the sitation (all with the same VM): Backup VM with PBS and restore to Ceph: FS broken Backup VM with PBS and restore to...

Hi @tom What do you want to know exactly? It's a separate Ceph cluster (not running on the PVE nodes) running this version: > ceph version 15.2.8 (bdf3eebcd22d7d0b3dd4d5501bee5bac354d5b55) octopus (stable)

Figured it out: When restoring any VM to Ceph storage, the FS is broken. When restoring to local disk it's fine. So it seems to be a problem with the restore from PBS to Ceph storage!

Storage is Ceph in this case. Will test with local storage also now.

Sure: Feb 16 17:36:03 vs5480 qemu-ga[842]: info: guest-fsfreeze called Feb 16 17:36:03 vs5480 host qemu-ga[842]: info: executing fsfreeze hook with arg 'freeze' Feb 16 17:36:03 vs5480 qemu-ga[842]: info: executing fsfreeze hook with arg 'thaw'

As mentioned in the first post, yes. You can also see this in the logs provided earlier: INFO: issuing guest-agent 'fs-freeze' command INFO: enabling encryption INFO: issuing guest-agent 'fs-thaw' command

FYI: Same happens with CentOS 8 when using ext4! @danielb Are you using LVM (we do)?

Backup: INFO: starting new backup job: vzdump 5480 --storage snap03 --mode snapshot --node hav301 --remove 0 INFO: Starting Backup of VM 5480 (qemu) INFO: Backup started at 2021-02-16 17:36:02 INFO: status = running INFO: VM Name: vs5480 INFO: include disk 'scsi0' 'ceph-vs:vm-5480-disk-0' 100G...

Ok, tested further: It does not depend or encryption or anything else. Even the first backup with PBS from a fresh deployed VM is broken after restore here with XFS :(

Maybe this is the cause, because on our site PVE does this? Will do some more tests.

Ok, thanks! Which backup-settings did you use? Any special settings or something? Encryption? We let PVE prune old backups and not PBS, maybe this causes a problem here? Did you try restores also from "incremental" backups? We're also using EL8.

Hello, we're currently testing PBS with PVE. Backups works so far, but when restoring VMs with XFS the VM is unbootable (see attached image) and always needs a xfs_repair in rescue. This is reproducible with different VMs and backups. With ext4 its fine and without errors. The backup setting...

I've replaced the implementation of fill_with_random_data with getrandom::getrandom - which provides an abstraction for getrandom(2) on Linux. However we have no Rust experience in-house so the patch might not be optimal, esp. regarding return value usage. With this change proxmox-backup-client...

Hi, we're currently in the process of trying to build proxmox-backup-client for CentOS 7 to evaluate and test the pbs beta. We've worked through some build strategies and are currently trying a dynamically linked binary (glibc, libacl, libfuse3 etc.) w/ statically linked OpenSSL 1.1 which -...

Libssl seems to be a problem, also libc - here the output from CentOS 7: # ldd proxmox-backup-client pxar | grep -e 'not' -e : proxmox-backup-client: . /proxmox-backup-client: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by ./proxmox-backup-client) ./proxmox-backup-client...

Thanks, you help is much appreciated. We failed to build the proxmox-backup from source (error[E0433]: failed to resolve: use of undeclared type or module ), so the static binary is our last hope for testing PSB with our servers running all CentOS ;-)

Thomas, this seems not to be the case - I've tested with the .deb from http://download.proxmox.com/debian/pbs/dists/buster/pbstest/binary-amd64/ and its dynamic linked. Do you have any ETA for the static binary?

Again: If the problem only exists within knet, why don't you use udpu instead?

Has anoyone here tried to use "udpu" instead of "knet" with Corosync3?

From where do you get this information? Normally, this should have a default value in seconds in QEMU.