Lotus Domino Server Troubleshooting

From SEPsesam
Jump to: navigation, search

Copyright © SEP AG 1999-2020. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo. For previous documentation version(s), check documentation archive.


Lotus Domino Server

Lotus Domino Server backup reports recovery failure

Problem

  • Backup reports "Recovery may fail" during backup of the SEP sesam extension for Lotus Domino Server. During the backup, the following warning appears for several or all Notes databases:
sbc-2076: Warning: 
Item [D:\notus03data\mailboxes\mail1\cruoff.nsf] is not logged. 
Recovering may fail.

Possible causes

  • There may be two reasons for this:
  1. Transactional logging was not turned on or is not in Archived mode.
  2. Transactional logging is running in Archived mode but is explicitly turned off for this database in the options of the database.

Solution

  • This message is a warning of the Notes Backup API and is only forwarded by SEP sesam. Turn on Transactional logging in general or just for this database.

Other than that, the message can be ignored. The warning is given during the backup for safety reasons because only the admin can determine if administrative intervention is necessary.

Insufficient temporary space

Problem

  • Temporary space may not suffice because every database must first be copied to the client.

Solution

  • Change the path gv_rw_tmp in <SESAM_VAR>/ini/sm.ini to a directory with sufficient space.

Transactional logging not active

Problem

  • The INCR backups fail.

Solution

  • Activate Transactional logging in Archived mode for Notes.

Transaction logs already in progress

Problem

  • This message appears in the SEP sesam:
DB Module: [Archiving of transaction logs already in progress.]

Possible causes

  • The Lotus Notes API sends this message to show that the transactional logs are already in the state Backup. The state cannot be set twice. If a backup could not be completed successfully, this state mat appear.

Solution

  • To finish the backup status, all logasio processes should be removed from the Notes system:
 UNIX:     killall -9 logasio
 WINDOWS:  sm_kill logasio
  • Alternatively, you can reboot the Notes server.

Backup reports incorrect transactional logging

Problem

  • After the restore of Transactional logging, Notes reports incorrect Transactional logging.

Solution

  • Delete the nlogctrl.* files in the log directory then restart the Notes server.

Server fails to restart after a Notes server crash

Problem

  • After a crash of the Lotus Notes server, the server cannot be started without rebooting.

Solution

  • If a server crash occurs during a log backup ,logasio processes may remain active. These processes must be stopped. The server can be restarted after running the following command:
 UNIX:     killall -9 logasio
 WINDOWS:  sm_kill logasio

Backup with missing options

Problem

  • The restore of Notes on a Linux client ends with:
 "RESTORE STATUS: Restore failed. 2007-05-02 08:52:32:
  sbc-1146: Error:    DB Module: [Notes API NotesInitExtended() failure"

Possible causes

  • The restore options are not identical to the backup options.

Solution

  • Set the restore options according to the task. Additionally, the options can be set in the restore wizard under Expert options in the Options tab. For example:
 -v 3 -a USER=nadmin -a NOTESINI=/srv/notedata/notes.ini

Abnormal termination of the sbc.exe process

Problem

  • Lotus Domino Console repeats: "C:\..\SEPSesam\bin\sesam\sbc.exe Process has terminated abnormally".

Possible causes

  • If there is a backup failure that causes the SEP sesam backup client to terminate abnormally, the failure will be notices by the Lotus Domino server API and repeat this error message every minute in its logging. If this persists over multiple reboots, please read this article from IBM on how to remove the message from the Domino logging: http://www-01.ibm.com/support/docview.wss?uid=swg21252974

Solution

  • Stop the Domino server forcibly by running nsd -kill.

Restoring Notes database files to different location doesn't work

Problem

  • When doing a restore of database files as a Notes restore to a different file location under Notes_Data, all databases are skipped.

Possible causes

  • Notes denies an access to an existing database with the same replica-id, e.g.:
Item [\JOBSCHED.NJF] not included. Skipped...

Solution

  • In the SEP sesam restore wizard, select a file location outside of Notes_Data and store the database file there. This makes it possible to copy the file to the Notes data directory structure.

See also

Lotus Domino