Symantec Backup Exec RALUS crashes on CentOS 7

We just deployed our first CentOS 7 machine and are trying to back it up using Backup Exec 2010 R3 and the RALUS agent.

After installing the missing compatibility libraries needed for the RALUS:

the agent installs and starts but once the Media Server connects to it the agent crashes.

Some log digging came up with this from /var/log/messages:

and running the agent in debug mode shows this:

 

I’ve opened a case with Symantec and their answer was that CentOS isn’t supported and neither is RHEL7.

Anyone else running into this? Have you fixed it?

I found a blog post where someone suggested hex editing the beremote binary which I’d rather not do. Plus our version of the agent is newer than the one he describes in his post: http://blog.redweb.at/2012/08/howto-backupexec-2012-linux-agent-and-kernel-3-0-debian/

6 thoughts on “Symantec Backup Exec RALUS crashes on CentOS 7

  1. Did you ever find a solution to this?  Have the same issue on a new box and came across your post with the same exact issue we have.

    • No not yet. We’re relying on Snapshots of the VM taken via vSphere and our NetApp Storage.

      We did just recently upgrade to Backup Exec 2014. My co-worker told me the RALUS hasn’t been updated since 2012 though so I suspect the same problem exists.

  2. I would try the libbesocket.so patch in that blog post you linked (now dead, try http://preview.tinyurl.com/j2le9ke instead) — the process for finding the place to change in newer versions of the library file is well-described in both the article and the comments there (i.e. find ‘$0x8938’ within the hex dump, find the offset of the nearest ‘jns’ op after that.

    If you’ve already got an alternative (i.e. your snapshots) then it shouldn’t present too much risk, and its probably a lot easier to manage than the patched kernel recommended by https://www.veritas.com/support/en_US/article.TECH201095

    • I should have updated my post. The latest Linux Agent from BE 2014 works fine on CentOS 7.

      I’ll double check at work tomorrow but I’m pretty sure that’s what we ended up doing.

Leave a Reply

Your email address will not be published. Required fields are marked *