I'm running a proxmox cluster v8.2.4 (homelab) consisting of two nodes pve1 and pve2.
pve1 is a slightly better spec and has a ZFS storage on mirrored disks called zfs-storage
pve2 is running with the VMs on local-lvm
I wanted to replicate the vDisks of a in single VM102 from pve1 to pve2 however this doesn't work because of the different storage names, and although you can specify the node to replicate to, you can't specify the target storage.
Is there a way to create aliased storage names? for example "shared-storage" is mapped to "zfs-storage" on pve1 and "shared-storage" is mapped to "local-lvm" on pve2.
I could then move the disks from "zfs-storage" on pve1 to "shared-storage" on pve1 and the enable replication.
I tried this by editing the /etc/pve/storage.cfg and adding the below, but it doesn't work. Only the first entry of "shared-storage" appears as you can only create unique named storage.
Side note: Before some ask, yes "vgname pve" as local-lvm is actually the LVM volume group name pve.
Maybe I am close with the above and just need to tweak a little to get working????
I did also try creating two additional VMs (VM300 on pve1 and VM301 on pve2) with large vDisks and installed GlusterFS on them, so they were themselves replicating data. I then added the GluterFS storage in proxmox at the datacenter level.
This works, but their is a performance hit as VM102 now has its vDisks on the GlusterFS which is on two other VMs.
Of course in a ideal world I would have two PVEs with the same storage and replication would be easier.
But this isn't an ideal work and welcome to the real world of homelab'ing. Grins.
Any ideas on replication for HA failover in this example would be welcome.
Regards
Ian
pve1 is a slightly better spec and has a ZFS storage on mirrored disks called zfs-storage
pve2 is running with the VMs on local-lvm
I wanted to replicate the vDisks of a in single VM102 from pve1 to pve2 however this doesn't work because of the different storage names, and although you can specify the node to replicate to, you can't specify the target storage.
Is there a way to create aliased storage names? for example "shared-storage" is mapped to "zfs-storage" on pve1 and "shared-storage" is mapped to "local-lvm" on pve2.
I could then move the disks from "zfs-storage" on pve1 to "shared-storage" on pve1 and the enable replication.
I tried this by editing the /etc/pve/storage.cfg and adding the below, but it doesn't work. Only the first entry of "shared-storage" appears as you can only create unique named storage.
Code:
zfspool: shared-storage
pool zfs-storage
nodes pve1
content images,rootdir
sparse 1
lvmthin: shared-storage
vgname pve
thinpool data
nodes pve2
content images,rootdirSide note: Before some ask, yes "vgname pve" as local-lvm is actually the LVM volume group name pve.
Maybe I am close with the above and just need to tweak a little to get working????
I did also try creating two additional VMs (VM300 on pve1 and VM301 on pve2) with large vDisks and installed GlusterFS on them, so they were themselves replicating data. I then added the GluterFS storage in proxmox at the datacenter level.
This works, but their is a performance hit as VM102 now has its vDisks on the GlusterFS which is on two other VMs.
Of course in a ideal world I would have two PVEs with the same storage and replication would be easier.
But this isn't an ideal work and welcome to the real world of homelab'ing. Grins.
Any ideas on replication for HA failover in this example would be welcome.
Regards
Ian
Last edited:
