1 / 14

SANPLAN

SANPLAN. By Thao Pham and James Horton For CS522, Dr. Chow. SANPLAN. S torage A rea N etwork P reparation L ocation A ctivation, and N ormalization. What is a SAN?. Storage Area Network A dedicated network that is separate from other LANs or WANs.

pink
Download Presentation

SANPLAN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SANPLAN By Thao Pham and James Horton For CS522, Dr. Chow

  2. SANPLAN • Storage • Area • Network • Preparation • Location • Activation, and • Normalization

  3. What is a SAN? • Storage Area Network • A dedicated network that is separate from other LANs or WANs. • Used as a storage repository for 1 or more hardware resources. • Typically it is a high-speed connection (Gbps). • INCLUDES controlling software.

  4. SAN Hardware/Software Each SAN is potentially unique, because there are no real “standards” in the industry yet. SANs can include RAIDs, hubs, switches, bridges, servers, backup devices, interface cards, and cabling. SANs are also usually software-dependant, which can again create compatibility issues. This is why that for now, it is very important to use a vendor that specializes in SAN design and support.

  5. Goals of this project • Improve performance of UCCS SAN in terms of efficiency, disaster recovery (reliability), interoperability, and possibly security. • Provide redundancy to the current system • Allow the use of the SAN among multiple Oss • Expand implemented security measures Should be no physical changes within the boundaries of the current SAN!!

  6. Current configuration of UCCS SAN

  7. Current RAID Setup • RAID 5 configuration • Size = 36G each • 10 Physical disks

  8. Constraints of the project • Current config. will be maintained until new config. is confirmed to be fully functional and fail-safe. • Limited university budget. (i.e., approx. $0) • Limited development staffing (Thao + I) • Technology to be used will be HP network equipment and utilities.

  9. Recommendations : future HW configuration

  10. Recommendations : future HW/SW changes • Update to the latest controller, version 8.7 • Add switch for redundancy • Add controller for redundancy and failover • Modify RAID configuration • Modify controller configuration • Allow access by NT • Improve performance • Set CACHE_FLUSH_TIMER = 45s • Set MAXIMUM_CACHE_TRANSFER_SIZE = 256

  11. Recommendations : future HW/SW changes (RAID) • Add 1 disk/bus • Support parallel reads/writes • Separate quorum disk • Create spare disk • Physical view next slide :

  12. Future RAID view

  13. Additional work • Storage Sharing • Backup considerations • Secure Shell

  14. Conclusions/Future work • SANs are EXPENSIVE!!! • Difficult to ‘upgrade’ a SAN due to price and proprietary concerns • Best suggestion is to make incremental improvements based on expense • Re-configure current RAID and controller • Add RAID disks • Install Secure Shell software • Add secondary SAN

More Related