User Tools

Site Tools


Sidebar

LUCY MANUAL Applies to LUCY versions above 2.2.

upgrade_to_43

How to upgrade from 4.2 to 4.3 or newer using Migration Tool

Note: An update from Lucy 4.2 to the version 4.3 is not possible. The update requires a new installation and a migration of the data using the steps provided in this guide. If you dont have any data to migrate, you can simply download (https://www.lucysecurity.com/en/resources/download/) and re-install LUCY and then provide us with your workstation ID in case you have a commercial license.
A PDF version of this guide is available here.

Required steps before beginning the upgrade

  1. Update the initial server to the latest patch for Lucy 4.2. The latest version of Lucy 4.2 is 4.2.14 (October 8th, 2018). Refer to this page on how to update Lucy;
  2. Make sure that you have at least 50% of available disk space on the server;
  3. Setup a new server with the latest version of Lucy, see the section “INITIAL INSTALLATION”. Only basic setup and automatic configuration (setup script) are required.
    :!: In case of installation based on Docker, please refer to this article;
  4. Create a backup of the entire server with Lucy 4.2 using any available backup tools.

:!: Caution: All campaigns must be stopped before the update.

:!: Caution: Do not terminate the server with Lucy 4.2 after upgrading to the latest version. Leave it alive until you are completely sure that all data has been restored to the new system and that you have not lost anything.

Step 1. Export data

  1. Log in to your server with Lucy 4.2 and navigate to the Support menu → Migration Tool;
  2. Select only those parameters that need to be migrated:
    Warning: Exporting templates (scenario, report, awareness) can take quite a long time and consume a huge amount of disk space. If you have not created your own custom templates, do not select these options for export. You can download all new templates again through the Download Templates page.

  3. Click on the “Create” button to start the export;
  4. You will be forwarded to the “Backups” page to monitor the status of the export:

    Be patient, this procedure can take from several minutes to several hours, depending on the number of options you have chosen to export.
  5. When the process is completed, you can download the archive by clicking on the link in the “Time” column:

Note: Large archives can be transferred to the new server directly through the terminal, for example, using SCP command:

  • Find your backup file in /opt/phishing/files/backups
  • Run the commands below:

cd /opt/phishing/files/backups/<id>
scp backup.tar.gz [email protected]<IP_address_Lucy>:/srv
where,
<id> is an identification number of the backup (can be found in the link to the file);
<IP_address_Lucy> - is an IP address of the new server with the latest version of Lucy.

Step 2. Import data

  1. Download (https://www.lucysecurity.com/en/resources/download/) and install the latest version of LUCY
  2. Send us your new workstation ID in order to transfer the license
  3. Log in to your new server and install all latest updates: go to the Support menuUpdate;
  4. Restart the server after the update;
  5. Navigate to the Support menu → Migration Tool → go to “Import” tab;
  6. Select the file you downloaded in Step 1 and wait for the process to complete (this can take a long time);
  7. restore the backup transferred via terminal please run the commands below:

cd /opt/phishing/current/web/protected
./yiic restore <path_to_backup.tar.gz>

Note. The “./yiic restore” command does not display the progress of the restoration process. You can track the progress by checking the log file /opt/phishing/runtime/resque_worker.log. The event indicating the end of the restore process will appear in the log as “RestoreJob …..has finished”.

Post migration steps

  1. (optional) Update and install all new available templates: go to the Support menu → Download Templates;
  2. Change\update system domain via the Setup Script
  3. If you have domains purchased via Lucy, please give us know if you need to update DNS records due to IP address changes.
upgrade_to_43.txt · Last modified: 2018/12/13 06:15 by lucy