7. Running the Migrator

The next task is to run the migrator in the Migration Control screen of your LOCKSS 1.x Web user interface.

You should now be looking at the Migration Control screen, after you clicked the Next button at the bottom of the Migration Settings screen in Chapter 6 (Configuring LOCKSS 1.x for Migration). Follow these steps:

1. Select the archival units (AUs) you wish to migrate at this time. You have multiple options:

   • Using the Select Plugin dropdown: Select "All Plugins" to migrate all AUs, or select a given plugin to migrate all its AUs.

   • Using the Choose File button: You can upload a text file containing a list of archival unit identifiers (AUIDs) corresponding to the AUs you would like to migrate at this time.

2. Select the desired migration mode:

   • To copy the each AU's URLs and state information and then apply a verification step to check that the copy was successful, select Copy and Verify. This is the recommended mode.

   • To only copy each AU's URLs and state information, select Copy Content.

   • dry run migration only If you are doing a Dry Run Migration, you will also have the option to select Verify Only, to only verify that already copied AUs match after the fact.

3. If you wish the verification step of the Copy and Verify or Verify Only modes to additionally perform byte-for-byte comparison of content data, select the Full content compare checkbox.

4. Start the migration by clicking the Start Migration button at the bottom of the form. (If you are doing a Dry Run Migration, the button is labeled Start Dry Run Migration instead.)

   Important

   • The first time this button is clicked, the principal migration phase migration phase officially begins.

   • During the |PRINCPAL|, users of the LOCKSS node must follow special operating guidelines; see Section 10.1 (Using LOCKSS During the Migration) in Chapter 10 (Appendix: Instructions for Users of LOCKSS Nodes).

   • Information about the status of the migration in progress will scroll in the pane below the Start Migration button. After any database copies, the first line of information, which begins with Status:, will say either Copying or Copying and verifying, as well as a count of AUs that have been processed. Once this copying status and process count appear, adding AUs, deleting AUs, and using the subscription manager may be done in the manner described in the Delegated AU handling during migration section of Chapter 1 (Introduction to the Migration).

   • If either LOCKSS 1.x or 2.x restarts while the migration is in progress, the migration will no longer appear active. Once LOCKSS 1.x and 2.x are back up, re-select the AUs (either with Select Plugin or Choose File), then click Start Migration (or Start Dry Run Migration) again to resume the interrupted migration.

   Tip

   The migration takes time

   The migration process takes a long time, proportional to the total content size, and impacted by system, network, and storage performance. There may be no apparent progress for a while during migration.

   Migration log files

   The migrator writes debugging information to two LOCKSS 1.x log files: /var/log/lockss/v2migration.txt and /var/log/lockss/v2migration.err.

   Stopping the migration in progress

   To stop the migration in progress, click the Abort button. It may take a moment for the migration to stop.

5. When the migration of the selected AUs ends, you will see Status: Done, possibly followed by the number of AUs that encountered errors during migration, on the first line of the status display. Take time to review the migration results in the status display and the Migration log files.

6. Refresh the page in your browser to reset the counters of active AUs shown in the Select Plugin dropdown. Go back to step (1) and repeat the process for additional batches of AUs, until all AUs have been migrated.