All my directories seem to be correct:
root@yscdtpbs:/mnt/dtsynlun2/.chunks/55be# ls -Al | head
total 132204
-rw-r--r-- 1 backup backup 3012125 May 23 00:12 55be068759f6752b5b385c0fe2664b08fedc5c5dca8a50da953160becc175818
-rw-r--r-- 1 backup...
and why shut this work with two interface names on one vmbr0?
what about a nic0, nic1 -> bondX -> vmbr0 setup with some bond mode?
# https://pve.proxmox.com/wiki/Network_Configuration
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...
When using iSCSI with Proxmox, it is generally used as LVM over iSCSI.
In this case, LVM is provisioned using Thick provisioning, not Thin provisioning.
Note that Snapshots are provided as snapshot-as-volume-chain, which differs from typical...
Hi everyone,
I’m working on a lightweight NOC monitoring platform called OPSHOME NOC, and I would like to get some feedback from Proxmox VE users, especially from homelab and small infrastructure environments.
The idea is to provide a simple...
"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...
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...
Echoing UdoB, setup a PDM VM and connect both PVE servers to it. Under the Remotes in the left pane, click on source server and in the middle pane you should see a little paper-airplane icon ( the icons in order are power, start, airplane...
Even then, AMD <-> Intel live migrations can break due to too many subtle differences and vendor-specific optimizations to guarantee that this could work independent of the used vCPU type; some types (like host) will make breakage much more...
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...
Another way is to just pipe a dd read call through tar through ssh from one to the other end where it untar's and dd writes all in a single call, this will minimize bandwidth and also achieve what you're after. I'm pretty sure I had an old backup...
A cluster file system should remain stable, even in case of hardware failure. I did read that thread and the point is that there was data unavailability that simply allows the OS to continue in a corrupted state. They didn’t know why only that it...
This will change as soon as qemu remove it's gluster support. Which will happen at some point otherwise they wouldn't have deprecated it. And maintaining a qemu fork is a whole different beast than continueing to ship a storage plugin.
How is the storage set up? If it is zfs at both sides you should be able to do a simple zfs send > zfs receive to copy from one machine to the other. If you have different storage types at both ends it could be a little harder, and at that...
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...
In order for it to be a true quorum provider, it has to be accessible to all nodes but NOT PHYSICALLY LOCATED at either site. The whole point is should one of the sites drop, the quorum provider is not affected.
Be mindful that if HA is enabled, around 2 minutes after losing quorum HA will reset the no-longer-in-quorum hosts. If you plan on using pvecm expected N, do it gradually as @UdoB explained above instead of setting it to 3 directly when the whole...