SysAdmin Adventures

I can happily confirm that Veritas NetBackup’s RedHat2.6 client installer works absolutely perfectly for Slackware. So all of you who are stuck with Veritas NetBackup can rest easy.

Simply:

1. Run the installer
2. Delete the symlinks it creates in /etc/rc.d/rc{x}.d
3. Move /etc/init.d/nbclient to /etc/rc.d/rc.nbclient
4. chmod 755 /etc/rc.d/rc.nbclient
5. Add “/etc/rc.d/rc.nbclient start” to /etc/rc.d/rc.local
6. Add “/etc/rc.d/rc.nbclient stop” to /etc/rc.d/rc.local_shutdown
7. Configure client & server policies on the server.

Worth noting that I use this config for the Slackware clients at the moment:
/usr/openv/netbackup/bp.conf:

SERVER = [server-name]
CLIENT_NAME = [client-name]
USEMAIL = [e-mail address]
MEGABYTES_OF_MEMORY = 512
SERVER_SENDS_MAIL = YES
BUSY_FILE_PROCESSING
BUSY_FILE_DIRECTORY = /tmp
BUSY_FILE_ACTION = /* mail
BUSY_FILE_ACTION = /* repeat 2

Update: In Slackware64-13.0 you need the multilib stuff to get this working because it’s only released as x86 and IA64, not x86_64 – but there’s a gotcha. The installer provides its own copy of x86 tar which depends on x86 libacl.so.1 which even the multilib packages don’t provide. Initially I set about trying to put an x86 libacl.so.1 into the Slack64 box until I realised I was going about it the wrong way:

UPDATE 20100222:
NetBackup 7 has been released and I have it running as a server on Slackware64-13.1:
http://blog.tpa.me.uk/2010/02/22/netbackup-7-server-on-slackware64-13-1/

Be Sociable, Share!

•