Veritas NetBackup™ for Lotus Notes Administrator's Guide
- Introduction to NetBackup for Lotus Notes;
- 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 Notes fast restores
- Configuring host properties for a Lotus Notes client
- About configuring a backup policy for a Lotus Notes database
- Adding a 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 for Domino policies
- 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
- Domino clustering
- Domino partitioned servers
- Domino server multiple installations (UNIX or Linux)
- Troubleshooting NetBackup for Lotus Notes
- About NetBackup for Lotus Notes debug logging
- Enabling the debug logs for a NetBackup for Lotus Notes client automatically (Windows)
- Debug logs for NetBackup for Lotus Notes backup operations
- Debug logs for NetBackup for Lotus Notes restore operations
- Setting the debug level on a UNIX client
- Setting the debug level on a NetBackup for Lotus Notes Windows client
- About NetBackup status reports
- About Notes restore operations
- About NetBackup for Lotus Notes debug logging
- Index
Example of clustered environment with four Domino servers
The environment is a Domino clustered environment with four Domino servers as members of the Domino cluster. Server A is identified as your backup server and runs archive-style transaction logging. Servers B, C, and D run circular or linear-style logging. To provide load balancing across all the servers, replicas of all databases exist on all four servers in your Domino cluster. A successful full backup of all databases was completed earlier in the week. Successful incremental backups of the archival-style transaction logs are completed every four hours, with the last one completing two hours ago. At 2:30 P.M., a user complains that the database acme.nsf is corrupted, while they modified the database on server C over the last 30 minutes. Unfortunately, because the environment is a Domino cluster environment, the corruption is replicated to all four member servers. The users state that the database was in a consistent state when they began to modify the database.
To restore a database to a consistent state do the following:
On server A, perform a point-in-time recovery of the database acme.nsf. Select the database acme.nsf from the last successful backup of the database (for example, a full backup that was completed successfully earlier in the week). Begin the restore.
On the Lotus Notes tab of the Restore Marked Files dialog box, select the option. Select the option. Specify today's date at 2:00 P.M. (the time that the user started to modify the database) as the point-in-time for recovery.
After the restore or recovery is successful, a version of acme.nsf from 2:00 P.M. today should exist on server. Verify the consistency of acme.nsf on server A. If all is as expected, from server A create new replicas of acme.nsf on servers B, C, and D. Cluster replication should now be functional on servers A, B, C, and D, with a consistent version of acme.nsf.