Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
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).
Setting up a cluster
Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
Creating replicas in a cluster
To create replicas in a cluster, you use the same Administration Process you would use to create replicas on any server.

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.
- 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).
  - Configuring a network
    This section presents the planning concepts and setup procedures necessary for a successful IBM® Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
  - Configuring users and servers
    Topics in this section describe how to set up users and servers.
  - Editing the NOTES.INI file
    You should rarely, if ever, need to modify a server's or client's NOTES.INI file. The NOTES.INI file contains many settings that Domino® and Notes® rely on to work properly. An accidental or incorrect change may cause Domino or Notes to run unpredictably. Therefore, you should edit the NOTES.INI file only if special circumstances occur or if IBM® Support Services recommends that you do so.
  - Configuring directory services
    This section describes how to plan, set up, and use IBM® Domino® directory services.
  - Configuring messaging
    This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
  - Configuring iNotes®
    IBM® iNotes® (previously IBM Domino® Web Access) provides IBM Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of IBM iNotes.
  - Configuring Web servers
    This section describes how to set up the IBM® Domino® Web server, the Domino Web Navigator, and other Web servers such as IBM HTTP.
  - Setting up a cluster
    Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
    - Creating a cluster
      A cluster is a group of application servers that you manage together as a way to balance workload. If possible, use the administration server when you create a cluster. This makes the creation process faster. The administration server does not have to be part of the cluster.
    - Verifying that the cluster was created correctly
      There are a number of ways you can check that the cluster was created correctly.
    - Managing user access to databases
      Users should have the same access rights in all replicas of a database in the cluster. Otherwise, if users fail over to a replica for which they have fewer access rights, they may be denied access, or they may not see the same documents or be able to perform the same functions as in the original database they were using.
    - Creating replicas in a cluster
      To create replicas in a cluster, you use the same Administration Process you would use to create replicas on any server.
    - Using symmetrical clusters
      A symmetrical cluster ensures that IBM® Notes® databases remain identical across all servers in a cluster. A repair service repairs missing or damaged databases by replacing them with good copies from donor cluster members.
    - Setting up mail in a cluster
      Mail routing fails over if the recipient's mail server is not available when the router attempts to deliver the mail. As long as the mail server is in a cluster, the router delivers the mail to another cluster server that contains a replica of the recipient's mail database. Thus, the recipient continues to receive mail.
    - Using scheduled replication in a cluster
      You should run standard replication on a regular basis. The number of times per day you run standard replication depends on how important it is for you to keep all replicas synchronized. In most cases, once or twice per day is sufficient. If it is absolutely critical to keeps data synchronized at all times, you may want to replicate every hour or two.
    - Replicating with all servers in a cluster
      An additional benefit of creating a cluster is that it can simplify your replication topology and increase the reliability and performance of replication. This is because you can set up a server outside the cluster to replicate with all the servers inside the cluster. You do this by creating a single Connection document that specifies the server outside the cluster as the source of replication and the cluster name as the destination of replication. Then, every database on the source server that has a replica in the cluster replicates. If the cluster contains more than one replica of a database, the source server replicates with only one of those replicas, and cluster replication propagates the changes to the other replicas in the cluster.
    - Enabling the display of cluster replication status messages
      You can tell the Cluster Replicator to display status messages on the server console.
    - Obeying database size quotas during cluster replication
      To make sure that replicas will be identical when users fail over, cluster replication ignores database size quotas by default. This makes cluster replication consistent with the router, which also ignores quotas by default. If you want cluster replication to obey database size quotas, follow these steps.
    - Using directory assistance in a cluster
      A server can use directory assistance to look up information in a directory other than its local primary Domino® Directory. The directory can be a remote LDAP directory or a local or remote replica of any of the following types of Domino directories: a secondary Domino Directory, an Extended Directory Catalog, or a primary Domino Directory. To configure directory assistance, you create a directory assistance database. This database contains information about directories on other servers and how to connect to them.
    - Setting up roaming servers in a cluster
      Configure a cluster of servers to support Notes® roaming users. Make sure that replicas of each user's roaming files are on at least two roaming servers in the cluster. When a user tries to access roaming files on a server that is not available, Domino® fails over to a different cluster server that has replicas of the user's roaming files.
    - Setting up cluster access for remote users
      You can give remote users the benefits of a cluster by setting them up to access the cluster through a pass-through server. The pass-through server can redirect the users to a different server in the cluster if the original server is busy or not available. Unless you use a pass-through server, users will have to dial each cluster server individually and will not fail over if the server they call is not available.
    - Using the Server Web Navigator in a cluster
      If you plan to use the Server Web Navigator in a cluster, be sure that the Web databases (WEB.NSF) on the cluster servers are replicas. Since the Web database is generated automatically when you start the Server Web Navigator, it is a common error for the clustered servers to contain Web databases that are not replicas of each other. Therefore, these databases do not fail over to each other.
    - Setting up a private LAN for a cluster
      Setting up a private LAN for your cluster separates the server probes and cluster replication from the rest of your network traffic. This prevents the cluster traffic from slowing down your primary network.
    - Clustering Domino® servers that run Internet protocols
      You can configure and use the Internet Cluster Manager (ICM) to extend the benefits of IBM® Domino® clusters to HTTP clients and Domino Web servers. You can also employ an alternative method of using failover with HTTP servers, as well as methods to use failover with POP3, IMAP, and LDAP servers.
- 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

Creating replicas in a cluster

To create replicas in a cluster, you use the same Administration Process you would use to create replicas on any server.

IBM® Domino® lets you use one procedure to create multiple replicas on multiple servers simultaneously. This makes it easy to populate the clusters with the replicas you want. While creating the replicas, you can select Show me only cluster members for cluster: cluster name in the Create Replica dialog box to see which servers are in each cluster. You can then create replicas on every cluster server you want.

Replicating unread marks

You should also determine which databases should replicate unread marks to other replicas in the cluster. When you replicate unread marks, every replica looks the same when a user fails over. The user cannot tell that failover occurred. In addition, unread marks help users track the status of documents. It is advisable to replicate unread marks in mail databases. However, replicating unread marks in very busy, multi-user databases might use enough processing power to have an effect on performance. Therefore, you should consider how important it is to replicate unread marks in these databases.

By default, databases do not replicate unread marks. Therefore, you should change the replication setting for databases that you want to replicate unread marks.