- Digital preservation in a DAM comes down to three things: backups, fixity, and audit trails. A platform that does all three well makes preservation a continuous process, not a one-time setup.
- The 3-2-1 backup rule — three copies, two storage types, one offsite — is the proven foundation for protecting against data loss, hardware failure, and local disasters.
- Fixity checks using checksums verify that assets haven't changed since ingest. A DAM that can generate, store, and compare checksums over time gives you proof of authenticity.
- Audit trails don't just record what happened — they tell you who was involved and why, which is essential for recovering from incidents without reintroducing the problem.
- File format obsolescence, virus threats, inconsistent metadata, and storage media degradation are all manageable risks with the right DAM configuration and maintenance practices.
Digital preservation has one goal: ensure that digital assets do not change over time. That means protecting their authenticity, verifying their integrity, and ensuring they remain accessible and recoverable when something goes wrong — because something always does eventually.
What often surprises organizations is how well a modern Digital Asset Management system can serve as the foundation for digital preservation. Where a dedicated preservation system functions as a lockbox — protecting assets from access or change — a DAM can achieve the same preservation goals while enabling permission-based access for the teams that need to use those assets.
This guide covers what digital preservation requires in a DAM, the best practices that ensure long-term asset integrity, and the specific capabilities your platform needs to support.
The Three Pillars of Digital Preservation in a DAM
Implementing digital preservation in a DAM requires the platform to perform three core functions: backups, fixity, and audit trails. These aren't independent features — they work together as a continuous cycle that detects problems, enables recovery, and prevents recurrence.
Pillar 1: Backups and Business Continuity
The foundation of any preservation strategy is ensuring that multiple copies of every asset exist in multiple locations. If a single copy can be lost, corrupted, or made inaccessible, it isn't preserved — it's just stored.
The industry standard framework for backup strategy is the 3-2-1 rule:
Maintain at least three copies — one primary and two backups — to ensure redundancy and protect against corruption or accidental deletion.
Store backups on at least two different types of media — internal hard drive, external drive, cloud storage, or tape — to mitigate the risk of hardware failure affecting multiple copies simultaneously.
Keep at least one backup in a remote location to protect against localized threats: fire, theft, flooding, or infrastructure failure at a single site.
A DAM is particularly well-suited to executing this strategy at scale. Modern platforms support multi-cloud and multi-storage configurations, meaning organizations can distribute backup locations without vendor lock-in. Version control keeps previous iterations accessible so accidental overwrites can be reversed. And in the event of data loss, DAM platforms are built for fast recovery — assets can be retrieved and restored without the downtime that would come from rebuilding from raw storage.
Pillar 2: Fixity — Verifying Asset Integrity Over Time
Fixity is the ability to confirm that an asset has remained unchanged since it was ingested. It's how a preservation system proves authenticity — not just that a file exists, but that it's the same file it was when it was first stored.
The mechanism is a checksum: a unique digital fingerprint generated from the asset's data at the time of ingest. To verify fixity, the system generates a new checksum from the current file and compares it to the original. If they match, the asset is intact. If they don't, something has changed.
A robust DAM platform should make this process straightforward — generating checksums at ingest, storing them against the asset record, and enabling scheduled or on-demand fixity reports that compare current checksums against the originals across the entire library.
When a checksum mismatch is detected, the response depends on the severity. In most cases, the correct action is to restore an unaffected version from backup. But restoration alone isn't sufficient for preservation purposes — it addresses the symptom without identifying the cause. That requires the third pillar: audit trails.
Pillar 3: Audit Trails — Visibility Into Every Asset Action
An audit trail is a complete, tamper-evident log of every action taken on every asset: uploads, downloads, edits, deletions, permission changes, and access events. For digital preservation, audit trails serve two functions: accountability and diagnosis.
When a fixity check reveals that an asset has changed, the audit trail answers the questions that matter: When did the change occur? Who had access at that time? What action was taken? Was this human error, a system issue, or a security incident?
Comprehensive event logs also support prevention. Reviewing audit data after an incident surfaces patterns — access events that preceded the corruption, permission structures that allowed unauthorized modifications, workflow gaps that created opportunities for accidental deletion. Those insights drive the configuration changes that prevent recurrence.
Digital Preservation as a Continuous Cycle
The three pillars above aren't a one-time setup. They function as a continuous cycle: detection, recovery, investigation, and prevention.
Fixity checks detect changes. Backups enable recovery. Audit trails support investigation into what happened and who was involved. And the insights from that investigation drive prevention — updated permissions, closed workflow gaps, additional safeguards — that reduce the likelihood of the same incident occurring again.
Organizations that treat digital preservation as a continuous practice — running regular fixity reports, monitoring audit data, testing backup recovery periodically — maintain collection integrity over years and decades. Organizations that treat it as a one-time configuration eventually discover that "set it and forget it" preservation isn't preservation at all.
Additional Best Practices for Long-Term Preservation
Monitor asset health proactively. Schedule routine fixity reports to identify corrupted files before they propagate through the library. Use metadata and expiration tracking to flag assets that may need review, migration, or archival. Implement retention policies that automatically archive or purge assets according to your organization's schedule, preventing the library from accumulating content that no longer needs to be actively managed.
Address file format obsolescence. File formats change over time, and assets stored in obsolete formats become inaccessible as the tools to open them disappear. A DAM can support format migration — automatically converting older formats to current standards while preserving the originals. Industry-recommended archival formats include uncompressed TIFF for images and MPEG-2 for video. Preserving originals alongside normalized versions ensures future flexibility.
Implement virus scanning at ingest and on schedule. Malware and corrupted files are a real threat to digital collections. A DAM should perform automated virus scanning on every upload and support scheduled full-library scans for dormant threats. Real-time alerts for failed scans or flagged assets enable rapid response before infected files spread.
Maintain rich, embedded metadata. Metadata is what makes assets findable, understandable, and usable over time. Embedded metadata — written into the file itself rather than stored only in the DAM database — travels with the asset if it's ever migrated to a different system. Use controlled vocabularies for consistency, automate metadata capture where possible, and include provenance information: origin, rights, and modification history.
Enforce role-based access controls. Unauthorized access and accidental deletion are among the most common causes of asset loss. Role-based permissions limit what each user can do based on their function. Approval workflows that require administrative sign-off for destructive actions — mass deletions, bulk modifications — add a human checkpoint before irreversible changes are made.
Maintain complete version history. Every modification to an asset should create a new version, with the previous version preserved and restorable. Version notes that record why a change was made and by whom give context to the version history, making it useful for investigation as well as recovery.
Audit and refresh backup storage media periodically. Storage devices degrade over time — a phenomenon known as bit rot. Regularly migrating assets from aging hardware to modern storage, combined with checksum verification during migration, ensures that the backup copies your preservation strategy depends on haven't silently degraded. Cloud storage with built-in redundancy and failover reduces this risk but doesn't eliminate the need for periodic validation.
Industry Standards for Digital Preservation
Organizations with formal preservation obligations can reference established standards for guidance. ISO 16363 — Audit and Certification of Trustworthy Digital Repositories — provides a framework for evaluating whether a repository meets the requirements for long-term preservation. The Library of Congress maintains recommended formats for moving image files and other content types. These standards are particularly relevant for cultural institutions, archives, broadcasters, and any organization with regulatory or legal obligations around records retention.
Frequently Asked Questions
What is the difference between a DAM and a digital preservation system?
A dedicated digital preservation system functions primarily as a lockbox — protecting assets from change and ensuring their long-term integrity, often with minimal access capability. A DAM can achieve the same preservation goals while also enabling permission-based access for teams that need to use those assets operationally. For organizations that need both preservation and active use of their collections, a DAM configured for preservation is often the more practical choice, provided it supports backups, fixity checking, and comprehensive audit trails.
What is a checksum and how does it verify asset integrity?
A checksum is a unique digital fingerprint generated from an asset's data at a specific point in time — typically when the asset is first ingested into the DAM. To verify integrity later, the system generates a new checksum from the current file and compares it to the original. If they match, the asset is unchanged. If they don't, something in the file has been altered, whether through corruption, unauthorized modification, or a storage error. The checksum itself doesn't prevent changes — it detects them, enabling recovery before the issue propagates.
How often should fixity checks be run?
The appropriate frequency depends on the size of the collection, the risk tolerance of the organization, and any regulatory or compliance requirements. For active collections with frequent uploads and modifications, monthly fixity reports are a reasonable baseline. For archival collections that change less frequently, quarterly may be sufficient. The key is that fixity checking should be scheduled and consistent — not run only when a problem is suspected, because by then the window for early detection has already closed.
What file formats are recommended for long-term digital preservation?
For images, uncompressed TIFF is the widely recommended archival format — it preserves all image data without the lossy compression that formats like JPEG apply. For video, MPEG-2 is one accepted archival standard. The Library of Congress publishes recommended formats for moving image files and other content types, which is a useful reference for organizations with formal preservation requirements. The general principle is to prefer open, well-documented formats over proprietary ones, as proprietary formats can become inaccessible when the software that reads them is discontinued.
What should be in a DAM audit trail for preservation purposes?
A preservation-grade audit trail should log every action taken on every asset: uploads, downloads, edits, deletions, permission changes, access events, and any administrative actions that affect the asset or its metadata. Each log entry should capture what happened, when it happened, and which user account was responsible. The trail should be tamper-evident — meaning the logs themselves can't be modified or deleted by standard users — and should be retained for a period consistent with the organization's retention policy and any applicable regulatory requirements.
How does file format migration work without losing the original?
A DAM configured for preservation should treat format migration as a normalization process that creates a new version in the current standard format while preserving the original file in its native format. The two versions coexist in the system — the normalized version for current access and distribution, the original for archival reference and potential future reprocessing if standards change again. Checksum verification during migration confirms that the original was preserved accurately and that the normalized version was generated without data loss.
See how Orange Logic supports digital preservation at enterprise scale.
Our team can walk through how OrangeDAM handles backups, fixity, audit trails, and long-term asset governance.
Book a demo →