The Replication Service handles the transfer of data to a Chronopolis Node. It does this by querying the Ingest Server in order to discover the collections it needs to process and transfer to preservation storage. Once this is complete, it runs an initial audit on an ACE AM server local to the Chronopolis Node.

Links

• Gitlab: https://gitlab.umiacs.umd.edu/chronopolis/chronopolis-coreBuilds: http://adaptci01.umiacs.umd.edu/resource/chronopolisChronopolis-Core

Installation

Prereqs

• ACE AM - The replication service will need to send requests to an ACE AM web application in order to register collections
• rsync - Transfers are done using rsync
• SSH key exchange - ssh is used for authentication so keys must be exchanged to any nodes planning on distributing content so that file transfers can occur
• Preservation Storage - The replication service pulls from the ingest server directly to your preservation area on a POSIX file system. We may expand this In the future, but for now, it is only on local disk.

...

This will be filled out as we experience problems. Check /var/log/chronopolis/replication.log to see if there are any stack traces.