I’m getting this error message from BE when attempting to run jobs on two separate servers.

The jobs are attempting to backup SQL server databases

Final error: 0xe00084f8 - The network connection to the Backup Exec Remote Agent has been lost. Check for network errors. Final error category: Resource Errors

This error happens on the Full and Daily Differential backups, not the log backups.

This happens when initiated manually or when run automatically

So background on the servers/other info

One is a physical machine, one runs on VMware ESXi 5.1

Both have 4 gigs of ram and similar CPU (8 cores)

OS: Windows 2003 R2

SQL Server: 2005 SP4

BE: 2010 R2

Job size is 250 gigs for one server, 300 gigs for another (We have several TB size databases that do not fail)

When failing on a full backup fails significantly % wise, 250 gig db only hits about 40-60gigs

Backups have their own dedicated network with 1gig access

Permissions are not an issue, tested via elevation

I've noticed that after a time if I'm watching the job run, the byte count will just stop increasing, it will fail 5-10 minutes after that.

So I’ll go through all of the things I’ve done thus far to try and solve this problem

-Restarted the be agent

-Restarted the server

-Uninstalled/Reinstalled the be agent

-Upgraded to SQL Server 2005 SP4 (This seemed to fix the problem for a couple of days)

-Originally these databases and servers were part of a large backup job with a number of SQL databases they have been since isolated and separate jobs created

--Tested each database individually and it appears size related (maybe?), as the larger databases fail, but the smaller ones grouped together also cause a fail.

-netstat –a shows nothing on port 10000

I get 4 or 5 error messages in the event log on the agent’s server, these pop up around the time the backup is running and are likely related. Here is the output from the latest attempt to run the job. (I’ve removed what I think might be sensitive info with ****)

---

Event Type:        Error

Event Source:    SQLVDI

Event Category:                None

Event ID:              1

Date:                     6/3/2014

Time:                     11:56:30 AM

User:                     N/A

Computer:          ****

Description: SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=4572. Thread=4492. Client. Instance=. VD=Global\****_00__215eddd0_1765_4cb6_978b_815fbd697760__SQLVDIMemoryName_0.

---

Event Type:        Error

Event Source:    SQLVDI

Event Category:                None

Event ID:              1

Date:                     6/3/2014

Time:                     11:56:30 AM

User:                     N/A

Computer:          ****

Description:SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=1672. Thread=944. Server. Instance=MSSQLSERVER. VD=Global\****_00__215eddd0_1765_4cb6_978b_815fbd697760__SQLVDIMemoryName_0.

--

Event Type:        Error

Event Source:    MSSQLSERVER

Event Category:                (6)

Event ID:              3041

Date:                     6/3/2014

Time:                     11:56:30 AM

User:                     ****

Computer:          ****

Description: BACKUP failed to complete the command BACKUP DATABASE **** WITH DIFFERENTIAL. Check the backup application log for detailed messages.

--

Event Type:        Error

Event Source:    MSSQLSERVER

Event Category:                (2)

Event ID:              18210

Date:                     6/3/2014

Time:                     11:56:30 AM

User:                     ****

Computer:          ****

Description: BackupVirtualDeviceFile::ClearError:  failure on backup device '****_00__215eddd0_1765_4cb6_978b_815fbd697760_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

---

Event Type:        Error

Event Source:    MSSQLSERVER

Event Category:                (2)

Event ID:              18210

Date:                     6/3/2014

Time:                     11:56:30 AM

User:                     ****

Computer:          ****

Description: BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device '****_00__215eddd0_1765_4cb6_978b_815fbd697760_'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

--

I’ve got the last bit of output from SGMon from a job I ran on Friday and truncated the log down to around the time the job failed if that would be helpful.

I’m new to systems administration and none of my coursework in the past covered third party backup applications. So please any help would be appreciated.

Also I know very little about SQL functionality so if I need to run queries I’ll need some help with that.

Thanks

Hello,

I am currently experiencing an issue with Symantec Backup Exec 2010 R3. An event is being spammed every 3 seconds in to the event viewer. The Heading to the event is ASP.NET 2.0.5.727.0 with Event ID 1309.

The contents of the Event Show:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 21/11/2013 14:00:58
Event time (UTC): 21/11/2013 14:00:58
Event ID: e41c698f1c084c6d8f9d5780ce0c5b83
Event sequence: 1
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: c738b644ff834fdb8b5031854efbc52e-34952-130295160569617174
    Trust level: 
    Application Virtual Path: /CRF
    Application Path: C:\ProgramData\Symantec\CRF\c738b644ff834fdb8b5031854efbc52e\
    Machine name: DOMAIN NAME
 
Process information:
    Process ID: 28192
    Process name: beserver.exe
    Account name: DOMAIN NAME\USERNAME
 
Exception information:
    Exception type: HttpException
    Exception message: Server cannot access application directory 'C:\ProgramData\Symantec\CRF\c738b644ff834fdb8b5031854efbc52e\'. The directory does not exist or is not accessible because of security settings.
 
Request information:
    Request URL: http://127.0.0.1/CRF/CRF.aspx?DataFile=C:\Users\USERNAME\AppData\Local\Temp\c738b644ff834fdb8b5031854efbc52e\Data.xml&RDLFile=C:\Users\USERNAME\AppData\Local\Temp\c738b644ff834fdb8b5031854efbc52e\RDL.rdl
    Request path: /CRF/CRF.aspx
    User host address: 127.0.0.1
    User: 
    Is authenticated: False
    Authentication Type: 
    Thread account name: DOMAIN NAME\USERNAME
 
Thread information:
    Thread ID: 13
    Thread account name: DOMAIN NAME\USERNAME
    Is impersonating: False
    Stack trace:    at System.Web.HttpRuntime.EnsureAccessToApplicationDirectory()
   at System.Web.HttpRuntime.HostingInit(HostingEnvironmentFlags hostingFlags)
 
 
Custom event details: NOTHING SHOWN

I've been unsuccessful in figuring out what is causing this, I can see from the error it is attempting to open a file that doesn't exist however how do I stop it?

Kind Regards

I am having the same exact issue as you Simonx182 with the same exact errors. We are running BackupExec 2010 R3 on a Server 2008 R2 OS which is our domain controller also. When I first started noticing the flooding of these events in the application log, I restarted the server. All was good for a couple of days and it came back. Did it come back for you after you restarted? Our CPU usage is between 80-90% all the time and beserver.exe was using 9GB of memory. This is ridiculous. Can someone help with this issue please?

I have a Windows Server 2008 R2 64-bit, Netbackup 7.5.0.6 master server for my virtual datacenter. I run vmware query based policies with overlapping full and differential backup schedules. I have 150 policies for about 2,000 virtual servers that start off in 30 minute increments from each other spread out accross a 24 hours per day, 7day window. Over time this has migrated to a steady and fairly even rate of data processing distribution throughtout the window. My backup failure rate before removing the false positive is under 1.5% on average each week. It would be less that that if there was a way to prevent these error/exit code 200's from occuring which are only informational in nature. Is there a way that when Netbackup finds that it has no jobs that are needed to run for a query based policy that they could be an exit code 0?

Hi

I am attempting to restore a server snapshot using the Symantec System Recovery boot CD but no target drives are being listed.

The server is a vmware/vcloud VM. I have run the driver validation tool which only mentioned the network driver was missing, which I have resolved. It didn't say anything about the storage driver being missing.

If I run a cmd from the Analyse menu and run diskpart, there are no fixed disks to show.

The VM boots in to the OS fine, so I know the virtual hard drive assigned to the VM is functioning fine.

Any ideas please?

Cheers,

James

Hi,

I would like to understand how Backup Exec keeps the information about LTO tapes. Here is my question;

I have a backup on LTO tape, i would like to send this tape to an other facilty/machine. What files do i need to provite ? For example, i have a LTO tape labeled as BCK-0001, if i just copy catalog information and send it with tape, will it be accesible ? If not, what else do i need to provite ?

Regards.

Hello,

I'm new to BE. Actually I've been waiting for the 2014 edition to use on a 2012r2 server.

I installed the product in trial edition and tried to configure storage. My tape, HP DAT 160 USB, is not recognized, so I cannot proceed with the evaluation.

How can I resolve the problem?

Thanks in advance for any help.

Best regards.

I am having an issue whereby we have the Symantec Backup Exec 2012 SP4 running on Windows Server 2008 R2 configured as only Media server, which has connectivity to the organization production LAN with (configured with static IP, net mask, gateway and DNS) and also the Private backup LAN (configured with separate IP and net mask).  I have configured the all backups network property tab to use the dedicated private back up network and the specific IPV4 subnet, but on some systems, this does not seem to work correctly and data seems to goes over the production LAN. On the media server, under Network Adaptor Advanced Settings was manually set to Backup LAN as first priority followed by Production LAN below.

Media server has a hostname on the production LAN eg xxxnbkp01 with 10.101.x.x, which is also registered in production DNS and a totally separate private IP and hostname for the backup LAN eg xxxnbkp01-bk 10.10.1.x (backup LAN information is configured in host file on media server/client servers OS to reference host and vice versa, but not registered in DNS).

Backup policies are configured to backup clients running Windows Server 2012, serverX IP 10.101.x.x using the backup LAN hostname and IP as specified in the host files eg. client1-bk IP 192.168.x.x.

We are running the latest version of Backup Exec 2012 SP4 and anyone could do with guidance on how others may have implemented a totally dedicated private backup network.  Also are there any issues encountered on best practices that need to be followed in using backup LAN. Anyone assistance would be helpful.

I'm trying to find out if Symantec has tested and qualified RHEL Cent OS v6.5 for use as a Master and Media Servers on Netbackup v7.6...please advise asap.

NOTE: I did not see it listed specifically in the supported OS compatibility matrix.

Thanks,

Monte Kasper

LexisNexis

Hi all,

using nbu 5230 as master server, version 2.6.0.1

All my policies using now are VMware and MS-windows. All with accelerator enabled.

All policies perform a daily incremental backup at Mon-Fri, and a Full backup at Saturday.

I read the guide recently that Symantec suggest to have a schedule with full backup and accelerator forced rescan every 6 months.

My question is, if I also have a full backup (with forced rescan) that runs every 6 months, at the day that this policy run, will I have 2 full backup at the same time? (as I also have a weekly full backup without forced rescan option) 

I want it works like when the policy with forced rescan runs, it will not run the weekly full rescan. Is it possible?

Thanks a lot!

Hi

I have a user who is having a problem starting his DLO agent. Most of the time he gets the error "Symantec DLO Desktop Agent has stopped working".

See attached screenshot.

This is what I've tried:

1) Uninstall Agent and re-install

2) Uninstall Agent, remove Symantec DLO directory from Program Files and AppData directories, re-install

Are there any registry keys that can be removed to ensure that everything related to Symantec DLO is removed?

Also, can you think of any other reasons why it keeps giving this error? Would it be an idea to start the Agent in Compatbility mode?

We're currently using Symantec DLO 7.0 and are not in a position to upgrade to 7.5 at the moment.

Any help is greatly appreciated.

Thanks

Jimmy

The Symantec engineers handling my currently open support cases have informed me that Backup Exec 2014 is out, and wouldn't I just try and upgrade in the hope that it might resolve the issues in question.

Frankly, I'm scared.

It took me nine months, half a dozen support cases, and countless posts to this honorable forum to get Backup Exec 2012 into a shape where I can say with conviction that I "have backups". I certainly don't want to repeat that experience. In fact I cannot afford to.

On the other hand, there are a couple of issues left which I would love to see fixed, including but not limited to the still open support cases, and I see most of these heading inexorably towards the "upgrade to BE 2014 or live with it" resolution, if not already there.

Is there already experience with upgrading from BE 2012 to 2014? What should I prepare myself for? How much time and manpower do I need to budget? Is there a step by step description of the upgrade process I can check in advance for problematic steps and necessary downtimes? What about the dreaded HCL and SCL? Is there a list of hardware and software for which support has been dropped? What is my way to back out in case the whole endeavour turns catastrophic?

Media server configuration:

• Backup Exec 2012 Service Pack 4
• Microsoft Windows Server 2008 R2 Standard
• Cisco UCS C22 M3S V02, dual Xeon E5-2440 quad core, 16 GB RAM
• LSI MegaRAID with six 1 TB S-ATA disks in RAID5 configuration als local disk storage
• Tandberg T24 LTO-5 changer connected to LSI SAS controller as main tape library
• Tandberg standalone LTO-5 drive connected to Emulex FibreChannel controller as secondary tape drive

Backed up servers:

• one VMware ESXi 5.5 HA cluster
• one virtual Windows Server 2008 R2 server (running on the VMware cluster but backed up separately through RAWS because Backup Exec 2012 AVVI cannot cope with a 2 TB disk)
• one physical Red Hat Enterprise Linux 6 server
• itself

Dear All,

One of the my vm backup is failling with status code 6 but in the same policy rest of backup is completing successfully . jobdetails are below and some log are also attached kindly assist on this .

Enviornment Details :-

Master and media Server windows 2008 R2,

netbackup 7.5.0.5 on master media

vmware backup is configured through vcenter

Thank You

6/4/2014 11:43:08 PM - Info nbjm(pid=8476) starting backup job (jobid=429485) for client WFBZAEHO1, policy VMWARE_VM_VCAEHO_GROUPC_CBT_PRD, schedule DAILY-INCR  
6/4/2014 11:43:08 PM - estimated 15346348 Kbytes needed
6/4/2014 11:43:08 PM - Info nbjm(pid=8476) started backup (backupid=WFBZAEHO1_1401910988) job for client WFBZAEHO1, policy VMWARE_VM_VCAEHO_GROUPC_CBT_PRD, schedule DAILY-INCR on storage unit medhoae3_ho_stu1
6/4/2014 11:43:10 PM - started process bpbrm (4864)
6/4/2014 11:43:11 PM - Info bpbrm(pid=4864) WFBZAEHO1 is the host to backup data from     
6/4/2014 11:43:11 PM - Info bpbrm(pid=4864) reading file list from client        
6/4/2014 11:43:12 PM - Info bpbrm(pid=4864) starting bpbkar32 on client         
6/4/2014 11:43:12 PM - connecting
6/4/2014 11:43:12 PM - connected; connect time: 00:00:00
6/4/2014 11:43:13 PM - Info bpbkar32(pid=11200) Backup started           
6/4/2014 11:43:13 PM - Info bpbkar32(pid=11200) CONTINUE BACKUP received.          
6/4/2014 11:43:13 PM - Info bptm(pid=8820) start            
6/4/2014 11:43:13 PM - Info bptm(pid=8820) using 524288 data buffer size        
6/4/2014 11:43:13 PM - Info bptm(pid=8820) setting receive network buffer to 2098176 bytes      
6/4/2014 11:43:13 PM - Info bptm(pid=8820) using 256 data buffers         
6/4/2014 11:43:18 PM - Info bptm(pid=8820) start backup           
6/4/2014 11:43:19 PM - begin writing
6/5/2014 12:18:42 AM - Info bptm(pid=8820) waited for full buffer 1 times, delayed 136103 times    
6/5/2014 12:18:42 AM - Info bptm(pid=8820) EXITING with status 90 <----------        
6/5/2014 12:18:42 AM - Info bpbkar32(pid=11200) bpbkar waited 0 times for empty buffer, delayed 0 times.   
6/5/2014 12:18:45 AM - Error bpbrm(pid=4864) could not send server status message       
6/5/2014 12:18:46 AM - Critical bpbrm(pid=4864) unexpected termination of client WFBZAEHO1        
6/5/2014 12:18:46 AM - Error bpbrm(pid=4864) cannot send mail to braju@unb.ae,Satish.K.Ajmera@unb.ae,DataCenter@unb.ae,criticala@unb.ae,omukthar@unb.ae        
6/5/2014 12:18:46 AM - end writing; write time: 00:35:27
the backup failed to back up the requested files(6)

I need to migrate my Master server from Windows server 2003 x86, running Netbackup 7.5 to Windows Server 2008 R2 running Netbackup 7.6

I have found the following documents:

http://www.symantec.com/business/support/index?page=content&id=TECH77447

http://www.symantec.com/business/support/index?page=content&id=TECH135546&actp=search&viewlocale=en_US&searchid=1401974277268

I would say that I am fairly happy with migrating our 2003 x86 master server (EMM) to a 2008 R2 x64 O/S, however the thing that’s concerning me is that my image DB is on a different drive partition to the NB installation drive, which was completed by using the ALTPATH method listed In the link above.

I believe that I need my Image DB to be on the same drive as the NB installation prior to backing up my catalog in readiness for the move, so I have an idea on how to get around this which is a bit of a bodge. Would anyone have best practise suggestions on how to accomplish this?

Any help with documents for this migration would be appreciated.

Carl

So I've gone to 2.6.0.2 now that Heartbleed has been addressed.  Why has root been taken away?  I know how to get it back but taking away root is like selling me a car then not letting me drive it.  As a former UNIX admin, I only run NBU on UNIX platforms and I am ALWAYS super-user.

I am really excited to announce that Backup Exec 2014 is generally available!

What’s New in Backup Exec 2014?

• Windows Server 2012 and 2012 R2 support: Backup Exec now fully supports Windows Server 2012 and Windows Server 2012 R2.
• Superior visibility into backup jobs: We heard you loud and clear. The Backup Exec job monitor is back. You can monitor the status of all backup jobs from a single view, giving you visibility into the status of your backup jobs. In addition, save time and simplify the creation of backup jobs by backing up and managing multiple servers with a single backup job.
• Simplified upgrade/migration process: Many of you asked us to simplify the migration process to the latest version. If you are using Backup Exec 12.5, 2010 or 2012 you can upgrade and keep your jobs and settings intact, simplifying the move to Backup Exec 2014.
• Granular recovery for Exchange 2013 and SharePoint 2013: Backup Exec granular recovery technology (GRT) is now available for Exchange 2013 and SharePoint 2013. From a single-pass backup, you can quickly recover granular objects such as Exchange email and SharePoint documents.
• Optimized performance: In our internal testing, Backup Exec 2014 has shown up to 100%[1] faster backup and deduplication speeds compared to previous versions of the software.

What about Cloud Capabilities?

Over the past several months, many of you have been asking about cloud capabilities. I’m excited to announce that Backup Exec 2014 also supports:

• Riverbed Whitewater Appliance
• Quantum Q-Cloud

Please stay tuned on this front - we plan to announce support for an additional cloud platform shortly.

What Are Customers Saying?

Thank you to the more than 3,700 customers and partners who registered to participate in the Beta program this spring. Below is some of the most recent feedback we’ve received:

• “Our backups complete with near 100% reliability and restores are consistently successful with zero fuss.” – Brandon Mosak, IT Director, Task Force Tips, Inc.
• “It Just Works!” – Terry Green, IT Manager, Autochair
•  “I’ve used other backup solutions on a virtualized environment with varying degrees of success. But for me, the ability to back up a virtual machine image as well as the files inside it—or restore an entire virtualized application or the granular data in it, whether it’s Exchange or SharePoint or SQL—that’s what makes Backup Exec 2014 far more compelling than its competitors.” – Paul Flatt, Infrastructure and Support Manager, Mitre 10 NZ

But don’t just take their word for it, download Backup Exec 2014 today and let me know what you think. I look forward to hearing about your experience.

What’s Next?

We will continue to release service packs every 90 days, and the current target for Backup Exec 2014 Service Pack 1 is September 2014. In addition, we’ll keep you updated as we have more information to share about future product plans.

If you’d like to read more about the journey to Backup Exec 2014, check out the post from Pablo Stern, Senior vice President for Symantec Backup and Recovery, here.

Thank you for your continued support of Backup Exec.

To access a 60-day trial of Backup Exec 2014, go to:

www.backupexec.com/trybe

––––––––––––––––––––––––––

[1] Symantec internal testing.

HI,

i take multiple backups of  file system on tape and each backup retention is two week. manually expire it first backup and check the use sapce on tape is remains the same.

Kindly guide me how i release its space after backup expire.

regards.

Hi,

I try configure a job of database Oracle on Windows Server. I follow this steps http://www.symantec.com/business/support/index?page=content&id=HOWTO73873 

Username and password of oracle are OK, agent oracle of the server is configured

When run jobs, stop about 15 sec and show this error:

Completed status: Failed
Final error: 0xe0000340 - The Database script returned an error.  Refer to the Database script output section in job logs for more details.
Final error category: Resource Errors

-

The Database script returned an error.  Refer to the Database script output section in job logs for more details.

Could you help me?

Thanks!

Greetings,

I have a domain controller (1 of 3) which must have a role removed before retiring.  The drive crashed and server had to be rebuilt and manually restored with advanced team assistance.  The C: restoration went well but the system state w/AD resulted in a hal.dll missing error and no boot. The server is Win2K8 Standard.  The BE version is 2012 but newer than the final version of the server tape. The repaired / restored server shows a W2K8 svr installation on the drive/partition.  I can browse the drives and directories from the repair command prompt.  The curious items are 1) the OS drive letters flipped - OS is now D: and the recovery drive is C: and 2) in most directories almost every file has a duplicate which has additions to the extensions.  I.E.the hal.dll file has below it a file named "hal.dll.USE1070C".  I can run DISKPART to re-letter the volumes.  I can run BCDEDIT to see details.  I ran bootrec.exe to add the OS.  I ran bootrec /fixboot and now have a missing bootmgr.  I seek ideas before attempting to run bootrec /fixmbr as this may result in another hardware rebuild and tape restoration.  A solution would be greatly appreciated as this is taking serious time away from other work. thnx

Can the creation of a RHE client iso images be done from a single RHE Linux BMR Boots Server if the other steps in creating a NBU 7.6 BMR solution are done correctly?  Recovery across the IP network is not required and all recoveries will be done via iso images. 
 

We have many VLANs and not able to put Boot Servers on every network segment.  Plus according to TECH161483 network recovery has the potential of interfering with the existing KickStart and Boot Relay servers.  With these limitations it appears that recovery via iso images is the way to go and looks simpler.

Creating iso images of the bootable SRT image seems to unique for each client restore - true?     
 

Methodology used for the network boot processing of a Linux Bare Metal Restore (BMR) client.
http://www.symantec.com/docs/TECH161483