Copy Database from Other Identikey Server

Linux

1. Stop the Identikey Server Daemon.

2. Restore database from backup. If you are using the embedded PostgreSQL database:

a. Enter the following command:

vds_chroot <install dir>

/opt/vasco/identikey/usr/local/pgsql/bin/pg_restore -d postgres -c -U <DB admin userid> [-v] "<path/filename>"

where:

<install dir> is the directory in which Identikey Server is installed

<path/filename> is the absolute path and file name of the file to restore from

<DB admin userid> is the database administrator account name. The database administrator account created during installation is digipass.

-v is an optional 'verbose mode' parameter. Use this if you wish to see output as the database is restored.

b. You will normally be prompted for the password of the database administrator account. When installed, this is set to digipassword.

c. Enter the following command:

vds_chroot <install dir> /opt/vasco/identikey/usr/local/pgsql/bin/vacuumdb -z -d postgres -U <DB admin userid> [-v]

where:

<install dir> is the directory in which Identikey Server is installed

<DB admin userid> is the database administrator account name. The database administrator account created during installation is "digipass".

-v is an optional 'verbose mode' parameter. Use this if you wish to see output as the database is restored.

d. You will normally be prompted for the password of the database administrator account.

This step forces the database to recalculate optimization statistics, because all the data has been removed and reloaded.

3. Delete the replication queue files for all destination servers. This can be done by deleting all files in the

<install directory>\ReplData directory (Note: if you have re-configured replication to store its files in a different directory, delete the files in that directory instead).

4. Restart the Identikey Server Daemon.

Follow the 6.2.2.4 Copy Database from Other Identikey Server procedure below on all other Identikey Servers in the system. It is essential to resynchronize all the databases in the system.

6.2.2.3 Rebuild Identikey Server, Restore Database

This procedure is required where both the Identikey Server and its database have been lost. Configuration files and the database will be restored from backups.

Windows

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 identikeyconfig.xml file and any other files from the Bin directory that were backed up.

3. Reinstall Identikey Server on the server. The same settings as those chosen in the previous installation should be selected. Do not run the Configuration Wizard.

4. Restore the backup copy of the configuration file identikeyconfig.xml into the <install directory>\Bin directory. Restore the backup copies of any other files that were backed up from the Bin directory at the same time.

5. Stop the Identikey Server Service.

6. Restore database from backup. If you are using the embedded PostgreSQL database:

a. Open a command prompt in <install directory>\PostgreSQL\Bin.

b. Enter the following command and hit ENTER:

pg_restore -d postgres -c -U <DB admin userid> [-v] "<path\filename>"

where:

<path\filename> is the absolute path and file name of the file to restore from

<DB admin userid> is the database administrator account name. The database administrator account created during installation is digipass.

-v is an optional 'verbose mode' parameter. Use this if you wish to see output as the database is restored.

c. You will normally be prompted for the password of the database administrator account. When installed, this is set to digipassword.

d. Enter the following command and hit ENTER:

vacuumdb -z -d postgres -U <DB admin userid> [-v]

where:

<DB admin userid> is the database administrator account name. The database administrator account created during installation is digipass.

-v is an optional 'verbose mode' parameter. Use this if you wish to see output as the database is restored.

This step forces the database to recalculate optimization statistics, because all the data has been removed and reloaded.

e. You will normally be prompted for the password of the database administrator account. When installed, this is set to digipassword.

7. Start the Identikey Server Service.

8. Follow the 6.2.2.4 Copy Database from Other Identikey Server procedure below on all other Identikey Servers in the system. It is essential to resynchronize all the databases in the system.

Linux

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 identikeyconfig.xml file and any other files from the Bin directory that were backed up.

3. Reinstall Identikey Server on the server. The same settings as those chosen in the previous installation should be selected. Do not run the Configuration Wizard.

4. Restore the backup copy of the configuration file identikeyconfig.xml into the <install directory>/Bin directory. Restore the backup copies of any other files that were backed up from the Bin directory at the same time.

5. Stop the Identikey Server Daemon.

6. Restore database from backup. If you are using the embedded PostgreSQL database:

a. Enter the following command:

vds_chroot <install dir>

/opt/vasco/identikey/usr/local/pgsql/bin/pg_restore -d postgres -c -U <DB admin userid> [-v] "<path/filename>"

where:

<install dir> is the directory in which Identikey Server is installed

<path/filename> is the absolute path and file name of the file to restore from

<DB admin userid> is the database administrator account name. The database administrator account created during installation is digipass.

-v is an optional 'verbose mode' parameter. Use this if you wish to see output as the database is restored.

b. You will normally be prompted for the password of the database administrator account. When installed, this is set to digipassword.

c. Enter the following command:

vds_chroot <install dir> /opt/vasco/identikey/usr/local/pgsql/bin/vacuumdb -z -d postgres -U <DB admin userid> [-v]

where:

<install dir> is the directory in which Identikey Server is installed

<DB admin userid> is the database administrator account name. The database administrator account created during installation is "digipass".

-v is an optional 'verbose mode' parameter. Use this if you wish to see output as the database is restored.

This step forces the database to recalculate optimization statistics, because all the data has been removed and reloaded.

d. You will normally be prompted for the password of the database administrator account. When installed, this is set to digipassword.

7. Start the Identikey Server Daemon.

8. Follow the 6.2.2.4 Copy Database from Other Identikey Server procedure below on all other Identikey Servers in the system. It is essential to resynchronize all the databases in the system.

6.2.2.4 Copy Database from Other Identikey Server

This procedure will be required where multiple Identikey Servers are synchronizing with each other, where one database has become unsynchronized or unstable. It must be replaced with a 'safe' database – one containing up-to-date, uncorrupted data. The instructions below assume a simple two-Identikey Server pair where one Identikey Server (SVR-2) is using a database that has become unstable, and the other (SVR-1) is using a 'safe' database.

To replace the database:

1. Identify the Identikey Server with the 'safe' database. For these steps, it will be referred to as SVR-1.

2. Stop the Identikey Server Service on SVR-1 and SVR-2.

3. Take a complete copy of the database used by the Identikey Server on SVR-1. If you are using the embedded PostgreSQL database, see 6.1.6.3 Backup of PostgreSQL Embedded Database for instructions.

4. Delete the replication queue files for SVR-2 which is on SVR-1:

a. On SVR-1, run the Identikey Server Configuration utility and change to the Destination Servers tab of the Replication section.

b. Find the Destination Server row that represents SVR-2 and note the Display Name.

c. Change to the Queue tab and check the File Path value. This will normally be <install directory>\ReplData, but may have been re-configured.

d. In that directory, delete all files with filename starting <Display Name>.

5. The Identikey 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.

6. Completely overwrite the database used by the Identikey Server on SVR-2 with the copy from SVR-1. If you are using the embedded PostgreSQL database, see Step 2 of 6.2.2.2 Restore Database, Identikey Server Undamaged.

7. Delete the replication queue file on SVR-2 for all other Identikey Servers. This can be done by deleting all files in the <install directory>\ReplData directory (Note: if you have re-configured replication to store its files in a different directory, delete the files in that directory instead).

8. Restart the Identikey Server Service on SVR-2.

Warning

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