Backup Exec 12.5 Error Code E000fe30
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT e000fe30 backup exec 2010 About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers e000fe30 backup exec 2014 Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas
Backupexec E000fe30
Veritas PartnerNet Error E000FE30 : A communication failure has occurred when attempting to backup or restore an ESX 3.5 server Article:000037650 Publish: Article URL:http://www.veritas.com/docs/000037650 Support / Article
E000fe30 A Communications Failure Has Occurred Backup Exec
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 Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Error E000FE30 e000fe30 backup exec 2015 : 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 communications. In addition, verify NDMP port 10000 for control communications during a backup / restore has also been made available for the service. esxcfg-firewall -Q If the ports are not specified proceed to the
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a
E000fe30 Backup Exec 15
Full Time Job Ways to Get Help Expand Search Submit Close Search Login e000fe30 backup exec 2012 Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > backup exec 2014 a communications failure has occurred Backup Exec Error - e000fe30 - A communications failure has occurred. Want to Advertise Here? Solved Backup Exec Error - e000fe30 - A communications failure has occurred. Posted on 2008-01-24 Storage Software https://www.veritas.com/support/en_US/article.TECH68682 1 Verified Solution 13 Comments 25,879 Views Last Modified: 2013-12-01 For the last week my backups have been failing with error: e000fe30 - A communications failure has occurred. There is no other information besides that. I am just backing up a domain controller. Most of the solutions I found relate to Exchange but in my case I am not backing up Exchange. I have https://www.experts-exchange.com/questions/23108830/Backup-Exec-Error-e000fe30-A-communications-failure-has-occurred.html tested and re ran full backups, I have restarted the servers and made sure everything is up to date as well as making sure all the remote agents are running. 0 Question by:tmelton82 Facebook Twitter LinkedIn Google Best Solution byStratfrordDC My problem occurred after I upgraded to version 12. Symantec got me to re-install the agent locally. I had to copy the RAWS32 directory from the remote server to the agent server and then execute the Go to Solution 13 Comments LVL 3 Overall: Level 3 Message Expert Comment by:ssparks8272008-01-24 Make sure the VSS is enabled in services...in backup exec select use shadow copy or vss can't remember which one it is...I've seen this error on DC before... 0 Message Author Comment by:tmelton822008-01-24 It still failed with the same error. However it did provide me with more information this time. Here is what I got. Backup set #2 on storage media #15 Drive and media mount requested: 1/24/2008 2:13:48 PM Drive and media information from media mount: 1/24/2008 2:13:59 PM Drive Name: Server Name Media Label: B2D000075 Media GUID: {989b3809-3714-4d12-b0be-6
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 http://e000fe30-communications-failure.blogspot.com/ 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
and issue where your jobs are crashing with Error 0xe000fe30.I've personally spent hours resolving this issue, and the job logs only tell youE000FE30 - A communications failure has occurred.Here's how I fixed it:Error E000FE30 in Backup Exec - V-79-57344-65072 Posted by Free Online Backup at 6:55 AM No comments: Home Subscribe to: Posts (Atom) Followers Blog Archive ▼ 2010 (1) ▼ March (1) E000FE30 - A communications failure has occurred