GF.Retention Engine - Revision history

Jan Schoonderbeek: another link fix

2013-10-02T06:59:11Z

another link fix

← Older revision		Revision as of 06:59, 2 October 2013
Line 7:		Line 7:
	\|summary=This function offers intelligent handling of data at the "unstructured data" abstraction level.		\|summary=This function offers intelligent handling of data at the "unstructured data" abstraction level.
	}}		}}
	A Retention Engine function presents data retention functionality beyond the four basic operations (store/retrieve/modify/delete). It can thus be seen as "adding storage intelligence" to [[GP.~~Raw Retention~~\|Raw Retention]] functionality, which itself provides the basic storage operations. However, this intelligence can be characterized as "back-end facing": generally speaking the facility's consumers don't have (direct) access to it, only the administrators and back-end systems.		A Retention Engine function presents data retention functionality beyond the four basic operations (store/retrieve/modify/delete). It can thus be seen as "adding storage intelligence" to [[GF.Raw_Retention\|Raw Retention]] functionality, which itself provides the basic storage operations. However, this intelligence can be characterized as "back-end facing": generally speaking the facility's consumers don't have (direct) access to it, only the administrators and back-end systems.

	When present, the Retention Engine is positioned "between" the Raw Retention functionality and the consumers that want to retain data or manipulate retained data. This means that the consumers cannot "see" the data stored by the Raw Retention functionality directly. Instead, they "see" data as the Retention Engine presents it to them, while the data that's actually stored on the Raw Retention facility may be different (e.g. split in different blocks and augmented with parity blocks, as happens when storing data on a RAID-5 storage device).		When present, the Retention Engine is positioned "between" the Raw Retention functionality and the consumers that want to retain data or manipulate retained data. This means that the consumers cannot "see" the data stored by the Raw Retention functionality directly. Instead, they "see" data as the Retention Engine presents it to them, while the data that's actually stored on the Raw Retention facility may be different (e.g. split in different blocks and augmented with parity blocks, as happens when storing data on a RAID-5 storage device).

Jan Schoonderbeek: link fix

2013-10-02T06:58:30Z

link fix

← Older revision		Revision as of 06:58, 2 October 2013
Line 18:		Line 18:
	* snapshotting;		* snapshotting;
	* meta-data reporting (e.g. space left on a physical or logical device).		* meta-data reporting (e.g. space left on a physical or logical device).
	Furthermore, the Retention Engine function may handle integration with other storage-related facilities, such as [[GP.~~Data Protection and Archive Management~~\|Data Protection ~~and~~ Archive Management]].		Furthermore, the Retention Engine function may handle integration with other storage-related facilities, such as [[GP.Data_Protection%2BArchive_Management\|Data Protection & Archive Management]].

	Note that the storage intelligence that the Retention Engine brings acts on the lowest abstraction level for data, that of [[OIAm_data_view\|"Unstructured Data"]], managing sets of basic data elements, such as the bits and bytes on a hard disk.		Note that the storage intelligence that the Retention Engine brings acts on the lowest abstraction level for data, that of [[OIAm_data_view\|"Unstructured Data"]], managing sets of basic data elements, such as the bits and bytes on a hard disk.
	{{FunctionIcon		{{FunctionIcon
	\|image=Icon GF Retention Engine.png		\|image=Icon GF Retention Engine.png
	}}		}}
	{{Text Footer GF}}		{{Text Footer GF}}

Jan Schoonderbeek: slight text update

2013-10-02T06:57:34Z

slight text update

← Older revision		Revision as of 06:57, 2 October 2013
Line 7:		Line 7:
	\|summary=This function offers intelligent handling of data at the "unstructured data" abstraction level.		\|summary=This function offers intelligent handling of data at the "unstructured data" abstraction level.
	}}		}}
	A Retention Engine ~~facility~~ presents data retention functionality beyond the four basic operations (store/retrieve/modify/delete). It can thus be seen as "adding storage intelligence" to [[GF.Raw Retention\|Raw Retention]] functionality, which itself provides the basic storage operations. However, this intelligence can be characterized as "back-end facing": generally speaking the facility's ~~clients~~ don't have (direct) access to it, only the administrators and back-end systems.		A Retention Engine function presents data retention functionality beyond the four basic operations (store/retrieve/modify/delete). It can thus be seen as "adding storage intelligence" to [[GP.Raw Retention\|Raw Retention]] functionality, which itself provides the basic storage operations. However, this intelligence can be characterized as "back-end facing": generally speaking the facility's consumers don't have (direct) access to it, only the administrators and back-end systems.

	When present, the Retention Engine is positioned "between" the Raw Retention functionality and the ~~clients~~ that want to retain data or manipulate retained data. This means that the ~~clients~~ cannot "see" the data stored by the Raw Retention functionality directly. Instead, they "see" data as the Retention Engine presents it to them, while the data that's actually stored on the Raw Retention facility may be different (e.g. split in different blocks and augmented with parity blocks, as happens when storing data on a RAID-5 storage device).		When present, the Retention Engine is positioned "between" the Raw Retention functionality and the consumers that want to retain data or manipulate retained data. This means that the consumers cannot "see" the data stored by the Raw Retention functionality directly. Instead, they "see" data as the Retention Engine presents it to them, while the data that's actually stored on the Raw Retention facility may be different (e.g. split in different blocks and augmented with parity blocks, as happens when storing data on a RAID-5 storage device).

	Examples of Retention Engine operations are:		Examples of Retention Engine operations are:
Line 17:		Line 17:
	* thin provisioning;		* thin provisioning;
	* snapshotting;		* snapshotting;
	* meta-data reporting (e.g. space left on a physical or logical device).		* meta-data reporting (e.g. space left on a physical or logical device).
	Furthermore, the Retention Engine ~~facility~~ may handle integration with other storage-related facilities, such as [[GF.~~Backup~~\|~~Backup]]~~ and ~~[[GF.Restore\|Restore~~]].		Furthermore, the Retention Engine function may handle integration with other storage-related facilities, such as [[GP.Data Protection and Archive Management\|Data Protection and Archive Management]].

	Note that the storage intelligence that the Retention Engine brings acts on the lowest abstraction level for data, that of "Unstructured Data", ~~manipulating~~ sets of ~~elementary~~ data elements, such as the bits and bytes on a hard disk.		Note that the storage intelligence that the Retention Engine brings acts on the lowest abstraction level for data, that of [[OIAm_data_view\|"Unstructured Data"]], managing sets of basic data elements, such as the bits and bytes on a hard disk.
	{{FunctionIcon		{{FunctionIcon
	\|image=Icon GF Retention Engine.png		\|image=Icon GF Retention Engine.png
	}}		}}
	{{Text Footer GF}}		{{Text Footer GF}}

Jan Schoonderbeek: GF created

2013-03-31T09:16:54Z

GF created

New page

{{Maturity|4}}
{{Pageheaderbox4GF
|name=Retention Engine
|WorkingArea=Storage
|version=0.92
|owner=J.A.H. Schoonderbeek
|summary=This function offers intelligent handling of data at the "unstructured data" abstraction level.
}}
A Retention Engine facility presents data retention functionality beyond the four basic operations (store/retrieve/modify/delete). It can thus be seen as "adding storage intelligence" to [[GF.Raw Retention|Raw Retention]] functionality, which itself provides the basic storage operations. However, this intelligence can be characterized as "back-end facing": generally speaking the facility's clients don't have (direct) access to it, only the administrators and back-end systems.

When present, the Retention Engine is positioned "between" the Raw Retention functionality and the clients that want to retain data or manipulate retained data. This means that the clients cannot "see" the data stored by the Raw Retention functionality directly. Instead, they "see" data as the Retention Engine presents it to them, while the data that's actually stored on the Raw Retention facility may be different (e.g. split in different blocks and augmented with parity blocks, as happens when storing data on a RAID-5 storage device).

Examples of Retention Engine operations are:
* adding and handling data redundancy;
* data integrity checking on retrieval/modification;
* data replication (usually to another instance of a Retention Engine);
* thin provisioning;
* snapshotting;
* meta-data reporting (e.g. space left on a physical or logical device).
Furthermore, the Retention Engine facility may handle integration with other storage-related facilities, such as [[GF.Backup|Backup]] and [[GF.Restore|Restore]].

Note that the storage intelligence that the Retention Engine brings acts on the lowest abstraction level for data, that of "Unstructured Data", manipulating sets of elementary data elements, such as the bits and bytes on a hard disk.
{{FunctionIcon
|image=Icon GF Retention Engine.png
}}
{{Text Footer GF}}