Isdpcman
20 pts. | Mar 10 2008 2:55PM GMT
There are some physical issues we have with this. If we go with SAN we can only use an iSCSI initiator as the host VM servers must be able to share this resource. They cannot use an HBA for this.
While we will undoubtedly have SQL Server needs they will be small (e.g. 30 - 80 users tops)
I will check out the link you have, thanks. This is new territory for me and I want to make the right choices for our needs. I appreciate your advice!
Rcp123
10 pts. | Mar 11 2008 5:00PM GMT
The performance differences between NAS and SAN start to blur at the high-end. There are NAS devices out there that have fairly high performance numbers. Several come with multiple GigE or even 10GigE that can
then be bonded together. Our own NAS has sustained over 70K IOPS . This is one server, not several. NAS can also scale fairly high — into the PB.
Both NAS and SAN storage offer replication and DR. Though at the lowest end, you may be hard pressed to find a SAN solution that provides this and may have to resort to purchasing something 3rd party. Most NAS will offer some type of replication…at the very least to another NAS box of the same type.
Traditionally NAS has been simpler to administer once you set it up. SAN has had the stigma of being difficult but I think that’s no longer true, especially with the newer storage devices available out there.
I think in either case, you should think about how you plan on scaling this service. If this is just the beginning, and you think you’ll be growing a lot, you may want to consider choosing backends which allow you to spread the load across all storage spindles non-disruptively. This allows you to keep growing your front-end compute w/o taking the downtime to upgrade your back-end storage should it ever become your bottleneck.






