StorNext File System
From Wikipedia, the free encyclopedia
 |
This article may require cleanup to meet Wikipedia's quality standards. Please discuss this issue on the talk page or replace this tag with a more specific message. This article has been tagged since April 2007. |
Quantum's StorNext
Data management software designed to streamline digital workflows and reduce data retention costs. StorNext creates a consolidated storage pool that multiple systems can access in parallel and achieve greater throughput and faster data sharing than possible with standard network attached storage architectures. StorNext also includes an integrated data movement engine that transparently migrates files between tiers of storage to reduce data retention costs and provide disaster recovery. StorNext is composed of two core components:
StorNext File System - provides data sharing functionality
StorNext Storage Manager - provides data movement functionality
[edit] See also
[edit] StorNext File System
StorNext File System is a heterogeneous shared file system that allows multiple servers to access a common disk repository. Servers - which can be Windows, SuSE, Red Hat, Mac OS-X (via Xsan), Solaris, Irix, HP-UX, and / or AIX - run StorNext client code which identifies and presents the disk repository as a local file system (e.g. your c:\ is a Windows file system). As far as applications know, the StorNext shared repository looks like any other direct attached storage volume.
Access a shared repository requires a "traffic cop" to manage and negotiate read / write operations. In StorNext, this function is performed using a MetaData Controller (MDC). The MDC is a server that sits outside the data path and is responsible for negotiating access and indicating the buffering mode the client should use (critical for allowing real-time parallel R/W operations to a single file). Clients communicate with the MDC to obtain information about file location, block allocation and then have direct, block level access to the disk - eliminating throughput bottlenecks associated with NAS.
At a physical level, a StorNext file system is composed of one or more LUNs that reside on one or more RAID devices depending on performance needs (in fact customers have design file systems to span across many controllers and arrays to provide throughputs exceeding 14 GBps).
In review, StorNext File System is used by customers to achieve 2 primary goals:
1. High throughput data operations (e.g. ingest, distribution, or access to large files)
2. Simple data sharing across OS platforms (eliminating slow, cumbersome LAN transfers)
[edit] StorNext Storage Manager
Storage Manager is an add on module to the StorNext File System which uses an integrated policy engine to migrate data to one or more archive repositories. This is done to reduce data retention costs and free up higher cost primary disk for utilization by the most current, actively used digital assets.
Storage Manager integrates tightly with the file system providing a value proposition that most other data movement products cannot provide: transparency - regardless of the client OS. Because StorNext is the core file system it manages all the detail of file location and can completely virtualize the location of a file, whether it is on disk, tape, NAS, or an offline storage vault.
Data movement policies occur in a three phase process as follows:
• Create archive cop(ies) of file at a designated time
• Mark copy of file on primary disk as candidate for truncation
• Remove file from primary storage so only archive cop(ies) remain
This structure enables rapid generation of file copies for data protection while still providing fast access to data via the copy on primary disk. Once files are no longer accessed on a regular basis, cost reduction is achieved by maintaining the file on lower cost storage that can still be accessed for content repurposing.
A critical component of the copy process is that multiple copies of a file can be generated (e.g. an onsite archive copy for user access and an offsite copy for disaster recovery). As a result, copies can be generated on tape disk (allows rapid retrieval and active archiving) and tape (tape media is extremely cost effective for long term storage). The copy process also includes an optional integrity check feature to guarantee that archived data has not been damaged or modified since its last access.
In review, Storage Manager is used by customers to achieve 2 primary goals:
1. Reduce data retention costs
2. Provide data protection
