I'm being tasked with defining SAN policies for an external organization. I'm not a sysadmin, these aren't systems we have any authority over. I'm also no SAN expert. Whoever said work had to make sense?
I've come up with a few bullet points based on the documentation provided by the vendors involved (which the external org that will is currently running the SAN has not bothered to look into). Things like "don't put high I/O test storage on the same slice as Prod data stores" which seem like they should be obvious but clearly weren't.
Any recommendations on general SAN conventions that should be in place to improve performance and reliability?
Specific to our setup (EMC hardware, DB2) these are the key items I have:
- Ideally each Logical Unit (LUN) of the SAN will be spread across multiple physical devices to allow concurrent I/O thus improving performance.
- Each LUN should be dedicated to single use (e.g. the DB2 store for a particular application)
- For DB2 transaction logs should be located on a separate LUN on a physically separate spindle or set of spindles from the table data
- Data LUNs should be RAID-5 as it provides the best performance though with reduced redundancy
- Log LUNs should be RAID-10 to provide maximum redundancy
- If LUNs are set up to use file systems instead of raw partitions (which is recommended) tablespaces should use the NO FILE SYSTEM
- CACHING clause to improve performance