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.1 Introducing Lotus Domino and Lotus Notes R5 . . . . . . . . . . . . .. . . . . .1
1.1.1 What is Lotus Domino R5? . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .1
1.1.2 What is Lotus Notes R5? . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .3
1.1.3 Benefits of R5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .4
1.1.4 Components and platforms . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .5
1.1.5 User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .6
1.1.6 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 11
1.1.7 Notes data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 12
1.1.8 Transaction logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 13
1.1.9 Backup API of R4 and R5 . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 17
1.1.10 Storage management of Notes . . . . . . . . . . . . . . . . . . . .. . . . . 19
1.2 Introducing Tivoli Storage Management . . . . . . . . . . . . . . . . . .. . . . . 19
1.2.1 Tivoli Storage Manager backup/archive client. . . . . . . . . .. . . . . 21
1.2.2 Tivoli Data Protection for Lotus Domino . . . . . . . . . . . . . .. . . . . 22

Chapter 2. Configuring storage management for Lotus Domino. . . . . 25
2.1 Project test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.2 Installation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.1 What to back up? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.2 Where to install?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.3 Silent installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.2.4 Migrating from Lotus Domino R4 . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3 Setting up Tivoli Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3.1 Tivoli Storage Manager server . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3.2 Tivoli Storage Manager backup-archive client. . . . . . . . . . . . . . . 34
2.4 Configuring TDP for Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
2.4.1 Include-exclude lists —TDP for Lotus Domino . . . . . . . . . . . . . . 36
2.4.2 Preferences file — TDP for Lotus Domino . . . . . . . . . . . . . . . . . 38
2.4.3 TDP for Domino on Windows NT option file . . . . . . . . . . . . . . . . 38
2.4.4 TDP for Domino on UNIX option files . . . . . . . . . . . . . . . . . . . . . 40
2.5 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.6 Scheduling TDP for Lotus Domino . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

© Copyright IBM Corp. 2000 iii

2.6.1 Tivoli Storage Manager scheduler . . . . . . . . . . . . . . . . . . . . . . . 45
2.6.2 Lotus Domino scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
2.7 Partitioned Notes servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.7.1 Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
2.7.2 UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.8 Clustered Domino servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 3. Operating TDP for Lotus Domino . . . . . . . . . . . . . . .. . . . . 63
3.1 Database backup and log archive. . . . . . . . . . . . . . . . . . . . . . .. . . . . 63
3.1.1 Incremental backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 63
3.1.2 Selective backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 67
3.1.3 Archive log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 69
3.2 Database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 72
3.2.1 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 73
3.2.2 Activation of database . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 76
3.3 Inactivation of archive logs . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 78
3.4 Restoring individual archive logs . . . . . . . . . . . . . . . . . . . . . . .. . . . . 79
3.5 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 80
3.5.1 Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 80
3.5.2 Changing the preferences file . . . . . . . . . . . . . . . . . . . . . .. . . . . 84
3.5.3 Changing the Tivoli Storage Manager password . . . . . . . .. . . . . 85
3.5.4 TDP for Domino message logging . . . . . . . . . . . . . . . . . .. . . . . 85
3.6 Graphical user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 89
3.6.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 91
3.6.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 93
3.6.3 Transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . 96
3.7 Restoring logged databases to an alternative Domino server . .. . . . . 99
3.8 Miscellaneous GUI functions . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 101
3.8.1 Application client settings . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 101
3.8.2 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 103
3.8.3 Other information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . 104
3.9 TDP for Lotus Domino performance . . . . . . . . . . . . . . . . . . . . .. . . . 105

Chapter 4. Backup strategy and recovery scenarios . . .. . . . . .. . . . 109
4.1 Domino considerations and backup . . . . . . . . . . . . . . .. . . . . .. . . . 109
4.1.1 Transaction logging modes. . . . . . . . . . . . . . . . . .. . . . . .. . . . 109
4.1.2 Changing the database instance identifier . . . . . .. . . . . .. . . . 111
4.1.3 Database compaction and the DBIID . . . . . . . . . .. . . . . .. . . . 111
4.2 Backup strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 112
4.2.1 No transaction logging . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 114
4.2.2 Circular logging . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 114
4.2.3 Archive logging . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 114
4.3 Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . 116

iv Backing Up Lotus Domino R5 Using Tivoli Storage Management

4.3.1 Sample backup scripts . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 116
4.3.2 Defining the schedules . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 118
4.3.3 Associating the schedules . . . . . . . . . . . . .. . . . .. . . . . .. . . . 119
4.4 Database and directory links . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 119
4.5 Shared mail . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 126
4.6 Media recovery. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 129
4.6.1 Restore database to its original location . . .. . . . .. . . . . .. . . . 130
4.6.2 Database to new location . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 131
4.7 Server recovery and migration . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 134
4.7.1 Migrating to a new Domino server . . . . . . .. . . . .. . . . . .. . . . 134
4.7.2 Disaster recovery . . . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . . 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

v

vi Backing Up Lotus Domino R5 Using Tivoli Storage Management

Figures

1. Domino Administrator client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2. Domino Designer client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3. Lotus Notes client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Domino Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5. Logical components of TDP for Lotus Domino . . . . . . . . . . . . . . . . . . . . . 24
6. Project test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7. Tivoli Storage Manager setup: management classes . . . . . . . . . . . . . . . . 33
8. Node names on Domino server machine. . . . . . . . . . . . . . . . . . . . . . . . . . 34
9. Tivoli Storage Manager Backup/Archive client . . . . . . . . . . . . . . . . . . . . . 35
10. Sample include/exclude list for backup-archive client . . . . . . . . . . . . . . . . 36
11. Sample domdsm.cfg file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
12. Scheduling TDP for Lotus Domino with Tivoli Storage Manager . . . . . . . . 46
13. Backup-archive client scheduler wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
14. TDP Scheduler Service on Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . 49
15. Lotus Domino scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
16. Partitioned Domino servers on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
17. Domino cluster environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
18. Domino cluster in test environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
19. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
20. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
21. Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
22. Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
23. Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
24. Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
25. Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
26. Example 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
27. Example 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
28. TDP for Lotus Domino NT GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
29. GUI: Selective backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
30. GUI: Incremental backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
31. GUI: Point-in-time restore (single stage) . . . . . . . . . . . . . . . . . . . . . . . . . . 95
32. GUI: Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
33. GUI: Archive Log Progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
34. GUI: View/Restore Log Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
35. GUI: Inactivate logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
36. GUI: Preference editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
37. GUI: Change TSM Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
38. Additional information about Tivoli Storage Manager server . . . . . . . . . . 105
39. Additional information about Lotus Domino server . . . . . . . . . . . . . . . . . 105
40. Modified domarc.cmd script for Windows NT . . . . . . . . . . . . . . . . . . . . . 117

© Copyright IBM Corp. 2000 vii

41. Domino’s logical directory structure: directory and database links . . . . . 120
42. Failure if you try to back up the directory link directly . . . . . . . . . . . . . . . 122
43. Successful backup of databases in the directory link . . . . . . . . . . . . . . . 123
44. Databases pointed to by a directory link restored to original locations . . 124
45. Link between users’ mail databases and shared mail databases . . . . . . 127
46. Recovery of deleted database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
47. Restore a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
48. Restore a database in a different location . . . . . . . . . . . . . . . . . . . . . . . . 132
49. Expiry of backup versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
50. Restore and apply transaction logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
51. Database properties showing undelete function . . . . . . . . . . . . . . . . . . . 140
52. Creating a view to display deleted documents. . . . . . . . . . . . . . . . . . . . . 141
53. Create an Undelete document action . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
54. Creating the Undelete button action code . . . . . . . . . . . . . . . . . . . . . . . . 143
55. Undeleting a deleted document in the Recycling Bin. . . . . . . . . . . . . . . . 144
56. Restoration of a deleted document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

viii Backing Up Lotus Domino R5 Using Tivoli Storage Management

Tables

1. Available platforms for Release 5.0 . . . . . . . . . . . . . . . ....... ...... ...5
2. User interface features. . . . . . . . . . . . . . . . . . . . . . . . . ....... ...... . . 10
3. Project DOMINO server systems. . . . . . . . . . . . . . . . . ....... ...... . . 28
4. Backup possibilities for transaction logging modes . . . ....... ...... . 110
5. Documenting your backup requirements . . . . . . . . . . . ....... ...... . 113

© Copyright IBM Corp. 2000 ix

x Backing Up Lotus Domino R5 Using Tivoli Storage Management

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

© Copyright IBM Corp. 2000 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 Backing Up Lotus Domino R5 Using Tivoli Storage Management

Mike Ebbers
International Technical Support Organization, Poughkeepsie Center

David Herbert
IBM Almaden Research Center, San Jose

Chris Zaremba
IBM Global Services, Endicott

Robert Delaney

Mary Uglow

William Degli-Angeli

Del Hoobler

Denise Conrad

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 Backing Up Lotus Domino R5 Using Tivoli Storage Management

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 Corporation’s 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,

© Copyright IBM Corp. 2000 1

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.
Domino’s 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 Backing Up Lotus Domino R5 Using Tivoli Storage Management

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 3

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 client’s 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 it’s 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 Domino Notes
Server R5 Client R5

UNIX (AIX V 4.3.1 or higher, HP-UX 11.0, Solaris/SPARC Yes No
2.6, Solaris/Intel 2.6, Solaris 7, Linux Red Hat 6.0)

OS/2 Warp Server V4.0 Yes No

Windows 95/98 No Yes

Windows NT Server 4.0 and Yes Yes
Windows NT Workstation 4.0 (Alpha and Intel)
Windows2000


Platform Domino Notes
Server R5 Client R5

Macintosh Power PC 7.6, 8.1 No Yes

AS/400 V4R2 Yes No

S/390 V2R6 Yes 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 Domino’s 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. Domino’s 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 Description

Welcome page 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 What’s New

Bookmarks Create bookmarks for anything you want to return to later whether
it’s from Notes or the Internet.

Navigation Navigate through open pages of information with tabs and Web-like
universal navigation buttons.


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:lotusdominosenegalserver.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.


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.


• 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.
• ..mailuser.nsf
This is a user’s 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


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.


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


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


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.


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.


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


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.


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


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


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.


• 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
Tivoli Storage Manager
Transaction
server
log

Domino TDP for TSM
API Lotus API
Domino

Domino R5
databases

Figure 5. Logical components of TDP for Lotus Domino


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.

© Copyright IBM Corp. 2000 25

In our project’s 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.

htiw revres denoititraP
sesserdda PI elpitlum

nedamlA/analap 2.3.4 xiA
nedamlA/ssenhcol
KOP/eo76cstw nedamlA/airotciv
EKOPS
BUH
EKOPS 0.4 revreS TN
093/SO
6R2V
retsu lC O STI

htiw revres denoititraP
sesserdda PI elpitlum nedamlA/oykot
nedamlA/lagenes
EKOPS EKOPS
nedamlA/tocrahc nedamlA/kawew
0.4 revreS TN
0.4 revreS TN

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


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 project’s environment.
Table 3. Project DOMINO server systems

Hostname System Operation Transaction Log Partition Cluster

palana Aix 4.3.2 archive Yes No

victoria Aix 4.3.2 circular Yes No

wtsc67oe OS/390 USS V2R6 disabled No No

senegal NT Srv. 4 archive Yes No

charcot NT Srv. 4 circular Yes No

lochness NT Srv. 4 archive No No

tokyo NT Srv 4 disabled No Yes

wewak NT Srv 4 disabled No 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
User’s Guide, SH26-4088
• Tivoli Data Protection for Lotus Domino for Windows NT V1R1: Installation
and User’s 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


Backing up lotus domino r5 using tivoli storage management sg245247

Backing up lotus domino r5 using tivoli storage management sg245247

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Viewers also liked

Viewers also liked (8)

Similar to Backing up lotus domino r5 using tivoli storage management sg245247

Similar to Backing up lotus domino r5 using tivoli storage management sg245247 (20)

More from Banking at Ho Chi Minh city

More from Banking at Ho Chi Minh city (20)

Recently uploaded

Recently uploaded (20)

Backing up lotus domino r5 using tivoli storage management sg245247