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 the 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 an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. 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 VII. Configuring cloud storage
- Section VIII. 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
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- 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
- Compressing files
- Section X. Reference
Adding tiers to a file system
You can add the following types of tiers to file systems:
simple
mirrored
striped
mirrored-stripe
striped-mirror
Note:
The ecoded layout is not supported for adding a secondary tier to a file system.
Note:
If a rollback exists for the file system, adding a tier can cause inconsistencies in the rollback hierarchy. The recommended method is to create the tier first and then create the rollback.
To add a second tier to a file system
- To add a tier to a file system where the layout is "simple" (concatenated), enter the following:
Storage> tier add simple fs_name size pool1[,disk1,...]
To add a mirrored tier to a file system
- To add a mirrored tier to a file system, enter the following:
Storage> tier add mirrored fs_name size nmirrors pool1[,disk1,...] [protection=disk|pool]
To add a striped tier to a file system
- To add a striped tier to a file system, enter the following:
Storage> tier add striped fs_name size ncolumns pool1[,disk1,...] [stripeunit=kilobytes]
To add a mirrored-striped tier to a file system
- To add a mirrored-striped tier to a file system, enter the following:
Storage> tier add mirrored-stripe fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes]
To add a striped-mirror tier to a file system
- To add a striped-mirror tier to a file system, enter the following:
Storage> tier add striped-mirror fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes]
fs_name
Specifies the name of the file system to which the mirrored tier is added. If the specified file system does not exist, an error message is displayed.
size
Specifies the size of the tier to be added to the file system (for example, 10m, 10M, 25g, 100G).
ncolumns
Specifies the numbers of columns to add to the striped tiered file system.
nmirrors
Specifies the number of mirrors to be added to the tier for the specified file system.
pool1[,disk1,...]
Specifies the pool(s) or disk(s) that is used for the specified tiered file system. If the specified pool or disk does not exist, an error message is displayed. You can specify more than one pool or disk by separating the pool or the disk name with a comma, but do not include a space between the comma and the name.
The disk needs to be part of the pool or an error message is displayed.
protection
If no protection level is specified, disk is the default protection level.
The protection level of the second tier is independent of the protection level of the first tier.
Available options are:
disk - If disk is entered for the protection field, then mirrors are created on separate disks. The disks may or may not be in the same pool.
pool - If pool is entered for the protection field, then mirrors are created in separate pools. If not enough space is available, then the file system is not created.
stripeunit=kilobytes
Specifies a stripe width of either 128K, 256k, 512K, 1M, or 2M. The default stripe width is 512K.