Restoring the Database Using the CLI

Use the instructions in this topic to restore an ExtremeCloud IQ Site Engine database backup using the CLI (command line). Restoring a database using the CLI may be necessary after making significant unwanted configuration changes.

	NOTE:	For ExtremeCloud IQ Site Engine 24.2 and earlier, a database backup created by the Backup/Restore procedure, with Back Up Alarm, End-System Event, and Reporting Database enabled, is required prior to running the following database restore procedure. This procedure does not work if Back Up Alarm, End-System Event, and Reporting Database are disabled. In release 24.2 and earlier, the backup script is mysqlbackup_restore.sh

NOTE:

For ExtremeCloud IQ Site Engine 24.2 and earlier, a database backup created by the Backup/Restore procedure, with Back Up Alarm, End-System Event, and Reporting Database enabled, is required prior to running the following database restore procedure. This procedure does not work if Back Up Alarm, End-System Event, and Reporting Database are disabled.

In release 24.2 and earlier, the backup script is mysqlbackup_restore.sh

The restore runs using the backup_restore script in the <install directory>/scripts directory.

To restore the backup from another instance of ExtremeCloud IQ Site Engine, the backup needs to be transferred first. The content of <install directory>/backup> including subdirectories should be transferred to the new instance. To restore the ExtremeCloud IQ Site Engine database backup:

Ensure you are running the same version of ExtremeCloud IQ Site Engine used when creating the database backup on the ExtremeCloud IQ Site Engine server.
Log into the system shell (via the local console or SSH) on the ExtremeCloud IQ Site Engine server as root.
Navigate to the scripts directory:
- Enter cd <install directory>/scripts.
Run the backup_restore script:
- Enter ./backup_restore.sh <full backup directory structure configured on Backup/Restore tab, including path>
  
  (for example, ./backup_restore.sh /usr/local/Extreme_Networks/NetSight/backup/xiqse_03302021/).

	NOTE:	If you restore a backup for troubleshooting purposes, disable the connection to ExtremeCloud IQ to prevent influencing the production statistics. The restoration script will offer you the option to disable the connection to ExtremeCloud IQ. For air gap deployment mode, the option to disable the ExtremeCloud IQ connection is not relevant.

NOTE:

If you restore a backup for troubleshooting purposes, disable the connection to ExtremeCloud IQ to prevent influencing the production statistics. The restoration script will offer you the option to disable the connection to ExtremeCloud IQ.

For air gap deployment mode, the option to disable the ExtremeCloud IQ connection is not relevant.

The database backup is restored. Devices onboarded to ExtremeCloud IQ after the backup was created become orphaned when the database restore is finished. Manual deletion of orphaned devices in ExtremeCloud IQ might be needed.

IMPORTANT:

The deployment mode (connected or air gap) is part of the database backup. Restoring from the backup will not change the deployment mode. The serial number is part of the database backup. Restoring the backup also restores the serial number. The air gap license file is bound to the serial number. Neither license keys nor license files are part of the database backup.

In Connected deployment mode, the following sequence is recommended:

Delete ExtremeCloud IQ Site Engine from ExtremeCloud IQ
Wait for all devices managed byExtremeCloud IQ Site Engine to disappear from ExtremeCloud IQ
Restore the backup of ExtremeCloud IQ Site Engine
Onboard ExtremeCloud IQ Site Engine to ExtremeCloud IQ

If you are restoring the backup to a clean installation, license files and license keys should be inserted into ExtremeCloud IQ Site Engine after the restore.

Related Information

For information on related help topics:

Database Backup Options