Content deleted Content added
Tag: gettingstarted edit |
Tag: gettingstarted edit |
||
Line 8:
StorNext has both software and hardware elements. On the front end, the filesystem is managed by usually two [[Metadata controller]]s, a primary and a failover or a metadata appliance. These MDC's act as the traffic director for the block-level filesystem with no data-overhead typically associated with [[NAS]] configured network shares.
Fibre Channel storage is the other key element of
Client systems are not required to run the same operating system to access a shared filesystem containing StorNext data. As of January 2008, the operating systems with available client software are [[Microsoft Windows]], [[Mac OS X]] (as [[Xsan]] developed by Apple), [[Red Hat Linux]], [[SuSE Linux]], [[HP-UX]], [[Solaris (operating system)|Solaris]], [[AIX]], and [[IRIX]]. Client systems can be attached either directly to the SAN or via an IP gateway, called a DLC (Distributed LAN Controller). Two or more DLCs can be configured for failover and/or load balancing. In some environments, users have used the DLC infrastructure to enable lower performance file sharing via NFS or CIFS. Using this capability, customers can create three tiers of front-end performance: SAN, native DLC, and NAS, all leveraging a common file sharing architecture.
Quantum offers customers two choices for infrastructure for StorNext: customized configurations, using the StorNext software on independently selected hardware; or, the use of the StorNext Appliances and Production Systems, a set of pre-configured solutions from Quantum which are said to be optimized for particular use cases (such as 4K editing). The latter solutions can include embedded technical support. <ref>www.stornext.com</ref>
| |||