Note When you create replicas on cluster mates for either the Move Replica or Create Replica process, the Administration Process assumes that Connection documents are in place to schedule replication between the source and destination servers.
Check access
Carried out on: The server that contains the database being replicated.
Carried out: Immediately
Result: The Administration Process on the source server checks that the user submitting the request and the destination server have at least Reader access in the ACL of the database. If the user and destination server have the necessary access and if a Connection document between the source and destination server exists, the Administration Process generates a "Accelerated create replica" request in the Administration Requests database of the source server.
Carried out on: The source server for the database.
Result: The Administration Process on the source server checks that the signer of the request is the source server. The Administration Process either creates a new copy of the database on the destination server by using Domino backup APIs or by creating a replica stub on the target server and then immediately populating the database. The decision to use the API, or not, can be based on whether you want to synchronize unread marks during replication. Under the following conditions, it is not possible for the Administration Process to create the new database using the Domino backup APIs:
Create replica
To populate the replica, the user submitting the request and the source server must have Create Replica access to the destination server. To populate the replica, some server with which the destination server replicates must have a replica of the database.
Carried out on: The destination server for the database.
Result: A new replica of the database is placed on the destination server. The database is populated during the next replication.