Data Archiving
Data archiving moves infrequently accessed data from primary systems to long-term storage where it remains retrievable but costs less to maintain. It addresses compliance retention requirements, reduces production system size, and preserves historical records beyond their active use period.
itStorage, backup, and data protection | OpenSkills.info
Intro
Data Archiving
Data archiving moves information out of routine use while keeping it trustworthy, understandable, and retrievable for a defined period. The goal is not to keep every byte forever. The goal is to preserve the right information for as long as a business, legal, historical, or research need requires it.
An archive is therefore more than low-cost storage. Storage holds bits. An archive also keeps the context, controls, and evidence that let you find those bits and use them later.
Use this mental model:
select -> package -> protect -> monitor -> retrieve -> dispose or preserve
Each step answers a different question. What belongs in the archive? What context must travel with it? How will you detect damage? Can an authorized person retrieve and interpret it? What happens when retention ends?
Why organizations archive data
Active systems are optimized for current work. Their data changes often, and users expect fast access. Older information may still have value without needing the same performance.
Organizations archive data to meet several needs:
- retain records for an approved period
- preserve evidence of decisions and transactions
- support audits, investigations, and legal discovery
- keep scientific, cultural, or historical material usable
- reduce the operational burden on active systems
- make long-term datasets available for later analysis
These needs overlap, but they are not interchangeable. A retention rule may require eventual destruction. A preservation mission may require continuing access with no fixed end date. Write the purpose before choosing storage.
Archive, backup, and replication solve different problems
A backup is a recovery copy. It helps restore recent operational state after deletion, corruption, or failure. Backup sets usually rotate, and recovery speed often drives their design.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-209.pdf
Supports
- Archiving as long-term data retention within storage infrastructure
- Storage threats, attack surfaces, data protection, isolation, restoration assurance, and encryption
- Immutability as prevention of alteration or deletion
- Inventory and location tracking for storage media
- Protection of sensitive data at rest and in transit
- Independent recovery copies and separation of backup media
- Long-lived key-management dependencies for protected data
- https://csrc.nist.gov/pubs/sp/1800/26/final
Supports
- Detection and response needs for ransomware and other destructive data-integrity events
- Preparation, tools, and human expertise as parts of integrity response
- https://www.archives.gov/preservation/digital-preservation/about
Supports
- Continued usability, authenticity, accuracy, and functionality as preservation goals
- Recorded fixity, action tracking, audits, metadata capture, and sustainable formats
- Descriptive, structural, and preservation metadata during ingest
- Separate public-use copies and preservation treatment
- https://www.archives.gov/preservation/digital-preservation/risk
Supports
- File-format risk analysis and prioritization
- Significant properties that should survive format migration
- Preservation plans and actions for electronic record types and formats
- https://www.archives.gov/records-mgmt/policy/transfer-guidance.html
Supports
- Acceptable and preferred formats for permanent electronic records
- Metadata requirements for identification, service, and interpretation
- Validation of wrappers and codecs where both apply
- https://www.archives.gov/about/records-schedule
Supports
- Retention and disposition instructions for record series
- Distinction between temporary destruction and permanent transfer
- https://www.archives.gov/records-mgmt/scheduling
Supports
- Inventory, scheduling, approval, implementation, and updating of records schedules
- Records value and disposition as managed lifecycle decisions
- https://www.loc.gov/preservation/digital/formats/sustain/sustain.shtml
Supports
- Disclosure, adoption, transparency, self-documentation, external dependencies, patents, and technical protection mechanisms as format factors
- Complete specifications and validation tools as aids to long-term preservation
- Format choice in relation to migration, emulation, and significant content characteristics
- Preservation risks created by inaccessible technical protections and dependencies
- https://www.dpconline.org/handbook/organisational-activities/storage
Supports
- Multiple independent copies and geographic redundancy
- Online and offline storage diversity
- Fixity monitoring and repair from verified copies
- Documentation, provenance, audit trails, and proactive storage migration
- Difference between storage-system migration and file-format migration
- Technology, provider, human-error, and obsolescence risks
- https://www.dpconline.org/handbook/technical-solutions-and-tools/fixity-and-checksums
Supports
- Fixity as assurance that digital objects remain unchanged
- Checksums for transfer, storage monitoring, and retrieval
- Limits of checksums in locating or repairing a change
- Periodic checking, logs, repair, and chain-of-custody evidence
- New checksums after deliberate format migration
- Multiple copies as the basis for repair after integrity loss