?
Solved

Exchange 2007 and BackupExec 12.5

Posted on 2011-03-12
7
Medium Priority
?
865 Views
Last Modified: 2012-05-11
I am betting the following erro backing up exchange 2007 on win2k8 after pushing the remote agent from the Backup Server remotely to the echange server.  I tried unistalling and reinstalling net 3.5 but no luck. Any ideas?

Job ended: Friday, March 11, 2011 at 11:29:31 PM
Completed status: Failed
Final error: 0xe0000f04 - The media server could not connect to the remote computer. The remote computer may not be running the Backup Exec
Remote Agent for Windows/Linux. Make sure that the correct version of the Remote Agent is installed and running on the target computer.
Final error category: Resource Errors

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

0
Comment
Question by:cheto06
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 4

Expert Comment

by:Scovndrel
ID: 35117080
Is Windows Firewall enabled on the 2008 server? if so, have you created a port exception for the Remote Agent? I'd start with disabling the firewall temporarily. If that fixes it, you'll need to find the port number and make an exception.
0
 

Author Comment

by:cheto06
ID: 35132658
Estrange now I am getting a different error:

(Server: "SBAKHQ01-P") (Job: "Exchange/Bberry Backups-Windows Backup-Full Monthly Backups") Exchange/Bberry Backups-Windows Backup-Full Monthly Backups -- The job failed with the following error: The directory or file was not found, or could not be accessed.

0
 
LVL 4

Expert Comment

by:Scovndrel
ID: 35132888
That's a pretty normal error. It means that when the backup job started, it listed out all of the files/folders it was going to back up. But by the time it got to that file/folder, the file/folder had been deleted.

This happens all of the time with log file folders, which generally don't need to be backed up.

This also means that your backup server is now communicating with your remote agent just fine, assuming that the folder in question is on the remote server. Did you make any changes?

0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:cheto06
ID: 35133417
I haven't made any changes to the selection list. See list attached.

SelectionJob.bmp
0
 
LVL 4

Accepted Solution

by:
Scovndrel earned 2000 total points
ID: 35133460
Did you make any changes to the firewall config or anything else that might have allowed the agent to start communicating?

I think your original question is resolved. Since you are getting an error about a folder being missing, that indicates agent communication is OK. Now you just have to decide whether to exclude that folder that is going missing, or what.

That's a different issue.
0
 

Author Comment

by:cheto06
ID: 35133616
I guess you are right.  Althoug I heven't been able to get a good back up yet.  I don't get the original error. Which I believe went away when I rebooted the back up exec server.
0
 
LVL 4

Expert Comment

by:Scovndrel
ID: 35133662
Thanks for the points.

One important thing to remember about Backup Exec is that if one little thing in the "critical" category goes wrong, it marks the whole job as "Failed" - but that is not necessarily true. I don't have the entire log file so  I can't say for sure, but it sounds to me as if that backup was perfectly fine except that one file/folder was missing when the backup software got there to back it up. That file/folder was most likely deleted as a normal function of whatever software is was part of.

The job got marked as "Failed", but you'd be able to do a perfectly good full restore from it because that file/folder was superfluous. There is a good chance that without you making any changes, the next backup will be successful because that scenario won't happen next time. Or maybe it will, but that still won't be anything to worry about - just an annoyance to clean up.

This happens all of the time. You will learn to determine what is an annoyance and what is important, and to exclude the "annoyances" from the backup so that the big red scary "Failed" bar does not appear in your logs.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
Suggested Courses
Course of the Month13 days, 15 hours left to enroll

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question