HP BladeSystem tested configuration for Quantum StorNext 3.1
StorNext data management software streamlines digital workflow and reduces data retention costs by creating a consolidated storage pool where multiple systems can access SAN storage in parallel. This enables greater throughput and faster data sharing than is possible with standard network attached storage architectures. StorNext includes an integrated data movement engine that transparently moves files between different tiers of storage to reduce data retention costs and provide additional data protection. The StorNext suite is composed of two discrete components:
• StorNext File System – provides data sharing functionality
• StorNext Storage Manager – provides automated data movement
StorNext creates shared pools of images, media content, analytical data, and other key digital assets, which are made accessible across multiple operating systems. As a result, StorNext reduces storage costs and the expenses normally associated with digital asset retention. Particularly in server blade architectures, StorNext provides fast, effective data sharing of this consolidated storage pool for any servers mounting the file system. Even if they are running different operating systems, these server blades have access to the shared data pool and eliminate any performance bottlenecks normally associated with traditional, serialized, workflow processes.
Conceptually, the server blade environment appears to StorNext as a high-speed, networked, server architecture. As such, the software takes full advantage of the high-speed data throughput, reliability, and cost benefits of this architecture. Each server blade can be configured as a client on the file system, and using the StorNext Distributed LAN Client (DLC), servers in remote locations can access the file system using a LAN connection.
An option for StorNext is the High-Availability (HA) feature. Utilizing two separate servers as MetaData Controllers (MDCs) in an active/standby mode, StorNext offers the inherent redundancy of such a configuration. In the event of a power loss on the primary MDC the software would utilize the HP Integrated Lights-Out (iLO) feature to power off the faulty MDC and turn over control to the standby unit; all without a loss of data.
Get pdf HP BladeSystem tested configuration for Quantum StorNext 3.1
