Shutting down a server cleanly

Before upgrading a Domino server, it’s important to shut down the server cleanly, without errors or hangs.

About this task

If the server doesn’t shut down cleanly, complete the following steps. These steps invoke the Recovery Manager and flush the transaction logs to disk, simulating a clean server shutdown.

Procedure

  1. Run nsd -kill.
  2. With the Domino server shut down, run a Domino maintenance task against a non-existent database. For example, run c:\domino>nfixup.exe fred.nsf, which generates output like this: 
    c:\domino> nfixup.exe fred.nsf 
Restart Analysis (117 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
Recovery Manager: Recovery being performed for DB d:\notefile\mail.box
Recovery Manager: Recovery being performed for DB d:\notefile\names.nsf
Recovery Manager: Recovery being performed for DB d:\notefile\log.nsf
Restart Replay (116 MB): 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
04/22/2018 04:33:03 PM Recovery Manager: Restart Recovery complete. (3/2 databases needed full/partial recovery)
04/22/2018 04:33:07 PM Informational, rebuild view needed - collection object was deleted (reading d:\notefile\names.nsf view note Title:'($Servers)')
04/22/2018 04:33:08 PM Informational, rebuilding view - container integrity lost (reading d:\notefile\names.nsf view note Title:'($Servers)')
04/22/2018 04:33:08 PM Informational, rebuild view needed - collection object was deleted (reading d:\notefile\names.nsf view note Title:'($Servers)')
04/22/2018 04:33:10 PM Database Fixup: Started
04/22/2018 04:33:10 PM Database Fixup: The pathname 'd:\notefile\fred' was not found: File does not exist
04/22/2018 04:33:10 PM Database Fixup: Shutdown