Q: What upkeep is required to run a LOCKSS node?

From Adpnwiki
Jump to navigation Jump to search

We are often asked what effort is involved in keeping a LOCKSS node running and up-to-date. Here is a summary of tasks related to operating LOCKSS

Centralized tasks

These tasks are handled by centralized teams in our LOCKSS network (the ADPNet Steering Committee and the ADPNet Technical Policy Committee).

  • Moving AUs through the ingest process
  • Notifying network of new AUs to add
  • First response technical troubleshooting
  • Manage centralized config server, file staging server
  • Writing policy documents
  • Organizing meetings, nominating meeting chairs
  • Yearly storage/usage statistics for billing
  • Billing and funds management
  • Onboarding nodes and participants

Sysadmin tasks (running a node)

These tasks are typically handled by sysadmins in the normal operation of running a LOCKSS node.

  • Initial LOCKSS node install and setup (one-time)
  • Major hardware upgrade (every ~5 years)
  • Disk recovery / migration (rare, in cases of failure)
  • Updating firewall rules (local + border) when new nodes or tools are added
  • Operating System patching (auto-install is possible)
  • LOCKSS daemon update (approx. yearly)
  • Account access chain of custody (2 people)
  • Setup for file ingest
  • Shared file store account setup, and/or
  • Local file store setup, install, local and border permissions
  • Attend LOCKSS technical meetings

Content Ingestion tasks

These tasks are typically handled by librarians / archivists in the normal operation of working with LOCKSS

  • Add existing AUs to this node (approx. monthly, only if you’re running a node)
  • Adding your own new AUs
  • Plugin creation (often one-time, or use a generic plugin)
  • Bagit bundling
  • Attend LOCKSS main meetings