9. Decommissioning LOCKSS 1.x

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 six boxes, successively labeled "Upgrading LOCKSS 1.x", "Preparing the LOCKSS 2.x Host", "Installing LOCKSS 2.x", "Configuring LOCKSS 2.x for Migration", "Configuring LOCKSS 1.x for Migration", "Running the Migrator", and "Reconfiguring LOCKSS 2.x for Normal Operation", are colored in light blue, indicating completed steps. The eighth box labeled "Decommissioning LOCKSS 1.x" is highlighted in yellow, indicating the step in progress.

The last task is to decommission your LOCKSS 1.x instance.

new-host migration only If you are doing a New-Host Migration, simply decommission the LOCKSS 1.x storage and host.

same-host migration only In the case of a Same-Host Migration, follow these cleanup steps:

Uninstall the LOCKSS 1.x software package and the LOCKSS Yum repository, with the following steps [1]:
1. LOCKSS 1.x host as root Run this Dnf command as root:
```
dnf remove lockss-daemon
```
  This will uninstall the lockss-daemon (LOCKSS 1.x) software package.
2. LOCKSS 1.x host as root Run this Dnf command as root:
```
dnf config-manager --disable lockss
```
  or:
```
dnf config-manager --set-disabled lockss
```
  This will disable the LOCKSS Yum repository.
3. LOCKSS 1.x host as root As root, run this command:
```
rm /etc/yum.d.repos/lockss.repo
```
  This will delete the configuration file that defines the LOCKSS Yum repository. (LOCKSS 2.x is not distributed via a Yum repository, so you will no longer need it, and it is being phased out.)
4. LOCKSS 1.x host as root As root, optionally run this command:
```
dnf clean all
```
  This will reclaim some storage space used by Dnf, some of which was used by the LOCKSS Yum repository.
Reclaim the storage space used by LOCKSS 1.x log files, with the following steps:
1. LOCKSS 1.x host as root Navigate to the LOCKSS 1.x log directory var/log/lockss as root:
```
cd /var/log/lockss
```
2. LOCKSS 1.x host as root We recommend you save the LOCKSS 1.x to 2.x Migration log files into the lockss user's home directory for a little while, in case you need to refer to them soon after migration. Run this command as root:
```
install -o lockss -g lockss v2migration* ~lockss/
```
1. LOCKSS 1.x host as root Run this command as root:
```
rm daemon* stdout* v2migration*
```
  This will free up the storage space used by LOCKSS 1.x log files.
same-host migration with future reclamation only If you are doing a Same-Host Migration With Future Reclamation, you can now free up the storage space formerly used by LOCKSS 1.x for preserved content. (If you are doing a Same-Host Migration With Incremental Reclamation, this was done gradually for you as the migration progressed and you do not need to do anything in this step.)

You will have to perform the following steps for each content storage directory your LOCKSS 1.x instance was configured to use. These are listed in your LOCKSS configuration file /etc/lockss/config.dat as the semicolon-separated list LOCKSS_DISK_PATHS. One way to output the list of LOCKSS 1.x content storage directories is this command:
```
( . /etc/lockss/config.dat && echo $LOCKSS_DISK_PATHS | tr ';' '\n' )
```
For each LOCKSS 1.x content storage directory <contentdir>, follow these steps:
1. LOCKSS 1.x host as root Navigate to the <contentdir> directory as root:
  
  cd <contentdir>
2. LOCKSS 1.x host as root Delete its cache subdirectory as root:
```
rm -rf cache/
```
  This may take some time depending on the content size.
Of the content storage directories your LOCKSS 1.x instance was configured to use, the first one in the list is the primary content storage directory and is used to store state data and temporary data which can now be deleted in addition to preserved content. One way to output the primary LOCKSS 1.x content storage directory is this command:
```
( . /etc/lockss/config.dat && echo $LOCKSS_DISK_PATHS | sed -e 's/;.*//' )
```
Follow these steps:
1. LOCKSS 1.x host as root Navigate to the primary LOCKSS 1.x content storage directory, symbolically <primarydir>, as root:
  
  cd <primarydir>
2. LOCKSS 1.x host as root Run this command as root:
```
rm -rf config/ db/ iddb/ plugins/ tfile/ tmp/ v3state/
```

Footnotes