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
Accessing the NFS server
To check on the NFS server status
- Prior to starting the NFS server, check on the status of the server by entering:
NFS> server status
The output shows the status. The output also indicates whether the NFS server being used.
The states (ONLINE, OFFLINE, and FAULTED) correspond to each Veritas Access node identified by the node name. The states of the node may vary depending on the situation for that particular node.
The possible states of the NFS> server status command are:
ONLINE
Indicates that the node can serve NFS protocols to the client.
OFFLINE
Indicates the NFS services on that node are down.
FAULTED
Indicates something is wrong with the NFS service on the node.
You can run the NFS> server start command to restart the NFS services, and only the nodes where NFS services have problems, are restarted.
To start the NFS server
- To start the NFS server, enter the following:
NFS> server start
You can use the NFS> server start command to clear an OFFLINE state from the NFS> server status output by only restarting the services that are offline. You can run the NFS> server start command multiple times without it affecting the already-started NFS server.
Run the NFS> server status command again to confirm the change.
To stop the NFS server
- To stop the NFS server, enter the following:
NFS> server stop