https://www.infra-repository.org/oiar-2013/index.php?action=history&feed=atom&title=BT.RestoreBT.Restore - Revision history2026-05-06T14:44:38ZRevision history for this page on the wikiMediaWiki 1.40.0https://www.infra-repository.org/oiar-2013/index.php?title=BT.Restore&diff=780&oldid=prevJan Schoonderbeek: start2012-11-11T23:22:21Z<p>start</p>
<p><b>New page</b></p><div>{{Maturity|4|Replaces Backup&Restore}}<br />
{{Pageheaderbox4BBT<br />
|name=Restore<br />
|WorkingArea=Storage (ST)<br />
|version=0.1<br />
|owner=J.A.H. Schoonderbeek<br />
}}<br />
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 [[BT.Backup|Backup]], which takes care of the necessary backing up of the data. Furthermore, it's usually paired with an instance of [[BT.Retention Engine|Retention Engine]] because<br />
* restore is one of the intelligent functions that the Retention Engine is supposed to offer, and<br />
* restore often requires the intelligence that the Retention Engine offers to actually restore the data, and/or to improve the restore processes.<br />
<br />
Restore can restore data at any one of several of the lower levels of [[Data view|data abstraction]], but usually handles only a single abstraction level. Examples are <br />
* at the "raw bits" level, restoring sets of elementary data elements, such as the bits and bytes on a hard disk;<br />
* at the "loosely structured data" level, restoring coherent chunks of data like files or documents;<br />
* at the "strictly structured data" level, restoring (parts of) databases.<br />
<br />
When creating a Building Block Variant of this type, the next items are points of consideration:<br />
* Is the data being restored over another set of data? If so, are there special permissions needed?<br />
* Should access to the raw bits/files/database be blocked for other users than the Restore facility during the restore action?<br />
* What actions are necessary should a restore procedure abort?<br />
* Is there interrelation between (sets of) data that need to be maintained, e.g. by restoring interrelated data in a single restore action?<br />
* What level is needed for monitoring of the success or failure of any restore action, and of available restore capacity?<br />
* How often are restore tests needed?<br />
* How can clients request/execute restore actions on selected sets of data?<br />
{{FunctionIcon<br />
|image=Icon BBT Restore.png<br />
}}<br />
{{BBT Text Footer}}</div>Jan Schoonderbeek