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

Configuring Information Map to access Amazon S3 account

To enable cloud support, you must configure communication between Information Map and your Amazon S3 account. Once this task is setup and a successful connection has been established, the Veritas Cloud Agent initiates a discovery scan and presents the data inventory for your Amazon S3 cloud storage account on the Dashboard and Map views.

To configure access to an Amazon S3 account

  1. On the vertical navigation panel in the Information Map application, expand the Administration section and click Tasks > New.
  2. On the Tasks page, configure a new task to collect metadata from the Amazon S3 account.

    See Managing tasks.

  3. Verify the content sources are populated once the initial discovery scan is complete. The collection status for content sources is disabled by default. You must enable it to initiate a metadata scan.

    See Managing content sources.

    Note that the initial discovery scan can take up to an hour to start.

  4. AWS locations are automatically updated in Information Map during the discovery phase if they have not been created manually. Once auto-populated, you can only edit certain fields for a location. The editable fields are Contact name, Contact telephone, Contact email, Storage tier, and Notes.

    See Configuring locations in Information Map.

  5. Once the metadata scan of the content sources (Amazon S3 buckets) is complete for all objects within your cloud data set, navigate to the Dashboard and Map views to visualize and filter the inventory for your Amazon S3 cloud data.

    Note:

    The metadata scans run daily and take between 24-48 hours before all your data inventory is discovered and available to be visualized. Content sources that have collected successfully cannot be deleted.