Search results

You used the same namespace?

Only directory based storages using a file system support .qow2 or .vmdk You can't, because it make no real sense. Those storage types are there because they already provide snapshots/clones in a more efficient way.

You need a quorate cluster.

Sorry, we still have no plans to support DVD burners.

You first create one bridge for each NIC. Then simply assign the corresponding NIC/bridge to the VM, and configure the IP and gateway inside the VM.

Dafür gibts ja das enterprise repository.

Sorry, but my previous answer was totally wrong. For Containers, we read the values from /sys/fs/cgroup/CTID/ (memory.stat and memory.current). This is because container memory is limited by the cgroup kernel system. Tools like "free" or "btop" use kernel syscalls, which simple return the...

Man kann aber schauen ob die "agent" property in der vm config gesetzt ist.

Please test again with the current version. It should work without problems.

This is not true. Proxmox backup use a special qemu feature to make snapshots (copy before write), and this is storage independent, i.e. it also works on NFS/raw.

Sorry, but that sounds strange. What problem do you have exactly?

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