Recovery
When a fixity check fails, APTrust sends an alert to Institutional Admin users and APTrust Admins. APTrust does not have an automated self-healing process for fixity failures. The recovery process depends on the storage class and the location of the affected object.
High Assurance
-
This class includes two copies:
- Hot copy (S3) – used for regular access and fixity checks.
- Cold copy (Glacier) – used as a second copy.
-
Fixity checks are performed on the hot (S3) copy.
- If a fixity check fails:
- Contact APTrust support.
- We will work with you to restore the Glacier copy.
- We'll verify the Glacier copy's fixity.
- If valid, we’ll replace the corrupted S3 copy with the Glacier version and record a PREMIS event.
Basic Archive and Deep Archive
- These classes store a single copy only.
- If a fixity check fails, the object cannot be recovered by APTrust.
- To remediate:
- Deposit a new version of the object.
- Use an update bag to replace the corrupted file in preservation storage. You only need to include the impacted file (keeping the same file name and path).