1 / 12

E-Mail System Update

E-Mail System Update. Tracy S. Holt Technology Coordinators Meeting March 15, 2005. The Current E-Mail System…. Originally Configured in 1999 Built for less than 100,000 messages per day Directory Services Dedicated to E-Mail Minimize Hardware Single Point of Failure

gayle
Download Presentation

E-Mail System Update

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. E-Mail System Update Tracy S. Holt Technology Coordinators Meeting March 15, 2005

  2. The Current E-Mail System… • Originally Configured in 1999 • Built for less than 100,000 messages per day • Directory Services Dedicated to E-Mail • Minimize Hardware Single Point of Failure • Did not account for spam and viruses • Based on the Netscape Software Suite • Disk Storage assumed 20MB quotas

  3. Since 1999… • Software has been acquired by Sun and merged into their messaging platform • Increased Storage Requirements (F/S Quota 50MB) • Increased Directory Services (Vernier, Web Apps, Mail Frontier) • Spam and Viruses • Security (ssl, access control) • Downtime less acceptable

  4. Incremental Upgrades • Added cpu and memory • Mail Frontier - Spam & Virus Solution • Added storage • Incremental Upgrades - iPlanet consortium • Retask existing hardware

  5. Current Issues • Cannot add storage (95% of available storage) • Cannot add cpu or memory • Solaris Operating System is very old • Software Single Points of Failure • Backup Duration • Increased Directory Requirements (Luminis, MESA) • Security

  6. Addressing The Issues • Partner with Sun Microsystems • Review existing architecture • Requirements Analysis • Multiple Architectures • Professional Services • Integration w/other applications

  7. Requirements • Reduce Single Points of Failure • Increased Storage and expandability • Upgrade to most current software (JES) • Increase Directory Services (privacy) • Security • Backup Duration and Disaster Recovery • Performance • Outbound Scanning • Utilize Sun’s Expertise • Upgrade Solaris Operating System • Enhance Network Connectivity

  8. The Plan • Purchase new hardware • Sun Servers • Storage Area Network (5tb - banner + email) • Test environment • Contract with Sun Pro Services • Review all requirements • Develop a plan that minimizes downtime

  9. Current Status • Hardware purchased and installed • Sun Pro Services Onsite • New 1GB Firewall Protected Network • Test Environment Operational • Mail Frontier 4.0 Beta Participant • SAN Configured • Directory Cleanup and Review

  10. Future Tasks • Configure Production Environment • Review options for data migration • Testing of Mail Frontier 4.0 • Sun PS onsite for data migration • Production Cutover • Shutdown of old servers • Enable new software features

  11. New Software Features • SSL enabled for outbound mail • Server Side Rules • New Web Interface - Unified Messaging Client • Outbound mail scanned for Viruses • Increased Quotas for Faculty & Staff • Delegated Administration • Identity Management, Access Management • E-Mail Address Flexibility

  12. Questions?

More Related