Quick Recovery for Lotus Notes: Fast Steps to Restore Mailboxes

Emergency Guide: Quick Recovery for Lotus Notes Files and Databases

Date: March 4, 2026

Overview

When Lotus Notes (IBM Notes/HCL Notes) mailboxes, NSF files, or databases become corrupted, accidentally deleted, or unavailable, fast, structured action reduces downtime and data loss. This emergency guide gives concise, actionable steps to assess damage, perform immediate recovery, and validate restored data.

Immediate priorities

1. Stop further writes — Prevent additional damage by taking affected databases offline or marking them read-only where possible.
2. Preserve backups and logs — Secure the latest full backups, incremental backups, and transaction logs (if using Domino clustering or transaction logging).
3. Isolate affected servers/clients — If corruption might spread, isolate the server or client from the network.

Quick assessment (5–15 minutes)

• Identify scope
  • Which NSF files/databases are affected (mail, application DBs, replicas)?
  • Number of users impacted.
• Check server health
  • Domino console: review error messages and server task statuses.
  • Disk space, memory, and I/O errors at OS level.
• Check backups and replication
  • Latest good backup timestamp.
  • Replica availability and last replication times.

Rapid recovery options (ranked fastest → safer)

1. Restore from latest backup
   • Restore the damaged NSF from last known good backup to a recovery location.
   • Replace the corrupted NSF only after verifying the restored file opens cleanly.
2. Use replica copy
   • If a healthy replica exists on another server or client, copy it to replace the damaged file.
   • Replicate changes back to other replicas to re-sync.
3. Transaction log replay (if enabled)
   • Ensure the correct base backup is present.
   • Use Domino Server’s transaction logging to roll forward to a consistent point.
4. Repair with nfixup, ncompact, nrepair
   • Run nfixup to check and fix view/index issues.
   • Use ncompact to rebuild databases; include -c option for compacting.
   • Use nrepair or database maintenance tools (third-party if available) for severe corruption.
   • Always work on a copy of the corrupted NSF—not the production file.
5. Restore from mail server’s tombstones/Trash (for deleted mail)
   • Check Domino Trash or user mail’s Deleted Items before restoring from backup.
6. Third-party recovery tools
   • When built-in tools fail, use reputable NSF recovery utilities to extract data from damaged files.

Step-by-step emergency restore (example workflow)

1. Quarantine the corrupted NSF: move to a safe folder and mark production replica read-only.
2. Retrieve latest backup or healthy replica and place in server data directory as a new filename (e.g., maildbrecovered.nsf).
3. Start Domino and open the recovered NSF with the Notes client or Domino Administrator.
4. Run nfixup:

   Code
    ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf” data-copycode=“true” role=“button” aria-label=“Copy Code”>Copy CodeCopied
   nfixup -f maildbrecovered.nsf 

5. Run ncompact:

   Code
    ffON2NH02oMAcqyoh2UU MQCbz04ET5EljRmK3YpQ CPXAhl7VTkj2dHDyAYAf” data-copycode=“true” role=“button” aria-label=“Copy Code”>Copy CodeCopied
   ncompact -c -i maildb_recovered.nsf 

6. Verify views, agents, and ACLs. Check mail routing for users.
7. If transaction logging is used, perform log replay per documented steps to bring DB to the desired point-in-time.
8. Replace production NSF only after full verification and notify affected users.