Skip to end of metadata
Go to start of metadata

The Replace File operation or replace file functionality replace the data object/checksum, identified by the given an ID in the bit repository with a given new data object. It may only replace the data on certain pillars if this is specified explicitly.

Replacement of a file consist of replacing a full copy or a checksum (depending on the pillar type) with another given data corresponding to given file identifier in a given service level agreement. Replacement can be used as part of re-establishment of integrity of files, where some of the replicas have been damaged - in this case only some of the replicas are replced. It can also be used to re-establishment of wrongly putted data objects - in this case all replicas are replaced.

An alternative to use of replacement using existing operations GetFile (object to replace another) DeleteFile (object to be replaced) and PutFile (object found via GetFile). This alternative can however be inefficient, as well as give challenges in regard of ensuring that the whole process is carried out. Otherwise the data is at risk of being lost. A 'regret period' for the replaced object is not part of the protocol, but as for Delete File, we assume a regret period in which it is possible to perform a manual roll-back is part of the SLA.

Replace File user stories

User stories involving Replace File operation.

Replace File Communications

The replacement is managed via a replace client and communication with pillars via the coordination layer through messages initiating actions and data transmission for data to replace.

Replace File Pillar requirements

Design Decisions - Replace File

Unresolved issues - Replace File

  • No labels