Hi, my name is Chris and we recently began using Proxmox at the shop I work at.
Little bit of story: I have an older backend storage server with lots of space that I wanted to use as a host for replication from the rest of the proxmox nodes in the cluster, and I assumed that one could simply select the remote replication storage pool the same as the node, but now I understand that all of the paths to storage have to be the same. (This stemming from a VM/CT being abstracted as an arbitrary resource to be started on any node in the cluster on what was some sort of shared backend storage but was extended to replication.)
I had two mirrored boot disks with an OS before that I replaced with Proxmox and then imported the old storage pool "tank". How would I go about pivoting the install to tank?
I'm thinking:
Little bit of story: I have an older backend storage server with lots of space that I wanted to use as a host for replication from the rest of the proxmox nodes in the cluster, and I assumed that one could simply select the remote replication storage pool the same as the node, but now I understand that all of the paths to storage have to be the same. (This stemming from a VM/CT being abstracted as an arbitrary resource to be started on any node in the cluster on what was some sort of shared backend storage but was extended to replication.)
I had two mirrored boot disks with an OS before that I replaced with Proxmox and then imported the old storage pool "tank". How would I go about pivoting the install to tank?
I'm thinking:
- zfs send the "ROOT" and "data" datasets and children to tank
- boot from rescue media, destroy old rpool and import tank as rpool
- setup and chroot into install on rpool
- copy zpool cache to /etc/zfs/zpool.cache
- run proxmox-boot-tool refresh (leaving boot partitions with same uuid's on two former rpool disks)