KB221178: How does the registry setting 'Cluster Synch Check Duplicate Cubes' work in a clustered environment in MicroStrategy

Introduction
When running Strategy Intelligence Server 9.4.1 and 10.x in maintenance mode, it is recommended for users to enable the setting Cluster Synch Check Duplicate Cubes through the Windows registry or through the MSIReg.reg file on UNIX/Linux operating systems. Refer to the following Strategy Knowledge Base document for additional information on maintenance mode and the required/recommended settings.
KB45399 : New Feature in Strategy 9.3.1: Maintenance Mode: Ability to retain Intelligent Cubes, Caches and History List on 'Normal Shutdown' of a server node in an Intelligence Server cluster.
Note: KB45399 also applies for Strategy 10.x versions.
 
The purpose of the 'Cluster Synch Check Duplicate Cubes' registry setting is explained below:

• Consider a 2-node Strategy Intelligence Server 9.4.1/10.x cluster
• Publish intelligent cube 'Intelligent Cube - Geography' on Node1 of the cluster
• Enable maintenance mode on both the nodes by just adding the registry entry for 'MaintenanceModeEnabled' and setting the value to 1.
• Shutdown Node 1 of the cluster.
• Since maintenance mode is enabled, the cube published on Node 1 is still available for use on Node 2.
• Now, publish the same intelligent cube from step 2 on Node 2. Two copies of the cube are now seen on Node 2. This is as expected. This is because Node 1 is down, Node 2 cannot inform Node 1 to delete its copy of the cube.
  
  

• Now, restart Node 1. In this case, 2 copies of the cube are still seen on Node 1.
• This is because the registry setting 'Cluster Synch Check Duplicate Cubes' was not enabled. If the setting was enabled along with the 'MaintenanceModeEnabled' setting, Node 1 checks for duplicate copies upon restart and deletes the duplicate entry. In a case where the 'Cluster Synch Check Duplicate Cubes' was enabled, upon restart, only one copy of the cube will be visible on Node1 (as well as Node 2), as Node1 will delete its entry after checking that there is a duplicate cube on the other node.