Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
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.
Cluster benefits and requirements
This section explains what an IBM® Domino® cluster is, how a cluster can benefit you, and the hardware and software requirements for setting up and using a cluster.

IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
- What's new in IBM® Domino® 10?
  Learn about all of the new features for administrators in IBM® Domino® 10.
- Overview
  Welcome to IBM® Domino® Administrator Help.
- Installing
  Use this documentation to install the IBM® Domino® server and subsequently deploy the IBM Notes® client.
- 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 IBM® 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
    IBM® Domino® provides a range of directory service features.
  - Planning a mail routing topology
    IBM® Domino® offers you considerable flexibility in configuring your mail system infrastructure, allowing you to use IBM 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 IBM® 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 IBM® 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 IBM® 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 IBM® 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 IBM® 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 to use the Internet Cluster Manager (ICM)
      Plan the cluster that the Internet Cluster Manager (ICM) will service. Then plan where to run the ICM itself and how many ICMs to run.
  - Planning the TCP/IP network
    The default TCP/IP configuration for an IBM® 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.
  - Planning the NetBIOS network
    The IBM® Domino® network is compatible with NetBIOS, a set of IBM session-layer LAN services that has evolved into a standard interface that applications use to access transport-layer network protocols.
  - Messaging overview
    The IBM® 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 IBM 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 IBM® 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.
- Configuring
  Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
- Securing
  This section describes IBM® Domino® security features, including execution control lists, IDs, and SSL.
- Administering
  This documentation provides information about the administration tools for managing and monitoring IBM Domino® servers and databases.
- Tuning
  Use this information to improve IBM® Domino® server, Domino Web server, and messaging performance through the use of resource balancing and activity trends, Server.Load commands, advanced database properties, cluster statistics, and the Server Health Monitor.
- Troubleshooting
  This section describes how to find and solve problems with IBM® Domino® server and Administrator client.
- Glossary

Cluster benefits and requirements

This section explains what an IBM® Domino® cluster is, how a cluster can benefit you, and the hardware and software requirements for setting up and using a cluster.

Server requirements are as follows:

All servers in a cluster must run on the Domino® Enterprise server or the Domino® Utility server
All servers in a cluster must be connected using a high-speed local area network (LAN) or a high-speed wide area network (WAN). You can also set up a private LAN for cluster traffic.
All servers in a cluster must use TCP/IP and be on the same Notes® named network
All servers in a cluster must be in the same Domino® domain and share a common Domino® Directory.
You must specify an administration server for the Domino® Directory in the domain that contains the cluster. If you do not specify an administration server, the Administration Process cannot change cluster membership. The administration server does not have to be a member of a cluster.
Each server in the cluster must have a hierarchical server ID. If any servers have flat IDs, you must convert them to hierarchical IDs to use them in a cluster.
A server can be a member of only one cluster at a time.
Each server must have adequate disk space to function as a cluster member. Because clusters usually require more database replicas, servers in clusters require more disk space than unclustered servers.
Each server must have adequate processing power and memory capacity. In general, clustered servers require more computer power than unclustered servers.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.