Veritas Information Map Installation and Administration Guide

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

Known limitations of Information Map Agent

The following notes cover limitations pertaining to the collection and display of data on the Map UI. These are present as a result of either development work in-progress or issues which have not yet been corrected.

User Interface limitations
  • Filters only show a maximum of 1,000 entries and ordering is limited to these entries. To see entries beyond the first 1,000, use the search to reduce to bring the number of matching entries below 1,000. Search is not currently available on the owners filter. This functionality will be added in a future version, as will the ability to scroll and order the entire list.

  • The Dashboard list views have a limit of 20,000 rows and ordering is limited to the returned subset. Filtering should be used to reduce the number of items in the list to below 20,000. The ability to search, scroll, and order the entirety of longer list will be added in a future version.

  • This release only supports the US English language in the user interface. The names of the objects discovered on your network and in your metadata (For example, owners and shares) can be in any language.

  • The copy or paste functionality on the Item List page is not supported on tablets and mobile devices.

  • On Safari and older versions of Firefox (version < 41), copy and paste on the Item List view requires you to use the Ctrl/Cmd + C keystroke combination.

  • The file count that is listed on the Export creation dialog may not exactly match the number of files in the Export. This is because files may have been added, removed, or moved from the Information Fabric platform between the time the export is created and the time it is processed. This limitation also applies to the file count on the Item List preview. However, it is not very apparent because the Item List view only displays a sample of the actual data.

Data collection limitations for NetBackup catalog
  • Metadata scanning for the special characters, newline, "|", and tab in file names is not supported.

  • The Agent must connect to the NetBackup master server(s) containing the relevant backup policies. They cannot infer these from Automatic Image Replication (AIR) replicas of backups from other NetBackup servers.

  • Container mappings will only be queried for Windows, Linux (/etc/export), NetApp, and EMC Isilon servers or filers.

  • The NetBackup master server(s) configured to use NetBackup Access Control (NBAC) in 'Required' mode are currently not supported. This configuration is comparatively rare.

  • Currently, Information Map does not process the deletion of content sources or content containers. This functionality will be added in a later release.

  • If the output of a scan runs into multiple lines, the Information Map Agent is not able to parse the output. As a result, the content sources and containers that are part of the scan output will not display on the Information Map.

  • Agent relies on NetBackup to return items in a certain order. However, if the items in a backup image are not returned in the right hierarchical order by NetBackup, you will see some discrepancy in the data being displayed on the Information Map.

  • The scan process is marked as complete for a backup ID that does not have any data in it in case of backup images from an incremental backup.

  • NetBackup allows users to pause and resume the backups. In case of multistreaming backup, if a backup is paused for more than the default timeout for processing backups from a multistreamed policy, the Information Map Agent may not be able to process such backups correctly. This would affect the data accuracy on the Information Map.

    As a workaround, you can configure a higher timeout period.

  • NetBackup supports backup selections for files for example, C:/f1/f2/foobar.txt or with wildcard characters C:/f1/f2/foo*.txt. However, the Information Map Agent expects backup selection as folders. Thus, in cases where the backup selection consists of file paths, the Agent does not process the backup correctly, which results in inaccurate data on the Information Map.

  • Ensure that the Information Map Agent server and the NetBackup master server are in the same time zone. If they are in different time zones the Agent may not function correctly.

  • Content sources that are part of a standard policy are not displayed in the Information Map, if the backup selection has a folder with only white space in the folder name. (Blank name made up of spaces.)

  • In the NetBackup policy, if a Hyper-V guest is configured for virtual machines, then during share discovery the Agent does not fetch the host name of that virtual machine. Instead, it fetches the display name or the GUID that is assigned to the virtual machine when it was created.

Data collection limitations for other on-premises and cloud data stores


For on-premises and cloud data stores, the Connectors perform only full scan. Incremental scan is not supported.

Table: On-premises data stores and their limitations

Data store


CMIS (OpenText Documentum, Opentext LiveLink, IBM FileNet)

The following limitations apply to all the CMIS data stores:

  • The Connector does not fetch the last accessed user and date information.

  • The Connector does not fetch the size and file extension details of a file that is not uploaded to the data store.

  • When a file has multiple versions, the Map UI displays each file version as a separate entry with the file name as <filename>_<version_number>.<extension>.

The following limitations are specific to the following data stores:

  • OpenText Documentum:

    • Documentum permits creation of multiple files with same name within the same folder. However, the Connector does not collect metadata for such files.

    • When a file is created but not checked in to the Documentum server, an empty template file gets created. Since a file is not present, the Connector does not fetch the extension of such template files.

  • IBM FileNet: The Connector does not collect the last modified date for the root folder.

  • Opentext LiveLink:

    • The Connector collects metadata only for files with type Documents. It ignores other types such as Tasks, Polls, and Projects.

    • The Connector discovers both, user's private space (user's repository) and public repositories. However, it scans only those repositories for which the user has sufficient access permissions.

    • If a file has multiple versions and each version has a different extension, then the Connector does not collect the version details for such a file.

Microsoft SQL

  • The Connector does not support the Windows Authentication mode.

  • When the Microsoft SQL Server service is restarted, the Connector does not collect the last access and modified time information.

Microsoft SharePoint

  • Sites that are locked will be discovered however, not scanned by the Connector.

  • When two Windows PowerShell scripts run in parallel for the same or different Connectors, then expect some latency in discovery of site collections and document libraries.

Oracle Database

The Connector does not collect the last access date and user details for Oracle data store.

Table: Cloud data stores and their limitations

Data stores


Microsoft OneDrive

  • For the Connector to discover the configured OneDrive account, the user of that account should log on to the account at least once.

  • The Connector does not discover the accounts that have expired.

  • When the Connector scans OneDrive accounts, it does not collect the location information. Consequently, location for such data stores is not populated on the Map UI.

Microsoft SharePoint Online

  • When scanning SharePoint Online account, the Connector does not collect the location information. As a result, location for such data stores is not populated on the Map UI.

  • The Connector does not discover SharePoint Online accounts that have expired.

  • The Connector discovers only the default document library (Documents) and custom document libraries.