Restoring an ODBC database and configuration from another OneSpan Authentication Server instance

In this scenario, multiple OneSpan Authentication Server instances are mutually synchronizing each other, but one OneSpan Authentication Server instance is lost or becomes unserviceable along with its database. This procedure assumes that there is at least one functional OneSpan Authentication Server instance (in this case, SVR-1) with an up-to-date database, and a server on which an OneSpan Authentication Server instance must be rebuilt (SVR-2), with its database copied from the functional OneSpan Authentication Server instance.

Figure: Synchronization of multiple OneSpan Authentication Server instances – One server and database lost or unserviceable

To restore an OneSpan Authentication Server instance and its database using another existing, functional OneSpan Authentication Server instance

1. Rebuild the server with your operating system SOE, using the same IP address as before, in the same domain as before.

2. Retrieve your backup copies of the configuration files that were previously created from the following folder:

   /etc/vasco/ias (Linux)

   %PROGRAMFILES%\VASCO\IDENTIKEY Authentication Server\bin (Windows)

   For more information, see Backup of sensitive data (Overview).

3. Reinstall OneSpan Authentication Server on the server using the same settings as those used in the previous installation. Do not run the Maintenance Wizard!
4. Restore the backup copy of the configuration file identikeyconfig.xml into its proper directory. Restore the backup copies of any other files that were backed up from the same directory at the same time. For more information, refer to Backup of sensitive data (Overview).
5. On SVR-1, stop the VASCO IDENTIKEY Authentication Server service.
6. Take a complete copy of the database used by the OneSpan Authentication Server instance SVR-1. If you are using the embedded MariaDB database, see Restoring an ODBC database from a backup.
7. Delete the replication queue files for SVR-2 which is on SVR-1. To do so:
   1. On SVR-1, run the Configuration Utility and navigate to the Destination Servers tab of the Replication section.
   2. From there, find the Destination Server row that represents SVR-2 and note its Display Name.
   3. Navigate to the Queue tab and check the File Path value. This will normally be %PROGRAMFILES%\VASCO\IDENTIKEY Authentication Server\ReplData, but may have been re-configured.
   4. In that directory, delete all files with filename starting Display Name.
8. The VASCO IDENTIKEY Authentication Server service on SVR-1 may be restarted now if needed – it will build up a new replication queue until it can connect to SVR-2.

9. Completely overwrite the database used by the OneSpan Authentication Server on SVR-2 with the copy from SVR-1. If you are using the embedded MariaDB database, see Restoring an ODBC database from a backup.

10. Delete the replication database. To do so, delete Replication.DB in the %PROGRAMFILES%\VASCO\IDENTIKEY Authentication Server\ReplData directory. If you have re-configured replication to store its files in a different directory, delete the files in that directory instead.
11. Restart the VASCO IDENTIKEY Authentication Server service on SVR-2.

If the OneSpan Authentication Server with the 'invalid' database (SVR-2) was synchronizing with another OneSpan Authentication Server instance, you must copy over the other database as well. Follow the steps above for any OneSpan Authentication Server with which SVR-2 was synchronizing.