FC SAN Storage connect hosts not support both Snapshot and Share storage

S

stevenyiu

New Member
Nov 27, 2024
7
0
1
Hi All,

I am facing a situation about connect FC SAN, if i choose to use LVM, all the Guest VM can't take snapshot, if i choose LVM-thin, seems the storage are not shared and trigger slow migration speed issue....As i think FC SAN connect hypervisor is a very common solution,, so, how can i configure it and make the cluster support both Snapshot and Share storage? Thanks
 
stevenyiu said:
so, how can i configure it and make the cluster support both Snapshot and Share storage? Thanks
Click to expand...
This currently isn't an option unless your FC SAN has a specific storage plugin in for Proxmox VE that you could use. LVM-thin's approach is sadly not really compatible with shared storages and LVM itself has not proper support for efficient snapshots.

One workaround could be you use your SAN box as an NFS storage and then use QCOW2 images on top of that. However, this will probably affect over all performance for the VM.
 
  • Like
Reactions: Johannes S
sterzy said:
This currently isn't an option unless your FC SAN has a specific storage plugin in for Proxmox VE that you could use. LVM-thin's approach is sadly not really compatible with shared storages and LVM itself has not proper support for efficient snapshots.

One workaround could be you use your SAN box as an NFS storage and then use QCOW2 images on top of that. However, this will probably affect over all performance for the VM.
Click to expand...
Thanks for your reply. As i only have this FC connected SAN storage, and i think it can't be use as a NFS storage...so, there is no way for me to use this SAN storage with Snapshot and Share storage?
 
stevenyiu said:
Thanks for your reply. As i only have this FC connected SAN storage, and i think it can't be use as a NFS storage...so, there is no way for me to use this SAN storage with Snapshot and Share storage?
Click to expand...
Again, the manufacturer of the storage might supply a plugin that can do that, but we currently don't offer a first-party solution for this problem, yes. There is a more detailed overview of how to deal with this situation over in our Wiki [1].

[1]: https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Storage_boxes_(SAN/NAS)
 
  • Like
Reactions: Johannes S
stevenyiu said:
As i only have this FC connected SAN storage, and i think it can't be use as a NFS storage...so, there is no way for me to use this SAN storage with Snapshot and Share storage?
Click to expand...
If not doing special (by your san) you have block usage over fc channel to your connected pve hosts so it would be normal not having nfs from the san available and it this case your "fc connected" pve host could do the nfs service or take separate hosts for that which sit between your san and pve's.
 
I'm also new to proxmox and I've been following this post today as I've been dealing with the same roadblocks as the OP, making use of my SAN Storage. I've spent a week looking around the depths of the internet for a solution. I was reading on reddit and other sites that there are possibly workarounds to the snapshot limitations such as formatting the LUN with a Clustered file system such as GFS2 or OCFS, Then migrating the VMdisk and converting it to qcow2 to allow snapshots. I am hoping that someone with some more expertise could either validate this as work around to this SAN limitation or explain why this is not a recommended practice. Thanks
 
Hi @NC-BCLLP , welcome to the forum.

NC-BCLLP said:
I was reading on reddit and other sites that there are possibly workarounds to the snapshot limitations such as formatting the LUN with a Clustered file system such as GFS2 or OCFS
Click to expand...
This is not a workaround. It is a completely different approach to managing storage as compared to LVM option. You could compare OCFS/GFS vs LVM, to CIFS vs NFS. Two options that are available to users.

NC-BCLLP said:
. I am hoping that someone with some more expertise could either validate this as work around to this SAN limitation
Click to expand...
There are multiple threads in this forum discussing these options. Additionally, there is at least one, possibly more, step by step tutorials on the implementation.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
Hi @NC-BCLLP , welcome to the forum.


This is not a workaround. It is a completely different approach to managing storage as compared to LVM option. You could compare OCFS/GFS vs LVM, to CIFS vs NFS. Two options that are available to users.


There are multiple threads in this forum discussing these options. Additionally, there is at least one, possibly more, step by step tutorials on the implementation.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Thanks for the clarification, I'll dig deeper on this then.
 
NC-BCLLP said:
I'm also new to proxmox and I've been following this post today as I've been dealing with the same roadblocks as the OP, making use of my SAN Storage. I've spent a week looking around the depths of the internet for a solution. I was reading on reddit and other sites that there are possibly workarounds to the snapshot limitations such as formatting the LUN with a Clustered file system such as GFS2 or OCFS, Then migrating the VMdisk and converting it to qcow2 to allow snapshots. I am hoping that someone with some more expertise could either validate this as work around to this SAN limitation or explain why this is not a recommended practice. Thanks
Click to expand...
I am also new to Proxmox...may i know any steps i can follow about the solutions you mentioned (formatting the LUN with a Clustered file system such as GFS2 or OCFS, Then migrating the VMdisk and converting it to qcow2)? thanks
 
You must log in or register to reply here.
Top Bottom