Home > Storage > PowerScale (Isilon) > Product Documentation > Storage (general) > PowerScale OneFS: Long Filename Support > Overview
Long filename support co-exists with most other OneFS data services. The exceptions are ICAP anti-virus, as noted in the following table, and SyncIQ replication, which entails meeting the prerequisites described in SyncIQ requirements for long filenames. The following table describes the integration, influence, and compatibility between inline data reduction and the various OneFS data services:
OneFS feature | Detail |
SyncIQ | |
NDMP Backup | Long filename backup and restore are supported and work as expected on clusters running OneFS 9.3 and later. Restoring data from a OneFS 9.3 or later backup containing long filenames to earlier OneFS versions fails with an ENAMETOOLONG error for the long-named files. However, files with regular-length names are restored from the backup stream successfully. |
SnapshotIQ | Filename length and/or directory name length does not affect the data stored in a snapshot. SnapshotIQ will successfully capture a snapshot of a dataset that contains long filenames and or long directory pathnames. Similarly, the SnapRestore job will successfully restore a snapshot containing long names. |
SmartLock | Long filenames are fully compatible with SmartLock, the OneFS data retention and compliance product. Long filename support provides additional flexibility to OneFS immutable archives and write once, read many (or WORM) protected datasets. |
SED Encryption | Clusters employing encryption with SED drives are fully compatible with long filenames. |
SmartQuotas | OneFS SmartQuotas is one of the principal methods for inline data reduction efficiency reporting. From the quota side, long-named files are reported on and acted on as expected in configured quota policies. |
SmartPools | Long filenames and SmartPools tiering are fully compatible with each other. |
CloudPools | CloudPools cloud tiering fully supports long filenames. When tiered, the data associated with a long-named file is moved to a cloud provider, and stub file reference is created locally. |
Non-disruptive Upgrade | Long filename support was introduced in OneFS 9.3.0. Non-disruptive upgrade to a later release is fully supported. Files with long filenames cannot be created on the cluster until OneFS 9.3 or later has been committed to the cluster. |
File Clones | File cloning, and the underlying shadow stores, fully support long filenames. |
In-line Data Reduction | In-line data reduction, including compression, deduplication, and single instancing, are fully compatible with long names. |
SmartDedupe | SmartDedupe post-process deduplication and long filenames are fully compatible with each other. |
Small File Storage Efficiency (SFSE) | Long filenames co-exist with OneFS small file storage efficiency (SFSE) features, including both containerized small files and files that store inline in inodes. |
Job Engine | The job engine and associated restriping jobs all fully support long filenames. |
InsightIQ and DataIQ | InsightIQ and DataIQ both support and accurately report on OneFS long names. |
Anti-virus | While ICAP does not support LFN, its replacement, CAVA, does support long filenames. |
Except for the job engine, file clones, and non-disruptive upgrade (NDU), each of the services that are listed in Table 6 require a product license or specific hardware. Licensed data services are not enabled, configured, or active by default on a cluster.