Veritas Information Map Installation and Administration Guide

Last Published:
Product(s): Information Map (1.0)
  1. Introduction to Veritas Information Map
    1.  
      Overview of Information Map
    2.  
      Deployment workflow
    3.  
      Information Map architecture
    4.  
      Creating new user accounts
  2. Planning installation of the Information Map Agent
    1.  
      System requirements
    2.  
      Supported browsers
    3.  
      Connectivity requirements
    4.  
      Security requirements
    5.  
      Generating a KeyStore file
    6.  
      Configuring access to a NetBackup master server
  3. Installing and configuring Information Map
    1.  
      Logging in to Veritas Information Map
    2.  
      Downloading the Agent installer
    3.  
      Configuring locations in Information Map
    4. Installing the Information Map Agent
      1.  
        Configuring proxy settings
    5.  
      Registering the Information Map Agent with Information Fabric
    6. Configuring credentials for share discovery and native scanning
      1.  
        Credentials required to configure share discovery
      2.  
        Configuring a non-administrator domain user on NetApp 7-mode filer
      3.  
        Configuring a non-administrator account on an EMC Isilon file server
    7.  
      Updating the Information Map Agent
  4. Cloud Agent configuration
    1.  
      About configuring the Amazon S3 Agent
    2.  
      Configuring metadata collection in Amazon Web Services (AWS)
    3.  
      Configuring Information Map to access Amazon S3 account
  5. Global settings
    1.  
      About configuring global settings
    2.  
      Configuring stale data definition
    3.  
      Configuring non-business data definition
    4.  
      Configuring storage tiers
    5.  
      Assigning storage tiers to storage
    6.  
      Customizing item types
  6. Managing Information Map settings
    1.  
      Configuring Information Map users
    2.  
      Managing Agents
    3.  
      Managing tasks
    4.  
      Managing content sources
  7. Troubleshooting
    1.  
      Veritas Information Map logging
    2.  
      Information Map Agent jobs
    3.  
      Information Map Agent issues
    4.  
      Information Map and data accuracy
    5.  
      Known limitations of Information Map Agent

Veritas Information Map logging

Information Map provides the following logs to help you troubleshoot some common issues.

  • Agent logs

    Information Map Agent logs contain details about the installation tasks and the overall progress status of the Agent components. These logs are useful for identifying Agent installation and registration issues. The installer creates the log directory as soon as you launch the wizard. The log files are located at on the Agent server at:

    <InstallDir>/log

    Here, InstallDir is the installation directory, typically, C:\Program Files\Veritas\InformationMapAgent.

  • Veritas NetBackup logs

    The NetBackup logs are located at <<InstallDir>>\bin\nbu\Veritas\NetBackup\logs.

Information Map provides the logscli.exe utility, which you can use to collect logs. This utility retrieves detailed diagnostic information about the installation and discovery configurations. You can use this information to troubleshoot issues and share these logs with Technical Support for further troubleshooting.

The utility is located at C:\Program Files\Veritas\InformationMapAgent\bin\logscli.exe

To collect the logs

  1. To collect the Agent or NetBackup logs, open a command prompt window and navigate to the location of the utility.
  2. Collect the logs using the following command:

    logscli.exe -b [OPTIONS]

    For example, logscli.exe -b -c

    --nbu

    Download logs related to NetBackup discovery scans.

    --debug-off

    Disable debug-level logging.

    --debug-on <Log_Level>

    Enable debug-level logging.

    The <Log_Level> argument in "--debug-on" is optional, and if you specify it, can have following values - FINE, FINER, FINEST, ALL.(The default is FINE if a value is not provided.)

    For example, logscli.exe --debugon

    Wait for debug activity to be captured. And run following command again:

    logscli.exe -b -c

    -h --help

    Display help.

    You can limit the diagnostic information to specific components using the various available options.

    If you do not specify any options, the command retrieves diagnostic information with the following options:

    [-c] [-o <output_dir>]

    -c,--configdb

    Include the config database

    -o,--output <output_dir>

    Output directory