Upgrading a server using Option 3

With this option, you install the new version of Domino on new hardware. This option requires you to shut down the original server once you being copying its Domino files to the new hardware.

Before you begin

Before continuing, see Options for upgrading a Domino server.

Procedure

  1. Configure the new hardware.
  2. 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.
  3. Note the location of the program, data, and transaction log directories on the current server.
  4. Note the network configurations (IP addresses, host file, etc.) on the original server.
  5. From the new hardware, connect to the file system of the original server.
  6. Copy the Domino program, data, and transaction log directories to the new hardware, placing them in the exact, relative location as they are on the original server.
    Note: If you are changing file locations and directory structure during this move, refer to the Support article: Changing directory locations when moving a Domino server to new hardware for more information.
    Note: Once you start copying the files to the new hardware, do not run the original server.
  7. (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.
  8. Install the new version of Domino on the new hardware, pointing the same relative directory locations used by the original server.
  9. Switch the server host and network identities to be that of the original server.
  10. Before starting the new (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.)
  11. Start the new (upgraded) Domino server on the new machine.
  12. (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.)
  13. 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.
  14. Run this configuration for a few days to make sure everything runs correctly. If there are no issues, you can safely discard the existing Domino server.