Migrating encrypted SMAT databases

In some instances, you must create an encrypted SMAT database on another server. For example, if the primary server is dead, you can still use the encrypted SMAT database on a backup server.

To do this and ensure the SMAT database can be decrypted on the secondary server:

  1. Create an encrypted SMAT database on server A.
  2. Close all connections before moving files.
  3. Move these database files to server B, using the same site name and directory path as the original: dbName.smatdb, dbName.smatdb–wal, dbName.smatdb-shm, dbName.smatdb-sec, dbName.smatdb-sec-wal, dbName.smatdb-sec-shm
    Some files might not be present. You must check the consistency of dbName.smatdb and dbName.smatdb-sec.
    The database can now be used at the new server. The site name must be the same as the original.