Move database from a non-cluster server

Check access for non-cluster move replica

Triggered by: Executing the non-cluster move command.

Carried out on: The source server for the database.

Carried out: Immediately

Result: The Administration Process on the source server checks that the user submitting the request is the Manager of the Domino® Directory and that the destination server has Reader access in the ACL of the database. Posts a Non-cluster Move Replica request.

Accelerated create replica

Triggered by: Successful completion of the Check Access for non-cluster move replica 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 creates a new copy of the database on the destination server using Domino backup APIs. Under the following conditions, it is not possible for the Administration Process to create the new database using the Accelerated Create Replica request:

• Source and destination server are not clustered
• Destination server is pre-Domino 6
• 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 has Reply/Forward Indication enabled and the destination server is a Domino pre-6.0.3 server
• Source database is full-text indexed and it is requested that the destination is not full-text indexed

In the preceding situations, the Administration Process generates a Create Replica request in the Administration Requests database of the source server.

Non-cluster move replica

Triggered by: Completion of the Check access for non-cluster move replica request.

Carried out on: Source server for the database.

Carried out: Immediately

Result: Creates a replica of the original database on the destination server. If the Activity Trends tool is not running on this source server, posts the Approve deletion of moved replica request. If Activity Trends is running on this source server, posts the administration request Maintain Trends database record.

Update replica settings

Triggered by: The administrator creating a new replica by replicating the source database to the destination database, where the database quota is not replicated to the destination database.

Carried out on: Destination server.

Carried out: Immediately

Result: Establishes updated replica settings on the new replica, the database quota field is reset to the same database quota as the source.

Change the server on which the agent runs

This request is generated only when there is an agent on the source server that needs to be signed by the destination server prior to running the agent.

Triggered by: The presence of an agent on the source server that must be signed by the destination server after the database is moved and can run on the destination server.

Carried out on: The destination server.

Carried out: Immediately

Result: If all access checks succeed, the agent is signed by the destination server and can be run according to normal processing.

Maintain Trends database record

Triggered by: Initiating the database move action as a result of resource balancing recommendations generated by the Activity Trends tool and successful completion of the Non-cluster move replica administration request.

Carried out on: The source server for the database being moved.

Carried out: Immediately

Result: Copies the database record from the source server to the destination server. If appropriate, it retires the database record on the source server.

Approve deletion of moved replica

Triggered by: Completion of the Non-cluster move replica request.

Carried out on: The Pending Administrator Approval View of the Administration Requests database, on any server. The deletion occurs on the source server.

Carried out: According to the administrator's discretion.

Result: Posts a Request to delete non-cluster move replicarequest.

Request to delete non-cluster move replica

Triggered by: Completion of the Approve deletion of moved replicarequest by the administrator's approval.

Carried out on: The administration server for the Domino Database.

Carried out: According to the Interval setting in the Administration Process section of the Server document.

Result: Posts a Delete non-cluster move replica request.

Delete non-cluster move replica

Triggered by: Completion of the Request to delete non-cluster move replica request.

Carried out on: Source server for the original database.

Carried out: According to the Interval setting in the Administration Process section of the Server document.

Result: Makes one last push replication of the source database to the destination server and deletes the original database from the source server.

Timing for move database from a non-cluster server