3. Preparing the LOCKSS 2.x Host

The next task in the migration process is to prepare your LOCKSS 2.x host for LOCKSS 2.0.91-beta2, the latest version of LOCKSS 2.0-beta2.

The necessary work depends on your Migration Scenario:

New-Host Migration

If you are doing a New-Host Migration, follow these steps:

1. Commission a new host for your LOCKSS 2.x instance, for example by setting up a new physical machine and installing Linux, or spinning up a new Linux virtual machine. See the System Prerequisites section and Operating Systems appendix of the LOCKSS 2.x System Manual for details.

   Coordinating with Administrators of LOCKSS Networks

   The administrator of your LOCKSS network has to incorporate the IP address of this new host to firewall rules and Web server access control on the network configuration server. See Access control before migration in Chapter 11 (Appendix: Instructions for Administrators of LOCKSS Networks).

2. If you are doing a New-Host Migration, you will need to make sure that firewalls at your institution and on your LOCKSS 2.x host allow some TCP connections from the LOCKSS 1.x host to the LOCKSS 2.x host for the duration of the migration, specifically:

Port	Description
9739 [1]	Temporary LCAP port
24602	LOCKSS 2.x Configuration Service Web user interface
24611	LOCKSS 2.x Repository Service REST API
24612	LOCKSS 2.x Configuration Service REST API
24620 [2]	PostgreSQL

Same-Host Migration

If you are doing a Same-Host Migration on a discontinued operating system in the RHEL family:

• CentOS Linux (not to be confused with CentOS Stream)

• CentOS Stream 8 (not to be confused with CentOS Linux)

• EuroLinux

• Red Hat Enterprise Linux (RHEL) 7 or earlier

• Oracle Linux 7 or earlier

• Scientific Linux

then you must upgrade your LOCKSS host to a supported operating system in the RHEL family:

• AlmaLinux OS 8 or later

• CentOS Stream 9 or later

• Red Hat Enterprise Linux (RHEL) 8 or later

• Oracle Linux 8 or later

• Rocky Linux 8 or later

before you can co-install LOCKSS 2.x with LOCKSS 1.x. In particular, CentOS Linux (not to be confused with CentOS Stream) was once common in the LOCKSS 1.x user community, and requires an upgrade before installing LOCKSS 2.x.

The LOCKSS Community Wiki offers a page on OS Upgrades, providing guidance on various upgrade paths.

---

Footnotes

[1]

This port is configurable, so if you choose a different temporary LCAP port in Chapter 5 (Configuring LOCKSS 2.x for Migration) than the default port, you will instead need to ensure that firewalls allow TCP connections from your LOCKSS 1.x host to that port on your LOCKSS 2.x host.

[2]

If you choose to configure LOCKSS 2.x with an external PostgreSQL database instead of the default embedded PostgreSQL database, you will instead need to ensure that firewalls allow TCP connections from your LOCKSS 1.x host to the appropriate PostgreSQL host and port for the duration of the migration. See PostgreSQL and External PostgreSQL Database in the LOCKSS 2.x System Manual.