Restoring the System

If it becomes necessary to repair the TAS database, you can restore a previous backup using the TAS Manager Console or the TAS Manager Web UI. There are three ways to restore a backup:

Use the TAS Manager Console to restore the system database
Use the TAS Manager Web UI to restore the system database
Use the CLI to restore the database via an SSH window to the Test Manager (TAS)

Use the TAS Manager Console or the TAS Manager Web UI to restore the system database:

Prior to using CLI Restore of Standard backup file, ensure you have enough hard drive space to make a complete copy of the .BCK file being restored, in addition to what is being restored.
Stop the TAS...
Select System > Restore from the TAS Console menu or select TAS Manager Web UI | Actions |Restore. The Restore TAS Settings window opens and any backup files stored on the TAS are displayed in the Available TAS Backup Files list. You can select a full, full_data tar.gz backup file when you restore from TAS Manager Console for both file upload and execution. See details below.
If you want to restore the database from a file that is stored on your machine or on a network share, click the Browse button and navigate to the backup file. Select the file and click Load to upload it to the TAS. When the upload is complete, the file will be displayed in the backup list.
Select the file to restore from the displayed list of backup files stored on the TAS and click Restore. Progress messages will be displayed in the console.
When the restore operation is complete, Start the TAS...

Use the CLI to restore the database via an SSH window to the Test Manager (TAS) :

restore-tas

Without arguments, the interactive way.

You can now select a full, full_data tar.gz backup file when you restore from TAS Manager Console for both file upload and execution:

When downloading the local copy of the backup file, progress will be shown:

Downloading local copy of backup
Setup download filesize:317150KB
6% Complete, 298110KB Remaining
12% Complete, 279086KB Remaining
18% Complete, 260062KB Remaining
24% Complete, 241022KB Remaining
30% Complete, 221998KB Remaining
36% Complete, 202974KB Remaining
42% Complete, 183934KB Remaining
48% Complete, 164910KB Remaining
54% Complete, 145886KB Remaining
60% Complete, 126846KB Remaining

The Restore warning has been update with critical information:

For both backup and restore, the backup files will be further verified to contain required/expected files to prevent accidentally partial backups or restores of bad files.

restore-tas <pathname_to_tar.gz_backup_file>

The restore option for the file backed up using backup-tas full command.

restore-tas - Restore the TAS

Usage: restore-tas

restore-tas <pathname_to_full_backup_tar_gz>

Call with no arguments for normal interactive restore with .bck file

If using automation, pass the path to the full tar.gz backup file. The file must be readable by everyone. This can be done by the owner with the chmod command.

chmod 755 <pathname_to_full_backup_tar_gz)

Example: ##> chmod 755 /tmp/TAS_Full_Backup.tar.gz

##> restore-tas /tmp/TAS_Full_Backup.tar.gz

Extracting files

Resetting and updating database

Restoring original/current sms password

Restore completed successfully, now restart TAS

Note : Full and Full_Data backups maintain timed licenses - Timed licenses are not normally allowed to be reinstalled, or backup / restored, they would normally need a regeneration. However if you do a full or full_data backup, and restore the TAS before the license expires, it will still work.

NOTEs:

When you restore a TAS using any type of backups, the sms password should still be unchanged. The sms password in the backup file will not be applied. However, once the TAS is restarted, if you try to STOP the TAS from CLI or TAS Manager Console and it doesn't work due to Authentication Failure, you just need to login to the Client as sms and File->Change Password, to fully re-apply the sms password. If any issues occur where there is an error about mysql root password, you can execute chg-mysql-root-password command and set that to the same password as the sms password.
After a restore from an older database that may have different permissions, if there are any issues, re-upgrade the TAS.