Whew, what a pain this has been.
Always had a heck of a time with BackupExec 12.5 and below backing up CentOS versions. I think early versions of RALUS were operational and worked back in the BackupExec 8-10.5 days prior to Symantec’s acquistion of Veritas. But, it has never been really easy to get this going well and incorporating a RedHat-like but not RedHat system into the BackupExec remote client world. Bring in 64-bit CentOS, and it got even more of a pain.
Well, now it seems it is possible and repeatable with Symantec BackupExec 2010. The change in naming conventions off the versions to years (even though everyone else is going back to the versions and moving off of years now!) signifies some code investment from Symantec in what must be a cash-cow for them in BackupExec.
We have a few Windows 2003 and 2008 servers along with some OS X 10.5.x servers and are backing them up to a LTO3 library on a 2008 server and made the move to BackupExec 2010 recently to try and shake some of the lingering issues with 12.5 rehashed code and makeshift RALUS client patches for Unix, Linux and Mac clients Symantec seems to have inherited and continued.
It seems you need to disable IPv6 to get the negotiation to happen correctly on top of the obvious IPTables and IPTables configurations to allow TCP ports 10000 and 6101 to communication between the BackupExec Server and your RALUS client.
Disabling IPv6 on CentOS (run all as root or you can sudo everything below)
– in /etc/sysconfig/network you need to add
– in /etc/modprobe.conf add:
alias ipv6 off
alias net-pf-10 off
– make sure IPTablesv6 is disabled at startup
/sbin/chkconfig ip6tables off
After all of that, give your network a restart
Then run the RALUS install from the Symantec BE 2010 download. If you have issues here during the install and possibly have multiple network interfaces straddling different networks, try ip addresses in lieu of hostnames. Also, on the BE 2010 server, restart all the services. Starting the RALUS client on CentOS 5 is