CTE and Quantum StorNext Compatibility
The following sections list the supported operating systems and CTE settings supported for use with Quantum StorNext file systems. Important unsupported configuration parameters are also listed.
Supported StorNext Server and Client Configurations
The CTE integration with SNFS file systems works only with certain SNFS versions, SNFS storage policies, and client operating systems.
| Configuration parameter | Linux |
|---|---|
| StorNext (SNFS) operating system version | 6.x |
| StorNext metadata controller (MDC) server OS type | Linux MDC supported |
| StorNext replication policy | Not supported |
| StorNext deduplication policy | Not supported |
| StorNext truncation | Supported |
| StorNext full and partial backup | Supported |
| StorNext expand file system | Supported |
| StorNext data migration | Supported |
| StorNext read-ahead cache | Disable for use with CTE |
| Client operating systems | Red Hat Enterprise Linux (RHEL) 7.x |
| StorNext LAN client | DLC |
| StorNext mount method: locally mounted directory | Supported |
| StorNext mount method: CIFS | Not supported |
| StorNext mount method: NFS | Not supported |
Supported GuardPoint and Key Settings for SNFS File Systems
When configuring CTE GuardPoints and keys for SNFS, keep in the mind the compatibility limitations listed in the following table.
Note
Because AES-CBC-CS1 keys are not supported on Windows, do not create a policy on Linux that uses AES-CBC-CS1 keys if access to the same SNFS GuardPoint is required by both Windows and Linux LAN clients.
| Configuration element | Linux |
|---|---|
| Offline data transformation | Supported |
| Live Data Transformation (LDT)v | Not supported |
| Key manager compatibility | See the Compatibility Matrix for CTE Agent with Data Security Manager or the Compatibility Matrix for CTE Agent with Data Security Manager for your CTE version |
| Guard unstructured data | Supported |
| Guard structured data | Not supported |
| GuardPoint type: Directory (including entire SNFS volume) | Supported |
| GuardPoint type: Raw device | Not supported |
| GuardPoint type: Block device | Not supported |
| GuardPoint mount option: manual guard | Supported |
| GuardPoint mount option: auto guard | Supported |
| GuardPoint mount option: automount | Not supported |
| AES-CBC key type | Supported |
| AES-CBC-CS1 key type | Supported |
Supported Concurrent Access Read/Write Scenarios
If you want to allow access by multiple clients (users) to CTE-protected SNFS files under the same GuardPoint, just read-only access is supported. StorNext file locking is not implemented in CTE, so there is currently no way to prevent concurrent conflicting writes to the same file. As a result, Thales does not support write access to the same GuardPoint from multiple clients.
To enable read access to the same GuardPoint from multiple clients, ensure that all clients are configured to use the same policy and key.
| Configuration parameter | Linux |
|---|---|
| Read/write access from a single LAN client to a GuardPoint | Supported |
| Read/write access from two or more LAN clients to the same GuardPoint | Not supported |
| Read-only access from one, two, or more LAN clients to the same GuardPoint | Supported |
