Adminlicious - A Guide To TCO Features In Domino v10
1 like•1,325 views
The document is a comprehensive guide on preparing for IBM's v10 upgrades, emphasizing the importance of conducting an audit of existing infrastructure and ensuring that systems meet new requirements. It discusses critical upgrades and dependencies, highlighting features aimed at improving total cost of ownership, database repair, and user experience improvements available in v10. Key topics include security steps, hardware requirements, and various enhancements such as improved replication features and full-text indexing improvements.
![Repair List Files Console Command
Mailturtle.nsf, 8055555:00372848 [Present]
TurtleRFC.NSF, 8055555:007ABEBD [Present]
Turtledbdesign.nsf, 858055555:0076FBF6 [Present]
Mailghedley.nsf, 802568E4:8055555[Present]
Missing files for server CN=Clouds/O=Turtle
archivea_turtle.nsf, 80256A24:0053E4CF [Missing]
archivel_turtle.nsf, 80256A24:0053F569[Missing]](https://image.slidesharecdn.com/adminlicious-180912204902/85/Adminlicious-A-Guide-To-TCO-Features-In-Domino-v10-13-320.jpg)
Adminlicious - A Guide To TCO Features In Domino v10
- 1. Adminlicious - A Guide to v10 Upgrades Gabriella Davis Technical Director The Turtle Partnership @gabturtle 2018
- 2. Gab Davis ✤ Admin of all things and especially quite complicated things where the fun is ✤ Working with the design, deployment and security of IBM technologies within global infrastructures ✤ working with the real world security and privacy aspects of expanding data ecosystems ✤ Stubborn and relentless problem solver ✤ http://turtleblog.infohttps://www.turtlepartnership.com ✤ IBM Lifetime Champion
- 3. Am I Ready? When / How / What Am I Going To Upgrade What Can I Do In Advance? Solid Security Steps to Upgrade
- 4. Am I Ready? ❖ Let’s start with an audit ❖ You’re going to do an audit - but one where you set the scope of what you want to discover ❖ What servers do I have? ❖ Where are they? ❖ Can I access them all? ❖ How about certifiers? (no you shouldn’t need them but let’s tick that box) ❖ Do I know who is using them? ❖ and for what?
- 5. Review System Requirements ❖ You don’t want to discover when v10 comes out that the old hardware and OS you are using are no longer supported ❖ We don’t know but it’s likely only the oldest will be no longer supported (and you already knew that needed upgrading right?) ❖ Check the exact requirements and limitations before you plan. They can change when new fix packs come out ❖ Is your operating system still supported by the developer ❖ Windows 2003 is no longer supported ❖ Windows 2008 support ends in January 2020 ❖ RHEL 6 and RHEL 7.3 both end support this year ❖ How old is your hardware, now may be a good time to plan a refresh
- 6. Priorities ❖ Although it would be nice to upgrade everything all at once over a single weekend that’s rarely practicable, or wise. ❖ Start by making a list of what is considered critical in your business, then look at what those services depend upon or “touch” ❖ For instance if Traveler is critical then you may want to upgrade the Traveler server but it won’t be a true upgrade test unless you also upgrade the Domino Directory and the mail templates - both of those things will have impact outside of Traveler ❖ Always be aware that you can usually upgrade back end services far in advance of the front end clients. A v9 client will still be able to read a v10 mail file on a v10 server formatted with ODS53 (just not using a v10 template design) ❖ When planning assume you will start with the platform base first. The actual Domino versions, the Sametime versions, the systems templates etc. Once those are in place you can start making changes to the things users see
- 7. Dependencies ❖ It’s also important to be aware of dependencies like integration products and the impact of design updates ❖ What could your dependencies be? ❖ Domino Directory design impacting all servers in the domain as it replicates out ❖ Is your Traveler server in its own domain? ❖ 3rd party products such as those loaded via EXTMGR in notes.ini ❖ Custom mail file design and changes ❖ Clustered servers
- 8. Domino v10 & TCO ❖ There are a lot of features coming with Domino 10 that are focused around total cost of ownership ❖ More than I can remember seeing since v8 ❖ Here are some of my favourites..
- 9. DISCLAIMER: What I am about a talk about is in Beta 2 I have permission to talk about and show you this stuff However this may change before GA. It’s just beta code
- 10. Database Repair & Symmetrical Clusters ❖ What problem is this solving? ❖ Missing databases across cluster mates ❖ Missing or corrupt NLOs ❖ Fast distribution of databases ❖ Corrupt databases
- 11. How Does It Work? Create a cluster configuration document. Or multiple cluster configuration documents ❖ The servers listed on the cluster configuration document are instructed to probe other servers in the cluster if they need to populate or replace a document ❖ Each server uses its own cldbdir.nsf to probe a server that it knows contains the file it needs and pull that file ❖ Files must have the same path and filename on each cluster mate including case sensitivity
- 12. How Does It Work? Folders to maintain Fix or list missing files - to be safe choose “list” initially
- 13. Repair List Files Console Command Mailturtle.nsf, 8055555:00372848 [Present] TurtleRFC.NSF, 8055555:007ABEBD [Present] Turtledbdesign.nsf, 858055555:0076FBF6 [Present] Mailghedley.nsf, 802568E4:8055555[Present] Missing files for server CN=Clouds/O=Turtle archivea_turtle.nsf, 80256A24:0053E4CF [Missing] archivel_turtle.nsf, 80256A24:0053F569[Missing]
- 14. Repair All Console Command ❖ “ archivea_turtle.nsf needs to be repaired but Auto Repair is configured to list only” ❖ With the configuration document set to “List” instead of “Fix” the server will not fix the database ❖ Repair end copy C:IBMDominodataarchivel_turtle.nsf : Invalid NSF version ❖ Requires ODS52 minimum (9.0.1) database format
- 15. ❖ REPAIR: Job-00007.1 *Copying* - Repair copying C: IBMDominodataarchivea_timd.nsf from donor CN=Oceanic/O=Turtle
- 17. NewRelic Reporting ❖ What problem is this solving? ❖ Statistics reporting into a Domino database that can get huge and has no built in analysis ❖ Utilising cloud services that are designed specifically to analyse statistics and can consolidate reporting from multiple servers in multiple domains
- 18. Statistics Reporting - NewRelic ❖ Domino servers can now send their stats directly to cloud based reporting systems ❖ by default NewRelic http://www.newrelic.com ❖ Creating an account is free ❖ Configuring statistics reporting is a case of adding one line to the notes.ini on the server
- 22. NewRelic Demo
- 23. Sending Mail Policy Limits ❖ What problem is this solving? ❖ Preventing mail from being delivered to the server mailbox if it fails criteria ❖ The server needn’t process the mail and return a non delivery ❖ The sender doesn’t think they have successfully sent a message only to get a non delivery report a few minutes later
- 24. Sending Mail Policy Limits Works for me in my v9 Mac client
- 25. Deletion Logging ❖ What problem is this solving? ❖ How to tell who deleted a document ❖ How to identify which document was deleted from a database and when
- 26. Deletion Logging ❖ Individual databases can be enabled to log deletions ❖ The detail of who deleted a document and the content of that document is written to delete.log file ❖ One for all databases that are enabled ❖ This is done via a compact option -dl that also specifies the fields in the document to log e.g. ❖ load compact mailgabdavis.nsf -dl on subject,posteddate,sendto,recipient ❖ different databases will want to use different fields in the log ❖ any Text, Text_List, RFC822_Text, or Time field can be used
- 27. Reviewing A Deletion Log Entry “20180308T211516,06+01", “Mailturtle.nsf", “80256487:00352154", “nserver","CN=DEWO=Turtle", “SOFT", “0001","72C0E3F8:44B53FB5DC4EDBF8:A785466D", "from","""New Relic” “<[email protected]>", “sendto","[email protected]", "deliveredDate","03/09/2018 21:05:05”, “posteddate","03/09/2018 16:15:18"
- 28. High Usage Views ❖ What problem is this solving? ❖ The updater is designed to queue databases that require view updates and process them as they appear in the queue ❖ Views that require continual updating can demand excessive resources from the updating threads ❖ The most in demand views can be isolated onto their own threads for updating
- 29. High Usage Views ❖ Domino can be configured to dynamically detect the 10 views across databases that need updating most frequently ❖ It then spins off a thread for each of those views to ensure they are kept up to date ❖ To enable set the notes.ini value NIF_VIEW_USAGE_ENABLED=1 ❖ More view rebuilds require more disk I/O
- 31. Improved Replication Features ❖ What problem is this solving? ❖ Faster streaming replication ❖ Forcing full replication via a console command without needing to clear replication history ❖ Reports to the console on replication activity and delays within a cluster
- 32. Improved Replication Features ❖ -F forces full replication without clearing rep history ❖ -L logs the replication activity that would happen ❖ ReplCurrency activity written to the statistics replica.cluster.currency* ❖ reports on databases that successfully replicated in each time window
- 33. Full Text Indexing Improvements ❖ What problems are these solving? ❖ Replicas becoming out of sync and incremental replication not including everything missing ❖ Full text searches missing newly created or updated document ❖ Admins refusing to full text index attachments because of the processing overhead ❖ Corrupted indexes that need to be manually deleted and rebuilt
- 34. On Demand Full Text Indexing ❖ If a client does a search on a database the unindexed documents are quickly indexed before the search is conducted ❖ Corrupted indexes are detected and rebuilt ❖ People don’t get frustrated that documents they just created aren’t appearing in search
- 35. Indexing Attachments ❖ The method for indexing document attachments when FT indexing is enabled has changed ❖ Currently I try and avoid indexing attachments at all because it causes so many problems ❖ Keyview has been replaced with Tika which runs as a java process on its own port ❖ FT_USE_MY_ATTACHMENT_WHITE_LIST=1 to determine what attachment types to index ❖ FT_USE_MY_ATTACHMENT_WHITE_LIST ❖ FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB ❖ FT_INDEX_FILTER_ATTACHMENT_TYPES=*
- 36. EXAMPLES OF INDEXING SETTINGS ❖ Tell the server to full text index only attachments that are word or pdf documents and only those that are 3MB or less ❖ FT_INDEX_FILTER_ATTACHMENT_TYPES=*.docx,*.pdf, ❖ FT_INDEX_FILTER_ATTACHMENT_TYPES_MAX_MB=3 ❖ This setting applies server wide ❖ Override the server wide setting with a specific database setting ❖ For the database with replica ID 80257D3A:0069F56A index word, pdf, excel and text documents that are less than 1MB ❖ FT_INDEX_FILTER_ATTACHMENT_TYPES_80257D3A0069F56A=*.docx,*.pdf,*.xls ,*.txt ❖ FT_INDEX_FILTER_ATTACHMENT_TYPES_80257D3A0069F56A_MAX_MB=1
- 37. ID Vault - Reinsertion ❖ What Problem Is This Trying To Solve? ❖ IDs in the vault can’t easily be replaced once they get out of sync, they have to be manually archived or deleted
- 38. ID Vault - Reinsertion ❖ IDV_Enable_Vault_Scan=1. ❖ Use qvault or ID Vault Scan in Domino Administrator to update person documents with vault assignments and dates forcing a re-insertion of an ID into the vault ❖ Or archive an ID in the vault to force a reinsertion of the client’s ID ❖ load qvault -x O=AllUsers -u “CN=Gabriella Davis/O=Turtle”
- 39. Working With Dead Mail ❖ Configured under router/smtp controls in the server configuration document ❖ When presented with dead mail the server will retry delivery (if internal user), send a non delivery report and delete the message ❖ By enabling this feature your mail.box doesn’t get filled with dead mail messages you have to manually delete
- 40. What More Do You Need To Know? ❖ Get your servers updated in plenty of time ❖ hardware, operating system, ODS version, cluster configuration ❖ Decide your priorities and design a plan for your upgrade whenever that will be ❖ Build a test environment with real data to start working with on v10 as soon as you can
- 41. Gab Davis ❖ My Perfect10 sessions are on my blog http:// turtleblog.info and on my Perfect10 Youtube channel ❖ You can contact me via twitter on @gabturtle ❖ This presentation is on my slideshare http:// www.slideshare.com/gabturtle