Create replica

You can create a database replica using this AdminP (Administration Process) request by selecting a database and then choosing Database - Create Replica from the tools pane in the Domino® Administrator.

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

Triggered by: Initiating the command from the Domino® Administrator.

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.

Accelerated create replica

Triggered by: Successful completion of the Check Access administration request.

Carried out on: The source server for the database.

Carried out: Immediately

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:

  • Source and destination server are not clustered
  • Destination server is a pre-Domino 6 server
  • Source database is linked with the Single Copy Object Store
  • Source database is a Single Copy Template database and the Single Copy Template does not exist on the destination server
  • Source database is full-text indexed and it is requested that the destination is not full-text indexed

In the conditions listed, if the administrator has included unread mark synchronization as part of the create replica request, the Administration Process attempts to create a replica stub on the target server, populate its contents, and then synchronize the unread marks immediately. If this fails, or if the administrator does not specify the synchronization of unread marks, a comment is generated in the administration request's log and processing continues. A Create Replica request is generated in the Administration Requests database on the source server.

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.

Triggered by: Unsuccessful completion of the Accelerated create replica administration request.

Carried out on: The destination server for the database.

Carried out: Immediately

Result: A new replica of the database is placed on the destination server. The database is populated during the next replication.