# Genesys Quality Management Suite 8.1.520 : Interactive Mode

The interactive upgrade process is performed as follows:

Login through the server console (CLI) or SSH remote session with root permissions.

Go to the local directory and start the following script:

    cd /home/upgrade
    ./upgrade_script.sh

You will be asked to type the target version.

Confirm the target version
Type the target version and hit Enter.

Backup directory
Select a backup directory for the current configuration data. The default is /home/backup/. Ensure that custom directories have enough storage space. If the backup directory is different than the default, it should already exist with full read-write permissions (750) before you run the script.

Database backup
Choose to keep the existing database.

Icon

If you choose 'no', the existing databases and data are deleted during the upgrade. A database that is not backed up can not be restored after the upgrade.

The script's behavior at this point depends on the current installation that is being upgraded. This could be a standalone server or a cluster. See Database backup process principles.

Upgrade configuration files
Choose 'n' to replace all the configuration files with their equivalent newer versions and default values. Configure the system manually afterwards.
Choose 'y' to execute the configuration backup process. This backs up all Call Recording configuration files and allows you to restore them automatically. Follow this link for more information about the backup-restore tool.

Confirm the source version
If you answered 'y' to the previous question, you will be asked to confirm the source version. This applies to the next two steps.
If you do not confirm the source version, you will be asked to provide the proper source version.

Confirm the configuration update commands files
If you wish to download the entire upgrade directory with subfolders, press enter. Otherwise, specify the proper directory.

Configure file backup destination
We recommend that you keep the default destination. The backed-up configuration files can be used in future investigations.

Confirm the production overwrite of the production configuration files

Back up the Key Manager files:
The script backs up files found on the server that are used by the service Key Manager. During backup, it encrypts them through a password. Provide the password. Write it in a safe place, as you will be required to provide it during the restoration process.

Check the RPM integrity

We recommend that you leave the default 'n' in place. The check tests the SHA1 sums of the RPM packages on the installation DVD in about 2 minutes. The check stops the upgrading process and doesn't allow the user to continue if an error is found.
If done before, the integrity process can be skipped.

Checking the integrity.

Stop Call Recording services

Select databases for backup (cluster installations only) If there is no Call Recording Configuration Service on the server (the server is part of a cluster) and you chose 'y' in the Database backup step, a list of existing databases is displayed. Each existing database has an index number that allows the user to specify their choice of database(s) during the backup process.

One of these can be entered:

- The index number of the database to be backed up (for example: 1).
- a – To back up the displayed databases.
- n – To back up none of the displayed databases. This cancels the backup and restore processes.

If you choose not to select all databases nor press 'n', you can choose individual databases for backup.

The upgrade process

The script begins the upgrade process. Based on the size of the database and file stores, this can take many hours. The screen may appear frozen while the script creates the database dumps.

Upgrade script - upgrade successful
When the upgrade finishes, the script displays a success message and exits. If it stops responding or shows a failure error, contact Genesys Tech Support. Use the top command to check the process status.

Next Page -> Post Upgrade Tasks