Difference between revisions of "Preservation node"
(Created page with "A preservation node is a server on the ADPNet private LOCKSS network. ''This article is a stub, put in place on 18 December 2018.''") |
(Preservation nodes need a config server) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | A [[preservation node]] is a server on the ADPNet private LOCKSS network. | + | A [[preservation node]] is a server on the ADPNet private LOCKSS network, which stores archival copies of the digital content preserved on the network. Preservation nodes are owned and operated by [[ADPNet Host]] members. |
| − | + | Each preservation node serves as a [[LOCKSS Cache]], collecting and safeguarding [[Archival Unit]]s from participating institutions. The cache is a computer whose sole purpose in life is to run a [[LOCKSS Daemon]] to continually collect content from specific places, store it, and check it against the copies preserved by the other LOCKSS caches in its network to insure that the content stored is complete and uncorrupted. | |
| + | |||
| + | The several preservation nodes are configured, linked together, and directed toward new source content by a single node acting as a [[configuration server]]. In some LOCKSS networks the configuration server is managed by an outside institution such as the LOCKSS development team; but on ADPNet, the configuration server is managed by one of the Host members (currently, [[Birmingham Public Library]]) and maintained on their preservation node. Configuration data and scripts to allow another preservation node to transition into the role of configuration server is [https://journal.code4lib.org/articles/11909 distributed throughout the network as an Archival Unit]. | ||
Revision as of 12:26, 18 December 2018
A preservation node is a server on the ADPNet private LOCKSS network, which stores archival copies of the digital content preserved on the network. Preservation nodes are owned and operated by ADPNet Host members.
Each preservation node serves as a LOCKSS Cache, collecting and safeguarding Archival Units from participating institutions. The cache is a computer whose sole purpose in life is to run a LOCKSS Daemon to continually collect content from specific places, store it, and check it against the copies preserved by the other LOCKSS caches in its network to insure that the content stored is complete and uncorrupted.
The several preservation nodes are configured, linked together, and directed toward new source content by a single node acting as a configuration server. In some LOCKSS networks the configuration server is managed by an outside institution such as the LOCKSS development team; but on ADPNet, the configuration server is managed by one of the Host members (currently, Birmingham Public Library) and maintained on their preservation node. Configuration data and scripts to allow another preservation node to transition into the role of configuration server is distributed throughout the network as an Archival Unit.