GF.Archiving: Difference between revisions
(Created page with "{{Maturity|3}} {{Pageheaderbox4GT |name=Archiving |WorkingArea=Storage |version=0.9 |owner=J.A.H. Schoonderbeek }} An archive is a primary copy of data (unlike a backup, which...") |
No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Maturity| | {{Maturity|2|superseded by backup & archive management pattern}} | ||
{{ | {{Pageheaderbox4GF | ||
|name=Archiving | |name=Archiving | ||
|WorkingArea=Storage | |WorkingArea=Storage | ||
|version=0.9 | |version=0.9 | ||
|owner=J.A.H. Schoonderbeek | |owner=J.A.H. Schoonderbeek | ||
|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). | ||
| Line 10: | Line 11: | ||
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. | 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. | ||
{{FunctionIcon | {{FunctionIcon | ||
|image=Icon | |image=Icon GF Archiving.png | ||
}} | }} | ||
{{ | {{Text Footer GF}} | ||
Latest revision as of 09:25, 19 May 2017
 | Page maturity This page has maturity level 2 (young) Status: superseded by backup & archive management pattern |
|
GF | Archiving | Version: | 0.9 | 
|
|---|---|---|---|---|---|
| Document type: | Generic Function | Owner: |
 | This function provides preservation with retention policies as add-on to another storage function. |
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:
Generic Patterns using this Generic Function
The following Generic Patterns use this function:
| Applied Pattern | Owner | Maturity |
|---|---|---|
| Message Handling | J.A.H. Schoonderbeek | 4 |
Applied versions of this Generic Function
The following variants of this function have been defined:
No Applied Pattern based on this Generic Pattern (yet)
