Search results

Proxmox Backup server just reads and writes data (It is not particularly bad to your drives) ...

Ja, das ist möglich und stabil.

What exactly is the problem? The picture only shows that you started in Debug mode ...

Our software is licensed as AGPLv3, so you need to tell your users what software it is, and provide a download option: See: https://www.gnu.org/licenses/agpl-3.0.html

That is up to you. But we always suggest to verify backups, and do regular restore tests.

There are two setting to optimize that: - Skip verified snapshots: Only verify new snapshots - Re-verify after X days: But reverify after X days

Da geht ganz sicher nicht (2 VM die gleichzeitig die gleiche Ressourcen verwenden). Außerdem ist der Zustand der kopierten VM anders als der der orginalen VM, d.h. du bist maximal inkonsistent!

The repository looks wrong ("root@pam@192.168.0.101:/test"). This should be without slash: "root@pam@192.168.0.101:test"

Mit einen richtigen benchmark Programm, z.B. fio

Mit diesem test schreibst du in den page cache (RAM), d.h. du testest nicht die festplatte!

Seems your disks are simply very slow...

Please note that each VM has a NAME, and you can change the name as you want. Exactly. The ID is used to uniquely identify the VM. Changing the ID would be counter productive, because you them have multiple ID for the same VM over time. This is not a basic task. Instead, this is something you...

Snapshots verbrauchen auch storage ...

You can use the command line tools to list/view the task logs (on the backup server), see: # proxmox-backup-manager help task Also, may I ask what kind of backup storage do you use? Your tape backup speed seems a bit too low (should be above 150 MB/s).

No, there are currently no plans to do that.

Maybe you run out of memory?

We now have "qm importovf", see # qm help importovf

I habe bereits einen fix für das problem hochgeladen: https://git.proxmox.com/?p=proxmox-backup.git;a=commitdiff;h=b44483a85332b555c7dc2dc4582ee084dc078f0d D.h. in der nächsten release ist das problem gelöst.

This is a text field, and you can add arbitrary text there - not limited to the values in the list.

You need to use the 'pct' command to manage containers (not 'qm') # pct unlock 104