My best practices presentation from the Greenville Lotus User Group (GLUG) from Q3 2009.

1. Running IBM Lotus Domino on VMware Or “We want to virtualize absolutely everything” Fall 2009 Greenville, SC Lotus User Group Darren Duke, Technical Lead, STS

3. Domino, VMware and BlackBerry certified

4. http://blog.darrenduke.net

5. Oddles of DAOS and VMware experience

7. Should you virtualize?

8. Easy ones and the basics

9. Performance

10. Domino infrastructure

11. Vmware infrastructure

12. Finally....

16. Consolidation/Upgrade refresh

17. Consolidation of servers

18. Ease issues with hardware upgrades

21. You are doing it to be “cool”

22. You are lacking a specific business case

25. To replace Domino clustering

29. PVU to vPVU, Nehalem, etc

31. SAN admins

32. Network admins

35. Local

36. SAN/NAS

38. Not VMware Workstation

40. Gold = 12 x 5

42. VMware are aware of the issue

44. vSphere 4 is your friend

46. Use a 64 bit Domino server

52. Separate LUN for Domino Data

53. Separate LUN for Transaction Logs

54. Yes, your SAN admin will hate you!

57. 8Gb is 2x faster than 4Gb

65. >= 10ms needs looking at

67. Incorrect fiber configuration

68. Slow SAN

70. iSCSI @ 10G Ethernet

71. Fiber @ 4+ Gbps (8 if you plan on scaling)

78. If you have the CPU cycles, compress the TCP port traffic (on Domino)

80. They are cheap, yet time and time again we see issues in this area

85. Prevent ballooning at all costs

89. UPDATERS=x (where x is vCPU count)

93. RDM for TX Logs

97. Split the load between many, smaller guests

99. Compress TCP port on server AND client

105. Don't forget to defrag Windows guests

109. Specifically NIC drivers, jumbo frames, etc

111. Each VMware environment is different

112. Test, test and test

116. http://blog.darrenduke.net

118. R6.5 is being “End Of Life” in April 2010.