You are here

Move log data from one Airlock to another

Affects version(s): 
5.0
4.2

Between Airlock 4.2.x and Airlock 5.x

Because of minor modifications in the log format on Airlock 5.0, we do not recommend transferring logs from an Airlock 4.2.x to an Airlock 5.x.

The transfer of the MySQL database is not supported and not neccessary as it contains only temporary information.

Between two Airlock 4.2.x hosts

If you want to copy all log data from <airlock-a> to <airlock-b>, follow these steps:

  1. copy everything from <airlock-a>:/data to <airlock-b>:/data , be sure to maintain permissions and ownerships.
  2. copy everything from <airlock-a>:/archive to <airlock-b>:/archive , be sure to maintain permissions and ownerships.
  3. svcadm disable slt-taclog-mysqld on <airlock-a> and <airlock-b>
  4. copy <airlock-a>:/opt/slt/ses/taclog/proxy/var/mysql/taclog/ to <airlock-b>:/opt/slt/ses/taclog/proxy/var/mysql/taclog/
  5. svcadm enable slt-taclog-mysqld on <airlock-a> and <airlock-b>
Important: you will loose all previous logdata and zoom/event information on <airlock-b>

Make sure to maintain permissions and ownerships of all files you copy to the target machine. The best solution may be to use tar.

Knowledge Base Categories: