Veritas Access Appliance 8.2 Troubleshooting Guide

Last Published:
Product(s): Appliances (8.2)
Platform: Veritas 3340,Veritas 3350,Veritas 3360
  1. Introduction
    1.  
      About troubleshooting
    2.  
      General tips for the troubleshooting process
    3.  
      General techniques for the troubleshooting process
  2. General troubleshooting procedures
    1.  
      About general troubleshooting procedures
    2.  
      Viewing the Access Appliance log files
    3.  
      About event logs
    4.  
      Setting the CIFS log level
    5.  
      Setting the NetBackup client log levels and debugging options
    6.  
      Retrieving and sending debugging information
    7.  
      Collecting time-based and archived logs
  3. Monitoring Access Appliance
    1.  
      About monitoring Access Appliance operations
    2.  
      Monitoring hardware components
  4. Common recovery procedures
    1.  
      About common recovery procedures
    2.  
      Restarting servers
    3.  
      Restarting cluster services
    4. Bringing services online
      1.  
        Using the services command
    5.  
      Recovering from a non-graceful shutdown
    6.  
      Testing the network connectivity
    7.  
      Troubleshooting with traceroute
    8.  
      Using the traceroute command
    9.  
      Collecting the metasave image of a file system
    10.  
      Replacing an Ethernet interface card (online mode)
    11.  
      Replacing an Access Appliance node
    12. Speeding up episodic replication
      1.  
        About synchronizing an episodic replication job
      2.  
        Synchronizing an episodic replication job
    13.  
      Uninstalling a patch release or software upgrade
  5. Troubleshooting the Access Appliance cloud as a tier feature
    1.  
      Troubleshooting tips for cloud tiering
    2.  
      Issues when reading or writing data from the cloud tier
    3.  
      Log locations for checking for cloud tiering errors
  6. Troubleshooting Access Appliance installation and configuration issues
    1.  
      How to find the management console IP
    2.  
      Viewing the installation logs
    3.  
      Installation fails and does not complete
  7. Troubleshooting Access Appliance CIFS issues
    1.  
      User access is denied on a CTDB directory share
  8. Troubleshooting Access Appliance GUI startup issues
    1.  
      Resolving GUI startup issues
  9. Troubleshooting Veritas Data Deduplication issues
    1.  
      Log locations for the Veritas Data Deduplication server
  10.  
    Index

Collecting time-based and archived logs

You can collect logs for a specific duration for the sds and backup modules. Collecting logs for a specific duration reduces the time taken to collect and upload the logs to a remote server. You can also collect archived logs for all the modules.

The following command shows the options for collecting time-based and archived logs:

debuginfo upload nodename debug-URL module archivedLogs={on|off|vxdefault} startDate endDate tarName

nodename

Specifies the nodename from which to collect the debugging information.

debug-URL

Specifies the remote file or directory for uploading debugging information.

Depending on the type of server from which you upload debugging information, use one of the following example URL formats:

ftp://admin@ftp.docserver.company.com/
patches/
scp://root@server.company.com:/tmp/

If debug-URL specifies a remote file, the debuginfo file is saved by that name. If debug-URL specifies a remote directory, the debuginfo file name displays as the following:

nas_debuginfo_nodename_modulename_timestamp.tar.gz

module

Specifies the values for module.

The following options are supported:

  • service-status: Current status of services that are running in the cluster.

  • performance:Performance logs for the cluster nodes.

  • common-logs:Logs that are common across multiple modules for the cluster nodes.

  • nas: Product information from the cluster nodes.

  • os:Logs for kernel and user dumps.

  • sos-report: Uses RHEL utility to collect troubleshooting data for the operating system. The sosreport is collected for all the loaded modules except for the selinux module.

  • explorer:The VxExplorer utility collects logs and environment data from all the servers where the Access Appliance product is installed.

  • install: Install logs from the CPI install log directory /opt/VRTS/install/logs/.

  • nas-procstacks: Stack trace for all the daemons that are in running state.

  • appliance: Logs related to the appliance.

  • sds: SDS logs.

  • upgrade: Upgrade logs for all the cluster nodes.

  • backup: NetBackup client logs and other diagnostic information.

  • vdd: Deduplication logs provided Veritas Data Deduplication server is configured for the cluster.

  • default: Logs from service-status, nas, explorer, install, nas-procstacks, appliance, sds, upgrade, and backup modules of the cluster nodes. This is the default option.

  • all: This module collects information for all the above modules from the cluster nodes.

archivedLogs

Collects historical logs. Options are on, off, and vxdefault.

startDate

Start date in mm/dd/yy format if you want to collect logs for a specific duration.

Time-based logs are collected only for nas and sds modules. Logs for sds and nas modules from the archived directory are also included.

endDate

End date in mm/dd/yy format if you want to collect logs for a specific duration.

Time-based logs are collected only for nas and sds modules. Logs for sds and nas modules from the archived directory are also included.

tarName

Name of the tar file that includes all the collected logs.

The following example shows how to upload all debug information to an FTP server including the archived logs:

Support> debuginfo upload node1_1 ftp://admin@ftp.docserver.veritas.com/patches/ all archivedLogs=on

The following example shows how to upload all debug information to an FTP server excluding the archived logs:

Support> debuginfo upload node1_1 ftp://admin@ftp.docserver.veritas.com/patches/ all archivedLogs=off

The following example shows how to upload all debug logs from all node for all modules for a specific duration. The logs for only sds and backup modules are collected for the specified duration; all logs are collected for all the other modules.

Support> debuginfo upload all file:///log/ all archivedLogs=off 06/12/2023 06/25/2023