Data Collector Upgrades
For performance reasons, APTARE recommends that you do not install Data Collectors on the same server as the StorageConsole Portal. However, if you must have both on the same server, verify that the Portal and Data Collector software do not reside in the same directory.
• If you are upgrading to 10.2.00 from a version prior to 10.1.01 P5, in some situations, primarily on Windows Portals, the automatic Data Collector upgrades may not complete. Data Collectors will attempt to automatically upgrade to JRE 8. If this fails, there are two options you can select from to resolve this issue:
Uninstall the pre-10.1.01 P5 data collector and reinstall by manually running the 10.2.00 Data Collector installer
OR
Mandatory Prerequisites
• On Windows Data Collectors, close all DOS Command Console windows in any of the <APTARE_HOME> directories before upgrading.
• Do not use downloadlib.[sh|bat] to upgrade the binaries on the Data Collector. Initiate the Data Collector upgrade from the StorageConsole Portal.
Troubleshooting - Manual Data Collector Upgrades
If the Data Collector fails after completing the previous requirements and prerequisites, perform the following:
On the Collector Server:
1. Kill all running APTARE-related Java processes.
2. Start the APTARE Agent Service
3. If the APTARE Agent Service does not continue to run, verify no APTARE-related Java processes are running. If required, kill all running APTARE-related Java processes.
• Restart the Collector Server, if the Java processes cannot be killed manually. Prior to restarting the server, disable the automatic start of the APTARE Agent Service.
4. Rename <APTARE_HOME>/jre to jre.old.
5. Copy <APTARE_HOME>/upgrade/staging/snapshot/jre to <APTARE_HOME>/
6. Enable the automatic start of APTARE Agent service, if you previously disabled the service.
Collector Updates from the StorageConsole Portal
1. Log in to the StorageConsole portal, and navigate to Admin>Data Collection>Collector Updates.
2. Select the Data Collector that failed to upgrade.
3. Verify if either aptare.jar or Upgrade Manager failed to upgrade.
4. Click Upgrade Both, Upgrade aptare.jar, or Update Upgrade Manager, depending on what failed to upgrade. Allow up to an hour for completion, depending on the size of your system.
5. Contact APTARE Global Support Services for additional issues.
Data Domain Data Collector Policy Updates
Enhancements to Data Domain data collection enable a Test Connection function for individual Data Domain servers configured in the policy. The following lists explain the impact on an existing Data Domain Data Collector Policy.
Before APTARE StorageConsole 10.x.xx
Data Domain servers listed in a data collection policy could have any of the following formats:
• host name, such as HQfinance1
• IP address, such as 10.2.3.162
• range of IP addresses, such as 10.2.3.1-250
After APTARE StorageConsole 10.x.xx
Data Domain servers in a data collection policy are listed by host name and can be activated/deactivated individually. During the Portal upgrade, the servers in each Data Domain policy are migrated as follows:
• IP addresses now will be listed by host name.
• Ranges of IP addresses are evaluated and if an IP address is associated with a Data Domain server, the host name will be added to the Data Collector policy list.
• As part of the Portal upgrade, a process searches for relevant Data Domain servers and then adds them to the policy’s list as Inactive (unchecked) servers. They will be listed as Inactive until they are explicitly activated.
Best Practice After the Portal Upgrade for Data Domain Verification
After the Portal upgrade, take the following steps.
1. Edit the Data Collector policy to verify that all expected Data Domain servers are listed as Active.
2. To facilitate verification in large environments, use the new Export button in the Data Collector policy to export the servers to a comma-separated list.
3. If you determine that Data Domain servers are missing from a policy’s list, check the scon.log file for database migration messages.
Clustered NetBackup Upgrade Procedure
For Distributed NetBackup deployments only (Data Collector software is installed on each NetBackup Master Server)
Clustered NetBackup Nodes require a unique upgrade strategy in order to keep their Data Collector versions in synch:
• The active node automatically updates during the Portal upgrade process.
• The passive node requires a manual update.
To ensure that both the active and passive nodes in a clustered pair are operating with the same version of the Data Collector, take the following steps:
1. After a Portal upgrade, the Data Collector automatically updates the NetBackup Master active node to the latest aptare.jar version. This process then pushes the update to all the collectors in the policy.
2. Fail over to the passive node in order to make it the active node.
3. At the command line of the newly active node, use the downloadlib utility to manually download and update aptare.jar.
Windows: <Home>\mbs\bin\downloadlib.bat
Linux: <Home>/mbs/bin/downloadlib.sh
Note: Check with your Veritas representative to determine if anything needs to be disabled prior to taking this step on the newly active node so that the upgrade does not trigger an event.
Upgraded Methods to Incorporate Enterprise Objects
During a Portal upgrade to APTARE StorageConsole 10.x.xx, all Dynamic Template Designer Methods will be modified to associate a method with an enterprise object (such as an array or host), rather than the method being associated with a StorageConsole product (such as Capacity Manager).
The upgrader automatically makes the necessary changes, which may result in the following considerations:
• If the upgrader encounters a method that could apply to multiple enterprise objects (for example, a backup method that is relevant for both a Data Domain and a Job enterprise object), the upgrader makes a copy of the method with an Upgrade label append to the method name. This new version of the method has a populated enterprise object field so that your reports won’t fail. Note that the WITH clause alias in this new version will still reference the old name, but this will not cause reports to fail. You can modify this to make the method accurate, however, this modification is not required.
• Once upgraded, some methods may have a null value for the enterprise object. For example, a method that was created for Virtualization Manager does not have a corresponding supported enterprise object (Data Domain, Host, Job, or Storage Array). If such a method is found by the upgrader and the method is in use by a Dynamic Template, the upgrader implicitly assumes the enterprise object for the template is relevant and populates the enterprise object field accordingly. However, if the method currently is not in use, the enterprise object field remains null.
• Upgraded methods that result in null enterprise object values can be identified by viewing the list of methods:
Tools > Templates > Method Designer.
• To use a method in a Dynamic Template, the enterprise object field must be populated. Therefore, when you modify and save a method (Save/Save as), you will be prompted to select an enterprise object.