This KB article help SVM on-premise customers with how they can recover the SVM on-premise database from backup.
The SVM database got corrupt due to any of the reasons below.
Can't log in to the SVM console via IE with the connection failed error.
The csi7 user has been deleted
The SVM private DB user has been modified
The Linux security modules have been updated
The Linux MySQL server version has been changed or updated.
Login to SVM on-premise Linux server and stop the Scandaemon and sgdaemon service.
service sgdaemon stop service scandaemon stop
Login to the SVM database
MySQL -u root -p
Drop the ca and ca_custid databases
Show databases; drop database ca; drop database ca_custid; drop database ca_custid_1; ( Only applicable if customer have multiple SVM partitions ) Flush privileges;
Create the ca and ca_custid databases
create database ca; create database ca_custid; create database ca_custid_1; ( Only applicable if customer have multiple SVM partitions ) Flush privileges; exit
Go to the SVM on-premise server backup location and unzip the backup files you want to recover the database from.
cd /usr/local/Secunia/csi/backup gunzip ca_backup_30-10-20.sql.gz gunzip ca_custid_backup_30-10-20.sql.gz gunzip ca_custid_1_backup_30-10-20.sql.gz ( Only applicable if customer have multiple SVM partitions )
Recover the SVM on-premise database from the unzipped database files
MySQL -u root -p ca < ca_backup_30-10-20.sql; MySQL -u root -p ca_custid < ca_custid_backup_30-10-20.sql; MySQL -u root -p ca_custid_1 < ca_custid_1_backup_30-10-20.sql;
Run the installation process from the SVM install directory
cd /usr/local/Secunia/csi/install/ ./installationProcess.sh ( Would you like to go through the configuration process where you can review/edit the settings? (Y/N) > choose N and proceed with the wizard)
Start the Scandaemon and sgdaemon service
service sgdaemon start service scandaemon start Please try to login to your SVM console via IE.
Nov 27, 202004:29 AM - edited Dec 01, 202003:24 AM