Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Configuring Veritas Access to work with Oracle Direct NFS
- Configuring an FTP server
- Configuring your NFS server
- Section V. Managing the Veritas Access Object Store server
- Section VI. Monitoring and troubleshooting
- Section VII. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Configuring cloud storage
- Section IX. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring Veritas Access with the NetBackup client
- Section XI. Reference
Erasure coding in a cluster file system (CFS) for NFS use case
Erasure coding is configured with the EC log option for NFS use case. The CFS erasure-coded file system for NFS can be created using the Erasure Coded Storage Policy in the Veritas Access GUI and also through the Veritas Access CLISH.
See the Veritas Access Online Help for more information on the Erasure Coded Storage Policy.
CFS erasure-coded file system for NFS use case can be created through Veritas Access using the following command:
Storage> fs create ecoded fs_name size ncolumns nparity pool1 [, disk1,...] [blksize=<bytes>][stripeunit=<kilobytes>] [encrypt={on|off}] [stripe_aligned={yes|no}] [stripe_tag={node|disk}] [rotating_parity= {yes|no}] [single_volume={yes|no}] [ecloglen={200M|500M|1G|2G|5G}] [disk1 [, disk2,...]] [workload={virtualmachine|mediaserver}]
stripe_unit | Specifies the stripe width size to use for erasure-coded volume. |
encrypt | Specifies whether the encrypted data is stored in erasure-coded volume |
stripe_aligned | Specifies whether the object allocations are aligned to stripe length. |
stripe_tag | Specifies tag for customize failure domain. It can be either disk or node. |
rotating_parity | Specifies whether the striping is done with distributed parity. |
single_volume | Specifies whether to create only a single volume in the erasure-coded file system. This parameter can be set only if stripe_aligned is set to no. |
ecloglen | Specifies the per column log size for erasure-coded volume. This parameter can be set only if stripe_aligned is set to no. |
eclogdisk | Specifies a comma-separated list of disks from all failure domains to be used for log allocation. This parameter can be set only if stripe_aligned is set to no. |
workload | Specifies the type of workload using the file system. |
For example:
Storage> fs create ecoded ecfs3 2g 3 1 pool1 blksize=1024 64k stripe_aligned=no stripe_tag=node rotating_parity=yes
See the Veritas Access Command Reference Guide for more details about creation of CFS erasure-coded file system for NFS.
You can also encrypt your file system using a Key Management Server (KMS).