Veritas Access 7.3 Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- About configuring the Veritas Access network
- About bonding Ethernet interfaces
- Bonding Ethernet interfaces
- Configuring DNS settings
- About the IP addresses for the Ethernet interfaces
- About Ethernet interfaces
- Displaying current Ethernet interfaces and states
- Configuring IP addresses
- Configuring Veritas Access to use jumbo frames
- Configuring VLAN interfaces
- Configuring NIC devices
- Swapping network interfaces
- Excluding PCI IDs from the cluster
- About configuring routing tables
- Configuring routing tables
- Changing the firewall settings
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- About storage provisioning and management
- Displaying information for all disk devices associated with the nodes in a cluster
- About configuring storage pools
- Configuring storage pools
- About quotas for usage
- About quotas for CIFS home directories
- Enabling, disabling, and displaying the status of file system quotas
- Setting and displaying file system quotas
- Setting user quotas for users of specified groups
- About Flexible Storage Sharing
- Workflow for configuring and managing storage using the Veritas Access CLI
- Displaying WWN information
- Initiating host discovery of LUNs
- Importing new LUNs forcefully for new or existing pools
- Increasing the storage capacity of a LUN
- About configuring disks
- Configuring disks
- Formatting or reinitializing a disk
- Removing a disk
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your NFS server
- About using NFS server with Veritas Access
- Using the kernel-based NFS server
- Using the NFS-Ganesha server
- Switching between NFS servers
- Recommended tuning for NFS-Ganesha version 3 and version 4
- Accessing the NFS server
- Displaying and resetting NFS statistics
- Configuring Veritas Access for ID mapping for NFS version 4
- Configuring the NFS client for ID mapping for NFS version 4
- About authenticating NFS clients
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About configuring Veritas Access for CIFS
- About configuring CIFS for standalone mode
- Configuring CIFS server status for standalone mode
- Changing security settings
- Changing security settings after the CIFS server is stopped
- About Active Directory (AD)
- About configuring CIFS for Active Directory (AD) domain mode
- Setting NTLM
- About setting trusted domains
- Specifying trusted domains that are allowed access to the CIFS server
- Allowing trusted domains access to CIFS when setting an IDMAP backend to rid
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ldap
- Allowing trusted domains access to CIFS when setting an IDMAP backend to hash
- Allowing trusted domains access to CIFS when setting an IDMAP backend to ad
- About configuring Windows Active Directory as an IDMAP backend for CIFS
- Configuring the Active Directory schema with CIFS-schema extensions
- Configuring the LDAP client for authentication using the CLI
- Configuring the CIFS server with the LDAP backend
- Setting Active Directory trusted domains
- About storing account information
- Storing user and group accounts
- Reconfiguring the CIFS service
- About mapping user names for CIFS/NFS sharing
- About the mapuser commands
- Adding, removing, or displaying the mapping between CIFS and NFS users
- Automatically mapping of UNIX users from LDAP to Windows users
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- Setting the CIFS aio_fork option
- About managing local users and groups
- Enabling CIFS data migration
- Configuring Veritas Access to work with Oracle Direct NFS
- About using Veritas Access with Oracle Direct NFS
- About the Oracle Direct NFS architecture
- About Oracle Direct NFS node or storage connection failures
- Configuring an Oracle Direct NFS storage pool
- Configuring an Oracle Direct NFS file system
- Configuring an Oracle Direct NFS share
- Best practices for improving Oracle database performance
- Configuring an FTP server
- About FTP
- Creating the FTP home directory
- Using the FTP server commands
- About FTP server options
- Customizing the FTP server options
- Administering the FTP sessions
- Uploading the FTP logs
- Administering the FTP local user accounts
- About the settings for the FTP local user accounts
- Configuring settings for the FTP local user accounts
- 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
- About creating and maintaining file systems
- Considerations for creating a file system
- Best practices for creating file systems
- About scale-out file systems
- Characteristics of a scale-out file system
- About striping file systems
- About creating a tuned file system for a specific workload
- About FastResync
- About scale-out fsck
- About setting retention in files
- About managing application I/O workloads using maximum IOPS settings
- Choosing a file system layout type
- Determining the initial extent size for a file system
- Creating a file system
- Bringing the file system online or offline
- Listing all file systems and associated information
- Modifying a file system
- Managing a file system
- Destroying a file system
- Upgrading disk layout versions
- Creating and maintaining file systems
- Section VIII. Configuring cloud storage
- Configuring the cloud gateway
- Configuring cloud as a tier
- Configuring the cloud as a tier feature for scale-out file systems
- Moving files between tiers in a scale-out file system
- About policies for scale-out file systems
- Obtaining statistics on data usage in the cloud tier in scale-out file systems
- Workflow for moving on-premises storage to cloud storage for NFS shares
- Section IX. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About NFS file sharing
- Displaying file systems and snapshots that can be exported
- Exporting an NFS share
- Displaying exported directories
- About managing NFS shares using netgroups
- Unexporting a directory or deleting NFS options
- Exporting an NFS share for Kerberos authentication
- Mounting an NFS share with Kerberos security from the NFS client
- Exporting an NFS snapshot
- Creating and maintaining CIFS shares
- About managing CIFS shares
- Exporting a directory as a CIFS share
- Configuring a CIFS share as secondary storage for an Enterprise Vault store
- Exporting the same file system/directory as a different CIFS share
- About the CIFS export options
- Setting share properties
- Hiding system files when adding a CIFS normal share
- Displaying CIFS share properties
- Allowing specified users and groups access to the CIFS share
- Denying specified users and groups access to the CIFS share
- Exporting a CIFS snapshot
- Deleting a CIFS share
- Modifying a CIFS share
- Making a CIFS share shadow copy aware
- Using Veritas Access with OpenStack
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Use cases for compressing files
- Best practices for using compression
- Compression tasks
- Compressing files
- Scheduling compression jobs
- Listing compressed files
- Showing the scheduled compression job
- Uncompressing files
- Modifying the scheduled compression
- Removing the specified schedule
- Stopping the schedule for a file system
- Removing the pattern-related rule for a file system
- Removing the modified age related rule for a file system
- Configuring SmartTier
- About Veritas Access SmartTier
- How Veritas Access uses SmartTier
- Adding tiers to a file system
- Adding or removing a column from a secondary tier of a file system
- Configuring a mirror to a tier of a file system
- Listing all of the files on the specified tier
- Displaying a list of SmartTier file systems
- About tiering policies
- About configuring the policy of each tiered file system
- Configuring the policy of each tiered file system
- Best practices for setting relocation policies
- Relocating a file or directory of a tiered file system
- Displaying the tier location of a specified file
- About configuring schedules for all tiered file systems
- Configuring schedules for tiered file systems
- Displaying the files that may be moved or pruned by running a policy
- Allowing metadata information on the file system to be written on the secondary tier
- Restricting metadata information to the primary tier only
- Removing a tier from a file system
- Configuring SmartIO
- About SmartIO for solid-state drives
- About configuring SmartIO
- About SmartIO read caching for applications running on Veritas Access file systems
- Setting up SmartIO read caching for Veritas Access
- About SmartIO writeback caching for applications running on Veritas Access file systems
- Setting up SmartIO writeback caching for VxFS file systems
- Tuning the writeback caching
- Flushing dirty data from a writeback cache area
- Setting the caching mode
- Customizing the caching behavior
- Viewing the caching statistics for a cache area
- Verifying the VxFS cache area and monitoring the caching
- Configuring replication
- About Veritas Access file-level replication
- How Veritas Access replication works
- About Veritas Access sync replication
- How Veritas Access sync replication works
- Starting Veritas Access replication
- Setting up communication between the source and the destination clusters
- Setting up the file systems to replicate
- Setting up files to exclude from a replication unit
- Scheduling the replication
- Defining what to replicate
- About the maximum number of parallel replication jobs
- Managing a replication job
- Replicating compressed data
- Displaying replication job information and status
- Synchronizing a replication job
- Behavior of the file systems on the replication destination target
- Accessing file systems configured as replication destinations
- Creating a recovery point objective (RPO) report
- Replication job failover and failback
- Using snapshots
- Using instant rollbacks
- About instant rollbacks
- Creating a space-optimized rollback
- Creating a full-sized rollback
- Listing Veritas Access instant rollbacks
- Restoring a file system from an instant rollback
- Refreshing an instant rollback from a file system
- Bringing an instant rollback online
- Taking an instant rollback offline
- Destroying an instant rollback
- Creating a shared cache object for Veritas Access instant rollbacks
- Listing cache objects
- Destroying a cache object of a Veritas Access instant rollback
- Configuring Veritas Access with the NetBackup client
- About Veritas Access as a NetBackup client
- Prerequisites for configuring the NetBackup client
- About the NetBackup Snapshot Client
- About NetBackup snapshot methods
- About NetBackup instant recovery
- Enabling or disabling the NetBackup SAN client
- Workflow for configuring Veritas Access for NetBackup
- Registering a NetBackup master server, an EMM server, or adding an optional media server
- Displaying the excluded files from backup
- Displaying the included and excluded files for backups
- Adding or deleting patterns to the list of files in backups
- Configuring or resetting the virtual IP address used by NetBackup
- Configuring the virtual name of NetBackup
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Performing a backup or restore of a Veritas Access file system over a NetBackup SAN client
- Performing a backup or restore of a snapshot
- Installing or uninstalling the NetBackup client
- Configuring Veritas Access for NetBackup cloud storage
- Section XI. 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. |
Examples of alerts:
NUMSPACE alerts in Report> showevents
2011 Nov 14 23:55:02 [CLUS_01,alert,master] [[fs alert]] numspace set at 70(%) crossed for File System fs1, current usage 98(%)
NUMINODES alert in Report> showevents
2011 Nov 15 00:05:22 [CLUS_01,alert,master] [[fs alert]] numinodes set at 2000 crossed for File System fs1, current usage 7768
Examples for setting alerts that are file-system specific:
Storage> fs alert set numinodes 2M fs1 ACCESS fs SUCCESS V-288-663 Alert of type [ numinodes ] set to 2M on the file system fs1
Storage> fs alert set numinodes 2M ACCESS fs SUCCESS V-288-663 Default Alert on the file systems of type [ numinodes ] set to 2M
Examples for default alerts:
Storage> fs alert set numspace 80 fs1 ACCESS fs SUCCESS V-288-663 Alert of type [ numspace ] set to 80 on the file system fs1
Storage> fs alert set numspace 60 ACCESS fs SUCCESS V-288-663 Default Alert on the file systems of type [ numspace ] set to 60
Example for setting a fullspace alert:
Storage> fs alert set fullspace 98 ACCESS fs SUCCESS V-288-1805 Default Alert on the file systems of type [ fullspace ] set to 98 Storage> fs alert unset fullspace ACCESS fs SUCCESS V-288-1740 Alert of type [ fullspace ] set to default value 0 (%)
Example for setting a fullinodes alert:
storage> fs alert set fullinodes 50000000 ACCESS fs SUCCESS V-288-1805 Default Alert on the file systems of type [ fullinodes ] set to 50000000 Storage> fs alert show File System Alert Type Value Current Usage ==================== ========== ========= ============= fs2 numspace 85% (D) 75% fs2 numinodes 0 (D) 110215 fs2 fullspace 98% (D) 75% fs2 fullinodes 50000000 (D) 110215 share1 numspace 85% (D) 80% share1 numinodes 0 (D) 8044 share1 fullspace 98% (D) 80% share1 fullinodes 50000000 (D) 8044