Home > Backup Exec > Symantec Backup Error E000fe30

Symantec Backup Error E000fe30

Contents

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? Perform the steps listed below: 1. Unable to open the item \\servername\C:\WINDOWS\system32\wins\winstmp.mdb - skipped. No Yes Did this article save you the trouble of contacting technical support? this contact form

Exceptions Backup- \\servername\D: Data V-79-57344-34108 - An unexpected error occurred when cleaning up Symantec Volume Snapshot Provider (VSP) snapshots. Ok so didn't found a solution M1ke Level 3 ‎10-04-2011 07:05 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content What should I try next? 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.

E000fe30 Backup Exec 2010

Login. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem When attempting to backup a remote file server running windows 2008 the following error occurs: 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 Ihave applied the DCOMFIG modifications to no avail.

Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0770157C.xml - skipped. Backup- \\server name\D: DataV-79-57344-65072 - The connection to target system has been lost. Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file. A Communications Failure Has Occurred Between The Backup Exec Job Engine And The Remote Agent Ok so didn't found a solution M1ke Level 3 ‎10-04-2011 07:05 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content

Check the network, and then run the job again. Backup Exec 2014 A Communications Failure Has Occurred Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP). Covered by US Patent. 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?

In addition, verify NDMP port 10000 for control communications during a backup / restore has also been made available for the service. E000fe30 Backup Exec 2012 So I'm a little baffled. 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 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

Backup Exec 2014 A Communications Failure Has Occurred

Thank You! Join & Ask a Question Need Help in Real-Time? E000fe30 Backup Exec 2010 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 E000fe30 Backup Exec 2014 You may also refer to the English Version of this knowledge base article for up-to-date information.

Veritas does not guarantee the accuracy regarding the completeness of the translation. http://allconverter.net/backup-exec/symantec-backup-exec-error-code-e000fe30.html I'm having a problem with a Windows 2003 Server that is running MSSQL 2005 and is also a guest VM on esx 3.0.1. Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Not a member? 0xe000fe30 - A Communications Failure Has Occurred.

However, if it is randomising the failures, I'd recommend updating the media server with any available patches and then push-installing these out to the remote servers you might have. The first file that it make it crash is a .pdf file. I forgot to mentionned that I am using the AOFO it is turned on with the radio on Microsoft Volume Shadow Copy Service (Windows 2003 and later) In the dropbox I navigate here 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)

I have the same problem! E000fe30 Backup Exec 2015 Go to Solution. Here is the error for just the SQL instance.

AOFO: Initialization failure on: "servername\SQLSERV".

Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped. Labels: 2010 Backing Up Backup and Recovery Backup Exec Error messages Troubleshooting 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! 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 V-79-57344-65072 - The Connection To Target System Has Been Lost. Backup Set Canceled. Creating your account only takes a few minutes.

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. Wondering even if it give the error E000FE30, it doesn't make sense and it's just that the issue it's trying to backup some corrupted files and probably by default backup exec The main reason is usually cost. his comment is here Solved!

I'm backing up system state, some of the directory structure and the SQL instance. 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 If this fails, check and make sure your AV (if you run one) isn't blocking access to those files...I've seen AVs do some funny things with files during a backup. Join and Comment By clicking you are agreeing to Experts Exchange's Terms of Use.

Backup set canceled. The one you pick depends on weather your running 32 bit or 64 bit software. When you think of replication, your mind drifts to solutions that replicate from one disk frame to another using block level technolo… Storage Software Dell Equalogic PS6000 - How to upgrade Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0129NAV~.TMP - 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. V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\D:". Thanks View solution in original post 0 Kudos Reply 6 Replies Hi M1ke, Do you need to CraigV Moderator Partner Trusted Advisor Accredited ‎09-15-2011 06:21 AM Options Mark as New voila!Top tip for anyone else facing this problem - don't just check the network drivers, but try turning off these features, even if you cannot see this issue at any other

Thanks 0 Kudos Reply OK, then on that particular CraigV Moderator Partner Trusted Advisor Accredited ‎09-15-2011 06:42 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email The job history indicates that it has backed up my C &Ddrives. I ran a backup and it crashed again on the same file. 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 agents, but I can't seem to figure

Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf - skipped. Run the ESX backup job again. Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf - skipped. 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

Ensure that WMI is running and that it's not blocked by a firewall. 1603". 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