Hi everyone—first off, thanks to the Pitstop community forum for being such a great space to share experiences and learn from one another. The resources here have been really helpful in guiding troubleshooting and performance tuning.

I’d like to start a discussion around building and maintaining a storage area network that supports both scalability and reliability. In many environments, storage paths get congested when backup jobs and application traffic overlap. Would creating a modular design—where dedicated network paths are reserved for specific workloads—help reduce latency and improve data availability?

From my experience, even small-scale storage networks benefit from redundancy and logical isolation, but I’d love to hear how others in this forum approach it. What strategies have you found effective for monitoring throughput, managing backup traffic, or ensuring seamless transitions when scaling?

Has anyone implemented a dual-path setup, with one layer for live app data and another dedicated purely to backups? If so, what lessons did you learn during deployment?

Thanks again to Pitstop and this community for encouraging these knowledge-sharing discussions. Looking forward to your insights and suggestions.