[SOLVED] Replication with different target storage name
- Thread starter Archmatux
- Start date
I have a number of smaller Proxmox nodes with HA replication setup. They all use single SSD, so all replication is on boot ZFS "rpool".
Now I am installing a bigger server where I will use separate OS and VM storage disks. So I need one of two things:
1) Ability to change "rpool" name during Proxmox installation
OR
2) This forum thread feature, being able to change which pool on each node to replicate to.
Right now I'm stuck trying to modify the boot "rpool" name, any help would be appreciated: https://forum.proxmox.com/threads/change-zfs-boot-pool-name.154692/
EDIT: For a solution how to rename the boot pool after fresh Proxmox install: https://forum.proxmox.com/threads/change-zfs-boot-pool-name.154692/post-705058
Now I am installing a bigger server where I will use separate OS and VM storage disks. So I need one of two things:
1) Ability to change "rpool" name during Proxmox installation
OR
2) This forum thread feature, being able to change which pool on each node to replicate to.
EDIT: For a solution how to rename the boot pool after fresh Proxmox install: https://forum.proxmox.com/threads/change-zfs-boot-pool-name.154692/post-705058
Last edited:
Wow it has been 8 years since some one first asked for this feature. It can not be that hard. Without this, I have to either manually migrate my existing vm to new servers with a separate zfs pool for vm or make my rpool very large like it currently is, not much separation between host os and the very large disks for my vm.
Please get this feature implemented.
Please get this feature implemented.
Nearly ten years. Wow!
I just asked this (https://forum.proxmox.com/threads/z...-and-different-pool-names.178638/#post-828572) and can't believe this is true and more so after all of these reports and ten years.
First sentence from: https://pve.proxmox.com/wiki/Storage
Seriously? That's the opposite of flexible.
Proxmox forces me to name my ZFS pools "rpool" and dataset "data" ? Can't believe it
I just asked this (https://forum.proxmox.com/threads/z...-and-different-pool-names.178638/#post-828572) and can't believe this is true and more so after all of these reports and ten years.
First sentence from: https://pve.proxmox.com/wiki/Storage
Seriously? That's the opposite of flexible.
Proxmox forces me to name my ZFS pools "rpool" and dataset "data" ? Can't believe it
It doesn't. You need two ZFS pools on each node with the same ID in the storage.cfg in /etc/pve but this name doesn't need to be rpool or data.
Let's say you have a vm image storaed on node pve-node1 local zfs pool "zfs-vm", then you can replicate it to the pve-node2 as long as pve-node2 also have "zfs-vm".
pve-zsync allows to configure the target pool but you won't have HA with it: https://pve.proxmox.com/wiki/PVE-zsync
Regarding "The Proxmox VE storage model is very flexible.":
This doesn t mean what you think it means. It doesn't mean's that any possible feature is allowed with each storage backend. Instead it means that a lot of different storage backends (ZFS,LVM,Ceph,ISCSI, NFS,Directory etc) are supported so that if you happen to have existing storage hardware (like a NAS, a FC-SAN or several discs attached to your compute nodes in a Vmware VSAN setup) you can reuse it with ProxmoxVE. The price is that not each feature will work with every storage backend. For example the ProxmoxBackupServer is one possible storage backend, but you can (big surprise) just use it to save backups. Other hypervisors have less options but they tend to share the same feature set. Whether this is a benefit or not is quite subjective.
Last edited:
Korrekt. Eben.
Das ist ein behelfsmäßiger Mechanismus. Ohne dass PVE dann anerkennt, dass diese Daten nun (wie bei der ZFS-Replikation) "shared" sind, ist das nicht einmal ein guter Workaround...