Hi, Welcome!
IT & Telecomunications Knowledgebase




 
Subscribe to Article Print Article Email Article to Friend Export to PDF

Mass changing the destination BackupExec Remote Agent server via deployment script



Summary


This article will assist a technician with creating a mass deployment script to modify the BackExec remote agent media server destination.

Details


Symantec BackupExeec 12.x


Description

This article will assist a technician with creating a mass deployment script to modify the BackExec remote agent media server destination.

Media servers are [typically] stand-alone, non-VM based machines with SCSi cards to connected robotic libraries or slower non-production disk storage devices. The primary reason for these machines to exist as a physical machine (as opposed to virtual, residing on a SAN) is due to the extraordinarily high I/O processes and bandwidth involved with backing up data. All of this data would absolutely grind a SAN/VM cluster to a screeching halt if it were all handled internally across a typical SAN controller.

Keeping in mind that setup, physical machines need to be upgraded and other (non-upgraded associated) network changes may require IP addresses and subnets to change. Where BackupExec severely limits centralized management is the ability to manage/maintain the destination media server IP/hostname. As it stands, this information is set during the inital BackupExec remote agent install and can be changed manually from the server's GUI console; Not exactly a fun task if you have a few hundred servers to change.

Prerequsites

  • User account running the script must have administrative rights/access to remotely connect to the remote machine's registry and WMI.

Solution

I worked with BackupExec support and found them to be a typical support company, only recommending "company-approved" solutions, which (in my case) would have involved visiting each server, making changes, saving and restarting services - a slow, lengthy process which didn't scale. I did some investigation on how the BackupExec remote agent works, and found a very easy work around which took an average 4:15 manual change time down to :06 per server. Create a file called AGENTUPDATE.BAT

echo off
echo *** Updating %1's BackupExec Remote Agent ***
reg.exe ADD "\\%1\HKLM\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Agents" /v "Agent Directory List" /t REG_MULTI_SZ /d newserver.domain.local
timeout /t 1 >null
echo *** Stopping %1's BackupExec Remote Agent ***
sc \\%1 STOP BackupExecAgentAccelerator
timeout /t 5 >null
echo *** Starting %1's BackupExec Remote Agent ***
sc \\%1 start BackupExecAgentAccelerator
echo *** Done ***

Usage
AGENTUPDATE.BAT machinename

Article properties


KB Article ID:00091
KB Article Permalink:http://kb.sleepyshark.com/article.php?id=91
Category:Symantec
Published:Thu, Sep 15, 2016 at 3:32 PM
Updated:Thu, Sep 15, 2016 at 3:33 PM
This article has been viewed 531 times.