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

NBU 7 support #180

Closed
linuxdan opened this issue Nov 15, 2012 · 9 comments
Closed

NBU 7 support #180

linuxdan opened this issue Nov 15, 2012 · 9 comments
Assignees
Labels
enhancement Adaptions and new features waiting for info

Comments

@linuxdan
Copy link

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"

@ghost ghost assigned gdha Nov 15, 2012
@gdha
Copy link
Member

gdha commented Nov 15, 2012

thanks, a small enhancement has to be added into script rescue/NBU/default/45_prepare_xinetd.sh to skip the xinetd entries if NBU version >7+

Now, my question, how can we check with which version of NBU we're dealing with? is there a small command for it?

@linuxdan
Copy link
Author

/usr/openv/netbackup/bin/version

On the box in question, that file contains:
NetBackup-RedHat2.6 7.0.1
(space, not tab, separating kernel reference from NBU version)

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 .....

@gdha
Copy link
Member

gdha commented Nov 16, 2012

Verified the script a bit more in depth and noticed that xinetd will get started and when there are no vnetd or bpcd startup files found under /etc/xinetd.d then these two will start up as standalone.

PROGS=( "${PROGS[@]}" xinetd )
COPY_AS_IS=( "${COPY_AS_IS[@]}" /etc/xinetd.conf /etc/xinetd.d/bpcd /etc/xinetd.d/vnetd /etc/xinetd.d/vopied )
cat >$ROOTFS_DIR/etc/scripts/system-setup.d/90-xinetd.sh <<-EOF
echo "Starting a minimal xinetd daemon ..."
xinetd
if [ ! -f /etc/xinetd.d/vnetd ]; then
        /usr/openv/netbackup/bin/vnetd -standalone
fi
if [ ! -f /etc/xinetd.d/bpcd ]; then
        /usr/openv/netbackup/bin/bpcd -standalone
fi
EOF
chmod $v +x $ROOTFS_DIR/etc/scripts/system-setup.d/90-xinetd.sh >&2

In your case you should see 2 daemons running (even before you start up the recover process).
Can you verify this? Please carefully check your rear.log file to see what it complains about...

@linuxdan
Copy link
Author

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

@linuxdan
Copy link
Author

@dagwieers
Copy link
Contributor

FYI Github uses Gist for this (see link at the very top of every page).

@gdha
Copy link
Member

gdha commented Nov 17, 2012

I know the startup script of netbackup, but what I was trying to say was that the rescue/NBU/default/45_prepare_xinetd.sh has a double function.
1/ when it finds NBU controlled by xinetd then it will use that
2/ when there are no xinetd startup files then it will start these daemons in standalone mode. In your case this will be the case.

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 nbftclnt (NetBackup SAN Client Fibre Transport daemon) and I'm not sure it gets copied. This might be your problem.

gdha added a commit that referenced this issue Nov 19, 2012
@gdha
Copy link
Member

gdha commented Nov 23, 2012

@linuxdan is it possible to try out with the latest git repository? All feedback is welcome

@gdha
Copy link
Member

gdha commented Feb 25, 2013

@linuxdan Can we close this???

@gdha gdha closed this as completed Mar 15, 2013
dagwieers pushed a commit to dagwieers/rear that referenced this issue Jun 7, 2013
dagwieers pushed a commit to dagwieers/rear that referenced this issue Jun 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adaptions and new features waiting for info
Projects
None yet
Development

No branches or pull requests

3 participants