GP.Data Protection+Archive Management - Revision history

Jan Schoonderbeek: fixed syntax error

2013-08-15T07:03:18Z

fixed syntax error

← Older revision		Revision as of 07:03, 15 August 2013
Line 12:		Line 12:
	Finally, clients of this Pattern can control the way in which it operates using Controlling. This function is also responsible for creating and maintaining the rule base and the corresponding schedules. It is also advised to maintain requirements surrounding the client interface to the restore functionality and to the archive under this function.		Finally, clients of this Pattern can control the way in which it operates using Controlling. This function is also responsible for creating and maintaining the rule base and the corresponding schedules. It is also advised to maintain requirements surrounding the client interface to the restore functionality and to the archive under this function.
	Finally, Logging functionality can be explicitly included in the pattern, since logging information is likely to be required for auditing purposes for either backup creation, archive creation, and the uses that clients make of thiese backups and archives.		Finally, Logging functionality can be explicitly included in the pattern, since logging information is likely to be required for auditing purposes for either backup creation, archive creation, and the uses that clients make of thiese backups and archives.




	~~{{Generic Pattern Composition Row}}~~
	{{Pattern Realizes		{{Pattern Realizes
	\|service=GS.Data Protection Management		\|service=GS.Data Protection Management

Jan Schoonderbeek: made data repl optional

2013-08-15T07:02:09Z

made data repl optional

← Older revision		Revision as of 07:02, 15 August 2013
Line 16:		Line 16:


	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row}}
	{{Pattern Realizes		{{Pattern Realizes
	\|service=GS.Data Protection Management		\|service=GS.Data Protection Management
Line 25:		Line 25:
	{{Pattern Graphic		{{Pattern Graphic
	\|graphic=GP.Data Protection+Archive Management.png		\|graphic=GP.Data Protection+Archive Management.png
	\|size=~~656px~~		\|size=694px
			\|title=Generic Pattern Data Protection & Archive Management
	}}		}}
	{{Generic Pattern Composition}}		{{Generic Pattern Composition}}
Line 40:		Line 41:
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Data Replication		\|function=GF.Data Replication
	\|choice=~~Must~~		\|choice=May
	\|reason=This function carries out the task of creating secondary copies of the data set to be protected, or primary copies of data to be archived. To this end, it needs access to the data to be protected/archived, and also access to a storage location that can hold the copy of the data. If this function creates an archive, it can also be tasked with deleting the data from the original location.		\|reason=This function carries out the task of creating secondary copies of the data set to be protected, or primary copies of data to be archived. To this end, it needs access to the data to be protected/archived, and also access to a storage location that can hold the copy of the data. If this function creates an archive, it can also be tasked with deleting the data from the original location.
	}}		}}

Jan Schoonderbeek: adjacency specified

2013-07-18T09:06:54Z

adjacency specified

← Older revision		Revision as of 09:06, 18 July 2013
Line 2:		Line 2:
	{{Pageheaderbox4GP		{{Pageheaderbox4GP
	\|name=Data Protection & Archive Management		\|name=Data Protection & Archive Management
			\|sector=Operations
	\|version=0.1		\|version=0.1
	\|owner=J.A.H. Schoonderbeek		\|owner=J.A.H. Schoonderbeek
	~~\|sector=Operations~~
	\|summary=This Pattern can help to realize a level of data protection for sets of data and/or convert these sets into archives.		\|summary=This Pattern can help to realize a level of data protection for sets of data and/or convert these sets into archives.
	}}		}}
Line 12:		Line 12:
	Finally, clients of this Pattern can control the way in which it operates using Controlling. This function is also responsible for creating and maintaining the rule base and the corresponding schedules. It is also advised to maintain requirements surrounding the client interface to the restore functionality and to the archive under this function.		Finally, clients of this Pattern can control the way in which it operates using Controlling. This function is also responsible for creating and maintaining the rule base and the corresponding schedules. It is also advised to maintain requirements surrounding the client interface to the restore functionality and to the archive under this function.
	Finally, Logging functionality can be explicitly included in the pattern, since logging information is likely to be required for auditing purposes for either backup creation, archive creation, and the uses that clients make of thiese backups and archives.		Finally, Logging functionality can be explicitly included in the pattern, since logging information is likely to be required for auditing purposes for either backup creation, archive creation, and the uses that clients make of thiese backups and archives.
	~~{{Pattern Graphic~~
	~~\|graphic=GP.Data Protection+Archive Management.png~~
	~~\|source=~~
	~~\|size=656px~~
	}}		{{Generic Pattern Composition Row
	{{Pattern Realizes		{{Pattern Realizes
	\|service=GS.Data Protection Management		\|service=GS.Data Protection Management
Line 22:		Line 22:
	{{Pattern Realizes		{{Pattern Realizes
	\|service=GS.Archive Management		\|service=GS.Archive Management
			}}
			{{Pattern Graphic
			\|graphic=GP.Data Protection+Archive Management.png
			\|size=656px
	}}		}}
	{{Generic Pattern Composition}}		{{Generic Pattern Composition}}
	~~{{Generic Pattern Composition Row~~
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Rules Engine		\|function=GF.Rules Engine
Line 69:		Line 72:
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Raw Storage		\|service=GS.Raw Storage
	\|choice=~~may~~		\|choice=May
	\|reason= this service provides access to the actual data to be protected, as well as storage space for the actual backups and archives.		\|reason=this service provides access to the actual data to be protected, as well as storage space for the actual backups and archives.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.File Storage		\|service=GS.File Storage
	\|choice=~~may~~		\|choice=May
	\|reason=this service provides access to the actual data to be protected or archived, as well as storage space for the actual backups and archives. Furthermore, it may be used to model the storage of backup/archive rules, schedules and logs.		\|reason=this service provides access to the actual data to be protected or archived, as well as storage space for the actual backups and archives. Furthermore, it may be used to model the storage of backup/archive rules, schedules and logs.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Data Management		\|service=GS.Data Management
	\|choice=~~may~~		\|choice=May
	\|reason=this service provides access to the actual data to be protected or archived. It may also be used as storage space for the actual backups and archives. Furthermore, it may be used to model the storage of backup/archive rules, schedules and logs.		\|reason=this service provides access to the actual data to be protected or archived. It may also be used as storage space for the actual backups and archives. Furthermore, it may be used to model the storage of backup/archive rules, schedules and logs.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Authentication+Authorization		\|service=GS.Authentication+Authorization
	\|choice=~~may~~		\|choice=May
	\|reason=Log events, especially those concerned with the success or failure of backup or archiving actions, may need to be monitored (locally or centrally)		\|reason=Log events, especially those concerned with the success or failure of backup or archiving actions, may need to be monitored (locally or centrally)
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Facilities Monitoring		\|service=GS.Facilities Monitoring
	\|choice=~~may~~		\|choice=May
	\|reason=Whether data is copied to a backup or moved to an archive, the Operations department must ensure that the action is successful. To that end, Monitoring is required. Furthermore, unauthorized access to the configuration or the files of a backup or archive is a security issue that needs to be recorded as well.		\|reason=Whether data is copied to a backup or moved to an archive, the Operations department must ensure that the action is successful. To that end, Monitoring is required. Furthermore, unauthorized access to the configuration or the files of a backup or archive is a security issue that needs to be recorded as well.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
	{{Text Footer GP}}		{{Text Footer GP}}

Jan Schoonderbeek: GP added

2013-07-16T07:36:57Z

GP added

New page

{{Maturity|2}}
{{Pageheaderbox4GP
|name=Data Protection & Archive Management
|version=0.1
|owner=J.A.H. Schoonderbeek
|sector=Operations
|summary=This Pattern can help to realize a level of data protection for sets of data and/or convert these sets into archives.
}}
This Pattern contains the main functionality required to realize a level of data protection for sets of data and/or convert these sets into archives. For this, the Pattern mainly relies on a Rules Engine that controls all actions concerning the creation of backups and archives, as well as actions concerning the restoring of a backup or consultation of an archive. Note that functionality surrounding the management of backup and archive metadata is not included in the Pattern, nor is the functionality surrounding the storage of the rules processed by the Rules Engine - however, these can be provided by an instance of adjacent Pattern Data Management.
In order to create the backups and archives, the Data Replication function is used. When using this function, the question is if the data replicated remains at the original location, in which case the action results in a backup, or is deleted, in which case the data is effectively migrated, and results in an archive. The Rules Engine may be supported by a Scheduling function to make use of timed schedules. Furthermore, backups that are not full secondary copies of the production data can be created using the Data State Preservation function.
If this Pattern is to provide Data Protection, then the Pattern needs to be able to restore data to the original and/or alternative locations - functionality that can be provided by the Restore function. If this Pattern is to secure Archives, then there needs to be a way for the clients to peruse the archive - which the Presentation Engine can provide.
Finally, clients of this Pattern can control the way in which it operates using Controlling. This function is also responsible for creating and maintaining the rule base and the corresponding schedules. It is also advised to maintain requirements surrounding the client interface to the restore functionality and to the archive under this function.
Finally, Logging functionality can be explicitly included in the pattern, since logging information is likely to be required for auditing purposes for either backup creation, archive creation, and the uses that clients make of thiese backups and archives.
{{Pattern Graphic
|graphic=GP.Data Protection+Archive Management.png
|source=
|size=656px
}}
{{Pattern Realizes
|service=GS.Data Protection Management
}}
{{Pattern Realizes
|service=GS.Archive Management
}}
{{Generic Pattern Composition}}
{{Generic Pattern Composition Row
{{Generic Pattern Composition Row
|function=GF.Rules Engine
|choice=Must
|reason=This function models the central intelligence of a Data Protection/Archive Management facility. It accepts input from clients, from the Scheduling function, and/or from a rule base, in order to initiate and complete activities that help protect data. It mainly uses Data Replication (and Data State Preservation, if available) to protect the data set(s) entrusted to it. When needed, it can use Restore to recover from a data incident, or Presentation Engine to allow access to archived data.
}}
{{Generic Pattern Composition Row
|function=GF.Scheduling
|choice=May
|reason=If (backup/archive/restore/other) actions are to be taken at predetermined times and/or schedules, then this function triggers the central functionality accordingly.
}}
{{Generic Pattern Composition Row
|function=GF.Data Replication
|choice=Must
|reason=This function carries out the task of creating secondary copies of the data set to be protected, or primary copies of data to be archived. To this end, it needs access to the data to be protected/archived, and also access to a storage location that can hold the copy of the data. If this function creates an archive, it can also be tasked with deleting the data from the original location.
}}
{{Generic Pattern Composition Row
|function=GF.Data State Preservation
|choice=May
|reason=To protect against less severe data corruption events, it may be convenient to use this function, as in most scenarios it requires less storage space to protect the data, and also allows for quicker restore.
}}
{{Generic Pattern Composition Row
|function=GF.Restore
|choice=May
|reason="Nobody cares if you can backup, only if you can restore". This function can take care of just that. After an incident that corrupted data has occurred, it can recreate the data in the state that it was in at a prior point in time, making use of the corresponding secondary copy of that data, and the access and permissions that it is provided to the location where the data is to be restored. This function may also need to delete or overwrite the corrupted data.
}}
{{Generic Pattern Composition Row
|function=GF.Presentation Engine
|choice=May
|reason=If the Pattern is used to manage archiving, then this function ensures that clients can consult the archive, by presenting them a view on the archived data.
}}
{{Generic Pattern Composition Row
|function=GF.Controlling
|choice=Must
|reason=The function that allows (authorized) clients to change the backup settings, archive parameters et cetera.
}}
{{Generic Pattern Composition Row
|function=GF.Logging
|choice=May
|reason=If the Pattern is to report its backup and/or archive status, this function is essential, as it can record how the backup and restore actions progressed, and which identities accessed the archive/backup data.
}}
{{Table Ending}}
{{Pattern Adjacent Services}}
{{Generic Pattern Adjacent Service Row
|service=GS.Raw Storage
|choice=may
|reason= this service provides access to the actual data to be protected, as well as storage space for the actual backups and archives.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.File Storage
|choice=may
|reason=this service provides access to the actual data to be protected or archived, as well as storage space for the actual backups and archives. Furthermore, it may be used to model the storage of backup/archive rules, schedules and logs.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Data Management
|choice=may
|reason=this service provides access to the actual data to be protected or archived. It may also be used as storage space for the actual backups and archives. Furthermore, it may be used to model the storage of backup/archive rules, schedules and logs.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Authentication+Authorization
|choice=may
|reason=Log events, especially those concerned with the success or failure of backup or archiving actions, may need to be monitored (locally or centrally)
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Facilities Monitoring
|choice=may
|reason=Whether data is copied to a backup or moved to an archive, the Operations department must ensure that the action is successful. To that end, Monitoring is required. Furthermore, unauthorized access to the configuration or the files of a backup or archive is a security issue that needs to be recorded as well.
}}
{{Table Ending}}
{{Text Footer GP}}