Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Does the new SP4 work on SLES 11 SP3?

Created: 18 Mar 2014 • Updated: 18 Mar 2014 | 10 comments
This issue has been solved. See solution.

This morning I saw the new Service Pack 4 for Backup Exec 2012.

Does it support SLES 11 SP3?

 

Affected version: Backup Exec 2012 revision 1798  Remote Media Agent for Linux Servers (64bit Linux Platforms) - BERMALS

Post requisites - Remote Agent for Linux/Unix/Macintosh Servers (RALUS/RAMS) will need to be updated after installing this hotfix.

 

How do we update RALUS after updating to BE 2012 SP4?.

Operating Systems:

Comments 10 CommentsJump to latest comment

SuperBrain's picture

Found these instructions on a technote (TECH179999):

To apply the patch, follow these steps:
 
1. Locate the .tar file in C:\Program Files\Symantec\Backup Exec\Agents\ or C:\Program Files\Symantec\Backup Exec\Agents\RALUS. These files can be copied to your RALUS/RAMS/RMALS target system and contain the latest available RALUS/RAMS/RMALS patch. Symantec does not recommend uncompressing these files on the Windows media server. Download the hotfix .tar file.
2. Transfer the .tar file to the Linux/Unix system.  Note: If FTP is used to transfer the file, ensure that binary mode is enabled prior to GETting or PUTting the .tar file.  Most GUI-based FTP applications will do this automatically.  For more information, refer to the FTP client documentation.  Do not untar the file on a Windows system as this may corrupt the data.
3. Log in to a command line on the target system with root privileges.
4. Extract the file to a temporary location:
# cd /tmp
# tar -xvf <path and filename, for instance /home/user/ralus1364HF301340-Linux_301342.tar>
5. Run this command and follow any prompts on screen:
# ./installraluspatch.sh
 
 
To verify the hotfix installed on the RALUS/RAMS/RMALS system:
$ cat /var/VRTSralus/ralus.ver
The file will contains a number in the format of <product revision>.<hotfix number>.
Note: RALUS/RAMS/RMALS hotfixes cannot be uninstalled.  Removing and reinstalling RALUS/RAMS/RMALS from the installation media will revert the system back to the base version of RALUS/RAMS/RMALS with no hotfixes installed.
 
Note: As with the installation of any patch, it is important to run a full backup of the resources on each Agent for Windows and RALUS/RAMS/RMALS system for recovery purposes after installing the patch.

 

SuperBrain's picture

Also from the Software Compatibility List for Backup Exec 2012 I see it supports up to SLES 11 SP2.

Ananya Bhattacharya's picture

Please refer to the Software Compatibility List to check if the product version is supported which can be found at http://www.symantec.com/docs/TECH175581

Use http://www.symantec.com/docs/TECH185802 to install the latest patches on your Linux machine

Regards,

Ananya Bhattacharya
Technical Support Engineer (Advanced Team)

Ananya Bhattacharya's picture

Also you can refer to this document by Pkh to know more about installation of patches on Linux systems

https://www-secure.symantec.com/connect/zh-hans/blogs/how-install-patches-ralus-rmals-and-rams

Regards,

Ananya Bhattacharya
Technical Support Engineer (Advanced Team)

cadsh's picture

Does the new service pack 4 support SLES 11 SP3?

sidd3009's picture

As Superbrain has replied, BE2012 with Service Pack 4 does not support SLES with Service Pack 3. 

Regards,

Siddhant Saini
Advanced Technical Support Engineer, Symantec Corporation 
www.symantec.com

SOLUTION
SuperBrain's picture

U got lucky with this one Sid yessmiley

Artegic's picture

According to

http://blog.redweb.at/2012/08/howto-backupexec-2012-linux-agent-and-kernel-3-0-debian/#comment-266

service pack 4 does fix the bug that causes RALUS to crash when started on kernel 3.x. I will verify that shortly.

The SCL has not been updated to include any more recent Linux releases but that doesn't mean it won't work, just that Symantec support will refuse to listen to your problems.

Artegic's picture

The RALUS from BE 2012 SP4 can at least be started without crashing on a CentOS 6.5 system running kernel 3.12.1-1.el6.elrepo.x86_64. I'm still waiting for the next backup run to see whether it really works, but it sure looks like the bug is finally fixed.