5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions

From aptrust
Jump to: navigation, search


5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions
Status Ready for review
Compliance Rating Fully compliant
Responsible

The repository shall have adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions.

Supporting Text

This is necessary in order to ensure continued access to and tracking of preservation functions applied to the digital objects in their custody.

Examples for Meeting the Requirement

Documentation of what is being backed up and how often; audit log/inventory of backups; validation of completed backups; disaster recovery plan, policy and documentation; fire drills; testing of backups; support contracts for hardware and software for backup mechanisms; demonstrated preservation of system metadata such as access controls, location of replicas, audit trails, checksum values.

Discussion

The repository should be able to demonstrate the adequacy of the processes, hardware, and software for its backup systems and the full range of ingest, preservation, and dissemination functions required of a repository entrusted with long-term preservation. Simple backup mechanisms must preserve not only the repository main content, but also the system metadata generated by the preservation functions. Repositories need to develop backup plans that ensure their continuity of operations across all failure modes.

Evidence Provided

APTrust system infrastructure is designed to be highly reliable. Deposits (main content) are packaged as “bags” and their structure defined in the BagIT specification (https://tools.ietf.org/html/draft-kunze-bagit-08, also see Bagging Specifications). Once uploaded to the repository bags are unpacked, verified (two file checksums are stored in the repositories metadata) and stored in APTrust. Bags are stored using AWS S3 (designed for 99.99% availability) buckets. These are replicated to a geographically diverse locations and stored using AWS Glacier (see the Technical Documentation#Architecture for additional information). Amazon Glacier is designed to provide average annual durability of 99.999999999% for an archive. All deposits are fixity checked every 90 days to detect data degradation.

More details about preservation and storage can be found here: Preservation and Storage.

Backup information about deposit metadata can be found on the Support and Maintenance#Backups. Additional auditing information for each technology can be found in the Technical Documentation#Auditing section.

APTrust has a designated systems administrator to make sure backups are successful and accurate. See 3.2.1 for the Systems Administrator/Developer job description.