Home
Planning
Use this topic as an overview of planning task.
Planning a cluster
When planning a cluster, it is important to consider the performance and ability of your hardware. The cluster must have enough CPU power, memory, and disk space to handle the cluster traffic and the number of databases and replicas required.
Determining whether to create a private LAN for your cluster
To make a busy cluster more efficient, you can create a private network for your cluster. To do so, you install an additional network interface card in each cluster server and connect these network interface cards through a private hub or switch.

Planning
Use this topic as an overview of planning task.
- Roadmap for deploying Domino® servers
  Use this as a tool when planning how to integrate HCL Domino® into your existing environment.
- Planning server-to-server connections
  Servers must connect to each other to exchange data, for example to replicate databases and exchange mail. You can create connections between servers across a local area network (LAN) or wide area network (WAN), by using a pass-through server (a server that acts as an intermediary server between a client and its destination), or over the Internet. Create a Server Connection document whenever you need to establish any new or additional server connections. You can modify this document when necessary.
- Planning directory services
  HCL Domino® provides a range of directory service features.
- Planning a mail routing topology
  HCL Domino® offers you considerable flexibility in configuring your mail system infrastructure, allowing you to use HCL Notes® routing, SMTP routing, or both, for internal and external messages.
- Planning a cluster
  When planning a cluster, it is important to consider the performance and ability of your hardware. The cluster must have enough CPU power, memory, and disk space to handle the cluster traffic and the number of databases and replicas required.
  - What is a Domino® cluster?
    An HCL Domino® cluster is a group of two or more servers that provides users with constant access to data, balances the workload between servers, improves server performance, and maintains performance when you increase the size of your enterprise. The servers in a cluster contain replicas of databases that you want to be readily available to users at all times. If a user tries to access a database on a cluster server that is not available, Domino opens a replica of that database on a different cluster server, if a replica is available. Domino continuously synchronizes databases so that whichever replica a user opens, the information is always the same.
  - Cluster benefits and requirements
    This section explains what an HCL Domino® cluster is, how a cluster can benefit you, and the hardware and software requirements for setting up and using a cluster.
  - How Domino® clustering works
    This section explains how HCL Domino® clustering works for Notes® clients and Domino servers. This section also describes operating system clusters and how Domino clusters work in conjunction with operating system clusters.
  - Determining how many Domino® servers to include in a cluster
    Adding HCL Domino® servers to the cluster increases the cluster's ability to balance the workload so that no server becomes overloaded and performance stays high. However, if servers use too many server tasks, CPU-intensive applications, and replicas, adding servers can decrease performance because of the additional amount of cluster traffic required to keep databases synchronized on all servers.
  - Determining the number and placement of replicas in a cluster
    There are two major reasons to create a replica for a database in a cluster -- to provide constant availability of the data and to distribute the workload between multiple servers. Before you create replicas in a cluster, consider how frequently users access a database and their need for data redundancy. If a database is extremely busy or its availability is extremely important, create multiple replicas and locate them on your most reliable servers. For databases that are not very busy and whose constant availability is not important, you may not want to create any replicas at all. A server log file, for example, does not need to have a replica on another server.
  - Distributing databases in a cluster
    The way you distribute databases significantly affects workload balancing, as well as the performance of your equipment.
  - Determining whether to create a private LAN for your cluster
    To make a busy cluster more efficient, you can create a private network for your cluster. To do so, you install an additional network interface card in each cluster server and connect these network interface cards through a private hub or switch.
  - Clustering over a wide area network
    A cluster over a wide are network (WAN) works the same way as a cluster on a LAN. However, if you have a low-speed WAN, you should consider disabling cluster replication. Instead, use scheduled replication more frequently than usual, such as every hour. This reduces WAN traffic, bottlenecks, and the cost of continual transmission.
  - Fault recovery in a cluster
    Fault recovery is the ability of an HCL Domino® server to clean up and restart itself after a failure. Fault recovery works well in a Domino cluster. If there is no Domino server to fail over to, fault recovery still ensures that users will have constant access to their data. Even if users fail over to another cluster server, fault recovery increases availability because the failed server becomes available again. In addition, depending on the workload balancing parameters you've set, some users will fail back to the original server when they open new databases.
- Planning the TCP/IP network
  The default TCP/IP configuration for an HCL Domino® server is one IP address that is globally bound, meaning that the server listens for connections at the IP addresses of all NICs on the computer. Global binding works as long as the computer does not have more than one IP address offering a service over the same assigned TCP port.
- Messaging overview
  The HCL Domino® mail system has three basic components: Domino mail servers, Domino mail files, and mail clients. The Domino mail server is the backbone of an organization's messaging infrastructure, acting both as an Internet mail server and an HCL Notes® mail server. Domino provides standards-based Internet messaging through its support of the Simple Mail Transfer Protocol (SMTP), Post Office Protocol version 3 (POP3), Internet Message Access Protocol (IMAP), and Multipurpose Internet Mail Extensions (MIME). At the same time, Domino supports Notes mail through the use of Notes routing protocols -- Notes remote procedure calls (NRPC) -- and the Notes rich text message format.
- Planning your Notes® client deployment
  Use the references listed here to plan for, install, upgrade to, and configure the HCL Notes® client.
- Planning security
  An important aspect of planning security for your Domino® environment is understanding the tasks and features involved with securing each type of resource.

Determining whether to create a private LAN for your cluster

To make a busy cluster more efficient, you can create a private network for your cluster. To do so, you install an additional network interface card in each cluster server and connect these network interface cards through a private hub or switch.

The main reason for creating a private LAN for your cluster is to separate the network traffic a cluster creates when it uses cluster replication and server probes. A private LAN can leave more bandwidth available on your primary LAN. If you anticipate a lot of cluster replication activity, create a private LAN.

You can also consider creating a private LAN for intra-cluster communication to ensure that cluster servers remain in communication with each other, even when certain network problems occur. By adding a private network, all servers in the cluster are connected by at least two distinct LAN segments. So if a network board or a cable on one LAN segment fails, there is still network connectivity between all servers in the cluster. This assures you that cluster servers remain in contact with each other and that cluster replication continues to keep databases synchronized.

If you create a private LAN for your cluster, all cluster members must be connected to both the private LAN, for intra-cluster communication, and the primary LAN, for client access.