Error Code E000fe30
Contents |
Followers Follow Symantec Backup Exec Join the Community! Creating your account only takes a few minutes. Join Now Anybody ever come across this error in Symantec Backup Exec? It looks like it's having a problem
E000fe30 Communications Failure
communicating with the backup exec agents, but I can't seem to figure this out. I've backup exec error code e000fe30 disabled A/V, the agent version numbers are the same. I am able to back up the server that the Backup exec is on,
Symantec Backup Error E000fe30
I'm even able to back up data to a different server share, but I can't backup a server that has an agent installed. Reply Subscribe View Best Answer RELATED TOPICS: Symantec Backup Exec 2014 alternative? Symantec Backup exec e000fe30 backup exec 2010 2014 I am running a one time backup on Symantec Backup Exec 2014...   11 Replies Pimiento OP Matagorda County Feb 20, 2015 at 7:35 UTC I had this same problem in 2010R3 and Symantec never could figure it out. They blamed my network and the servers the agents were on. Even when it did work we found out the hard way we couldnt restore any data from the backups. Backup Exec would e000fe30 a communications failure has occurred backup exec back the data up and show everything was ok. You could see the files on the backup to disc volume, but Back Exec couldnt during the restore. We ended up having to abandon Backup Exec and go elsewhere. 0 Jalapeno OP Craig IT Feb 20, 2015 at 7:37 UTC well that turns my stomach... 0 Poblano OP Neelrad Feb 20, 2015 at 7:41 UTC This thread is scary to read, because this weekend I am upgrading from a UTL2 tape drive/Backup Exec 2010 R3 to UTL5 and Back-up Exec 2014! I am getting double-speak from Symantec's tech support about my license's structure if it includes the Agent for Applications & Databases or not. I got my license through TechSoup (non-profit here!) and TechSoup say one thing, but Symantec says another. I have a gut feeling that this will be a LONG weekend for me! 0 Jalapeno OP Craig IT Feb 20, 2015 at 7:55 UTC Mine is through tech soup as well. It's supposed to be a perpetual license. 0 Serrano OP Best Answer Elias_VTC (Veritas) Feb 20, 2015 at 8:12 UTC Brand Representative for Veritas Double check your firewall ports that you have opened on the server(s)While this is an older post, it is still relevant for the ports needed for Backup Exec:
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your
E000fe30 Backup Exec 2014
search results by suggesting possible matches as you type. Showing results for Search instead for Do e000fe30 backup exec 2015 you mean VOX : Backup and Recovery : Backup Exec : Weekly Backup of Server keeps failing with error E... VOX : Backup and
E000fe30 Backup Exec 15
Recovery : Backup Exec : Weekly Backup of Server keeps failing with error E... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Weekly Backup of https://community.spiceworks.com/topic/803129-symantec-backup-exec-2014-error-e000fe30-a-communications-failure-has-occurred Server keeps failing with error E000FE30 Devan10 Level 3 01-30-2012 07:26 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I'm having a bit of a problem with Backup Exec 12.5. I have a Windows 2008 R2 server (64 bit) and it has a remote backup exec agent installed on it (the main backup exec program resides on another server). The 2008 server is set to do daily backups, https://vox.veritas.com/t5/Backup-Exec/Weekly-Backup-of-Server-keeps-failing-with-error-E000FE30/td-p/489498 weekly backups and monthly backups. The daily backups are differential, and both the weekly and monthly backups are full backups. The 2008 server has been in place for a few months now, the first couple months the server had some files but not alot (approx 100 GB of files and data), all the backups worked fine then, but around the end of December I moved all of our files from an older server to this new 2008 server, now there is about 2.5TB of files and data on this server. The problem is ever since I moved all of the file to this server the weekly backups have been failing with error code E000FE30 "A communications failure has occurred.". The daily backups and the monthly backups have worked without any problems. I would have though this might have somethinbg to do with the full backup, but the monthly and weekly backups are backing up the exact same files. I have no idea why this is happening to the weekly backups, especially when the monthly backups are fine. Please help. Thanks. Edit: The windows 2008 server in question is hosted on VMware ESXi 4.1.0, but before I moved all the files and data the server was on a physical machine. Also I can do a test run of the weekly backup and it will be successful. Labels: 12.x and Earlier Backing Up Backup and Recovery Backup Exec E
Fails With an E000FE30 Error Home » Backup Exec » Backup Exec Job Fails With an E000FE30 Error KB http://www.petenetlive.com/KB/Article/0000382 ID 0000382 Dtd 25/01/11 Problem A common error on Backup Exec version 12, essentially the media server is losing communication to the Backup Exec remote agent http://backupexec-hell.blogspot.com/2009/09/error-e000fe30-every-day-on-one-server.html Note: Even if you only have one server it will still be running a remote agent! Errors: Final error: 0xe000fe30 - A communication failure has occurred Final backup exec error category: Server Errors V-79-57344-65072 - The Exchange Store service is not responding. Backup set canceled. V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine {server name} Remote Agent not detected on {server name} Note: You may also see error E0000F04 Solution 1. Firstly make sure the e000fe30 backup exec Backup Exec Remote Agent service is running under the local system account. Start > run > services.msc. 2. Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall). The one you pick depends on weather your running 32 bit or 64 bit software. Open the appropriate folder. 3. On a x32 bit server run double click the following two files, setupaa.cmd and setupaofo.cmd (noting will happen other than a command window will flash up). 3. On a x64 bit server run double click the following two files, setupaax64.cmd and setupaofox64.cmd (noting will happen other than a command window will flash up). 4. Finally on launch Backup Exec and click Tools > Live Update > follow the instructions, Note: you may be asked for a reboot when its finished. Related Articles, References, Credits, or External Links NA Author: Migrated Share This Post On GoogleFacebookTwitter Search for: Copyright PeteNetLive © 2016
eventually gave up with Backup Exec, so while this was "Backup Exec Hell - The Daily Torture of making Backup Exec 10d, 12d and 12.5 work..." it's now "The Joy of Microsoft DPM. Although it isn't perfect, it's a damn sight better. Wednesday, 30 September 2009 Error E000FE30 every day on one server... ...for months. For months I've struggled with a problem on ONE server, that happens to be at a remote site on a different subnet, connected via a WAN VPN Link.Every day, one or more jobs would fail with Backup Exec Errors, mainly E000FE30 - with the useful and generic messages about "communications failure has occured" and sometimes the "connection lost to the remote agent".Needless to say, I've spent some time working on this, and tried all sorts. Reconfiguring the system to use a different WAN link to ensure the fault isn't with the WAN. Nothing. Checking to ensure the issue isn't with the server, reinstalling agents, trying all sorts.I've updated network drivers, checked all sorts of patches etc - but nothing, Still this error - consistently failing jobs.I even got a colleague to look at it for a fresh pair of eyes and he too tried all sorts. Given the error, we suspected "something" to do with comms, but never found any issue, and in hundreds of tests conducted could never replicate the issue - transferring large files to/fro the server worked fine etc.Today I found the answer. The "Large TCP Offload" feature on the Network Card. While I've seen plenty of issues with this feature before, you normally see it with terrible throughput on the system in general and so on - but this machine is solid as a rock for everything else.Still, the setting is off, and first complete, full backups in a few weeks... voila!Top tip for anyone else facing this problem - don't just check the network drivers, but try turning off these features, even if you cannot see this issue at any other time on the machine.Is this a Backup Exec issue? I'm not sure, but I'm happy to blame it since everything else works just fine. Posted by The Backup Exec Goat at 11:00 Labels: backup, error messages, failed jobs 4 comments: Anonymous said... I have the same problem! I don't have the "Large TCP Offload" option, but I have a short list of other Offload options on both my built-in NIC and my SAN connection. Offload Receive IP ChecksumOffload Receive TCP ChecksumOffload TCP SegmentationOffload Transmi