The detailed instructions for upgrading a standalone CIS server are provided in the following video:
Source Server: OES 2018 SP3 or OES 2023.
Ensure that the CIS server is upgraded to OES 23.4.
Follow the step-by-step instructions for upgrading to OES 23.4 server. For more information, see Upgrading OES in the OES 23.4: Installation Guide.
If CIS is configured on /root, /home or /media/nss/VOL1 (non-clustered), the path is mounted.
If CIS is configured on a cluster volume (for example, /media/nss/CLUS_VOL), then verify if the cluster volume is mounted. If not, then mount the cluster volume manually.
Ensure the configurationStatus.json and status.json file is available in the /etc/opt/novell/cis/ folder.
Verify if key-value pair "cisConfigSuccess": true is present in both the files. Do not proceed if this is not available contact OpenText for further information.
Execute the following command to upgrade the CIS services:
sh /opt/novell/cis/bin/cis_upgrade.sh
On successful execution of upgrade script, a few of the CIS services are stopped.
Ensure that the database configured for CIS is up and running.
If it is a local database, verify the status of the database service:
systemctl status mysql.service
If the database is down, then enable and restart it:
systemctl enable mysql.service
systemctl restart mysql.service
Verify the status of the CIS Infra services. If not running, then start the services.
/root or /home or /media/nss/VOL1 (non clustered):
systemctl status oes-cis-zk.service oes-cis-opensearch.service oes-cis-kafka.service
Start the logging and configuration services.
systemctl start oes-cis-fluentbit.service oes-cis-configuration.service
Start the Core services.
systemctl restart oes-cis-server.target
Ensure all the CIS services are running, by executing the following command:
docker ps -a
This displays the status of all the CIS services.
Verify the health of the CIS server.
cishealth
When the status displays “Healthy”, then the CIS server is successfully upgraded.
NOTE:The upgrade takes time to complete depending on the size of the database getting migrated from the earlier version of OES server. During this phase, the CIS health might display the status of some services as “Not Healthy” because the scanned data is getting updated. On completing the update, the health status changes to “Healthy”.
Restart the agent services.
systemctl restart oes-core-agent.service oes-dashboard-agent.service oes-cis-agent.service oes-cis-recall-agent.service oes-cis-scanner.service
systemctl status oes-core-agent.service oes-dashboard-agent.service oes-cis-agent.service oes-cis-recall-agent.service oes-cis-scanner.service
The CIS Admin Console's Insights and Dashboard pages are not displaying any data since elasticsearch stores the data of these pages.
To transfer the data from Elasticsearch to OpenSearch, complete the following steps:
Ensure to have completed procedure mentioned in Section 5.1.2, Upgrading to OES 23.4 Server.
NOTE:(Conditional) If CIS is configured on a cluster volume (for example, /media/nss/CLUS_VOL), then verify if the cluster volume is mounted. If not, then mount the cluster volume manually.
Verify the status of the Elasticsearch. If not running, restart the service.
systemctl status oes-cis-elastic.service
systemctl restart oes-cis-elastic.service
Verify the health of CIS.
cishealth
Before proceeding ensure CIS is healthy.
Move data from the Elasticsearch to OpenSearch:
sh /opt/novell/cis/bin/elastic_move_data.sh migrate
You can verify the logs at
/var/opt/novell/log/cis/cis_opensearch_move__<timestamp>.log
NOTE:The duration of the migration can be prolonged depending on the data saved in Elasticsearch.
Verify the data migration count.
sh /opt/novell/cis/bin/elastic_move_data.sh verify
On successfully transferring the data, the Insights and Dashboard pages of the CIS Admin Console will populate the existing data.
Cleanup the Elasticsearch data.
sh /opt/novell/cis/bin/elastic_move_data.sh cleanup
/media/nss/CLUS_VOL (clustered volumes): Replace the oes-cis-elastic.service with the oes-cis-opensearch.service in the Load, Unload, and Monitor script. For more information, see Modifying the Load, Unload, and Monitor Scripts. This ensures all the required services start on bringing the resource online.