Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes for NetBackup (NBU) support #2544

Merged
merged 2 commits into from Jan 26, 2021

Conversation

pcahyna
Copy link
Member

@pcahyna pcahyna commented Dec 16, 2020

Pull Request Details:
  • Type: Bug Fix

  • Impact: High

  • How was this pull request tested?

Tested by a customer using ReaR (2.4 version in RHEL 8) with NetBackup 8.2

  • Brief description of the changes in this pull request:

It was found by our customer that when attempting to restore from NetBackup, bprestore is unable to restore data from NetBackup server:

EXIT STATUS 25: cannot connect on socket
bprestore failed (return code = 25)

The fix is to copy the NetBackup PBX (vxpbx_exchanged) service to the rescue system and start it on boot before starting NetBackup. Additionally, it was needed to add the /usr/openv/tmp directory.

The problem was reported for NetBackup 8.2, but the service is apparently needed even in older versions of NetBackup (https://www.veritas.com/support/en_US/article.100031908). There were fixes for previous NetBackup versions in ReaR reported by @rmetrich, so I don't know why the problem was not seen at that time.

Copy NetBackup PBX related files to the rescue system and start
vxpbx_exchanged on boot
Add /usr/openv/tmp directory to the NBU skeleton
@gdha gdha added enhancement external tool The issue depends on non common software e.g. third-party backup tools. labels Dec 17, 2020
@gdha gdha self-assigned this Dec 17, 2020
@gdha gdha requested a review from jsmeix December 17, 2020 13:25
@gdha gdha added this to the ReaR v2.7 milestone Dec 17, 2020
@gdha
Copy link
Member

gdha commented Dec 17, 2020

@pcahyna updates look good to me and these were tested as you mentioned, so I'm good. Question: no plans to replace rear-2.4 with rear-2.7 on RH when it would be released?
@jsmeix any comments from your side before we perform the PR?

@gdha gdha self-requested a review January 26, 2021 13:44
@gdha gdha merged commit 285c0c7 into rear:master Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement external tool The issue depends on non common software e.g. third-party backup tools. fixed / solved / done
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants