<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Working with Cluster Utilities on</title><link>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/</link><description>Recent content in Working with Cluster Utilities on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/index.xml" rel="self" type="application/rss+xml"/><item><title>RPAgent Control Script</title><link>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_rpagent_ctrl/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_rpagent_ctrl/</guid><description>&lt;p>The &lt;code>cluster_rpagentctrl.sh&lt;/code> script, in the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils&lt;/code> directory, manages the RPAgent services on all
the nodes in the cluster that are listed in the BDP hosts file.&lt;/p>
&lt;p>The utility provides the following options:&lt;/p>
&lt;ul>
&lt;li>Start – Starts the RPAgent on all the nodes in the cluster.&lt;/li>
&lt;li>Stop – Stops the RPAgent on all the nodes in the cluster.&lt;/li>
&lt;li>Restart – Restarts the RPAgent on all the nodes in the cluster.&lt;/li>
&lt;li>Status – Reports the status of the RPAgent on all the nodes in the cluster.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> While executing the RPAgent Control utility, the script will prompt to enter the path of the SSH private key file to securely login into the cluster nodes.&lt;/p></description></item><item><title>Log Forwarder Control Script</title><link>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_logfrwdr_ctrl/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_logfrwdr_ctrl/</guid><description>&lt;p>The &lt;code>cluster_logforwarderctrl.sh&lt;/code> script, in the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils&lt;/code> directory, manages the Log Forwarder services on all
the nodes in the cluster that are listed in the BDP hosts file.&lt;/p>
&lt;p>The utility provides the following options:&lt;/p>
&lt;ul>
&lt;li>Start – Starts the Log Forwarder on all the nodes in the cluster.&lt;/li>
&lt;li>Stop – Stops the Log Forwarder on all the nodes in the cluster.&lt;/li>
&lt;li>Restart – Restarts the Log Forwarder on all the nodes in the cluster.&lt;/li>
&lt;li>Status – Reports the status of the Log Forwarder on all the nodes in the cluster.&lt;/li>
&lt;/ul>
&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> While executing the Log Forwarder Control utility, the script prompt to enter the path of the SSH private key file to securely login into the cluster nodes.&lt;/p></description></item><item><title>Sync Config.ini</title><link>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_config_ini_sync/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_config_ini_sync/</guid><description>&lt;p>The &lt;code>sync_config_ini.sh&lt;/code> script in the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils/&lt;/code> directory, updates the &lt;code>config.ini&lt;/code> parameters across all the nodes in the cluster.
For example, to update the &lt;code>config.ini&lt;/code> file, edit the file on the Lead node and propagate the change to all the nodes in the cluster using the &lt;code>sync_config_ini.sh&lt;/code> script.&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Log in to the lead or the Primary node.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils/&lt;/code> directory.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>To replicate the &lt;code>config.ini&lt;/code> file from the lead node to all the nodes, run the following command:&lt;/p></description></item><item><title>Sync Log Forwarder Configuration</title><link>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_logfwrdr_sync/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_logfwrdr_sync/</guid><description>&lt;p>The &lt;code>sync_logforwarder.sh&lt;/code> script in the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils/&lt;/code> directory, updates the Log Forwarder configuration across the nodes in the cluster.
For example, to update the Log Forwarder configuration, edit the changes on the Lead node and propagate the change to all the nodes in the cluster using the &lt;code>sync_logforwarder.sh&lt;/code> script.&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Log in to the lead or the Primary node.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils/&lt;/code> directory.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>To replicate the RPAgent configuration from the lead node to all the nodes, run the following command:&lt;/p></description></item><item><title>Sync RPAgent Configuration</title><link>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_rpagent_sync/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/protectors/10.2/docs/bdp/bdp_amz_emr/working_with_cluster_utilities/bdp_emr_static_rpagent_sync/</guid><description>&lt;p>The &lt;code>sync_rpagent.sh&lt;/code> script in the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils/&lt;/code> directory, updates the RPAgent configuration and the
certificates across the nodes in the cluster.
For example, to update the RPAgent configuration, make the changes on the Lead node and propagate the change to all the nodes in the cluster using the &lt;code>sync_rpagent.sh&lt;/code> script.&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Log in to the lead or the Primary node.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Navigate to the &lt;code>&amp;lt;installation_directory&amp;gt;/cluster_utils/&lt;/code> directory.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>To replicate the RPAgent configuration from the lead node to all the nodes, run the following command:&lt;/p></description></item></channel></rss>