SOLVED: Domino V10.0.1 – Symmetrical cluster configuration… May the journey continue

2 days ago I posted this blog entry about the new feature of “Symmetrical Cluster” in Domino V10 ( https://bit.ly/2EFtuyT ).

After opening a case I received the information that the “RepairCleanup” task only is running when there´s something to repair. During my V10.0.1 migration last week the RepairCleanup task I started via the ServerTasks entry in the NOTES.INI started right after the restart of the Domino server.

It is simply explained because there have been defect databases or the cluster was not in symmetry ( was this tool was made for… ).

During the migration this week the cluster was running fine and no databases had to be repaired why the RepairCleanup task shutdown after some seconds.

Today I received the information from the Support Team that it´s recommended to add the “RepairCleanup” task to the NOTES.INI ( for a repair of defect or “out of sync” cluster databases during startup ) AND also create a program document for a scheduled run of the “RepairCleanup” task like this:

( on a Windows server use “nserver” in the Program Name field )

Maybe the documentation should be updated because you cannot find the information that this is not only recommended but mandatory…

Advertisements

Domino V10.0.1 – Symmetrical cluster configuration… May the journey continue

This week I migrated a Domino 9 environment to new Operating Systems, migrated them to V10.0.1 and everything ran fine.

Today I tried to activate the new feature “Symmetrical Cluster” and ran into another problem. Of course I also did this little customization ( https://bit.ly/2H52biZ ) but when trying to start the “RepairCleanup” task I received the following error message on the server console:

lo RepairCleanup

OSGetModuleHandle failed
Repair Cleanup started
Repair Cleanup shutdown

Any idea what´s causing this error message ?? I already opened a case and hopefully will receive a quick solution.

Sync database quotas between servers

Today I again had the issue, that Database Quotas have not been synced between IBM Domino Cluster servers. After some search, I found the following post:

http://tippner.blogspot.co.at/2011/08/synchronizing-database-quotas.html

I did some modifications in the code and ran the agent with the Server ID and scheduled the agent one time a day… So far it´s looking fine…

You can download the database here: https://www.dropbox.com/s/9ebh3r0qh4hl6ft/sync_dbquotas.nsf?dl=1