Recent content by UdoB

Im Datacenter --> Backup ist rechts oben ein Button, der den "Schedule Simulator" bereitstellt. Damit zu experimentieren lohnt sich! In der Dokumentation gilt wohl: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvesr_schedule_format_examples

It would be a temporary extension. Basically it is exactly the same what "replace" does if the old drive is still connected, just more "manually". $ man zpool-replace DESCRIPTION Replaces device with new-device. This is equivalent to attaching new-device, waiting for it to resilver, and...

Well, it includes the additional (possibly important!) steps for a boot device. Of course you don't need to execute those for a pure data pool ;-) There are just much too many optional steps to include all of of them in the official reference documentation. For example you want to "6. Wipe the...

Official documentation: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_zfs_change_failed_dev

I do not use SDN, so I can not help. For "risky" experiments (originally with Ceph, in my case) I've setup a virtual PVE cluster. Inside that cluster one can run dangerous experiments without the fear to destroy something important - just create a snapshot of the "hosts" in beforehand :-)

See also: https://pve.proxmox.com/pve-docs/chapter-pvesm.html#_storage_types for a top level overview.

"not allowed" sounds like an access-right problem. Examine that chunk on the destination. You may move it away (this means to create a backup of it and then eliminate the problematic chunk) and repeat your attempt to backup #103 Re-verify that the user "backup" on the PBS has full access...

Sure. That approach is called a mesh: https://pve.proxmox.com/wiki/Full_Mesh_Network_for_Ceph_Server#Example I do not use it, nowhere. You cannot expand it easily: to add a fourth member you would need to utilize a third NIC on each node. After setup you can test it, a simple "ping" from each...

Look at Datacenter --> HA --> Affinity Rules --> HA Node Affinity Rules. Read about the "Strict" flag shown there. Probably you can create two rules, one with the AMD nodes and one with the Intel nodes. Select the VMs to be "in" the corresponding Affinity Rule.

Du meinst damit die virtuelle Platte des Betriebssystem und den Speicherort der Chunks? Ich habe zwei Synology-Kisten. Eine hat nur ein einziges riesiges Volume und eine hat acht oder neun. Mehre Volumes hatte ich angelegt, weil ich die Eigenschaften einzeln managen wollte. Bei mir zeigt sich...

No, that's definitely the wrong tool for your task. If you want to use a supported method with a GUI you may look at https://pdm.proxmox.com/docs/ - you can connect multiple PVE installations with this. As I am not using that one, I can only guess: PDM should be able to clone/copy a VM from...

Jedes Backupsystem, welches unabhängig vom PVE (egal, ob Cluster oder nicht) funktionsfähig ist, ist gut. Ich habe ebenfalls eine PBS-VM in einer Synology, neben mehreren echten PBS. Mir war damals nicht klar, ob ich (für den Chunk-Store) eine virtuelle Platte mit fixer Größe haben wollen...

You can set "expected N" as soon as only N nodes are left up and running. I prefer to do it step-by-step: shutdown node 6 and then pvecm expected 5; shudown node 5, pvecm expected 4; shutdown node 4, pvecm expected 3. Correct!

You did not give many details about your system. By far too few. So you get only a very sparse reply: check your NIC names and verify the network settings.

Sure. I am mostly on "Debian Stable" for a reason. Obviously you have your reasons and you know a lot of details, including the background. I am absolutely fine to let you choose your way to go, even when I would never go that route :-)