Eniac – Lotus Consolidation 2009


Published on

Presentation about Lotus Notes and Domino email and collaboration consolidation.

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Eniac – Lotus Consolidation 2009

  1. 1. Consolidate messaging & groupware platform What does it mean and how to approach. Author: Edwin Kanis
  2. 2. Why consolidate messaging and groupware platform <ul><li>Reducing the TCO by: </li></ul><ul><ul><li>Building a less complex environment </li></ul></ul><ul><ul><li>Easier administration and systems management (bundle competences) </li></ul></ul><ul><ul><li>Sharing complementing services (IM, anti-spam, anti-virus etc) </li></ul></ul><ul><ul><li>Reduce server license costs </li></ul></ul><ul><ul><li>Standardize your environment </li></ul></ul><ul><li>Gain more control, create flexibility and improve security </li></ul><ul><li>Creating high availability </li></ul><ul><li>Improving back-up and restore operations </li></ul><ul><li>Creating opportunities for future compliancy reasons </li></ul><ul><li>Creating opportunities for archiving and data offload reasons </li></ul>
  3. 3. Statement <ul><li>“ Lotus Domino is a great and flexible platform, it is scalable for every organization and the technology can handle full consolidation” </li></ul>
  4. 4. Why Domino is a good messaging platform for consolidation <ul><li>Why Advantage </li></ul><ul><li>Scalable and platform independent -> CPU and Memory </li></ul><ul><li>Support for 32 and 64bit platforms -> CPU and Memory </li></ul><ul><li>Domino clustering is proven to be excellent -> High availability, maintenance </li></ul><ul><li>Network compression / streaming replication -> Bandwidth savings </li></ul><ul><li>Storage compression / Single attachment -> Storage savings </li></ul><ul><li>Transactional logging -> IO, back-up, rebuilt </li></ul><ul><li>Multi language support -> Maintenance </li></ul><ul><li>Mixed versions and backward compatibility -> Maintenance </li></ul><ul><li>Multi client support (Notes, Browser, Pop etc) -> Maintenance </li></ul>
  5. 5. Steps to follow for consolidation <ul><li>Define desired and future services </li></ul><ul><li>Define your requirements and describe company standards </li></ul><ul><li>Describe a logical and physical infrastructure architecture </li></ul><ul><li>Built the new technical environment </li></ul><ul><li>Transition from the current to new environment </li></ul><ul><li>Support services </li></ul>
  6. 6. 1) Define your desired and future services (examples) <ul><li>Messaging and Calendaring services </li></ul><ul><ul><li>Mobile, Web Access, Archiving? </li></ul></ul><ul><ul><li>Instant messaging? </li></ul></ul><ul><li>Directory and security services </li></ul><ul><ul><li>LDAP, SSO, SSL </li></ul></ul><ul><li>Application service </li></ul><ul><ul><li>Browser Notes apps? </li></ul></ul><ul><ul><li>Integration? </li></ul></ul><ul><li>Development service </li></ul><ul><ul><li>Apps dev and test? </li></ul></ul><ul><li>Remote location service </li></ul>
  7. 7. 2) Define your requirements and describe company standards <ul><li>Organizational ( ! ) </li></ul><ul><li>Service level requirements </li></ul><ul><li>Company policies and standards (conventions etc) </li></ul><ul><li>Consolidation level: Local versus regional versus global </li></ul><ul><li>Technical </li></ul><ul><li>Working local replica’s (LBC) andor increase networking bandwidth </li></ul><ul><li>Level of Redundancy required </li></ul><ul><li>Server platform and operating systems </li></ul><ul><li>Storage and back-up requirements </li></ul><ul><li>Archiving andor data offload </li></ul><ul><li>User management (Global or delegated) </li></ul>
  8. 8. 3) Describe a logical and physical infrastructure architecture <ul><li>Architect a logical environment </li></ul><ul><ul><li>Domains, organizations </li></ul></ul><ul><ul><li>Security and access layers </li></ul></ul><ul><ul><li>Functional ‘clusters’ </li></ul></ul><ul><li>Architect a physical environment </li></ul><ul><ul><li># users #mailboxes per server </li></ul></ul><ul><ul><li>Locations and data centers </li></ul></ul><ul><ul><li>Server CPU and Memory </li></ul></ul><ul><ul><li>Storage amount and speed (IOPS) </li></ul></ul><ul><ul><li>Clustering and fail-over components </li></ul></ul><ul><ul><li>Anti-virus and spam </li></ul></ul><ul><ul><li>Networking (users, storage, back-up, cluster) </li></ul></ul>
  9. 9. 4) Built the new technical environment <ul><li>Building needs project management and communications </li></ul><ul><li>Stick to the design plans, use your architects </li></ul><ul><li>Test individual solutions and load test your total solution </li></ul><ul><li>Use your architect for reviews </li></ul>
  10. 10. 5) Transition from the current to new environment <ul><li>Cleaning the current environment (garbage out – garbage in) </li></ul><ul><li>How to transition from current to new central defined standards? </li></ul><ul><li>How to move mailboxes from local to central (large amount of data)? </li></ul><ul><li>How to move from online to Local but Connected (LBC)? </li></ul><ul><li>How to move applications from local to central? </li></ul><ul><ul><li>Do application integrate in other systems? </li></ul></ul><ul><li>How to switch into new user management situation? </li></ul>
  11. 11. 6) Support services <ul><li>Support organization and support roles </li></ul><ul><li>Monitoring the environment on several levels </li></ul><ul><li>Tools to make administration easier </li></ul><ul><li>Support and maintenance contracts 3 rd parties. </li></ul>
  12. 12. What else is important <ul><li>Politics </li></ul><ul><li>Involve highest level management (due to politics). </li></ul><ul><li>Think of an chargeback model up-front (impact on local budgets) </li></ul><ul><li>Design </li></ul><ul><li>Make use of experienced architect(s) in design phase. </li></ul><ul><li>Bring Domino architect together with storage and networking architects. </li></ul><ul><li>Built-in review moments for architect(s) </li></ul><ul><li>Project </li></ul><ul><li>Create a solid project organization </li></ul><ul><li>Separate project tasks from maintenance tasks </li></ul>
  13. 13. Conclusions <ul><li>The technology is there and is ready for consolidations </li></ul><ul><li>Do not over promise your services, start small and let your service grow. </li></ul><ul><li>Make your environment more simple. </li></ul><ul><li>Make use of experts, this saves time and makes later operations more simple. </li></ul><ul><li>Consolidation not only a technical project, this about your governance. </li></ul>
  14. 14. First steps into consolidation <ul><li>We advice to plan the following first steps towards consolidation: </li></ul><ul><li>Workshop (0,5 - 1 day): one level deeper into consolidation and architecture scope. </li></ul><ul><li>Built a business case (when required) around costs savings, simplification, administrative control and data management. </li></ul><ul><li>Built a consolidation approach, create planning and budget estimations. </li></ul><ul><li>Eniac Essentials can help every customer through this process. </li></ul>
  15. 15. Reference projects
  16. 16. The End <ul><li>Eniac BV Hogeweg 41 Postbus 2065 5300 CB Zaltbommel </li></ul><ul><li>TEL. +31 (0)418 57 07 00 FAX. +31 (0)418 57 07 66 </li></ul><ul><li>www.eniac.nl </li></ul><ul><li>Eniac is part of Imtech ICT </li></ul>