Backup: Difference between revisions - Wikipedia

Line 29:

===Information repository models===

Any backup strategy starts with a concept of an [[information repository]], "a secondary storage space for data".<ref name="wiseGEEKInformationRepository">{{cite web |last1=McMahon |first1=Mary |title=What Is an Information Repository? |url=https://www.wisegeek.com/what-is-an-information-repository.htm

|website=wiseGEEK |publisher=Conjecture Corporation |accessdate=8 May 2019 |date=1 April 2019

|quote=In the sense of an approach to data management, an information repository is a secondary storage space for data.}}</ref> The backup data needs to be stored, so part of the model is the [[backup rotation scheme]].<ref name=Kissell/> The repository must be methodical to a degree; the method could be as simple as a sheet of paper with a list of all backup media (CDs, etc.) and the dates they were produced. A more sophisticated method could include a computerized index, catalog, or [[relational database]]. Different backup methods have different advantages:

====Information repository====

{{other uses|Knowledge base}}

In '''information''' technology, a '''repository''' is "a central place in which an aggregation of data is kept and maintained in an organized way, usually in computer storage."<ref name="WhatIsInformationRepository">{{cite web |last1=Rouse |first1=Margaret |title=Definition: repository |url=https://searchoracle.techtarget.com/definition/repository |website=whatis.com |publisher=TechTarget |accessdate=1 May 2019 |date=April 2005}}</ref> It "may be just the aggregation of data itself into some accessible place of storage or it may also imply some ability to selectively extract data."<ref name="WhatIsInformationRepository" />

==Federated information repository==

A '''federated information repository''' is an easy way to deploy a secondary tier of [[data storage device|data storage]] that can comprise multiple, networked data storage technologies running on diverse [[operating system]]s, where data that no longer needs to be in primary storage is protected, classified according to captured [[metadata]], processed, de-duplicated, and then purged, automatically, based on data service level objectives and requirements. In federated information repositories, data storage resources are virtualized as composite storage sets and operate as a [[Federation (information technology)|federated]] environment.<ref name="SNIA2007BenefitsFederated Information Repository">{{cite web |last1=Armstrong |first1=Mark |title=Benefits of a Federated Information Repository as a Secondary Storage Tier |url=https://web.archive.org/web/20081121202134/http://www.enterpriseinformationworld.com/abstracts/benefits_federated_info.htm |website=SNIA Enterprise Information World 2007 Conference |publisher=Storage Networking Industry Association (SNIA) |accessdate=1 May 2019 |date=9 August 2007}}</ref>

Federated information repositories were developed to mitigate problems arising from [[data proliferation]] and eliminate the need for separately deployed data storage solutions because of the concurrent deployment of diverse storage technologies running diverse operating systems. They feature centralized management for all deployed data storage resources. They are self-contained, support heterogeneous storage resources, support resource management to add, maintain, recycle, and terminate media, track of off-line media, and operate autonomously.<ref name="SoleraTecPhoenixRSM">{{cite web |title=Area Under Surveillance |url=https://www.soleratec.com/solutions/surveillance/ |website=SoleraTec |publisher=SoleraTec LLC |accessdate=6 May 2019 |at=Phoenix RSM: (Record, Store, Manage), Surveillance Video Management (information repository), Ultra-fast Search and Playback (content-based search queries) |date=2019}}</ref>

===Automated data management===

Since one of the main reasons for the implementation of an federated nformation repository is to reduce the maintenance workload placed on IT staff by traditional data storage systems, federated information repositories are automated. Automation is accomplished via policies that can process data based on time, events, data age, and data content. Policies manage the following:

*File system space management

*Irrelevant data elimination (mp3, games, etc.)

*Secondary storage resource management

Data is processed according to media type, [[Storage virtualization|storage pool]], and [[data storage device|storage technology]].

Because federated information repositories are intended to reduce IT staff workload, they are designed to be easy to deploy and offer configuration flexibility, virtually limitless extensibility, redundancy, and reliable failover.

===Data recovery===

Federated information repositories feature robust, client based data search and recovery capabilities that, based on permissions, enable end users to search the information repository, view information repository contents, including data on off-line media, and recover individual files or multiple files to either their original [[Computer network|network]] computer or another network computer.<ref name="SoleraTecPhoenixRSM" />

{{DEFAULTSORT:Information Repository}}

[[Category:Information technology management|*]]

[[Category:Content management systems|*]]

[[Category:Data management]]

[[Category:Data security]]

[[Category:Records management]]

; Unstructured : An unstructured repository may simply be a stack of tapes or CD-Rs or DVD-Rs with minimal information about what was backed up and when. This is the easiest to implement, but probably the least likely to achieve a high level of recoverability as it must lack automation.