Veritas NetBackup™ for HCL Domino Administrator's Guide

Last Published:
Product(s): NetBackup (9.1)
  1. Introduction to NetBackup for Domino;
    1.  
      About the features for NetBackup for Domino
    2.  
      About supported Notes database configurations
    3.  
      About the Notes database files that can be backed up
  2. Installing NetBackup for Domino
    1.  
      Planning the installation of NetBackup for Domino
    2.  
      NetBackup server and client requirements
    3.  
      Notes server software requirements
    4.  
      About the license for NetBackup for Domino
    5.  
      Specifying the Notes home path (UNIX)
    6.  
      (UNIX or Linux) About adding new Notes installations
  3. Configuring NetBackup for Domino
    1.  
      About configuring NetBackup for Domino
    2. Configuring Notes fast restores
      1.  
        About the transaction log cache path
      2.  
        About the maximum number of logs to restore
    3. Configuring host properties for a Notes client
      1.  
        Lotus Notes properties
    4. About configuring a backup policy for a Notes database
      1.  
        Adding a NetBackup for Domino policy
      2.  
        About policy attributes
      3. Adding schedules to a NetBackup for Domino policy
        1.  
          About schedule properties
        2.  
          NetBackup for Domino backup types
      4.  
        Adding clients to a policy
      5. Adding backup selections to a Notes policy
        1.  
          Adding directives to the backup selections list
        2.  
          About directives for Notes policies
        3.  
          Adding Notes databases to the backup selections list
      6.  
        About excluding Notes databases from backups
      7.  
        About backups of Notes database links and directory links
    5.  
      Configuring a backup policy for Notes database supporting files
    6.  
      Performing a manual backup
  4. Performing backups and restore of Notes databases
    1. Performing a user-directed backup of a Notes database
      1.  
        Options for Notes database backups
    2. Restoring a Notes database
      1.  
        General tab
      2.  
        Lotus Notes tab
      3.  
        Restoring linked databases or directories and the link file
      4.  
        Restoring linked databases or directories and manually recreating the link file
    3.  
      Redirecting a Notes restore to a different client
    4.  
      Recovering the Notes environment
  5. Domino clustering
    1.  
      About Domino clustering components
    2.  
      Backing up a Domino replicated or clustered environment
    3. About the restore and recovery in a Domino replicated or clustered environment
      1.  
        Example of clustered environment with four Domino servers
      2.  
        Example of clustered environment with three Domino servers
  6. Domino partitioned servers
    1.  
      About Domino partitioned servers
    2.  
      About performing backups in a Domino partitioned server environment
    3.  
      About restoring a Domino partitioned server environment
  7. Domino server multiple installations (UNIX or Linux)
    1.  
      About Domino server multiple installations
    2.  
      About configuring NetBackup for a multiple Domino server environment
    3.  
      About backups in a multiple Domino server environment
    4.  
      About restores a multiple Domino server environment
  8. Troubleshooting NetBackup for Domino
    1. About NetBackup for Domino debug logging
      1.  
      2.  
        Debug logs for NetBackup for Domino backup operations
      3.  
        Debug logs for NetBackup for Domino restore operations
      4.  
        Setting the debug level on a UNIX client
      5.  
        Setting the debug level on a NetBackup for Domino Windows client
    2. About NetBackup status reports
      1.  
        Viewing the progress report of a NetBackup for Domino operation
    3.  
      About Notes restore operations
    4.  
      Windows client backup fails with status 69
    5.  
      Point-in-time restore from master server fails with status 12

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 Assign new database instance ID and replica ID option. Select the Recover database(s) to specified point in time 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.