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
Information Map Agent issues
This section provides an overview of the common issues that you may encounter during an Agent installation and registration. The section also describes the steps you can perform to work around these issues.
Make sure that you configure the proxy setting while installing the Agent or at a later time.
For instructions to configure the proxy settings, see Configuring proxy settings.
To verify whether the Agent is installed successfully
Once the Agent is installed, ensure there is connectivity between the Agent and the NetBackup master server before you continue.
Error code 25 signifies that network connectivity is not available between the Agent and the NetBackup master server.
From the Agent server ping the master server. Make sure that the reverse and forward DNS lookup is working.
From
<install_directory>\bin, run the following command:connector_config.exe test_conn_<hostname of master server>. You should see the connection successful output.
If you cannot connect either to the master server from the Agent server or the other way, then verify the firewall settings.
Ensure that the communication between the Information Map Agent and the NetBackup master server is configured. You must add the Fully Qualified Domain Name (FQDN) of the Agent server to the NetBackup master server.
To configure communication between the Information Map Agent and the master server,
See Configuring access to a NetBackup master server.
Note:
Error code 37 signifies that Agent server host name is not added to the NetBackup master server.
The Agent must be authorized to connect and collect the catalog data from NetBackup, you must modify the
bp.conffile located at/usr/openv/netbackupon a UNIX master server to add an entry for the Agent. In case of a Windows master server, in the Registry Editor, navigate to HKEY_LOCAL_MACHINE > Software > Veritas > NetBackup > CurrentVersion > Config > Server, and add the Agent server entry to the list.
Various Agent processes run to extract the metadata from the NetBackup master servers and to populate the content sources in the Information Map application.
To check the Agent processes
- Open the command prompt from the
<install_directory>\binfolder and execute the following command to check the status of Agent jobs:configcli.exe list_jobs
- Look for
NbuDiscoveryJobandNbuIFConfigSyncJobin the listing as these are the first jobs to run. If there is an asterisk (*) next to a job name, it indicates that the job is running. For more information, check the last run time. - Monitor the
<data_dir>/nbu/outboxfolder to see if the output is being created. Once the Agent completes the discovery, you should see the following files in the outbox folder:nbu_discovery_contentsources_<master server ID>_<timestamp>
nbu_discovery_containers_<master server ID>_<timestamp>
scan_nbu*.json files containing the scan meta data based on the scanning schedule of the task.
If the output is created, but it does not appear in the Information Map content sources list, then there may be an issue with the firewall. For more details, check the firewall settings.
- Review the following Agent logs located at
<install dir>/bin. Scroll to the end of the log file and work back up to understand the issue.commd0_0.log- Contains details of the overall discovery process and about communication with the master server.nbu_scan0.0.log- Contains the scan statistics such as how many paths were scanned, the scan throughput the duration of the scan, and if there are any issues with the scan.
The Agent server periodically sends a signal to the Information Fabric technology platform. The status indicates the availability of the Agent server and notifies you if the application is not receiving a signal from it. By, default, the NbuIFConfigSyncJob process sends the heartbeat information every 2 minutes. You can view the heartbeat status on the Administration > Task Controllers page.
If the NbuIFConfigSyncJob process is heavily loaded, it may not be able to send the heartbeat status. In this case, the NbuIFHeartBeatJob process takes over and sends the heartbeat information every 2 minutes. You can configure a higher threshold for the NbuIFConfigSyncJob process.
To configure the heartbeat threshold
- Open the command prompt from the
< install_directory>\binfolder and execute the following command:configdb -o -T node -k 1 -J node.nbu.heartbeat.threshold -j 5
Where, 5 is the time in minutes.
Note:
You must type the command in the command prompt. Do not copy/paste it.
The Agent can exchange information with the Information Fabric technology platform only when it is authenticated using the key pair. The key pair authentication is performed during the registration stage. While completing the registration, if you get a key pair mismatch error or you forgot the key pair, then you must contact the Information Map Technical Support team. The Technical Support team will troubleshoot the issue and request you to regenerate the key pair.
Note:
The Keystore file holds the encrypted key pair.
For more information on regenerating the keystore, see Generating a KeyStore file.