Backups alone are not enough
April 25, 2010Poor policy management
No Standards or procedures
No indexing or search capabilities
Poor segmentation
Data is “clumped” on media haphazardly according to source time and place rather than according to policy
Data sharing the same media cannot be truly expired
Retrieval requests will bring back unrelated data
Unworkable as everything we need archives for…
Legal discovery process
Long-term retention
Distant-future recoverability
Consistency of data
Archiving Approaches
Traditional archiving
Point-in-time copy of set of related data
E.g., quarterly financials
Sometimes original data deleted after archive
The backup-archiving connection
Hierarchical Storage Management (HSM), NAS, SANs
Automated migration of data to lower cost storage or tape
Typically based on access-based file aging
Data migrated and a “stub” left in its place
File recalled to primary storage upon re-access
Active archiving (redirection)
Pointers to archived data
Supports single instance store
Data recalled without re-copy to primary store
Indexing and quick retrieval
Key Backup Considerations
Frequency – when, how often is an archiving copy to be taken
Retention – how long should the data be kept
Retrievability – drives access/search architecture
Taxonomy – indexing requirements for retrieval
Ingestion – what will be captured and when
Security – both physical (site) and logical (encryption)
Authentication – roles and responsibilities, access control
Immutability – requirement to demonstrate data is unchanged
Render options –is it to be transformed into information
Future proofing – common formats, pdf, xml
Refresh criteria – expiration of media life, platform life
Purge – when is archived data no longer required and how will it be destroyed
https://www.bestitdocuments.com/Samples