Jan Schoonderbeek at 16:23, 27 July 2013

2013-07-27T16:23:01Z

← Older revision		Revision as of 16:23, 27 July 2013
Line 1:		Line 1:
	{{Maturity\|4}}		{{Maturity\|9\|obsoleted because of new Data Protection pattern}}
	{{Pageheaderbox4GF		{{Pageheaderbox4GF
	\|name=Backup		\|name=Backup

Jan Schoonderbeek: GF created

2013-03-30T10:51:47Z

GF created

New page

{{Maturity|4}}
{{Pageheaderbox4GF
|name=Backup
|WorkingArea=Storage
|version=0.2
|owner=J.A.H. Schoonderbeek
|summary=Function that creates (primary or secondary) copies of data.
}}
Backup is a Storage facility that creates a (primary or secondary) copy of (a specified set of) data, 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 either an instance of [[GF.Restore|Restore]], which takes care of the actual restoring of the data, or [[GF.Presentation Engine|Presentation Engine]] which allows users to consult the backup (e.g. for archive purposes). Furthermore, it's usually paired with [[GF.Retention Engine|Retention Engine]] because
* backup is one of the intelligent functions that the Retention Engine is supposed to offer, and
* backup often requires the intelligence that the Retention Engine offers to actually access the data, and/or to improve the backup processes.

Backup can preserve data at any one of several of the lower levels of data abstraction, but usually handles only a single [[OIAm_data_view|abstraction level]]. Examples are
* at the "unstructured data" level, storing sets of elementary data elements, such as the bits and bytes in a storage system;
* at the "loosely structured data" level, storing coherent chunks of data like files or documents;
* at the "strictly structured data" level, storing (parts of) databases.

When creating an Applied Function of this type, the next items are points of consideration:
* What data needs to be secured?
* Is the backup supposed to create a primary or a secondary copy (i.e. a backup or an archive)?
* For a backup: how often and in which manner
* Is there interrelation between (sets of) data that need to be maintained, e.g. by backing up interrelated data in a single backup?
* When must the backup process start? (one could pair Backup with [[GF.Scheduling|Scheduling]] to manage automated backups)
* How long must the secured data be retained (minimum and/or maximum period)?
* What level is needed for monitoring of the success or failure of any backup action, and of available backup capacity?
* At what physical and/or logical location must the backup be created? Are there requirements whether or not created backups need to physically be moved off-site and on-site?
{{FunctionIcon
|image=Icon GF Backup.png
}}
{{Text Footer GF}}

GF.Backup - Revision history

Jan Schoonderbeek at 16:23, 27 July 2013

Jan Schoonderbeek: GF created