Upgrading a server using Option 2

This option uninstalls the current Domino version before installing over the current version.

Before you begin

Before continuing, see Options for upgrading a Domino server.

Procedure

  1. Shut down the Domino server. Make sure the server shuts down cleanly, with no errors or hangs. For information on what to do if the server doesn’t shut down cleanly, see Shutting down a server cleanly.
  2. Before uninstalling, make a backup of the following files:
    File name Location
    NOTES.INI Domino program directory (...\Domino)
    NAMES.NSF Domino\Data directory

    Any other directory databases (if your environment uses them):

    • Directory Assistance
    • Extended Directory Catalog
    • Condensed Directory Catalog
    • Schema database
    		 Domino\Data directory
    LOG.NSF Domino\Data directory
    CERTLOG.NSF Domino\Data directory
    *.NTF (ONLY templates you have modified) Domino\Data\*.NTF
    *.ID Domino\Data\*.ID
    Mail Files Domino\Data\Mail\*.*
    Diagnostic Files \Domino\Data\IBM_TECHNICAL_SUPPORT\*.*
  3. Confirm that the backup files are acceptable.
  4. Uninstall Domino using the uninstaller.
  5. Reboot the machine.
  6. (DAOS, pre-V11 upgrade) Rename the daoscat.nsf in the data directory to daoscat.bak or some other unique non-nsf name. For example: mv/local/notesdata/daoscat.nsf/local/notesdata/daoscat.bak.
  7. Launch installer application.
  8. Follow on-screen prompts.
  9. Before restarting the upgraded server:
    1. Set the notes.ini to the desired database ODS level. For example, for the V12 ODS level, use Create_R12_Databases=1. For more information, see Domino on-disk structure (ODS) in the Domino documentation.
    2. Upgrade databases to the specified ODS level by running the command dbmt -compactThreads <n> <datadirectory> where <n> is a value less than or equal to the number of CPUs. For example:
      • Windows: ndbmt.exe -ct 4 d:\notefile\
      • AIX and Linux: dbmt -ct 4 /local/notesdata/
      • IBM i: (See article How to run Fixup, Compact, or other command while the Domino iSeries server is down on the Support site.)
    3. (DAOS, pre-V11 upgrade) Run the following command to create daoscat.nsf and the catalog indexes.
      • Windows: ndaosmgr.exe resync quick
      • AIX and Linux: daosmgr.exe resync quick
      • IBM i: (See article How to run Fixup, Compact, or other command while the Domino iSeries server is down on the Support site.)
  10. Start the Domino server.
  11. (DAOS, pre-V11 upgrade) Schedule a full resync at some point in the future, for example off-business hours in a maintenance window with the Domino Server down. DAOS object deletions are suspended until the full resync is completed.
    • Windows: ndaosmgr.exe resync force
    • AIX and Linux: daosmgr.exe resync force
    • IBM i: (See article How to run Fixup, Compact, or other command while the Domino iSeries server is down on the Support site.)
  12. Run the Fixup task at some point in the future, for example off-business hours in a maintenance window with the Domino Server down, as described in the Running Fixup section. This step ensures that any updates to the fixup task that have been released in the latest version of the Domino server are applied to your environment.
  13. After the upgrade is complete and you have verified that Domino is operating as expected, you can optionally remove the backup files. If there is a need to recover a file from the backup, shut down the Domino server, recover the files from the backup, and then restart your Domino server to determine if the issue is resolved.