A file system interface to CAStor
CAStor FSG provides legacy applications with instant access to CAStor through familiar CIFS (Common Interface File System) and NFS (Network File System) protocols. Simply mount a file share, set your policy constraints and point your application to the share. The result is freedom from vendor-proprietary hardware and a lower total cost of ownership.
Industry standard access protocols
CAStor FSG is not a file system, but a database driven, thin mapping layer that provides instant access to CAStor for applications that interface to CIFS or NFS. No changes are required to the applications and the customer receives the full value of CAStor without any additional work. Unix/Linux users can mount CAStor FSG as a network drive via NFS. Windows users can map a Windows network drive via CIFS (the CAStor Cluster looks like a Windows file system). Mac OS X users can do both. CAStor FSG Product Sheet .pdf
CAStor FSG Features:
- Policies such as retention, number of replicas and lifepoints can be set per share
- Once a file has been written to CAStor, all replication, policy management, integrity and storage is managed automatically by CAStor. This allows multiple applications to use CAStor as a storage layer and they can all defer the compliance and integrity of the content to CAStor. Many applications, many sources, one repository with guaranteed integrity.
- No limit to the size or number of files
- The database in CAStor FSG contains the OS file metadata and the mapping between the file name and the Unique ID (UUID) in CAStor as well as additional useful information. The database can be queried with standard SQL queries to discover information such as the file name, the UUID mapped to the file, last access, last modification, permissions, file size and type and the user ID.
- Content stored in CAStor through the gateway can be accessed via applications and UUIDs interchangeably. There is no requirement for only one type of interface. CAStor FSG can surface multiple virtual views into a single content store.
- CAStor FSG is multi-threaded and uses connection pooling for scalability and performance. CAStor FSG automatically takes advantage of the multiple contact points in CAStor as your Cluster scales up. The connections to each node can remain open and multiple threads can be spun on each connection. The scalability and throughput of CAStor become accessible to legacy applications without changing a line of code.
- MySql and Oracle are supported out of the box.
- CAStor FSG can operate in a standalone fashion or may be integrated with your existing user directories, using standard authentication methods such as NTLMSSP, SPNEGO, NTLMv2 and Active Directory/Kerberos.
|
|
Manage the lifecycle of your content
CAStor FSG enables admins to set policies, permissions, and constraints for content storage to meet internal goals and/or to assure regulatory compliance. Once these policies are configured, CAStor transparently monitors data and enforces these policies, ensuring the correct number of replicas for a particular file, verifying file lifecycle information and managing secure deletion.
Uses industry standard access protocols
Classic file system mapping provides a virtual file system front end to CAStor that users can access through standard network file systems and protocols. Once the content and reference information has been stored in CAStor it can be accessed directly through Simple Content Storage Protocol (SCSP) (CAStor's HTTP 1.1 subset) using the UUID's stored in the database, or as files in a regular file system. This allows for phased migration strategies to a native CAStor interface and all the benefits derived.
|
|
email us © Copyright 2008 Caringo, Inc. All rights reserved.
