Disaster Recovery

Internal Database Protection

vPlus stores all the metadata in the local database. It is highly recommended to set up periodic DB backup on vPlus Server. Check Initial configuration for more information.

In case you need to restore vPlus DB:

• if you have a working vPlus - you can use it to restore this file to the specified location and then restore it

• if vPlus 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 vPlus 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, for example 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 vPlus Server:

1. Reinstall vPlus Server

   • if you lost your license file, contact support

2. Before starting vPlus Server - restore the database

   • you can also restore it later (for example if you want to reinstall it with Ansible or all-in-one option), but remember to shut down the server first, then restore DB and start the server again

3. Replace all backup provider-specific files (install any binaries specific for required backup destinations)

4. Start vPlus Server service

5. Install vPlus Nodes

6. Make sure the staging path on each node is correct and available

7. Re-register and start nodes

At this point, vPlus should be ready to continue operation.