5 replies
Nothing if your apps is SAN aware.
SQL 2000, exchange 2000 are both SAN (or storage) aware, that it to said, many servers can connect to the same big hard disk, but each of them to a little part of the disk. That?s also call as share-nothing.
Two Nt servers can't share the same piece of disk, however, there is a software that allows you to do that. It's call network load balancing, with automatically distributes input request to many servers, and they access the data.
Another SQL 2000 feature is the ability to ma
nage a database partitioned in multiple servers. This allows you to have a very big database, distributed among different servers, depending on a filed contents, That's to said the last 5 years on server1, the previous years in server2 and so on.
You can read more about it at www.support.microsoft.com article:Q264135
Perhaps you will found more literature about IIS5.0 and a SAN rather than SQL & SAN.
Good Luck
by djake
What you need when creating a SAN is an arbitration layer. For two or more computers to have concurrent access to the same filesystem at the file level, the typical solution is a product like Tivoli's (IBM) SANErgy, which provides the MDC (Meta DataController) software to abritrate access. For a large number of shared volumes or LUNs you can distribute the MDCs across the servers to balance the load. Otherwise, if you point two servers or workstations at the same filesystem, it will become corrupted virtually instantenously.
W
by djake
by djake
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending