Of course there are multiple ways to create copies or replicas of databases either to other folders on the same server or to other servers ( especially when the servers are running in a cluster ).
I always use the following way and it´s working very fine:
First, you have to set an entry in the NOTES.INI of the server where you want to put the commands directly in the console:
You also can set this NOTES.INI setting directly from the console with a “set configuration Cluster_Admin_On=1” – you don´t have to restart the server, … ! This parameter is taken “on the fly”.
Now to the commands:
cl copy sourcedatabase targetdatabase > Example: cl copy dev/demo.nsf prod/demo.nsf > Creates a copy of the database dev/demo.nsf in the directory prod
cl copy sourcedatabase targetdatabase replica > Example: cl copy Server1!!dev/demo.nsf Server2!!dev/demo.nsf replica > Creates a full replica of the database dev/demo.nsf on Server 1 on Server 2
cl copy sourcedatabase targetdatabase template > Example: cl copy Server1!!dev/demo.nsf Server2!!dev/demo.nsf template > Only creates a template from the database dev/demo.nsf on Server 1 on Server 2 without any data
You also can use this command to create copies, replicas or templates within a program document:
If you plan to run multiple “cl copy” commands you can pack them into a single text file ( in the example it´s called “command.txt” ):
There all new mail databases are created. I now activated the RepairCleanup task and the “repaired” ( because not existing mail databases ) have been successfully created from the cluster member, but not in the directory from the directory link. Instead of the directory from the Directory Link, a new directory “mail” was created in the DATA directory:
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…
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:
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.