After the appliance is set up and running, no more manual interaction is required. This way of setting up the appliance is therefore ideal for using cron jobs to create and upload supportconfig archives.

1. On the machine on which to install the appliance, log in to a console and execute the following commands:

   zypper install sca-appliance-* sca-patterns-* vsftpd
   systemctl enable apache2.service
   systemctl start apache2.service
   systemctl enable vsftpd.service
   systemctl start vsftpd.service
   yast ftp-server

2. In YaST FTP Server, select Authentication › Enable Upload › Anonymous Can Upload › Finish › Yes to Create /srv/ftp/upload.

3. Execute the following commands:

   systemctl enable mysql.service
   systemctl start mysql.service
   mysql_secure_installation 
   setup-sca -f

   The mysql_secure_installation will create a MariaDB root password.

This way of setting up the appliance requires manual interaction when typing the SSH password.

1. On the machine on which to install the appliance, log in to a console.

2. Execute the following commands:

   zypper install sca-appliance-* sca-patterns-* 
   systemctl enable apache2.service 
   systemctl start apache2.service
   sudo systemctl enable mysql.service
   systemctl start mysql.service
   mysql_secure_installation 
   setup-sca

1. For Apache and MariaDB, install the Web and LAMP installation patterns.

2. Set up Apache, MariaDB, and optionally an anonymous FTP server.

3. Configure Apache and MariaDB to start at boot time:

   sudo systemctl enable apache2.service mysql.service

4. Start both services:

   sudo systemctl start apache2.service mysql.service

After installing the packages, use the setup-sca script for the basic configuration of the MariaDB administration and report database that is used by the SCA appliance.

It can be used to configure the following options you have for uploading the supportconfig archives from your machines to the SCA appliance:

1. Install the appliance and the SCA base-pattern library:

   sudo zypper install sca-appliance-* sca-patterns-base

2. Additionally, install the pattern packages for the types of supportconfig archives you want to analyze. For example, if you have SUSE Linux Enterprise Server 11 and SUSE Linux Enterprise Server 12 servers in your environment, install both the sca-patterns-sle11 and sca-patterns-sle12 packages.

   To install all available patterns:

   zypper install sca-patterns-*

3. For basic setup of the SCA appliance, use the setup-sca script. How to call it depends on how you want to upload the supportconfig archives to the SCA appliance server:

   • If you have configured an anonymous FTP server that uses the /srv/ftp/upload directory, execute the setup script with the -f option and follow the instructions on the screen:

     setup-sca -f

     

     Note: FTP Server Using Another Directory

     If your FTP server uses another directory than /srv/ftp/upload, adjust the following configuration files first to make them point to the correct directory: /etc/sca/sdagent.conf and /etc/sca/sdbroker.conf .

   • If you want to upload supportconfig files to the /tmp directory of the SCA appliance server via scp, call the setup script without any parameters and follow the instructions on the screen:

     setup-sca

   The setup script runs a few checks regarding its requirements and configures the needed subcomponents. It will prompt you for two passwords: the MySQL root password of the MariaDB that you have set up, and a Web user password with which to log in to the Web interface of the SCA appliance.

4. Enter the existing MariaDB root password. It will allow the SCA appliance to connect to the MariaDB.

5. Define a password for the Web user. It will be written to /srv/www/htdocs/sca/web-config.php and will be set as the password for the user scdiag. Both user name and password can be changed at any time later, see Section 2.4.2.5.1, “Password for the Web Interface”.

1. Log in as root user at the system console of the server running the SCA appliance.

2. Put the appliance into maintenance mode by executing:

   scadb maint

3. Start the backup with:

   scadb backup

   The data is saved to a TAR archive: sca-backup-*sql.gz.

4. If you are using the pattern creation database to develop your own patterns (see Section 2.4.3, “Developing Custom Analysis Patterns”), back up this data, too:

   sdpdb backup

   The data is saved to a TAR archive: sdp-backup-*sql.gz.

5. Copy the following data to another machine or an external storage medium:

   • sca-backup-*sql.gz

   • sdp-backup-*sql.gz

   • /usr/lib/sca/patterns/local (only needed if you have created custom patterns)

6. Reactivate the SCA appliance with:

   scadb reset agents

To restore the database from your backup, proceed as follows:

1. Log in as root user at the system console of the server running the SCA appliance.

2. Copy the newest sca-backup-*sql.gz and sdp-backup-*sql.gz TAR archives to the SCA appliance server.

3. To decompress the files, run:

   gzip -d *-backup-*sql.gz

4. To import the data into the database, execute:

   scadb import sca-backup-*sql

5. If you are using the pattern creation database to create your own patterns, also import the following data with:

   sdpdb import sdp-backup-*sql

6. If you are using custom patterns, also restore /usr/lib/sca/patterns/local from your backup data.

7. Reactivate the SCA appliance with:

   scadb reset agents

8. Update the pattern modules in the database with:

   sdagent-patterns -u