DD Boost OST Plugin Sometimes Generates a Strange Storage Server Name Causing Backup and Restore Failure
Summary: DD Boost plug-in name resolution of the Data Domain may result in an unexpected hostname on some client operating system versions.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
On Red Hat Enterprise Linux 8 systems, DD Boost plug-in calls to resolve the Data Domain may intermittently result in an unexpected name being used.
Example:
The first hostname is the expected hostname, but characters 6-22 are overwritten with characters from 17-33 and creates the second hostname.
Example:
The first hostname is the expected hostname, but characters 6-22 are overwritten with characters from 17-33 and creates the second hostname.
AAAAABBBBBBBBBBCDEFGHIJKLMNOPQRST.GREAT.MYCOMPANY AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST.GREAT.MYCOMPANY ^^^^^^^^^^^^^^^^This new name is not resolvable by the Domain Name System (DNS), and causes backup and restore failures.
Cause
A call to a standard function in Red Hat Enterprise Linux 8 intermittently returns an unexpected value. The plug-in mis-interpreted this and results in the mangled hostname.
Resolution
Upgrade the DD Boost Plugin to version 7.10.1.20+ or 8.0+. These versions contain a fix that accounts for the intermittent difference in a standard function response within Red Hat Enterprise Linux 8.
Workaround:
Add a local host entry on the impacted system to resolve the mangled name to the correct IP address.
(If you have several Data Domains with similar names that are being mangled to the same name, then the below workaround only works if you can limit the media server to only access one of the Data Domains so that name resolution can work to the correct IP address.)
Media server B: (NBU configuration limits access to DD - AAAAACCCCCBBBBBCDEFGHIJKLMNOPQRS)
Workaround:
Add a local host entry on the impacted system to resolve the mangled name to the correct IP address.
(If you have several Data Domains with similar names that are being mangled to the same name, then the below workaround only works if you can limit the media server to only access one of the Data Domains so that name resolution can work to the correct IP address.)
- Example: /etc/hosts file
<IP address> <FQDN of original hostname> <short hostname> <FQDN of the mangled hostname> <short mangled hostname>
10.10.10.10 AAAAABBBBBBBBBBCDEFGHIJKLMNOPQRST.GREAT.MYCOMPANY AAAAABBBBBBBBBBCDEFGHIJKLMNOPQRST AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST.GREAT.MYCOMPANY AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST
- Example of two media servers with similar DD names.
Media server A: (NBU configuration limits access to DD - AAAAABBBBBBBBBBCDEFGHIJKLMNOPQRS)
/etc/hosts file: 10.10.10.10 AAAAABBBBBBBBBBCDEFGHIJKLMNOPQRST.GREAT.MYCOMPANY AAAAABBBBBBBBBBCDEFGHIJKLMNOPQRST AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST.GREAT.MYCOMPANY AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST
Media server B: (NBU configuration limits access to DD - AAAAACCCCCBBBBBCDEFGHIJKLMNOPQRS)
/etc/hosts file: 10.10.20.20 AAAAACCCCCBBBBBCDEFGHIJKLMNOPQRST.GREAT.MYCOMPANY AAAAACCCCCBBBBBCDEFGHIJKLMNOPQRST AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST.GREAT.MYCOMPANY AAAAADEFGHIJKLMNOPQRSIJKLMNOPQRST
Affected Products
Data DomainProducts
Data Domain ReplicatorArticle Properties
Article Number: 000219160
Article Type: Solution
Last Modified: 23 Feb 2024
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.