Home > Backup Exec > Backup Exec 2010 Error Code E000fe30

Backup Exec 2010 Error Code E000fe30

Contents

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 I have the same problem! No Yes How can we make this article more helpful? They cautioned me repeatedly that it wasn't supported and I could lose my backup job definitions, etc. (Understood, it's an Alpha, Beta or whatever you want to call it, I just http://sovidi.com/backup-exec/backup-exec-2010-error-e000fe30.php

Backup set canceled. 0 LVL 3 Overall: Level 3 Message Expert Comment by:ssparks8272008-01-24 What is being backed up on the DC? Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... esxcfg-firewall -Q If the ports are not specified proceed to the resolution section   NOTE: Symantec recommends having NDMP port 10000 and a specific dynamic port range available on the Backup 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 2015

Reply Subscribe View Best Answer RELATED TOPICS: Symantec Backup Exec 2014 alternative? This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities

Thank You! The network connection failed during the snapshot. The USB drive must be s… Storage Software Windows Server 2008 Disaster Recovery Advertise Here 846 members asked questions and received personalized solutions in the past 7 days. 0xe000fe30 - A Communications Failure Has Occurred. Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview

Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). E000fe30 Backup Exec 15 We have a nearly identical duplicate of this server for development and it backs up just fine. Note: Example open port command would be: esxcfg-firewall -o 50000,tcp,in,RALUS 2. 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:

Thanks! The Connection To Target System Has Been Lost Backup Set Canceled Backup Exec Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf - skipped. Unable to open the item \\servername\C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped. The closest option had the same basic error message of V-79-57344-65072 - The connection to target system has been lost.

E000fe30 Backup Exec 15

Now need to expand second partition, then expand LVM PV inside that, then the VG then the PV 8 57 79d Connecting VMWare ESXi 6.0 Hosts to Windows Storage Server 2008 Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf - skipped. E000fe30 Backup Exec 2015 VOX : Backup and Recovery : Backup Exec : E000FE30 - A communications failure has occurred i... Backup Exec 2014 A Communications Failure Has Occurred 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.

Open the appropriate folder. 3. http://sovidi.com/backup-exec/backup-exec-e000fe30-error.php I don't have the "Large TCP Offload" option, but I have a short list of other Offload options on both my built-in NIC and my SAN connection. This particular client has been having backup troubles on an old server for a while, so we're working without a net here on the new one. If it repeats you will need to contact Symantec Support and see if you might need the updated bedsmbox.dll. E000fe30 Backup Exec 2012

V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\D:". 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 Windows 2012 Server, Fortimail Server Installing a new 2012 windows Server for HyperV and Fortimail email server. http://sovidi.com/backup-exec/backup-exec-error-code-e000fe30.php The "Large TCP Offload" feature on the Network Card.

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 A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Agent For Windows 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 Backup set canceled.

My previous home was wired with Cat5E in almost every room.

Posted by The Backup Exec Goat at 11:00 Labels: backup, error messages, failed jobs 4 comments: Anonymous said... No Yes Did this article save you the trouble of contacting technical support? It says No for AOFO used but I have the box checked to choose the AOFO type automatically. V-79-57344-65072 Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped.

When we bought that house, it had an unfinished basement and an unfinished attic room, making the cabling process very simple. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf - skipped. Backup set canceled. http://sovidi.com/backup-exec/backup-exec-12-5-error-code-e000fe30.php I haven't had any issues since. 0 Message Author Closing Comment by:tmelton822008-06-12 I had Symantec Tech Support basicaly had me to do the same thing. 0 LVL 57 Overall:

Check the network, and then run the job again. You might see one or more listed in the following state: Writer name: 'System Writer'    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}    Writer Instance Id: {b25db62a-f58e-4d9f-bf54-37f17f12742e}    State: [5] Waiting for completion