Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

6/3/2011
12:08 PM
George Crump
George Crump
Commentary
50%
50%

How To Design A 100 Year Data Retention Strategy

A cost effective hardware strategy is only the first step, a process and software strategy is vital to identifying for retention and moving it from primary storage.

100 years is a long time to retain anything let alone electronic data. While not everyone needs to retain data for that long, most organizations have retention needs at least in the seven to 10 year range. Most modern storage systems, however, are not designed to last more than five years, so how to create a storage strategy that can retain data for more than a century?

There are two components to a 100-year retention strategy. The first is to develop a hardware strategy that can cost effectively store that data for the next 100 years. The second is to develop a software and process strategy that will identify and move data to the retention storage area, ideally removing it from primary storage. I believe we need to be driving toward a data center where primary storage is small, fast, and only used for the most active set of data. Even at today's prices, many environments could be solid-state storage only for their primary tier.

I am specifically avoiding calling this storage area an archive tier. Using the term archive implies that this data will be moved to the archive, never to be accessed again. Thanks to initiatives like analytics, litigation management, and compliance, this data will be accessed and the system needs to be able to deliver that data in a timely manner relative to its age and no matter what all the data needs to be easily found.

This does not mean though that the disk tier needs to be disk only. I struggle with how organizations are going to afford to be able to keep 100 years of data on spinning disk. I don’t think all the power management and deduplication in the world is not going to make 100 years of disk only retention a reality. Additionally tape has overcome some of its challenges when it comes to use as a long term archive specifically in the form of the Long Term File System (LTFS) as we discuss in our article "What is LTFS?". The answer for the retention storage area is going to be a mixture of tape and disk.

The disk component needs to be a scaleable infrastructure where nodes of storage can be added to the disk area. More importantly, as we describe in our recent article "Building Affordable, Scalable Storage Infrastructures", these scaleable designs need to support mixed node types. This means nodes of varying disk capacity and processor types but still acting as one within the cluster. This is important because it allows for a rolling migration of storage nodes as equipment ages. Meaning that, over time, you can add new nodes with the latest processors and storage while at the same time gradually deactivating older nodes. This allows you to upgrade the cluster but not have to do a massive data migration, which, depending on the archive, may be almost impossible because of the capacity of the storage area.

The size of the disk component of this retention tier though should be kept at a reasonable level for what you need. Analytics (Big Data) will need to be larger because of the amount of data that needs to be scanned. Compliance and other forms of retention areas can have smaller disk areas but will still be large in comparison to primary storage. The fact that scale out systems can potentially scale to hundreds of nodes does not mean that you want to power, cool, and protect hundreds of nodes. At some point, and I know the disk guys won't like this, you really do need to push to tape. In the past, I have advocated for a disk only repository but LTFS in large part changes all that. I’ll explain why and how to use tape in this 100 year retention strategy in our next entry.

Follow Storage Switzerland on Twitter

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Storage Switzerland's disclosure statement.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
How Attackers Could Use Azure Apps to Sneak into Microsoft 365
Kelly Sheridan, Staff Editor, Dark Reading,  3/24/2020
Malicious USB Drive Hides Behind Gift Card Lure
Dark Reading Staff 3/27/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-10940
PUBLISHED: 2020-03-27
Local Privilege Escalation can occur in PHOENIX CONTACT PORTICO SERVER through 3.0.7 when installed to run as a service.
CVE-2020-10939
PUBLISHED: 2020-03-27
Insecure, default path permissions in PHOENIX CONTACT PC WORX SRT through 1.14 allow for local privilege escalation.
CVE-2020-6095
PUBLISHED: 2020-03-27
An exploitable denial of service vulnerability exists in the GstRTSPAuth functionality of GStreamer/gst-rtsp-server 1.14.5. A specially crafted RTSP setup request can cause a null pointer deference resulting in denial-of-service. An attacker can send a malicious packet to trigger this vulnerability.
CVE-2020-10817
PUBLISHED: 2020-03-27
The custom-searchable-data-entry-system (aka Custom Searchable Data Entry System) plugin through 1.7.1 for WordPress allows SQL Injection. NOTE: this product is discontinued.
CVE-2020-10952
PUBLISHED: 2020-03-27
GitLab EE/CE 8.11 through 12.9.1 allows blocked users to pull/push docker images.