Number of Cluster Members|0Consistent Domain Membership|1Consistent Protocols|2Required Server Tasks|3Consistent Server Web Navigators|4Consistent ACLs|5Replication Enabled|6Consistent Replication Formulas|7Replicas Exist Within Cluster|8
Test Result:
TestResult
TestResult
Pass|1Fail|0
Source
Destination
Source Database:
SourceDB
0S0E
SourceDB
Destination Database:
DestinationDB
0S0E
DestinationDB
TestName
TestName
3S4S
Source Server:
Source
0S0E
Source
Destination Server:
Destination
0S0E
Destination
TestName
1S2S
Fomula Detail:
TestName
1S2S
ACL Detail:
TestName
TestName
1S2S3S4S5S6S
SourceTextDetail
SourceTextDetail
Formula Detail:
ACL Detail:
DestTextDetail
DestTextDetail
Description
Description:
Description
Description
Categori_zes
_Edit Document
Send Docu_ment
_Forward
_Move To Folder...
_Remove From Folder_
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
Fde!f^^
$TITLE
$Info
$WindowTitle
$$Script_O
$$ScriptName
$Body
$ACTIONS
Times New Roman
Using Cluster Analysis
Viewing the results of a Cluster Analysis
Three views are provided in the Cluster Analysis database.
Views
By Cluster -- Categorizes documents by the name of the cluster tested.
By Date -- Categorizes documents by the date the reported event occurred.
By Test -- Categorizes documents by the type of test performed.
Each document in the Cluster Analysis database contains the following information:
Basics
Contains information for the following fields:
Date
-- Date when the cluster analysis was run.
Time
-- Time when the cluster analysis was run.
Server Name
-- Name of the server on which the cluster analysis was run.
Cluster Name
-- Name of the cluster tested.
Test Performed
-- Name of the specific test performed on the cluster.
Test Result
-- Results of the test performed. This value is either Pass or Fail.
Source
May contain
information for one or both of the following fields, depending on the test run:
Source Database
-- Name of the first database used in a comparison.
Source Server
-- Name of the first server used in a comparison. This is usually the server selected to run the Cluster Analysis from the Administration Panel.
Destination
May contain information for one or both of the following fields, depending on the test run:
Destination Database
-- Name of the second database used in a comparison.
Destination Server
-- Name of the second server used in a comparison.
Description
May contain additional information about the results of the specific test (optional).
Basic
Server Tests
Number of cluster members
This test checks the number of servers defined in the cluster. The actual status of the servers are not considered. The test reports a failure if the number of servers in the cluster exceeds the maximum allowed.
One report document is created for the cluster being analyzed. The report document contains the following information:
Number of servers defined in the cluster
Consistent domain membership
This test checks that all servers in the cluster belong to the same Notes domain. The test verifies that the Address Books on each server in the cluster have consistent replica IDs. The test reports a failure for each case where two servers are found to have inconsistent Address Books.
One report document is created for each failure detected. Each report document contains the following information:
The name of the server on which the Address Book resides (in the Server Name field and Source Server field)
The path name of the Address Book on the source server (in the Source Database field)
The name of the server on which no replica of the source server's Address Book resides (in the Destination Server field)
Consistent protocols
This test checks that each server in the cluster can be accessed on each protocol running on the client from which the test is executed. The test reports a failure for any protocol for which some but not all cluster servers can be accessed. (Note that this test uses information from the Server documents in the Public Address Book to determine which protocols are available on each server -- it does not actually attempt to access the servers, and thus does not report a failure for servers that are unavailable at the time the test is run.)
One report document is created for each failure detected. Each report document contains the following information:
A server in the cluster that can be reached on the specified protocol (in the Server Name field and the Source Server field)
The server that cannot be reached (in the Destination Server field)
The protocol on which the server was not accessible
For each protocol checked, if no failures are detected (i.e. all servers in the cluster can be accessed over the protocol), a report document is created indicating the protocol passed this test.
Required server tasks
This test checks the ServerTasks NOTES.INI setting on each server in the cluster to verify that it includes CLDBDIR, CLREPL, ROUTER, and UPDATE. The test reports a failure for a particular server if any of these tasks is missing from the ServerTasks setting. Failures could also occur if the destination server is down, or if the user does not have sufficient authority to issue remote console commands for the server. (This test does not verify that the required server tasks are actually running on the servers in the cluster.)
One report document is created for each failure detected. Each report document contains the following information:
The server that does not have the required server tasks defined to start at server startup (in the destination server field)
A list of the specific task names not found in the server's ServerTask NOTES.INI setting.
If no failures are detected (i.e. all servers in the cluster are running the required server tasks), a report document is created indicating that all servers passed this test.
Database Tests
Replicas exist within cluster
This test checks that each database in the cluster has another replica on another server in the cluster. The test reports a failure for each database that does not have at least one other replica on another server in the cluster.
One report document is created for each failure detected. Each report document contains the following information:
The name of the server on which the database resides (in the Server Name field)
The path name of the database for which no other replicas exist in the cluster (in the Source Database field)
Consistent ACLs
This test checks all replica databases within the cluster to see whether ACLs are identical across replicas. The test reports a failure for each case where matching ACLs cannot be confirmed on a pair of replica databases. Failures could occur because the user running the analysis does not have sufficient authority to view the ACL for a database.
One report document is created for each failure detected. Each report document contains the following information:
The name of the server on which the one replica resides (in the Server Name field and Source Server field)
The path name of the replica on the source server (in the Source Database field)
The name of the server on which the other replica resides (in the Destination Server field)
The path name of the replica on the destination server (in the Destination Database field)
The ACL entry in the source database that was found to be inconsistent with the destination database (in the Description field)
The ACL component (Level or Flags) found to be inconsistent (also in the description field)
The values of the ACL component for the source and destination databases (in the corresponding ACL Detail fields)
Disabled replication
This test checks all replica databases within the cluster to see if replication has been disabled (i.e., through Replication Settings, Other, "Temporarily disable replication"). Disabling replication for a database disables all forms of replication, including cluster replication. The test reports a failure for each database for which replication has been disabled. Failures could occur because the user running the analysis does not have sufficient authority to view the replication settings for a database.
One report document is created for each failure detected. Each report document contains the following information:
The name of the server on which the database resides (in the Server Name field)
The path name of the database for which replication is disabled (in the Source Database field)
Consistent replication formulas
This test checks all replica databases within the cluster to see whether selective replication formulas are consistent across replicas. The test verifies that when a replication formula only applies to a specific server, and that server is a member of the cluster, that all replicas of the database contain an equivalent replication formula for this server. The test reports a failure for each case where consistent replication formulas cannot be confirmed on a pair of replica databases. Failures could occur because the user running the analysis does not have sufficient authority to view the replication formulas for a database.
One report document is created for each failure detected. Each report document contains the following information:
The name of the server on which the one replica resides (in the Server Name field and Source Server field)
The path name of the replica on the source server (in the Source Database field)
The name of the server on which the other replica resides (in the Destination Server field)
The path name of the replica on the destination server (in the Destination Database field)
A description of the inconsistency detected, which is either:
No matching replication formula was found: indicates that the source database contains a selective replication formula but the destination database does not, or
Replication formulas not equivalent: indicates that both the source and target database contain a selective replication formula, but the formulas are not equivalent
For failures in which the replication formulas are not equivalent, the formulas from the source and destination database (in the Formula Detail fields)
Web Navigator Tests
This test checks that all Web Navigator databases in cluster are replicas. It checks each server in the cluster for a WEB.NSF -- if more than one WEB.NSF is found, the replica IDs of these databases are compared. The test reports a failure if two WEB.NSF databases are found that do not have the same replica id.
One report document is created for the cluster being analyzed. The report document contains the following information:
The name of the server on which one Web Navigator database resides (in the Server Name field and Source Server field)
The name of the server containing another Web Navigator database which is not replica (in the Destination Server field)
O=Lotus Notes
O=Lotus Notes
PURSAFO
|.:#U
O=Lotus Notes
CN=Lotus Notes Template Development/O=Lotus Notes
PURSAFO
$Info
$Body
Times New Roman
About Cluster Analysis
A Cluster Analysis database contains documents that record the results of Cluster Analysis tests. By default, Domino writes the analysis results to the Cluster Analysis database on the local computer. When you set up an analysis, you can specify another database by clicking Results Database. At the time the analysis is run, the administrator may choose to analyze Servers, Databases, and/or Server Web Navigator databases in the cluster. The following describes the tests performed for each of these choices:
Server
Number of cluster members
-- Checks the number of servers in the cluster
Consistent domain membership
-- Checks that all servers are members of the same domain
Consistent protocols
-- Checks that servers are running consistent protocols
Required server tasks
-- Checks that the required cluster tasks are running
Database
Replicas exist within cluster
-- Checks databases for replicas in the cluster
Consistent ACLs
-- Checks that access control lists are consistent among replicas
Disabled Replication
-- Checks databases for disabled cluster replication
Consistent replication formulas
-- Checks for inconsistent replication formulas among replicas
Server Web Navigator
This test checks that the Web databases on multiple cluster members are replicas.
For more detail on the checks performed and the corresponding report documents, see the Using this Database document.
(.txt)