nci_export

Edit online

The nci_export tool exports data source, data type, service, policy, and project information from an instance of the Impact server to a specified directory. The exported data can then be transferred to another Impact server and imported using nci_import.

About this task

To export data from Impact on cloud, the Impact server (nciserver) must be scaled down to 1. If your nciserver is already scaled to 1 server, you can skip to Step 4.

Procedure

Scale nciserver to zero:

oc scale sts <release name>-nciserver --replicas=0

Edit the stateful set and set NCISERVERS_REPLICA_COUNT to 1:
```
oc edit sts <release name>-nciserver
```

Scale nciserver to 1:

oc scale sts <release name>-nciserver --replicas=1

Wait for nciserver-0 to restart, then log into nciserver:
```
oc rsh <release name>-nciserver-0
```
Go to the Impact home directory:
```
cd /opt/IBM/tivoli/impact/
```
Run the export command:
```
./bin/nci_export NCI_0 /tmp/nci_0_export
```
Note: If you changed the Impact instance name, replace NCI in the command with your instance name. For example, if the instance name is PRI, the export will be for PRI_0.
The export results will be in the /tmp/nci_0_export directory.
From outside the nciserver pod, copy the data:
```
oc rsync <release name>-nciserver-0:/tmp/nci_0_export <local path>/nci_0_export
```
If you had nciserver scaled to more than one server, edit the nciserver stateful set and set NCISERVERS_REPLICA_COUNT to the desired number:
```
oc edit sts <release name>-nciserver
```

Scale nciserver to the NCISERVERS_REPLICA_COUNT value:

oc scale sts <release name>-nciserver --replicas=<number>