BT.Restore

From OIAr Archive 2013
Revision as of 00:22, 12 November 2012 by Jan Schoonderbeek (talk | contribs) (start)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Informational
Page maturity
This page has maturity level 4 (mature)
Status: Replaces Backup&Restore

This is a Building Block document

Document icon BT Restore Version: 0.1 OIAr logo
Document type: Building Block Type Owner:

J.A.H. Schoonderbeek


Informational
Create commentary

Description

This Building Block Type belongs to Working Area Storage (ST). Restore is a Storage facility that takes a previously created backup of (a specified set of) data and restores it to a specified location, in order to be able to rescue data after an incident or emergency has occurred. In this way, data can be restored when the original data is lost, corrupted or (un)intentionally changed. It's always paired with an instance of Backup, which takes care of the necessary backing up of the data. Furthermore, it's usually paired with an instance of Retention Engine because

  • restore is one of the intelligent functions that the Retention Engine is supposed to offer, and
  • restore often requires the intelligence that the Retention Engine offers to actually restore the data, and/or to improve the restore processes.

Restore can restore data at any one of several of the lower levels of data abstraction, but usually handles only a single abstraction level. Examples are

  • at the "raw bits" level, restoring sets of elementary data elements, such as the bits and bytes on a hard disk;
  • at the "loosely structured data" level, restoring coherent chunks of data like files or documents;
  • at the "strictly structured data" level, restoring (parts of) databases.

When creating a Building Block Variant of this type, the next items are points of consideration:

  • Is the data being restored over another set of data? If so, are there special permissions needed?
  • Should access to the raw bits/files/database be blocked for other users than the Restore facility during the restore action?
  • What actions are necessary should a restore procedure abort?
  • Is there interrelation between (sets of) data that need to be maintained, e.g. by restoring interrelated data in a single restore action?
  • What level is needed for monitoring of the success or failure of any restore action, and of available restore capacity?
  • How often are restore tests needed?
  • How can clients request/execute restore actions on selected sets of data?

Icon

The icon below can be used to represent this infrastructure function in graphical Pattern representations that it might be part of:

Icon for this function


Variants of this Building Block Type

The following variants of this function have been defined:

Semantic query

No Pattern Variants based on this Pattern Type (yet)


Pattern Types using this Building Block Type

The following Pattern Types use this function:

Semantic query
Pattern VariantBrief DescriptionOwnerMaturity
PAT.Data ManagementData Management?J.A.H. Schoonderbeek?3
PAT.File StorageFile StorageJ.A.H. Schoonderbeek4
PAT.Raw StorageRaw StorageJ.A.H. Schoonderbeek4
... more about "BT.Restore"
Icon BBT Restore.png +
J.A.H. Schoonderbeek +
unspecified +