Backup Exec 12.5 Error E000fe30
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer backup exec error code e000fe30 Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate
E000fe30 Backup Exec 2010
Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch
E000fe30 Backup Exec 2014
Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Error E000FE30 : A communication failure has occurred when attempting to backup or restore
E000fe30 A Communications Failure Has Occurred Backup Exec
an ESX 3.5 server Article:000037650 Publish: Article URL:http://www.veritas.com/docs/000037650 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print backupexec e000fe30 Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Error E000FE30 : A communication failure has occurred when attempting to backup or restore a ESX 3.5 server Error Message E000FE30 : A communication failure has occurred. Cause When attempting to run a backup or restore job to a Vmware ESX 3.5 server utilizing the Remote Agent for Linux and Unix Servers (RALUS) agent while the ESX firewall is enabled generates the error and no byte count occurs. Disabling the firewall, in troubleshooting this issue, allows successful backups and restores.This error is caused when the ESX server's firewall is not configured with correct port exceptions to be used by Backup Exec. Solution Use the following command to verify if fifty or more ports, for both inbound are specified for the dynamic port range use by the beremote service for DATA com
Symantec 258196 Followers Follow 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 communicating with the backup e000fe30 backup exec 2015 exec agents, but I can't seem to figure this out. I've disabled A/V, the agent e000fe30 backup exec 15 version numbers are the same. I am able to back up the server that the Backup exec is on, I'm even able to back backup exec 2014 a communications failure has occurred 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 2014 I am running a one time https://www.veritas.com/support/en_US/article.TECH68682 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 back the data up and show everything was ok. You could https://community.spiceworks.com/topic/803129-symantec-backup-exec-2014-error-e000fe30-a-communications-failure-has-occurred 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:http://www.symantec.com/business/support/index?page=content&id=TECH49563Hope that helps. 2 Poblano OP Neelrad Feb 20, 2015 at 8:29 UTC Thanks CraigIT! Here's to a successful instal
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 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