Most organisations back up their systems as a natural part of their IT security work. Creating archival copies on a regular basis, however, is far less common. A backup and an archival copy serve different purposes, and when a system stops working, the difference can determine whether you can still access your content or not.
Backups restore systems
A backup is a security copy used to restore systems and data after, for example, a technical failure, a cyberattack or an accidental deletion.
A backup is usually tied to the system it comes from. Restoring it often requires the same software, system environment and technical conditions. In addition, backups are typically kept only for a limited period before being overwritten.
It is an essential function. But it assumes there is a working environment to restore to, and that the backup itself has not been affected.
An archival copy gives access to the content
An archival copy has a different purpose. It preserves content in a format that can be read and used even when the original system is unavailable. This means you don’t have to restore the entire environment in which the content was created first.
Take a website as an example. If the publishing system, the server or the service running the website is down, the archival copy can still display the website’s pages, documents and contact details, exactly as they looked when the copy was made.
An archival copy also shows what the content looked like at a specific point in time. This makes it possible to show afterwards what was published and when, which matters both as evidence and for meeting preservation requirements. For public sector organisations, websites, intranets and social media may also contain official records that must be preserved.
When systems can’t be reached
More and more organisations depend on cloud services and external suppliers. This brings great opportunities, but it also makes access to information dependent on someone else’s service working.
This becomes clear time and again. One example is when a Swedish data centre was hit by a ransomware attack in January 2024. Many government agencies were affected, partly because one of the biggest payroll systems stopped working, and several companies had problems with their websites and e-commerce. For some of those affected, the backup solutions were also knocked out, and it took weeks before the systems were up and running again.
The example shows that it is not always enough to trust that systems will work, or that the supplier can restore them quickly. An archival copy provides a separate, independent route to the organisation’s content.
How an archival copy can be used during an incident
Imagine your intranet goes down on a Monday morning. Staff can’t reach procedures, contact lists or crisis plans, and the support desk is flooded with questions.
With an up-to-date archive copy, you can quickly publish a static version of the intranet or the external website. Staff and the public keep access to the right information, and the pressure on support eases. And if you have stored the copy locally, it works even when the internet connection is down.
Backup and archive copy at a glance
| Backup | Archive copy | |
|---|---|---|
| Purpose | Restore systems and data | Preserve and give access to content |
| Requires | The original system or an equivalent environment | No specific system environment |
| Time perspective | Short term, often overwritten | Long term, shows what the content looked like at a given time |
| During an incident | Can only be used once the environment works again | Can be used immediately |
You need both
Backups and archival copies don’t compete with each other, they complement each other. The backup helps you get your systems back on their feet. The archival copy keeps you connected to your content in the meantime, and long afterwards.
Want to know how to get started with regular archive copies of your websites and intranet? Contact us.

