Der IBM/Lotus Support erzählte uns, dass unsere Backup-Software beim Backup-Vorgang die notes.ini des DOmino-Servers sperrt. Das hat zur Folge, dass der Domino-Server nicht mehr auf seine Konfig-Datei "notes.ini" zugreifen kann und daher solche Fehlermeldungen bring uns schliesslich hängt. Wir haben sogar ein HotFix zu dem Problem von der IBM gekriegt.
Gruss,
Andycha
PS: Es gibt einen SPR, der das Problem beschreibt:
Content *
This issue has been reported to Quality Engineering via SPR JCHS63CL7J.
Dev were able to reproduce this problem by locking the Notes.INI file using the same APIs Legato NML uses to read the Notes.INI. To make sure that this is the exact same problem that the customer is having, please have the customer stop backing up the Notes.INI file. In Legato NML, the network backup client allows files to be added to an exclusion list. To test this theory, please have the customer add the Notes.INI to Legato NML's Exclusion list so that it is no longer backed up. This will tell us the we have nailed the cause of the problem, and also provide the customer with one possible workaround.
What we believe to be happening is the Legato NML Backup Client opens the Notes.INI file for shared read access. Notes, eventually gets a filesystem error when it does a fileIO operation on the Notes.INI, (most likely a write operation). This operations fails. Notes periodically checks for the list of enabled ports on the server, by looking at the Notes.INI (Ports=) variable. The operation eventually fails, which causes the Notes Server to shutdown all it's ports. This problem is not limited to the (Ports=) notes.ini. All Note.INIs read/write operations can fail, returning incorrect results, it the Notes.INI file was locked by someone outside of Notes/Domino.
The workaround that is proposed to customers is not to use -R option in MYARGS or the NOTES: as a saveset rather use NOTES:Drive\Full_Path\Domino_Data_Directory as a saveset. This will ensure to skip backing up the notes.ini. This is only a temporary workaround to get a better understanding of the nature of this issue.
For disaster recovery purposes, the notes.ini needs to be backed up.
