E000fe30 Backup Exec Error
Contents |
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
Backup Exec E000fe30 Communications
on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible backup exec error code e000fe30 matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec
Backup Exec 15 Error Code E000fe30
: Job fails each time - Error e000fe30 - A communica... VOX : Backup and Recovery : Backup Exec : Job fails each time - Error e000fe30 - A communica... Subscribe to RSS Feed Mark e000fe30 backup exec 2012 Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Job fails each time - Error e000fe30 - A communications failure has occurred CWTokyo Level 4 07-16-2013 11:00 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I get the following link when I try to run symantec backup exec e0008703 a backup job that has never run successfully: V-79-57344-65072. I have an agent running on one server running WS 2008 r2, and the BE server is running Windows 2012. The storage unit is a NAS. The BE server is also a file server and it runs like clockwork to the same NAS with no failures. However, the agent running on another server (it's a fax server) has never successfully backed up even a single bit of data; it errors out each time. I've ensured that the agent has local admin access to both the BE server and the local server where it's running, and the NAS allows the same user read/write access (it's actually open to anyone). The server running the BE agent can open and write to the NAS's file share. It can telnet on port 10000 to the BE server and vice-versa. What else can I cover? I tried disabling IPv6 but it still fails each time. Solved! Go to Solution. Labels: Agents Backing Up Backup and Recovery Backup Exec Configuring Error messages Managing Backup Devices Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Here is the list of all the Jaydeep_S Level 6 Employee Accredited Certified 07-22-2013 01:43 AM Optio
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
Backup Exec Error E0008821
CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest backup exec error 1603 helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search
Backup Exec Error 1068
instead for Do you mean VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... VOX : Backup and Recovery : Backup Exec : https://vox.veritas.com/t5/Backup-Exec/Job-fails-each-time-Error-e000fe30-A-communications-failure-has/td-p/621978 E000FE30 - A communications failure has occurred i... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution E000FE30 - A communications failure has occurred in Backup Exec Error adam3344 Level 2 05-23-2012 05:47 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed https://vox.veritas.com/t5/Backup-Exec/E000FE30-A-communications-failure-has-occurred-in-Backup-Exec/td-p/479571 Highlight Print Email to a Friend Report Inappropriate Content Hi! I'm trying to restore VM form Tape, backed up with Backup Exec 2010 13.0. Full backup restores without any problem, there is problem when trying restore from Incremental backup Restore Job properties: I'm using VMware redirection to ESXi 5.0 server. Everything seems to work well at the begining, but after few minutes Byte Count stops, and Job rate successively goes down, Tape Autoloader starts with daily (with incrementals) tape loading after long time restore job are crashing with "0xe000fe30 - A communications failure has occurred" Backups are encrypted Problem is observed by me on 2 separate installations of Symantec Backup Exec, Tape drivers from symantec are installed, VMware Converter are installed on that server also. Im not using Backup Exec Granular Recovery Technology (GRT) Device Name Created On Job Type Job Status Percent Complete Start Time End Time Elapsed Time Byte Count Job Rate Error Code HP 1 Central Administration Server Restore Failed 5/21/2012 2:47:25 PM 5/22/2012 12:56:41 AM 10:09:16 808,193,348 1.00 MB/min E000FE30 Is t
server and an old shared SAS array. We need more storage, more speed and new hardware that we're not worried is going to fail at any https://community.spiceworks.com/topic/803129-symantec-backup-exec-2014-error-e000fe30-a-communications-failure-has-occurred minute. CED Moving CED Moving in the offices of Milan and Bologna System ECM http://www.petenetlive.com/KB/Article/0000382 - Repozytorium dokumentów System ECM - Repozytorium dokumentów TECHNOLOGY IN THIS DISCUSSION Symantec 258512 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 communicating with the backup exec backup exec agents, but I can't seem to figure this out. I've disabled A/V, the agent 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 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 error Backup exec 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 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!)
Fails With an E000FE30 Error Home » Backup Exec » Backup Exec Job Fails With an E000FE30 Error KB 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 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 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