Purging hot storage data

Guardium® Insights provides a gi_data_purge.sh script that allows you to purge data that is no longer being analyzed.

Before you begin

The gi_data_purge.sh script is supported on machines that are configured with the appropriate hardware cluster requirements - the script must be run on machines that support kubectl and oc commands.

Use the cpctl utility to download the gi_data_purge.sh script. For more information, see Downloading support scripts

Procedure

Make the gi_data_purge.sh script executable by issuing chmod +x gi_data_purge.sh.
Ensure that you are logged in to the IBM Cloud® Private command line interface. This also ensures that you are authenticated to the OpenShift® command line interface. Use this command to log in:
```
cloudctl login -a <ICP_hostname> -u <openshift_username> -p <openshift_password> --skip-ssl-validation
```
where
- <ICP_hostname> is your Cloud Private server, for example https://cp-console.apps.myserver.com
- <openshift_username> is your OpenShift user name
- <openshift_password> is your OpenShift password
When prompted, choose the Guardium Insights OpenShift namespace that you created when preparing your environment.
Tip: You can check the list of namespaces currently deployed on the cluster by running this command:
```
kubectl get namespace
```
If you specify the incorrect namespace when prompted, you can correct the namespace by issuing this command:
```
oc project <guardium_insights_namespace>
```
where <guardium_insights_namespace> is the Guardium Insights OpenShift namespace that you created when preparing your environment.
Run the script as follows:
```
gi_data_purge.sh <tenant_id> <timestamp_utc>
```
where
- <tenant_id> is your Guardium Insights account (or tenant ID), as described here.
- <timestamp_utc> is the timestamp that determines the data to be purged. All data that is older than the timestamp that you provide will be purged.