Debian: Symantec Backup Exec 12 and Debian Etch 32/64

A quick note for users of BE 2010 and later: deb packages are now included with the product and you no longer need to user alien to convert from rpm. There is also an installer included with the product but you still HAVE TO install the deb package separately FIRST. Then run the installer “./installralus” from RALUS_RMALS_RAMS-xxxxxversion.tar.gz (yep, I assume you know that you’ll have to untar the archive, yada yada yada. Don’t forget to install libstdc++5 while you’re at it!).

Now for BE 12 and earlier

To install Symantec Backup Exec 12 agent under Debian Linux (32 and 64 bit). Version numbers have been masked with “xxx” to make it a general post.

Find the appropriate agent from the installer CD or download the latest version from Symantec website. 32 bit packages are normally under /Linux/RALUSx86/pkgs/Linux and 64 bit under /Linux/RALUS64/pkgs/Linux. Both packages must be properly installed: VRTSralus and VRTSvxmsa.

To untar:
tar -zxvf VRTSralus.tar.gz
tar -zxvf VRTSvxmsa.tar.gz

Symantec provides rpm packages so we will have to convert them to deb. If you don’t have the package “alien” installed use the command “aptitude install alien” to install the package.

Converting rpm to deb:
alien --scripts VRTSralus-xxx.rpm
alien --scripts VRTSvxmsa-xxx.rpm

(64 bit packages end with x86-64.rpm).

Installing deb packages:
dpkg -i vrtsralus-xxx-.deb
dpkg -i vrtsvxmsa-xxx-.deb

RALUS runs under a backup user called beoper. Go ahead and add the user/group and give it root access:
addgroup beoper
adduser root beoper

Before loading the agent for the first time install the following packages:
aptitude install libstdc++5
for 64 bit Debian you will need an additional package:
aptitude install ia32-libs
Now load the agent for the first time to have it create your configuration file. Backup Exec installation will copy your init script to /opt/VRTSralus/bin/VRTSralus.init. Either run it directly from there or create a symbolic link where your other scripts are:
ln -s opt/VRTSralus/bin/VRTSralus.init /etc/init.d
Load the agent:
/etc/init.d/VRTSralus.init start
OK confirms that your script ran properly, and if you followed my direction it should. Now kill the process
/etc/init.d/VRTSralus.init stop
and go open the configuration file
nano /etc/VRTSralus/ralus.cfg

Insert the following string and replace the IP to match your media server’s:

Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents\Agent Directory List_1=192.168.1.35
I have highlighted what I think is important: agent advertising option and your media server IP. Make sure they are correct and if you don’t have any of those lines go ahead and add them to your config file.

Save/close the file and re-run your agent. You’re all set! If you like to have the agent run every time your box reboots navigate to /etc/init.d/ and:
update-rc.d -f VRTSralus.init defaults
Note that Backup Exec 12.5 comes with a pre-compiled .deb package. Hooray for Symantec!

16 thoughts on “Debian: Symantec Backup Exec 12 and Debian Etch 32/64

  1. Erik says:

    Hi,

    Thanks for the excellent article. I just wanted to let you know that the installation procedure with BE 12.5 and the included .deb package is identical with this one (except that you dpkg -i the .deb file).

    The deb doesnt run any installer by it self, so you have to manually add the beoper group as described. I noticed that it chown’ed the fils in /opt/VRTS(..etc) to 100:10000 – so just to be on the safe side I chown’ed all the files in the bin folder to root:beoper.

  2. Jeff says:

    You have probably moved on from this post but… When I do this I get to the point where I am supposed to start the server but get a Permission Denied error. I am running Ubuntu 9 and BE 12.5. Any help would be greatly appreciated. Thanks.

  3. Jeff says:

    Here is a copy of my terminal. Does the fact that this is Ubuntu make a difference? Symantec said it does.

    root@nas:/# /opt/VRTSralus/bin/VRTSralus.init start
    bash: /opt/VRTSralus/bin/VRTSralus.init: Permission denied
    root@nas:/#

    • It very well might be as it’s not a Debian clone. Is root account active in your system? I’m talking about activating it permanently with ‘sudo passwd root’ and logging in directly as root, instead of sudo.

  4. Jeff says:

    I’m not sure but I’m going to guess probably not because I cannot login with the un of root. I am a complete newb so I will have to research how to do that if it might help. Is Red Hat a Debian clone? This is just a NAS on a Windows domain and nothing more so I really don’t care what OS it is as long as it is stable, fast, secure, free and I can use my newly purchased BE Linux license. Thanks

    • If it’s a server then use Debian… RedHat is not free. It seems like your root account is not active. To activate it use:

      sudo passwd root

      and follow directions. Once you’re done you can logon directly as root. If your BE is still not working I’d just go with Debian. You will be able to get support from Symantec if you use Debian, RedHat or SuSE.

  5. Tobias Nyström says:

    Jeff: You probably need to set the executable flag to the script with:

    chmod +x /opt/VRTSralus/bin/VRTSralus.init

    then run:

    /opt/VRTSralus/bin/VRTSralus.init start

  6. trigital says:

    Thank you. Excellent article that helped me very much.
    Did work also for the 64 Bit Agent of BackupExec 11d under Ubuntu LTS 10.04

    • You’re welcome. I’m glad Debian is becoming more mainstream every day… as I mentioned a deb package is included in 12.5 and newer!

  7. Sean says:

    Ali, Thanks for the blog post. Love hearing from the BE user community. If you ever have any questions or issues, drop me a tweet @seanjregan I work on the BE product team for Symantec.

Leave a Reply

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

Time limit is exhausted. Please reload CAPTCHA.