Commentary

Dave Methvin
 

Petabyte Storage Hurdles Are Technical--And Maybe Political

On Monday, Ed Bott blogged about an interesting discovery he made in the vssadmin command-line tool that Vista uses to manage the System Restore and Shadow Copy features. That utility allows you to specify the reserved sizes in petabytes (1,000 terabytes) or exabytes (1,000 petabytes). Since the drive makers have just started pushing out 1-TB drives this year, is this just a former Boy Scout inside Microsoft who wants to be prepared?

On Monday, Ed Bott blogged about an interesting discovery he made in the vssadmin command-line tool that Vista uses to manage the System Restore and Shadow Copy features. That utility allows you to specify the reserved sizes in petabytes (1,000 terabytes) or exabytes (1,000 petabytes). Since the drive makers have just started pushing out 1-TB drives this year, is this just a former Boy Scout inside Microsoft who wants to be prepared?Ed wonders how long it will be before personal storage achieves petabyte stature. NTFS volumes top out at 256 TB, and an individual file is limited to 16 TB, so a new file format will be needed. Just like the FAT file system had to evolve from FAT16 to FAT32, we'll need to go from NTFS32 to NTFS64 when the drives get that big. Either that or we'll extend its life with crazy partitioning tricks like we did when FAT16 ran out of room.

Then there are questions about how to use, manage, and back up that much data. A hierarchical file system seems woefully underpowered to organize a petabyte of data. This is where WinFS might come in handy. Perhaps WinFS was too far ahead of its time, and we didn't need it desperately enough to appreciate what it could do. Give me a petabyte of data and I'll be begging for a better way to search and organize it. On the data security side, I have to assume that any petabyte-sized storage will use RAID redundancy to avoid catastrophic data loss in the event of a drive failure, and the Windows Previous Versions feature can protect against user accidents. Will future Internet connections be fast enough to do petabyte-sized off-site data backup?


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Beyond these technical and practical problems, though, I see the possibility of legal and political hurdles. The creators and distributors of "intellectual property" -- music, movies, books, and the like -- have waged open warfare with technology and had mixed results. Their battles against copiers and videotapes failed, but digital audio tape was killed in the early 1990s thanks to their efforts. Canadians pay a tax on CDs and DVDs, with the proceeds going to the industries that are supposedly hurt by illegal copying. Here in the United States, the DMCA has turned exercising your fair-use rights into a criminal act by making it illegal to circumvent even ineffective copy protection.

Let's say a high-quality MP3 is 10 MB, and a 90-minute high-definition video file is 1 GB. That petabyte of disk space will store 100 million songs, 1 million HD movies, or 1.5 million hours (nearly two continuous years) of off-the-air HD recording. You can keep your own private copy of anything -- no, make that everything. For comparison, Netflix only carries 100,000 DVD titles, so it's unlikely you'll be able to fill that drive with DVD titles alone.

To the MPAA and RIAA, a consumer with a petabyte of disk space has a weapon of mass business-model destruction. Companies threatened by this expanding consumer storage will find a way to kill or criminalize it. I can hear their arguments already: "Sure consumers have fair use, but any use of a petabyte of storage is inherently unfair!" I wouldn't bet against them getting their way.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links