Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- 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
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
Adding or removing a column from a file system
You may want to add or remove a column from a file system in specific situations. Adding columns can help to perform more I/Os in parallel, so you may want to increase the number of columns in the file system.
Note:
For a striped file system when you add a column, the layout that is displayed when you issue the Storage> fs list and Storage> fs list fsname commands may be different than the original layout of the file system while the relayout (addition of new columns) operation is in progress. The original file system layout is displayed when the relayout operation is completed.
Note:
Adding and removing a column to and from a file system involves a volume-level relayout. This is an I/O intensive operation. For a large file system, adding or removing columns takes a long time and can hurt application performance during this relayout period.
To add a specified number of columns to a file system
- To add a specified number of columns to a file system, enter the following:
Storage> fs addcolumn tier_name fs_name ncolumns pool_or_disk_name
fs_name
Specifies the file system for which you want to add additional columns.
tier_name
Specifies the tier name.
ncolumns
Specifies the number of columns that you want to add to the file system.
Note:
In the case of a striped file system, the number of the disks that are specified should be equal to the number of columns (ncolumns).
Note:
In the case of a mirrored-stripe and a striped-mirrored file system, the disks should be equal to (ncolumns * number_of_mirrors_in_fs).
pool_or_disk_name
Specifies the pool or the disk name for the file system.
To remove a column from a file system
- To remove a column from a file system, enter the following:
Storage> fs rmcolumn tier_name fs_name
where fs_name is the name of the file system for which you want to remove the column and tier_name is the name of the tier.