Symantec Backup Exec 2012 Error E000fe30
Nothing. but I get it for everything that is backing up on that server. Open the appropriate folder. 3. Creating your account only takes a few minutes. this contact form
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. 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 We 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 More from the Author Richard Clapp Systems Engineer LinkedIn Cleaning Up WinSXS Folder on Windows Server 2008 R2 Posted 07.16.14 Getting Access to Multiple Branches while Using a Split VPN Tunnel
E000fe30 Backup Exec 2010
Check the Windows Event Viewer for details. I did all those things and still no good, nothing but e000fe30 - A communications failure has occurred. Double-Urgh.
Error : e000fe30 - A communications failure has occurred. Advanced Open File Option used: No. Experiences, tips, problems, rants and ideas. E000fe30 Backup Exec 2012 System State and Shadow Copy Components g.
Get 1:1 Help Now Advertise Here Enjoyed your answer? Backup Exec 2014 A Communications Failure Has Occurred I know it's set up only to scan files and NOT function as a firewall. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdbdata.mdf - skipped. System Utilities Storage Software Storage Software-Other Storage Hardware Installing and Configuring Windows Server Backup Utility Video by: Rodney This tutorial will walk an individual through the steps necessary to install and
If it repeats you will need to contact Symantec Support and see if you might need the updated bedsmbox.dll. V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. I tried it anyway and was pointed to the Backup Exec Remote Agent for Windows Servers (RAWS) crashing. Exceptions Backup- \\servername\D: Data V-79-57344-34108 - An unexpected error occurred when cleaning up Symantec Volume Snapshot Provider (VSP) snapshots. I am just backing up a domain controller.
Backup Exec 2014 A Communications Failure Has Occurred
The backup job had crashed and the logs really left me without much - they only showed the following: V-79-57344-65072 - The connection to target system has been lost. V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\D:". E000fe30 Backup Exec 2010 But, it had a different problem description. E000fe30 Backup Exec 2015 Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall).
Labels: 2010 Agent for VMware Virtual Infrastructure Backup and Recovery Backup Exec Restore VMware VMworld Windows 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! weblink 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. Reply Subscribe RELATED TOPICS: Symantec backup exec, connectivity issue BE 2014 v-ray job failing after upgrade Can you run 2 schedule at the same time in Backup Exec? Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). 0xe000fe30 - A Communications Failure Has Occurred.
But did you ever see this?http://seer.entsupport.symantec.com/docs/290098.htmIt was posted before your blog about TCP Offload. 16 April 2010 at 08:09 PeteLong said... The closest option had the same basic error message of V-79-57344-65072 - The connection to target system has been lost. Here is the error for just the SQL instance. http://allconverter.net/backup-exec/symantec-backup-exec-error-code-e000fe30.html About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up
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. Final Error 0xe000fe30 A Communications Failure Has Occurred View my complete profile (C) VPW / All Rights Reserved |. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf - skipped.
You may get a better answer to your question by starting a new discussion.
What I DO know is that the AV client is NOT acting as a firewall and as previously mentioned, port 10000 is open. 2. 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? Here is the list of all the Jaydeep_S Level 6 Employee Accredited Certified 07-22-2013 01:43 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a A Communications Failure Has Occurred Backup Exec Check the network, and then run the job again. 0 Message Expert Comment by:StratfrordDC ID: 211385732008-03-16 I am having the same problem with version 12.0 on a 2003 Server.
Once you have verified that the services are stable again you can try and retest. Advanced Open File Option used: No. In most organizations, VMs contain many duplicate copies of data, such as VMs deployed from the same template, VMs with the same OS, or VMs that h… VMware Storage Software Virtualization his comment is here However it did provide me with more information this time.
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. Backup set canceled. For additional information regarding this error refer to link V-79-57344-65072 Resolution: This error can occur if the iptables firewall on the remote linux server is not allowing dynamic non-ephemeral ports open However, the odds are that they will hook you up with the hotfix for Bedsmbox.dll required to solve your headaches.
Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? The error is the same one that tmelton is getting on his D: drive.