1 / 12

ODG SAN/VMware Implementation

ODG SAN/VMware Implementation. Agenda. What model did we have? What limitations were we experiencing with this method? What were our business drivers to move to server virtualisation and a SAN ? What were the price trends for storage? What products and partners did we choose and why?

tehya
Download Presentation

ODG SAN/VMware Implementation

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. ODG SAN/VMware Implementation

  2. Agenda • What model did we have? • What limitations were we experiencing with this method? • What were our business drivers to move to server virtualisation and a SAN ? • What were the price trends for storage? • What products and partners did we choose and why? • What benefits did we achieve? • What are we planning next? • Any Questions?

  3. What model did we have? • We had the direct attached storage model at ODG • Disk drives were housed either within the server or directly connected via SCSI to external storage bays • Server proliferation (despite best efforts) was growing on the basis of one app per server exponentially

  4. Limitations we experienced? • Inflexible Resource Sharing • Duplication of data • Out-of-date information • Unbalanced load • Backup Complexity • Multiple backup devices • Multiple software licenses • Harder to troubleshoot complex jobs • Backup windows • Hardware Proliferation • More equipment meant less space • More setup time • More hardware to troubleshoot and fix

  5. What were our business drivers to move to a SAN\Virtualised infrastructure? • Data growth increasing exponentially • New requirements by clients • Compliancy laws (IT and Media) • Service hosting for CMS • Service hosting for Data Warehousing • Implementation times • Space/heat/power • Scalability • Better load balancing of data and resources • Limited IT resources

  6. What were the price trends for storage? • Storage capacity increases year on year and therefore becomes cheaper with time. • With that in mind, it made more sense to buy a modular storage model and increase it as and when the company requires it.

  7. What products and partners did we choose and why? • Virtualisation product • VMware ESX 3i • Features • HA • DRS • VMotion • Support

  8. What products and partners did we choose and why cont? • SAN Vendor • Equalogic • Ease of use • Speed of implementation • Scalability • Features • Snapshots • Replication • Clones • Costs

  9. What products and partners did we choose and why cont? • Implementation partners • Coal IT • Staff ethos • Knowledge of our requirements and technical expertise • Willingness to go the extra mile

  10. What benefits did we achieve? • Server Consolidation (15:3) • Availability • SAN storage has been more reliable than DAS attached disks • Improved resource sharing • Disk utilisation • Reduce wasted space • Improve performance • Management • Manage all storage globally from a single console • Faster provisioning of storage • Reduced downtime for changes to configurations • Backup • Snapshots • Fewer devices

  11. What are we planning next? • Complete the server migration to virtualisation • Begin beta trialling Lab Manager/Stage Manager for CMS system • Implement Site Recovery Manager • Implement a 4 tier storage solution as part of our digital workflow project

  12. Any Questions?

More Related