Topic: Symantec/Veritas BackupExec Agent

[daniel]

I'm using BackupExec to backup windows and novell servers.  I want to use the linux/unix client that allows my backup server to reach across the LAN and backup the SME server.  I installed the linux agent on the SME server, loaded it up, and my backup server can see the  SME and backup and restore files to it over the LAN.  Works awesome. 

I can reboot the SME server and still everything works great untill I do a signal-event post-upgrade, then it stops working.   My test server is a server only mode so I don't think the firewall is the problem.  If I do a reinstall and restart the /etc/rc.d/init.d/agent.init start  then it will keep working till I do another server reconfigure.

Here is the agent.log file when everything is installed and working.
/etc/bkupexec/agent.be: Using configuration file: /etc/bkupexec/agent.cfg
/etc/bkupexec/agent.be: Agent configuration OK.
/etc/bkupexec/agent.be: Workstation Name: "LINUX"
/etc/bkupexec/agent.be: Backup Exec Agent ready to service requests.

After a reconfigure of the server the log file looks like this:
/etc/bkupexec/agent.be: Using configuration file: /etc/bkupexec/agent.cfg
/etc/bkupexec/agent.be: Agent configuration OK.
/etc/bkupexec/agent.be: Workstation Name: "LINUX"
**** getservbyname(grfs, tcp) failed! ****
**** using default port number(6101) for resource advertising ****
/etc/bkupexec/agent.be: Backup Exec Agent ready to service requests.

Does anyone have any suggestions on where I can look to find out what templates I need to customize for agent.be to work each time?  I'm at a loss so far.

[Stefano]

Hi

you could try something like

Code: [Select]

config set agent.be service status enabled TCPPort portnumber
cd /etc/rc7.d
ln -s /etc/rc.d/init.d/e-smith-service S99agent.ini
signal-event post-upgrade; signal-event reboot

I would also check with google if there's a init script for redhat/centos (i.e. something different than agent.ini)

HTH

[daniel]

Thank you for your response, however it did not change the problem.  I'm not sure I understand the purpose of the link file S99agent.init  (the file is init not ini, I assumed that was a typo on your response)  I did however do a better google and found the solution.   

In the /etc/services file the installer adds a line
grfs      6101/tcp   # Backup Exec Agent

I created a custom template to add this to the end of the services file and now the signal-event post-upgrade doesn't break the agent. I'm able to backup the SME test server over the LAN with backup exec. 

Thanks for pointing me in the right direction.  My next step is to determine the best procedure for restoring and creating the SME from a total failure with a bkupexec agent backup.

[Stefano]

Thank you for your response, however it did not change the problem.  I'm not sure I understand the purpose of the link file S99agent.init  (the file is init not ini, I assumed that was a typo on your response)

yes, a typo

I did however do a better google and found the solution.   

excellent

In the /etc/services file the installer adds a line
grfs      6101/tcp   # Backup Exec Agent

I created a custom template to add this to the end of the services file and now the signal-event post-upgrade doesn't break the agent. I'm able to backup the SME test server over the LAN with backup exec. 

Thanks for pointing me in the right direction.  My next step is to determine the best procedure for restoring and creating the SME from a total failure with a bkupexec agent backup.

well, when you finish, could you create an how-to in the wiki? thank you

[daniel]

I'm not actually familiar with the proper way to do How-tos in the Wiki.  Here is the How To I followed.

For Symantec/Veritas Backupexec 10 for windows or 9.1-9.2 for Novell to backup SME 7.4 as a remote server.
In server-manager add a group called beoper
Copy be_agent.tar to a folder on the SME server.  I use /root/bkupexec
tar -xvf be_agent.tar
./INSTALL to run the installer
Select Linux 2.4 as the server to install.
Follow through the prompts based on the backup environment you are using
create a custom template
/etc/e-smith/templates-custom/etc/services/99bkupexec
In the 99bkupexec file add this line: grfs      6101/tcp   # Backup Exec Agent

To manually start be_agent at the command prompt type: /etc/rc.d/init.d/agent.init start

If you wish to have this started automatically add the startup line to the file /etc/rc.d/rc.local

Once this is finished you can go to your backup media server and search for the SME server, then create the backup file selection for the backup routine. 

I'm also doing testing on backup exec 2010 and V12 for Windows SErvers.  The backup agent RALUS that comes with this version works correctly during install if the compat-libstdc++-33.i386 from the base repository is installed prior to starting the installralus command.

[Stefano]

tar -xvf be_agent.tar
./INSTALL to run the installer
Select Linux 2.4 as the server to install.

I hope that 2.4 is not referring to kernel version, as we are using 2.6.X