The restore of a Lotus Domino database is a two-part process. The first part of the restore copies database files from the media to the server. The second part of the restore is a recovery process that applies data from the transaction logs to the database to bring it up-to-date.

During a restore of the Lotus Domino database, the existing database is taken offline and deleted, the database is restored, and changed records contained in the backup job are applied to the database.

If the database is unlogged or local, the database is brought back online. If the database is logged and multiple databases are being restored, the database name is added to a list for recovery. During the restore process, Backup Exec assigns a unique name to databases and then before databases are brought online, reassigns the original name. Changing the name during the restore process has no effect on restored databases.

The recovery process begins automatically after the last database is copied to the server. The database is restored to a point in time using transactions from the required transaction logs. Required transaction logs that were backed up and recycled are also included in the recovery process. After the recovery process completes, the Lotus Domino database is brought online.

If you back up your Lotus Domino databases regularly, then restoring the most recent backup set containing the Lotus Domino data is all that is required to restore the most recent backups of your Lotus Domino databases.

Use the same procedures to restore a server in a Microsoft Cluster Server cluster that you use to restore a server in a non-clustered environment.

When restoring a Lotus Domino database to a MCSC cluster and a failover occurs during the restore operation, active restore jobs are paused for 15 minutes as they wait for existing connections to resolve themselves. If the restore job does not restart before the failover time-out period expires, the job fails. If this occurs, the restore job must be resubmitted.