Backing Up Lotus Domino R5 Using Tivoli Storage Management Sg245247

Backing Up Lotus Domino R5 Using Tivoli Storage Management
Trouble-free storage management for R5 databases Backup, restore, and disaster recovery scenarios Procedures for Windows and UNIX platforms
Mathis Landzettel Clarence Beukes Charlotte Brooks Denise Kikumoto Flavio Pires Vieira Raghavendra Rao
ibm.com/redbooks
SG24-5247-00
International Technical Support Organization Backing Up Lotus Domino R5 Using Tivoli Storage Management October 2000
Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix B, Special notices on page 145.
First Edition (October 2000) This edition applies to Version 1.1.0 and Version 1.1.1.0 of Tivoli Data Protection for Lotus Domino Number 5697-DPN for use with Windows NT, Windows 2000, AIX, Solaris, and OS/390. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. 471F Building 80-E2 650 Harry Road San Jose, California 95120-6099 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
Copyright International Business Machines Corporation 2000. All rights reserved. Note to U.S Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi The team that wrote this redbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Comments welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii Chapter 1. Lotus Domino and Tivoli Storage Management 1.1 Introducing Lotus Domino and Lotus Notes R5 . . . . . . . . . 1.1.1 What is Lotus Domino R5? . . . . . . . . . . . . . . . . . . . . 1.1.2 What is Lotus Notes R5? . . . . . . . . . . . . . . . . . . . . . 1.1.3 Benefits of R5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.4 Components and platforms . . . . . . . . . . . . . . . . . . . . 1.1.5 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.6 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.7 Notes data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.8 Transaction logging . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.9 Backup API of R4 and R5 . . . . . . . . . . . . . . . . . . . . . 1.1.10 Storage management of Notes . . . . . . . . . . . . . . . . 1.2 Introducing Tivoli Storage Management . . . . . . . . . . . . . . 1.2.1 Tivoli Storage Manager backup/archive client. . . . . . 1.2.2 Tivoli Data Protection for Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . .1 . .1 . .3 . .4 . .5 . .6 . 11 . 12 . 13 . 17 . 19 . 19 . 21 . 22 . 25 . 25 . 28 . 28 . 29 . 29 . 30 . 31 . 31 . 34 . 36 . 36 . 38 . 38 . 40 . 44 . 45
Chapter 2. Configuring storage management for Lotus Domino. 2.1 Project test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 What to back up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Where to install?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Migrating from Lotus Domino R4 . . . . . . . . . . . . . . . . . . . . 2.3 Setting up Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . 2.3.2 Tivoli Storage Manager backup-archive client. . . . . . . . . . . 2.4 Configuring TDP for Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . 2.4.1 Include-exclude lists TDP for Lotus Domino . . . . . . . . . . 2.4.2 Preferences file TDP for Lotus Domino . . . . . . . . . . . . . 2.4.3 TDP for Domino on Windows NT option file . . . . . . . . . . . . 2.4.4 TDP for Domino on UNIX option files . . . . . . . . . . . . . . . . . 2.5 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Scheduling TDP for Lotus Domino . . . . . . . . . . . . . . . . . . . . . . .
Copyright IBM Corp. 2000
iii
2.6.1 Tivoli Storage Manager scheduler 2.6.2 Lotus Domino scheduler . . . . . . . . 2.7 Partitioned Notes servers . . . . . . . . . . . 2.7.1 Windows NT . . . . . . . . . . . . . . . . . 2.7.2 UNIX . . . . . . . . . . . . . . . . . . . . . . 2.8 Clustered Domino servers . . . . . . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . .
. 45 . 50 . 51 . 51 . 52 . 59
Chapter 3. Operating TDP for Lotus Domino . . . . . . . . . . . . . . 3.1 Database backup and log archive. . . . . . . . . . . . . . . . . . . . . . 3.1.1 Incremental backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2 Selective backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3 Archive log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 Activation of database . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Inactivation of archive logs . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Restoring individual archive logs . . . . . . . . . . . . . . . . . . . . . . 3.5 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 Changing the preferences file . . . . . . . . . . . . . . . . . . . . . 3.5.3 Changing the Tivoli Storage Manager password . . . . . . . 3.5.4 TDP for Domino message logging . . . . . . . . . . . . . . . . . 3.6 Graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3 Transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Restoring logged databases to an alternative Domino server . 3.8 Miscellaneous GUI functions . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1 Application client settings . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.3 Other information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 TDP for Lotus Domino performance . . . . . . . . . . . . . . . . . . . . Chapter 4. Backup strategy and recovery scenarios . 4.1 Domino considerations and backup . . . . . . . . . . . . . 4.1.1 Transaction logging modes. . . . . . . . . . . . . . . . 4.1.2 Changing the database instance identifier . . . . 4.1.3 Database compaction and the DBIID . . . . . . . . 4.2 Backup strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 No transaction logging . . . . . . . . . . . . . . . . . . . 4.2.2 Circular logging . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3 Archive logging . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. .. .. .. .. .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..
. . 63 . . 63 . . 63 . . 67 . . 69 . . 72 . . 73 . . 76 . . 78 . . 79 . . 80 . . 80 . . 84 . . 85 . . 85 . . 89 . . 91 . . 93 . . 96 . . 99 . 101 . 101 . 103 . 104 . 105 . 109 . 109 . 109 . 111 . 111 . 112 . 114 . 114 . 114 . 116
iv
4.3.1 Sample backup scripts . . . . . . . . . . . . . . 4.3.2 Defining the schedules . . . . . . . . . . . . . . 4.3.3 Associating the schedules . . . . . . . . . . . 4.4 Database and directory links . . . . . . . . . . . . . 4.5 Shared mail . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6 Media recovery. . . . . . . . . . . . . . . . . . . . . . . . 4.6.1 Restore database to its original location . 4.6.2 Database to new location . . . . . . . . . . . . 4.7 Server recovery and migration . . . . . . . . . . . . 4.7.1 Migrating to a new Domino server . . . . . 4.7.2 Disaster recovery . . . . . . . . . . . . . . . . . .
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
.. .. .. .. .. .. .. .. .. .. ..
. . . . . . . . . . .
. . . . . . . . . . .
. 116 . 118 . 119 . 119 . 126 . 129 . 130 . 131 . 134 . 134 . 136
Appendix A. Creating a recycling bin in Domino R5 . . . . . . . . . . . . . . 139 Appendix B. Special notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Appendix C. Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 C.1 IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 C.2 IBM Redbooks collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150 C.3 Tivoli Storage Management publications . . . . . . . . . . . . . . . . . . . . . . . . 150 C.4 Referenced Web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 How to get IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 IBM Redbook fax order form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 IBM Redbooks review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
vi
Figures
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. Domino Administrator client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Domino Designer client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Lotus Notes client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Domino Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Logical components of TDP for Lotus Domino . . . . . . . . . . . . . . . . . . . . . 24 Project test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Tivoli Storage Manager setup: management classes . . . . . . . . . . . . . . . . 33 Node names on Domino server machine. . . . . . . . . . . . . . . . . . . . . . . . . . 34 Tivoli Storage Manager Backup/Archive client . . . . . . . . . . . . . . . . . . . . . 35 Sample include/exclude list for backup-archive client . . . . . . . . . . . . . . . . 36 Sample domdsm.cfg file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Scheduling TDP for Lotus Domino with Tivoli Storage Manager . . . . . . . . 46 Backup-archive client scheduler wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 TDP Scheduler Service on Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Lotus Domino scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Partitioned Domino servers on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Domino cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Domino cluster in test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Example 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Example 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 TDP for Lotus Domino NT GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 GUI: Selective backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 GUI: Incremental backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 GUI: Point-in-time restore (single stage) . . . . . . . . . . . . . . . . . . . . . . . . . . 95 GUI: Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 GUI: Archive Log Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 GUI: View/Restore Log Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 GUI: Inactivate logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 GUI: Preference editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 GUI: Change TSM Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Additional information about Tivoli Storage Manager server . . . . . . . . . . 105 Additional information about Lotus Domino server . . . . . . . . . . . . . . . . . 105 Modified domarc.cmd script for Windows NT . . . . . . . . . . . . . . . . . . . . . 117
vii
41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. 56.
Dominos logical directory structure: directory and database links . . . . . 120 Failure if you try to back up the directory link directly . . . . . . . . . . . . . . . 122 Successful backup of databases in the directory link . . . . . . . . . . . . . . . 123 Databases pointed to by a directory link restored to original locations . . 124 Link between users mail databases and shared mail databases . . . . . . 127 Recovery of deleted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Restore a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Restore a database in a different location . . . . . . . . . . . . . . . . . . . . . . . . 132 Expiry of backup versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Restore and apply transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Database properties showing undelete function . . . . . . . . . . . . . . . . . . . 140 Creating a view to display deleted documents. . . . . . . . . . . . . . . . . . . . . 141 Create an Undelete document action . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Creating the Undelete button action code . . . . . . . . . . . . . . . . . . . . . . . . 143 Undeleting a deleted document in the Recycling Bin. . . . . . . . . . . . . . . . 144 Restoration of a deleted document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
viii
Tables
1. 2. 3. 4. 5. Available platforms for Release 5.0 . . . . . . . . . . . . . . . User interface features. . . . . . . . . . . . . . . . . . . . . . . . . Project DOMINO server systems. . . . . . . . . . . . . . . . . Backup possibilities for transaction logging modes . . . Documenting your backup requirements . . . . . . . . . . . ....... ....... ....... ....... ....... ...... ...... ...... ...... ...... ...5 . . 10 . . 28 . 110 . 113
ix
Preface
Tivoli Storage Management is a suite of products from Tivoli which encompasses an enterprise-wide network storage management solution. Together, these products provide data protection, including backup and restore, for over thirty major operating systems as well as for many of the most popular databases and applications. Lotus Domino R5 is one of these applications an industry-leading product for messaging and collaborative computing. Tivoli Storage Manager server and Tivoli Data Protection for Lotus Domino together provide online backup and restore of Lotus Domino R5 databases. This IBM Redbook addresses backup and recovery of Lotus Domino R5 databases on Windows NT, Windows 2000, and UNIX platforms. This redbook provides an overview of Tivoli Storage Management products and Lotus Domino, and then covers installation and configuration of Tivoli Data Protection for Lotus Domino R5 on Windows NT and UNIX, and operational procedures for backup and restore, as well as various scenarios for backup and restore. This redbook gives a broad understanding of the new architecture and features of Lotus Domino R5 as compared to R4, especially as they impact backup and recovery. Many examples and screenshots are included, to provide practical step-by-step instructions on setting up and maintaining this environment. This redbook is intended for customers, consultants, IBM and Tivoli Business Partners, and IBM and Tivoli personnel who are familiar with Tivoli Storage Manager and Lotus Domino and who want to know how to use Tivoli Storage Manager to protect their Domino data. We refer to Lotus Domino R5 simply as Domino for the remainder of this redbook.
The team that wrote this redbook

This redbook was produced by a team of specialists from around the world working at the International Technical Support Organization San Jose Center. Mathis Landzettel was a Project Leader at the International Technical Support Organization, San Jose Center. He joined IBM in 1994 after completing his degree in mathematics at the Technical University of Darmstadt. He writes extensively and has taught IBM classes worldwide in all areas of ADSM and Tivoli Storage Manager. Before joining the ITSO in 1998, Mathis worked in the ADSM development department in Mainz, Germany, as
xi
a software test team leader. Mathis is now with the SAN Interoperability Lab, also in Mainz. Clarence Beukes is an IT Specialist in South Africa. He has four years of experience with Tivoli Storage Manager. He holds a National Diploma in Information Technology from Technikon Witwatersrand. His areas of expertise include Tivoli Storage Manager planning, implementation, and troubleshooting. Charlotte Brooks is a Tivoli Storage Management Project Leader at the International Technical Support Organization, San Jose Center. She has ten years of experience with IBM in the fields of RS/6000 and Storage Management. She writes extensively and teaches IBM classes worldwide in all areas of Tivoli Storage Manager. Before joining the ITSO at the beginning of 2000, Charlotte was the Technical Support Manager for Tivoli Storage Management in the Asia Pacific region. Denise Kikumoto is an IT Specialist in Brazil. She has three years of experience in the storage field. Denise holds a degree in Systems Analysis from PUCC University in Campinas. She has worked at IBM for over three years. Her areas of expertise include Tivoli Storage Manager planning, implementation, availability of Notes/Domino servers on AIX, applications, and recovery of Notes/Domino servers on AIX and other platforms, including OS/2 and Windows NT. Flavio Pires Vieira is a System Support Specialist in Brazil. He has over three years experience in the storage field. He holds a degree in Electronic Engineering from UFRJ in Rio de Janeiro and has started a Master Course in Network Management at UFF in Rio de Janeiro. His areas of expertise include Tivoli Storage Manager planning and implementation, PSM planning and implementation, AIX support, Lotus Notes/Domino support, and network management. Raghavendra Rao is a Country Software Support Professional from Integrated Technology Services in IBM India. He has over four years of experience which includes Lotus Domino, Tivoli Storage Manager, and CATIA. He is also a Principal Certified Lotus Professional. His areas of expertise include infrastructure design, deployment, technical support, and application development for Lotus Domino/Notes, Tivoli Storage Manager, and Digital Library.
Thanks to the following people for their invaluable contributions to this project:
xii
Mike Ebbers International Technical Support Organization, Poughkeepsie Center David Herbert IBM Almaden Research Center, San Jose Chris Zaremba IBM Global Services, Endicott Robert Delaney IBM Global Services, Endicott Mary Uglow IBM Global Services, Endicott William Degli-Angeli IBM Global Services, Endicott Del Hoobler IBM Global Services, Endicott Denise Conrad IBM Global Services, Endicott Peter Symonds IBM Storage Systems Division, San Jose David Morrison Lotus Redbooks Team. Cambridge Ferdy Nagy IBM Global Services, Mountain View
Comments welcome
Your comments are important to us! We want our redbooks to be as helpful as possible. Please send us your comments about this or other redbooks in one of the following ways: Fax the evaluation form found in IBM Redbooks review on page 159 to the fax number shown on the form. Use the online evaluation form found at ibm.com/redbooks Send your comments in an internet note to redbook@us.ibm.com
xiii
xiv
Chapter 1. Lotus Domino and Tivoli Storage Management

This chapter gives a brief introduction to Lotus Domino, its components and interfaces, and its operation as a database system. We discuss the importance of storage management and various approaches to a backup solution. Tivoli Storage Manager, the industry-leading enterprise storage manager in a distributed environment, provides a backup solution for a heterogeneous Domino environment. We discuss the server, backup-archive client, and the Tivoli Data Protection for the Lotus Domino product.
1.1 Introducing Lotus Domino and Lotus Notes R5

Lotus Domino and Lotus Notes, respectively, are the server and client components of Lotus Corporations groupware product, which provides distributed collaborative messaging and e-business solutions in a multiplatform environment.
1.1.1 What is Lotus Domino R5?

Lotus Domino R5 is Lotus next generation of Internet products that include Notes integrated Internet client and Domino server platform for messaging, collaboration, Internet and Intranet applications. Lotus Domino R5 brings messaging, Internet integration, and scalability to a whole new level. The new Domino server includes the latest innovations in Internet messaging with native support for all the major Internet standards, such as industry-leading support for Web applications, including Common Object Request Broker Architecture (CORBA) support and integration with Microsoft Internet Information Server (IIS). The Domino Server has increased reliability and scalability including improvements in performance, capacity, availability, and maximum database size. In addition, the server has a new administration interface with a task-oriented approach that makes Domino easier to deploy, use, and manage. Lotus Domino R5 continues to support a wide variety of clients in addition to the traditional Notes clients. Messaging features are available to Web browsers and Internet mail clients, such as Post Office Protocol, Version 3 (POP3) and Internet Message Access Protocol, Version 4 (IMAP4) clients. Directory features are available to browsers and Lightweight Directory Access Protocol (LDAP) clients. Discussion features are available to browsers and Network News Transfer Protocol (NNTP) news reader clients,
and administration features are available to browsers as well as the Notes clients. Domino continues to be the best platform for designing dynamic Web applications. With the new Domino Designer R5, you can easily build a single application that looks and runs the same for both the Web and Notes clients. The Domino Designer is a Web and intranet application development tool. Dominos integrated platform delivers messaging and collaborative solutions for the Internet. Several key services enable IT professionals to manage and run their messaging and Web application infrastructures easily and efficiently. The new R5 Domino Administrator makes it fast and easy for administrators to manage users, configure systems, and optimize performance all from an intuitive user interface. The Lotus Domino R5 server builds on its already strong foundation for messaging and Web applications. The R5 enhancements are the next step in making Domino easy to use and a better fit for any sized organization. Specific Lotus Domino R5 features include:
Internet messaging and directories Provide robust messaging for your users with native MIME and SMTP support
Use the new Directory Catalog to save space and provide quick name lookups Use new LDAP features to authenticate users in external directories, customize the directory, and more
Expanded Web application services Design applications with CORBA-standard distributed objects, Java, or JavaScript
Use Web clusters for high availability of Web services, expanded security options, and more Run Domino using the IIS HTTP services
Database improvements Use transactional logging for faster restarts and data recovery
Convert to the new on-disk structure (ODS) for better performance, data integrity, and more
Easier administration Manage users, databases, and servers with the new Domino Administrator. It includes the Administration Process, a tool for analyzing
2
what you need to do to decommission a server, topology maps, and integration hooks for third-party tools to appear on the registration interface. Migrate users from cc:Mail, Microsoft (MS) Mail, Exchange, or Windows NT with the redesigned user registration. New tools for server monitoring and message management.
1.1.2 What is Lotus Notes R5?

The Lotus Notes R5 client gives you easy access to all the information that is important to you whether that information is personal (like your e-mail and calendar) or public (like your favorite Web sites and Internet news groups). The client includes a new browser-like user interface with a customizable welcome page for tracking your important daily information. It also includes improvements to the applications you use in your daily work, such as mail, calendar and scheduling, Web browsing, and discussions. The Notes R5 client is server independent, that is, you can use it with Domino R5 as well as other Internet-standard servers, such as the ones your Internet Service Provider (ISP) may use. For example, you can read and send messages to any Internet mail server, read and post topics to any Internet news group, search any Internet directory, view HTML from any Web server, and use X.509 certificates for security. The best part is that you can do all these things from within one, consistent interface without needing to know about the Internet standards involved. You simply do your work within the Notes interface, and Notes handles the rest for you. The new Lotus Notes R5 interface is more intuitive and easier to use than ever. It provides a single integrated environment to manage e-mail, appointments, tasks, key contacts, and Web information. It gives you a headlines page that helps you stay on top of your most important priorities throughout the day. Lotus Notes R5 offers powerful, new knowledge management tools. Its bookmarks help get back to information quickly. It is state-of-the-art e-mail, calendaring, group scheduling, Web access, and information management all integrated in an easy-to-use and customizable environment. Lotus Notes R5 extends the lead in integrated collaboration clients with even more Internet support and a Web-style interface that adapts to your work style plus scores of other improvements to help you work smarter and be more productive. The new look and feel of Lotus Notes R5 focuses on creating an environment that makes it easy for both new and existing users to access all of their information. This has involved adding features that help new users, such as
Lotus Domino and Tivoli Storage Management
cc:Mail and Internet mail users, feel comfortable within the Notes mail interface as well as making other existing features, such as calendar and scheduling, easier to use. Underlying both of these areas is the clients total embrace of Internet standards; so, you can work with the information that matters to you regardless of where that data is stored or what protocol is used to deliver it. Specific Lotus Notes R5 features include:
The new user interface Use the new Welcome page for instant access to your mail, calendar, and more; and, customize it to track your important information.
Create bookmarks for anything that you want to return to later, whether it is from Notes or the Internet. Navigate through open pages of information with tabs and Web-like universal navigation buttons.
Improved applications Use new mail features, such as cc:Mail-like address headers, mail rules, easier mail archiving, and others.
Get organized with enhanced calendar and scheduling features, such as tasks that follow you, improved calendar management, a group calendar, and more.
Native support of Internet standards View Internet mail messages, Web pages, and news groups with full fidelity (because of MIME and HTML support) and security (using SSL, S/MIME, and X.509 certificates).
Read and send messages from Internet mail servers (using POP3 or IMAP). Search any Internet directory (using LDAP). Read and post articles to any Internet news group discussion (using NNTP).
1.1.3 Benefits of R5
Some of the benefits of R5 are given below: Ease of use Notes makes it easy to find, sort, and manage all your work in a way that makes sense to you.
Notes works your way You can personalize the new Headlines page or customize your Bookmarks so that the information you need is the information you see. Universal In-Box Notes support for Internet Protocols lets you manage all your e-mail from one place whether its from your network or from an Internet account. One place for all information Notes is a truly integrated Internet client providing access to a world of information and helping you manage it with ease. Mobile support Whether you are in the office or on the road, you can stay connected. Notes synchronizes data with PCs, pagers, faxes, and popular hand-held devices. Easy to install and setup A simple installation of software will get you right to work. A powerful tool for any infrastructure Current Notes users can upgrade quickly and easily to take advantage of all the enhancements in Notes and Domino R5.
1.1.4 Components and platforms

The new release of Lotus Domino Server raises the standard for Enterprise messaging, groupware, and Web application development servers. It is available on all Lotus Domino Server platforms. Table 1 is a summary of the various operating systems platforms that support Lotus Notes/Domino Release 5.0.
Table 1. Available platforms for Release 5.0
Platform UNIX (AIX V 4.3.1 or higher, HP-UX 11.0, Solaris/SPARC 2.6, Solaris/Intel 2.6, Solaris 7, Linux Red Hat 6.0) OS/2 Warp Server V4.0 Windows 95/98 Windows NT Server 4.0 and Windows NT Workstation 4.0 (Alpha and Intel) Windows2000
Domino Server R5 Yes Yes No Yes
Notes Client R5 No No Yes Yes
Platform Macintosh Power PC 7.6, 8.1 AS/400 V4R2 S/390 V2R6
Domino Server R5 No Yes Yes
Notes Client R5 Yes No No
The Domino Server family consists of three core servers: 1. Domino R5 Mail Server: Combines full support for the latest Internet mail standards with Dominos industry-leading messaging capabilities. 2. Domino R5 Application Server: Is an open, secure platform optimized to deliver collaborative Web application that integrate your Enterprise system with rapidly changing business processes. 3. Domino R5 Enterprise Server: Delivers all the functionality of the Domino Mail and Application Servers reinforced with clustering for the high availability and reliability required by mission-critical applications.
1.1.5 User interfaces

The Domino client family consists of three core clients: 1. Domino Administrator Domino Administrator is the new administration client for Notes and Domino. It has a new interface with different navigation from the R4.x Administration panel. Dominos integrated platform delivers messaging and collaborative solutions for the Internet. Several key services enable IT professionals to manage and run their messaging and Web application infrastructures easily and efficiently. The new R5 Domino Administrator makes it faster and easier for administrators to manage users, configure systems, and optimize performance all from an intuitive user interface. The Domino Administrator is shown in Figure 1.
Figure 1. Domino Administrator client
2. Domino Designer Domino Designer is an integrated development environment. It enables developers to rapidly build secure Web applications that incorporate Enterprise data and streamline business processes. The basic interface of a Domino Designer is shown in Figure 2.
Figure 2. Domino Designer client
3. Notes Client The Notes Client provides the interface that allows a Lotus Notes user to access shared databases for e-mail and other collaborative computing applications. The client user interface has been significantly enhanced and redesigned in R5 and is shown in Figure 3.
Figure 3. Lotus Notes client
One of the major differences between the appearance of the R4 and R5 notes clients is the R5 client Welcome page which is the first page the end-user sees when starting Notes. It provides instant access to mail, calendar, and more and can be customized to suit individual preferences. The R5 Notes client can create bookmarks for anything that you want to return to later, either from Notes or the Internet. Navigation through open pages of information is via tabs and Web-like universal buttons. While the interface has changed, you can still use the legacy Notes workspace from the previous releases of Notes. The Notes R5 client is server independent, that is, you can use it with Domino R5 as well as other Internet-standard servers. The best part is that you can do all these things from within one, consistent interface without needing to know about the Internet standards involved. You simply do your work within the Notes interface, and Notes handles the rest for you. See Table 2.
Table 2. User interface features
UI Features Welcome page
Description Start on the Welcome page for all your important information. The Welcome page contains some basic tasks, and you can customize it in these ways: Instant access to mail, calendar, and to-do lists Customize the page to see your latest mail messages and appointments at a glance Add your favorite Web sites or news groups Instant search of Web sites, local documents, or databases A Notes Tour See Whats New
Bookmarks Navigation
Create bookmarks for anything you want to return to later whether its from Notes or the Internet. Navigate through open pages of information with tabs and Web-like universal navigation buttons.
10
1.1.6 Administration
Lotus Domino R5 makes server administration much easier compared to Lotus Domino R4. You still have the standard server console interface shown here.
Lotus Domino (r) Server, Build V5010707, 07 July 1999 Copyright c 1985-1999, Lotus Development Corporation, All Rights Reserved Restart Analysis: 100% 02/24/2000 10:22:23 AM Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery) The ID file being used is: c:\lotus\domino\senegal\server.id Enter password (press the Esc key to abort): 02/24/2000 10:25:10 AM Mail Router started for domain ALMADEN 02/24/2000 10:25:10 AM Router: Internet SMTP host senegal in domain almaden.ibm.com 02/24/2000 10:25:15 AM Database Replicator started 02/24/2000 10:25:20 AM Index update process started 02/24/2000 10:25:25 AM Agent Manager started 02/24/2000 10:25:25 AM JVM: Java Virtual Machine initialized. 02/24/2000 10:25:31 AM AMgr: Executive '1' started 02/24/2000 10:25:30 AM lochness/Almaden is the Administration Server of the Domino Directory. 02/24/2000 10:25:31 AM Administration Process started 02/24/2000 10:25:35 AM Calendar Connector started 02/24/2000 10:25:40 AM Event Dispatcher started 02/24/2000 10:25:44 AM Releasing unused storage in database statrep.nsf... 02/24/2000 10:25:45 AM Schedule Manager started 02/24/2000 10:25:47 AM SchedMgr: Validating Schedule Database 02/24/2000 10:25:48 AM SchedMgr: Done validating Schedule Database 02/24/2000 10:25:50 AM Stats agent started 02/24/2000 10:25:55 AM Database Server started
However, there is also a new dedicated Domino Administrator client as shown in Figure 1 on page 7. Most Notes administration is done by using the Domino Directory, which was previously called the Names and Address Book (Public Address Book). The new Lotus Domino Directory has a similar interface to Lotus Domino R4. The new Domino Directory is shown in Figure 4.
11
Figure 4. Domino Directory
1.1.7 Notes data

The Notes database is the basic component of a Notes application. It is a repository where users create, update, store, and track documents in various formats.A Notes Database is stored on a server or client as a single notes structure file with a .nsf extension. Besides the Notes databases themselves, there are other non-database files used for configuration, identification and other purposes. Here is a list of database and non-database files which are part of any Notes environment: notes.ini This file is the notes server and client initialization file that defines various configuration and performance variables.
12
names.nsf This file is the server Domino Directory. It is the central repository for address and server configuration information for users, groups, and servers within a Notes domain. log.nsf This database is automatically created to record and store information about all types of Notes server activities and remote client communication activities. cert.id The certifier ID file is used to create new Notes user and server ID files and to cross-certify existing servers, users and other certifier ID files. server.id This server id file is used to start and run the Domino Server. user.id This id file identifies the Notes user when accessing a Domino server. desktop.dsk This is the configuration file for the Notes workspace. catalog.nsf This database catalog lists all public databases. It records and stores information about the databases on a Domino Server. mail.box This file is the Notes mail-router mail box. ..\mail\user.nsf This is a users mail database. It is used to send and receive electronic mail using Notes. In a large Notes environment, there will be several mail subdirectories including mail databases for all users.
1.1.8 Transaction logging

One of the major new functions of the R5 Domino server, which relates particularly to how the databases can be backed up and restored, is the introduction of transaction logging. 1.1.8.1 Database transactions in R4 Prior to R5, database-specific transactions (or operations) such as creating, modifying, or deleting documents; updating views; or changing database attributes required that the operation commit to disk before being
13
considered successful. In other words, the transaction was either successful or failed; there was no middle ground. Even when you used database buffers (such as, the NOTES.INI setting NSF_BUFFER_POOL), the transaction and its data were still required to be committed to disk. On an active server, the actual writing to disk could be a lengthy process. Modifications could occur on different parts of a database or across multiple databases. Then, the server's disk head had to move randomly over all areas of the disk to get to the proper track and sector for the data that was changed or updated. Repositioning the head in this "random" manner added to the total time required to complete a transaction. So, as the number of database users on an R4 server increased, so did the number of transactions as well as the average transaction completion time. Waiting for commits to complete (as opposed to returning from the operation and "trusting" that the system would eventually get the data to disk) was necessary so that in the event of a system failure, the fixup task could fix the databases and restore them to a "clean" state. 1.1.8.2 Transaction logging in R5 Transaction logging in Domino R5 is a new method of writing out database changes to improve performance and to ensure data integrity. With transaction logging, Domino posts transactions (or writes) to a series of transaction log extents before allowing any updates to the database. Each Domino server or partition on a server has a dedicated transaction log which is shared among all the logged databases. A transaction log consists of one or more transaction log extents, which are files that have a .txn extension. These files are used to store the transactions as they are made. The log extents are automatically allocated and named as required by the server, once transaction logging is enabled. Successfully posting to the log is also considered a commit (the data is safely stored to persistent storage), allowing the database operation to complete and continue. The transactions and their data are written to the actual database from the log at some point in the future. In the event of a system failure, transaction log recovery can apply or undo only those transactions not written to disk at the time of the failure. 1.1.8.3 Benefits of transaction logging The biggest benefit of writing to the log first, then writing to the database is that all writes to log extents are sequential in nature. Therefore, there is less head movement on the data disk(s), resulting in faster commits to disk. Why is there less head movement? Quite simply, random access is slower than sequential access. As mentioned above, random access requires the disk head to move randomly over the disk to find the proper data points. With sequential access, the disk head can move directly to the next available track on the disk.
14
Transaction logging provides three main benefits: In most situations, you no longer need to run the fixup task to recover databases following a system failure. Excluding fixup results in quicker server restarts, since fixup must check every document in each database, while transaction log recovery applies or undoes only those transactions not written to disk at the time of the system failure. Transaction logging can improve server performance in most cases. It saves processing time, because it allows Domino to defer database updates to disk during periods of high server activity. Transactions are recorded sequentially in the log extents, which is much quicker than database updates to random, nonsequential parts of a disk. Because the transactions are already recorded, Domino can safely defer database updates until a period of low server activity. Using transaction logging simplifies your daily backup procedure. You can use a third-party backup utility to perform daily incremental backups of the transaction log extents (if using archive transaction logging), rather than always requiring full database backups. To use all of the features of transaction logging and recovery, you need a third party backup utility that supports Domino Release 5 and transaction logging, such as Tivoli Data Protection for Lotus Domino, used with Tivoli Storage Manager. 1.1.8.4 Transaction logging modes There are two different modes when using transaction logging enabled: Circular: This is the default mode when transaction logging is enabled. The Domino server continuously reuses the same log file which is defined at a designated size and overwrites old transactions once the transaction log is filled to capacity. You are limited to restoring only the transactions stored in the transaction log. Archiving of transaction logs is not possible if circular transaction logging is used. Archive: This is the recommended mode. All transactions are written to the active transaction log extent. The active transaction log extent contains only the transactions necessary for a restart recovery. Once all changes in the active transaction log extent have been committed to the database, it is termed inactive and can be archived using a third-party utility. The backup utility queries the log extents to determine which need backing up and then reports when the backup is complete so the log extent can be reused. The Domino server does not reuse the log extents until they are archived. When Domino starts using the existing space again, it increments the log file name. If all the log files become inactive and are not archived, Domino creates additional log files. When used with an appropriate backup utility (such as Tivoli Data Protection for Lotus
15
Domino), archive logging will enable rollback, media recovery, and point-in-time of the databases.
Important note
In order to achieve performance improvement with transaction logging, the transaction log must be on a separate physical drive from the databases themselves. If this is not done (that is, if the same physical or logical drive or partition is used to locate both the transaction log and the databases), performance may actually degrade. We also highly recommend for you to mirror the log device, and if possible, use a dedicated disk controller. More detailed information on the operation of transaction logging for R5 and setup recommendations is available from Lotus Customer Support at http://support.lotus.com. You should look particularly at the Technical Papers, Transaction Logging in Domino R5, 172508; Transactional Logging and How it Operates, 179858; and Circular Versus Archive Transactional Logging in Domino 5.x, 179363. To find any of these articles, you can enter the article number in the Search by Keyword box, specifying to Search the Lotus Knowledge Base. 1.1.8.5 Transaction logging and the database instance ID Because a logged transaction is relative to the database version to which it is applied, there needs to be a way to associate transaction logs with the right database. This mechanism is called the database instance ID or DBIID. When you enable transaction logging, Domino assigns a DBIID to each Domino R5 database. When a transaction is recorded in the log, it includes the DBIID. During recovery, Domino uses the DBIID to match transactions to databases, that is, it identifies which database the changes should be applied to. The DBIID is stored in the file header, along with the database ID and the replica ID. There is no connection between the DBIID and database ID or the replica ID. Some database maintenance activities, such as compaction with certain options, cause Domino to assign a new DBIID to a database. From that point onward, all new transactions recorded in the log use the new DBIID; however any old transactions will still have the old DBIID recorded which will not match the current DBIID. As a result, Domino cannot restore these old transactions to the database. To avoid losing data, you should immediately perform a full database backup whenever a databases receives a new DBIID. When you perform this backup, it will reflect all the database transactions up until that point and ensures that Domino needs only the new transaction (with the new
16
DBIID) to restore the database. If the DBIID changes and a backup is not taken immediately after that, the database will not be able to be successfully restored, since the DBIID of the database and the transactions in the log will not match. We discuss the DBIID in more detail, and the operations which cause it to be changed in 4.1.2, Changing the database instance identifier on page 111.
1.1.9 Backup API of R4 and R5

Backing up application specific databases, as opposed to normal files, should be done wherever possible via an API provided by the application vendor. This ensures that the backup product can use the full capabilities and intelligence of the product and be fully application-aware. In a Tivoli Storage Management environment, Notes R4 databases are backed up using the Tivoli Data Protection for Lotus Notes product. R5 databases are backed up using the Tivoli Data Protection for Lotus Domino product. R4 databases cannot be backed up or restored using TDP for Domino, and R5 databases cannot be backed up or restored using TDP for Notes. The functionality of the two TDP products is somewhat different. In particular, TDP for Lotus Notes had the ability to backup only the changed documents in a database and to restore individual documents to a database. This was achieved using a Lotus Notes R4 API which was not actually specifically designed to be used for backup and restore, since there was no other API available. While many customers found this document level backup and restore facility to be very useful, in practice, the API that was used often did not scale well for larger databases. In particular performance could be slow when doing document level backup and restore, where the database contained a large number of documents. Where performance of document level incremental backup became too slow, customers implemented a method where they used the TDP for Notes application for backup during the week. On the weekends, they would shutdown the Notes databases and use the backup/archive client to take a full offline baseline backup. This clearly impacted their ability to provide 24 hour availability of their databases to the end users and complicated the backup process. Lotus Domino R5 introduces some significant changes in the Notes server architecture. These include a new application program interface (API) specifically for backup and recovery of R5 databases. This enables third-party vendors to design a backup utility to use this new backup and recovery API in Lotus Domino R5 to provide online backup and restore capabilities. The Tivoli Storage Management backup solution for Lotus Domino R5 uses these APIs.
17
Specifically the APIs allow the backup product to perform these functions: Online backup R5 databases Maintain multiple backup versions of R5 databases Archive transaction log extents (if archival logging is used Restore any backup version of an R5 database and apply changes since the backup from the transaction log Restore R5 databases to a specific point in time Restore one or more archived transaction logs Expire database backups automatically based on version limit and retention period Inactive archived transaction log extents when they are no longer needed for restore Automate scheduled backups Document level backup and restore is no longer available with TDP for Lotus Domino. This is because the Lotus R5 API does not provide this function and the previous R4 method is no longer available, mainly because of the performance implications mentioned above. Instead, the new functionality provided should allow more scalable performance on both backup and restore, as well as the flexibility of point-in-time and roll-forward restore. Also, it should eliminate the requirement to take periodic offline Domino database backups using the backup/archive client. An individual Notes document can still be restored in Domino R5 by restoring the entire database to an alternate name and then copying the desired document back to its required location using the Notes client. There is an alternative function available within the Domino server which can greatly reduce the requirement for providing document level restores for users in the backup product. New options in the Domino R5 server allow databases to be configured so that the user can restore deleted documents for a specified amount of time by accessing them in a special view. By setting the soft delete database option and creating this view, mistakenly deleted documents can be restored to their original location simply and quickly. This feature is completely external to and independent of the backup operation. We describe it in detail in Appendix A, Creating a recycling bin in Domino R5 on page 139.
18
1.1.10 Storage management of Notes

Providing effective storage management services for a Notes Domino system can be a demanding task. All nondatabase Domino data comes under your general storage management policy. Regular backups need to be run against frequently updated data. The challenge with Domino, however, is the storage management of Domino databases. Domino databases are complex logical structures, often very large, that appear to traditional storage management tools as single client files. A backup tool that operates only at the operating system level will always back up the entire database. Whenever a single document is updated within a database, an incremental backup would catch the entire database since the modification time stamp of the database has changed. This leads to an enormous amount of data and backup copies on the storage location. Domino itself provides a function for database protection: replication. Replication is the process of updating databases that reside on different servers and clients within a Domino environment, simultaneously. Updates to a database can be reflected on all database copies wherever they physically reside. This update works on a document level. If a database or a document within a database is accidentally deleted, it can be recovered as long as a replication database copy is available elsewhere in the Domino environment. However, replication is not a substitute for an effective backup solution. Replication will duplicate user errors throughout a Domino network. If a critical document or database is erased by accident, replication will, in time, erase that same information wherever it is replicated. With the introduction of transaction logging in R5 another storage management requirement arises you need to regularly back up both the logged databases and the transaction log since transaction logging is an integral part of recovering from system and media failures. A system failure causes the server to stop and requires you to start the server. During the start, Domino automatically performs database recovery. The system uses the transaction log to apply or undo database transactions not written to disk for databases that were open during the system failure. A media failure causes databases to be damaged or lost. To recover, you need to restore a database backup and archived transaction log extents, which are then applied to the database.
1.2 Introducing Tivoli Storage Management

Tivoli Storage Manager is the core application of the Tivoli Storage Management solution set. Tivoli Storage Manager is an enterprise-wide
19
storage management application for the network. It provides automated storage management services (including backup and restore, archive and retrieve hierarchical space management and disaster recovery) to multivendor workstations, personal computers, mobile laptops and servers of all sizes and operating systems, which are connected via WAN, LAN, and SAN. Tivoli Storage Manager includes these components: Server Provides backup, archive, and space management services to its defined clients. The server maintains its own database and recovery log for information about Tivoli Storage Manager resources, users, and user data including all backed-up, archived and migrated files. The client data itself is stored in server-controlled entities called storage pools. These are groups of random and sequential access media that store backed-up, archived, and space-managed files. The Tivoli Storage Manager server is responsible for maintaining the integrity of client sessions, reliably receiving client data, storing client data in storage pools, and efficiently managing that data internally so that it can be restored or retrieved when required. You can set up multiple servers in your enterprise network to balance storage, processor, and network resources. Tivoli Storage Manager allows you to manage and control multiple servers from a single interface that runs in a Web browser (the enterprise console). Administrative interface Allows administrators to control and monitor server activities, define management policies for client files, and set up schedules to provide services at regular intervals. Administrative functions are available from an administrative client command line and from a Web browser interface. A server console is also available. Backup/archive client Allows users to maintain backup versions of their files, which they can restore if the original files are lost or damaged. Users can also archive files for long-term storage and retrieve the archived files when necessary. A command line interface, native GUI interface, and Web browser interface are available for the backup/archive clients. Application program interface (API) Allows users to enhance existing applications with backup, archive, restore, and retrieve services. When users install the Tivoli Storage Manager API client on their clients, they can register as client nodes with a Tivoli Storage Manager server.
20
The Tivoli Storage Management solution set also includes the following client programs: Tivoli Data Protection for applications (application clients) Allows users to perform online backups of data that is used by particular applications such as database programs. After the database initiates a backup or restore, the application client uses the API to interface to Tivoli Storage Manager. The Tivoli Storage Manager server then applies its storage management functions to the data. The application client can perform its functions while users are working, with minimal disruption. Tivoli Data Protection clients are available for Oracle, Informix, SAP R/3, Lotus Notes R4, Lotus Domino R5, MS Exchange and MS SQL Server. Tivoli Space Manager (hierarchical storage management client) Provides space management services for clients on some platforms. Tivoli Space Manager users can free client storage by migrating less frequently used files to server storage. These migrated files are also called space-managed files. Users can recall space-managed files automatically simply by accessing them as they would normally. You can learn more about Tivoli Storage Manager in Tivoli Storage Management Concepts, SG24-4877. Tivoli Disaster Recovery Manager Tivoli Disaster Recovery Manager automatically generates a disaster recovery plan containing the information, scripts, and procedures needed to automate restoration to help ensure quick recovery of your data after a disaster. It automatically manages and tracks the media on which your data is stored, whether on-site, in-transit, or off-site in a vault, so your data can be easily located if disaster strikes.
1.2.1 Tivoli Storage Manager backup/archive client

The Tivoli Storage Manager backup/archive client is designed to back up and restore, archive and retrieve client file system data. The client therefore can back up any nondatabase and database Notes Domino data on both Notes server and client. Tivoli Storage Manager clients use standard operating system functions to access files within file systems, but they do not understand any logical structure that might exist within a file. This is not a limitation only of Tivoli Storage Manager; all other client backup products that work at the file system level are similarly limited. These limitations affect how Domino and other database systems are backed up. Each database appears as an individual file with .nsf extension on the server or client file systems. A Tivoli Storage Manager backup/archive client
21
running on a Domino server or client can back up and restore, archive and retrieve entire Domino databases. It cannot back up smaller increments. Tivoli Storage Manager clients can be installed wherever there are Domino databases that require backing up. However, that approach could potentially lead to large numbers of duplicate database backup copies if Domino replication is also being used. A more sensible approach is to implement Tivoli Storage Manager clients on Domino servers only. If possible, identify those databases on the servers that are replicas from other servers and exclude them from backup. This approach assumes that backups of those databases have already been performed at the originating database server. Other than the issues of size and replication, using a Tivoli Storage Manager backup/archive client to back up Domino databases is straightforward. Each database is a self-contained NSF file that is backed up and restored. Tivoli Storage Manager restores a database in its entirety because it is just a file for Tivoli Storage Manager. If a database is deleted or corrupted, it is a simple task for Tivoli Storage Manager to restore the most recent or any previous backup version of this database from the Tivoli Storage Manager server to the Domino server or client. The Tivoli Storage Manager backup/archive client, however, does not meet all requirements for an ideal storage management solution in a Domino environment. Drawbacks when using the Tivoli Storage Manager backup/archive client are: Consider a 5 GB database that changes everyday. The Tivoli Storage Manager backup-archive client will back up the full 5 GB even if only a 2 MB document has changed. You waste a lot of storage space using this strategy. Some databases like the Domino Directory, names.nsf, need to operate twenty four hours a day, seven days a week, and are likely to be constantly locked by Lotus Domino. The Tivoli Storage Manager backup-archive client is not able to override the locking mechanism of Lotus Domino, and therefore does not back up the database. An alternative is to shut down the Lotus Domino server, and take backups of all selected databases. This will result in server unavailability, which is not good for business.
1.2.2 Tivoli Data Protection for Lotus Domino

The TDP for Lotus Domino application client provides an integrated solution for performing full backup and restore operations on Lotus Domino R5
22
databases and database templates. It is a client application that provides full backup of online databases and restore of full databases to the original or different location. TDP for Lotus Domino also archives the transaction log extents of a Domino server and retrieves the appropriate transaction log extents for the recovery of databases if archive transaction logging is enabled on the Domino server. It is supported on these platforms: Microsoft Windows NT and Windows 2000 (on Intel) IBM AIX Sun Solaris IBM S/390 USS
TDP for Lotus Domino is not intended as a substitute for the standard Tivoli Storage Manager backup/archive client. TDP for Domino cannot be used to back up or restore any non-database data, such as Notes ID files, or notes.ini, or any other system configuration files. Those files need to be backed up by the Tivoli Storage Manager backup/archive client. Therefore, the two client types work together to provide full data protection for your Notes environment. The TDP for Lotus Domino application client and the Tivoli Storage Manager backup/archive client can run simultaneously on the same Domino server, however, they are totally separate clients as far as the Tivoli Storage Manager server is concerned. TDP for Lotus Domino provides the following actions and operations: Perform full backup of online databases (.nsf) and templates (.ntf). Perform conditional full backup, incremental backup of entire databases. Archive of transaction log extents, if archive transaction logging is enabled on Domino server. Restore any backup version of a database and apply changes since the last backup from the transaction log. Restore a database to a specific point-in-time. Restore a database to another Domino server. Restore individual archived transaction logs. Expire database backups automatically based on version limit and retention period. Expire archived transaction log extents when no longer needed for the recovery of database backup versions.
23
Queries of backed up databases, archived transaction log extents, and Tivoli Storage Manager server information. Queries of Domino databases and server information. Query and change of current values set in the preference file for TDP for Lotus Domino. Change of TDP client password. The TDP for Lotus Domino application client provides a command line interface for performing backups and restores. The application client commands are issued from a command prompt. On Windows NT, TDP for Lotus Domino also provides a GUI which supports most of the functions of the application client. Unlike the Lotus Notes R4 API, Lotus Domino R5 uses an API specifically developed for backup and restore purposes. This API increases performance and reduces backup times. Figure 5 illustrates the logical components of the TDP for Lotus Domino application client.
Domino R5 server
Transaction log
Domino API TDP for Lotus Domino
Tivoli Storage Manager server

TSM API
Domino R5 databases
Figure 5. Logical components of TDP for Lotus Domino
24
Chapter 2. Configuring storage management for Lotus Domino

In this chapter, we describe the test environment used in this project. Then, we discuss installation and configuration of the various components of a Tivoli Storage Management data protection solution for Lotus Domino servers on various platforms, including the TDP application clients, the Tivoli Storage Manager server and backup/archive client, and operation scheduling. Finally, we mention special considerations when running Domino in a partitioned or clustered environment.
2.1 Project test environment

Obviously, there are many very different Domino environments in real life. In this redbook, we cannot provide Domino backup solutions for all of these. During the project, we built a sample environment which enabled us to simulate a typical midsize Domino environment. This typical environment is illustrated in Figure 6 on page 26. In this environment, we implemented a server replication method which is based on a common concept, called hub and spoke. The hub and spoke method uses a central Domino server (hub) that schedules and initiates all replication with the other spoke servers. Using this method, we can allow the same databases to be updated simultaneously on different servers and then replicated with the hub server, the hub server keeps the updated database which includes all changes done at spoke servers. This updated database can be replicated back to spoke servers to maintain consistent images of the database. We implemented various Domino functions, trying to cover a complex Domino scenario as practically as possible. We created partitioned and clustered servers using Domino Enterprise server installation. We populated all servers with mail databases for several users and various application databases. Partitioned servers share the same binary files and therefore run at the same version. However, they have individual Domino data directories that allow for independent configuration of resources. In our test environment, we created two partitioned servers on both Windows NT and on AIX systems. We interconnected two Domino Enterprise servers to provide high availability, scalability, and load balancing to Lotus Notes users. This is achieved by placing multiple replicas of all databases onto different servers within the cluster. This cluster was formed between two Windows NT servers.
25
In our projects Domino environment, we implemented all the different modes of transaction logging: some servers had transaction logging disabled and some had circular transaction logging enabled. For most of our Domino servers, we enabled archive transaction logging, because this is the recommended mode. With this feature enabled, the system captures database changes and writes them to the transaction log. Then if a system or media failure occurs, you can use the transaction log and a third-party backup utility to recover your databases. A single transaction is a series of changes made to a database on a server. For example, a transaction might include opening a new document, adding text, and saving the document.
Figure 6. Project test environment
In this environment, we have the following servers: lochness. This is the first server in the domain Almaden, also called the hub, running on a Windows NT server. This server is host to the original Domino directory, names.nsf. All updates to the names.nsf database are
26
nedamlA/kawew
nedamlA/oykot
nedamlA/ssenhcol
0.4 revreS TN 0.4 revreS TN
retsu lC O STI
BUH
EKOPS
2.3.4 xiA
EKOPS
EKOPS
sesserdda PI elpitlum htiw revres denoititraP

nedamlA/airotciv nedamlA/analap
0.4 revreS TN
EKOPS
nedamlA/tocrahc
nedamlA/lagenes
KOP/eo76cstw
6R2V 093/SO
made at the hub. These updates are then replicated to all the spokes. This server also hosts mail databases and it has archive transaction logging enabled. palana. This is a spoke server in the Almaden domain, running on AIX. It receives replicas of the names.nsf database from the hub. This server houses mail and applications databases, and it also is a partitioned server with archive transaction logging enabled. victoria. This is a spoke server in the Almaden domain, running on AIX. It receives replicas of names.nsf database from the hub. This server houses mail and applications databases, and it also is a partitioned server and shares the hardware and devices with server palana. It is running with transaction logging disabled. wtsc67oe. This is an additional server in a different domain running on OS/390 USS. It is not a part of the Almaden hub and spoke replication configuration. This server houses mail and applications databases. It is running transaction logging disabled. senegal. This is a spoke server in the Almaden domain, running on a Windows NT server. It receives replicas of the names.nsf database from the hub. This server houses mail and applications databases, and it also is a partitioned server with archive transaction logging enabled. charcot. This is a spoke server in the Almaden domain, running on a Windows NT server. It receives replicas of names.nsf database from the hub. This server houses mail and applications databases, and it also is a partitioned server and shares hardware and devices with the server senegal. It is running with circular transaction logging enabled. tokyo. This server is a member of the ITSO Domino cluster, running on a Windows NT server. All members of the cluster have the same version of the database in each server. They would normally have a private network between them, but in our environment it was not necessary, because the replication traffic is light. In addition, we scheduled replication 24 hours a day, seven days a week, at an interval of 60 minutes. It is running transaction logging disabled. wewak. This server is the other member of the ITSO cluster, running on a Windows NT server. It is running transaction logging disabled.
Configuring storage management for Lotus Domino
27
Table 3 summarizes our Domino servers of the projects environment.

Table 3. Project DOMINO server systems
Hostname palana victoria wtsc67oe senegal charcot lochness tokyo wewak
System Operation Aix 4.3.2 Aix 4.3.2 OS/390 USS V2R6 NT Srv. 4 NT Srv. 4 NT Srv. 4 NT Srv 4 NT Srv 4
Transaction Log archive circular disabled archive circular archive disabled disabled
Partition Yes Yes No Yes Yes No No No
Cluster No No No No No No Yes Yes
2.2 Installation considerations

You use the standard operating system installation method to install TDP for Lotus Domino. In this section, we provide some additional guidelines and suggestions for installation. For detailed information on hardware and software requirements and installation procedures, refer to the appropriate manuals: Tivoli Data Protection for Lotus Domino for UNIX V1R1: Installation and Users Guide, SH26-4088 Tivoli Data Protection for Lotus Domino for Windows NT V1R1: Installation and Users Guide, GC26-7320
2.2.1 What to back up?

TDP for Lotus Domino is an application that backs up and restores Lotus Domino databases, Domino templates, and transaction logs. It does not provide a complete data protection solution for a Domino server, because there are many other files that are part of a Domino installation. We discussed the complete Domino data environment in 1.1.7, Notes data on page 12. These non-database files can be backed up using the Tivoli Storage Manager backup-archive client, for example: notes.ini desktop.dsk All .id files
28
We will describe in later sections how to perform this operation and how to coordinate this with database backup using TDP for Lotus Domino.
2.2.2 Where to install?

TDP for Lotus Domino must be installed on the same hardware where each Domino server Release 5.01 or later is installed. It also needs the Tivoli Storage Manager application program interface (API) to communicate with Tivoli Storage Manager server. This API is actually part of the Tivoli Storage Manager backup-archive client package and will probably already be available on the Domino server if the backup-archive client has been previously been installed. If not, the API is also included on the installation media for TDP for Domino. This means that installing the complete Tivoli Storage Manager backup-archive client is not required in order to run TDP for Domino. However, it is generally recommended to install the backup-archive client on Domino servers, so that non-database files can be backed up and restored (we already discussed this in 2.2.1, What to back up? on page 28). The backup-archive client is also used to enable TDP for Domino operations to scheduled (see 2.6, Scheduling TDP for Lotus Domino on page 45 for more information). TDP for Lotus Domino normally is normally required to run using the same operating system user ID or account which the Domino server runs under. In cases where you run the Domino server as an NT or Windows 2000 service, use an operating system. Often this will be the Administrator account, but it could be another account with the appropriate authority. Personal copies (replicas) of Domino databases that are stored on Notes clients are not protected by TDP for Lotus Domino. If you want to specifically protect these database replicas, you can either use the local Tivoli Storage Manager backup-archive client (if installed) to backup and restore these files, or simply start a new replica from the server if one of these databases is somehow destroyed.
2.2.3 Silent installation

Administrators can install TDP for Lotus Domino for Windows NT using silent installation. A silent installation runs on its own, without any user intervention, so administrators are free from the task of monitoring the installation and providing input to dialog boxes. This method is especially useful when TDP for Lotus Domino must be installed on a number of computers with identical hardware. For example, a company may have twenty five Domino servers spread out across twenty five different sites. To ensure a consistent configuration and to avoid having twenty five different people enter TDP for
29
Lotus Domino parameters, an administrator may chose to produce an unattended installation and make it available to the twenty five sites by burning and sending out 25 CDs or by placing the unattended installation package on a file server. To perform a silent installation of TDP for Lotus Domino for Windows NT, run setup -r from the installation directory. When you have finished, a response file setup.iss will have been created in the C:\WINNT directory. To use this on another system for silent installation, copy this file to that system, to the TDP installation directory and run setup -s. Note, setup.iss must exist in the same directory as setup.exe. See Appendix B of Tivoli Data Protection for Lotus Domino for Windows NT V1R1: Installation and Users Guide, GC26-7320, for more information on silent installation.
Note
We found while testing silent installation that selecting Custom installation does not correctly create the setup.iss response file when using the TDP for Lotus Domino version 1.1.0.0. If you are using this code level, you should choose Compact or Typical installation. Otherwise, use the PTF level of TDP for Lotus Domino which fixes this problem.
2.2.4 Migrating from Lotus Domino R4

With the release of Domino R5, Lotus implemented a new design for Domino databases. The R5 databases include a new API which is developed especially for backup and restore operations. We have already discussed (in 1.1.8, Transaction logging on page 13) how with R5, transaction logging is available for databases as a new recovery feature. Although R4 and R5 databases are differently designed and implemented you can replicate them across servers of different releases. When replicating a R4 database to a R5 Domino server, the server runs an automatic task to adjust the downlevel database to R5. Tivoli provided a special application client for backing up Lotus Notes R4 databases to a Tivoli Storage Manager server. This was Tivoli Data Protection for Lotus Notes, formerly known as the ADSM Connect Agent for Notes. This product is discussed in detail in Using Tivoli Storage Manager to Back Up Lotus Notes, SG24-4534. Both TDP application clients, TDP for Lotus Notes and TDP for Lotus Domino, interconnect with the API of the corresponding Lotus database release. However, they are not compatible with either each other or the other
30
Lotus release. This means that you cannot back up or restore R5 databases using TDP for Lotus Notes R4, nor can you back up or restore R4 databases using TDP for Lotus Domino R5. Therefore, when migrating the Domino environment from R4 to R5, you also need to migrate your backup solution. This has the following consequence when you are migrating from Domino R4 to R5 and you were previously using TDP for Lotus Notes for backup: If you were using TDP for Lotus Notes for your R4 databases, you cannot restore those databases using TDP for Lotus Domino. For a more detailed discussion plus some suggestions for migration in replicated and non-replicated environments, see the appropriate platform Installation Guide for the TDP application client (listed in page 28).
2.3 Setting up Tivoli Storage Manager

In this section, we discuss all the steps necessary to configure your environment to work with TDP for Lotus Domino. These comprise the configurations on Tivoli Storage Manager Server, on Tivoli Storage Manager backup-archive client, on TDP for Lotus Domino, and on the Domino server.
2.3.1 Tivoli Storage Manager server

We assume that your Tivoli Storage Manager server is already installed and configured for backup and restore. If this is a brand new installation you will need to perform this configuration first. Assistance with this can be found in the product documentation and other ITSO Tivoli Storage Manager redbooks (see list in C.1, IBM Redbooks on page 149 and C.3, Tivoli Storage Management publications on page 150). Once this is complete, you can extend your environment to enable backup of the Domino servers by defining appropriate policies, registering nodes, and modifying the backup/archive client configurations. 2.3.1.1 Policy Definition TDP for Lotus Domino works similarly to the Tivoli Storage Manager client for databases that do not have transaction logging enabled. That is, when we take a backup of this type of database a complete version of the entire database will become a new backup version. If you are using archive transaction logging, then each archived transaction log file contains changes to one or more logged databases over a period of time. Each of these transaction log files has a unique name, so you will never have multiple versions of the same log file on the Tivoli Storage Manager server. Because
31
of this difference, TDP for Lotus Domino requires special Tivoli Storage Manager policy settings. Here, we explain these policy settings in detail: It is recommended that you define and use a separate policy domain for your Domino backups. Register all your Domino nodes in that domain. An Archive Copy Group is not necessary in the policy domain, because TDP for Lotus Domino stores all files as backup files. It can still exist in the policy domain, if there is any other requirement for it. There are some parameters in a copy group that should be left as default, because they are not used for TDP for Lotus Domino. The parameters are: frequency, mode, and serialization. All the version controls from Tivoli Storage Manager server are applied on databases that are backed up using TDP for Lotus Domino. You can set verdeleted, verexist, retonly, and retextra parameters according to your retention requirements. Archived transaction log files never expire due to version limits, because they have unique names (that is, multiple versions of the same file will never be created).The only way to expire transaction logs files is through the use of the inactivatelogs command that will inactivate a transaction log file when all databases that require that file for a complete recovery are also inactive.The inactive transaction log files will be expired after the retention period has passed. Since this period should be equal or greater than the retention period for database objects, you should use the same management class for both. You will see two different file spaces in your Tivoli Storage Manager server for TDP for Lotus Domino nodes, one for databases and another one for transaction logs. You should consider use of collocation to optimize the restore if they are stored on a sequential media.
Note
If you choose to use a non-default management class for TDP for Lotus Domino, you will need to add an include/exclude statement in the TDP for Lotus Domino option file to bind all objects to that management class. For example:
include * TDP_CLASS
Figure 7 shows the Tivoli Storage Manager server policy for our test environment.
32
Figure 7. Tivoli Storage Manager setup: management classes
We define one policy domain, DOMINO, for all Domino servers. We create a policy set for this domain, DOMINO_SET, where we define two management classes: TDP_CLASS is used for all Domino databases, transaction logs, and templates. These files will be backed up using TDP for Lotus Domino. Tivoli Storage Manager_CLASS is used for all other data backed up daily. This include all general system data and Notes nondatabase data. These files will be backed up using Tivoli Storage Manager backup-archive client. 2.3.1.2 Node Name Before starting to backup your environment, you must register a node for TDP for Lotus Domino in your Tivoli Storage Manager Server. If you already have registered a node for your Tivoli Storage Manager backup-archive client, an additional node will be necessary. In a UNIX machine, if your system already
revres reganaM egarotS iloviT

TES_ONIMOD :teS yciloP
ssalC_PDT :ssalC .ganaM
puorG ypoC pukcaB
puorG ypoC pukcaB
ssalC_reganaM egarotS iloviT :ssalC .ganaM
ONIMOD :niamoD yciloP

33
has a node name assigned to the Tivoli Storage Manager backup-archive client, we recommend creating a separate stanza in the dsm.sys system options file for TDP for Lotus Domino. See 2.4.4, TDP for Domino on UNIX option files on page 40 for more information. Figure 8 shows the node names on one of the Domino Server machines running on Windows NT. Both these node names are registered in the DOMINO policy domain.
machine: lochness
node names : backup-archive client - lochness TDP for Lotus Domino - lochness_tdp
Figure 8. Node names on Domino server machine
2.3.2 Tivoli Storage Manager backup-archive client

We use the Tivoli Storage Manager backup/archive client for backing up non database files. Figure 9 shows the GUI interface of Tivoli Storage Manager backup/archive client on a Windows NT machine. The client is configured by options files, which are by default in the client executable directory.
34
Figure 9. Tivoli Storage Manager Backup/Archive client
2.3.2.1 Option files for UNIX For UNIX, the Tivoli Storage Manager backup-archive client options reside in two separate options files, the client system options file (dsm.sys) and the client user options file (dsm.opt). Either the Tivoli Storage Manager administrator or the end users themselves setup these files when the Tivoli Storage Manager backup-archive client is first installed on the users workstation. See Tivoli Storage Manager Installing the Clients, SH26-4102, for more information.
35
2.3.2.2 Option files for Windows NT For Windows NT, the Tivoli Storage Manager backup-archive client options reside in the dsm.opt file. 2.3.2.3 Include-exclude lists An include/exclude list contains statements that identify any data you want to specifically include or exclude from backup services. See Figure 10. The list can also contain a statement that assigns a particular management class to a range of files affected by a backup. In our test environment, we are using the include/exclude list below. In it, we exclude all the files that we do not want to use Tivoli Storage Manager backup-archive client to back up. These files are Notes databases, templates, and transaction log files, and we will back them using the specialized features of TDP for Lotus Domino.
exclude *.nsf exclude *.ntf exclude s*.txn
Figure 10. Sample include/exclude list for backup-archive client
2.4 Configuring TDP for Lotus Domino

We recommend using unique node names, policy domains, and management class names across your configuration, that is, a combination Domino environment, Tivoli Storage Manager and TDP for Lotus Domino. There may be references across the solution and the use of duplicate names may lead to serious problems and confusion.
2.4.1 Include-exclude lists TDP for Lotus Domino

Tivoli Data Protection for Lotus Domino deals only with Domino databases and transaction log files (if archival logging is in effect on the Domino server). Other files that may exist on the server are not backed up by the TDP for Domino application client, so they do not need to be excluded. However, if you want to limit the backups to a subset of the databases on your Domino server, the standard include/exclude syntax can be used. There are some important things you need to know before starting to work with include/exclude statements in a TDP for Lotus Domino configuration: Domino databases are stored by their relative names on the Tivoli Storage Manager server so these must be used on include/exclude statements. That means the Notes data directory should not be specified and databases linked to the Notes data directory by database or directory links
36
must be referenced by their symbolic name. Do not use fully qualified physical file names. A single database backup is stored as two objects on the Tivoli Storage Manager server. The objects created are the relative database name and the relative database name plus a .DATA extension. For example, a backup of database mail6/user1.nsf would result in two objects as: the relative name of the database (mail6/user1.nsf) and the relative name of the database + .DATA (mail6/user1.nsf.DATA). As a result, when excluding a group of databases (for example, all DBs in a directory) and then including a specific subset of that group, you must be sure to include both objects. For example, if you wanted to back up only the DB user1.nsf in the directory mail6 (excluding all other DBs), you would code the following statements:
EXCLUDE mail6/* INCLUDE mail6/user1.nsf INCLUDE mail6/user1.nsf.DATA
Note
When excluding a specific database, the .DATA object does not need to be excluded explicitly because the .DATA object will not be created unless the database is included.
If archival logging is in effect on the Domino server, you must be sure not to exclude the transaction log files from backup. The transaction logs have a base object name of S#######.TXN. Where ####### is a number. If you code a broad exclude statement, make sure you include the transaction log files by coding a statement as follows: INCLUDE S*.TXN. In our Notes test environment, we define the following include/exclude list for TDP for Lotus Domino. This server has transaction logging enabled in archive mode, so we include transaction log files in our list. We are backing up all Domino databases, templates, and transaction with TDP for Lotus Domino. We are using a different management class for TDP backup, so we put TDP_CLASS beside all include statements, to assign this management class for this type of file.
INCLUDE *.nsf TDP_CLASS INCLUDE *.ntf TDP_CLASS INCLUDE s*.txn TDP_CLASS
37
2.4.2 Preferences file TDP for Lotus Domino

Another important file which will need modification and customization is the preferences file, domdsm.cfg. This file contains additional options used during backup and restore processing. To update domdsm.cfg, you can either select Preferences from the TDP for Lotus Domino GUI Edit menu to define options and assign values in the preference file, or you can use the command line domdsmc set command to update the preferences file. You should not try to edit this file directly. The domdsm.cfg file looks like the sample in Figure 11, for an NT server in our environment.
BUFFers BUFFERSIze LOGFile LOGPrune REPlace SUBDir MOUNTWait DATEformat TIMEformat NUMberformat
3 1024 domdsm.log 60 yes no yes 1 1 1
NOTESIniPath c:\lotus\domino LastPruneDate 08/17/1999 15:39:27

Figure 11. Sample domdsm.cfg file
The NotesIniPath in the domdsm.cfg specifies the directory path where the Notes.ini file resides for the target Domino server. When specified for a partitioned Domino server, this option identifies the server that TDP for Domino interacts with. See 2.7, Partitioned Notes servers on page 51, for more information.
2.4.3 TDP for Domino on Windows NT option file

The TDP for Lotus Domino options reside in the client options file called dsm.opt in the application client executable directory. This should not be confused with the dsm.opt file in the backup-archive client executable
38
directory which is only used by the Tivoli Storage Manager backup-archive client. The TDP for Lotus Domino dsm.opt file identifies the Tivoli Storage Manager server to contact and specifies backup and restore options. It can also contain include and exclude statements. It can be edited using your system editor. This is an example of the TDP for Lotus Domino dsm.opt from our environment:
COMMMETHOD TCPIP TCPBUFFSIZE 32 TCPNODELAY Yes TCPPORT 1500 TCPSERVERADDRESS palana TCPWINDOWSIZE 58 PASSWORDACCESS GENERATE NOdeName lochness_tdp INCLUDE *.nsf TDP_CLASS INCLUDE *.ntf TDP_CLASS INCLUDE s*.txn TDP_CLASS EXCLUDE log.nsf EXCLUDE mail.box
By default, the installation process creates a dsm.opt file in c:\Program Files\Tivoli\TSM\Domino. You may either edit this directly or copy the provided sample options file, dsm.smp to dsm.opt, and edit this. We recommend that you identify all Notes databases, which may not be required for backup, and record these databases in the exclude list in the dsm.opt file. In our options file above, log.nsf and mail.box are excluded from backup. You can also use this file to specify a particular management class to which to bind your Domino backups (we discussed this already in 2.4.1, Include-exclude lists TDP for Lotus Domino on page 36). We did this in our sample environment, using the management class, TDP_CLASS. 2.4.3.1 Precedence of TDP option resolution on Windows NT Some options affecting the operation of TDP for Domino can be specified in more than one way. The same option can derive from more than one configuration source. When this happens, the source with the highest priority takes precedence: TDP for Lotus Domino command line option ( domdsmc). TDP for Lotus Domino preferences file, domdsm.cfg. Tivoli Storage Manager backup-archive client user option file, dsm.opt.
39
TDP for Lotus Domino will look for the option and preference files in the TDP installation directory. If you want to specify another location for either of these files to override this default, specify the actual directory location in the /adsmoptfile and /configfile parameters respectively when you start the client using domdsmc.
2.4.4 TDP for Domino on UNIX option files

In a UNIX (including Solaris, AIX and OS/390) environment, there are a number of configuration files required. These are: dsm.opt: Identifies the Tivoli Storage Manager server to contact and specifies backup and restore options. Also, this is called the client users options file. You can edit the dsm.opt file using your system editor. An example of this type of file is shown below:
SERVERNAME palana_tdp
dsm.opt.smp: Sample options file that can be copied and modified if dsm.opt does not exist. You can edit the dsm.opt.smp file using your system editor. By default TDP for Lotus Domino will look for dsm.opt in the client installation directory. For example, in AIX it is installed in /usr/tivoli/tsm/client/domino/bin. You can over-ride this by changing the environment variable DSMI_CONFIG to point to a new path of dsm.opt dsm.sys: Contains stanzas describing Tivoli Storage Manager servers to contact for services. These stanzas also specify communication methods, backup and restore options, and select scheduling options. Also, this is called the client system options file. If your system has a node name assigned to the Tivoli Storage Manager backup-archive client, we recommend you have a different node name and create a separate stanza in the dsm.sys system options file for the TDP for Lotus Domino. Only the root or Tivoli Storage Manager authorized user can edit the dsm.sys system options file. This file is found in the Tivoli Storage Manager backup-archive client installation directory. Note that we have specified a location for the scheduler output log (using the SCHEDLOGNAME option), which we will use when we discuss automatic scheduling of Domino database backups. An example of this type of file is shown below:
40
SERVERNAME palana1 nodename palana COMMMETHOD TCPIP TCPBUFFSIZE 32 TCPNODELAY Yes TCPPORT 1500 TCPSERVERADDRESS palana3 TCPWINDOWSIZE 58 PASSWORDACCESS GENERATE SERVERNAME palana_tdp nodename palana_tdp COMMMETHOD TCPIP TCPBUFFSIZE 32 TCPNODELAY Yes TCPPORT 1500 TCPSERVERADDRESS palana TCPWINDOWSIZE 58 INCLEXCL /tmp/inclexcl.lst PASSWORDACCESS GENERATE PASSWORDDIR /usr/tivoli/tsm/api/bin SCHEDLOGNAME /usr/tivoli/tsm/baclient/domino/bin/dsmscheddomino.log
include/exclude list: the location of this file is indicated by the INCLEXCL parameter in the dsm.sys file. In our case, the file /tmp/inclexcl.lst will contain the following statements:
INCLUDE INCLUDE INCLUDE EXCLUDE EXCLUDE
*.nsf TDP_CLASS *.ntf TDP_CLASS s*.txn TDP_CLASS log.nsf mail.box
2.4.4.1 Domino server UNIX environment variables The following environment variables are used to point to files and directories that the TDP for Lotus Domino uses: DOMI_DIR: This points to the directory where the TDP for Lotus Domino was installed. The default installation directory is /usr/tivoli/tsm/client/domino/. DOMI_CONFIG: This points to the TDP for Lotus Domino preferences file. Specify this environment variable to change the default setting. The default is domdsm.cfg in the directory where TDP for Lotus Domino is installed. The file name can include a fully-qualified path or a relative path. A relative path is the directory where TDP for Lotus Domino is run.
41
DOMI_LOG: This points to the directory where the TDP for Lotus Domino log file (domdsm.log) will be stored. The default is the installation directory. Specify this environment variable to change the default setting. The following Tivoli Storage Manager API environment variables are used to point to files that the API uses: DSMI_DIR: This points to the directory where the Tivoli Storage Manager API is installed. This environment variable is required and there is no default. DSMI_LOG: This points to the directory where the Tivoli Storage Manager API error log file (dsierror.log) will be stored. Specify this environment variable to change the default setting. The default directory is the TDP for the Lotus Domino install directory. DSMI_CONFIG: This points to the Tivoli Storage Manager API options file name. Specify this environment variable to change the default setting. The default is dsm.opt file in the directory where TDP for Lotus Domino is installed. The file name can include a fully-qualified path or a relative path. A relative path is relative to the current directory where TDP for Lotus Domino is run. The operating system path variable is also required: PATH: As of Domino server V5.0.2b and higher, the Domino resource directory must be added. The resource directory is the res/${LANG} directory under the Domino executable directory. On AIX that would be /opt/lotus/notes/latest/ibmpow/res/${LANG}. On Solaris, the directory is /opt/lotus/notes/latest/sunspa/res/${LANG}. For AIX only, the following variable must also be set: AIXTHREAD_MNRATIO: This is an AIX system variable which is related to the scheduling of threads. It must be set to 1:1. 2.4.4.2 Setting Bourne and Korn shell environment variables For the Bourne or Korn shell, enter the environment variables in the .profile file of the user ID that runs the Domino server. DSMI_DIR and PATH are the only required environment variables, except for AIX where AIXTHREAD_MNRATIO is also required.
42
For example:
DOMI_DIR=/usr/tivoli/tsm/client/domino DOMI_LOG=/home/domserver/alllogs DOMI_CONFIG=/usr/tivoli/tsm/client/domino/domdsm.cfg DSMI_DIR=/usr/lpp/adsm/api/bin DSMI_LOG=/home/domserver/allLogs DSMI_CONFIG=/usr/tivoli/tsm/client/domino/dsm.opt DOM=/opt/lotus/notes/latest/ibmpow PATH=$PATH:$DOM:/local/notesdata:$DOM/res/${LANG} AIXTHREAD_MNRATIO=1:1 export DOMI_DIR DOMI_CONFIG DOMI_LOG DSMI_DIR DSMI_CONFIG DSMI_LOG PATH AIXTHREAD_MNRATIO
The PATH statement specifies the Domino executable directory, the Domino resource directory, and optionally the Notes data directory that is specified when the Domino server was installed. 2.4.4.3 Setting C shell environment variables For the C shell, enter the environment variables in the .cshrc file of the user ID that runs the Domino server. DSMI_DIR and PATH are the only required environment variables, except for AIX, where AIXTHREAD_MNRATIO is also required. For example:
setenv setenv setenv setenv setenv setenv setenv setenv setenv
DOMI_DIR /usr/tivoli/tsm/client/domino DOMI_LOG /home/domserver/allLogs DOMI_CONFIG /usr/tivoli/tsm/client/domino/domdsm.cfg DSMI_DIR /usr/lpp/adsm/api/bin DSMI_LOG /home/domserver/allLogs DSMI_CONFIG /usr/tivoli/tsm/client/domino/dsm.opt DOM /opt/lotus/notes/lates/ibmpow PATH $PATH:$DOM:/local/notesdata:$DOM/res/${LANG} AIXTHREAD_MNRATIO 1:1
Important
If your environment is not set up correctly, you may receive a Domino error when running TDP for Domino. If the problem persists and the setup appears to be correct, there is a manual procedure to follow which may fix the problem. This procedure is documented in the README file contained in the application install package. You should carefully follow the steps, including the special considerations for partitioned servers. If this does not fix the problem, then contact Technical Support.
43
2.4.4.4 Precedence of TDP option resolution in UNIX Some options affecting the operation of TDP for Domino can be specified in more than one way. The same option can derive from more than one configuration source. When this happens, the source with the highest priority takes precedence, in the sequence shown as follows: Tivoli Storage Manager backup-archive client system options file, dsm.sys. TDP for Lotus Domino command line option, domdsmc. TDP for Lotus Domino preferences file, domdsm.cfg. Tivoli Storage Manager backup-archive client user options file, dsm.opt. 2.4.4.5 Running the setup script on UNIX After completing the installation and setting your environment variables, run the setup script, domsetup. The setup script assigns the group name, file owner, file permissions, and creates the symbolic link required by the TDP for the Lotus Domino executable. To run the domsetup script, perform the following steps: 1. Logon as the userid that was setup to run the Domino server. 2. Switch to the root userid by entering the su root command. 3. Change to the directory where TDP for Lotus Domino is installed. 4. Enter domsetup. You can run the setup script without prompting by using the domsetup.dat file. Copy and edit the domsetup.dat file, follow the instructions within the file, and pass it as a command line argument to domsetup. If, for example, you create the domsetup.input file from the domsetup.dat file, use the following command:
domsetup domsetup.input
2.5 Passwords
By default, you will be prompted for the TDP client node password (which is specified originally when you register it to the Tivoli Storage Manager server) whenever you start the TDP for Domino application. You can avoid this prompt by giving the password whenever you start the client like this:
domdsmc /adsmpwd=xxxx
44
Alternatively, to permanently avoid having to enter the password, you can specify PASSWORDACCESS GENERATE in the dsm.sys (UNIX) or dsm.opt (NT) file. After you do this, the next time you invoke the client, the API will save the current password in encrypted form on the client and also automatically generate a new password when it expires. Specifying PASSWORDACCESS GENERATE is specially recommended if you are doing automatic scheduling of Domino backups.
2.6 Scheduling TDP for Lotus Domino

Although TDP for Lotus Domino comes with a rich and powerful GUI and command-line interface (as described in the next chapter), in practice you will use these mainly for queries and restore operations. Most customer environments require automatic, regular scheduling of critical operations such as data backups. This ensures these operations will always be executed when required, without the need for human intervention. There are a number of choices for scheduling the TDP for Lotus Domino client: 1. Using Tivoli Storage Manager Scheduler 2. Using Lotus Domino Scheduler 3. Using another operating system or third party scheduler, for example, cron for UNIX. We do not explore this possibility any further here, however the techniques discussed for other schedulers can be easily applied.
2.6.1 Tivoli Storage Manager scheduler

Setting up scheduling the TDP for Lotus Domino with the Tivoli Storage Manager command scheduler is slightly more complicated than for the backup-archive client. The Tivoli Storage Manager backup-archive clients can run in a scheduled mode (using the scheduling daemon), and schedules are defined on the Tivoli Storage Manager server to automate their operation. The TDP for Lotus Domino application client cannot run in a scheduled mode, however. To schedule the TDP for Lotus Domino with Tivoli Storage Manager, you must configure schedule the backup-archive client on the Domino server to execute a script containing the required domdsmc commands. See Figure 12.
45
Domino R5 server
Transaction log
Domino API TDP for Lotus Domino
Tivoli Storage Manager server

TSM API
sched.cmd
Domino R5 databases
c:\sched.cmd domdsmc incremental "*" .....
Tivoli Storage Manager scheduler service

tsm: PALANA1> define schedule domino tdp \ cont> action=command object=c:\sched.cmd
Figure 12. Scheduling TDP for Lotus Domino with Tivoli Storage Manager
Figure 12 shows the backup-archive client and TDP for Lotus Domino implemented on the Domino server. They are each defined to the Tivoli Storage Manager server using different node names. The backup-archive client is set up to run in scheduled mode; it waits to perform scheduled operations defined on the Tivoli Storage Manager server. Client functions, including backups, archives, restores, and retrieves, can be scheduled, as can ordinary operating system commands. A schedule can be defined on Tivoli Storage Manager that, when invoked, runs a script which contains the domdsmc backup command on the Domino server. The Tivoli Storage Manager server thinks it is scheduling the backup-archive client, but, in reality, it is starting the TDP for Lotus Domino. To achieve this, you use the ACTION=COMMAND and OBJECTS=<scriptname> options on the define schedule command. Sample scripts are provided with the TDP for Lotus Domino installation and we discuss these, along with recommendations for defining the schedules in 4.3, Scheduling on page 116. 2.6.1.1 Install and start scheduler service for TDP on Windows The Tivoli Storage Manager scheduler runs as a service in NT and is installed using the dsmcutil command. If you have already installed a scheduler service for your existing backup-archive client, we recommend for you to install an additional service for the TDP client.
46
Specify a different service name and your TDP client node name and option file when defining the service as in the following example:
C:\Program Files\Tivoli\TSM\baclient>dsmcutil install /name:"TDP for Lotus Domin o Schedule" /node:senegal /password:senegal /optfile:"c:\program files\tivoli\tsm\domino\ dsm_senegal.opt" /clientdir:"c:\program files\tivoli\tsm\baclient" /schedlog:"c: \program files\tivoli\tsm\domino\domsch.log" TSM Windows NT Client Service Configuration Utility Command Line Interface Version 3.00.a Last Updated Sep 20 1999 TSM Api Verison 3.7.1 Command: Install TSM Client Service Machine: SENEGAL (Local Machine)
Installing TSM Client Service: Machine Service Name Client Directory Automatic Start Logon Account : : : : : SENEGAL TDP for Lotus Domino c:\program files\tivoli\tsm\baclient No LocalSystem
The service was successfully installed. Creating Registry Keys ... Updated Updated Updated Updated Updated Updated Updated Updated registry registry registry registry registry registry registry registry value value value value value value value value 'ImagePath' . 'EventMessageFile' . 'TypesSupported' . 'OptionsFile' . 'EventLogging' . 'ClientNodeName' . 'ADSMClientKey' . 'ScheduleLog' .
Generating registry password ... Authenticating password with TSM for node SENEGAL .... Connecting to TSM Server via client options file 'c:\program files\tivoli\tsm\do mino\dsm_senegal.opt' ... Password authentication successful. The Registry password for node SENEGAL has been updated . Starting the 'TDP for Lotus Domino' service ... The Service was successfully started
You can see we also used the /schedlog option to specify a separate location from the default for the logfile, dsmsched.log. This ensures that the two schedule services (for backup/archive client backup and for TDP for Domino) will log their results in different places.
47
Note
Normally, we dont need to specify /clientdir option while installing a scheduler. However, at some levels of the Tivoli Storage Manager client, the dsmcutil command needs to be specified with /clientdir option. Without this option, the WIndows NT service will not start and gives a message %1 is not a valid Windows NT application. If you have already installed the scheduler without the /clientdir option, you should update the scheduler by using dsmcutil /update command to include it. If you are using the Tivoli Storage Manager backup/archive client at Version 3.7.2 or higher, you can also use the GUI scheduler configuration wizard instead of the dsmcutil command to install an additional scheduler service. This wizard is shown in Figure 13.
Figure 13. Backup-archive client scheduler wizard
48
After the scheduler service is installed, it can be controlled from the control panel-services screen. Figure 14 shows the services screen with the status and attributes of TDP for Lotus Domino Scheduler as a separate entry from the standard Tivoli Storage Manager client scheduler entry, TSM Central Scheduler.
Figure 14. TDP Scheduler Service on Windows NT
2.6.1.2 Install and start schedule process on UNIX After you have done all the necessary configuration on the Tivoli Storage Manager server and on your Domino server, it will be necessary to start the Tivoli Storage Manager scheduler process on your Domino server. Since you probably already have a scheduler process running for your Tivoli Storage Manager backup/archive client, to avoid confusion we recommend you run another scheduler instance dedicated to TDP for Domino. You can invoke this scheduler instance using the SERVERNAME parameter to point it to the correct stanza in the dsm.sys file (as described in 2.4.4, TDP for Domino on UNIX option files on page 40). You will have specified a filename location for the scheduler output log using the DSMSCHEDLOGNAME parameter in the dsm.sys file, as we showed in the example. To start the scheduler in foreground mode, run the following command as the root user:
# nohup dsmc sched -servaname=palana_tdp&
49
Normally, you will want to have the scheduler process start automatically whenever you reboot the system. For this, you need to include a line in the /etc/inittab file. Here is the safest way to do this in AIX.
# mkitab dsmsched:2:once:/usr/tivoli/tsm/client/ba/bin/dsmc sched -servername=palana_tdp > /dev/null 2>&1 Tivoli Storage Manager client scheduler
To make sure that the scheduler process is running, use the following command:
# ps -ef | grep dsmc sched | grep -v grep root 29562 22104 0 17:51:09 pts/1 0:00 /usr/bin/dsmc sched -servername=palana_tdp
2.6.2 Lotus Domino scheduler

As an alternative to using the Tivoli Storage Manager scheduler, you can use Lotus Dominos own built-in scheduler. This scheduler executes a specified executable file at the given time interval. The method of scheduling involves a program to be written. The program includes the command which has to be executed. For example, the file start.exe, which contains the command:
domdsmc incremental db1.nsf /ADSMnode=Lochness_tdp
This is created using a C compiler and is specified in the program document in Domino Directory(Public Address Book). Figure 15 shows the view of Domino Directory, where a program is specified.
50
Figure 15. Lotus Domino scheduler
Note: Make sure that you load a command prompt at the Lotus Domino Server Console. You can do this by issuing a load cmd at the sever console. Because the program expects a command prompt to execute, this step is necessary.
2.7 Partitioned Notes servers

Domino server partitioning lets you run multiple Domino servers on a single computer. Each partitioned server has its own Domino data directory and notes.ini file, but all partitioned servers share the same Domino program directory. In this section, we discuss what to consider when configuring TDP for Lotus Domino for partitioned Domino servers
2.7.1 Windows NT
To use TDP for Lotus Domino with multiple Domino partitions on a single machine, you must specify which partition you want to work with by identifying the location of the notes.ini file for that partition. In addition, when
51
working with multiple Domino partitions, you should have separate TDP for Lotus Domino log files for each server instance. Since the log file to be used is also specified in the Domino application client preferences (by log file options), the method to support multiple Domino partitions is to create multiple preferences or configuration files as follows: Use the set command with the configfile option to define a configuration file for each Domino partition to be supported. Be sure to set the notesinipath and logfile values appropriately. For example:
domdsmc domdsmc domdsmc domdsmc
set set set set
notesinipath=c:\notes\data1\ /configfile=domino1.cfg logfile=domdsm1.log /configfile=domino1.cfg notesinipath=c:\notes\data2\ /configfile=domino2.cfg logfile=domdsm2.log /configfile=domino2.cfg
Note: Other Domino application client preferences can be set as desired for each partition. Use the configfile option when invoking the TDP for the Lotus Domino executable to identify which configuration file is used for the command execution and therefore which Domino partition will be accessed. In our example, we have two partitioned Domino servers on one Windows NT system, CHARCOT and SENEGAL. We are using node name charcot_tdp to back up databases from both servers. We use configuration files setup as above, called domdsm_charcot.cfg and domdsm_senegal.cfg, respectively:
C:\Program Files\tivoli\tsm\domino\domdsmc selective * /configfile=C:\Program Files\tivoli\tsm\domino\domdsm_charcot.cfg C:\Program Files\tivoli\tsm\domino\domdsmc selective * /configfile=C:\Program Files\tivoli\tsm\domino\domdsm_senegal.cfg
To see which databases were backed up from server charcot and senegal, issue the following commands:
C:\Program Files\tivoli\tsm\domino\domdsmc query dbbackup /server=charcot C:\Program Files\tivoli\tsm\domino\domdsmc query dbbackup /server=senegal
2.7.2 UNIX
On UNIX, Lotus recommends that you run each partitioned Domino server with a separate user ID. When running TDP for Lotus Domino commands you must be logged in as the Domino server ID that owns the partition. Otherwise, you do not have access to the Domino databases for backup and restore operations. Additionally, the owner ID of the TDP for Lotus Domino
52
executable (domdsmc) must match the login ID for password access to work. This is since only the owner of the generated password file has access to the password file. Since you need to login in and run domdsmc with more than just one login ID, you need to create and control multiple copies of domdsmc, each with a different owner ID (one for each partition). You also need to setup multiple Tivoli Storage Manager node names, one for each executable. In our example, shown in Figure 16, we have two partitioned Domino servers on one AIX system, PALANA and VICTORIA. The Domino server IDs are notes1 and notes2. We highly recommend that you keep all server IDs in the same UNIX group. We used a group called notes for our IDs. Each partition has a different TCP/IP address but they are sharing the same network adapter. We use aliasing under AIX to configure the additional TCP/IP address for the adapter.
Figure 16. Partitioned Domino servers on AIX
On partition palana, we have a file system called /palana and this file system belongs to the notes1 user in the group notes. On the other partition, we have a file system called /victoria which belongs to the notes2 user that is also in the notes group.
analap :eman edon tneilc evihcra-pukcab
10.5R onimoD 2.3.4 xiA
pdt_airotciv : eman edon onimoD sutoL rof PDT
pdt_analap : eman edon onimoD sutoL rof PDT
seton.2seton=resU airotciv/=ataD 94.051.1.9 nedamlA/airotciv
seton.1seton=resU analap/=ataD 311.051.1.9 nedamlA/analap
53
2.7.2.1 Partitioned server initialization After the installation of TDP for Lotus Domino on the partitioned AIX server, we do the following: 1. Setup all required environment variables for each server ID login in their .profile files.
Environment variables for palana
PATH=$PATH:/opt/lotus/notes/latest/ibmpow:/palana DOMI_DIR=/usr/tivoli/tsm/client/domino/bin/palana DOMI_LOG=/usr/tivoli/tsm/client/domino/bin/palana DOMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/palana/domdsm.cfg DSMI_DIR=/usr/tivoli/tsm/client/api/bin DSMI_LOG=/usr/tivoli/tsm/client/domino/bin/palana DSMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/palana/dsm.opt
Environment variables for victoria
PATH=$PATH:/opt/lotus/notes/latest/ibmpow:/victoria DOMI_DIR=/usr/tivoli/tsm/client/domino/bin/victoria DOMI_LOG=/usr/tivoli/tsm/client/domino/bin/victoria DOMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/victoria/domdsm.cfg DSMI_DIR=/usr/tivoli/tsm/client/api/bin DSMI_LOG=/usr/tivoli/tsm/client/domino/bin/victoria DSMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/victoria/dsm.opt
2. Run domsetup as before once on each of the partitions. 3. Put all server IDs into a common UNIX group, for example, notes (if they are not already). Set the group ID of the TDP for Domino install directory (/usr/tivoli/tsm/client/domino/bin) to this common group ID. Set the owner to one of the partition server IDs. Set permissions on the TDP for Domino install directory to -rwxrwxr-.
# chown notes1.notes /usr/tivoli/tsm/client/domino/bin # chmod 774 /usr/tivoli/tsm/client/domino/bin
4. Under the install directory, create a subdirectory for each server ID.
# mkdir palana # mkdir victoria
54
5. Copy the domdsmc executable to each subdirectory (use the -p parameter to keep the permissions while copying the file). Change the owner and group of the subdirectory and its content to the associated server ID and group:
# # # #
cp -p cp -p chown chown
domdsmc palana domdsmc victoria -R notes1.notes palana -R notes2.notes victoria
6. Create a symbolic link in the Domino executable directory (/opt/lotus/notes/latest/ibmpow by default) to each copy of domdsmc. Name the link domdsmc_"serverid". Remove the domdsmc link that was created by domsetup:
# # # #
cd ln ln rm
/opt/lotus/notes/latest/ibmpow -s /usr/tivoli/tsm/client/domino/bin/palana/domdsmc domdsmc_palana -s /usr/tivoli/tsm/client/domino/bin/victoria/domdsmc domdsmc_victoria domdsmc
7. In each server ID's login .profile, setup the alias:
# domdsmc=domdsmc_"serverid"
8. Set up a preferences file for each server ID with the correct NOTESINIPATH=value. Or, Update each server's PATH= statement with the Domino Executable directory and the associated Notes data path. You may be able to share one preferences file among all server IDs with this second approach, by placing the Notes data path in your path statement. In this case, you can leave the NOTESINIPATH= value blank in the preference file. 9. To verify the setup, as server ID: execute profile, switch to root:su, cd to $DOMI_DIR/server_id, and execute:
# domdsmc q adsmserver
To work with TDP for Lotus Domino in a server using partitions, it is necessary to register a Tivoli Storage Manager node name for each one. Each partition has its own TDP configuration file (domdsm.cfg) and Tivoli Storage Manager option file (dsm.opt). In AIX, each dsm.opt file points to a
55
different stanza on the single dsm.sys file. It is not necessary to use an additional Tivoli Storage Manager backup-archive client for each partitioned server, but you should make sure that the backup-archive client excludes the Domino databases that are being backed up by each TDP for Lotus Domino. 2.7.2.2 Partitioned server profiles Here is the .profile for the user ID notes1 (which owns the palana Domino partition):
NOTES_USER=notes1 NOTES_PATH=/palana NOTES_SERVER=palana OUTPUT_LOG=/tmp/$NOTES_SERVER.log INPUT_FILE=$NOTES_PATH/$NOTES_USER.input PATH=$PATH:/opt/lotus/notes/latest/ibmpow:/palana DOMI_DIR=/usr/tivoli/tsm/client/domino/bin DOMI_DIR=/usr/tivoli/tsm/client/domino/bin/palana DOMI_LOG=/palana/allLogs DOMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/domdsm.cfg DOMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/palana/domdsm.cfg DSMI_DIR=/usr/tivoli/tsm/client/api/bin DSMI_LOG=/palana/allLogs DSMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/palana/dsm.opt DSM_DIR=/usr/tivoli/tsm/client/ba/bin DSM_LOG=/usr/tivoli/tsm/client/ba/bin DSM_CONFIG=/home/palana/dsm.opt export PATH DOMI_DIR DOMI_CONFIG DOMI_LOG DSMI_DIR DSMI_CONFIG DSMI_LOG DSM_DIR DSM_CONFIG DSM_LOG export TERM=xterm set -o vi PS1=`whoami`"@"" "'$PWD >' alias domdsmc=domdsmc_palana
56
And, for notes2 (which owns the victoria partition):
NOTES_USER=notes2 NOTES_PATH=/victoria NOTES_SERVER=victoria OUTPUT_LOG=/tmp/$NOTES_SERVER.log INPUT_FILE=$NOTES_PATH/$NOTES_USER.input PATH=$PATH:/opt/lotus/notes/latest/ibmpow:/victoria DOMI_DIR=/usr/tivoli/tsm/client/domino/bin DOMI_DIR=/usr/tivoli/tsm/client/domino/bin/victoria DOMI_LOG=/victoria/allLogs DOMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/domdsm.cfg DOMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/victoria/domdsm.cfg DSMI_DIR=/usr/tivoli/tsm/client/api/bin DSMI_LOG=/victoria/allLogs DSMI_CONFIG=/usr/tivoli/tsm/client/domino/bin/victoria/dsm.opt DSM_DIR=/usr/tivoli/tsm/client/ba/bin DSM_LOG=/usr/tivoli/tsm/client/ba/bin DSM_CONFIG=/home/victoria/dsm.opt export PATH DOMI_DIR DOMI_CONFIG DOMI_LOG DSMI_DIR DSMI_CONFIG DSMI_LOG DSM_DIR DSM_CONFIG DSM_LOG export TERM=xterm set -o vi PS1=`whoami`"@"" "'$PWD >' alias domdsmc=domdsmc_victoria
2.7.2.3 Partitioned server configuration files Note the different values for DOMI_CONFIG and DSMI_CONFIG. Each partition uses different options files indicated in the DSMI_CONFIG variable which refer to different stanzas on the dsm.sys file. For example, /usr/tivoli/tsm/client/domino/bin/palana/dsm.opt has the entry servername palana_tdp and similarly for victoria. We define these server names in the backup-archive client dsm.sys file.
57
The relevant stanzas of the dsm.sys file are:
SERVERNAME palana1 nodename palana COMMMETHOD TCPIP TCPBUFFSIZE 32 TCPNODELAY Yes TCPPORT 1500 TCPSERVERADDRESS palana TCPWINDOWSIZE 58 PASSWORDACCESS GENERATE SERVERNAME palana_tdp nodename palana_tdp COMMMETHOD TCPIP TCPBUFFSIZE 32 TCPNODELAY Yes TCPPORT 1500 TCPSERVERADDRESS palana TCPWINDOWSIZE 58 PASSWORDACCESS GENERATE SERVERNAME victoria_tdp nodename victoria_tdp COMMMETHOD TCPIP TCPBUFFSIZE 32 TCPNODELAY Yes TCPPORT 1500 TCPSERVERADDRESS palana TCPWINDOWSIZE 58 PASSWORDACCESS GENERATE
Below we show the TDP configuration file (domdsm.cfg) of each partition. This file has different configuration options for each partition, and we need to use the domdsmc set commands to change the parameters in these files.
LastPruneDate 08/04/2000 08:36:50 BUFFERSIze 1024 NOTESInipath /palana BUFFers 3
LastPruneDate 08/04/2000 08:38:48 BUFFers 3 NOTESInipath /victoria BUFFERSIze 1024
The palana notes server has transaction logging enabled in archive mode while the victoria Notes server does not have transaction logging enabled. Both of them belong to a management class TDP_CLASS that was created
58
for TDP for Lotus Domino on our Tivoli Storage Manager server, palana. There is another management class Tivoli Storage Manager_CLASS that was created for Tivoli Storage Manager backup-archive files and it was assigned as our default class.The next three screens show the difference between the include/exclude lists. The first screen shows the include/exclude list for node palana_tdp. It specifies to backup all of the Domino databases using TDP for Domino, explicitly specifying the management class for each. We also include the transaction log extents (extension *.txn). TDP for Domino can only backup these kinds of files, so we do not need to include an exclude statement.
include *.nsf TDP_CLASS include *.ntf TDP_CLASS include s*.txn TDP_CLASS
The next screen, shows the include/exclude list for node victoria_tdp. It is the same as the previous list, except the transaction log extents are not included, since we are not using archive logging mode.
include *.nsf TDP_CLASS include *.ntf TDP_CLASS
The last screen shows the include/exclude list to be used for the Tivoli Storage Manager backup-archive client nodes (both victoria and palana). We do not want to backup the files that we are backing up with TDP for Lotus Domino, so we exclude all Domino databases and template files.
exclude *.nsf exclude *.ntf exclude s*.txn
2.8 Clustered Domino servers

A Domino cluster is a group of two to six servers that lets you provide users with access to data, balance the workload between servers and to improve server performance. The servers in a cluster contain replicas of databases that you want to be readily available. Domino opens a replica of that database on a different cluster server, if the original database on your server is not working. This operation is called failover. Domino continuously synchronizes databases so that, no matter which replica the user opens, the information is always identical.
59
In Figure 17, we show an example of a Domino cluster environment. In this environment we have databases spread over the cluster servers. Depending on the importance of these databases you should include more database replicas on the others cluster members. In each cluster member that has a replica of a database you can control the number of clients that can access this database. This is a good way to balance the workload. Even though more than six servers can technically be added into Domino cluster, it is not supported by Lotus Corporation.
Figure 17. Domino cluster environment
60
7BD 6BD 5BD 4BD
3 revreS
ciffarT retsulC rof NAL etavirP
tneilC setoN 2 revreS
4BD 5BD 2BD 1BD
1 revreS
2BD 3BD 1BD
NAL
Additional Notes Administration is necessary when you are planning to use a Domino cluster, because it is necessary to make sure that all replicated databases in the cluster environment are synchronized. The cluster directory database is very useful to control the databases that are replicated between the cluster servers. This database is replicated between all the cluster members and it has an entry for all databases in each cluster member. You can use it to disable or enable the replication between databases in cluster environment. To backup a server member of a Domino cluster, it is necessary to use TDP for Lotus Domino to backup the Domino data and Tivoli Storage Manager backup-archive client to back up the non-Domino data. You will need to use two Tivoli Storage Manager node names, one for Tivoli Storage Manager backup-archive client and another one to TDP for Lotus Domino. To save space in your Tivoli Storage Manager storage pools you should exclude the databases that are replicated in all clusters members. To exclude these databases you should use include/exclude statements on your option file. You can find examples on how to exclude databases in the customization section earlier in this chapter. In Figure 18, we show the Domino cluster that we used in our test environment. We used two NT servers to make this Domino cluster and only some important databases are replicated between these servers. We backup the replicated databases in just one member of the cluster, tokyo. You do not need to backup the replicated databases on the other member of the cluster. This will save space in your Tivoli Storage Manager server as well as reduce network traffic and daily backup window.
61
TSM b/a client node name: tokyo TDP for Lotus Domino node name: tokyo_TDP
TSM b/a client node name: wewak TDP for Lotus Domino node name: wewak_TDP
Figure 18. Domino cluster in test environment
62
0.4 revreS TN
kawew
ciff arT re tsulC rof NAL etavirP
rets ulC OSTI
NAL 0.4 revreS TN

oykot
Chapter 3. Operating TDP for Lotus Domino

In this chapter, we give examples of various TDP for Lotus Domino operations, using both the command-line, and the graphical user interface (GUI). All examples assume that the PASSWORDACCESS option in the TDP for Lotus Domino option file is set to GENERATE, to avoid the need to manually enter the client node password when starting a TDP for Lotus Domino action. This option is discussed in 2.5, Passwords on page 44. All TDP for Lotus Domino platforms can use domdsm, which is the TDP for Lotus Dominos single executable program. It provides a number of commands and parameters for backup, restore, and query. In addition, the TDP for Lotus Domino on Windows NT features a graphical user interface (GUI). We discuss the fundamental backup and restore functions, as well as options to query and update various preference settings, and finally discuss factors affecting performance. Many of the operations discussed here, especially those related to backing up databases, archiving the transaction logs and inactivating the transaction logs, are unlikely to be performed interactively very often once the backup system has been tested and put into production. This is because at most sites, it is required to have these functions performed automatically, by way of a schedule. We discuss recommended schedules and how to implement them in 4.3, Scheduling on page 116, however, it is important to understand the command structures which make up these schedules, and also how to use the GUI.
3.1 Database backup and log archive

The following examples illustrate the various ways in which databases can be backed up using TDP for Lotus Domino.
3.1.1 Incremental backup

The incremental command provides a conditional backup function that performs a full online backup of selected Domino databases. A Domino database will be backed up when the incremental command is issued under the following conditions: The database is not excluded from backup operations via an include/exclude statement in the Tivoli Storage Manager options file.
63
The database matches the file specification in the incremental command. You can state one or more specific databases to be backed up, or use wildcards and pattern matching to restrict those databases for consideration (for example, * or acct*.nsf). The database is new or newly included in the backup (no active backup copy already exists on the Tivoli Storage Manager server). The database is not logged, and was modified since the last backup (both data and non-data modification dates are checked and if either is different from that of the active backup, the database will be backed up). The database is logged (archive or circular), and the DBIID has changed since the last backup. For more information, see: - Section 1.1.8.5, Transaction logging and the database instance ID on page 16 - Section 4.1.2, Changing the database instance identifier on page 111 The TDP for Lotus Domino incremental backup operation should not be confused with the incremental backup function of a Tivoli Storage Manager backup-archive client which backs up only changed files. TDP for Lotus Domino backs up entire databases which meet these criteria. It does not back up smaller components within databases, for example documents. This means that the backup granularity is on a database level. This is different to the document level granularity of TDP for Lotus Notes R4, as discussed in 1.1.9, Backup API of R4 and R5 on page 17. Both the incremental and selective (see next section) backup operations are so-called full backups, meaning they will both backup the entire database. The difference is in the conditions under which a database will be selected for backup as well as what, if any, inactivation or deletion process is done along with the backup operation. A query of the current backup versions of the specified databases stored at the Tivoli Storage Manager server is automatically performed before any backup actions take place. The incremental backup operation also inactivates any database backups on the Tivoli Storage Manager which have been newly excluded from backup, or deleted from the Domino server since the last incremental operation took place.
64
3.1.1.1 When to use incremental backup? The incremental backup of all Domino databases needs to be run regularly, for the following reasons: Non-logged databases: For a non-logged database all transactions are directly applied to the database. The incremental backup assures that if transactions occurred within a database the database is backed up to the Tivoli Storage manager server. Circular and archive logged databases: If the DBIID of a database changes, all transactions which occur within this database are stored in the transaction log. The transactions refer to the new DBIID of the database. If the database is corrupted and needs to be recovered those transactions can only be applied to a restored version of the database if the DBIID matches. Therefore, the incremental backup assures that a database is backed up to Tivoli Storage Manager server when the DBIID has changed.
Example 1 This command executes an incremental backup of all databases in the Domino data directory. Much of the output has been deleted, to save space. Note that on UNIX, you must enclose any file specification wildcards in quotes. See Figure 19.
Operating TDP for Lotus Domino
65
notes1@ /palana >domdsmc incremental "*" /subdir=yes Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Backing up database admin4.nsf, 1 of 56. Full: 0 Read: 1064448 Written: 1064448 Rate: 4442.31 Kb/Sec Backup of admin4.nsf completed successfully. Backing up database admin4.ntf, 2 of 56. Full: 0 Read: 515584 Written: 515584 Rate: 1201.67 Kb/Sec Backup of admin4.ntf completed successfully. Backing up database alog4.ntf, 3 of 56. Full: 0 Read: 165376 Written: 165376 Rate: 276.07 Kb/Sec Backup of alog4.ntf completed successfully. Backing up database archlg50.ntf, 4 of 56. Full: 0 Read: 252416 Written: 252416 Rate: 363.57 Kb/Sec Backup of archlg50.ntf completed successfully. ..... Total Domino databases inspected: 78 Total Domino databases backed up: 56 Total Domino databases excluded: 0 Total Domino backup objects expired: 0 Throughput rate: Total bytes transferred: Elapsed processing time: 3151.07 Kb/Sec 392982528 121.79 Secs
Figure 19. Example 1
66
Example 2 In this command, we run an incremental backup of all mail databases. The file specification is relative to the Domino data directory. See Figure 20.
notes1@ /palana >domdsmc incremental "mail/*.nsf" Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Backing up database mail/mathis.nsf, 1 of 3. Full: 0 Read: 5767168 Written: 5767168 Rate: 3234.92 Kb/Sec Backup of mail/mathis.nsf completed successfully. Backing up database mail/ppires.nsf, 2 of 3. Full: 0 Read: 5767168 Written: 5767168 Rate: 3957.84 Kb/Sec Backup of mail/ppires.nsf completed successfully. Backing up database mail/vbarros.nsf, 3 of 3. Full: 0 Read: 5767168 Written: 5767168 Rate: 2687.02 Kb/Sec Backup of mail/vbarros.nsf completed successfully.
Total Total Total Total
Domino Domino Domino Domino
databases inspected: databases backed up: databases excluded: backup objects expired:
3 3 0 0 3190.33 Kb/Sec 17301504 5.30 Secs
Throughput rate: Total bytes transferred: Elapsed processing time:
3.1.2 Selective backup

The selective command provides an unconditional backup function that performs a full online backup of Domino databases. It backs up all databases that match your specification and that are not excluded from the backup operation via an include/exclude statement in the Tivoli Storage Manager options file. There is no comparison of attributes such as DBIID and logging status, as is performed by the incremental backup command (see 3.1.1,
67
Incremental backup on page 63); and version control of backups, including removal of deleted or extra backup versions, is not done. 3.1.2.1 When to use selective backup As stated in 3.1.1, Incremental backup on page 63 an incremental backup backs up logged databases only if the DBIID of the database has changed. Since the DBIID of a database only changes in certain circumstances (see 4.1.2, Changing the database instance identifier on page 111) and if you only perform incremental backups, it could happen that your active backup version of a logged database on Tivoli Storage Manager server is quite old. When an archive logged database is corrupted and needs to be recovered you would first restore the active backup version of the database. Then, you would apply the transactions required for the recovery of the database to bring it up to date. These required log extents would first need to be restored to the Domino server for the recovery and then played against the database. If the database has been quite active, these combined processes could take a large amount of time. Since you want this restore to be as quick as possible you want to keep the number of required log extents to the minimum. Therefore, you should run a selective backup of all logged databases regularly, for example weekly, to make sure you have a recent backup version of all logged databases on the Tivoli Storage Manager server. If you are running incremental backup of non-logged databases regularly, you do not need to run additional selective backups. This is because a selective backup will back up non-logged databases, even if they are not modified since the last backup operation. This would lead to redundant backup versions on the Tivoli Storage Manager server, since the incremental backup operation backs up those databases whenever they change. Therefore, we recommend that you to exclude non-logged databases from selective backups using the LOGGEDONLY parameter with the selective backup.
68
Example 3 The following screen shows the command line syntax for selective backup (Figure 21).
notes1@ /palana >domdsmc selective "a*" /loggedonly Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Logging on to the Tivoli Storage Manager server, please wait... Backing up database admin4.nsf, 1 of 1. Full: 0 Read: 1350144 Written: 1350144 Rate: 995.85 Kb/Sec Backup of admin4.nsf completed successfully.
Total Domino databases inspected: Total Domino databases backed up: Total Domino databases excluded: Throughput rate: Total bytes transferred: Elapsed processing time:
1 1 0 994.34 Kb/Sec 1350144 1.33 Secs
3.1.3 Archive log

The archivelog command provides a backup function for Domino transaction log extents when archive logging is enabled on the Domino server. This command queries the Domino server to determine if any log extents are ready for archiving. Only filled log extents which do not include any transactions required for a Domino server restart are eligible for the archive log operation, unless you are using TDP for Lotus Domino V1.1.1.0 or higher with Domino server V5.0.4 or higher. See the Note in section 3.1.3.1 for details. Once log extents are backed up to the Tivoli Storage Manager server, the Domino server is notified of their availability for reuse. This means the transaction log space which is allocated by the backed up log extents is freed and again available for transaction logging.
69
Note:
You can only archive the transaction log files if you have transaction logging enabled and you are using archive mode. This command does not apply if you have transaction logging enabled in circular mode or if transaction logging is not enabled at all. If you try to issue it, you will receive an error message. 3.1.3.1 When to use archive log If the Domino server runs with archive transaction logging enabled it requires that allocated transaction log space is regularly freed. Otherwise, the transaction log could fill up and the Domino server will stop. Therefore, it is important to regularly run the archive log command, for example, daily or even hourly, to prevent the Domino server from halting under these conditions. You can specify high and low threshold values using the THRESHOLD parameter as a percentage of the log capacity with the archivelog command. This enables you to control whether or not filled log extents should be backed up when the command is run. By specifying a high threshold value with the archivelog command, for example 80%, you want TDP for Lotus Domino to back up the archive log extents only when the total transaction log utilization exceeds 80%. If so, the log extents are backed up to Tivoli Storage Manager server and transaction log space is freed. If you also specify a low threshold value with the archivelog command, for example 20%, TDP for Lotus Domino stops backing up log extents as soon as the log utilization is below 20%. This mechanism allows you to set up a strategy where sufficient log space is allocated to handle a normal days update processing. Once a day (typically at a time of low processing demand), archive the logs without specifying any threshold values. This ensures that all the eligible logs will be archived. Then, schedule an hourly archive log operation, with appropriate threshold values specified. This will allow the system to respond to an unexpectedly high change rate on the database, and corresponding heavy log usage, by only archiving the logs in peak processing periods when absolutely necessary. Experienced Tivoli Storage Manager server administrators will be familiar with this type of strategy, because it is analogous to the recommended setup and scheduling of migration from their disk storage pools. Unfortunately, there is no way to query the current utilization of the Domino database transaction log.
70
Note
At Version 1.1.1.0 and higher of TDP for Lotus Domino, when used with Version 5.0.4 or higher of Domino server, the active transaction log will also be backed up. The active transaction log will be backed up as part of normal archivelog processing unless you enter a specific low threshold instead of the default value of 0.
Example 4 In the following command, we back up the eligible transaction log extents (Figure 22).
notes1@ /palana >domdsmc archivelog Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino transaction log backup... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Backing up archivelog file /palanalog/S0000012.TXN Full: 0 Read: 67109888 Written: 67109888 Rate: 3230.97 Kb/Sec Backup of /palanalog/S0000012.TXN completed successfully.
Total Domino log files ready for backup: 1 Total Domino log files backed up: 1 Throughput rate: Total bytes transferred: Elapsed processing time: 3230.81 Kb/Sec 67109888 20.29 Secs
Example 5 In the following command, we conditionally back up the current transaction extents by specifying a high and a low threshold for the transaction log space utilization. If the log space utilization exceeds 80%, log extents are backed up and freed until the utilization drops to 20%. See Figure 23.
71
notes1@ /palana >domdsmc archivelog /threshold=80,20 Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino transaction log backup... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Backing up archivelog file /palanalog/S0000013.TXN Full: 0 Read: 67109888 Written: 67109888 Rate: 3505.03 Kb/Sec Backup of /palanalog/S0000013.TXN completed successfully. Backing up archivelog file /palanalog/S0000014.TXN Full: 0 Read: 67109888 Written: 67109888 Rate: 3846.29 Kb/Sec Backup of /palanalog/S0000014.TXN completed successfully.
Total Domino log files ready for backup: 2 Total Domino log files backed up: 2 Throughput rate: Total bytes transferred: Elapsed processing time: 3667.43 Kb/Sec 134219776 35.74 Secs
3.2 Database recovery

When you restore a Domino database, you copy the appropriate backup version from the Tivoli Storage Manager server down to the Domino server. By default, it will be put into a pending, offline state. In order to activate it, or bring it online, you will need to run a separate operation. This activate function can also optionally restore and apply the appropriate transactions from the log before bringing the database online. Alternatively, you can specify to activate the database at the same time as you restore it. The reason for having the database restore and activate options available as either a one or two step process is because of the way logged transactions are applied. You might be restoring a number of databases and want to apply the log to each one. However, there is only one set of transaction log extents shared among all the databases. If you restored and activated each one in turn, you would incur significantly more processing overhead, as the transaction log extents would be applied separately and sequentially for each database. The same transaction log extents also might have to be fetched multiple times from the Tivoli Storage Manager server. Instead, if you restore
72
the databases (without activation) and leave them in the pending state until the end, you can then run a single activate process for all of them. The required transaction log extents will be fetched once from the backup server, and applying the transactions for all the restored databases is performed at once. This avoids restoring the same transaction log extents multiple times. Restoring and updating a database with current changes from the transaction log is a two-step process implemented by the restore and activatedbs commands.
3.2.1 Restore
The restore is the first step of the two-stage recovery process of a database. The restore function restores a single database or a group of databases from Tivoli Storage Manager server to the Domino server. When you restore a database, it is temporarily stored as an offline database. This temporary database is in a pending state and not available to the Domino server. As naming convention for this temporary database, it uses the database file and a DAD suffix. For example, if you restore a database test.nsf, it is first stored as test.nsf.dad. The second step of the recovery process of a database is bringing the database online to the Domino server, the so-called activation. If you want to restore a database without applying transactions from the transaction log you can combine the two steps of the recovery by using the ACTIVATE=YES parameter with the restore command. However, if you use the ACTIVATE=YES parameter, then you will not be able to subsequently apply transactions from the transaction log. If you are planning to apply the transactions to the restored database to get a more current state of the database, you must use the ACTIVATE=NO parameter (default) with the restore command. You can also specify a certain date and time to perform a point-in-time restore of a database by using the PIT parameter with the restore command. With this option, the most recent database backup images available before the specified date and time are restored. Logged databases can then be rolled forward to that point by specifying the same date and time values on the /APPLYLOGS option of the activatedbs command. If you want to restore inactive database versions, use the PICK option with SHOWALI to display all backups. You can then select an inactive database for restore.
73
After doing the restore, if you do not specify ACTIVATE=YES, you then need to do the second step of the database recovery, activation of the database. You can restore the database to a different file name. You can also restore a group of databases to a different directory and preserve existing file names. You can also specify whether or not to overwrite an existing database of the same name (the default is to overwrite).
Example 6 The following command restores the database homepage.nsf to its original location, at a previous point in time. The temporary name of the restored file is homepage.nsf.dad. See Figure 24.
notes1@ /palana >domdsmc restore homepage.nsf /pit=11/02/2000,08:00:00 Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database restore... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Restoring database homepage.nsf, 1 of 1, to /palana/homepage.nsf.dad Full: 0 Read: 0 Written: 0 Rate: 0.00 Kb/Sec Waiting for TSM server... Full: 0 Read: 458752 Written: 458752 Rate: 55.81 Kb/Sec Restore of homepage.nsf completed successfully.
database database database database
backups inspected: backups requested for restore: backups restored: activated:
1 1 1 0 55.81 Kb/Sec 458752 8.03 Secs
Example 7 The following command restores the database homepage.nsf to its original location and activates immediately after the restore. Since no transactions
74
are applied to the logged database, the DBIID of the database changes as Lotus Domino understands that this specific database is a new version of the old database. You would need to run an incremental backup immediately to ensure that the database can be completely recovered in case of a future failure. See Figure 25.
notes1@ /palana >domdsmc restore homepage.nsf /activate=yes Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database restore... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Restoring database homepage.nsf, 1 of 1, to /palana/homepage.nsf 11/22/00 01:47:46 PM Recovery Manager: Assigning new DBIID for /palana/homepage.nsf (need new backup for media recovery). Restore of homepage.nsf completed successfully.
1 1 1 1 128.77 Kb/Sec 458752 3.48 Secs
Example 8 In the following command, the database names.nsf is restored to another file name, names_temp.nsf. This can be useful you want to recover only single documents from a database. You just need to activate the restored database, names_temp.nsf, and open it from your Notes workspace. Select the documents you want to recover and copy them to the original database, names.nsf. Then you can delete the temporary restore database. See Figure 26.
75
notes1@ /palana >domdsmc restore names.nsf /into=names_temp.nsf Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database restore... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Restoring database names.nsf, 1 of 1, to /palana/names_temp.nsf.dad Full: 0 Read: 55312384 Written: 55312384 Rate: 3366.53 Kb/Sec Restore of names.nsf completed successfully.
1 1 1 0 3366.53 Kb/Sec 55312384 16.05 Secs
3.2.2 Activation of database

The activation is the second step of the two-stage process to recover a database. The activatedbs command brings restored databases online for use by the Domino server. You can optionally apply transactions from the transaction log to synchronize the database. This is done by using the APPLYLOGS parameter with the command. You can also specify a point-in-time with this parameter. When this is specified, transactions that are completed and committed before the specified date or time are applied to the restored database. This is usually done in conjunction with specifying the same date and time with the PIT parameter on the restore command. The date specified should be after the backup date of the backup copy of the database that is being restored. By default, all databases in a pending state will be activated together when you issue the activatedbs command. This is more efficient, because the transactions from the log are applied to all the databases together. To
76
activate only a subset of databases that are in a pending state, use the PICK parameter with the command. This displays a list of all databases in pending state and enables you to select which databases you want to bring online. Use the query pendingdbs command to find out which databases are in pending state.
Note
In the current release of the software, TDP for Lotus Domino does not prompt you when it activates a database which already exists at the Domino server; instead it replaces the existing database.
Example 9 This command will activate all databases that are in pending state and, at the same time, apply transactions until the specified date and time, 07/02/2000, 8:00a.m., to synchronize the activated database. If you use the APPLYLOGS parameter, then no new DBIID will be assigned to the activated database, because the archived transaction log will only apply transactions that have the same DBIID reference as the database. See Figure 27.
77
notes1@ /palana >domdsmc activate /applylogs=07/02/2000,08:00:00
Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database activation... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Starting archivelog recovery... Media Recovery Replay: 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 07/22/00 02:23:14 PM Recovery Manager: Media Recovery complete for /palana/homepage.nsf.dad, last update applied 07/01/00 01:30:39 PM. Archivelog recovery completed successfully. Activating database names_temp.nsf, 1 of 1, Activate of names_temp.nsf completed successfully.
Total pending databases inspected: 1 Total pending databases requested for activation: 1 Total pending databases activated: 1 Throughput rate: Total bytes transferred: 0.00 Kb/Sec 0
3.3 Inactivation of archive logs

Use this command to expire unneeded transaction log extents from the Tivoli Storage Manager server. Because there is a single shared transaction log for all logged databases on a Lotus Domino server, log extents within that log cannot be inactivated (and allowed to expire) until all backup versions of databases which require that log file for recovery are inactive. This command queries the database backups on the Tivoli Storage Manager server to determine which log extents are required by any active database backup. This command then inactivates the log extents that are no longer required (because the database backups were inactivated). This command should be run after full database backups are complete, so that the transaction log extents are inactivated after the database backups requiring them are inactivated. If you use different management classes for your databases, then we recommend that you bind the transaction log extents to the management
78
class with the longest period for the RETEXTRA parameter. If you dont, then the transaction log extents might be expired before their associated database backups. If this happens, then you cannot apply logs for databases that still need those extents. Since transaction log file names are unique and automatically assigned when needed by the Domino R5 server, they will not expire because of version limit values in the management class. The output of the inactivatelogs command simply returns then number of log extents inactivated, if any, as shown here.
notes1@ /palana >domdsmc inactivatelogs Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Number of Logs Inactivated: 1
3.4 Restoring individual archive logs

Support has been added to allow recovery of one or more archived transaction log extents independent of a database recovery. This function is available from the command line with the restorelogarchive command. This function is provided to support the capability to recover the transaction log introduced in Domino server 5.03. If invoked without parameters, the last active transaction log extent archived to the Tivoli Storage Manager server will be restored. Otherwise, you can select other transaction log extents to be restored by using the PICK option. This command would be used most commonly in the situation where there is a media failure of the recovery log. When using archive transaction logging, archived transaction log extents contain updates to logged databases that may not yet be captured in a full database backup. Recovering a database to the most recent available backup requires restoring the last full backup plus applying updates to that backup from the archived transaction log files. In order for these archived transaction log files to be used for database recovery, the current transaction log ID must match that of the archived log files. However, if you lose the current transaction log because of media failure, creating a new one will result in a new log ID, and, therefore, the archived log files would be unusable for database recovery, since you cannot use the transaction log after the logger ID is changed. Therefore, we need a way to restore the transaction log instead of recreating it.
79
We describe how this function can be used in a disaster recovery scenario, where both database and recovery log are destroyed in 4.7.2, Disaster recovery on page 136.
3.5 Miscellaneous
In this section, we discuss some other functions of TDP for Domino, including query commands, setting a tuning parameter in the preferences file, changing the client password, as well as information about the logging facilities is provided.
3.5.1 Queries
A number of query commands are available in the TDP for Domino client. Most of them will return results which are obtained from the Tivoli Storage Manager server: Query Query Query Query Query Query ADSMserver DBbackup Domino Logarchive Pendingdbs Preferences
80
3.5.1.1 QUERY ADSMSERVER Use this command to query the Tivoli Storage Manager server information.
notes1@ /home/palana >domdsmc query adsmserver Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Tivoli Storage Manager Server Connection Information ---------------------------------------------------Nodename ............................... PALANA_TDP NetWork Host Name of Server ............ 9.1.150.113 TSM API Version ........................ Version 3, Release 1, Level 7 Server Name ............................ Server Type ............................ Server Version ......................... Compression Mode ....................... Domain Name ............................ Active Policy Set ...................... Default Management Class ............... PALANA1 AIX-RS/6000 Version 3, Release 7, Level 1.0 Client Determined DOMINO DOMINO DOMINO
3.5.1.2 QUERY DBBACKUP This command displays a list of database and template backups that are stored on the Tivoli Storage Manager server. Active and inactive databases can be displayed, depending on whether you specify the INACTIVE parameter, and the output also tells you whether the database is logged or not.
notes1@ /home/palana >domdsmc query dbbackup homepage.nsf /inactive Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Database Backup List -------------------Domino Server: /palana -------------DB Backup Date Size A/I Logged Database Title --------------------- --------- --- ------ -------------07/22/2000 14:29:45 448.00KB A Yes homepage 07/22/2000 14:28:03 448.00KB I Yes homepage Database File ------------homepage.nsf homepage.nsf
81
3.5.1.3 QUERY DOMINO This command generally displays Lotus Domino server information, including the type of logging which is being used. If you also give a database name pattern, then a list of databases and templates matching that pattern on the server is also displayed.
notes1@ /home/palana >domdsmc query domino homepage.nsf Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Domino Server Information ------------------------Domino Server Name: palana Domino Server Level: 5.0 Domino Server Build: 166 Logging: Archival Domino Database Information --------------------------Last Modified Date -----------------07/09/2000 14:28:04 Size Logged ---- -----448.00KB Yes Database Title -------------homepage Database -------homepage.nsf
If you have a partitioned Lotus Domino environment, then you can use the /CONFIGFILE parameter to distinguish between the two Lotus Domino servers. 3.5.1.4 QUERY LOGARCHIVE Displays a list of the archived transaction log extents. The default is to display only active log extents, however, inactive extents can also be displayed by specifying the /INACTIVE parameter.
82
notes1@ /home/palana >domdsmc query logarchive Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Domino Server: /palana -------------Logger Id: OF082567B7:00007FAC-OND9030000:7C0ACDA1 ---------Transaction Log Filename -----------S0000014.TXN S0000013.TXN S0000012.TXN S0000011.TXN
Log Archive Date --------------------07/23/2000 12:17:01 07/23/2000 12:16:43 07/22/2000 11:14:27 07/08/2000 16:46:44
A/I --A A A A
Size -----64MB 64MB 64MB 64MB
3.5.1.5 QUERY PENDINGDBS This command displays a list of all the databases that have been restored, but not yet activated.
notes1@ /home/palana >domdsmc query pendingdbs Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Pending Database List --------------------Domino Server: /palana -------------Backup Time Stamp Size A/I Logged Database Title --------------------- --------- --- ------ -------------07/22/2000 14:29:45 448.00KB A Yes homepage Database File ------------homepage.nsf
3.5.1.6 QUERY PREFERENCES This command shows a list of the current values set in the preference files for TDP for Lotus Domino.
83
C:\Program Files\Tivoli\TSM\Domino\domdsmc query preferences Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 1.0 (C) Copyright IBM Corporation 1999, 2000. All rights reserved. License file exists and contains valid license data. TDP for Lotus Domino Preferences -------------------------------BUFFers ........................ 3 BUFFERSIze ..................... 1024 DATEformat ..................... 1 LOGFile ........................ domdsm.log LOGPRUne ....................... 60 MOUNTWait ...................... Yes NOTESInipath ................... C:\lotus\domino\senegal NUMBerformat.................... 1 REPlace..........................Yes SUBDir ......................... No TIMEformat ..................... 1
3.5.2 Changing the preferences file

The preferences displayed above can be changed using various domdsmc set <option> commands. Also, if using TDP for Lotus Domino for NT, which includes a GUI, you have the option of graphically displaying and setting preferences. Section 3.8.1, Application client settings on page 101 describes the GUI preference editor and also explains the various options which can be set in more detail. The domdsmc set commands provided are:
domdsmc domdsmc domdsmc domdsmc domdsmc domdsmc domdsmc domdsmc domdsmc domdsmc domdsmc set set set set set set set set set set set buffers buffersize dateformat logfile logprune mountwait notesinipath numberformat replace subdir timeformat
84
An example of executing a command to change the preferences is shown here:
C:\Program Files\Tivoli\TSM\Domino\domdsmc set buffers=8 Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 1.0 (C) Copyright IBM Corporation 1999, 2000. All rights reserved. License file exists and contains valid license data. ACD5217I The preference has been set successfully.
3.5.3 Changing the Tivoli Storage Manager password

This command changes the Tivoli Storage Manager password that is used by the TDP for Lotus Domino client. You can either enter the old password plus the new password and a confirmation all on the command line, in which case all the entries will be displayed on the screen, or you can omit these parameters and you will be prompted for each entry in turn. In this case, the passwords will be entered into a protected field so that they will not be displayed.
notes1@ /home/palana >domdsmc changeadsmpwd tdp new new Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. ACD0260I Password successfully changed.
3.5.4 TDP for Domino message logging

This section shows details of the logging facilities provided on both the TDP for Domino client and the Tivoli Storage Manager server. You will want to include checking the logs both as part of regular Tivoli Storage Manager operations and also to know where the logs are in case of problems where you want to perform error diagnosis.
85
3.5.4.1 TDP for Domino client logging TDP for Lotus Domino logs errors and status messages to a number of locations. Here are the important files which you should monitor to ensure correct operations: domdsm.log: TDP for Lotus Domino log file created by default in the application client installation directory. This file indicates the date and time of a backup, data backed up, and any error messages or completion codes. This file is very important and should be monitored daily. It also logs other TDP operations, such as queries. Here is some sample output from this file showing a query operation and a subsequent database backup:
------------------------------------------------------------------------07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 07/18/2000 15:13:00 15:13:00 15:13:00 15:13:00 15:13:00 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:14:09 15:15:17 15:15:17 15:15:17 15:15:17 15:15:17 15:15:17 ========================================================================= Request : QUERY DOMINO Database Input List : denise\* Process Subdirectories? : No ------------------------------------------------------------------------========================================================================= Request : SELECTIVE Database Input List : Number of Buffers : 3 Buffer Size : 1024 Logged Databases Only? : No Wait for Tape Mounts? : Yes Process Subdirectories? : Yes TSM Options File : C:\PROGRA~1\Tivoli\TSM\domino\dsm.opt TSM Nodename Override : ------------------------------------------------------------------------Total Domino databases inspected: 1 Total Domino databases backed up: 1 Total Domino databases excluded: 0 Throughput rate: 1,158.39 Kb/Sec Total bytes transferred: 79,429,632 Elapsed processing time: 66.96 Secs
dsierror.log: Tivoli Storage Manager API logs API error information, by default, to the dsierror.log file in the directory where TDP for Lotus Domino is installed. This file does not contain backup statistics. dsmerror.log: The Tivoli Storage Manager backup/archive client logs errors here. By default, this file is located in the backup/archive installation directory. dsmsched.log: Tivoli Storage Manager scheduler logs information to this file. By default, this file is located in the directory where the Tivoli Storage Manager backup-archive client is installed and is used for the same purpose as in the backup-archive client. We recommended, however, (in 2.6.1.1, Install and start scheduler service for TDP on Windows on page 46) when installing the scheduler service for the TDP for Domino client, to specify a separate scheduler log file location. In this way, scheduler messages will be separated between regular backup/archive client
86
operations and those for TDP for Domino. Here is some sample output showing how a scheduled operation to archive the Domino transaction log on an AIX server was performed:
03/17/00 12:29:06 --- SCHEDULEREC QUERY BEGIN 03/17/00 12:29:06 --- SCHEDULEREC QUERY END 03/17/00 12:29:06 Next operation scheduled: 03/17/00 12:29:06 -----------------------------------------------------------03/17/00 12:29:06 Schedule Name: AIX_ARCHIVE_LOGS 03/17/00 12:29:06 Action: Command 03/17/00 12:29:06 Objects: /notescode/tdpclient/usr/tivoli/tsm/c lient/domino/bin/domarc.smp 03/17/00 12:29:06 Options: 03/17/00 12:29:06 Server Window Start: 12:29:00 on 03/17/00 03/17/00 12:29:06 -----------------------------------------------------------03/17/00 12:29:06 Executing scheduled command now. 03/17/00 12:29:06 Executing Operating System command or script: /notescode/tdpclient/usr/tivoli/tsm/client/domino/bin/domarc.smp 03/17/00 12:29:06 Finished command. Return code is: 0
3.5.4.2 Tivoli Storage Manager server logging Certain TDP for Domino messages are also logged to the Tivoli Storage Manager server activity log which can be queried with the query actlog command. If you are at Version 1.1.1.0 or higher of TDP for Domino, and Version 3.7.3 or higher of the Tivoli Storage Manager server, you will see that these messages are more clearly identified as coming from the API client.
87
Before these software levels, an activity log output showing a selective database backup looked like this:
07/18/00 07/18/00
07/18/00
07/18/00
07/18/00
07/18/00
14:50:37 ANR0406I Session 372 started for node SENEGAL_TDP (TDP Domino NT) (Tcp/Ip 9.1.150.42(1044)). 14:50:37 ANE4991I (Session: 372, Node: SENEGAL_TDP) TDP Domino NT ANE4991 TDP for Lotus Domino: Starting selective database backup from server senegal. 14:50:37 ANE4991I (Session: 372, Node: SENEGAL_TDP) TDP Domino NT ANE4991 TDP for Lotus Domino: Starting backup of database denise\philip.nsf from server senegal. 14:51:44 ANE4991I (Session: 372, Node: SENEGAL_TDP) TDP Domino NT ANE4991 TDP for Lotus Domino: Backup of database denise\philip.nsf from server senegal completed successfully. 14:51:44 ANE4991I (Session: 372, Node: SENEGAL_TDP) TDP Domino NT ANE4991 TDP for Lotus Domino: Selective database backup from server senegal complete. Total Domino databases backed up: 1 Total bytes transferred: 79429632 Elapsed processing time: 67.32 Secs Throughput rate: 1152.25 Kb/Sec 14:51:44 ANR0403I Session 372 ended for node SENEGAL_TDP (TDP Domino NT).
With the later client and server releases, TDP for Domino messages which potentially can be sent to the server are assigned specific numbers in the range ACD5200 to ACD5299. However, not all messages in this range are actually logged. The TDP for Lotus Domino Installation and Users Guide for each platform gives a description of all the possible messages and indicates (by the field Centrally Logged) which messages can be sent to the server.
88
The same backup event as in the previous screen in the activity log of the Tivoli Storage Manager server at the later software levels now looks like:
07/18/00 07/18/00
07/18/00
07/18/00 07/18/00
07/18/00
07/18/00
15:10:06 ANR0406I Session 379 started for node SENEGAL (TDP Domino NT) (Tcp/Ip 9.1.150.42(1035)). 15:10:06 ANE4991I (Session: 379, Node: SENEGAL) TDP Domino NT ACD5208 TDP for Lotus Domino: Starting selective database backup from server senegal. 15:10:06 ANE4991I (Session: 379, Node: SENEGAL) TDP Domino NT ACD5200 TDP for Lotus Domino: Starting backup of database denise\philip.nsf from server senegal. 15:10:18 ANR2017I Administrator ADMIN issued command: QUERY ACTLOG 15:11:13 ANE4991I (Session: 379, Node: SENEGAL) TDP Domino NT ACD5201 TDP for Lotus Domino: Backup of database denise\philip.nsf from server senegal completed successfully. 15:11:13 ANE4991I (Session: 379, Node: SENEGAL) TDP Domino NT ACD5209 TDP for Lotus Domino: Selective database backup from server senegal complete. Total Domino databases backed up: 1 Total bytes transferred: 79429632 Elapsed processing time: 66.96 Secs Throughput rate: 1158.39 Kb/Sec 15:11:13 ANR0403I Session 379 ended for node SENEGAL (TDP Domino NT).
Eligible TDP for Domino events, like other client and server events, also can be sent to additional event receivers, such as the Tivoli Enterprise Console (TEC), SNMP managers, or a user written exit using the enable events command. Refer to the Administrators Guide for your Tivoli Storage Manager Server platform for more details on how to do this. See Appendix C, Related publications on page 149. Also, if you have a TEC installed, there are unique event identifiers for the messages sent there. These are in the format TSM_TDP_DOMINO_ACD52XX.
3.6 Graphical user interface

A graphical user interface is available for TDP for Lotus Domino on the Windows NT and 2000 platforms only. The GUI provides nearly all of the same functions of the command line, so these are not discussed in detail here. After you install TDP for Lotus Domino, you will be able to choose between either the command line syntax and the GUI for TDP operations.
89
The GUI runs on the server where TDP for Domino is installed. To invoke it: 1. Click Start. 2. Go to Programs. 3. Go to Tivoli Storage Manager. 4. Go to Tivoli Data Protection for Lotus Domino. 5. Click Domino Client GUI. After the welcome screen, you will see the TDP for Lotus Domino start window (Figure 28). It defaults to the backup operation, and note that no databases appear in the backup window because the server directories on the left hand side have not yet been expanded. When you click the plus sign to traverse the subdirectories, any eligible database and template files will be displayed in the right hand window.
90
Figure 28. TDP for Lotus Domino NT GUI
3.6.1 Backup
You can take two types of backups: incremental and selective backups. 3.6.1.1 Selective Backup If you want to unconditionally backup one or more databases: 1. Click the Backup tab. 2. In the left box, you can see the Server name, the Domino Data Directory, and all the directories pertaining to it. Go into the directory where the database resides. 3. On the right box, select the option Selective. 4. Select the database or databases required for backup from that directory.
91
5. Repeat steps 2 to 4 to select databases in any other directory. 6. Click the Backup button. The window for selective backup is shown in Figure 29.
Figure 29. GUI: Selective backup
A window will show you each database as it is backed up, along with its size and how long it took. At the end of the operation you will see the total number of bytes sent, elapsed time and transfer rate. 3.6.1.2 Incremental Backup If you want incrementally backup all the databases, or all the databases in one or more directories: 1. Click the Backup tab. 2. In the left box, you can see the Server name, the Domino Data Directory and all the directories pertaining to it. Go into the directory where the databases reside. You cannot select individual databases for incremental backup at the GUI, only whole directories.
92
3. On the right box, select the option Incremental. 4. Click the Backup button. The window for incremental backup is shown in Figure 30. Note how the databases are grayed out indicating that you cannot select them individually.
Figure 30. GUI: Incremental backup
A window will show you each selected database as it is backed up, along with its size and how long it took. At the end of the operation, you will see the total number of bytes sent, elapsed time, and transfer rate.
3.6.2 Restore
Data restoration with TDP for Lotus Domino is a two-step activity: 1. Restoration 2. Apply transactions from the log (if applicable) and activate the database If you dont want to apply the transaction log to the restored database, you can combine the two stage restoration activity to a one stage activity. But, if
93
the database is restored and immediately activated, you will not be able to subsequently apply the transaction log. To apply logged transactions, you must follow the two stage restore method. You may also do a point in time restore of a database, in case of multiple backup versions. The restore window behaves the same way as the GUI Tivoli Storage Manager backup/archive client, that is, by default only active backups are displayed. To display inactive backups as well, select Show active/inactive backups from the View pull-down menu. Here are the steps required to perform a point-in-time restore with immediate activation (single stage restore): 1. Click the Restore tab. 2. In the left hand window, you can see the Tivoli Storage Manager node name, the Domino Data Directory, and all the directories underneath it. Go into the directory where the databases reside. 3. On the right hand window, select the option Activate. 4. If required, click the Set Point in Time button, and select appropriate date and time, otherwise the most recent backup will be restored. 5. Click the Restore button. Figure 31 shows these selections.
94
Figure 31. GUI: Point-in-time restore (single stage)
If you dont select the option Activate during restoration, you have to activate the database and apply the transaction log in the second stage. The following steps apply the transaction log and activate the database: 1. Click the Activate tab. 2. In the left hand window, you can see the option Activation to your Domino server, which expands to the list of pending databases to be activated. 3. In the right hand window, select the appropriate database, select the option Apply Logs and you can also select Point in Time option, which enables you to synchronize the database to the specified date and time. 4. Click the Activate button. The window where you can apply logged transactions and activate the database is shown in Figure 32.
95
Figure 32. GUI: Activation
3.6.3 Transaction logs

As already discussed, each Domino server or partition transaction log requires regular archiving and inactivation. This section discusses how to archive transaction logs, query transaction logs, restore transaction logs, and inactivate transaction logs. To archive the transaction log, select Archive Logs from the Utilities menubar. The Domino server will be queried to determine if there are any transaction log extents eligible for archive, and if so, will archive them. You will see a display similar to Figure 33 as each eligible archive log extent is activated. Note that the GUI does not provide the equivalent of the command line THRESHOLD option.
96
Figure 33. GUI: Archive Log Progress
Once the transaction log extents are archived, you can issue a query to display how many active/inactive transaction logs are available, the date and time the transaction logs were archived, and so on. The same option (if at Version 1.1.1.0 or higher of TDP for Domino) allows you to restore archived transaction log extents. To display and optionally restore archived log extents, you need to select View/Restore Log Archive from the Utilities menu. By default, only active extents will be displayed, however, you can select to display inactive ones as well. You can select to restore the extents to their original location or to another directory. The GUI for querying log archives is shown in Figure 34.
97
Figure 34. GUI: View/Restore Log Archive
As we have already mentioned, it is very important to regularly inactivate the archived transaction log extents, to avoid running out of disk space. You can inactivate the archived log extents by selecting Inactivate Logs from the Utilities menu. The GUI for Inactivating Logs is shown in Figure 35.
98
Figure 35. GUI: Inactivate logs
After selecting the server, you will receive a message telling you how many archive log extents were inactivated.
3.7 Restoring logged databases to an alternative Domino server

It is possible to restore logged databases to a different Domino server from the one where they were originally backed up. The following procedure describes how to use an alternate server to restore logged databases. You can only use this process if your Domino server is at 5.03 or above. 1. Install the same level Domino server code as is used on the production Domino server to a separate machine. This Domino server can be left unconfigured if the restored databases are to be moved back to the production Domino server or accessed via a remote Domino client. Configure the Domino server installation only if you plan to launch this server instance for some other purpose. You will also need to install the TDP for Lotus Domino code on this machine. 2. If the Domino directory contains a notes.ini file, rename it to notes.save. 3. Create a directory to contain the restored databases as well as a directory to contain the restored log extents. The databases and log files may be
99
restored to the same directory as long as there is enough space on the volume. 4. Create a notes.ini file with the entries listed below. This notes.ini is to be used only in this special restore process. It may be placed in the Domino directory or in any other directory of your choice.
[Notes] Directory=<directory for restored dbs> KeyFilename=<directory for restored dbs>\server.id TRANSLOG_Status=0 TRANSLOG_Style=1 TRANSLOG_Path=<directory for restored log files> TRANSLOG_MEDIAONLY=1
5. Place a copy of the production Domino server's server.id file in the directory created for restored databases. 6. If you have placed the notes.ini file to be used in the restore process in a directory different from the default Domino directory, modify TDP for Lotus Domino's configuration file to point to the location of the notes.ini file as follows:
DOMDSMC SET Notesinipath=<directory for restored databases>
7. Note that transaction logging is disabled at this point. Using TDP for Lotus Domino, restore the transaction log extent to be used in the log recovery procedure to the Domino transaction log directory. This should be the last transaction log file archived. (To be able to apply the latest updates from the transaction log, be sure to do an archive of the transaction log on the production server before doing this step.) If using the TDP for Lotus Domino GUI, close it before proceeding to the next step. 8. Enable transaction logging by modifying the notes.ini file created in step 4 for the special restore process with the following setting:
TRANSLOG_Status=1
9. Restore (but don't activate) the databases you want to recover to the latest state using archived log extents with TDP for Lotus Domino. This will trigger the Domino transaction log recovery process which may take some time.
100
10.Use TDP for Lotus Domino to activate the databases you are recovering and apply the transaction log. 11.Copy the recovered databases to the production server or access them through a remote Notes client to copy individual documents as desired.
Very Important
Do not attempt to open or access the restored databases with the local Domino server if the entire databases are ultimately to be copied to the production Domino server. If you access them first with the local Domino server, you will have to run the Fixup process after copying them to resolve inconsistencies on the production Domino server. 12.If the Domino server used for the recovery had been configured and you saved its notes.ini file in step 2, rename that notes.save file back to notes.ini to be able to launch the server. Lotus Domino also provides a complete Disaster Recovery procedure, which will be described in 4.7.2, Disaster recovery on page 136.
3.8 Miscellaneous GUI functions

Here we discuss how to access and change various non-backup/restore related functions from within the Windows GUI for TDP for Domino. These functions can be accomplished at the command line using the domdsmc query preferences and domdsmc set <option> commands (see 3.5.1, Queries on page 80 and 3.5.2, Changing the preferences file on page 84).
3.8.1 Application client settings

Figure 36 shows the GUI preference editor. It is divided into the following sections and functions, and more information on each option is available in the online help.
101
Figure 36. GUI: Preference editor
Each tab of the GUI preference editor is explained here:
General Wait for tape mounts: Specifies whether TDP will wait or not when an operation is performed which requires a tape mount (for example, restoring a database which is located on tape not currently mounted at the Tivoli Storage Manager server). If it is not selected, then the requested operation will end automatically if a tape mount is required. Normally you would check this option, especially if you have an automated tape library, since manual intervention will usually not be required.
Replace existing files on restore: Specifies whether or not to overwrite existing databases or transaction logs when restoring. This option is available at TDP Version 1.1.1.0 and above. Include subdirectories: This option only applies to command line client operations (domdsmc) and controls whether or not subdirectories are included when processing a backup or restore operation.
102
Notes.INI path: Specifies the directory where the file notes.ini is stored. This is mainly useful when you are operating in a partitioned server environment, as it allows you to change which internal server is being operated on. You have to restart TDP for Domino before any change to this will take effect.
Activity logging Log file name: Specifies the location of the log file for TDP for Domino. The default is DOMDSM.LOG in the installation directory.
Prune old entries and Keep old entries: Specify whether the logfile should be pruned, and if so, how many days of entries to retain. You can then select the Prune now button to immediately truncate the log file.
Performance Number of buffers to use: Specifies the number of buffers to use when transferring data between the Domino server API and the Tivoli Storage Manager API.
Buffer size: Specifies the size of the buffers. These two settings are the main options specific to TDP for Domino which can affect performance. See 3.9, TDP for Lotus Domino performance on page 105 for more information.
Regional Date format Time format Number format

These options allow you to select alternative formats for date, time, and numerical displays (for example, mm/dd/yyyy, or dd-mm-yyyy).
3.8.2 Password
You can change your client password for accessing Tivoli Storage Manager. You can change the existing password from the Utilities pull-down menu as shown in Figure 37.
103
Figure 37. GUI: Change TSM Password
3.8.3 Other information

You can also view additional information about the Tivoli Storage Manager and Lotus Domino servers being accessed. Figure 38 and Figure 39 show these information screens, which can be displayed by selecting them from the Help pull-down menu. This is a quick way to see what level of Tivoli Storage Manager and Domino server software is being used, as well as what mode of transaction logging, if any.
104
Figure 38. Additional information about Tivoli Storage Manager server
Figure 39. Additional information about Lotus Domino server
3.9 TDP for Lotus Domino performance

Performance is usually measured in terms of either overall throughput (Megabytes per second, Gigabytes per hour, and so on) or time to complete a backup or restore operation. Measuring performance is easier than trying to improve it, since there are many factors which can affect the actual numbers achieved. The hardware resources available on both the Tivoli Storage Manager client and server (for example, number and speed of disks, tape
105
drives, CPU capacity, I/O bandwidth, available memory and network topology and resources) all have a great impact on the performance capability of an environment. The logical resources and configuration are equally important, such as, the placement of critical files and filesystems on the disks, other applications running simultaneously, level of network traffic, and general tuning of the operating system and applications. Changing any of these factors may have a positive or negative effect on performance. There are also a large number of tunable parameters within the Tivoli Storage Manager server and client themselves. A detailed discussion of Tivoli Storage Manager performance issues and how to tune it is contained in the ADSM Performance and Tuning Guide that is available from your Tivoli or IBM representative. This guide is also available at:
http://www.tivoli.com/support/storage_mgt/adsm/pfguide/tgv31mst.htm
For the TDP for Lotus Domino product, there are only two tunable options, number of buffers and buffersize. Methods to set these are discussed in 3.5.2, Changing the preferences file on page 84 and 3.8.1, Application client settings on page 101. The default setting is to use three buffers, each consisting of 1024 kilobytes, and the maximum possible settings are 8 buffers and 8192 kilobytes, respectively. The optimum configuration will depend on the available resources. As with any performance tuning exercise, the primary objective is to locate the bottleneck, that is, the system resource which is constraining the performance, to be able to determine what adjustments will actually improve performance. In this section, we suggest some general guidelines and things to be aware of when trying to improve performance. If you run a single TDP for Domino session, increasing the buffersize and number of buffers may yield some performance improvement, but it is important to carefully test the effect of this in your own environment. Increasing these parameters is most likely to increase performance when there are frequent temporary fluctuations in the available network bandwidth. For example, if the network bandwidth fluctuates quite a bit due to spikes in other network traffic, then using additional buffers for the TDP client can help smooth out those peaks and valleys and yield a better overall throughput. However, if the network tends to remain at a somewhat steady bandwidth or there is another performance limiting factor before the network, then additional buffers will probably not make much difference. Also, using the largest possible buffer size might degrade performance in a memory constrained environment by causing excessive swapping.
106
Another way to increase performance is to run multiple parallel instances of the TDP backup commands. Each instance would backup different databases. For example, if your Domino server is configured in such a way that the databases are spread across separate physical disks, perhaps even using separate disk I/O adapters, you may see a performance improvement by running multiple domdsmc selective or incremental commands concurrently, with each one specifying a different subset of databases to backup. Again, this will be most likely to improve performance if you have sufficient CPU capacity and your I/O and network pipes have enough bandwidth to sustain and support multiple sessions. For example, if a single TDP for Domino session is already saturating your network interface card from the client, then running multiple instances may actually degrade performance, but if system resources are available to sustain multiple TDP client instances, it will usually be the case that using multiple instances will provide more benefit than tuning the buffer parameters.
107
108
Chapter 4. Backup strategy and recovery scenarios

In this chapter, we give you some recommendations on how to backup your Domino environment, suggested automatic schedules, and some recovery procedures from various failures. We also discuss some Domino internal issues and how they affect backup, including database and directory links and shared mail.
4.1 Domino considerations and backup

Three things which can greatly affect how and when backup should be done are the type of transaction logging used, Database Instance Identifier (DBIID), and compaction of R5 databases.
4.1.1 Transaction logging modes

One of the major changes between Lotus Domino Release 4 and Release 5 is transaction logging. When it is enabled on the server all database changes are logged. These changes can be opening a new document, adding text, and saving the document, and so on. There are two types of transaction logging: circular and archive. We have explained the differences in 1.1.8, Transaction logging on page 13. Below we summarize the advantages and disadvantages of using either method. Circular logging - Uses less space on the Domino R5 server and the space usage is controlled since only one log extent of a designated maximum size is required. - You dont need to worry about the transaction log filling up, since old data is written (first in, first out) once the allocated file size has been reached with new transactions. - May be most appropriate for hub servers which perform an administrative function, for example, a mail hub or replication hub if the server has no mail or application databases that will require restore from backup. - Limits the administrators recovery options, since it may not be possible to apply updates to a restored database if the log has wrapped since the backup was taken. In this case, you should perform more frequent full backups to minimize the possibility of losing database updates when restoring.
109
Archive logging - The size of the transaction log is not fixed, since Domino will continue to allocate new extents as required. Space will not be freed until the log extents are archived by your backup utility. If you do not perform regular log archiving you run the risk of running out of disk space or causing the Domino server to halt. - Is the recommended transaction log mode by Lotus. - Gives you more backup and restore options than with circular or no logging. Archiving the transaction log is normally faster than performing complete backup operations. However you still need to perform regular database backups so that your restore and recovery process does not become too long. This is because this process requires restoring the last complete backup, then all the required transaction log extents, and then applying all the relevant transactions from the log. Archive transaction logging also gives you the option of performing point-in-time recovery of databases by applying different parts of the transaction logs. Your usage of TDP for Domino backup techniques will depend on if and how you have implemented transaction logging for your databases. Table 4 describes what type of backup you should use depending on your server R5 characteristics
Table 4. Backup possibilities for transaction logging modes
Transaction Logging None Circular Archive
Selective backup Yes, but unnecessary Yes Yes
Incremental backup Yes Yes Yes
Archive log N/A N/A Yes
In a Domino Release 5 environment without transaction logging enabled, you should use TDP for Lotus Domino to take regular incremental backups of your databases. If you have changes in your databases, the incremental backup will perform the backup of your database and if it was deleted it will be expired. Selective backups are not required and could possibly lead to wastage of Tivoli Storage Manager server storage space, as discussed in 3.1.2.1, When to use selective backup on page 68.
110
4.1.2 Changing the database instance identifier

We discussed the database instance identifier (DBIID) in 1.1.8.5, Transaction logging and the database instance ID on page 16. All the transactions recorded in the transaction log are keyed by a Database Instance Identifier (DBIID) which is unique for each database in a Domino server, and the DBIID must match that of a restored database in order for transactions in the log to be applied to the database. If the DBIID changes, a full backup must be taken immediately after, so that you can use subsequent updates on the transaction log to a restored backup of that database. Domino will assign a new DBIID to a R5 database when any of the following conditions occur: Transaction logging is enabled for the first time. System logging is disabled then re-enabled. The compact server task is run with options to reduce the database size (see 4.1.3 below). The fixup task is run on corrupt databases. A R5 database is moved from one logged server to another logged server or from an unlogged server to a logged server. Note that changing the log file location path or maximum log file size does not trigger a DBIID change, once transaction logging is being used.
4.1.3 Database compaction and the DBIID

Compaction of Domino databases is part of normal system administration and is performed to re-order data in a database, so that the data is stored contiguously, increasing the percent utilization of the database. Optionally, it can also reduce the file size. A third compacting option creates a new compacted copy of the database. The impact of compaction is important to consider in your backup strategy, because certain compacting processes will reset the DBIID. Domino administrators use compaction to ensure both efficient disk space utilization and database performance. You must be aware of when compaction tasks are run and what style of compaction is used so that you can coordinate these tasks, if necessary, with TDP for Domino database backups. More information on compacting is available in the Lotus Technical Notes Domino R5 Compact Not Reducing the Size of the Database, 173311; and Switches for COMPACT Server Task for Domino R4 and R5, 172454. These can be accessed at the Lotus Customer Support Web site, http://support.lotus.com. To find any of these articles, you can enter the
Backup strategy and recovery scenarios
111
article number in the Search by Keyword box, specifying to Search the Lotus Knowledge Base. 4.1.3.1 Compacting with space recovery only This style of compacting recovers unused space but does not reduce the size of the database. It does not change the DBIID, so the relationship between the compacted databases and the transaction log remains intact. This is the default method for compaction when run without options on logged databases and may be selected for non-logged databases by using the -b option on the command. 4.1.3.2 Compacting with space recovery and file size reduction This style of compacting does reduce the file size, as well as recovering unused space in the database. It takes more time to complete than the first style of compacting. It will assign a new DBIID, therefore, for logged databases, it is very important to know when this operation is performed so that a database backup can be scheduled immediately afterward. This method of compacting is the default for non-logged databases and may be selected for logged databases by using the -B option on the command. To optimize disk space utilization, Lotus recommends running this style of compaction on all R5 format databases once a week. 4.1.3.3 Copy-style compacting This style of compacting creates copies of databases and then deletes the original databases after compacting completes. Essentially, it creates a new database with a new DBIID and can also be used to convert R4 databases to R5 format. Since a new DBIID is assigned, a full backup is required immediately after for any logged databases. Copy-style compacting will be performed if the -c option is used on the command.
4.2 Backup strategy

Your backup and recovery strategy will mainly depend on the type of Lotus Domino environment that you have as we have discussed in the previous section and chapters. Other contributing factors are: Network traffic: This will influence performance as well as to help determine issues, such as how often to archive the transaction log and whether to use a threshold. Backup window: This tells you how much time is available for the backup operation. Although TDP for Domino does not require the Domino applications to be shutdown during backup, backing up databases still requires some processing on the Domino server. You will need to gauge
112
the impact of this in your environment while deciding when to run backups for each database, and whether to run full backups or simply logarchive operations. Acceptable restore times: This should help you determine how often to initiate a selective backup of your logged databases. As we have discussed, if you do not force a backup of logged databases, but instead rely on the incremental operation of backups, you run the risk of increasing your restore time to an unacceptable level. This is because of the number of transactions which will have to be applied from the log to bring the database back to its most recent point in time. These, and other factors should all be investigated in advance, documented, and used as part of your pilot and test implementation environment. The process of understanding these requirements and using them to develop a service level agreement and backup strategy is beyond the scope of this redbook, but a useful general approach will be found in Getting Started with Tivoli Storage Manager: Implementation Guide, SG24-5416. Table 5 shows some information which has to be collected by Lotus Domino users, and backup users/administrators for defining a backup strategy.
Table 5. Documenting your backup requirements
Lotus Domino Server Name Senegal/Almaden
List of databases to backup names.nsf log.nsf statrep.nsf all mail databases all application databases Organization critical databases
Type of backup selective
Schedule of backup 22:00 hrs, every Monday, Wednesday and Friday 06:00 hrs, Every day 03:00 hrs, Everyday 22:00 hrs, every Tuesday, Thursday, Saturday
Comments
Very Critical, High priority
incremental
Critical, medium priority Critical, medium priority Extremely Critical, Highest priority
incremental
selective
Next, you need strategies for your databases, depending on what, if any, style of transaction logging is used.
113
4.2.1 No transaction logging

If you dont have transaction logging enabled in your Lotus Domino environment, then you do not need any extra disk space to format logs to store changes to databases. All changes are written directly to the databases. In this case, you have to take a full backup every time, since there are no transaction logs to be backed up. The incremental backup operation will backup all non-logged databases that have been modified since the last backup occurred, providing they are not excluded from backup. We recommend a nightly incremental backup of these databases using TDP for Domino, because it also expires databases that have been deleted off the Lotus Domino server.
4.2.2 Circular logging

Circular logging will keep transaction log data on the Lotus Domino server and once the log wraps, the oldest log data will be overwritten. Therefore, when using circular logging, it may not be possible to apply updates to a restored database if the log has wrapped since the backup was taken. We recommend that you implement the following backup option: Run regular selective backups, for example, nightly. Perform occasional incremental backups (for example, weekly or bi-weekly) to inactivate backup copies of the databases that have been deleted from the Lotus Domino server. Each backup takes longer to perform, but the restore process is most efficient, because only the most recent (or other appropriate) full backups need to be restored. You cannot archive the transaction log if circular logging is used. Therefore, if you lose both the database and the recovery log, you will only be able to recover the database, at its state at the last backup.
4.2.3 Archive logging

Archive logging is the most flexible and recommended option. It will allow transaction log data to be archived to the TSM server. By archiving the transaction log file extents, you free up space allocated to these files so that they can be reused by the Lotus Domino logger. This method prevents the Lotus Domino server from halting. Here is an example for scheduling backups in an archive logging environment: 1. Perform weekly selective backups of all logged databases (for example, every Sunday).
114
This reduces the number of transaction log extents to be processed during a restore. Regular selective backups also saves you storage space on the TSM server, especially if you have a large Lotus Domino environment. 2. Archive the transaction log frequently each day. The frequency of the transaction log file archives depends on the size of your transaction log and the rate of changes to logged databases. You could start by archiving twice a day, then if you find you have a high rate of changes to logged databases, increase the frequency. You should run selective backups more frequently, if you generate a lot of database changes. This will reduce the number of transaction log extents you have to process in the event of a restore. In our example, 4.3.2, Defining the schedules on page 118, we will show an hourly archive of the transaction log extents without use of the THRESHOLD parameter. Alternatively, as described in 3.1.3.1, When to use archive log on page 70, you could archive the log extents throughout the day specifying a THRESHOLD parameter. This means the log extents are only archived if utilization is an issue. You would then schedule an archivelog operation without threshold once per day to force all log extents to be archived. Perform daily incremental backups. An incremental backup will only backup a logged database if the databases DBIID has changed. The incremental backup also expires databases that have been deleted from the Lotus Domino server. 3. Issue the Inactivatelogs command to allow non-essential transaction log files to expire. Run this command after each selective backup completes. As well as these four basic schedules, you need an additional schedule to perform a Tivoli Storage Manager backup/archive client incremental backup. This should normally run every night and will make sure all your non-Notes database data, such as initialization and configuration files, as well as any other operating system files, are also protected on the Tivoli Storage Manager server. If the Domino server was previously part of a Tivoli Storage Manager configuration, then this schedule will probably already exist. In this case, you will need to check what time it is set to start, and make sure that this coordinates with your new TDP for Domino schedules. If you have followed the scheduler setup which we used in this redbook, you could technically run this incremental backup concurrently with a TDP for Domino scheduled operation, since separate scheduler processes are used for each. However, for performance reasons and simplicity of operation, it is preferred to separate their operations completely so that they do not overlap. Experience and testing will allow you to decide on an appropriate timing for each.
115
4.3 Scheduling
We assume you have already configured appropriate scheduler services or processes in your environment, as described in 2.6, Scheduling TDP for Lotus Domino on page 45.
4.3.1 Sample backup scripts

TDP for Lotus Domino ships with sample scripts to perform the four basic operations as described in the previous section. These are stored in the application client installation directory and are called: domsel.smp - selective backup of Domino databases domarc.smp - archive transaction logs dominc.smp - incremental backup of Domino databases domina.smp - inactivate transaction logs You need to customize these files to suit your environment. You should copy them to another filename so that you always have access to the original unmodified version. For example, under Windows, you could rename these to use a .cmd extension, so they can be executed. In a UNIX environment you could also rename these to use a .cmd extension or simply remove the extension altogether. Also, check that the permission bits are set correctly for the required users. You then need to modify the scripts to meet your requirements. You might need to add or modify environment variable definitions, log output destinations and other parameters. Figure 40 is the domarc.cmd script for Windows NT, modified for use in our environment:
116
@ECHO OFF rem ================================================================== rem Sample Command File - domarc.smp rem rem Sample command file containing commands to do a scheduled archive rem of transaction logs to TSM storage. rem rem This file is meant to be executed by the TSM central scheduler rem in response to a defined schedule on the TSM server. rem rem Complete paths must be given for all file names and non-system rem commands. rem rem Copy this file to domarc.cmd and edit it to match your rem local environment. rem rem ================================================================== rem ================================================================== rem Replace "X:" with the drive where the Domino Application Client rem is installed. rem ================================================================== rem set dom_dir=C:\Program Files\Tivoli\TSM\domino cd /d c:\Program Files\Tivoli\TSM\domino rem rem rem rem rem rem echo date echo time ================================================================== The 2 lines below put a date and time stamp in a log file for you. Note: You can change "domarc.log" to whatever you prefer. ================================================================== Current date is: >> C:\Program Files\Tivoli\TSM\domino\domarc.log /t < NUL >> C:\Program Files\Tivoli\TSM\domino\domarc.log Current time is: >> C:\Program Files\Tivoli\TSM\domino\domarc.log /t < NUL >> C:\Program Files\Tivoli\TSM\domino\domarc.log
rem ================================================================== rem Now call the command line to do the archive of the logs: rem rem Note: You can change "domasch.log" to whatever you prefer. rem ================================================================== start /B C:\Program Files\Tivoli\TSM\domino\domdsmc archivelog /adsmoptfile=C:\Program Files\Tivoli\TSM\domino\dsm.opt /logfile=C:\Program Files\Tivoli\TSM\domino\domasch.log >> C:\Program Files\Tivoli\TSM\domino\domarc.log
Figure 40. Modified domarc.cmd script for Windows NT
Hint
We found that in some circumstances, depending on the version of Windows NT and TDP for Domino, it was necessary to change the line set dom_dir=C:\Program Files\Tivoli\TSM\domino to set dom_dir=C:\Progra~1\Tivoli\TSM\domino in the sample scripts provided. If we didnt do this, script execution would fail with the message ACD0104E Invalid option.
117
4.3.2 Defining the schedules

Next, you need to define schedules on the Tivoli Storage Manager server to execute your customized scripts at the required times and days. Here are some sample commands: Define a schedule to archive the transaction log extents every hour on the half hour.
tsm: PALANA1>define schedule DOMINO DOMARC \ cont> description="Domino: hourly archivelog" action=command \ cont> objects="C:\Program Files\tivoli\tsm\domino\domarc.cmd" \ cont> starttime=01:30 duration=15 durunit=minutes period=1 perunits=hours ANR2500I Schedule DOMARC defined in policy domain DOMINO.
Define a schedule to incrementally backup all the databases every morning at 2 a.m.
tsm: PALANA1>define schedule DOMINO DOMINC \ cont> description="Domino: daily incremental" action=command \ cont> objects="C:\Program Files\tivoli\tsm\domino\dominc.cmd" \ cont> starttime=02:00 ANR2500I Schedule DOMINC defined in policy domain DOMINO.
Define a schedule to selectively backup all the databases every Sunday at 8 p.m.
tsm: PALANA1>define schedule DOMINO DOMSEL \ cont> description="Domino: weekly selective" action=command \ cont> objects="C:\Program Files\tivoli\tsm\domino\domsel.cmd" \ cont> starttime=20:00 perunits=weeks dayofweek=sunday ANR2500I Schedule DOMSEL defined in policy domain DOMINO.
Define a schedule to inactivate the transaction log extents every Sunday at 10 p.m. Note that this schedule should execute after the weekly selective backups. You could experiment to find a reasonable time to start this schedule, or you could combine the two operations into a single command script to ensure sequential execution.
tsm: PALANA1>define schedule DOMINO DOMINA \ cont> description="Domino: weekly inactivate" action=command \ cont> objects="C:\Program Files\tivoli\tsm\domino\domina.cmd" \ cont> starttime=22:00 perunits=weeks dayofweek=sunday ANR2500I Schedule DOMINA defined in policy domain DOMINO.
118
Define a schedule (if it does not exist already) to run a regular backup-archive client incremental backup operation. This schedule will use the nodename associated with the backup-archive client, not the TDP for Domino nodename.
tsm: PALANA1>define schedule DOMINO FILE_INC \ cont> description="Domino server: nightly file incremental backup" action=incremental \ cont> starttime=05:00 ANR2500I Schedule FILE_INC defined in policy domain DOMINO.
You can query the schedules you have just defined to see related information as shown below:
tsm: PALANA1>query schedule DOMINO Domain * Schedule Name Action ------------ - ---------------- -----DOMINO DOMARC CMD DOMINO DOMINA CMD DOMINO DOMINC CMD DOMINO DOMSEL CMD DOMINO FILE_INC INC Start Date/Time Duration Period Day -------------------- -------- ------ --11/02/2000 01:30:00 15 M 1 H Any 11/02/2000 20:00:00 1 H 1 W Sun 11/02/2000 02:00:00 1 H 1 D Any 11/02/2000 20:00:00 1 H 1 W Sat 11/02/2000 05:00:00 1 H 1 D Any
4.3.3 Associating the schedules

Finally, dont forget to associate your TDP for Domino clients with the schedules so that they will execute. Use the define association command as shown below:
tsm: PALANA1>def assoc DOMINO DOMINA PALANA_TDP ANR2510I Node PALANA_TDP associated with schedule DOMINA in policy domain DOMINO.
4.4 Database and directory links

Both Domino administrators and IT Managers are responsible for putting databases into production and maintaining databases on the server. Database maintenance involves monitoring database activity and size, fixing corrupted databases, updating full-text indexes, and moving and replicating databases to other servers, when necessary.
119
Lotus Domino implements a logical view of the database location within a Domino system. The logical Domino database location is implemented within the physical file system. When Domino is installed, it creates a default data directory where all of the Domino executable files are located. The data directory is also the default database location. For example, if Domino is installed on the C: drive, the data directory is typically c:\lotus\domino\data. When Domino users open a database from the Domino workspace by selecting File from the action bar and then Database>Open, a list of databases residing on the local Domino (c:\lotus\domino\data) server is presented. The databases located in the Domino data directory are listed as well as the subdirectories below the data directory. The subdirectories may or may not contain databases. When a user opens a database, it appears that all Domino databases are in the directory or its subdirectories. The inability to place databases on other drives or file systems may appear to be a limitation of Domino. It is not, however. Domino provides a solution: directory or database links. Directory links point to directories containing databases on other drives or file systems. Database links are explicit pointers to a specific database at a fixed location. Figure 41 illustrates how directory and database links work. Users can also specify alternative locations without links if they specify the full database path and file name.
C Drive
Directory Link
notes\data\names.nsf
log.nsf viv.dir
D Drive
new\research\abc.nsf
new..nsf .............. .............. end.nsf
Database Link
sherbon.nsf
research\sherbon.nsf
Figure 41. Dominos logical directory structure: directory and database links
In our example, Domino is installed in c:\lotus\domino\data, the Domino data directory that contains several databases. There is also a file, viv.dir, which is
120
a Domino directory link that points to a different drive location, d:\new\research. When users open a database (File>Database>Open), they see a directory called viv containing the databases that physically reside in the d:\new\research directory, new.nsf, ..., end.nsf. The file viv.dir is a simple text file containing a drive and path pointer to the real directory location in our example, d:\new\research. Looking at Figure 41, we see that viv is a subdirectory. If in the Notes client, we double-click viv (or single-click viv and click the Open button), we see the database names that correspond to the new.nsf, ..., end.nsf databases. A database link is a link to a specific database that appears to users to actually reside in the data directory. In our example, there is a Domino database in d:\research called sherbon.nsf. In the Domino data directory, c:\lotus\domino\data, there is also a file called sherbon.nsf, but it is not a database; it is a text file containing the path to the database of the same name. Domino recognizes sherbon.nsf as a pointer to a database rather than as an actual database. To a user, sherbon.nsf would appear to reside in the Domino data directory, because it is listed with all of the other databases that actually do reside in the Domino data directory (see Figure 41). In summary, Domino has its own logical directory structure for databases. You can think of the default data directory as the virtual root point of the structure. Databases can reside in the default data directory or in subdirectories. You can create directory links to other file systems or drives. Directory links are similar to virtual mount points in a UNIX NFS file system. Alternatively, you can use database links to reference specific databases in other file systems. This concept is similar to that used in UNIX soft links. You can store databases in a directory outside of the Lotus Domino data directory to take advantage of disk space available on other server. Then you can create a link that is in the Lotus Domino data directory and points to that directory. For example, in our Lotus Domino environment, we created a directory link, FINANCE.DIR. Users see the directory link FINANCE.DIR as the subdirectory FINANCE, with a directory folder icon next to it. Users who do not have access to a linked directory can see the directory link, but cannot access the directory.
121
TDP for Lotus Domino recognizes the logical directory structure, but it imposes some limitations when it comes to the backup process and to include/exclude filter lists. When you run a backup of a directory that includes a directory link file, TDP for Domino does not interpret the directory link file as a pointer to another subdirectory. The backup operation will fail if you try to backup the directory link directly, as shown in Figure 42.
C:\win32app\IBM\ADSM\domclient>domdsmc sel finance.dir Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains vaild license data Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Restart Analysis: 100% 08/09/00 09:45:48 AM Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery)
0 0 0 0.00 Kb/Sec 0 0.00 Secs
ACD5115E No databases were found that match the file specification entered.
Figure 42. Failure if you try to back up the directory link directly
122
To successfully run backups of databases in the directory link directory, you need to run an additional command specifying the subdirectory, FINANCE. See Figure 43.
C:\win32app\IBM\ADSM\domclient>domdsmc sel finance\* Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains vaild license data Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Restart Analysis: 100% 08/09/00 09:51:10 AM Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery) Logging on to the Tivoli Storage Manager server, please wait... Backing up database finance\analysis.nsf, 1 of 2. Full: 0 Read: 393216 Written: 393216 Rate: 369.94 Kb/Sec Backup of finance\analysis.nsf completed successfully. Backing up database finance\ledger.nsf, 2 of 2. Full: 0 Read: 1064448 Written: 1064448 Rate: 963.39 Kb/Sec Backup of finance\ledger.nsf completed successfully.
2 2 0 656.90 Kb/Sec 1457664 2.17 Secs
Figure 43. Successful backup of databases in the directory link
123
Databases pointed to by a directory link, will be restored to their original locations. See Figure 44.
C:\win32app\IBM\ADSM\domino>domdsmc rest finance\* Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains vaild license data Starting Domino database restore... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Restoring database finance\analysis.nsf, 1 of 2, to c:\projects\finance\analysis.nsf.dad Full: 0 Read: 393216 Written: 393216 Rate: 772.64 Kb/Sec Restore of finance\analysis.nsf completed successfully. Restoring database finance\ledger.nsf, 2 of 2, to c:\projects\finance\ledger.nsf.dad Full: 0 Read: 1064448 Written: 1064448 Rate: 1907.34 Kb/Sec Restore of finance\ledger.nsf completed successfully.
2 2 2 0 1364.81 Kb/Sec 1457664 1.04 Secs
Figure 44. Databases pointed to by a directory link restored to original locations
You can store a single database outside the Lotus Domino data directory and create a database link to it from the Lotus Domino data directory. A database link appears in the Lotus Domino data directory as a database icon followed by the name of the linked database.
124
In our environment, we created a database link, FLAVIO.NSF, that points to a single database in C:\DBLINK\FLAVIO.NSF. The FLAVIO.NSF is a simple text file that has the path to the physical database. It contains only one line:
c:\dblink
TDP for Lotus Domino recognizes the physical databases behind the database link.
C:\win32app\IBM\ADSM\domclient>domdsmc sel flavio.nsf Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains vaild license data Starting Domino database backup... Initializing Domino connection... Querying Domino for a list of databases, please wait... Restart Analysis: 100% 08/09/00 11:37:39 AM Recovery Manager: Restart Recovery complete. (0/0 databases needed full/partial recovery) Logging on to the Tivoli Storage Manager server, please wait... Backing up database flavio.nsf, 1 of 1. Full: 0 Read: 1350144 Written: 1350144 Rate: 834.49 Kb/Sec Backup of flavio.nsf completed successfully.
1 1 0 821.50 Kb/Sec 1350144 1.61 Secs
When you restore a database pointed to by a database link, the physical database will be restored to the Lotus Domino data directory.
125
Important notes
Since databases pointed to by a database link are restored to the data directory, you will need to manually move these databases to their required location. Remember that database links are often used because of lack of space in the Lotus Domino data directory partition. So, be aware that if you restore a number of databases which are actually links, you might inadvertently fill up the data directory before the databases can be copied to their proper location. If this happens, you will need to break down the restore into smaller chunks, so that you do not use up all the available disk space. Both database and directory links must exist before using TDP for Lotus Domino to restore databases that would be affected by these links. TDP for Domino will re-create those links on a restore operation. If the links themselves (since directory links are just text files) have been deleted, for example, in a disaster recovery situation, you must first use the backup/archive client to restore the directory links. Only then can you attempt to restore the linked databases.
4.5 Shared mail

After you set up Notes mail, you can set up a shared mail database on each mail server. A shared mail database is a space saving feature that stores a single copy of mail messages that are addressed to multiple recipients. When multiple recipients whose mail files are on the same server receive a message, the shared mail database stores the actual message content, while each recipients mail file only stores the message header. Using a shared mail database is completely transparent to users. Users can delete, reply, change the view or folder, edit, save, resend, and perform all the same tasks on a mail message stored in a shared mail database as they would with the same message stored in their own mail files. Each user can edit, save, and resend the original message, without affecting how the message is presented to the other users. Using a shared mail database to store messages conserves disk space. To keep the shared mail database small, after all recipients have deleted a particular message from their mail files the Object Collect task, which runs by default, purges that message from the shared mail database. See Figure 45.
126
User's mail database

To: Essop Seedat/Almaden cc: Dudley Ward/Almaden Subject: Car Prices
User's mail database

To: Essop Seedat/Almaden c: Dudley Ward/Almaden Subject: Car Prices
Header information + content of document

-----------------------------------------------------------
This has been a very good quarter. I would like to thank you all, for your extra effort. Keep up the good work.
Shared mail database: shared.nsf

Figure 45. Link between users mail databases and shared mail databases
When you enable shared mail on the Lotus Domino server, two databases are created: SHARED.NSF MAILOBJ.NSF SHARED.NSF is a shared mail database which holds all the header information and the contents of each note. MAILOBJ.NSF is a directory link that points to the shared mail database. If you have archive logging enabled in your environment, than the shared mail databases will not be logged. Therefore, if you use shared mail, you should consider a frequent backup schedule for this database. If an active shared mail database is damaged beyond recovery and restored from backup, every message delivered since the last backup will be lost. You will have to run the Collect process to delete mailbox headers which correspond to unrecoverable messages. This will clean up the entries but will still not recover those messages.
127
We set up shared mail in our Lotus Domino environment, with archive logging enabled. If you have a big shared mail database, only run incremental backups of SHARED.NSF, because MAILOBJ.NSF is only a directory link, and by including it in the backup process, it will automatically back up SHARED.NSF again. This duplication of data, takes up space on the Tivoli Storage Manager server. Shared mail can be restored in numerous ways.
Scenario 1 If your shared mail database, SHARED.NSF, is corrupt or damaged but still exists, then:
Restore SHARED.NSF to a new location. For example:
C:\win32app\IBM\ADSM\domino>domdsmc rest shared.nsf /into=c:\dblink\shared.nsf / activate=yes Tivoli Storage Manager Tivoi Data Protection for Lotus Domino - Version 1, Release 1, Level 0.0 (C) Copyright IBM Corporation 1999. All rights reserved. License file exists and contains valid license data. Starting Domino database restore... Initializing Domino connection... Logging on to the Tivoli Storage Manager server, please wait... Querying Tivoli Storage Manager server for a list of database backups, please wa it...
Restoring database shared.nsf, 1 of 1, to c:\dblink\shared.nsf The ID file being used is: C:\Lotus\Domino\Senegal\senegal.id Enter password (press the Esc key to abort):
Restore of shared.nsf completed successfully.
1 1 1 1 517.17 Kb/Sec 262144 0.50 Secs
On the Lotus Domino server console, use the Push command to push changes from the restored shared mail database to the current shared mail database. For example:
Push Senegal c:\dblink\shared.nsf
128
Scenario 2 This scenario assumes that an administrator accidentally deleted the shared mail database, SHARED.NSF.
Shut down the Lotus Domino server. Restore SHARED.NSF to its original location. Start the Lotus Domino server.
Scenario 3 This scenario assumes that the database link, MAILOBJ.NSF, is deleted.
Restart the Lotus Domino server. The Lotus Domino server startup process will automatically create a new database link, called MAILOBJ.NSF.
Scenario 4 This scenario assumes that you have lost both SHARED.NSF and MAILOBJ.NSF
Shut down the Lotus Domino server. Restore SHARED.NSF from the TSM server. Start the Lotus Domino server. A new database link, MAILOBJ.NSF, will be created. A new shared mail database, SHARED1.NSF, will be created. The new shared mail database will be used for all the new mail transactions. Users can still access their old mail documents, that were linked to SHARED.NSF.
4.6 Media recovery

Either the command line or GUI of TDP for Lotus Domino can be used to restore databases. In this section, we discuss some more detailed recovery scenarios, particularly from media failure. When you have a media or disk failure, you have to replace the disk, format it and restore all the data which was on it. This means everything needs to be created from scratch. Depending on the failure and on whether archive transaction logging is in effect, you may be able to roll forward the database after restore to its more recent point. If this is not possible, then the database will be restored as at the time of its last full backup, and most likely, some data will be lost.
129
4.6.1 Restore database to its original location

Restoring an individual database can be done from either the command line or the GUI of TDP for Lotus Domino. We already covered this topic in detail in 3.2, Database recovery on page 72, however, we repeat it here for convenience. In Figure 46, you can see the procedure that can be followed when a user wants to restore a specific database.
I accidently deleted my database!
S0000001.txn
User
TSM Server
S0000002.txn
Restoring Deleted Database
S0000003.txn
Transaction Logging
Notes Workstation
Notes Server Notes Administrator
Figure 46. Recovery of deleted database
Here are the steps to restore the database using the TDP for Domino GUI: 1. Select the Restore tab. 2. Dont forget to specify to view active and inactive files if you want to see all the database backup versions, not just the active ones.
130
3. Select the database that you want to restore. They will be listed in the left hand window underneath Backup from Server Name. 4. If the database is not logged, you can select to Activate immediately. 5. Click the Restore button. 6. If you did not select Activate you will now need to Activate the database separately. See Figure 47.
Figure 47. Restore a database
After these steps, a dialog box informs you of a successful restore.
4.6.2 Database to new location

You can also restore a database to another location using the following steps: 1. Select the Restore tab. 2. Dont forget to specify to view active and inactive files if you want to see all the database backup versions, not just the active ones. 3. Select the Database that you want to Restore. They will be listed in the left-hand window underneath Backup from Server Name. 4. Enter the new database path and filename in the Restore Into window. 5. If the database is not logged, you can select to Activate immediately. 6. Click the Restore button.
131
7. If you did not select to Activate, you will now need to separately Activate the database. In Figure 48, you can see where you can put the path to restore a database into a different location.
Figure 48. Restore a database in a different location
You can restore in a different location with a different name as well as to the same database name in a different location. If you restore into a different location using this process, you can then select and copy individually selected documents from the newly restored database back into the original. If this was the only reason to restore the database, you could then delete it, leaving the original with the required documents restored. Dont forget that your ability to restore inactive or older backup versions depends on the settings for number of versions to keep in your management class and how often the database is backed up. For example, suppose your management class specifies to keep three versions of database backups and you are performing a selective backup every night starting from Monday. By Thursday morning, we have three backup versions, from Monday, Tuesday and Wednesday, respectively. After Thursday nights backup, the oldest backup version will be deleted, in this case from Monday. You will no longer be able to restore the database back,
132
because at that date, this version is no longer available on the Tivoli Storage Manager server. Figure 49 shows a typical situation, where a user has lost important documents in his database. In this case, the administrator has to restore the latest full backup and then apply transactions from the archived log extents to roll forward to the most recent state.
I lost my project.nsf database!
Mon 08/09
Tue 08/10
Wed 08/11
Thu 08/12
Database not available on the server after the 3rd version
Management class: VEREXISTS=3
Figure 49. Expiry of backup versions
Figure 50 shows a typical situation, where a user has accidentally deleted an important document in an archive logged database. Luckily for him, the document was created on the previous day and was included in the backup that night. The log is also being regularly archived. In this case, the administrator has to restore the last full backup and then apply the archived transactions to roll forward to the most recent state.
133
S0000001.txn S0000002.txn
I lost one important document!
TSM Server
S0000003.txn
Transaction Logs
Weekly Full Backup
Database Loss
Sun 08/08
Mon 08/09
Tue 08/10
Wed 08/11
Thu ... 08/12
Daily Incremental Backup using TDP for Lotus Domino
Figure 50. Restore and apply transaction logs
4.7 Server recovery and migration

In this section, we present two scenarios. The first describes how to migrate the Domino server to a replacement system. The second shows a procedure for recovering from a complete media failure on the same system, where both databases and the recovery log are lost.
4.7.1 Migrating to a new Domino server

In this section, we describe the steps to migrate one server with Release 5 to another machine with the same release. There are a number of variables which could affect this procedure, so we recommend that you test it first in
134
your environment to take account of any differences and make necessary modifications. In our environment, we have two machines, charcot, the original server, and ununbium, the new server. Here are the steps to follow to re-create charcots environment and data on ununbium. 1. Take a full backup from the original system, charcot, except for log.nsf. Archive the transaction log. 2. On ununbium, remove any existing Domino server and client, and install the Domino Server code at the same level as on charcot.
Note
Be sure that you are installing in the same directory structure used by charcot. If you have to install in another directory, you will need to change this setting in the notes.ini file. 3. On charcot, use the backup archive client to make sure these files are backed up: \logir\nlogctrl.lfh \logdir\s000...txn \domino\notes.ini \data\desktop5.dsk \data\jobsched.njf \data\pid.nbf \data\server.id If you have a cluster, also backup this file: \data\cluster.ncf If you have a domino web, also backup this file too: \data\domino.cnf. 4. Install the Tivoli Storage Manager backup client on ununbium. 5. Use the backup archive to restore all the files that you backed up in step 3. 6. Install the TDP for Lotus Domino client on ununbium. 7. Use TDP for Domino to restore (but not activate) all the Domino databases on ununbium. 8. Use TDP for Domino to activate the databases and therefore apply the logged transactions on ununbium. 9. Install a Domino Administrator client on ununbium.
135
10.Start the Domino Administrator client on ununbium but do not connect to the server. 11.Use the administrator client on ununbium to update the names.nsf, in local browse mode, by changing the host name in Server Basics and Server Ports. Update the TCP/IP address to point to ununbium in the Connection Document. 12.From ununbium, use the push command to replicate the names.nsf 13.Use the administrator client on ununbium to update Location Preferences for the Domino Server. 14.Start the server on ununbium. 15.Use the administrator client on ununbium to connect to the server on ununbium.
4.7.2 Disaster recovery

In this scenario, we assume that we have either completely lost or massively corrupted our Lotus Domino Server due to a complete disaster or large scale media failure. We have to re-create both the databases and the transaction log. 1. If corrupted server code exists, uninstall the Domino server, if possible. Otherwise, if starting from a bare metal server, re-install and configure the operating system, including TCP/IP. 2. Re-install and configure the Domino server. 3. Install and configure the Domino Administrator client. 4. Using the Domino Administrator, turn on archival logging. To restore the address book, you must turn archival logging on at this step. You must take the server down, then up again, to activate archival logging. Once archival logging is activated, you must take the server down again before performing the next step. 5. Install and configure TDP for Lotus Domino. You will use the same nodename as for the destroyed server. 6. Restore the databases you want to recover using TDP for Lotus Domino. Do not activate these databases. 7. Use the Restorelogarchive command to restore the transaction log extent to be used in the disaster recovery procedure. Normally, this would be the last transaction log extent archived prior to the data loss. 8. Close the TDP for Lotus Domino GUI.
136
9. Delete the contents of the Domino transaction log directory except for the transaction log extent you restored in step 7. 10.Modify the notes.ini file on the Domino server with this setting:
TRANSLOG_Recreate_Logctrl=1
11.At a DOS prompt, run nfixup on a database you are not recovering. The notes.ini file will automatically modify to this setting:
TRANSLOG_Recreate_Logctrl=0
12.Bring up the Domino server in the Start menu. 13.Use TDP for Lotus Domino to activate the databases you are recovering. Apply logged transactions as necessary. 14.Replicate with all servers that contain copies of the databases. 15.Use TDP for Lotus Domino to perform full backups of all databases. The DBIIDs of the recovered databases have not changed. As a result, these backups must be performed as selective backups, not incremental backups. 16.Use TDP for Lotus Domino to archive the transaction log. The transaction log used in the recovery procedure will be modified and available for archiving. This transaction log will also have the ID of the current logger.
137
138
Appendix A. Creating a recycling bin in Domino R5

This appendix describes how to use Domino R5 features to create the equivalent of a Windows Recycle Bin facility for the Notes client. Normally, when a user deletes a document, it will be flagged to be removed when the database is refreshed. However, here we describe how to setup a recycling bin function for critical databases so that user-deleted documents will not completely disappear. Instead, they will move to the Recycle Bin, which is actually a special view to hold deleted documents. The user is then able to restore documents from this view, back to their original location within a specified time limit. This capability should reduce if not eliminate the requirement to perform a single document restore for users. You will need Designer access on a database to set up this feature and probably the assistance of your Domino administrator since we assume basic familiarity with Notes database design. 1. For each database where the undelete function is required, turn on the Allow soft deletions database property in the Advanced tab of the Database Properties popup. This places a Soft Delete status flag on any document that a user deletes. Such a document appears to be deleted from the user interface, that is, it is removed from all the views; however, it will be available for restoring if required. The $Undelete Expire Time controls how long a deleted document is available for undeleting. If the document is not undeleted before the $Undelete Expire Time expires, the document is permanently deleted from the database. The window in Figure 51 shows these database properties set, so that deleted documents will be kept for two days.
139
Figure 51. Database properties showing undelete function
2. Now, you need to create the view to display the deleted documents. Select Create > View, and the screen in Figure 52 is displayed. We call our new view Recycling Bin, set the view type to Shared, contains deleted documents and click OK .
140
Figure 52. Creating a view to display deleted documents
3. After the view is created, you need to modify its design to include a button to undelete a document and restore it back to its original location. The screen is shown in Figure 53. Open the newly created Recycling Bin view in design mode (Actions > View Options > Design) . To add a button, select Create > Action and give the action a name (for example, Undelete Document). We will want the action to appear as a button on the view, so be sure that the field Action appears in button menu is selected. You can also select an appropriate icon for your action button in the Graphic option, or design your own.
Creating a recycling bin in Domino R5
141
Figure 53. Create an Undelete document action
4. Next, create the action code as shown in Figure 54. Expand the Undelete Document action in the Objects list and click the Click property. This will open the Formula window. Select to run Simple action(s), choose the Add Action button, and select @Function Formula for the Action. Type @UndeleteDocument in the Formula window and click OK .
142
Figure 54. Creating the Undelete button action code
5. Now, when you display the Recycling Bin, as in Figure 55, you will see your newly created button. We had previously deleted a document from the database being worked on, which removed it from the normal database view. It shows up now only in the Recycling Bin view. To restore the document, (within 48 hours of deletion as per the database properties which we set previously), display the Recycling Bin, click on the required document and select the UndeleteDocument button.
Creating a recycling bin in Domino R5
143
Figure 55. Undeleting a deleted document in the Recycling Bin
6. Finally, display the original database view as in Figure 56. The document which we undeleted in the previous step is now back in its original location.
Figure 56. Restoration of a deleted document
144
Appendix B. Special notices

This publication is intended to help customers, consultants, IBM and Tivoli Business Partners and staff to back up Lotus Domino R5 using Tivoli Storage Management. The information in this publication is not intended as the specification of any programming interfaces that are provided by Tivoli Storage Management. See the PUBLICATIONS section of the IBM Programming Announcement for Tivoli Storage Management for more information about what publications are considered to be product documentation. References in this publication to IBM products, programs or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent program that does not infringe any of IBM's intellectual property rights may be used instead of the IBM product, program or service. Information in this book was developed in conjunction with use of the equipment specified, and is limited in application to those specific hardware and software products and levels. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact IBM Corporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The information contained in this document has not been submitted to any formal IBM test and is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. While each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee
145
that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. Any pointers in this publication to external Web sites are provided for convenience only and do not in any manner serve as an endorsement of these Web sites. The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries:
IBM Netfinity OS/390 S/390 System/390 SP2 Domino Redbooks Redbooks Logo OS/2 RS/6000 SP Lotus Notes Notes
The following terms are trademarks of other companies: Tivoli, Manage. Anything. Anywhere., The Power To Manage., Anything. Anywhere., TME, NetView, Cross-Site, Tivoli Ready, Tivoli Certified, Planet Tivoli, and Tivoli Enterprise are trademarks or registered trademarks of Tivoli Systems Inc., an IBM company, in the United States, other countries, or both. In Denmark, Tivoli is a trademark licensed from Kjbenhavns Sommer - Tivoli A/S. C-bus is a trademark of Corollary, Inc. in the United States and/or other countries. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States and/or other countries. PC Direct is a trademark of Ziff Communications Company in the United States and/or other countries and is used by IBM Corporation under license. ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States and/or other countries.
146
UNIX is a registered trademark in the United States and/or other countries licensed exclusively through X/Open Company Limited. SET and the SET logo are trademarks owned by SET Secure Electronic Transaction LLC. Other company, product, and service names may be trademarks or service marks of others.
Special notices
147
148
Appendix C. Related publications

The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook.
C.1 IBM Redbooks

For information on ordering these ITSO publications see How to get IBM Redbooks on page 153.
Book Title General Topics Getting Started with Tivoli Storage Manager: Implementation Guide Tivoli Storage Manager Version 3.7: Technical Guide Tivoli Storage Management Concepts Tivoli Storage Manager Version 3.7.3 & 4.1: Technical Guide ADSM Client Disaster Recovery: Bare Metal Restore Specific Server Books A Practical Guide to Implementing Tivoli Storage Manager on AS/400 Windows NT Backup and Recovery with ADSM ADSM Server-to-Server Implementation and Operation ADSM Server for Windows NT Configuration and Recovery Examples AIX Tape Management ADSM/6000 on 9076 SP2 Tivoli Storage Manager with Other Products A Practical Guide to Network Storage Manager Using ADSM to Back Up Databases Using Tivoli Storage Manager to Back Up Lotus Notes Tivoli Storage Management Reporting Managing Storage Management: Tivoli Enterprise Integration with Tivoli Storage Management Lotus Domino Books Lotus Domino R5 for Sun Solaris Lotus Notes and Domino Take Center Stage: Upgrading from R4 to R5 Lotus Domino R5 for IBM RS/6000
Publication Number SG24-5416 SG24-5477 SG24-4877 SG24-6110 SG24-4880 SG24-5472 SG24-2231 SG24-5244 SG24-4878 SG24-4705 GG24-4499 SG24-2242 SG24-4335 SG24-4534 SG24-6109 SG24-6117
SG24-5969 SG24-5630 SG24-5138
149
C.2 IBM Redbooks collections

Redbooks are also available on the following CD-ROMs. Click the CD-ROMs button at ibm.com/redbooks for information about all the CD-ROMs offered, updates and formats.
CD-ROM Title Collection Kit Number IBM System/390 Redbooks Collection SK2T-2177 IBM Networking Redbooks Collection SK2T-6022 IBM Transaction Processing and Data Management Redbooks CollectionSK2T-8038 IBM Lotus Redbooks Collection SK2T-8039 Tivoli Redbooks Collection SK2T-8044 IBM AS/400 Redbooks Collection SK2T-2849 IBM Netfinity Hardware and Software Redbooks Collection SK2T-8046 IBM RS/6000 Redbooks Collection SK2T-8043 IBM Application Development Redbooks Collection SK2T-8037 IBM Enterprise Storage and Systems Management Solutions SK3T-3694
C.3 Tivoli Storage Management publications
Book Title Tivoli Storage Manager for AIX Quick Start Tivoli Storage Manager for AIX Administrators Guide Tivoli Storage Manager for AIX Administrators Reference Tivoli Storage Manager for HP-UX Quick Start Tivoli Storage Manager for HP-UX Administrators Guide Tivoli Storage Manager for HP-UX Administrators Reference Tivoli Storage Manager for Sun Solaris Quick Start Tivoli Storage Manager for Sun Solaris Administrators Guide Tivoli Storage Manager for Sun Solaris Administrators Reference Tivoli Storage Manager for MVS and OS/390 Quick Start Tivoli Storage Manager for MVS and OS/390 Administrators Guide Tivoli Storage Manager for MVS and OS/390 Administrators Reference Tivoli Storage Manager for Windows NT Quick Start Tivoli Storage Manager for Windows NT Administrators Guide Tivoli Storage Manager for Windows NT Administrators Reference Tivoli Storage Manager Messages Tivoli Storage Manager for AS/400 Quick Start
Publication Number GC35-0402 GC35-0403 GC35-0404 GC35-0412 GC35-0413 GC35-0414 GC35-0406 GC35-0407 GC35-0408 GC35-0415 GC35-0377 GC35-0417 GC35-0409 GC35-0410 GC35-0411 GC35-0405 GC35-0317
150
Book Title Tivoli Storage Manager for AS/400 Administrators Guide Tivoli Storage Manager for AS/400 Administrators Reference Tivoli Storage Manager for VM Quick Start Tivoli Storage Manager for VM Administrators Guide Tivoli Storage Manager for VM Administrators Reference Tivoli Storage Manager for VM Messages Tivoli Storage Manager Using the Backup-Archive Client for UNIX Tivoli Storage Manager Using the Backup-Archive Client for Windows Tivoli Storage Manager Using the Backup-Archive Client for NetWare Tivoli Storage Manager Installing the Clients Tivoli Storage Manager Using the Application Programming Interface Tivoli Storage ManagerTrace Facility Guide Tivoli Data Protection for Lotus Domino for UNIX Installation and Users Guide Tivoli Data Protection for Lotus Domino for Windows NT Installation and Users Guide
Publication Number GC35-0315 GC35-0316 GC35-0351 GC35-0352 GC35-0353 GC35-0271 SH26-4122 SH26-4117 SH26-4116 SH26-4119 SH26-4123 SH26-4121 SH26-4088 GC26-7320
C.4 Referenced Web sites

These Web sites are also relevant as further information sources: http://ibm.com/redbooks IBM ITSO home page http://support.lotus.com/ Lotus Support home page http://www.tivoli.com/products/index/storage_mgr/index.html Tivoli Storage Manager home page http://www.tivoli.com/support/index/storage_mgt/adsm/pfguide/
tgv31mst.htm
Performance Tuning Guide for Tivoli Storage Manager
Related publications
151
152
How to get IBM Redbooks

This section explains how both customers and IBM employees can find out about IBM Redbooks, redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided. Redbooks Web Site ibm.com/redbooks Search for, view, download, or order hardcopy/CD-ROM redbooks from the redbooks Web site. Also read redpieces and download additional materials (code samples or diskette/CD-ROM images) from this redbooks site. Redpieces are Redbooks in progress; not all Redbooks become Redpieces and sometimes just a few chapters will be published this way. The intent is to get the information out much quicker than the formal publishing process allows. E-mail Orders Send orders by e-mail including information from the IBM Redbooks fax order form to: In United States Outside North America Telephone Orders United States (toll free) Canada (toll free) Outside North America 1-800-879-2755 1-800-IBM-4YOU Country coordinator phone number is in the How to Order section at this site: http://www.elink.ibmlink.ibm.com/pbl/pbl e-mail address pubscan@us.ibm.com Contact information is in the How to Order section at this site: http://www.elink.ibmlink.ibm.com/pbl/pbl
Fax Orders United States (toll free) Canada Outside North America 1-800-445-9269 1-403-267-4455 Fax phone number is in the How to Order section at this site: http://www.elink.ibmlink.ibm.com/pbl/pbl
This information was current at the time of publication, but is continually subject to change. The latest information may be found at the Redbooks Web site. IBM Intranet for Employees IBM employees may register for information on workshops, residencies, and Redbooks by accessing the IBM Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO Mailing List button. Look in the Materials repository for workshops, presentations, papers, and Web pages developed and written by the ITSO technical professionals; click the Additional Materials button. Employees may access MyNews at http://w3.ibm.com/ for redbook, residency, and workshop announcements.
153
IBM Redbook fax order form

Please send me the following: Title Order Number Quantity
First name Company Address City Telephone number Invoice to customer number Credit card number
Last name
Postal code Telefax number
Country VAT number
Credit card expiration date
Card issued to
Signature
We accept American Express, Diners, Eurocard, Master Card, and Visa. Payment by credit card not available in all countries. Signature mandatory for credit card payment.
154
Index A
ADSMConnect agent for Lotus Notes migrating to TDP for Domino 30 and the DBIID 111 API comparison of R4 and R5 17 Tivoli Storage Manager 20 archive logging 110 archive transaction logging 15 domdsm.log 86 domdsmc 84, 101 Domino Administrator 6 Domino cluster 59 Domino Designer 2, 7 Domino recycling bin 139 DRM 21 dsierror.log 86 dsm.opt 35 dsm.sys 35 dsmerror.log 86 dsmsched.log 86
B
backing up logged databases 114 backup scripts 116
E
editing preferences 101
C
CHANGEADSMPWD command 85 circular logging 109 circular transaction logging 15 clustered Domino servers 59 compaction 16, 111 CORBA 1
F
filespaces 32
G
GUI preference editor 101
D
database activation after restore 76 backup policy 19 backup versions 132 incremental backup after updating 19 maintenance needs 119 point-in-time restore 74 replication 19 restore to a different Domino server 99 restoring and recovering 72 simultaneous update on different servers 25 Tivoli Storage Manager backup and restore 22 database instance identifier 16, 111 database links 120 DBIID 16, 64, 111 Directory Catalog 2 disaster recovery 136 disk writes and transactions 14 document level backup 17 document level restore 75, 139 domdsm.cfg 38
H
Headlines 3 hub and spoke concept 25
I
ID 79 IMAP4 1 INACTIVATELOGS command 78 include/exclude list TDP for Domino 36 Tivoli Storage Manager client 36 incremental backup Domino databases 63 ISP 3
L
LDAP 1, 2 logged databases backing up 114 logger ID 79 Lotus Domino 1, 75 and Tivoli Storage Manager client 22
155
backing up non-database files 28 backup API 17 database activation 76 database links 120, 121 directory links 121 disaster recovery 136 inactivating transaction logs 78 introduction 1 logical directory structure 121 migrating from R4 to R5 30 migrating to a new server 134 partitioned servers 25, 51 platforms 5 replication 19 scheduler 50 shared mail 126 Tivoli Storage Manager backup 21 transaction logging 13 Lotus Notes R5 3 Benefits 4 UI features 10
option files Tivoli Storage Manager client 35
P
partitioned servers NT 51 UNIX 52 partitioning Lotus Domino servers 51 PASSWORDACCESS option 45 passwords 44, 85 platforms 5 point-in-time restore 74 POP3 1 preferences file 84 editing 101
Q
QUERY ADSMSERVER command 81 QUERY DBBACKUP command 81 QUERY DOMINO command 82 QUERY LOGARCHIVE command 82 QUERY PENDINGDBS command 83 QUERY PREFERENCES command 83
M
message logging 85 TDP for Domino 85 migrating to a new Domino server 134 MIME 2
R
R4 and R4 API comparison 17 recommended policies 31 recycling bin 139 replication 19 based on hub and spoke concept 25 error duplication 19 simultaneous update on different servers 25 RESTORELOGARCHIVE command 79
N
NNTP 1 Notes default data directory 120 storage management 19 Notes Client 8 Notes R4 document level backup 17 Notes R5 client 3 Notes server hub and spoke concept 25 hub and spoke replication 25 putting Tivoli Storage Manager clients on 22 Tivoli Storage Manager backup 21 Notes workstation Tivoli Storage Manager backup 21
S
sample backup scripts 116 schedule associations 119 schedule definitions 118 scheduler automatic startup on AIX 50 installing second service 46 output messages 86 scheduling 45 scheduling TDP for Domino 116 selective backup
O
ODS 2
156
Domino databases 67 server event logging 87 shared mail 126 SMTP 2
T
TDP application clients 21 TDP for Domino 126 archive transaction logs 69 automation 45 changing client password 85 client password 44 clustered servers 59 command-line interface 24 database and log recovery 136 database compaction 111 database links 120 database recovery 72 GUI 24, 89 incremental backup 63 installation 28 integration with TEC 88 logging messages to the server 87 NT option file 39 partitioned servers 51, 52 platforms 22 preferences file 38, 84 queries 80 restoring a database 72 restoring archive logs 79 sample backup scripts 116 scheduling 116 selective backup 67 setup script 44 silent installation 29 UNIX environment variables 41 UNIX option files 40 TEC (Tivoli Enterprise Console) 88 Tivoli Data Protection for applications 21 Tivoli Data Protection for Lotus Domino 22 Tivoli Disaster Recovery Manager 21 Tivoli Space Manager 21 Tivoli Storage Management 19 Tivoli Storage Manager 31 administrator 20 API 20 backup/archive client 21, 34 database backup and restore 22
DRM 21 filespaces 32 HSM 21 management class 132 running TDP and backup/archive client 23 scheduler client 45 server 20 server event logging 87 Tivoli Storage Manager backup/archive client 20 transaction log 79 restoring individual logs 79 transaction logging 13 and DBIID 16 archive 15, 110 benefits 14 circular 15, 109 modes 109 transaction logs archiving 69 inactivating 78
U
undeleting documents 139 Universal In-Box 5 User interface 10
V
version control 132
X.509 3, 9
157
158
IBM Redbooks review

Your feedback is valued by the Redbook authors. In particular we are interested in situations where a Redbook "made the difference" in a task or problem you encountered. Using one of the following methods, please review the Redbook, addressing value, subject matter, structure, depth and quality as appropriate. Use the online Contact us review redbook form found at ibm.com/redbooks Fax this form to: USA International Access Code + 1 914 432 8264 Send your comments in an Internet note to redbook@us.ibm.com
Document Number Redbook Title Review
SG24-5247-00 Backing Up Lotus Domino R5 Using Tivoli Storage Management
What other subjects would you like to see IBM Redbooks address?
Please rate your overall satisfaction: Please identify yourself as belonging to one of the following groups: Your email address: The data you provide here may be used to provide you with information from IBM or our business partners about our products, services or activities. Questions about IBMs privacy policy?
O Very Good
O Good
O Average
O Poor O Solution Developer
O Customer O Business Partner O IBM, Lotus or Tivoli Employee O None of the above
O Please do not use the information collected here for future marketing or promotional contacts or other communications beyond the scope of this transaction.
The following link explains how we protect your personal information. ibm.com/privacy/yourprivacy/
159
(0.2spine) 0.17<->0.473 90<->249 pages

Trouble-free storage management for R5 databases Backup, restore, and disaster recovery scenarios Procedures for Windows and UNIX platforms
Tivoli Storage Management is a suite of products from Tivoli which encompasses an enterprise-wide network storage management solution. Together, these products provide data protection, including backup and restore, for over thirty major operating systems as well as for many of the most popular databases and applications. Lotus Domino R5 is one of these applications - an industry-leading product for messaging and collaborative computing. Tivoli Storage Manager server and Tivoli Data Protection for Lotus Domino together provide online backup and restore of Lotus Domino R5 databases. This IBM Redbook addresses backup and recovery of Lotus Domino R5 databases on Windows NT, Windows 2000, and UNIX platforms. This redbook provides an overview of Tivoli Storage Manager and Lotus Domino, details on how to install and configure Tivoli Data Protection for Lotus Domino R5 on Windows and UNIX, and operational procedures for backup and restore, as well as various scenarios for backup and restore.This book gives a broad understanding of the new architecture and features of Lotus Domino R5 as compared to R4, especially as they impact backup and recovery issues. Many examples and screenshots are included, to provide practical step-by-step instructions on setting up and maintaining this environment.
INTERNATIONAL TECHNICAL SUPPORT ORGANIZATION
BUILDING TECHNICAL INFORMATION BASED ON PRACTICAL EXPERIENCE IBM Redbooks are developed by the IBM International Technical Support Organization. Experts from IBM, Customers and Partners from around the world create timely technical information based on realistic scenarios. Specific recommendations are provided to help you implement IT solutions more effectively in your environment.
For more information: ibm.com/redbooks

SG24-5247-00 ISBN 0738417319

Backing Up Lotus Domino R5 Using Tivoli Storage Management Sg245247

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Backing Up Lotus Domino R5 Using Tivoli Storage Management Sg245247

Загружено:

Авторское право:

Доступные форматы

Backing Up Lotus Domino R5 Using Tivoli Storage Management

Copyright IBM Corp. 2000