1 / 33

**Email Replacement Project at SFU: Enhancing Communication Infrastructure**

Explore SFU's successful transition to Zimbra email/calendaring system. Discover why the current system was replaced, the project's structure, technical details, automated data migration, and user perspectives. Learn from the project's outcomes and future possibilities.

erma
Download Presentation

**Email Replacement Project at SFU: Enhancing Communication Infrastructure**

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. Email Replacement ProjectBCnet Conference April 18, 2008 Frances Atkinson, IT Services DirectorSteve Hillman, IT Services ArchitectAnnay Slabikowska, User Experience Coordinator, Email Project

  2. Topics • Why Replace the Current System? • In Scope – Out of Scope • Structure of Project • Technical Infrastructure • Automated Data Migration • User Perspective: Who, what, when, how • What we Learned • Future Possibilities

  3. High-level overview SFU’s implementation of new email/calendaring technology

  4. Why we replaced the current system

  5. How we selected Zimbra

  6. Why we selected Zimbra

  7. Scope – Replaced coloured components

  8. Scope – Details • Moved 50,000 email accounts to new system • Moved 1300 Corporate Time calendar accounts • Trained the support staff & end users • Branded the new system • Scaled the infrastructure & support to handle fully loaded conditions • Retired the old Calendaring system • Still to do - Retire the old Email system

  9. Out of Scope - What we did not do

  10. Structure of Project

  11. Technical perspective SFU’s implementation of new email/calendaring technology

  12. Legacy Architecture Amaint LDAP Directory Barracuda MTA MailLists IMAP POP Webmail Store Webmail Mail Store Barracuda Desktop Home Directories

  13. Single server - vulnerable to system failure – expensive to replace

  14. Several dated components

  15. Our Email infrastructure was fully understood by one person – me

  16. Technical Objectives

  17. Zimbra Server Architecture HTTP/SOAP IMAP/POP Postfix

  18. Smtpserver MTA MailLists IMAP POP Mail Store

  19. Zimbra Multi-Server Architecture LDAP LDAP Proxy Proxy MTA MTA Amaint LDAP Zimbra Mailbox Server Zimbra Mailbox Server Zimbra Mailbox Server Zimbra Mailbox Server iSCSI NFS Index DB Primary Mail Store Index DB Primary Mail Store Secondary Mail Store

  20. Developed Automated Migration Scripts

  21. End-user perspective SFU’s implementation of new email/calendaring technology

  22. Who: Stakeholders

  23. What: New technology

  24. When? 1 year implementation timeline

  25. How: Obtaining buy-in

  26. How: Voluntary student signup

  27. How: Engaging departmental computer support staff

  28. How: Voluntary staff / faculty signup

  29. How/When: Moving calendaring users

  30. Lessons Learned

  31. Future Possibilities

More Related