You can create multiple commands in txt file and then launched from a single command in the server console.
Create a text file and name it c:\replica-commands.txt.
Enter the following information into the file and save it: cl copy Server1!!DB1.nsf Server2!!DB1.nsf replica cl copy Server1!!application\DB2.nsf Server2!!application\DB2.nsf replica cl copy Server1!!DB3.nsf Server2!!application\DB3.nsf replica
At the Domino console, type “< c:\replica-commands.txt >” The Domino console will execute thecommands listed in the text file sequentially.
Domino 10.0.1 now allows for easier configuration of SSL ciphers. The SSL cipher options are in the Security tab of Internet Site documents or in the Ports tab of Server documents. Now clearly list all of the supported SSL ciphers, in order of strength Note that the
RSA_WITH_3DES_EDE_CBC_SHA cipher is categorized as a weak cipher as of Domino 10. This is a change from Domino 9.0.1.
Sometimes you need to make a copy of the database (not a replica) to another server or an existing server.
Most of the Notes client uses an option in the File – Application – New Copy. You select the location of the DB name and start creating a copy.
However, when creating a copy from a server to a server, all of the data first goes to your local Notes client and then back to the server. The whole operation will take a lot of time, and your computer and local network will be busy.
You can use the command on the Domino console.
First, add a parameter to the server notes.ini: CLUSTER_ADMIN_ON=1 Servers do not need to be a part of a Domino Cluster
You can now use these commands: CL copy server1!!dbA.nsf server2!!dbB.nsf This would create a regular non-replica copy of dbA.nsf on server1 as dbB.nsf on Server2
CL copy dbA.nsf dbB.nsf This would create a regular non-replica copy of dbA.nsf as dbB.nsf on the same local server
CL copy server1!!dbA.nsf server2!!dbB.nsf REPLICA This would create a replica copy of dbA.nsf on server1 as dbB.nsf on Server2
CL copy server1!!dbA.nsf server2!!dbB.nsf TEMPLATE This would create a template copy (only design, no data) of dbA.nsf on server1 as dbB.nsf on Server2
ODS 53 supports larger databases and folders. The maximum size of databases allowed in IBM Domino 10 has increased to 256 GB; previously it was 64 GB.
ODS 52 is the default ODS level. he default On-Disk Structure (ODS) for databases is now ODS 52, the ODS for IBM Domino and Notes 9.0.1. Unless there is a Create_Rx_Databases=1 notes.ini setting on server or client that specifies another ODS (for example, Create_R10_Databases=1).
Publishing statistics to external services. A Domino server is preconfigured to publish Domino statistics to the New Relic service using the New Relic Plugin API.
Dynamic indexing of high-usage views. IBM Domino now dynamically assigns dedicated view indexing threads to views with content that is frequently updated. This feature keeps busy views up-to-date and enables them to be opened more quickly.
Symmetrical clusters. Symmetrical clusters is a feature that ensures that Notes databases remain identical across all servers in a cluster. Any missing or damaged databases are repaired (replaced) with good copies from a donor cluster member.
Improved streaming cluster replication during server restarts. IBM Domino 10 implements streaming cluster replication improvements that help preserve the state of the SCR queue after Domino server restarts.
New way to synchronize database replicas. IBM Domino 10 provides a new argument for the Replicate command, -F, to force a full database replication when replicas of a database get out of sync. The replication occurs on the side and allows users to continue to see replication updates during the full replication.
Document deletion logging. A new compact task option is available to enable logging of data about deleted documents in databases that you specify. The data is logged to entries in deletion log files added to the IBM_TECHNICAL_SUPPORT directory on a server. For example, you can log when documents are deleted from mail files to help troubleshoot if users report missing documents.
Automatic dead mail processing. Dead mail occurs when the router can’t deliver or transfer a message to the intended recipient or a non-delivery report to the sender. Prior to Domino 10, if administrators wanted to retry sending dead mail, they did it manually. Also, dead mail stayed in mail.box until an administrator deleted it. In Domino 10, administrators can configure the router to automatically retry delivery of dead mail and if unsuccessful delete it from mail.box after a specified number of retry attempts.