All Backup Vendors
The topics covered in this section apply to all supported backup vendors.
Verify the Data Collector Configuration
The Data Collector configuration file contains key information captured during the installation process. If the information was entered incorrectly, this may be the cause of the failure.
Check the Configuration File
1. Edit the configuration file.
Windows:
edit “C:\Program Files\Aptare\mbs\conf\wrapper.conf”
Linux:
edit “/opt/aptare/mbs/bin/startup.sh” and "/opt/aptare/mbs/bin/updateconfig.sh"
2. Verify the values of the following parameters and update them, if necessary.
wrapper.app.parameter.2 | Should match the Collector Name you specified in “Adding/Editing Data Collectors” on page 17. |
wrapper.app.parameter.3 | Should match the Passcode you specified in “Adding/Editing Data Collectors” on page 17. |
wrapper.app.parameter.4 | For IN-HOUSE installations: http://aptareagent.yourdomain.com where: yourdomain.com has the appropriate value. For APTARE HOSTED installations: http://agent.storageconsole.com For third-party HOSTED installations: http://aptareagent.domain.com where: domain.com has the appropriate value. |
3. If you changed any of the configuration file parameters, you’ll need to:
Verify Connectivity
To verify that the Data Collector Server can access the Portal Server:
1. Ping the Data Collector URL:
ping http://aptareagent.yourdomain.com
2. Verify that the URL has been set up correctly in DNS or in the local hosts file, to resolve to the Portal Server.
Configuring Web Proxy Updates
If you are using a proxy server to connect to the Portal, the Data Collector was configured during installation to use the proxy to connect to the Portal. If the web proxy configuration changes in your environment, the Data Collector must be aware of those changes in order to maintain connectivity. These settings can be found in:
/opt/aptare/mbs/conf/collectorsystem.properties