Veritas Access Appliance 8.2 Troubleshooting Guide
- Introduction
- General troubleshooting procedures
- Monitoring Access Appliance
- Common recovery procedures
- About common recovery procedures
- Restarting servers
- Restarting cluster services
- Bringing services online
- Recovering from a non-graceful shutdown
- Testing the network connectivity
- Troubleshooting with traceroute
- Using the traceroute command
- Collecting the metasave image of a file system
- Replacing an Ethernet interface card (online mode)
- Replacing an Access Appliance node
- Speeding up episodic replication
- Uninstalling a patch release or software upgrade
- Troubleshooting the Access Appliance cloud as a tier feature
- Troubleshooting Access Appliance installation and configuration issues
- Troubleshooting Access Appliance CIFS issues
- Troubleshooting Access Appliance GUI startup issues
- Troubleshooting Veritas Data Deduplication issues
- Index
Restarting servers
Some configuration changes do not take effect until the associated server is restarted. Therefore, some configuration problems can be solved by stopping and restarting the associated server. For example, when you change AD Domain settings, you need to restart the CIFS server.
Table: Commands to start and stop servers shows commands you can use to start and stop Access Appliance servers.
Table: Commands to start and stop servers
Command | Definition |
|---|---|
Backup> start | Starts all configured backup services. |
Backup> stop | Stops all configured backup services. |
CIFS> server start | Starts the CIFS server. |
CIFS> server stop | Stops the CIFS server. |
NFS> server start | Starts the NFS server. |
NFS> server stop | Stops the NFS server. |
Storage> iscsi start | Starts the iSCSI initiator service. |
Storage> iscsi stop | Stops the iSCSI initiator service. |
Note:
Some commands include the server argument and some do not. Also, some Support> commands use a service (instead of server) argument.