Restoring the Parameters using the Helper Script

Before uninstalling the Big Data Protector, restore the configuration parameters. These parameters will vary depending on the services in use. Protegrity now provides the set_unset_bdp_config.sh script to restore the configuration parameters for the required services.

To set the paramters using the helper script, refer Setting the Parameters using the Helper Script.

To restore the Big Data Protector configuration:

Log in to the staging machine.
Navigate to the directory where you executed configurator script and generated the installation files.
To restore the configurations using the helper script, run the following command:
```
./set_unset_bdp_config.sh
```

Press ENTER.

The prompt to enter the protocol for the Cloudera Manager server appears.

Select the Cloudera Manager URL Protocol.
[ 1 ] : http://
[ 2 ] : https://
Enter the no.:

To use https, type 2.
Press ENTER.
The prompt to enter the IP address of the Cloudera Manager server appears.
```
Enter Cloudera Manager Server Node's Hostname/IP Address:
```
Enter the IP address of the node where the Cloudera Manager Server is installed.
Press ENTER.
The prompt to enter the port number for the Cloudera Manager server appears.
```
Enter Cloudera Manager Server's Port No. [7183]:
```
Note: For https, the script will use 7183 as the default port and for http, the script will use 7180 as the default port.
Press ENTER.
The prompt to enter the name of the cluster appears.
```
Enter Cluster's Name:
```
Enter the name of the cluster.
Press ENTER.

The prompt to enter the username to access Cloudera Manager appears.

```
Enter Cloudera Manager's Username:
```

Enter the username.
Press ENTER.
The prompt to enter the password appears.
```
Enter Cloudera Manager's Password:
```
Enter the password.

Press ENTER.

The script verifies the cluster details and the prompt to set or remove the configuration appears.

Cluster's existence verified.

Do you want to set or unset the BDP configs?
[ 1 ] : SET the BDP configs
[ 2 ] : UNSET the BDP configs
Enter the no.:

To restore the configuration for the Big Data Protector, type 2.

Press ENTER.

The script updates the configuration for the Big Data Protector.

Checking existence of HBase service with name 'hbase'.
##O=#    #
Warning: Unable to check existence of HBase service 'hbase'. Skipping this service...
{
"message" : "Service 'hbase' not found in cluster <cluster_name>."
}

Checking existence of Hive on Tez service with name 'hive_on_tez'.
##O=#    #
Service 'hive_on_tez' exists.

Unsetting Hive on Tez's config...
##O=#    #
##O=#    #
############################################################################################################################## 100.0%
Hive on Tez Service wide configs ('HIVE_ON_TEZ_service_env_safety_valve' and 'hive_service_config_safety_valve') have been updated.
##O=#    #
##O=#    #
############################################################################################################################## 100.0%
Hive on Tez's 'hive_client_env_safety_valve' config for Role Group 'hive_on_tez-GATEWAY-BASE' has been updated.

Checking existence of Tez service with name 'tez'.
##O=#    #
Service 'tez' exists.

Unsetting Tez's config...
##O=#    #
############################################################################################################################## 100.0%
Tez Service wide config ('tez.cluster.additional.classpath.prefix') has been updated.

Checking existence of Impala service with name 'impala'.
##O=#    #
Warning: Unable to check existence of Impala service 'impala'. Skipping this service...
{
"message" : "Service 'impala' not found in cluster <cluster_name>."
}

Checking existence of Spark3 on Yarn service with name 'spark3_on_yarn'.
##O=#    #
Service 'spark3_on_yarn' exists.

Unsetting Spark3 on Yarn's config...
##O=#    #
############################################################################################################################## 100.0%
Spark3 on Yarn Service wide config ('spark3-conf/spark-env.sh_service_safety_valve') has been updated.

Feedback

Was this page helpful?

Last modified : February 20, 2026