Veritas NetBackup™ for Lotus Notes Administrator's Guide
- Introduction to NetBackup for Lotus Notes
- About NetBackup for Lotus Notes
- About the features for NetBackup for Lotus Notes
- About supported Lotus Notes database configurations
- About the Lotus Notes database files that can be backed up
- About Lotus database transaction logging styles
- About recycling Lotus database transaction log extents
- About Lotus Notes backup operations
- About Lotus Notes restore operations
- Installing NetBackup for Lotus Notes
- Planning the installation of NetBackup for Lotus Notes
- Verifying the operating system and platform compatibility
- NetBackup server and client requirements
- Lotus Notes server software requirements
- About the license for NetBackup for Lotus Notes
- Specifying the Lotus Notes home path (UNIX)
- (UNIX or Linux) About adding new Lotus Notes installations
- Configuring NetBackup for Lotus Notes
- About configuring NetBackup for Lotus Notes
- Configuring Lotus fast restores
- Defining properties for a Lotus Notes client
- About configuring a backup policy for a Lotus Notes database
- Adding a new NetBackup for Lotus Notes policy
- About policy attributes
- Adding schedules to a NetBackup for Lotus Notes policy
- Adding clients to a policy
- Adding backup selections to a Lotus Notes policy
- About directives in the backup selections list for Lotus Notes policies
- About backups of Windows network shared folders and UNIX NFS directories
- About excluding Lotus Notes databases from backups
- About backups of Lotus database links and directory links
- Configuring a backup policy for Lotus Notes database supporting files
- Performing a manual backup
- Performing backups and restore of Lotus Notes databases
- About performing backups and restores of Lotus Notes databases
- About performing user-directed backups of a Lotus Notes database
- About performing a Lotus Notes database restore
- Redirecting a Lotus Notes restore to a different client
- About restoring individual Lotus Notes documents or mail messages
- Recovering the Lotus Notes environment
- Domino clustering
- Domino partitioned servers
- Domino server multiple installations (UNIX or Linux)
- Troubleshooting NetBackup for Lotus Notes
About Domino clustering components
Several components work together to control a Domino cluster. These components include the Cluster Manager, the Cluster Database Directory, the Cluster Database Directory Manager, and the Cluster Replicator.
The Cluster Manager runs on each server in a Domino cluster and monitors the state of the other servers in the Domino cluster.
The Cluster Manager performs the following tasks:
Determines which servers belong to the Domino cluster
Monitors for server availability and workload
Fails over database requests due to unavailability of a clustered Domino server
Performs workload balancing
The Cluster Database Directory (CLDBDIR.NSF) is replicated on every server in a Domino cluster. The Cluster Database Directory contains information for each database on each server in the Domino cluster. This information includes file name, server, replica ID, cluster replication status, and out-of-service information. The different cluster components use this information to perform their tasks.
The Cluster Database Directory Manager (CLDBDIR) task on each server manages the Cluster Database Directory and keeps it up to date. The Cluster Database Directory Manager also monitors the status of each database to determine if they are out of service or not yet deleted.
The Cluster Replicator (CLREPL) task constantly synchronizes the database replicas in a Domino cluster. Changes to the database are pushed immediately to the other replicas in the cluster. This event-drive replication ensures that each time a database is accessed that it contains the most up-to-date data. The Cluster Replicator task pushes changes only to those servers in a Domino cluster. The traditional scheduled replication is used to replicate changes to and from servers outside a Domino cluster.
Because Domino stores replication events in memory only, both the source server and destination server must be available for the replication to complete successfully. If a destination server is not available, the replication events are stored on the source server until the destination server becomes available. If the source server shuts down before the replication completes, the replication events in memory are lost. To prevent this loss, configure immediate replication with all members of the Domino cluster whenever a Domino cluster server is restarted. Perform scheduled replications between Domino clustered servers on a regular basis to help maintain database consistency for all members of the Domino cluster.