HOW TO install BackupExec 2010 agent on Debian (RALUS)

[magix]

I hope this post will be useful to many people (please vote for it or mark it as solution if it helps you).

Installing directly RALUS on Debian will not always work.

• First problem : ../perl/Linux/bin/perl: No such file or directory
• Second problem : at the end "was not successfully installed" and "impossible to add VRTSralus to (server)"
• And some others that will get solved when following my solution

This is a simple way to install it and avoid these (and other) problems :

1. (optional) Create a folder to keep all RALUS files and copy the archive into it :

• mkdir /root/BE
• mkdir /root/BE/RALUS2010
• mv RALUS_RMALS_RAMS-2896.9.tar.gz /root/BE/RALUS2010/
• cd /root/BE/RALUS2010

2. Unpack the archive provided by Symantec

• tar xzf RALUS_RMALS_RAMS-2896.9.tar.gz

3. Stop the RALUS service if it is already installed and runnig

• /etc/init.d/VRTSralus.init stop

4. Very important, if you are under a 64 bit Linux you have to this

• Extract debian package :
  tar xzf RALUS64/pkgs/Linux/VRTSralus.tar.gz
• Install debian package :
  dpkg -i VRTSralus-13.0.2896-0.x86_64.deb
• Start installation :
  ./RALUS64/installralus

5. But if you are under a 32 bit Linux you have to this (I didn't tested under 32 bits) :

• 
  Extract debian package :
  tar xzf pkgs/Linux/VRTSralus.tar.gz
• Install debian package :
  VRTSralus-13.0.2896-0.i386.deb
• Start installation :
  ./RALUSx86/installralus or ./installralus

6. Be sure to answer all questions correctly especially the one about the host server (XXX.XXX.XXX.XXX), you must give the IP of the Backup Exec server.

7. Do a restart of the RALUS Backup Exec agent, and it should say "[ OK ]"

• /etc/init.d/VRTSralus.init start

I hope it will help ! Send me questions if you have other problems...

Denis

P.S. Tested with Debian 5.0.3

P.P.S. If you still have some problems :

A) If you get "ERROR: VXIF_HOME is invalid. It must point to the root of VxIF. Exiting ...", simply edit ./RALUS64/installralus, and change line 3 :

• from : VXIF_HOME=../;export VXIF_HOME
• to : VXIF_HOME=/root/BE/RALUS2010/;export VXIF_HOME

B) If you get "./RALUS64/installralus: line 50: ../perl/Linux/bin/perl: No such file or directory", simply edit ./RALUS64/installralus, and change line 50 :

• from : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ../installralus.pl $*
• to : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ./installralus.pl $*
• or to : perl -I.. -I$PATH -I$VXIF_HOME ./installralus.pl $*
• (to be clear, remove one dot in front of"/installralus.pl", keep only one dot instead of two)

C) If the installation is sucessful but VRTSralus refuses to start, launch /opt/VRTSralus/bin/beremote –-log-console to see the error.
If you get error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory you simply need to install the package :

• Under Debian 6.0.3 : apt-get install libstdc++5 (Thanks to RockwellMuseum)

[SIGames]

64-bit Debian

I get the following error:
 ERROR: VXIF_HOME is invalid. It must point to the root of VxIF. Exiting ...

from the point at


4)
* Start installation :
./RALUS64/installralus

[magix]

Dear SIGames,

I now added a solution to your "VXIF_HOME is invalid" problem in my first post.
The solution is to change the path from relative "../" to absolute.

Strangely I also got this error on only one of my servers with same installation DVD and same procedure as the other servers.
Anyway, if you modify the perl script as explained under "P.P.S. A)" it should work !

Good luck :)

Denis

[chakrey]

After i do this process

B) If you get "./RALUS64/installralus: line 50: ../perl/Linux/bin/perl: No such file or directory", simply edit ./RALUS64/installralus, and change line 50 :

• from : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ../installralus.pl $*
• to : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ./installralus.pl $*
• or to : perl -I.. -I$PATH -I$VXIF_HOME ./installralus.pl $*
• (to be clear, remove one dot in front of"/installralus.pl", keep only one dot instead of two)

still get this error

Now it's working, after restart :)

[arsnova]

For Ubuntu 10.04 64-bit users upgrading to BE2010, these steps worked for me as well. It was necessary to adjust VXIF_HOME per the thread's addendum, and it also required libstdc++5 installed from the Ubuntu repositories (libstdc++5_3.3.6-17ubuntu1_amd64.deb). I created the 'beoper' group with root as a member prior to the RALUS installation.

Thanks, Magix, for the contribution!

[RockwellMuseum]

Specific OS used: Debian 2.6.26-13untangle4 32 bit

If you get the error "The installer was unable to determine the version of C++ Compatability Package..."
CTRL-C to stop the installation
apt-get install libstdc++5

If you then get "Package libstdc++5 is not available, but is referred to by by another package..."
Then download it with
wget http://ftp.us.debian.org/debian/pool/main/g/gcc-3.3/libstdc++5_3.3.6-18_i386.deb
Install it with
dpkg -i libstdc++5_3.3.6-18_i386.deb
Then retry ./installralus

[magix]

Dear arsnova and RockwellMuseum,

I'm very thankful for your comments with more solutions :)

I hope this thread will help everyone having difficulties while installing RALUS...

Best regards...

[henryluiz]

Hi

Has anyone successfult installed this version on Fedora v13 64bit. I have applied the chnages as above and now recieive an error

./RALUS64/installralus: ./perl/Linux/bin/perl: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

any help wuld be appreciated.

[itsmeaffinity]

Hi

Can you open new thread for  same seems to be old thread.

Much appreciated

Thank You

[magix]

Dear Henry,

I think this is looking like a Fedora/Linux error unrelated to Backup Exec...

I found lots of people having this problem :

• http://www.google.com/search?q=bad+ELF+interpreter%3A+No+such+file+or+directory&ie=utf-8&oe=utf-8&aq...

magix

[aloyr]

got it working with fedora 14 today. took us a bit, but the elf issue has to do with the fact that the version of perl shipped with BUE is compiled against 32-bit libraries.

i did a blog post about how I fixed it here: http://www.petercarrero.com/content/2011/02/01/installing-backupexec-agent-linux-hosts-64-bit-fedora...

essentially, what I did was recreate the perl folders that came inside the BUE installer with sym links to the 64-bit that is included in fedora. not that hard to do, and all is outlined on the link above.

this worked for us and i hope this helps you...

-A

[henryluiz]

Hi

i have managed to install BE 64 bit agent on Fedora 64 V12.

BE 64 bit window server sees the fedora server....i can login..... but when i browse an error message says

The version of the backup exec remote Agent is incompatible with the backup exe media server attemting to access it.

any ideas

Thank you

[JGreer]

When attempting step 5, part 2 (dpkg -i VRTSralus.....) I get the following error:

dpkg: error processing VRTSralus-13.0.2896.0.x86_64.deb (--install):

cannot access archive: No such file or directory.

Do I need to simply create the archive folder? If so, what path is it looking for?

Thanks,

Jeff

[DecInd_Support]

I was able to install the agent using your instructions.  I am also able to connect to the agent running on the Ubuntu Server but with I try to expand the folders all I see is the [ROOT] level.  I have tried calling Support but the agent is only supported on Version 7 and 8 of Ubuntu.  Below is the error I am getting – any help would be greatly appreciated.

52d6b70 Mon Jul 25 18:56:11 2011 : FS_ResolveDevName: [\]

52d6b70 Mon Jul 25 18:56:11 2011 : FS_BlowOutMachine: FS_ResolveDevName returns -->192.168.100.100<-- as the machineName

52d6b70 Mon Jul 25 18:56:11 2011 : FS_BlowOutMachine: processing as local machine

52d6b70 Mon Jul 25 18:56:11 2011 : FS_BlowOutMachine: returning 0

52d6b70 Mon Jul 25 18:56:11 2011 : ====>VX_AttachToDLE

52d6b70 Mon Jul 25 18:56:11 2011 : Resetting hard link info

52d6b70 Mon Jul 25 18:56:11 2011 : Hard link info has been reset

52d6b70 Mon Jul 25 18:56:11 2011 : VX_AttachToDLE: initializing mount list

52d6b70 Mon Jul 25 18:56:11 2011 : VX_AttachToDLE: create mount list returned 0

52d6b70 Mon Jul 25 18:56:11 2011 : Adding any excluded filesystems

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type devpts

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type proc

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type sysfs

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type rpc_pipefs

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type tmpfs

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type cd9660

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type ftp

52d6b70 Mon Jul 25 18:56:11 2011 : Excluding filesystem type ntfs

52d6b70 Mon Jul 25 18:56:11 2011 : Attach to: \\192.168.100.100\[ROOT]

52d6b70 Mon Jul 25 18:56:11 2011 : ====> VX_ChangeDir

52d6b70 Mon Jul 25 18:56:11 2011 : ====> VXX_ChangeDir : apath : , asize : 1

52d6b70 Mon Jul 25 18:56:11 2011 : ====>ChangeDir : psize : 1

52d6b70 Mon Jul 25 18:56:11 2011 :              vx_stat_by_name: Getting stat of /

52d6b70 Mon Jul 25 18:56:11 2011 : ===> gfsp vxms plugin: stat failed /home/tsupport/.gvfs errno 13

52d6b70 Mon Jul 25 18:56:11 2011 : ===> gfsp vxms plugin: stat failed /home/tsupport/.gvfs errno 13

52d6b70 Mon Jul 25 18:56:11 2011 : ===> vf_newpgn: couldn't initialize libgfsp.so

52d6b70 Mon Jul 25 18:56:11 2011 : Function vfmStatFileName, VxMS resolved the error code to this message: 

object not claimed by any plugin

52d6b70 Mon Jul 25 18:56:11 2011 :              vx_stat: objname is / returned 2059

52d6b70 Mon Jul 25 18:56:11 2011 :              vx_open_by_name: Opening object name : /, openflags : B

52d6b70 Mon Jul 25 18:56:11 2011 : ===> gfsp vxms plugin: stat failed /home/tsupport/.gvfs errno 13

52d6b70 Mon Jul 25 18:56:11 2011 : ===> gfsp vxms plugin: stat failed /home/tsupport/.gvfs errno 13

52d6b70 Mon Jul 25 18:56:11 2011 : ===> vf_newpgn: couldn't initialize libgfsp.so

52d6b70 Mon Jul 25 18:56:11 2011 : Function vfmOpenFileName, VxMS resolved the error code to this message: 

 object not claimed by any plugin

52d6b70 Mon Jul 25 18:56:11 2011 :              vx_open_by_name: Error : 2059

52d6b70 Mon Jul 25 18:56:11 2011 :              vx_open_by_name: new handle =(

52d6b70 Mon Jul 25 18:56:11 2011 :      VX_FindFirstFile: vx_open_by_name failed for path '/' errno=-536836984

52d6b70 Mon Jul 25 18:56:11 2011 : DSEnumerator failed with -536836945: 0

[jbrice]

except that /var/log/messages logs a segmentation fault as well. The FS is ext3 and there are no missing NFS mounts.  This looks like a compatibility issue with the file system even thouttgh it is ext3.  Anybody have any suggestions?

 Aug  1 22:03:39 home123-9 kernel: [31401.864652] beremote[3761]: segfault at 114cb010 ip 00007fa9108d7644 sp 00007fa9114cac60 error 6 in libext2fs.so[7fa9108ce000+e000]
 

[jbrice]

Make sure the current libext2fs.so for that platform is installed:

  apt-get install e2fslibs-dev
 

The replace the Ralus installed version of libext2fs.so....

 # find . -name libext2fs.so
./opt/VRTSralus/VRTSvxms/lib/map/libext2fs.so
./opt/VRTSralus/bin/VRTSvxms/lib/map/libext2fs.so
./usr/lib/libext2fs.so
# mv ./opt/VRTSralus/VRTSvxms/lib/map/libext2fs.so ./opt/VRTSralus/VRTSvxms/lib/map/libext2fs.so.old
# /etc/init.d/VRTSralus.init stop
Stopping Symantec Backup Exec Remote Agent
Stopping Symantec Backup Exec Remote Agent:                              [  OK  ]
# mv ./opt/VRTSralus/bin/VRTSvxms/lib/map/libext2fs.so ./opt/VRTSralus/bin/VRTSvxms/lib/map/libext2fs.so.old
# cp ./usr/lib/libext2fs.so ./opt/VRTSralus/VRTSvxms/lib/map/libext2fs.so
# cp ./usr/lib/libext2fs.so ./opt/VRTSralus/bin/VRTSvxms/lib/map/libext2fs.so
# /etc/init.d/VRTSralus.init start
Starting Symantec Backup Exec Remote Agent ......
Starting Symantec Backup Exec Remote Agent:                              [  OK  ]
 

Presto.....

[magix]

This is due to the fact your Backup Exec version is maybe older than your agent ?

Normallly you can use old agents version with new Backup Exec versions, but not the opposite...

[magix]

Woaw ! Congratulations, and thank you for your post with all details.

I am sure it will help people in the future !

Best regards !