Restoring NSF databases to an alternate server

Edit online

Instructions for how to restore NSF databases to an alternate server are described.

About this task

This procedure describes how to use an alternate server to restore logged databases.

Production Server Domino Environment
  • Installation directory: /opt/lotus
  • Data Directory: /production/notesdata
  • Notes User: notesp
  • Database to be restored: restoredb.nsf
Alternate Server Domino Environment
  • Installation directory: /opt/lotus
  • Data Directory: /alternate/notesdata
  • Notes User: notesa

Procedure

  1. Install Domino server on a separate system.
    1. The level of Domino server that is installed must be the same as on the production server. Do not configure this Domino server.
    2. If you are using an existing Domino server, make sure that the server is stopped.
  2. Install Data Protection for HCL Domino on the same system. Run the following tasks:
    1. Run the dominstall program. For more information about dominstall, see Configuring manually with dominstall.
    2. Update the Notes user environment as created by the dominstall program.
    3. Update the dsm.opt and dsm.sys files so that they contain the same settings as these options files on the production server.
    4. If the nodename option is not set in the IBM Storage Protect server stanza, add the nodename option and specify the host name of the production server.
    5. Verify that you can successfully run the domdsmc q adsm command.
  3. Create the following directories (as the Notes user) on the alternate server:
    1. A directory to contain the restored databases. If you are using an existing directory, make sure that the directory is empty.
      For example:/alternate/notesdata/restoredb
    2. A directory to contain the restored log files. If you are using an existing directory, make sure that the directory is empty.
      For example: /alternatelog
  4. Create (as the Notes user) a notes.ini file on the alternate server with the following values: [Notes] Directory=<directory for restored databases> KeyFilename=<directory for restored databases>/server.id TRANSLOG_Status=0 TRANSLOG_Style=1 TRANSLOG_Path=<directory for restored transaction logs> TRANSLOG_MEDIAONLY=1. This notes.ini file can be stored in any directory of your choice.
    1. If you place the notes.ini file in the alternate server data directory, save a copy of the existing notes.ini file.
      For example:mv notes.ini notes.save
    2. If you place the notes.ini file in a directory other than the alternate server data directory, update the Data Protection for HCL Domino preferences file, domdsm.cfg, to point to the location of the notes.ini file: DOMDSMC SET Notesinipath=<directory for notes.ini>
    3. This notes.ini file is used only during this alternate server restore process. Note, transaction logging is disabled.
      For example, /alternate/notesdata/notes.ini[Notes] Directory=/alternate/notesdata/restoredb KeyFilename=/alternate/notesdata/restoredb/server.id TRANSLOG_Status=0 TRANSLOG_Style=1 TRANSLOG_Path=/alternatelog TRANSLOG_MEDIAONLY=1
  5. Place a copy of the server.id file, from the production Domino server, on the alternate server in the directory that is created for restored databases. Change the permissions of the server.id file to be accessible to the alternate server Notes user.
  6. Run an archive of the transaction log (as the Notes user) on the production server.
    For example: domdsmc archivelog
  7. Restore (as the Notes user) one of the following on the alternate server:
    1. The last archived transaction log file is the transaction log file to be used in the log recovery procedure.
      For example: domdsmc restorelogarchive.
    2. A transaction log file to be restored from an old Logger ID. This might be necessary if you are trying to restore and apply transactions for a logged database that used an old Logger ID. Run the restorelogarchive command with the pick option, and choose the wanted log extent.
      For example: domdsmc restorelogarchive logname /pick=showall
  8. On the alternate server, modify (as the Notes user) the notes.ini file to enable transaction logging: TRANSLOG_Status=1. This is the notes.ini file that is created in Step 3 for the alternate server restore process only.
    Note: The HCL Domino server must be restarted and then stopped so that it can recognize the changes that are made to the notes.ini file.
  9. On the alternate server, restore (as the Notes user) but do not activate the databases that you want to recover to their latest state.
    Activation at this step triggers the Domino transaction log recovery process, which requires considerable processing time. For example,domdsmc restore restoredb.nsf.
  10. On the alternate server, activate (as the Notes user) the databases you are recovering and apply transaction logs.
    For example, domdsmc activate /applylogs.
  11. Now you can do the following tasks:
    • Copy the recovered databases to the production Domino server, or
    • Access the recovered databases through a remote Notes client to copy individual documents.
    Do not attempt to open or access the restored databases with the alternate Domino server if the databases are to be copied to the production Domino server. If you access them with the alternate Domino server, they require corrections to resolve inconsistencies on the production Domino server.
  12. If the Domino server used for the recovery is a configured server and you saved the notes.ini file, copy that notes.save file back to notes.ini to be able to start the server.