topic Re: Redundant Cluster Manager Synchronization in Splunk Enterprise

Redundant Cluster Manager Synchronization

earl-b — Fri, 08 Mar 2024 13:54:40 GMT

When adding a new cluster manager to redundant cluster manager cluster do I need to manually deploy the current manager-apps?

Re: Redundant Cluster Manager Synchronization

richgalloway — Fri, 08 Mar 2024 21:35:28 GMT

The standby CM will receive the apps after they have been sent to the indexers. If I understand the question correctly, that means you must manually deploy the cluster bundle as part of setting up CM Redundancy. See https://docs.splunk.com/Documentation/Splunk/9.0.8/Indexer/CMredundancy#Update_the_peer_nodes.27_configuration_bundle

Re: Redundant Cluster Manager Synchronization

earl-b — Fri, 08 Mar 2024 21:40:03 GMT

@richgalloway - thanks for the response. I just wanted to make sure that I understood correctly that the cluster bundle must be pushed to indexers before the redundant CMs get the settings.

Re: Redundant Cluster Manager Synchronization

richgalloway — Sat, 09 Mar 2024 01:14:31 GMT

That's my interpretation of what's in the manual.

Re: Redundant Cluster Manager Synchronization

Mitesh_Gajjar — Thu, 30 Jan 2025 06:52:52 GMT

Hi @earl-b ,

To achieve redundant cluster manager synchronization in a Splunk environment hosted on a Linux server, you can utilize the rsync utility. This tool will assist in syncing the primary cluster master's configuration to the standby cluster.

To manually run the synchronization, execute the following rsync command on the primary cluster master:

"rsync -avz --delete /path/to/source user@target_node_ip:/path/to/destination"

For automated configuration synchronization, you can employ the crontab utility. This allows you to schedule the rsync command to run at regular intervals, ensuring continuous synchronization between the clusters.