Backup: an extra copy with recovery in view

The word points to a recovery purpose. It does not, by itself, show that the copy is current, complete, readable, or available after something goes wrong. This page explains that purpose without recommending a storage product or promising a recovery result.

Name what the copy is supposed to cover

Imagine an adult keeping digital files for a fictional neighborhood newsletter. Their working folder contains draft articles, finished pages, and a few images. They have also made an additional copy of selected files for possible recovery.

To understand that copy, they need more than the label “backup.” Which files were included? When was the copy made? What would they expect to recover from it? These are questions about the actual record, not claims that a particular method is adequate.

An optional copy-description label could read:

Collection: Neighborhood-newsletter files
Copy made on: Record the actual date.
Included: List only the files or folders confirmed.
Not included: Record known exclusions.
Location recorded by owner: Keep private where appropriate.
Recovery checked: State the actual check, or say not checked.

The label is original and does not contain credentials or a real storage location. “Not checked” should remain visible if no recovery check has been performed.

A copy and a record of changes answer different questions

A history of revisions may show earlier states within a document service. An archive may retain material no longer in active use. This entry reserves backup for the recovery purpose described above; it does not infer that every retained file serves that purpose.

Similarly, seeing matching files in two places does not establish how those places behave. Ask whether edits or deletions in one location also affect the other, and consult the actual service documentation. Do not assume that a feature called synchronization provides the independent recovery option you have in mind.

Keep the owner's control intact

A family member helping with the newsletter could assist in listing the intended files. That role does not authorize moving, deleting, or uploading them. Before sharing a copy, the owner should decide what belongs in it and who should have access.

A student might be working within a school's storage system. The family can help formulate a question about what the system retains without requesting account credentials or experimenting on the student's only copy.

No recovery guarantee

This glossary does not select a backup schedule, location, encryption method, or retention policy. It does not certify security or advise recovery from an active incident. The NIST glossary supports the narrow terminology, not the sufficiency of the newsletter arrangement. The copy-description label simply separates what the owner has actually recorded from what remains assumed or untested.

Source

[1] National Institute of Standards and Technology, Computer Security Resource Center. backup. No exact page-specific publication date shown. Accessed September 6, 2026. [1] uses only the terminology specified above; additional findings, recommendations, and source examples are not adopted.

Related guides

• Version history
• Archive
• File naming convention
• Digital folder