There are many variables involved in database storage, but I'll try to make a general comment here in the space available.
If you are using raw partitions for your Oracle database then NAS is probably not the best choice. However, if your database is running on top of the file system, then you might consider migrating to a high-end NAS environment with an Enterprise NAS system and a Gigabit Ethernet network.
Otherwise, a small SAN using one or two 8-port switches (depending on path redundancy reqs) could be dedicated to your database system. If you already have a SAN, you might be able to establish a "database zone" for your Oracle system. Leave extra ports for expansion and upgrade connections.
The data is probably on SCSI storage now. SCSI to FC routers/bridges could be used to connect those subsystems to the SAN. If transaction rates need to be high, then you need to carefully look at the specs of the bridge to see if they are adequate.
If you are using the Veritas volume manager and Veritas file system, then you can add storage to the volume space and expand the file system to use the additional storage.
Other virtualization methods could be used also. I tend to prefer host-based volume management or out-of-band virtualization for databases in order to maintain existing transaction rates. For instance, the StoreAge virtualization solution delivers future scalability with minimal introduced latency.
Editor's note: Do you agree with this expert's response? If you have more to share, post it in one of our .bphAaR2qhqA^0@/searchstorage>discussion forums.
This was first published in November 2002