Host discovery: EMC Avamar
In a specific circumstance, EMC Avamar data collection can persist duplicate clients in the Portal database. This occurs in the following case:
Multiple enterprise domains are configured.
The same host name is used in multiple domains, but for different hosts.
If your Portal has the above configuration, configure the following to prevent the creation of duplicate Avamar clients. And, logging can be configured to identify how a host is determined and persisted in the Portal database.
Note:
Another parameter, Enable IP address matching for Host search, is also used by the Avamar host-matching algorithm. If your environment has already enabled this parameter, it will be honored by the host-matching algorithm.
Enable short name matching for Avamar Host Search: This parameter is used to enable comparisons of a client's base name. During data collection, the data persistence logic will compare the short name retrieved by data collection and compare it to what exists in the Portal database. This parameter currently is used only while searching for a host in Avamar data. For example, the host name in the database might be xyz.aptare.com, but the collected host name is xyz.apt.com. If this parameter is enabled, the host-matching algorithm will find the host with the name, xyz.aptare.com, based on matching the short name, xyz, thereby preventing the creation of a duplicate host.
Remove patterns in host matching: This parameter will enable the stripping of unwanted suffixes while searching for hosts based on host name. This parameter is currently used only while searching for a host in Avamar data.
: Any suffix that needs to be ignored must first be inserted into the apt_host_name_excld_suffix database table, as described in the following procedure. When the parameter is enabled, the host-matching algorithm searches this table for suffixes that should be ignored.
Add suffixes to the database table:
INSERT INTO apt_host_name_excld_suffix (excld_suffix, suffix_length, priority) VALUES (<<excludeSuffixInitials>>,<<totalSuffixLength - lengthOfexcludeSuffixInitials>>, <<priority>>); COMMIT;
The data searching logic used when this system parameter is enabled is described in the following examples.
Host name in the database is xyz and the collected host name is xyz_UCMAAZWlR6kihhBHN5R8iA. The host-matching algorithm will find the host with the name xyz and _UCMAAZWlR6kihhBHN5R8iA will be removed while searching.
Host name in the database is xyz and the collected host name is xyz_UA3rT06VdULrQyViIxEFuQ2011.07.22.16.05.49. The host-matching algorithm will find the host with the name xyz and _UA3rT06VdULrQyViIxEFuQ2011.07.22.16.05.49 will be removed while searching. The time portion, 2011.07.22.16.05.49, is automatically removed if the parameter is enabled.
Host name in the database is xyz and the collected host name is xyz2011.07.22.16.05.49. The host-matching algorithm will find the host with the name xyz and 2011.07.22.16.05.49 will be removed while searching. The time portion, 2011.07.22.16.05.49, is automatically removed if the parameter is enabled.
Host name in database is xyz and the collected host name is xyz2011.07.22.16.05.49_UA3rT06VdULrQyViIxEFuQ. The host-matching algorithm will find the host with the name xyz and 2011.07.22.16.05.49_UA3rT06VdULrQyViIxEFuQ will be removed while searching. The time portion, 2011.07.22.16.05.49, is automatically removed if the parameter is enabled.