• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4398
  • Last Modified:

BackupExec 10d, Unable to attach to a resource error causing failed backups

Hello.  I'm running BackupExec 10d on a server with an attached SQL server agent, Exchange server agent, and multiple file server agents installed on their respective machines.

Just recently, without any change, I'm starting to have failed jobs.  The repsonse is:

----
0xe000848c - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-33932
----

All the research I do isn't resulting in an answer.  Usually I use a seperate network for backups, but I changed the setting to any available network connection and I still get the same error.  It's almost like my agents license expired or something, but I don't think they expire.  Any help would be GREATLY appreciated, as of now, I'm not getting any backups!!!

Thanks!
Mike
0
mlamartina
Asked:
mlamartina
  • 5
  • 4
1 Solution
 
fpcitCommented:
I have run into this on occasion and a reboot of a given server or the BE server will resolve it.  If that doesn't get it can you let me know if the BE server or the remote server has any errors that are useful in the event viewer.

Also, your contract may expire that would prevent you from upgrading to a new version but your purchased licenses and agents won't expire.

Cheers
0
 
mlamartinaAuthor Commented:
I have rebooted all of the servers in our office and the issue remains.  I've also restarted the BackupExec services and still no luck.  Here are the errors I received:

----
Backup- EXCHANGE A network ID was not specified for the specified network interface.
Backup- \\EXCHANGE\Microsoft Information Store\First Storage Group A network ID was not specified for the specified network interface.
Unable to attach to \\EXCHANGE\Microsoft Exchange Public Folders.
V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.
A network ID was not specified for the specified network interface.
Backup- SERVER1The Media Server was unable to connect to Remote Machine SERVER1. The machine could not be found on the network.
The Media Server will fall back on the local agent to try and complete the operation.
Unable to attach to \\SERVER1\.
V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.
Make sure that the Remote Agent is installed on the target computer and is running.
The Media Server was unable to connect to Remote Machine SERVER1. The machine could not be found on the network.
The Media Server will fall back on the local agent to try and complete the operation.
Unable to attach to \\SERVER1\.
V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.
Make sure that the Remote Agent is installed on the target computer and is running.
The Media Server was unable to connect to Remote Machine SERVER1.
The Media Server will fall back on the local agent to try and complete the operation.
Unable to initialize Remote Agent
0
 
fpcitCommented:
From the BE server can you ping the exchange server?  That would show connectivity.    

Assuming you can do that try to redeploy the remote agent on to the exchange server

Create a new job and confirm that you can see the exchange server.  Assuming you can test the job.  

If it fails check the permissions on the account that you are using to access the servers.  has the password changed on the account recently?

http://seer.support.veritas.com/docs/266177.htm

0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
mlamartinaAuthor Commented:
I can ping and no the password hasn't changed.  I will redeploy the agents and setup a new job and test as you've suggested.  I will let you know how it goes.

Thank you for the help.
Mike
0
 
mlamartinaAuthor Commented:
Ok, I setup a new job to backup my entire system without backing up the Exchange server, which is where the problem seems to be primarily.  That works great - so the problem is definitely with the Exchange server or the agent.  I'm having trouble figuring out how to redeploy the Exchange agent, however.  Right now, my Exchange server isn't even showing up in the backup selections list as a server that's available to back up!  Argh!

Mike
0
 
mlamartinaAuthor Commented:
I've reinstalled the agent to my Exchange box and rebooted.  When I go into Backup Exec, I still don't see my mail server in the selections list!!!

0
 
fpcitCommented:
I saw something recently that was similar to this and it turned out the windows firewall has been inadvertently turned on, on the mail server.  

Can you post the beremote.log file or at least any parts that have errors in them?
0
 
mlamartinaAuthor Commented:
fpcit - thank you for keeping with me on this issue.  The firewall is completely off on the mail server.  Yesterday, I started to play around and this now the problem has morphed a little, but may shed some light on the situation.

I went to setup a new backup job, as you suggested, and noticed that my mail server was no longer in the backup selections list.  I reinstalled the Exchange agent on the Exchange box as you said and it still didn't show up.  Again, as suggested, I went into the mail server's service permissions and changed the Backup Exec agent from using the local administrator account to my domain's administrator account.  Wah-La!!!  I could see my mail server in the backup selections.  I reran my backup job that was giving me problems.  The whole thing completed!  HOWEVER...  (there's always a catch)...  I now have two other odd issues:

1) When I run a test run of the backup job that was giving problems, it runs for 5 seconds and comes back failed saying that the credentials for ALL of my servers are invalid.  They all have valid agents loaded on them, I can see them in the backup selections, AND the backup for these machines actually works...  Very odd...  But I'm not losing sleep over this error because 99% of the backup is working, even though the test fails.

2) My mailboxes are being backed up on the mail server now and all looks good.  However, now it will not back up my public folders and gives the error:
--
Unable to attach to \\MAILSERVER\Microsoft Exchange Public Folders.
V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.
--
I was playing with some public folder permissions the other day and cleaning things out.  I'm afraid that I deleted the wrong user permission in Exchange Manager and now it is causing this to fail?  I doubt that's the case though.  Also, I could not find a beremote.log file on my servers.

Thank you for your help, patience, and working me thru this problem!  I'm happy I got a relatively decent backup last night!
Mike
0
 
fpcitCommented:
It sounds like we have made good progress.  Well done.  As for 1 and 2 here is what I think.

1) I assume that is your original job that has now been replaced with your newly created job.  The fact that it is failing on the credintials is likely why you had problems originally.  You could potentially troubleshoot the job.  However, if it has been replaced with the new job and the new job is working correctly I wouldn't bother fixing the original.  In fact assuming the new job does everything you need I would suggest deleting the original unless there is a strong reason not to.

If you haven't replaced the job with a the new one, then we may want to troubleshoot the original and the first thing we look at are the credentials for each server set in the backup job itself.  We will dig into that if we need to.

2) The public folders error is fairly generic but it does suggest that the credentials you are using on the backup server don't have rights to the public folders.  You can check the backup job's resource credentials by looking at the properties of the job.  Once you know what you are using to attach to the public folder, confirm on the exchange side that the account has access to the public folders.  

If there are still issues, you can search for recently changed log files on the BE server.  You should find things like adamm.log in the c:\program files\symantec\BE\logs directory
0
 
sun_01usCommented:
Hi,

I am unable to restore mail contacts of one user to other user mailbox using exchange 2003, Backup exec 12.5. Below is the error.

Final error: 0xe000848c - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-33932
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now