Backup Exec Error - e000fe30 - A communications failure has occurred.

For the last week my backups have been failing with error: e000fe30 - A communications failure has occurred. There is no other information besides that.  I am just backing up a domain controller. Most of the solutions I found relate to Exchange but in my case I am not backing up Exchange.  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 running.
tmelton82Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ssparks827Commented:
Make sure the VSS is enabled in services...in backup exec select use shadow copy or vss can't remember which one it is...I've seen this error on DC before...

0
tmelton82Author Commented:
It still failed with the same error. However it did provide me with more information this time.
Here is what I got.

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: B2D000075
Media GUID: {989b3809-3714-4d12-b0be-628677608208}
Overwrite Protected Until: 1/26/2008 2:13:56 PM
Appendable Until: 12/30/9999 4:00:00 PM
Targeted Media Set Name: Media Set 1
 Backup set #2 on storage media #16
Backup- \\servername\D: Data
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.
0
ssparks827Commented:
What is being backed up on the DC?  Just the shadow copy components, or data too?  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 NTBackup and see if that works...

I also found this article that says Symantec is aware of the problem.

http://seer.entsupport.symantec.com/docs/285437.htm

0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

tmelton82Author Commented:
It will back up everthing just fine except the D: drive which is our data drive when I do test runs.
0
tmelton82Author Commented:
I just ran the job and now I am getting this when trying to back up just the D: drive.

Backup- \\server name\D: DataV-79-57344-65072 - The connection to target system has been lost. Backup set canceled.

Exceptions

Backup- \\servername\D: Data  V-79-57344-34108 - An unexpected error occurred when cleaning up Symantec Volume Snapshot Provider (VSP) snapshots. Make sure that no other application has a lock on the cache files created by the snapshot operation.

 
0
ssparks827Commented:
Do you have an antivirus running?  If so try disabling it then run a test backup.
0
tmelton82Author Commented:
The job is running now but it is taking it over 20 hours to back up 300 GBs and still counting.
0
tmelton82Author Commented:
I let the job run and here is the errors I am getting now.

Backup- servername
V-79-57344-34110 - AOFO: Initialization failure on: "C:". Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP).
Snapshot provider error (0xE0008520): Device could not be snapped because it contains an active cache file.
Check the Windows Event Viewer for details.

Backup- \\servername\C:
Unable to open the item \\servername\C:\Documents and Settings\Administrator\NTUSER.DAT - skipped.
Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped.
Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc035EBE2E.xml - skipped.
Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0770157C.xml - skipped.
Unable to open the item \\servername\C:\Documents and Settings\Administrator\Local Settings\Temp\mmc0EF21990.xml - skipped.
Unable to open the item \\servername\C:\Documents and Settings\LocalService\NTUSER.DAT - skipped.
Unable to open the item \\servername\C:\Documents and Settings\LocalService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped.
Unable to open the item \\servername\C:\Documents and Settings\NetworkService\NTUSER.DAT - skipped.
Unable to open the item \\servername\C:\Documents and Settings\NetworkService\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\model.mdf - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdbdata.mdf - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf - skipped.
Unable to open the item \\servername\C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf - skipped.
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:\Program Files\SAV\SAVRT\0129NAV~.TMP - skipped.
Unable to open the item \\servername\C:\Program Files\SAV\SAVRT\0719NAV~.TMP - skipped.
Unable to open the item \\servername\C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db - skipped.
Unable to open the item \\servername\C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.log - skipped.
Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\enterprisesec.config.cch.2172.13372828 - skipped.
Unable to open the item \\servername\C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\security.config.cch.2172.13372828 - skipped.
Unable to open the item \\servername\C:\WINDOWS\system32\dhcp\tmp.edb - skipped.
Unable to open the item \\servername\C:\WINDOWS\system32\wins\winstmp.mdb - skipped.
V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\D:". Advanced Open File Option used: Symantec Volume Snapshot Provider (VSP).
Snapshot provider error (0xE000851C): Cache files required for the Symantec Volume Snapshot Provider (VSP) snapshot could not be created. Check that there is at least 50 MB of free disk space, and review the settings for the snapshot that are reported in the job log.
Check the Windows Event Viewer for details.

Backup- \\servername\D: Data
V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\Shadow?Copy?Components". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.
V-79-57344-34110 - AOFO: Initialization failure on: "\\servername\System?State". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.

0
StratfrordDCCommented:
I am having the same problem with version 12.0 on a 2003 Server.
I have a call logged with Symantec and will share the resolution if and when I get a response.
0
pslitbuyCommented:
StratfordDC did you ever hear back from Symantec...

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.  We have a nearly identical duplicate of this server for development and it backs up just fine. So I'm a little baffled.

The error is the same one that tmelton is getting on his D: drive. but I get it for everything that is backing up on that server.  I'm backing up system state, some of the directory structure and the SQL instance.

Here is the error for just the SQL instance.
AOFO: Initialization failure on: "servername\SQLSERV". Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the network, and then run the job again.

It says No for AOFO used but I have the box checked to choose the AOFO type automatically. Anywho, any light you can shed would be helpful!
0
StratfrordDCCommented:
My problem occurred after I upgraded to version 12.
Symantec got me to re-install the agent locally. I had to copy the RAWS32 directory from the remote server to the agent server and then execute the setupaa.cmd and setupaofo.cmd files which perform a silent install.
I then ran live update from the main console to apply 3 or 4 patches.
I haven't had any issues since.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tmelton82Author Commented:
I had Symantec Tech Support basicaly had me to do the same thing.
0
Pete LongTechnical ConsultantCommented:
The command files are slightly different for x32 and x64 bit servers

http://www.petenetlive.com/KB/Article/0000382.htm

Pete
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.