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
Setting file system alerts
For a file system to run efficiently, you should always reserve some space for the file system rather than using 100% of the space. You can set file system alerts based on file system or snapshot usage. You can set the alert based on the number of inodes used, file system space used, or snapshot usage.
File system alerts can be displayed by using the Report> showevents command.
To set file system alerts
- To set file system alerts, enter the following:
Storage> fs alert set numinodes | numspace | fullspace | fullinodes value [fs_name,...] [snapshot_name]
numinodes | When setting the alert for numinodes, value is the number of inodes used. The default alert value for numinodes is set at 0. An alert will not be sent until you set it to a different value. |
numspace | When setting the alert for numspace, value is the percentage you want to set to trigger the alert. By default, the alert is sent at 80%. If you do not specify a file system name, the default value is modified. |
fullspace | fullspace is the tunable for setting an alert if the file system becomes full. When file system usage is above the limit set by the fullspace tunable, all the NFS/CIFS shares on the file system are automatically changed to read-only to prevent the file system from becoming full again. When you grow the file system or delete some files to free up space, the NFS/CIFS shares are automatically changed back to read-write (there might be a delay of up to five minutes) for the change to occur. Note: The file system size is checked every five minutes. During this five-minute interval, if the usage of the file system grows to more than 80%, the NFS/CIFS shares are changed to read-only. If the file system is small and write I/O is fast, then the file system can be filled up to 100% before being changed to read-only. This is by design. By default, the fullspace tunable is set to 0, which means that the fullspace tunable is disabled. |
fullinodes | fullinodes is the tunable for setting an alert if the file system becomes full. When inodes on a file system reach the limit of fullinodes, the NFS/CIFS shares on the file system are automatically changed to read-only. After the file system is changed to read-only, you need to delete some files from the file system, and a remount of the file system may be required for the NFS/CIFS shares to be changed to read-write. By default, the fullinodes tunable is set to 0, which indicates that the fullinodes tunable is disabled. |
fs_name | Name of the file system for which you want to set the file system alerts. fs_name is optional. To specify multiple file systems, use commas to separate the file system names. |
snapshot_name | Name of the snapshot for which you want to set the file system alert. Note: The following are reserved words for snapshot_name: flags, ctime, and mtime. |