Database Restore

Key points:

• The CORE database restore procedure is immutable: it cannot be performed in an already bootstrapped CORE server.

Note
In particular, this procedure cannot be used in a live system.

• Once the CORE database is restored on a pair of servers, bootstrap them as the first EP-Partner pair (or triplet, when restoring the FIPSFederal Information Processing Standards - standards developed by the United States federal government for use in computer systems by non-military government agencies and government contractors system) using the --restore option.
• To restore the cluster, continue with the Cluster Scale-out procedure.

Restore Prerequisites

Required Items

• Backup Archives. The matching pair of EP and its Partner's archives.
• Servers. Two servers without CORE software and data.
• Initial Software release. It must be the same release that was used to create the backup archive.

Note
We upgrade the software to the required release following the bootstrap.

• Java Keystores. Presence of the Java Security Provider software compatible with the keystore type and supporting the required decryption algorithm. In the following examples we assume the following:
  • providername SunJCE.
  • storetype JCEKS.

Preparation Steps

1. Backup Archives.
   • Optionally, use ekm_verify_backup to assure mutual conformance of the two archive files. To execute this command:
     1. Upload both archives to a system with installed CORE server software.
     2. Extract the digest file from each archive.
     3. Run the ekm_verify_backup procedure referring to these digests.
   • Check the content of the .properties file in one of the archives and note the following:
     • The software server_version=2.0.xxx.xxx that created this archive.
     • The server_role=<EP|Partner> whose database is stored in this archive.
2. Servers. On each of the two servers that are designated to be the first EP–Partner pair:
   1. As needed:
      1. Uninstall the CORE software.
      2. Clear the CORE database folder – see Database Folder.
      3. Clear the CORE CORE Server Certificates Folder.
   2. Install CORE Server software release that is specified in the .properties file.

   Note
   Do not bootstrap the server. If you do, you will have to repeat step 1.

Restore Quickstart

Note
To restore the first FIPSFederal Information Processing Standards - standards developed by the United States federal government for use in computer systems by non-military government agencies and government contractors triplet, see FIPS System Backup and Restore.

Step 0 - Prerequisites

1. Make sure you have the Required Items.
2. Make sure you completed the Preparation Steps.

Step 1 - Restore the Database of the First EP

1. Upload to your current working directory
   • The keystore with the EP backup decryption key (e.g. EpRestore.jks).
   • The EP backup file (.tar.gz).
2. Obtain the passphrase for JKSA Java KeyStore (JKS) is a repository of security certificates – either authorization certificates or public key certificates – plus corresponding private keys, used for instance in SSL encryption. (e.g. EpRestore1!), the name of the key (e.g. DEKData Encryption Key - the key that encrypts the database. See also - KEK.), the keystore type, and the required Java Security Provider. Use this data to run ekm_restore:
Linux:

sudo /opt/ekm/bin/ekm_restore.sh -p SunJCE -t JCEKS \
-f ./EpRestore.jks -w EpRestore1! -n DEK \
-b ./database_2017-09-05-05-53-05.tar.gz

Windows:

C:\Progra~1\Dyadic\ekm\tomcat\bin\ekm_restore.bat -p SunJCE -t JCEKS \
-f .\EpRestore.jks -w EpRestore1! -n DEK \
-b .\database_2017-09-12-14-17-12.tar.gz

Step 2 - Restore the Database of the First Partner

1. Repeat the same steps on the designated Partner using the corresponding files and data:
   Linux:

   sudo /opt/ekm/bin/ekm_restore.sh -p SunJCE -t JCEKS \
   -f ./PaRestore.jks -w PaRestore1! -n DEK\
   -b ./database_2017-09-05-05-53-05.tar.gz

   Windows:

   C:\Progra~1\Dyadic\ekm\tomcat\bin\ekm_restore.bat -p SunJCE -t JCEKS \
   -f .\PaRestore.jks -w PaRestore1! -n DEK \
   -b .\database_2017-09-12-14-17-12.tar.gz
   

Step 3 - Bootstrap the Restored Pair

With both databases restored on the selected servers:

1. Bootstrap EP the server that restored the EP DB using the --restore option:
   Linux:

   sudo /opt/ekm/bin/ekm_boot_ep.sh -s <ep-hostname> -p <partner-hostname> -w <the root so password> -restore

   Windows:

   C:\Progra~1\Dyadic\ekm\tomcat\bin\ekm_boot_ep.bat -s <ep-hostname> -p <partner-hostname> -w <the root so password> -restore

2. Bootstrap Partner the server that restored the Partner DB using the --restore option:
   Linux:

   sudo /opt/ekm/bin/ekm_boot_partner.sh -s <partner-hostname> -p <ep-hostname> -restore

   Windows:

   C:\Progra~1\Dyadic\ekm\tomcat\bin\ekm_boot_partner.bat -s <partner-hostname> -p <ep-hostname> -restore

Step 4 - Optional Steps

As needed, perform the following:

• Upgrade the software. See Server Upgrade.
• Restore files that were individually saved in Not Included in the Backup.
• Rebuild the backup infrastructure, see Backup Prerequisites Quickstart.
• Re-register the EP with partitions that should be UCLUnbound Command Language-managed from the EP.