How to Store and Back Up Your Digital Archive: A Guide for Heritage Organisations

Hard drives fail. Buildings flood. One copy is not a plan.

These are not abstract anxieties. In 2004, a fire at Morecambe Town Hall destroyed council records stretching back centuries. Every week, somewhere in the country, a hard drive containing a decade’s worth of digitised photographs simply stops spinning — taking irreplaceable material with it.

If you have done the work of digitising your collection, you deserve an archive storage strategy that protects it. The National Archives provides guidance on digital preservation for UK institutions, and the NLHF digital good practice guidance emphasises that storage planning should be built into project budgets from the start. This guide covers the practical steps for any UK heritage organisation: local history societies, small museums, council record offices — all managing large amounts of data with limited budgets and no dedicated IT team.

---

The foundation of digital archive backup storage: the 3-2-1 rule

The 3-2-1 rule is the starting point for any digital archive backup storage strategy. It is simple enough to explain in a trustee meeting, and robust enough to satisfy most professional standards.

3 copies of every file. Your primary working copy plus two backups. If you only have two copies and one fails, you are immediately in crisis.

2 different types of storage. Do not keep all three copies on the same type of storage media. An external hard drive and a cloud backup are two different storage media types. A USB stick and an external hard drive are not — both are portable magnetic or flash media subject to similar failure modes.

1 copy off-site. This is the one most small organisations skip. Off-site means genuinely off-site: not in the same building, not in a staff member’s car in the car park. Cloud storage counts as off-site, which is one reason it has become central to digital preservation planning.

The 3-2-1 rule does not tell you what archive storage to use, or how to verify your copies remain intact over time. That is what the rest of this guide covers.

---

Local archive storage options

Most heritage organisations start with local storage — physical drives that sit in the building. This makes sense as part of a broader strategy, but it cannot be the whole strategy.

Hard drive storage

External hard drives are the most common type of storage for small archives. A 4TB hard drive costs around £80–100 and can hold a substantial digitised collection. For a local history society, a pair of external hard disk drives — one on-site, one kept at a committee member’s home — is a realistic starting point.

The problem is lifespan. Hard drives have moving parts, and moving parts wear out. Mechanical hard disk drives have a mean time between failures of three to five years under regular use — but failures can happen at any time, including to drives that appear healthy. Heat, physical shock, and age all accelerate failure. SSDs are more robust but carry their own risks: flash storage can lose data when left unpowered for extended periods.

Best practice: Replace hard drives on a scheduled cycle every three to four years. Do not wait for a drive to show signs of trouble. Drives rarely give warning.

NAS and on-site storage capacity

A NAS (Network Attached Storage) device holds multiple hard drives in a RAID configuration, so if one drive fails your data survives while you replace it. NAS offers better storage capacity and resilience than a single drive, but it adds complexity and cost — entry-level systems run from £300 to £600 — and it remains on-site, subject to the same risks as everything else in the building.

For most small heritage organisations, a NAS is more complexity than the benefit justifies. The on-site storage component of your 3-2-1 strategy is better served by well-maintained external hard disk drives.

---

Cloud storage for digital archives

Cloud storage solves the off-site problem. Your digital files are held on remote servers in data centres with built-in geographic redundancy — multiple copies spread across different locations. You do not need to remember to take a drive home; the backup happens automatically.

When evaluating cloud storage for archive backup, consider:

Durable storage with geographic redundancy. Reputable providers use object storage infrastructure — such as Amazon S3 — that replicates your archived data across multiple locations. A single data centre failure does not cause data loss.

Storage costs and data transfer charges. Cloud storage costs vary significantly by tier. Cold storage classes (sometimes called archive storage tiers) are low cost for data you store but rarely access, but they charge for data retrieval. Services offering low-cost archive storage tiers like AWS S3 Glacier are worth understanding — the low-cost storage is attractive, but data transfer fees when you need to restore data can be significant. For working digital archives you access regularly, choose online storage with straightforward retrieval.

Scalability. As your digitisation programme grows, the amount of data you store will grow with it. Cloud storage offers scalability that local solutions cannot match — you are not constrained by physical storage capacity.

GDPR and compliance requirements. If your archive contains personal data — oral history recordings, photographs of identifiable individuals, membership records — your cloud storage must comply with UK GDPR. Confirm your provider has appropriate data processing agreements and that data residency meets compliance requirements.

---

Cloud storage versus purpose-built archive storage

This is where many organisations make a costly mistake: assuming generic cloud storage is the same as a purpose-built archival platform.

Storing digital files in Dropbox, Google Drive, or OneDrive gives you cloud backup. It does not give you:

• A structured descriptive metadata framework
• Fixity checking to verify data integrity over time
• Standardised export packages for long-term digital preservation
• An audit trail of access and modification
• Any understanding of archival hierarchy or provenance

These are not pedantic distinctions. Data management in an archive is not simply about keeping files safe in the short term — it is about ensuring those digital files remain usable, meaningful, and verifiable over decades. Without fixity checking, you cannot know whether your stored copies are actually intact; you are taking it on faith that bit rot or silent data corruption has not occurred.

Our complete guide to digitising an archive covers how digitisation planning and archive storage fit together across the whole project lifecycle.

---

Backup, storage, and preservation are not the same thing

These three terms are often used interchangeably, but they describe different levels of care — and confusing them is one of the most common mistakes in digital archive management.

Backup is about recovery. It means having copies of your files so that if one copy is lost or corrupted, you can restore from another. The 3-2-1 rule described above is a backup strategy. It protects against hardware failure, accidental deletion, and local disasters.

Storage is about keeping files accessible. It covers where your digital objects live day-to-day — on a local drive, a NAS, or in the cloud — and how they are organised, secured, and made available to staff or researchers.

Digital preservation goes further than both. It is the active, ongoing commitment to ensuring that digital files remain usable, authentic, and interpretable over time. Preservation includes fixity checking (verifying files have not changed), format migration (converting files to current formats before old ones become unreadable), documentation of provenance and processing history, and governance — clear policies about who is responsible for what, and how decisions about the collection are made and recorded.

Multiple copies on different media reduce the risk of loss. That is essential, but it is not preservation. A file that has been backed up three times but silently corrupted is three copies of a damaged file. A file stored on resilient cloud infrastructure but saved in a proprietary format that no software can open in ten years is safely stored but not preserved.

The practical takeaway: treat the 3-2-1 rule as the foundation, but recognise that preservation requires fixity monitoring, format awareness, migration planning, and documented responsibility on top of that foundation. If you are applying for Heritage Fund support, our guide to budgeting for digitisation in an NLHF bid covers how to present storage costs to funders.

---

BagIt, fixity checking, and data integrity

BagIt is a standard developed by the Library of Congress for packaging digital content for transfer and long-term data archiving, formalised as RFC 8493. A BagIt package contains your digital files plus a manifest — a list of every file and its checksum.

A checksum is a digital fingerprint. When you create a BagIt package, the software calculates a unique checksum for each file and records it. Later, you — or any other system — can recalculate those checksums and compare them to the manifest. If they match, the archived data is intact. If they do not, something has changed: bit rot, accidental modification, or corruption.

This is fixity checking, and it is fundamental to trustworthy archive storage. It is also the accepted standard: The National Archives, the Digital Preservation Coalition, and most serious archival repositories understand and accept BagIt packages. If you ever want to deposit material with another institution or transfer a collection, BagIt provides the common language for doing so safely.

Our article on choosing the right file formats covers how format decisions interact with long-term digital preservation — another key consideration alongside how you store data.

---

A practical archive backup storage plan

Here is what a realistic 3-2-1 archive storage strategy looks like for a small heritage organisation.

Copy 1 — working copy. Your active digital archive on a local computer or NAS. This is what you work from day-to-day.

Copy 2 — on-site backup. An external hard drive updated weekly during active digitisation, monthly otherwise. Stored securely away from the primary machine. Label it, date your backups, and keep a log.

Copy 3 — cloud backup, off-site. Your safety net. Set it up once and ensure it runs automatically. A purpose-built archival platform gives you fixity checking and structured data management alongside the cloud backup — not just file storage.

Take these steps this month:

• Identify where all your digitised files currently live. Write it down.
• Check when each copy was last updated.
• If you do not have an off-site copy, set one up before anything else.
• Schedule a drive replacement review for any hard drives older than three years.
• Check whether your current archive storage offers BagIt export.

---

Protecting your digital archive for the long term

Digital preservation is not a project with an end date — it is an ongoing commitment to data retention and data integrity. The fundamentals are straightforward: keep multiple copies across different storage media, keep one copy off-site, verify your archived data is intact, and use formats and packages that other systems can retrieve and understand.

The organisations that lose digital material are rarely the ones who made the wrong technical choices. They are the ones who made no choices at all — who stored data on a single hard drive and assumed that was enough.

You can do better than that, without an IT department or a large budget.

The Archiver is a cloud-hosted archival platform built for heritage organisations, including museum directors and heads of collections looking for a managed solution. It provides durable archive storage with built-in redundancy, automatic fixity checking, and BagIt export — proper data archiving, not just cloud backup. Request early access to try The Archiver on your own collection. Explore the full feature set to see how it fits your organisation.