waspsoft.com


Home > Backup Exec > Backup Exec Error Code E000fe30

Backup Exec Error Code E000fe30

Contents

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 Ran the following commands from the ESX server: - esxcfg-firewall --load - service iptables stop - service iptables start - VRTSralus stop and start - service iptables status Note: The ESX Join Now For immediate help use Live now! Thanks 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business have a peek here

Terms Of Service | Privacy Policy | Copyright Policy | Affiliates

Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Text Quote Post |Replace Attachment Add link Text to display: Where should this link go?

E000fe30 A Communications Failure Has Occurred

Any activity while the backup runs on the server .. Microsoft to end Windows 7 PC sales, Firefox tackles weak encryption Spiceworks Originals A daily dose of today's top tech news, in brief. © Copyright 2006-2016 Spiceworks Inc. The one you pick depends on weather your running 32 bit or 64 bit software.

  1. Go to Solution.
  2. 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
  3. I also found this article that says Symantec is aware of the problem.
  4. This hotfix is not included in SP4.
  5. The daily and monthly backups do use the same selection list as the weekly backup. 0 Kudos Reply on the event viewer this is Devan10 Level 3 ‎01-30-2012 09:26 AM Options

Now locate your Backup Exec Install Media, locate the Remote agent for Windows folder (usually in winntinstall). This should be the first step. 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 Backup Exec Error 80004005 I have Backup Exec 2010 R3 on a Windows Storage Server 2007 64 bits Service Pack 2 The server i'm trying to backup Data is a Windows Server 2003 R2 Standard

Make sure that no other application has a lock on the cache files created by the snapshot operation. 0 LVL 3 Overall: Level 3 Message Expert Comment by:ssparks8272008-01-28 Do Backup Exec Error Code E000846b Check the network, and then run the job again. 0 Message Expert Comment by:StratfrordDC2008-03-16 I am having the same problem with version 12.0 on a 2003 Server. Backup- servername V-79-57344-34110 - AOFO: Initialization failure on: "C:". No Yes Did this article save you the trouble of contacting technical support?

Connect with top rated Experts 9 Experts available now in Live! Backup Exec 80004005 You may also refer to the English Version of this knowledge base article for up-to-date information. 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 Go to Solution.

Backup Exec Error Code E000846b

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 Snap! E000fe30 A Communications Failure Has Occurred There is no other information besides that. Symantec Backup Exec E000fe30 Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may

Thank You! http://waspsoft.com/backup-exec/backup-exec-12-5-error-e000fe30.html Shouldn't that have included this hot fix? 0 Kudos Reply Would recommend you to VJware Level 6 Employee Accredited Certified ‎01-31-2012 10:30 AM Options Mark as New Bookmark Subscribe Subscribe to Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf - skipped. I have a Windows 2008 R2 server (64 bit) and it has a remote backup exec agent installed on it (the main backup exec program resides on another server). E000fe30 Backup Exec 2010

These are all the installed updates: Service Pack 4 Hotfix 355944 Hotfix 357378 Hotfix 355377 Hotfix 141389 Hotfix 142707 Hotfix 358478 Hotfix 153394 Hotfix 153395 Hotfix 160050 Hotfix 157584 Hotfix 169741 The error is the same one that tmelton is getting on his D: drive. I will do a shadow copy of the data to a different place see what it does. http://waspsoft.com/backup-exec/backup-exec-2010-error-code-e000fe30.html 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 Highlight

What else can I cover? Symantec Backup Exec E0008703 It says No for AOFO used but I have the box checked to choose the AOFO type automatically. 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

What should I try next?

My mistake. 0 Kudos Reply ...if there is an AV on that CraigV Moderator Partner Trusted Advisor Accredited ‎07-16-2013 11:54 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Image 1: Backup Exec log Image 2: Esxi 5.0 (destination server ) - network performace Image 3: Windows Event log (event id: 1000) Solved! You may get a better answer to your question by starting a new discussion. Backup Exec Error Code E0008821 VOX : Backup and Recovery : Backup Exec : Weekly Backup of Server keeps failing with error E...

Firstly make sure the Backup Exec Remote Agent service is running under the local system account. Join our community for more solutions or to ask questions. I have no idea why this is happening to the weekly backups, especially when the monthly backups are fine. this contact form Symantec got me to re-install the agent locally.

Reply Subscribe View Best Answer RELATED TOPICS: Symantec Backup Exec 2014 alternative? What I noticed so far is that error message is always coming on some specific files. Go to Solution Backup fail on same files with error E000FE30 M1ke Level 3 ‎09-15-2011 05:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to