0xe000fe30 - A Communications Failure Has Occurred.
It can telnet on port 10000 to the BE server and vice-versa. If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity ProCurve ACL 5 58 2016-09-19 Best method for creating a Recovery Windows I then ran live update from the main console to apply 3 or 4 patches. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : e000fe30 - A communications failure has occurred Subscribe to RSS Feed Mark Topic http://itivityglobal.com/backup-exec/backup-exec-2012-service-failed-to-start-15-service-logon-failure.html
One question; let me verify the ports we have open as the NAS and BE server are on one subnet and the fax server I'm trying to back up are on I also found this article that says Symantec is aware of the problem. Hi, I suspect your issue CraigV Moderator Partner Trusted Advisor Accredited 05-23-2012 07:37 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Hi, I suspect your issue CraigV Moderator Partner Trusted Advisor Accredited 05-23-2012 07:37 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend
0xe000fe30 - A Communications Failure Has Occurred.
Backup- \\servername\C: Unable to open the item \\servername\C:\Documents and Settings\Administrator\NTUSER.DAT - skipped. View this "Best Answer" in the replies below » 11 Replies Pimiento OP Matagorda County Feb 20, 2015 at 7:35 UTC I had this same problem in 2010R3 For additional information regarding this error refer to link V-79-57344-65072 My configuration is as follows: Microsoft Small Business Server 2003r2 w/ 4GBRam Symantec BackupExec for Windows 12 (Small Business Server License) Backup Exec would back the data up and show everything was ok.
Even with BE 2012 SP2 which is due to be released soon, BE 2012 can only back up Windows 2012. 0 Kudos Reply I'm sorry - I just checked - CWTokyo NOTE: If not logged on to Backup Exec server with the same user name as the Backup Exec logon account being edited, Backup Exec prompted to provide the account owner’s password I know it's set up only to scan files and NOT function as a firewall. Backup Exec 2014 A Communications Failure Has Occurred Veritas does not guarantee the accuracy regarding the completeness of the translation.
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. A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent 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 Technologies LLC. Backup set canceled. 0 LVL 3 Overall: Level 3 Message Expert Comment by:ssparks827 ID: 207396022008-01-24 What is being backed up on the DC? https://www.veritas.com/support/en_US/article.TECH28737 CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical
You can also try uninstalling the RAWS agent, and then reinstalling it. V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. Thanks! 0 Kudos Reply Check everything that Craig Jaydeep_S Level 6 Employee Accredited Certified 07-17-2013 12:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to 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. Unable to open the item \\servername\C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db - skipped.
A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent
Final error category: Resource Errors The error occurs during backups of remote computers. https://www.veritas.com/support/en_US/article.TECH68682 Thanks! 0xe000fe30 - A Communications Failure Has Occurred. I would test with two different jobs, one for data and see if it finishes without failures and one with just the shadow components...the other way to test would be use E000fe30 Backup Exec 2010 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!
Most of the solutions I found relate to Exchange but in my case I am not backing up Exchange. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? An event is listed in the application event log Source:BackupExec Category:None Event ID:34113 Labels: 12.x and Earlier Backup and Recovery Backup Exec Configuring 0 Kudos Reply 4 Replies Having the same Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Final Error: 0xe000fe30 - A Communications Failure Has Occurred.
Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Job fails each time - Error e000fe30 - A communica... It is possible that updates have been made to the original version after this document was translated and published. Join the community of 500,000 technology professionals and ask your questions. Veritas does not guarantee the accuracy regarding the completeness of the translation.
The job history indicates that it has backed up my C &Ddrives. V-79-57344-3877 Backup Exec 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 Here is what I got.
I was able to find a short-term solution to maintain backups, and a long-term solution for the benefit of the organization.
Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped. Check the link below: http://www.symantec.com/business/support/index?page=content&id=TECH137682 You can try restoring the VM to a local disk, and then copying to the virtual centre is this is possible. Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config.cch.2172.13372828 - skipped. V-79-57344-65301 - The System State Resource Is Not Responding. Backup Set Canceled We have a nearly identical duplicate of this server for development and it backs up just fine.
There is no other information besides that. Advanced Open File Option used: No. 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 but I get it for everything that is backing up on that server.
Open 50 ports (i.e. Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\enterprisesec.config.cch.2172.13372828 - skipped. The server running the BE agent can open and write to the NAS's file share. I have 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
Change the port range inside Backup Exec: a. Open Backup Exec b. Click Tools | Options c. In the left pane, click Network and Security d. For Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file. Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0770157C.xml - skipped.