Storware Backup & Recovery stores all of the metadata in the local database. It is highly recommended to set up periodic DB backup on Storware Backup & Recovery Server. Check Initial configuration for more information.
In case you need to restore Storware Backup & Recovery DB:
if you have a working Storware Backup & Recovery - you can use it to restore this file to the specified location and then restore it
if Storware Backup & Recovery don't work- you can try to use the last copy of the database (it is left by default in /tmp/vprotect_db.sql.gz on the server host
if it is not there and you don't have Storware Backup & Recovery working - you may need to use external tools such as S3 browser, TSM client, or just browse through your file system backup destination directories to find and download this file and later restore it
Once you have your backup you can restore DB with the following command:
gunzip < PATH_TO_GZIPPED_BACKUP | mysql -u root -pDBPASSWORD vprotect
Additionally, it is recommended to also keep a copy of backup provider-specific files, i.e. dsm.opt and dsm.sys files for IBM Spectrum Protect, or other config files used by NetBackup, Networker, OpenDedup, etc.
In case of a complete loss of the Storware Backup & Recovery Server:
Reinstall Storware Backup & Recovery Server
if you lost your license file please contact support
Before starting Storware Backup & Recovery Server - restore the database
you can also restore it later (i.e. if you want to reinstall it with Ansible or all-in-one option), but remember to shutdown server first, then restore DB and start the server again
Replace all backup provider-specific files (install any binaries specific for required backup destinations)
Start Storware Backup & Recovery Server service
Install Storware Backup & Recovery Nodes
Make sure the staging path on each node is correct and available
Re-register and start nodes
At this point, Storware Backup & Recovery should be ready to continue operation.