Best Practices when Backup Exec integrates with Veritas™ Information Map

Best Practices when Backup Exec integrates with Veritas™ Information Map

Article: 100040596
Last Published: 2017-11-06
Ratings: 0 0
Product(s): Backup Exec



The Veritas™ Information Map renders unstructured data in visual context and guides users towards unbiased, information-governance decision making. Using the dynamic navigation in Information Map, customers can identify areas of risk, areas of value, and areas of waste across their environment and make decisions which reduce information risk and optimize information storage.

For more information, refer to the Veritas™ Information Map documentation.

Backup Exec collects metadata as part of the daily backup jobs, building a rich catalogue of the unstructured data an organization owns.

With the Information Map Integration feature, Backup Exec sends metadata about these items in the backup sets of the protected servers to the Information Map Agent. The Information Map Agent sends the metadata to the Information Map services hosted in the cloud. Thus, Backup Exec acts as a proxy and the metadata already captured during the backup is shared with Information Map and one can access up-to-date information about large storage environments very quickly.

The following data sources are supported when integrating with Veritas™ Information Map

  • File systems that are supported by Backup Exec. For example, NTFS, ext2, ext3.
  • NDMP file servers
  • Windows shares

Best Practices

  • When you install the Information Map Agent, ensure that in the Shared Data Location option, a remote share is specified. If the Information Map Agent is uninstalled or reinstalled, the cache information that is used in the previous installation is not lost and can be reused.

For more information about how to install and configure the Information Map Agent, refer to the Veritas™ Information Map documentation.

  • To limit the load on the Backup Exec server and to be able to use the Information Map Agent for different Information Map datastores, it is recommended that you install Information Map Agent on a different computer.
  • Ensure that the time duration that is selected in the Catalog panel is more than the duration that you set for sending item-level metadata created within the specified number of days to Information Map. To change the catalog setting, go to Configuration and Settings > Backup Exec Settings > Catalog > Truncate catalogs after.

For example, if 60 days is selected in the Truncate catalogs after option, in the Send metadata about items in the backup sets created within the specified number of days option, you need to select duration of less than 60 days.

  • If you want to send metadata about protected data of a virtual agent, ensure that the backup jobs are configured with the appropriate option in the Instant GRT tab. Go to Configuration and Settings > Job Defaults > Backup to Disk> Instant GRT. In this tab, select any of the following options:
    • Run a full catalog operation as a separate job immediately after the backup job finishes.
    • Schedule a full catalog operation as a separate job after the backup finishes.
  • It is recommended that you configure the scan schedule in the Veritas Connection Center to be outside your backup window.
  • If you have many servers for which you want to send item-level metadata to Information Map, it is recommended that you not enable all servers at the same time, and instead enable them in phases. Enable the servers after taking a full backup.

For example, if you have 10 servers, you can enable 3 servers first, then enable 3 more, and so on.


The following requirements are for integrating Backup Exec with Veritas Information Map.

  • Information Map displays metadata only for the servers that are configured in a domain.
  • For servers that are protected using CIFS backups (no remote agent is installed on the server)

For example, NAS box, ensure that the server is added in Backup Exec using its FQDN name.

  • For servers that have the remote agent installed, Backup Exec can determine its FQDN name irrespective of how the server is added in Backup Exec.
  • For CAS-MMS deployment, if the CAS server is registered with the Information Map Agent, the encryption key for backup sets of MMS must to be available on the CAS server to send metadata about such backup sets.
  • For CAS-MMS deployment, you must register with the Information Map Agent from the CAS server. Backup Exec sends item-level metadata from all servers in the CAS-MMS deployment. There is no requirement to register with the Information Map Agent from the MMS servers.
  • In CAS-MMS environment configured in distributed catalog mode, when the backup set is on MMS and such backup set is being scanned from CAS then a temporary file gets created on CAS server having scan task information.

Ensure that there is sufficient space on C: of CAS server. The required size is dependent on number of items in the backup set. For example, for 6 million items in backup set it needs ~100GB free space on CAS server’s C:

For more information about how to troubleshoot issues, refer to the following technote:



Was this content helpful?