Skip to main content

An Exabyte sounds like a lot

Recently I was watching Ocean’s 13 which passed the time reasonably pleasantly.  There was a supposedly awesome computer which our handsome heroes had to overcome called “The Greco”.  Apparently it stored its data “in a field of Exabytes”.

This got me thinking about all the different storage metrics and the fact many of us can get them confused.  I decided to pop the following list down for your viewing pleasure…

Name Abbreviation Amount
bit b Fundamental unit of data storage
Nibble   4 bits
Byte B 8 bits
Kilobyte kB 1024 Bytes
Megabyte MB 1024 Kilobytes
Gigabyte GB 1024 Megabytes
Terabyte TB 1024 Gigabytes
Petabyte PB 1024 TB
Exabyte EB 1024 PB

An Exabyte is seriously huge!  If you take it that DVD quality video requires a bandwidth of around 5Mbits/s plus about 0.45Mbits/s for its audio that gives a total bandwidth of 5.45Mbits/s.  This equals 0.68MB/s.  Now an Exabyte is a million million MB so divide that by 0.68, then by 60, then by 24, and finally by 365 and the answer is:

An Exabyte would be able to store 46,632 hours of playback time!!

Comments

Anonymous said…
So, when in 2007 the first 1TB harddisk was announced, this computer already had a million of them connected :)

Popular posts from this blog

Where are SCANPST.EXE and/or SCANOST.EXE?

I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...