02. Create the Cluster (scenario 1)

Added by James A Riel | Edited by IBM contributor

Kristopher T Stoddard on July 19, 2009 | Version 5

Edit
More Actions ▼

Abstract

No abstract provided.

Tags: replica_stubs

< Previous | Contents | Next

To create a cluster, you must have the following access rights:

Author access and Delete Documents rights and the ServerModifier and ServerCreator roles in the IBM® Lotus® Domino™ Directory

Author access with Create documents rights in the Administration Requests database

If possible, use the administration server when creating a cluster. This makes the creation process faster. The administration server does not have to be part of the cluster.

If a server belongs to a different cluster, you do not have to remove the server from that cluster before you add it to the new cluster. The Cluster Administration Process removes the server from the original cluster and then adds it to the new cluster.

Note You cannot use the Web Administrator to create a cluster.

For complete instructions on creating a cluster, refer to Creating a cluster in the Lotus Domino 8.0.1 Administrator information center. You would need to repeat the steps detailed in the linked-to topic for each server you intend to add to the cluster.

Enable replication between all servers by adding the Lotus Domino servers you included in the cluster to the "Create databases&template" and "Create new replicas" fields of Server Access in each Server document's Security section.

Add the following attribute into the notes.ini file of all Quickr servers:
```
NoWebFileSystemACLs=1 

$QuickPlaceInCluster=1 
```

Before you can use a new Lotus Quickr server in an existing cluster, you must first replicate the place data from another Lotus Quickr server in the cluster. Create replica stubs for new places, rooms, and PlaceTypes/Templates. After the creation of new places, rooms, and PlaceTypes/Templates, use the qptool replicamaker command to create replica stubs for them on other servers in a cluster. Note that after creation of the replica stubs, cluster replication or standard replication must then replicate the new places, rooms, and PlaceTypes to populate them initially and then to keep them synchronized. The qptool replicamaker command does the following:
- Creates replica stubs for MAIN.NSF and CONTACTS1.NSF on the local server or another server when a place or PlaceType/Template is created.
- Makes a new copy of SEARCH.NSF on the local server or another server when a place is created.
- Creates replica stubs on the local server or another server for any new rooms. The qptool replicamaker command takes the following arguments:
```
-? Prints help on the command. 

-s sourceserver The name of one server involved with the replication.
If not specified, default is the local server. If you don't use -s, you
must use -t. 

-t targetserver  The name of another server involved with the
replication. If not specified, default is the local server. If you don't
use -t, you must use -s. 

-a Creates replica stubs for all new places, rooms, and PlaceTypes/Templates.


-p place(s) Creates replica stubs for a specific new place or stubs for
a space-separated list of new places. 

-pt placetype(s)Creates replica stubs for a specified PlaceTypes/Templates
or stubs for a space-separated list of PlaceTypes/Templates. 
```
  Note You cannot use XML input and output files with this command.
  
  To ensure that replica stubs of new places, rooms and PlaceTypes are created quickly and that replication then populates the places, rooms, and PlaceTypes/Templates quickly, perform the following steps:

Create Program documents in the Domino Directory that runs the qptool replicamaker command with the -a argument between the servers in a cluster every 10 minutes. If there are more than two servers in the cluster, you must use more than one Program document to run the qptool replicamaker command to ensure that replica stubs are created on all servers in the cluster.

Schedule non-cluster replication between all servers in the cluster to occur at least every 20 minutes, to compensate for any lags in cluster replication.

For more information on Program documents and on scheduling replication, see Using standard replication in the IBM Lotus Quickr 8.0.1 Administrator information center.

Note To configure qptool replicamaker to run in verbose mode, so that all activity and errors are logged to the server console to help identify any problems as they arise, use the notes.ini setting QuickPlaceStubMakerLogging=3.

To create replica stubs manually, enter the following command at the server console:
```
load qptool replicamaker arguments 
```

Examples of qptool replicamaker

To create replica stubs on the server Server2/Acme for the new place P1 on the local server, enter either of the following commands:

 
load qptool replicamaker -p P1 -t Server2/Acme 

>load qptool replicamaker -p P1 -s Server2/Acme

To create replica stubs on the local server, for the new place P1 on Server2/Acme, enter either of the following commands:

 
load qptool replicamaker -p P1 -t Server2/Acme 

>load qptool replicamaker -p P1 -s Server2/Acme

To create replica stubs on Server2Acme for all new places, rooms, and PlaceTypes created on the local server, and to create replicate stubs on the local server for all new places, rooms, and PlaceTypes on Server2/Acme, enter either of the following commands:

 
load qptool replicamaker -t Server2/Acme -a 

>load qptool replicamaker -s Server2/Acme -a

Perform the following steps to replicate place data from another Lotus Quickr server. When you are done, add the new server to the cluster, as described in Creating a clusterin the Lotus Domino 8.0.1 Administrator information center.

Start the new server.

Use the link to specify user directory, security, and other settings. These settings are specified on each server independently.

To prevent the use of this server during the data replication process, shut down the HTTP task by entering the following command at the server console:
```
tell http quit 
```

Enter the following command at the server console to create replica stubs for places in the cluster on the new server:
```
 
load qptool replicamaker -s remote_server_name -a 
```
where remote_server_name is the hierarchical name of a server in the cluster, for example, Server2/Acme.

Wait for the replicamaker command to finish running successfully. This step may take several minutes.

Enter the following command at the server console of the new server to use the Domino Replicator to replicate the data and initialize the replica stubs:
```
replicate remote_server_name 
```
where remote_server_name is the hierarchical name of the remote server specified previously, for example, Server2/Acme.

Wait for the Domino Replicator to finish. This step may take several hours, depending on the amount of data.

Enter the following command at the server console of the new server to start the HTTP task:
```
load http 
```

Optional: Enter the following command at the server console of the new server to create search indexes on the newly replicated places. Creating the indexes can take several hours, and can be done while the server is running. Or, wait for the updall task to run automatically at 2 AM.
```
load updall 
```