Backup Exec agent on Mac OS Intel not starting

[Jeff_Nelson_2]

We are having a problem with the install of the Backup Exec agent for Mac on Macs with Intel processors. While not completely confident it is related to the Intel processor and or the version of the Mac OS they run, the Backup Exec agent service (agent.be) is not running automatically when a user logs in and needs to be started manually by an local administrator.

Where can be check/fix who the agent starts on this Mac? And/or how do we completely uninstall the agent for a reinstall?

This is running Mac OS 10.4.7 for Intel processors and the Backup Exec 10d server is running under Windows 2003 server.

[Deepali_Badave]

Hello,

What error mesasge you are getting in the event logs?

Regards,

[Jeff_Nelson_2]

There are no error messages in the console logs on the Mac OS Intel client as the agent.be process seems not to be running. The process only runs when started manually through the command line and will only backup if then the server executes a job within a few minutes, otherwise the client side processes seem to become unresponsive.

On the server the event logs the only error in the Application log during the relevant time frame is this:

Event Type:Error
Event Source:Application Error
Event Category:(100)
Event ID:1000
Date:9/26/2006
Time:9:33:18 AM
User:N/A
Computer:BKUPSRV
Description:
Faulting application bengine.exe, version 10.1.5629.23, faulting module bengine.exe, version 10.1.5629.23, fault address 0x000a9bdf.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 62 65 6e ure ben
0018: 67 69 6e 65 2e 65 78 65 gine.exe
0020: 20 31 30 2e 31 2e 35 36 10.1.56
0028: 32 39 2e 32 33 20 69 6e 29.23 in
0030: 20 62 65 6e 67 69 6e 65 bengine
0038: 2e 65 78 65 20 31 30 2e .exe 10.
0040: 31 2e 35 36 32 39 2e 32 1.5629.2
0048: 33 20 61 74 20 6f 66 66 3 at off
0050: 73 65 74 20 30 30 30 61 set 000a
0058: 39 62 64 66 9bdf

[shweta_rege]

Hello,


Try to repair the Backup Exec :-

Repairing VERITAS Backup Exec (tm) 9.x for Windows Servers

http://support.veritas.com/docs/253199




Thank You,

Shweta

[Jeff_Nelson_2]

This has no effect. The problem is client side. The 'agent.be' process does not run properly on an Mac OS Intel client. We have plenty of other Mac OS PowerPC clients that work just fine as well as the server providing many other Backup Exec roles.

The 'agent.be' process simply is not launched upon login or system startup on an Intel Mac, it has to be started from the command line by an administrator and then the backup will run. However, if you also leave the 'agent.be' process idle for a period before starting the backup, it will generate a communications error on the server as the process seems to sleep and not recover if not used soon after started.

[Deepali_Badave]

Hello,

As the agent.be is not running on the MAC os, this problem is occured after installing any patches on it?

Regards,

[Jeff_Nelson_2]

The Intel Mac OS computer is running the latest version of the Mac OS and it was a fresh install of the Backup Exec Mac agent.

I can try reinstalling the Backup Exec Mac agent, however what is the correct procedure to uninstall the Backup Exec Mac agent?

[tejashree_Bhate]

Hello,

To uninstall the Mac agent you need to just drag and drop the Backup Exec directory to the trash folder

Reboot the server

Thanks

[Michael_Wineke]

Hi Jeff,
I did get this to work on my MacBook Pro. Initially, it was difficulty with the firewall on the server, then it was a matter of setting up the agent.cfg properly via deletion and reinstall of the agent and adding a host entry to the /etc/hosts file. I've now tested the agent on a G4 laptop running 10.4.7 and the MacBook Pro running 10.4.8.
Both work fine so far.

The documentation for the agent install says you need to enable and be root, but I installed on both machines under an admin account using sudo.

Now I'm investigating adding exclusions to the agent.cfg, but I keep getting out of memory messages when relaunching the agent.be. Not sure what's going on there, but it sure would be handy if agent.be could accept wild cards (*) in paths.
Because, if we add a user to a workstation, it would be nice to not backup (or have to specify a directory entry for each user account.
example: exclude_dir */Library/Caches
...or whatever similar folders in subdirectories of the published directory.

I'll try to remember to open a new thread, or support ticket on that... :p

[Jeff_Nelson_2]

Michael:

Thanks for your reply, installing using 'sudo' instead of a root account (as the Backup Exec instructions describe) does work.