Storage Area Network WHAT IS A STORAGE AREA NETWORK – According to the Storage Networking Industry Association dictionary: A storage area network (SAN) is any high-performance network whose primary purpose is to enable storage devices to communicate with computer systems and with each other.
What Makes a SAN? Computers are indeed connected to storage today, but are all of an installation's computers connected to all of its storage? That's the key point about SANs—they connect lots of computers to lots of storage devices, enabling the computers to negotiate device ownership among themselves and, ideally, to share data. If there is one defining characteristic of a SAN, it's universal connectivity of storage devices and computers.
What is the goal of OEPA and Storage Predicting, Managing and Controlling the cost of Storage Growth while keeping total cost of ownership and managed storage more efficiently, while still addressing the needs of the agency.
Overview of EPA Storage This is an optimistic design pending approval OIT - LAZ NWDO - OIT SWDO - OIT SEDO - OIT NEDO - OIT
Server Virtualization The Server/Storage Virtualization & Consolidation Workgroup (Server WG) is formed under the auspices of the Multi-Agency CIO Advisory Council (MAC) Enterprise Technical Architecture Subcommittee (ETA SC) to develop enterprise technical architecture and best practice recommendations for server and storage virtualization and consolidation. Enterprise technical architecture recommendations enable educated technology choices by providing the basis for a stable and consistent technology foundation across the enterprise. Further, they position the state and its respective agencies to leverage multi-agency combined buying power to optimize multiple objectives, such as economies-of-scale savings and overall business improvement. The Server WG will develop component specifications that will be used as input to the State’s sourcing process. These work products will consist of hardware and software specifications for each required component. Additionally, each component specification will detail the role and purpose for each component, with any identified or required best practices. Other Server WG outcomes may include the complementary development of other work products, such as guidelines, practices, research notes or other related content to support the topic. The goals of these work products are to assist state IT practitioners in the design, development, acquisition, or management of server and storage technologies to further the mission of state government.) This recommendation reports the results of member agency hypervisor selection, rationale, and Gartner analysis of industry suppliers confirming VMware as recommended hypervisor for x86 server environments. Economical alternatives are identified.
Multi-Agency CIO Advisory Council Findings 1.17 of 24 cabinet agencies (71%) have made investments in Vmware 2.27 out of 33 MAC agencies (82%) have invested in VMware virtualization software and services 3.25 of the 40 largest agencies (63%) have made investments in Vmware 4.31 state agencies have made investments in Vmware 5.The WG is preparing a collection of suggestions, rules of thumb, best practices, and lessons learned titled “Ohio Server/Storage Virtualization and Consolidation Guidelines” to provide agencies with planning assistance 6.In January, the Board of Regents announced a three-year purchasing agreement with VMware with the potential to save Ohio colleges and universities $130 million. The agreement was amended to include state agencies, school districts, and political sub-divisions. Agencies can purchase VMware products for 70% less than commercial list prices and obtain 35% discount for platinum level maintenance services. The Server WG recommends that state agencies use VMware’s hypervisor and related products to accomplish the savings and efficiencies associated with virtualization objectives and use the state’s VMware enterprise purchasing agreement to acquire products and services for x86 server environments. Biennial Review of Hypervisor and Related Virtualization Techniques Any new license procurements will need to follow the Governance procedures outlined above.
VMWare @ OEPA 1.Develop a test environment with access to network administrators 2.Develop policy and procedures for authorizing, creating, managing, and using virtual servers 3.Conduct server inventory (including all existing virtual and physical servers, their location, administrator, and purpose) 4.Implement virtual servers at each physical location after each server environment has been tested; some environments will be moved more slowly than others (specifically the Oracle and BEA environments) 5.District offices will first have Netware, Zen, Patch, and Microsoft servers virtualized
ITS Responsibilities for VMWARE Installation of test environment Lead policy/procedure development Initiate server inventory Installation of production virtual host server environments Administration of virtual host server environments
Division /District Responsibilities Identify and catalog guest server needs Request specific guest servers Administer division/district-specific guest servers
Backup Strategy – Currently Production DB takes 11 hours on LTO-2 to backup just 1.45 TB We know our data is growing at a much faster pace SEDO’s full backup takes 20 hours Mail backup takes 23 hours to backup 850 GB GFO full backup is no longer able to fit in one tape, and we have no one at GFO (off hours) to exchange tape when a new tape is needed. To solve this problem we split the full backup job into 2 separate jobs to get full backup done LTO-1 can hold 100 GB natively with maximum speed of 15 MB/s LTO-2 can hold 200 GB natively with maximum speed of 40 MB/s LTO-3 can hold 400 GB natively with maximum speed of 80 MB/s LTO-5 can hold 1.5 TB natively with maximum speed of 140 MB/s
Backup Strategy – What might be coming We’re going to get a new SAN with much faster switches. We going to get a new tape library with (2 ) LTO-5 tape drives, they will help cut down on backup time. The new SAN will be configured it so that our volumes will have many considerable amount of stripe across multiple disks. That way though put will be higher. We’re going to convert a majority of servers to VM (virtual machine). We’re going to upgrade Syncsort backup to version 3.2.1 to see what it has for vmware. With all this chances, what are the backup schemes going to look like. We intend to use old SAN as a full backup of all the servers in computer room. We would nightly create incremental backup of new SAN then apply it to old SAN; during working hour if we have to without effect bandwidth. We would have all day to do full backup for offsite in case if friendly neighbor decide to raise money by convert empty space to become meth lab and it blow up. For districts, we were thinking since the districts are going to get 10 MB bandwidth, we can do incremental backup of all districts nightly and full backup on the weekend. That way, offsite tapes are no longer needed. Also if a user in district need some files to restore and the district NA is not available, we can fulfill user request for district NA.