Thank you for taking the time to show this off. Looking to replace our current SAN with something that provides flexibility, scalability, HA, and replication for DR. Ceph checks all of those boxes for us but the books that I have (from '19) say that they do not support VMware clusters, specifically, where multiple hosts share iSCSI block storage. I think this has changed, but it's reassuring to see PetaSAN catering to this use-case.
m new to this setup. I wonder if I install peteSAN without virtual box how can I setup HDD, let say I have 12 separate HDDs and I want to combine it as one HDD. Windows has storage space to do that, but I did not see that in petaSAN
I believe that is just how iSCSI multipathing works. When I first saw it I throught it was someone's goofy deployment but I looked into it and see it everywhere so, even if it's not technically mandatory (and I think it is), it's at least a standard convention with iSCSI.
Since iSCSI is deterministic, you can vastly benefit from segregating the iSCSI paths on separate subnets, so you don't end up with any crosstalk and ensure each IO in your RR config gets sent to and from the correct interfaces
Just the video I was waiting. Thanks a lot.
Thank you for taking the time to show this off. Looking to replace our current SAN with something that provides flexibility, scalability, HA, and replication for DR. Ceph checks all of those boxes for us but the books that I have (from '19) say that they do not support VMware clusters, specifically, where multiple hosts share iSCSI block storage. I think this has changed, but it's reassuring to see PetaSAN catering to this use-case.
Awesome video! nice tech. Can we have a video on how to backup a ceph pool?
m new to this setup. I wonder if I install peteSAN without virtual box how can I setup HDD, let say I have 12 separate HDDs and I want to combine it as one HDD. Windows has storage space to do that, but I did not see that in petaSAN
Very informational video
I don't get the redundant subnets for iscsi multipathing. Whats the benefit?
I believe that is just how iSCSI multipathing works. When I first saw it I throught it was someone's goofy deployment but I looked into it and see it everywhere so, even if it's not technically mandatory (and I think it is), it's at least a standard convention with iSCSI.
Since iSCSI is deterministic, you can vastly benefit from segregating the iSCSI paths on separate subnets, so you don't end up with any crosstalk and ensure each IO in your RR config gets sent to and from the correct interfaces