How to install Backup Exec Remote Agent for Windows

-
How to install Backup Exec Remote Agent for Windows Servers (RAWS) and/or Advanced Open File Option (AOFO) for Backup Exec 11d - 2010 R3.

We can install BE Agent in 3 way.  Please follow the below instructions on how to install Backup Exec Remote Agent for Windows System (RAWS):

   1. Automated (push) Installation. (to be performed from the Backup Exec media server) 
  2. Local (manual) installation. (to be performed on the remote machine) 
  3. Silent (command line) installation. (to be performed on the remote machine)


1. Automated (Push) Installation of RAWS:
 

  1. On the media server, open the Backup Exec console.
     
  2. Go to Tools - Install Agents & Media Servers on Other Servers 

    Note:     For Backup Exec 11d / 10.x go to Tools - Install Remote Agents.
  3. On the 'Remote Install' / 'Remote Server' section perform one of the following to add remote servers:
    1. For Backup Exec 11d - 12.5:
      • Right-click Windows Remote Agents and select Add Remote computer
      • Click on the drop down menu under Add

        OR
         
    2. For Backup Exec 2010 / 2010 R2 / 2010 R3
      • Choose Add a Single Server (If Remote Agent needs to be installed on only one server)
      • Choose Add Multiple Servers with the Same Settings (To select multiple servers for Remote Agent Installation)
        Note: The Box Save the server list for future remote installation sessions enables the names of all the remote computers and their credentials to be added automatically the next time Backup Exec or any of its options need to be installed to these remote computers.
         
  4. From the Select the Remote Product under Choose the Product to Install: Select Remote Agent for Windows Systems
  5. On the Choose Remote Server(s) screen:
    1. When selecting Add a Single Server:
      • Enter the Remote Server Name
      • Enter the Remote Install Credentials (type the user name and password of the account that has administrative rights on Server)

        OR
         
    2. When selecting Add Multiple Servers with the Same Settings
      • Enter the Remote Server Name
      • Click Add to List 
        Note:         Repeat above two steps to add multiple servers
      • Enter Remote Install Credentials (type the user name and password of the account that has administrative rights on all the Servers).
         
  6. Check the box for 'Remote Agent for Windows Systems' and/or 'Advanced Open File Option'.

    Note    :
    1. Installation of an Advanced Open File Option may require a reboot to finish the installation.
    2. The destination location for Remote Agent install files can be changed if required.
    3. AOFO installation is not applicable for Windows Server 2008, Windows Vista or Windows 7.

       
  1. On the Remote Agent publishing screen:
    1. Check the box which says 'Enable remote agent to publish the IP address and name of the remote computer and the version of the Remote Agent to media server'
    2. Click Add and enter the Media Server name or IP address (or both) and press OK.
    3. Click Next.
       
  1. Click Next when the screen shows Ready to install the Remote Agent for Windows Systemsbeside the server name(s)
     
  2. Click Install to begin the installation.
     
  3. Wait for the installation to complete and click Finish

IMPORTANT:
For Backup Exec 2010 R3, a SSL trust will need to be established after a manual install of Remote Agent. This can be done by following instructions on the below technote:How To Enable and Troubleshoot SSL Certificates in Backup Exec 2010 R3 - www.symantec.com/docs/TECH158716



2. Local (manual) installation of RAWS:


When automated (push) installation of the RAWS fails it may be necessary to perform a local installation.

A local (manual) installation of the Remote Agent for Windows Systems (RAWS) and Advanced Open File Option (AOFO) can be performed by following the steps below:
  1. Copy the RAWS32 or RAWSX64 and MSXML (for Backup Exec 2010 / 2010 R2 / 2010 R3) folder(s) from the Media Server to the remote computers local drive.
    Note:
    1. The default path for the above mentioned folders is 'X:\Program Files\Symantec\Backup Exec\Agents' ('X' is the drive letter where Backup Exec is installed)
    2. For Remote Agent installation on:
      • 32-bit system: Copy the RAWS32 folder.
      • 64-bit system: Copy the RAWSX64 folder.
         
  2. Go to the remote computer and open the RAWS32 or RAWSX64 directory which is copied on the remote server.
     
  3. Double-click on Setup.exe file.
    Note: 
    1. Turn off User Access Control (UAC) for Windows 2008, Vista or 7.
    2. It is recommended to right-click on Setup.exe file and select 'Run as Administrator' to avoid any access issues during the installation process.
       
  4. Click Next on the Welcome screen.
     
  5. Select Local Install and click Next.
     
  6. Check the box for 'Remote Agent for Windows Systems' and/or 'Advanced Open File Option





    Note:
    1. Installation of an Advanced Open File Option may require a reboot to finish the installation. 
    2. AOFO installation is not applicable for Windows Server 2008, Windows Vista or Windows 7.
    3. The destination location for Remote Agent install files can be changed if required by clicking on the 'Change' button.
       
  7. On the Remote Agent publishing screen:
    1. Check the box which says 'Enable remote agent to publish the IP address and name of the remote computer and the version of the Remote Agent to media server'
    2. Click Add and Enter the Media Server name or IP address (or both) and press OK.
    3. Click Next.
       
       
  1. Click Install to begin the installation.
     
  2. Wait for the Installation to complete and Click Finish. 
IMPORTANT:
For Backup Exec 2010 R3, a SSL trust will need to be established after a manual install of Remote Agent. This can be done by following instructions on the below technote:How To Enable and Troubleshoot SSL Certificates in Backup Exec 2010 R3 - www.symantec.com/docs/TECH158716





3. Silent (command line) installation of RAWS:

To perform a command line install of the RAWS or AOFO on a remote Windows server, follow the instructions given below:
Note: If Backup Exec 10.x (or prior) for Windows 2000/2003 version of the Open File Option (OFO) or the Remote Agent is installed on the remote server, uninstall the OFO and the Remote Agent through Control Panel - Add/Remove Programs, and then reboot the server to continue.
  1. Copy one of the following sub-folders from the Backup Exec media server's installation folder (by default located in C:\Program Files\Symantec\Backup Exec\) to the root of the C: drive on the remote server.
    • RAWS32: For a 32-bit (x86) Windows System.
    • RAWSX64: For a 64-bit Windows System.
    • RAWSIA64: For a 64-bit Windows System for Itanium Processors. (Does not apply to Backup Exec 12.5 and above)
       
  2. On the remote server, go to the command prompt (click Start - Run - cmd) :
    1. Browse to the RAWS folder which was copied on the local drive using DOS commands.
    2. In the command prompt window type setupaa.cmd (for 32-bit OS) or setupaax64.cmd(for 64-bit OS) and press enter to install RAWS only.
      OR
    3. Type setupaofo.cmd to install AOFO and RAWS together.
      Note:
      1. Installation of an Advanced Open File Option may required a reboot to finish the installation. 
      2. AOFO installation is not applicable for Windows Server 2008, Windows Vista or Windows 7.  
OR
  1. On the remote server, open the RAWS folder which was copied on the local drive:
    1. Double-click on setupaa.cmd (for 32-bit OS) or setupaax64.cmd (for 64-bit OS) to install RAWS only.
    2. Double-click on setupaofo.cmd to install AOFO and RAWS together.
      Note:
      1. AOFO installation is not applicable for Windows Server 2008, Windows Vista or Windows 7.
      2. On Windows Server 2008, Windows Vista or Windows 7, right-click on Setupaa.cmd and Run as administrator.
      3. Installation of an Advanced Open File option may require a reboot to finish the installation.
    3. The command prompt will appear blank between a few seconds and a couple of minutes while the remote agent installs.
    4. Once completed, the command prompt cursor will appear awaiting further input.
       
  2. To check if the RAWS was installed go to the Windows services console (Start - Run - Services.msc), and see if the Backup Exec Remote Agent for Windows Servers service is present and started.
     
  3. To check if AOFO is installed:
    1. Open Computer Management
    2. Click System Tools - System Information - Software Environment - Drivers.
    3. Select any driver listed in the right pane and press the "V" key on the keyboard.
    4. Look for the driver vsp.sys, which is the Volume Snapshot Provider Kernel Driver. This should be started.


IMPORTANT:
For Backup Exec 2010 R3, a SSL trust will need to be established after a manual install of Remote Agent. This can be done by following instructions on the below technote:How To Enable and Troubleshoot SSL Certificates in Backup Exec 2010 R3 - www.symantec.com/docs/TECH158716

Comments

Post a Comment

Popular posts from this blog

Veeam Guest Agent is not started

-
Backup Technology: - Veeam Issue: - Veeam job failed with below error message. ------------------- VMware Tools are not running. Guest processing skipped. Failed to prepare guest for hot backup. Error: Veeam Guest Agent is not started ------------------- Cause :- -        VM might be rebooted or down during backup job running. -        Veeam run time agent service stuck on VM server. -        VSS writers might be in failed status. Solution :- 1. Login to the effected VM and verity the uptime. If the VM is rebooted during backup job running then it will completed successfully in next retry attempt or next run. or 2. If you found any VSS writers are in failed status then reboot the server to resolve VSS writers issue. or 3. If Veeam run time agent service “VeeamVssSupport” stuck or not deleted after the veeam job completed then you need to delete the service manually or reboot the server.
Read more

VeeamVssSupport Service not found

-
Backup Technology:- VEEAM Issue: - Backup job failed with below error message. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Error: Cannot register management service. Service name: [VeeamVssSupport]. Cannot create service. Machine: [x.x.x.x]. The specified service has been marked for deletion. Code:1072 Cannot create service. Win32 error:The specified service has been marked for deletion. Code: 1072. Vvv Cause: - The VeeamVssSupport service cannot be installed because it was never uninstalled. It was marked for deletion instead of being deleted. It cannot be removed, but will be removed automatically when the guest OS reboots. Typically this is due to one of the following programs being open at the time the deletion command w
Read more

Veem job Failed to prepare guest for freeze, wait timeout 900 sec

-
Backup Technology: Veeam Sometimes Veeam backup jobs failed on VM with below error message continuously. Failed to prepare guest for host backup. Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec We need to follow the below steps to resolve the issue. Cause: This issue typically involves a very active transactional application running in the virtual machine, and it is taking longer than expected per the default timeout to freeze the I/O for this application/VM Solution You can change this timeout by modifying the value in the registry of the server where Veeam Backup & Replication is installed as follows: 1.        Go to Veeam registry path HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication. 2.        Add a DWORD (32-bit) value named VssPreparationTimeout. The value is in milliseconds (decimal), the default timeout is 900000, which equa
Read more