Network Computing 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.

Long-Term Storage & Compliance: CAS Vs. Locked NAS: Page 2 of 7

Plasmon's ultra-density optical WORM disks, with a capacity of up to 60GB each, are state of the art for organizations seeking long media life. Like all WORM disks, they need WORM-aware archiving software to write to them. Plasmon's current archiving system, the Enterprise Active Archive, uses a server running Nexsan's Assureon NAS software as a front end. Data is typically written to a RAID array when initially stored, then migrated after 60 to 90 days as the rate of access falls off and long-term storage becomes more important than access time.

All of today's popular tape formats, from LTO in the midrange to Sun's T10000 at the high end, have firmware in the drive that identifies special WORM cartridges, and once data is written to them, prevents overwriting or erasure. With capacities of 800GB per cartridge, WORM tape, especially if used behind a RAID cache, is the lowest cost, and greenest, solution for very large archives where IT can deal with file access times measured in minutes. RAID or even MAID uses power when not being accessed. Optical disks take lots of floor space. High density and no need for power when not being accessed make tape the new green.

RELATED LINKS
bulletCisco Unveils Data Center 3.0: A Road Map Toward Making All Servers Virtual
The State of Data Backup Protection
Cheap disks and smoking bandwidth have changed the face of backup. In tandem with evolving technologies like de-duplication and more efficient use of VTLs, backup is hot. We explore new approaches to data archiving that won't bust your budget.

Contents Under Pressure
Rather than use a file's name and location in a hierarchy of directories as the primary identifier, as conventional file systems do, CAS systems generate a globally unique identifier, or GUID, for each file as it's saved using a hash function like MD-5 or SHA-1. The file is stored based on that GUID. If the CAS device provides a CIFS or NFS interface -- and most do -- it does a database lookup to find the GUID for the full file path, then uses the GUID to retrieve the file.