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.

I am trying to install the Backup Exec Agent on a CentOS server, but when i run the command sh./installralus.pl it returns the following error. Install Ralus Agent Centos Yum. I have just installed CentOS 6 64bit version, I'm trying to install a 32-bit application on a 64-bit machine and got this error.

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 NETWORKING_IPV6=no – 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 /etc/init.d/network 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 /etc/init.d/VRTSralus.init start or /etc/init.d/VRTSralus.init restart Posted in,,,, Tagged,,,,,, Post navigation.

I like stats and so I track visits to my blog. If you are using the 'Do not track' feature in most modern browsers my website will respect that. Diver T Program Dallas County Records here. I do not sell or share any information I collect. Other than to brag to friends on the internet. But I don't share your specific information.

It's more like 'Hey! Someone linked to my blog from a NetApp KB Article' but I digress. All data is stored on my server in Canada and only I have physical and remote access to it. As far as I know at least. Aug 7 16:09:41 localhost kernel: beremote[10898]: segfault at fffffffffffffffc ip fbc8cc sp 0c29d8 error 5 in libc-2.17.so[7f7543f3c000+1b6000] Aug 7 16:09:41 localhost abrt-hook-ccpp: Saved core dump of pid 10894 (/opt/VRTSralus/bin/beremote) to /var/tmp/abrt/ccpp-2014-08-07-16:4 (48660480 bytes) Aug 7 16:09:41 localhost abrt-server: Package 'VRTSralus' isn't signed with proper key Aug 7 16:09:41 localhost abrt-server: 'post-create' on '/var/tmp/abrt/ccpp-2014-08-07-16:4' exited with 1 Aug 7 16:09:41 localhost abrt-server: Deleting problem directory '/var/tmp/abrt/ccpp-2014-08-07-16:4'. [root@localhost bin]#./beremote --log-console f8a1b740 Thu Aug 7 16:: Starting BE Remote Agent f8a1b740 Thu Aug 7 16:: Requested no generation of log file f8a1b740 Thu Aug 7 16:: No configuration file specified.