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=
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!

Linux: Reset iptables firewall rules

Create a shell script ( and copy paste the following lines:

echo "Flushing iptables rules..."
sleep 1
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT

Make the file executable
chmod +x
and run the script:

Debian: NIC bonding (teaming) 32/64 bit OS

Install package ifenslave-2.6.
aptitude install ifenslave

make sure the real NICs kernel modules are loaded automatically
modprobe --list | grep -i bonding

edit /etc/network/interfaces and replace all references to eth0 to bond0. Also, replace “allow-hotplug” with “auto”, and save the file. You can use sed to do all this in one command:
sed 's/eth0/bond0/;s/allow-hotplug/auto/' </etc/network/interfaces

Execute the following commands:
echo "up /sbin/ifenslave bond0 eth0 eth1" >> /etc/network/interfaces
echo "down /sbin/ifenslave -d bond0 eth0 eth1" >> /etc/network/interfaces
echo "bonding" >> /etc/modules
echo "bonding mode=1 miimon=250 primary=eth0" >> /etc/modules

The above commands are equivalent to opening each file separately and adding the quoted lines manually.

Stop eth0:
ifdown eth0

And restart networking:

Debian: Etch x64 and VMware Server Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it.

A bit off-topic, but just a reminder that VMware Server 1.x is basically a 32 bit installer. To take care of compatibility issues make sure to install ia32-libs:
aptitude install ia32-libs

If you cannot connect to your console with the error message: Cannot connect to host x.x.x.x: No connection could be made because the target machine actively refused it, try to install inetutils-inetd:
aptitude install inetutils-inetd

Why? Because VMware-mui actually works and hooks with the package inetd which is not installed with 64 bit Debian by default.