Veritas Information Map Installation and Administration Guide
- Introduction to Veritas Information Map
- Planning installation of the Information Map Agent
- Installing and configuring Information Map
- Logging in to Veritas Information Map
- Downloading the Agent installer
- Configuring locations in Information Map
- Installing the Information Map Agent
- Registering the Information Map Agent with Information Fabric
- Configuring credentials for share discovery and native scanning
- Updating the Information Map Agent
- Cloud Agent configuration
- Global settings
- Managing Information Map settings
- Troubleshooting
Managing content sources
The Information Map agents scan data stores to discover content sources (physical storage devices, such as NetApp and EMC file server targets or content repositories such as Amazon S3 buckets).
Information Map scans run at a scheduled time. During the scan, it first discovers information about the content sources on-premises or cloud) and the underlying containers (shares) on those content sources. If a terabyte (TB) cap is in place, newly discovered content sources are disabled by default. Once enabled, the Information Map agents will proceed with the item-level metadata collection from the content sources .
You can view details of the content sources discovered by the Information Map Agent, on the page of the portal.
You can edit the following three properties for each content source - manual selection of the storage tier, location, and the content collection status.
Content source location
A content source's location is typically determined automatically by pattern matching its IP address against the subnet CIDRs assigned to the location. This method, while effective for the majority of use cases, may not assign the content source correctly if IP addresses clash across locations. In this case, you can manually set the location the application should use when processing content under that content source.
For Amazon S3 data store, the location is fixed based on the known location of the AWS bucket. However, you cannot edit the location.
Discovery date
The date and time when the content source was first discovered by an Information Map agents.
Note:
The date will be Unknown for all content source sizes discovered by the Information Map NetBackup Agent before upgrading to the October 2016 release (version 1.0.0.1137) of the Agent.
Size
In case of physical content repositories, the approximate size of the content source as reported by the Information Map Agent is displayed. For example, this size is calculated by querying the NetBackup master server for a combined size of all policies configured to back up the content source. The size within NetBackup is only updated upon a full backup, so the size should be used only as an additional guide for choosing whether to enable the content source for collection.
In case of cloud content repositories, the accurate size is always displayed if Information Map has access to the bucket . If Information Map does not have permissions to access the bucket . then the size is displayed as Unknown.
If the content source is enabled and is processed within the last 24 hours, the approximate size of the content source corresponds to the total size of data collected so far and presented within the Information Map.
When one or more content sources with an unknown size are selected, the total size is at least the sum of known sizes. Content sources with an unknown size can be enabled unless the cap is exceeded.
Note:
The size may be Unknown if the Information Map Agent is unable to determine a size from NetBackup.
Collection status
By default, the collection of item metadata is disabled for all content sources that the Agent discovers. You must manually enable collection for the content sources that you do not wish to submit to the Information Fabric technology platform.
Note:
Content Sources can only be enabled if the combined size of all enabled content sources is within your terabyte (TB) cap. Content sources with an unknown size can always be enabled unless the FETB cap has already been exceeded. Metadata collection occurs for all enabled content sources, however if the TB cap is exceeded, existing content sources must be disabled to bring the total size below the TB cap before any other content sources can be enabled.
A message warns users if they enable collection for the content sources after the configured cap limit is reached.
Storage tier
By default, the parent location's storage tier is used to calculate the cost of information. You can edit the property to manually assign a tier to use for these calculations.
You can disable collection of metadata for the content sources that you do not wish to submit to the Information Fabric technology platform or want to make visible within the Information Map. For example, you can disable collection for content sources that may have sensitive information.
When collection for a specific content source is disabled, the following actions take place:
An Agent will stop reporting data for the disabled content source and the underlying containers.
An Agent does not discover any newly added containers for that content source.
The Information Fabric will not take into account the metadata for the containers belonging to the disabled content source.
The disabled content source and the underlying containers will not be visible within the Information Map application.
To edit content sources
- On the vertical navigation panel in the Information Map application, expand the Administration section and click Content Sources.
- From the list, select the item you wish to edit, or use the check boxes to select multiple items.
- Select the check box for the content source for which you want to enable/disable collection.
If using Information Map in trial mode, ensure that the content sources selected to enable collection does not exceed the capped capacity.
- Click Edit.
On the Edit panel, modify the value, and click Save to apply the change.
- Click Yes on the confirmation dialog.
If multiple items are edited, the confirmation dialog displays the progress of the status change and errors, if any. Click Retry to initiate the save action for the failed content sources.
Note:
If you change the collection status for a content source, it may take up to 24 hours before the data for that content source is reflected in the Information Map application. Similarly, any changes to the storage tier definition can take up to 24 hours to take effect in the cost displayed in the Information Map application.