Best Practices. Ranjit Rai Ranjit Rai 8April 2010

Transcription

1 Best Practices Ranjit Rai Ranjit Rai 8April 2010

2 OPEN MIC LOTUS TEAM Ranjit Rai - Lotus Technical Advisor Presenter Focussing on entire Notes/Domino Hansraj Mali - Lotus Technical Advisor Focussing on Notes/Domino, LotusLive Hemant Parulekar - Tech Lead Core, Crash and Performance Focussing on core, crash and performance Reetu Sharma - Software Engineer Focussing on crash and performance Soumitra Limaye Lotus Support Facilitator for Open Mics

3 Agenda Backup and restoration. Policy. Lotus Domino upgrade Lotus Notes upgrade

4 Backup and restore Domino administrators now have two choices for backup procedures; the traditional method of making backup copies of files to tape or file server or relying on transaction logging. Lotus Domino backup should include: Domino server data files All databases Template files notes.ini file ID files Mail.box Follow these general guidelines to back up a Domino server: Domino requires that these files be open when it runs: log.nsf names.nsf mail.box server ID file If your backup utility cannot back up open files, you must shut down the server before you create the backup.

5 Backup and restore Never rely only on replication as your method of database backup. A damaged or accidentally changed database may replicate, and then your only recourse is to recover the database from a server backup tape. Though every morning you can create a replica of names.nsf on one of system and check temporary disable replication on it. This will ensure you have a backup copy ready for emergency situation. Separate procedure needs to be followed for the DAOS backup and restore same is detailed in the link below Archive style transaction logging will allow you to take incremental backup of Lotus Domino. For more information on transaction logging you may refer to the following link. Transaction Logging on Domino Servers Notes/Domino Best Practices: Transaction Logging

6 Backup and restore Lotus Notes backup should include Personal Address book. User ID file. Desktop8.ndk Bookmark.nsf notes.ini Other NSFs (Local replicas, archive etc). Workspace folder.

7 Policy Never use IP address or hostname of the server in the location document, this is known to cause issues in password synchronization policy. Always re-configure the client for the new user by deleting old address book, bookmark.nsf, cache.ndk and desktop8.ndk.don't just create or modify a location document. Make sure policy is create using the ID that will stay with Lotus Domino environment as if the signer of the setting or policy document doesn't exist in address book, policy won't work. When implementing password change and sync policy for first time make sure you have cleared the last change date (Notes password) value in the person document of the user. If not done many of your user might end up getting locked next time they access the server. Unexpected policies were pushed when servers were upgrade to Whenever you want to test a policy perform the test on a user id not on admin ID, further it is always recommended to perform test on Lotus Notes only not on Lotus Notes Administration and Lotus Notes Designer.

8 Upgrade Phase 1: Planning the deployment Phase 2: Deploying Domino servers Phase 3: Deploying Notes clients Phase 4: Upgrading Notes/Domino applications to 8.5.1

9 Planning the deployment Evaluate and monitor your existing environment Evaluate Operating System and Hardware Requirements for 8.5.x Upgrade Domino on an existing machine or move to a new one? Evaluate what's new in Lotus Notes and Domino 8.5.x Create a server test environment Pilot the server upgrade in the production environment Upgrade to release 6.5.x if the current Domino version is older Prepare your production environment before you upgrade Plan your deployment sequence How Customers and Business Partners download Notes/Domino Other helpful resources

10 Deploying Domino servers

11 Deploying Domino servers The recommended deployment sequence for Lotus Domino / Notes environment is: 1. Upgrade the Notes clients that administrators will use to edit and operate on the Domino Directory 2. Upgrade Administration Server of Domino Directory 3. Allow the new Domino Directory design to replicate freely to the other servers 4. Upgrade the Hub servers 5. Upgrade the Resource and Reservations (R&R) servers 6. Upgrade the Mail servers 7. Upgrade the SMTP servers 8. Upgrade the Application/Web servers 9. Upgrade 3rd Party/Companion Product servers 10. Upgrade the general population to Lotus Notes Replace design of mail files with MAIL85.NTF

12 Deploying Notes clients PHASE 1: Plan the Deployment PHASE 2: Download & Customize Install Kit PHASE 3: Build & Test Deployment Package PHASE 4: Pilot Upgraded Client PHASE 5: Roll Out the Deployment PHASE 6: Manage the Desktop

13 Upgrading Notes/Domino applications to Planning Start thinking about applications from the outset Create an inventory of applications Determine what to do with the applications Plan your upgrade in "small" steps Testing Based on your application inventory, group applications. Test a sample of applications.. Remediation Depending on the server upgrade strategy... all critical applications must be fixed for in-place server upgrades critical applications must be moved to new servers After upgrading the server or once applications are deployed to new servers: make sure that you document and resolve any new issues start to look at new application features and how they can benefit your company

14 Resources Upgrade Cookbook DAOS: Backup and Restore Transaction Logging for Domino Best Practices : Transaction Logging Upgrade Resource Download link for customer - Passport Advantage Download link for business partner PartnerWorld Free download of Lotus Domino Designer 8.5.1

15 Questions?