Move database from a cluster server

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 for move replica creation

Triggered by: Choosing Database > Move from the tools pane.

Carried out on: The source server.

Carried out: Immediately

Result: The Administration Process checks that the administrator initiating the request has Manager with Delete documents access to the database being moved and that the destination server has Reader access to the database being moved.

Move replica

Triggered by: Completion of the Check Access for move replica creation request.

Carried out on: The destination server (the server to which the database is being moved).

Carried out: Immediately

Result: The Administration Process checks that the administrator and the source server have Create Replica access to the destination server. If so, the Administration Process creates a replica. The replica is populated with documents the first time any server with the complete replica replicates with the destination server. If the Activity Trends tool is running on the source server, posts the administration request Maintain Trends database record. If Activity Trends is not running on the source server, posts the administration request Monitor replica stub.

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 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.

Monitor replica stub

Triggered by: Creation of the replica on the destination server.

Carried out on: The destination server.

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

Result: The Administration Process monitors the replica. When it detects that the replica is initialized (another server has begun replicating to it), it posts a Delete original replica after move request.

Delete original replica after move

Triggered by: Completion of the Monitor replica stubrequest.

Carried out on: The source server.

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

Result: The Administration Process marks the original database for deletion. The Cluster Database Directory Manager on the source server then monitors the database for usage. When all user connections to the database have closed, the Cluster Database Directory Manager pushes changes to another replica in the cluster and deletes the database.

Timing for move database from a cluster server