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
NBU 7 support #180
Comments
thanks, a small enhancement has to be added into script Now, my question, how can we check with which version of NBU we're dealing with? is there a small command for it? |
/usr/openv/netbackup/bin/version On the box in question, that file contains: On older servers, the file says: NetBackup-RedHat2.4 6.5 or NetBackup-RedHat2.6 6.5 Now if I can just figure out why the bplist command barfs ..... |
Verified the script a bit more in depth and noticed that
In your case you should see 2 daemons running (even before you start up the recover process). |
NBU 7+ does not use xinetd. bpcd and vnetd and nbftclnt (NetBackup SAN Client Fibre Transport daemon) I am kinda new to GitHub and this issue interface. I'd like to upload the /etc/init.d/netbackup script for you rather than pasting it in here. 600+ lines :( If there is no built-in for that, I will use PasteBin |
FYI Github uses Gist for this (see link at the very top of every page). |
I know the startup script of netbackup, but what I was trying to say was that the I believe that the NBU startup script does exactly the same as what I described in step 2. The only daemon that is not started is |
of the different NBU daemons - issue #180
@linuxdan is it possible to try out with the latest git repository? All feedback is welcome |
@linuxdan Can we close this??? |
of the different NBU daemons - issue rear#180
NBU support in the current package appears to be targeting NBU v6.5 because it references xinetd.
NBU 7+ no longer uses xinetd and the bplist command in the NBU-prep returns "EXIT STATUS 227: no entity was found"
The text was updated successfully, but these errors were encountered: