Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    12
  • Views views
    102
  • Users 0 members are here
Related
Options

DP23_4 Unable to create gateway on RHEL Dedupe store server

Andy Heath

Hi,

We have a simple set up in a small standalone environment we're building using DP23_4:

  • VM1 - DP Cell Manager RHEL 8.8
  • VM2 - DP RHEL 8.8 Media Server with Dedupe Store
  • VM3 - DP Windows 2016 Media Server with Dedupe Store

Plan is to spread the backups between both media servers, backups made up of VM backups, selected filesystem backups, and potentially SQL/Oracle in the future. We have created new Deduplication Stores on each of the media servers. The Dedupe Stores have a backend dedicated storage array used for backups only, with the VM's themselves on a different set of storage arrays. So a simple setup, well looks simple to us!

We created the Windows Dedupe Store first, added DP agents (Disk/General Media/User Interface/Virtual Environment Integration/Deduplication Store/Storeonce Software Deduplication), created the dedupe store, and created gateways successfully for all three servers to access the Dedupe Store on the Windows server. Great, working a treat, all three servers can see and use the Dedupe Store on Windows.

Move on to the RHEL media server, created it's Dedupe Store, but had problems with gateways. Managed to create a gateway talking back to VM1/VM3 just fine, but when we tried to create the local gateway on the RHEL media server itself, it failed. Error message:

12:17302 Failed to establish sdfs client proxy connection

I couldn't find any help online for that code, has anyone got any further info about a cause for this error? 

Cheers,

Andy

  • 0  

    Andy,

    I found a similar issue on 23.4 in our support database, unfortunately without a solution as the customer moved to another setup. Are you able to report this in a support case and provide debugs of the failure? That would be the best way forward. If you drop me the case ID then I can put my comments into the case.

    Thanks.

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

  • 0 in reply to   

    Hi Koen,

    Thanks for the reply, good to know it's not just us who have the problem! Frustratingly we unable to upload any logs to 3rd parties for analysis, we can only raise the issue in our own words, with any pertinent error messages. This makes it a pain for 3rd parties, I know, I've seen it from both sides of the support fence myself over the years.

    As with the other customer, we can work around the issue ourselves, we can use the cell manager to be the gateway to write out to the Linux media server which has the Dedupe Store on it. This new environment is pretty small, all virtualised, dedicated segregated network, so jumping from one box to act as the gateway to another which has the Dedupe Store is no big deal. 

    Given someone else has already logged it, and we can't send debug logs, we'll hold off raising another case, unless you would like us too to show it's affecting more than one customer.

    Cheers,

    Andy

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.