6. Configuring LOCKSS 1.x for Migration

A diagram of eight consecutive arrow-shaped boxes, representing from left to right the steps of the migration workflow from LOCKSS 1.x to LOCKSS 2.x. The first four boxes, successively labeled "Upgrading LOCKSS 1.x", "Preparing the LOCKSS 2.x Host", "Installing LOCKSS 2.x", and "Configuring LOCKSS 2.x for Migration", are colored in light blue, indicating completed steps. The fifth box labeled "Configuring LOCKSS 1.x for Migration" is highlighted in yellow, indicating the step in progress. The last three boxes, successively labeled "Running the Migrator", "Reconfiguring LOCKSS 2.x for Normal Operation", and "Decommissioning LOCKSS 1.x", are not colored, indicating future steps.

The next task is to configure LOCKSS 1.x for migration in the Migration Settings screen of your LOCKSS 1.x Web user interface.

Your LOCKSS 2.x system will need to be running, and you will need to know the LOCKSS 2.x hostname, Web user interface username and password, and PostgreSQL database password, supplied when Configuring LOCKSS 2.x for Migration.

Tip

This phase occurs in the Migration Settings screen of your LOCKSS 1.x Web user interface. Some of the fields in this screen are passwords related to your newly installed LOCKSS 2.x instance. Web browsers pop up dialogs offering to save these LOCKSS 2.x passwords, but you should decline, as they would overwrite the password you may have saved for the LOCKSS 1.x Web UI.

Follow these steps:

Log in to your LOCKSS 1.x Web user interface, and click on Migration Settings in the top-right navigation menu.
Complete the four fields in the LOCKSS 2.x Target section of the screen using the appropriate LOCKSS 2.x values:
1. Hostname: Enter the hostname of your LOCKSS 2.x host:
  - new-host migration only If you are doing a New-Host Migration, enter the LOCKSS 2.x hostname, for example lockss2.myuniversity.edu.
  - same-host migration only If you are doing a Same-Host Migration, enter the LOCKSS 2.x hostname:
    - containerized LOCKSS 1.x In the unlikely event you are running LOCKSS 1.x as a Docker container, enter the fully qualified hostname, for example lockss.myuniversity.edu.
    - all other migration scenarios Otherwise, simply enter localhost.
2. Configuration Service Web UI Port: The default Web UI port for the LOCKSS 2.x Configuration Service, 24602, should remain unchanged.
3. Web UI Username: Enter the Web UI username for the LOCKSS 2.x instance.
4. Web UI Password: Enter the Web UI password for the LOCKSS 2.x instance.
Click the Load Configuration button. The metadata database configuration will be queried from the LOCKSS 2.x instance and displayed in the Metadata Database section of the screen.
In the Database Password field, enter the password for the LOCKSS 2.x PostgreSQL database.
dry run migration only If you are doing a Dry Run Migration, select the Perform dry run migration checkbox in the Migration Options section.
same-host migration with incremental reclamation only If, and only if, you are doing a Same-Host Migration With Incremental Reclamation, select the Delete each AU after migration checkbox.

Caution

Selecting this option causes content to be permanently deleted from your LOCKSS 1.x instance, gradually as the migration progresses. This option should be used if, and only if, you are doing a Same-Host Migration With Incremental Reclamation, that is, a same-host migration with insufficient storage space to hold two copies of the content. You will receive a popup warning when you check this checkbox, which you need to acknowledge before you can continue. See Section 1.3.2.2.

Click on the Next button at the bottom of the Migration Settings screen to navigate to the Migration Control screen.