iscsi storage motion

F

fastboar154

New Member
Apr 9, 2025
3
1
3
Dear everyone

I am new to the community and also to this virtualization system, I come from a vmware environment now migrated to azure however I deal in my free time with a small reality still tied to the same platform (vmware) and for cost reasons the owner has decided under my suggestion to migrate to proxmox.

The current environment is equipped with 4 vmware hosts on two different twin clusters and replicated with site manager in case of a site failure the other goes up and vice versa.
I have seen that it is possible to activate hyperconverged cluster with proxmox and it is also possible to share an iscsi storage as they have now.
Having said that in case of a host failure the machines automatically move to other hosts and I think I have understood this clearly, however what happens if instead the storage where the VMs are active fails? Is it possible, having hardware available, to distribute a single iscsi MPIO volume shared on two storages or somehow replicate the contents of a storage on another in mirroring? Do you have any suggestions?
thank you all
 
fastboar154 said:
if instead the storage where the VMs are active fails? Is it possible, having hardware available, to distribute a single iscsi MPIO volume shared on two storages or somehow replicate the contents of a storage on another in mirroring? Do you have any suggestions?
Click to expand...
Hi @fastboar154 , welcome to the forum.

If you want storage redundancy, you need to invest in a solution that’s designed for it. There are software models that implement mirroring or data distribution across independent nodes - Ceph is an example of such.

If you're using an existing SAN - PVE will not make the storage redundant unless the SAN itself already provides that capability.

Cheers

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: fastboar154 and Johannes S
Thank you for reply @bbgeek17 understood i've read something about Ceph and i saw that is redundant but is applied to local disks if am I correct.
SAN is providing a sort of replication so we can use it but not so efficient.
We'll use backup over proxmox in case of disruption will be easy to retrieve back data.
 
fastboar154 said:
i've read something about Ceph and i saw that is redundant but is applied to local disks if am I correct.
Click to expand...
There are many storage technologies available. Ceph is a member of Distributed Storage, SAN is a Centralized Storage. Each has it's own use-cases.
fastboar154 said:
SAN is providing a sort of replication so we can use it but not so efficient.
Click to expand...
In storage "replication" generally refers to Disaster Recovery, i.e. across sites. "High Availability" is used to describe recovery from a component failure. The two can be used at the same time to provide maximum protection.
Backup is in addition to DR and HA, it does not replace them.

That said, you have not described what type of environment you are operating in. If it is a homelab - good backup is sufficient. If it is a business, different rules apply.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
There are many storage technologies available. Ceph is a member of Distributed Storage, SAN is a Centralized Storage. Each has it's own use-cases.

In storage "replication" generally refers to Disaster Recovery, i.e. across sites. "High Availability" is used to describe recovery from a component failure. The two can be used at the same time to provide maximum protection.
Backup is in addition to DR and HA, it does not replace them.

That said, you have not described what type of environment you are operating in. If it is a homelab - good backup is sufficient. If it is a business, different rules apply.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...

Unfortunately it is not a home lab but a real migration process from the VMware environment to PROXMOX with passage and migration of the VMs (only 5) all under Windows Win2k19
  1. DC Controller
  2. File server
  3. MDaemon
  4. Finance app
  5. Backup server
a small redundant and functioning environment, however it is necessary to mediate between RTO and RPO risk. Their data is fully on premise backup is homemade with XSIBackup and then with Veeam community edition. I've implemented VMWARE site recovery feature to make DR because i was not sure about implementation made by old IT, as because bandwidth between site were too slow (Bridged radio) current QSAN supported QREPLICA feature which allows to replicate between storage with the same hardware.
I don't think DR is needed for this type of approach and having a powerful backup for sure will not give any DRP/BCP but reduce time of rebuild everything from scratch
 
Last edited:
  • Like
Reactions: Johannes S
You must log in or register to reply here.
Top Bottom