Bold move using so many drives in a raidz1. You risk losing your entire pool in the event of a raid rebuild burning out another disk, which is a high risk operation and is likely to happen. Its one of the main reasons no one recommends raid 5 anymore (raidz1 is essentially the same fault tolerance). Sure, you have the performance, but you run a large risk there. I don't even run raidz1 at home anymore for that exact reason.
As for Minio, Veeam is notoriously hard on Object Storage systems using any kind of erasure coding. You could try increasing the block size to 4 MB or 8 MB, but for an on-premises repository I'd go for an XFS repository over a single node Object Storage repo, no matter the brand you use. I don't see the benefits of using on-premises Object Storage unless you're going to go for a system that supports erasure coding to avoid a single node failure wiping you out. If your use case includes M365 backups, Object Storage would be preferred there as well.
As for Minio, Veeam is notoriously hard on Object Storage systems using any kind of erasure coding. You could try increasing the block size to 4 MB or 8 MB, but for an on-premises repository I'd go for an XFS repository over a single node Object Storage repo, no matter the brand you use. I don't see the benefits of using on-premises Object Storage unless you're going to go for a system that supports erasure coding to avoid a single node failure wiping you out. If your use case includes M365 backups, Object Storage would be preferred there as well.
Statistics: Posted by tyler.jurgens — Mar 13, 2024 4:14 pm
![VA – DVD-Audio Music Sampler Vol.2 (2003) [DVD-Audio ISO]](http://imghd.xyz/images/2026/05/13/4lSo1rN.jpg)
