Renaming storage on a node in the cluster

O

oester

Member
Jan 9, 2021
24
2
23
68
I have a 2 node cluster (3rd node a qdevice) with nodes pve01 and pve03.

Node pve01 has a vm storage ZFS pool called "vmstore"
Node pve03 has a vm storage ZFS pool called "vmstore1"

The fact that the 2 nodes have different VM storage names, makes it difficult for me to create templates on one node and then try and create a full clone on the other node. I'm looking for a way to rename the "vmstore1" pool to "vmstore" so they match. I do have full backups of everything on each node (Proxmox backup server), so I'm thinking that I could just remove all the VM's, delete the pool and then recreate it under a new name.

Any other thoughts on how I could do this without having to delete and recreate everything?

Thanks, Bob.
 
Thanks. After I edit the storage.cfg file, I'll have entries that look like this:

zfspool: vmstore
pool vmstore1
content images,rootdir
mountpoint /vmstore1
nodes pve01
sparse 1

zfspool: vmstore
pool vmstore1
content images,rootdir
mountpoint /vmstore1
nodes pve03
sparse 1

Should I combine them into one entry, like this?

zfspool: vmstore
pool vmstore1
content images,rootdir
mountpoint /vmstore1
nodes pve01,pve03
sparse 1
 
I combined them into one entry:

zfspool: vmstore
pool vmstore1
content rootdir,images
mountpoint /vmstore1
nodes pve03,pve01
sparse 1
 
Thanks for the quick reply.

I wonder how it knows they are two, local ZFS pools and not a "shared storage"? I guess because the type is "zfspool" and not something like "zfs" with a target?
 
FWIW: A quick test just changing the name on the second entry to match the entry on node 1 (i.e. having two storage config sections with the same "id") made the first storage disappear from the GUI (I did not check pvesm info). That's not good.

I haven't tested it yet, but I assume the way you configured it is "the right way".

There's a huge gap in storage configuration planning that's not documented. :(
 
You must log in or register to reply here.
Top Bottom