Difference between revisions of "GF.Archiving"

From OIAr
Jump to: navigation, search
 
Line 5: Line 5:
 
|version=0.9
 
|version=0.9
 
|owner=J.A.H. Schoonderbeek
 
|owner=J.A.H. Schoonderbeek
|summary=This function is no longer used as it's superseded by the use of a complete pattern for backup and archiving purposes
+
|summary=This function provides preservation with retention policies as add-on to another storage function.
 
}}
 
}}
 
An archive is a primary copy of data (unlike a backup, which is a secondary copy). Archiving is a function that offers long-term storage for data. Archiving can preserve data at any one of several of the lower levels of [[OIAm data view|data abstraction]], but usually handles only a single abstraction level. Examples are archiving at the hardware level (storing bits and bytes, such as in SANs), on a more abstracted level (storing loosely structured data, such as files in a file system), or still higher (storing strictly structured data such as databases).
 
An archive is a primary copy of data (unlike a backup, which is a secondary copy). Archiving is a function that offers long-term storage for data. Archiving can preserve data at any one of several of the lower levels of [[OIAm data view|data abstraction]], but usually handles only a single abstraction level. Examples are archiving at the hardware level (storing bits and bytes, such as in SANs), on a more abstracted level (storing loosely structured data, such as files in a file system), or still higher (storing strictly structured data such as databases).

Latest revision as of 09:25, 19 May 2017


This is a Generic Function document GF Archiving Version: 0.9 OIAr logo
Document type: Generic Function Owner:

J.A.H. Schoonderbeek



Description

This Generic Function belongs to Working Area Storage. An archive is a primary copy of data (unlike a backup, which is a secondary copy). Archiving is a function that offers long-term storage for data. Archiving can preserve data at any one of several of the lower levels of data abstraction, but usually handles only a single abstraction level. Examples are archiving at the hardware level (storing bits and bytes, such as in SANs), on a more abstracted level (storing loosely structured data, such as files in a file system), or still higher (storing strictly structured data such as databases).

In case it is (also) used to make auditing possible, mechanisms may be put in place to prevent alteration of the data after being preserved.

Icon

The image "Icon GF Archiving.png" (shown below) can be used to represent this infrastructure function in graphical Pattern representations that it might be part of:

Icon for this function

Generic Patterns using this Generic Function

The following Generic Patterns use this function:

Semantic query
Generic PatternOwnerMaturity
Message HandlingJ.A.H. Schoonderbeek4

Applied versions of this Generic Function

The following variants of this function have been defined:

Semantic query
No Applied Function based on this Generic Function (yet)
Facts about "GF.Archiving"
Brief descriptionThis function provides preservation with retention policies as add-on to another storage function. +
Friendly nameArchiving +
Function iconIcon GF Archiving.png +
OwnerJ.A.H. Schoonderbeek +
Page maturity2 +
PagetypeGF +
Version0.9 +
Working AreaStorage +