1. Support
  2. Knowledge base
  3. 100025904

Backup Exec for Windows Servers hotfix and service pack installation guide.

Article: 100025904
Last Published: 2017-12-07
Ratings: 1 0
Product(s): Backup Exec

Problem

Backup Exec for Windows Servers hotfix and service pack installation guide.

Solution

This installation guide outlines steps on how to install hotfixes and service packs in different Backup Exec configurations.  Not all configurations will be applicable to every environment; refer to only those used in the environment where the hotfix/service pack is being deployed.

Live Update Installation Procedure

To install a hotfix/service pack on a media server using Live Update, within the Backup Exec console go to 'Menu > Installation and Licensing > Live Update'. By default Live Update will be launched in Express mode and after clicking next any available patches will be installed.

Note:  In order to see the hotfix(s)/service pack(s) that are available first and then choose which to install, it is necessary to change the mode from Express to Interactive. To do this, go to 'Options > Configure' on the initial Live Update screen and change the install mode. The Interactive mode will also allow more details to be seen about each available update before it is installed.
Agent for Windows (RAWS) 32bit and x64bit

Note : The Remote Agent for Windows Servers (RAWS) has been renamed to Agent for Windows in Backup Exec 2012 and above.


After installing the hotfix/service pack to the Backup Exec media server(s) perform one of the following to update any machines with the Remote Agent:
1. Push install the Remote Agent to all servers from the Backup and Restore tab by right clicking on the Agent for Windows Server and clicking Update.
The remote agent patching or update process creates a job that can be scheduled on a recurrence, run on date, or run now.
2. Push install the Remote Agent to all servers from the Backup Exec button select Installation and Licensing > Install Agents and Backup Exec Servers on Other servers.
-OR-
3. Copy the Remote Agent installation files from C:\Program Files\Symantec\Backup Exec\Agents\RAWS32 (for 32bit) or C:\Program Files\Symantec\Backup Exec\Agents\RAWSX64 (for x64bit) to the server where the Remote Agent is installed.  Once copied run the setupaa.cmd or setupaax64.cmd file to update the Remote Agent.


      See Related Documents 000016001 for more information on how to install\update the Agent for Windows Server.

 

Microsoft Cluster

The hotfix/service pack must be installed on all nodes of the cluster. After installing the hotfix/service pack on the primary node, use the cluster administrator to move the BEWS group to each node in the cluster, and run the hotfix/service pack installation again on that node.  This must be done for each node in the cluster.



Central Administration Servers

Before installing the hotfix/service pack on a Backup Exec Central Administration Server (CAS), see the About upgrading an existing CASO installation section in the Backup Exec Administrator's Guide for recommendations on upgrading CAS and Managed Backup Exec server systems.

 

Remote Agent for Linux/Unix Servers (RALUS), Remote Agent for Macintosh Systems (RAMS), and Remote Media Agent for Linux Servers (RMALS)


If the hotfix is identified as targeting RALUS/RAMS/RMALS and you have RALUS/RAMS/RMALS systems in your environment, you must deploy the patch to all RALUS/RAMS/RMALS protected systems in your environment.  Note that some patches affect only certain platforms - for example, a patch that targets only Linux does not need to be applied to systems running RALUS on Solaris.  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.
Example: ralus1786.1009HF218527.tar.gz represents a hotfix "HF" and hotfix number  218527.    Example:  ralus1798.1364SP4.tar.gz represents a Service Pack "SP".   Veritas does not recommend uncompressing these files on the Windows media server. 
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.



 

 


Was this content helpful?

Article Languages