Search results

Simply restore using a new VMID (from the backup datastore panel).

Instead, you need to find out the real problem. Why does the VM crash? Any hint in the backup log or syslog?

Also, do you run the latest version of PBS?

All Proxmox VE related services depend on pve-cluster, so there is no single pve service, VM or Container running unless that is up.

SHA is always used, and is not related to encryption (encryption is done using AES).

I don't think that will change anything...

Its not only compression. See the output of "proxmox-backup-client benchmark". For example, SHA256 checksum computation speed is 13% compared to the reference system.

The CPU (Intel Xeon E5-2650L V4) seems to be very slow.

Most likely you have an unstable storage system. What is the output of # pvesm status

3-2-1 backup rule: You should have three total copies, use two different media (disk and tape, usually), and keep one copy offsite (tape). You will be always able to restore the offsite tape.

Again, pmxcfs is not a general purpose file system, and we have bumped the limits where sensible in the past. I suggest that you use a real cluster file system if you run into limits, for example cephfs, ... Plus, we're always interested in improving things. As soon as I have an idea to do...

pmxcfs is not a filesystem used to store arbitrary data. Instead, It is used to store PVE configuration into a transactional database. Each write is atomic and synced to the disk! So please use other filesystems if you want to store large files. pmxcfs is not meant for that, and was never...

yes

Sure, this is a basic feature for any hypervisor: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_migration

Ceph is far superior to these legacy storage technologies. So in short, we do not plan to implement that.

That is explained in the developer documentation: See: http://pve.proxmox.com/wiki/Developer_Documentation

You need to change the ha group from group1 to group2.

PUT /api2/json/storage/{storage} See: https://pve.proxmox.com/pve-docs/api-viewer/index.html#/storage/{storage}

Have you tried to wipe the disk, so that it is empty (no filesystem on it)?

External qcow2 snaphots is when you create a second qcow2 file, which refers to the original as base file. New data is always written to the second file. The base file is read-only. AFAIK ovirt is using this model.