Restoring the Big Data Protector configuration

Before uninstalling the Big Data Protector from CDP PVC Base, restore the configuration parameters to their previous values. These parameters will vary depending on the CDP-PVC-Base services used. Protegrity now provides the set_unset_bdp_config.sh script to restore the configuration parameters.

Note: For more information about manually restoring the configuration parameters, refer to the table in Setting the Big Data Protector configuration.

To restore the Big Data Protector configuration using the helper script:

1. Log in to the master node of the cluster.

2. Navigate to the directory where you have installed the Big Data Protector.

3. To restore the configurations using the helper script, run the following command:

   ./set_unset_bdp_config.sh
   

4. Press ENTER.

   The prompt to enter the IP address of the Cloudera Manager server appears.

   Enter Cloudera Manager Server Node's Hostname/IP Address:
   

5. Enter the IP address of the master node.

6. Press ENTER.

   The prompt to enter the name of the cluster appears.

   Enter Cluster's Name:
   

7. Enter the name of the cluster.

8. Press ENTER.

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

   Enter Cloudera Manager's Username:
   

9. Enter the username.

10. Press ENTER.

    The prompt to enter the password appears.

    Enter Cloudera Manager's Password:
    

11. Enter the password.

12. Press ENTER.

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

    Checking Cluster's existence...
    
    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.:
    

13. To remove the configuration for the Big Data Protector, type 2.

14. Press ENTER.

    The script removes the configuration for the Big Data Protector.

    Checking existence of HBase service with name 'hbase'.
    
    Service 'hbase' exists.
    
    Unsetting HBase's config...    
    
    ######################################################################################################################################################################### 100.0%
    HBase's 'hbase_coprocessor_region_classes' config for Role Group 'hbase-REGIONSERVER-BASE' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    HBase's 'hbase_coprocessor_region_classes' config for Role Group 'hbase-REGIONSERVER-1' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    HBase's 'hbase_coprocessor_region_classes' config for Role Group 'hbase-REGIONSERVER-2' has been updated.
    
    Checking existence of Hive on Tez service with name 'hive_on_tez'.
    
    Warning: Unable to check existence of Hive on Tez service 'hive_on_tez'. Skipping this service...
    {
        "message" : "Service 'hive_on_tez' not found in cluster 'Protegrity'."
    }
    
    Checking existence of Tez service with name 'tez'.
    
    Service 'tez' exists.
    
    Unsetting Tez's config...
    
    ######################################################################################################################################################################### 100.0%
    Tez Service wide config ('tez.cluster.additional.classpath.prefix') has been updated.
    
    Checking existence of Impala service with name 'impala'.
    
    Service 'impala' exists.
    
    Unsetting Impala's config...
    
    ######################################################################################################################################################################### 100.0%
    Impala's 'IMPALAD_role_env_safety_valve' config for Role Group 'impala-IMPALAD-BASE' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    Impala's 'IMPALAD_role_env_safety_valve' config for Role Group 'impala-IMPALAD-2' has been updated.
    
    ######################################################################################################################################################################### 100.0%
    Impala's 'IMPALAD_role_env_safety_valve' config for Role Group 'impala-IMPALAD-1' has been updated.
    
    Checking existence of Spark on Yarn service with name 'spark_on_yarn'.
    
    Service 'spark_on_yarn' exists.
    
    Unsetting Spark on Yarn's config...
    
    ######################################################################################################################################################################### 100.0%
    Spark on Yarn Service wide config ('spark-conf/spark-env.sh_service_safety_valve') has been updated.
    
    Checking existence of Spark3 on Yarn service with name 'spark3_on_yarn'.
    
    Service 'spark3_on_yarn' exists.
    
    Unsetting Spark3 on Yarn's config...
    
    ######################################################################################################################################################################### 100.0%
    Spark3 on Yarn Service wide config ('spark3-conf/spark-env.sh_service_safety_valve') has been updated.