Backup Exec agent not responding

[Trilithon]

Originally Posted by lupobutcher

Trilithon,
Were you ever able to get this resolved? I am running into the same problem but with BUEexec version 10 and OS 10.4.6. The agent is running, I can select files from the selections dialog in BUExec, but I fail when I attempt to backup.

Any more insight would be greatly appreciated
Lupo

Hi Lupo,

I've managed to get things up and running again. In my case I solved it by replacing my accounts under "Network" -> "Logon Accounts" in BUExec with the exact same accounts. It seems that you just have to set them up again even if you use the same account credentials as before. In my case I also changed from the local admin account on my DC to the doamin admin account. According to the manuals this shouldn't be neccecary but I did it anyway and now it's working. Hope that this helps!

If you need more info I'd be glad to help.

Regards
T

[TobyG]

Sorry to resurrect an old thread... I would have resurrected a less-old thread here: Backup Exec and OS 10.4.4 Server but this one is already closed.

Anyway, I've been having this problem for some time now. For the life of me I can't get this thing to work. I'm still on 10d and just tried installing SP2 and that didn't help.

Basically it allows for me to select things to backup, but when the backup tries to run it fails. Mac is listening on 8192, BUT, Backup Exec is trying to talk on 10000. Ran a netmon and I can see it trying to talk to the mac on 10000. The mac client is still the legacy client and uses port 8192... why would backup exec use 10000?

I've tried the suggestions... changing login accounts, removing the password, adding passwords, everything... tried it on multiple macs... can't get this thing to work. I have yet to try a different media server, but the media server is working fine except for this problem.

Anyone else find a real definitive solution to this problem? Thanks!

[kevharris]

I am also having issues with Backup Exec. In my case I am running Backup Exec 11D and I have an Intel based Xserve with an Xserve RAID attached. The problem I am running into is, I can backup everything on the root directory of the internal drive of the Xserve but I cannot get the RAID to backup successfully. It keeps complaining that I need to enable ACLs and extended attributes on the RAID, and I have no idea was those are. I did turn on Access Control Lists in the Workgroup Manager but the backup still doesn't work.

Any ideas?

[TobyG]

My problem is weird. I can fix my problem, I just haven't done it yet.

I installed a fresh install of backup exec 10d on a different server and was able to successfully backup my Mac via the agent. I compared registry values between the two boxes, my old and the new fresh install and everything was almost the same, and I ended up changing the one or two values that were different to match. So all settings in the registry were the same. Still couldn't backup my Mac from my old server.

Then I used the beutility program to backup my database, then choose to "Recover Database" and choose "reload from base". This starts you off with a fresh database.

After that, I could now backup my Mac just fine. At the time I've reverted back to my database by this time choosing "Recover Database" and selecting "Reload from backup".

My Backup Exec server is an upgrade of a 8.x that was upgraded to 9.x and now 10d. Something must be whacked inside of the database.

The 'fix' for me is probably going to be to start over with a fresh database. I just haven't done that yet because I don't want to redo all of my jobs just yet. I would have never suspected the database would be the issue, but I guess it is. I did clear out all of my login accounts except for the main one, and that didn't help.

Repair and Rebuild Indicies on the old database both did not help.

I don't anticipate any of this will help you with your xserve problem, but if someone else has the same problems I've had in the past, perhaps they will find this post and can at least test to see if starting with a fresh database fixes their problem too.

EDIT:

I fixed the problem, without having to start with a fresh database. I had read the post from Trilithon but was only deleting and recreating the accounts I was trying to use to connect to the mac. Instead, this time I went through and recreated all of my logon accounts, even the ones I've had for years that I never even tried to use when connecting to the mac. I recreated them using the same accounts. This time now my Mac jobs work fine! That's really messed up. I wasn't even using those accounts to try and connect to the mac, but for some reason it didn't like something to do with them. Some sort of bug with Backup Exec, I'm guessing related to my upgrades of Backup Exec over the years.

[durwin]

I have same issue.

Windows 2003 running Backup Exec. Linux agent installed on Fedoracore 3 machine. Agent installed and runs with no errors. I can browse the linux tree for selecting to backup. But when it runs, it says

The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.

Agent is listening on port 10000 (ran beremote --log-console), is this same port Media machine is listening on?

This is a new install, no update, Version 11d.

Anything else I can check?

Here is the tail end from --log-console

4a1ebb0 Thu Feb 22 13:53:03 2007 : No Oracle SID's were discovered
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_FindDrives: Creating DLE: [ROOT]
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: entered -->\\ZAPHOD\users<--
4a1ebb0 Thu Feb 22 13:53:03 2007 : ******************************************************************************
4a1ebb0 Thu Feb 22 13:53:03 2007 : Initial DLE Tree
4a1ebb0 Thu Feb 22 13:53:03 2007 : -->[ROOT]<-- address 0x0000095658C8 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
4a1ebb0 Thu Feb 22 13:53:03 2007 : End of List
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_ResolveDevName: [\]
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: resolve returns -->\\ZAPHOD<-- as the machineName
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: and it's me!
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: but we couldn't be found
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_CreateTempDLE
4a1ebb0 Thu Feb 22 13:53:03 2007 : ====>VX_CreateTempDLE
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_CreateTempDLE: Creating DLE: \\ZAPHOD
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: trying to attach to ourselves
4a1ebb0 Thu Feb 22 13:53:03 2007 : ====>VX_AttachToDLE
4a1ebb0 Thu Feb 22 13:53:03 2007 : Resetting hard link info
4a1ebb0 Thu Feb 22 13:53:03 2007 : Hard link info has been reset
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_AttachToDLE: initializing mount list
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_AttachToDLE: create mount list returned 0
4a1ebb0 Thu Feb 22 13:53:03 2007 : BlowupChildren: Did not find DLE \\ZAPHOD\[ROOT] in list. Creating new.
4a1ebb0 Thu Feb 22 13:53:03 2007 : No Oracle SID's were discovered
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_SurrogateCalling: ZAPHOD
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_RemoveDLE: DestroyDLE()
4a1ebb0 Thu Feb 22 13:53:03 2007 : Attach to: \\ZAPHOD
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: attached to ourselves
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: didn't find -->\\ZAPHOD\users<--
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: detaching from ourselves
4a1ebb0 Thu Feb 22 13:53:03 2007 : Detach from: \\ZAPHOD
4a1ebb0 Thu Feb 22 13:53:03 2007 : Resetting hard link info
4a1ebb0 Thu Feb 22 13:53:03 2007 : Hard link info has been reset
4a1ebb0 Thu Feb 22 13:53:03 2007 : ******************************************************************************
4a1ebb0 Thu Feb 22 13:53:03 2007 : Modified DLE Tree
4a1ebb0 Thu Feb 22 13:53:03 2007 : -->[ROOT]<-- address 0x0000095658C8 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
4a1ebb0 Thu Feb 22 13:53:03 2007 : -->\\ZAPHOD<-- address 0x000009565C80 type 22 subtype 0 feature bits 0x03020603 0x00004002 dataId 49 bedsId 49 bedsVer 0
4a1ebb0 Thu Feb 22 13:53:03 2007 : -->\\ZAPHOD\[ROOT]<-- address 0x0000095900F8 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
4a1ebb0 Thu Feb 22 13:53:03 2007 : End of List
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_BlowOutMachine: returning 0
4a1ebb0 Thu Feb 22 13:53:03 2007 : FS_CreateTempDLE
4a1ebb0 Thu Feb 22 13:53:03 2007 : 1 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:03 2007 : 2 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:03 2007 : 3 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:03 2007 : 4 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:03 2007 : 11 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:03 2007 : RMAN_CreateTempDLE: Function called
4a1ebb0 Thu Feb 22 13:53:03 2007 : 14 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:03 2007 : ====>VX_CreateTempDLE
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_CreateTempDLE: Creating DLE: \\ZAPHOD
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_RemoveDLE: DestroyDLE()
4a1ebb0 Thu Feb 22 13:53:03 2007 : 22 = 0x00000000
4a1ebb0 Thu Feb 22 13:53:03 2007 : ====>VX_AttachToDLE
4a1ebb0 Thu Feb 22 13:53:03 2007 : Resetting hard link info
4a1ebb0 Thu Feb 22 13:53:03 2007 : Hard link info has been reset
4a1ebb0 Thu Feb 22 13:53:03 2007 : VX_AttachToDLE: initializing mount list
4a1ebb0 Thu Feb 22 13:53:04 2007 : VX_AttachToDLE: create mount list returned 0
4a1ebb0 Thu Feb 22 13:53:04 2007 : BlowupChildren: Did not find DLE \\ZAPHOD\[ROOT] in list. Creating new.
4a1ebb0 Thu Feb 22 13:53:04 2007 : No Oracle SID's were discovered
4a1ebb0 Thu Feb 22 13:53:04 2007 : VX_SurrogateCalling: ZAPHOD
4a1ebb0 Thu Feb 22 13:53:04 2007 : VX_RemoveDLE: DestroyDLE()
4a1ebb0 Thu Feb 22 13:53:04 2007 : Attach to: \\ZAPHOD
4a1ebb0 Thu Feb 22 13:53:04 2007 : FS_CreateTempDLE
4a1ebb0 Thu Feb 22 13:53:04 2007 : 1 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : 2 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : 3 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : 4 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : 11 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : RMAN_CreateTempDLE: Function called
4a1ebb0 Thu Feb 22 13:53:04 2007 : 14 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : ====>VX_CreateTempDLE
4a1ebb0 Thu Feb 22 13:53:04 2007 : 22 = 0xE000FE23
4a1ebb0 Thu Feb 22 13:53:04 2007 : 34 = 0x00000000
4a1ebb0 Thu Feb 22 13:53:04 2007 : ERROR: CreateBSD: Couldn't find \\ZAPHOD\users
4a1ebb0 Thu Feb 22 13:53:04 2007 : startBackup: CreateBSD() failed!
4a1ebb0 Thu Feb 22 13:53:04 2007 : Backup Job Stop(10) - Thu Feb 22 13:53:04 2007
4a1ebb0 Thu Feb 22 13:53:04 2007 : VX_RemoveDLE: DestroyDLE()
4a1ebb0 Thu Feb 22 13:53:04 2007 : VX_RemoveDLE: DestroyDLE()
4a1ebb0 Thu Feb 22 13:53:04 2007 : VX_RemoveDLE: DestroyDLE()
4a1ebb0 Thu Feb 22 13:53:04 2007 : @@@@@@@MyCloseSocket called with sockfd = 5(0x5) retval = 0
4a1ebb0 Thu Feb 22 13:53:04 2007 : @@@@@@@MyCloseSocket called with sockfd = -1(0xffffffff) retval = -1

Ragards,

Durwin

[vatmds]

I hate to resurrect such an old post, but I had this same problem recently and found this post while searching for a solution, only to be dismayed that there was none. After some digging I found a solution:

Even though I was able to browse the agent's file system real-time from the BE console, jobs failed every time. Running the agent in debug mode with -d revealed that the password stored in the agent.cfg file is not transmitted as-is - Veritas changes the case and may also strip out special characters (-, _, etc.). Setting a new password using all lowercase with no special characters and updating the "connect as" logon account within BE console allowed backups and restores to run properly. Hope this helps!
Vince