Hard disk drives keep getting bigger, meaning capacity just keeps getting cheaper. But storage capacity is like money: The more you have, the more you use. And this growth in capacity means that data is at risk from a very old nemesis: Unrecoverable Read Errors (URE).
The Four Horsemen of storage system performance cannot be denied, but they do offer a clear path forward. Storage systems must improve in many different areas, from spindles and drives to caching and I/O bottlenecks. But above all else, storage systems must become smarter in order to become faster, and this requires greater insight into the true nature of the data stream being stored. All storage performance developments, from the laptop to the enterprise, boiled down to adaptations to the demands of the Four Horsemen.
The next version of Microsoft Windows Server includes integrated data deduplication technology. Microsoft is positioning this as a boon for server virtualization and claims it has very little performance impact. But how exactly does Microsoft’s de-duplication technology work?
It’s been a slow week (the holidays) and a crazy one. I’ve started pouring out the thin provisioning series, with 10 posts so far, as well as launching a new video “talk show” about enterprise IT. And I’ve got a new post over at SearchStorage, too. Whew!
I began by introducing the core problem: Storage isn’t getting any cheaper due to storage utilization and provisioning problems. Thin provisioning isn’t all it’s cracked up to be, since the telephone game makes de-allocation a challenge. So now let’s talk about how to make thin provisioning actually work.
My regular series resumes this week.
One of the daily hassles of using Apple Macintosh computers is the incompatibilities that arise with the broad Microsoft Windows world. Individual files often require conversion, but what about whole disks? Apple has long supported the universal and simplistic FAT filesystem, and added read-only support for NTFS back in 2003 in OS X 10.3 “Panther”. Third-party software like Paragon’s NTFS or the free NTFS-3G driver enabled read/write support, but a native solution was more desirable. Although 10.6 “Snow Leopard” includes NTFS write support, it is disabled by default. In this post, I’ll discuss methods for activating this native NTFS write support, as well as the pros and cons of doing so!
Microsoft already gave the world FAT and NTFS, and both have become common in the non-Windows world thanks to flash drives, SD cards, and portable disks. But the folks from Redmond are now introducing a new filesystem, exFAT. Do we really need a new filesystem?
Robocopy is the best tool to move data between NTFS filesystems but was never very quick. Windows Vista, Windows Server 2008, and later versions include a new version of Robocopy with performance tweaks including multi-threading that speed things up dramatically.
I’ve been using the NTFS-3G driver myself for quite some time. It works as advertised: Install it and you can read and write to NTFS-formatted drives with ease. These drives are integrated right into the Finder, appearing just like Mac-standard HFS+ disks. This is the method I used to assign custom drive icon for my Boot Camp volume and USB drives, for example.