Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 6307

Backup Exec 2012 using all the memory

$
0
0
I need a solution

I have an extremely odd issue that just started happening a few days ago.  I have Backup Exec 2012 (Version 14 Rev. 1798) running on a Windows Server 2008 R2 box that is also my file server and domain controller.  I came in Wednesday and noticed I did not get my automated email that tells me the backup job had completed successfully.  I got on the server and seen that the bengine.exe process was using 98% of RAM and the backup job was still running.  I rebooted the server and the backup ran fine after the server came back online and finished as usual.  However, its done the exact same thing the last 2 days, but since its my DC and file server I can't just reboot it once employees start showing up so the backup isn't completing.  I restarted all backup exec services today and manually fired off the backup and this is what I've found:

-Initally the job says "Ready, no backup exec servers found"

-After about 5 minutes the job actually starts running and the memory usage is only about 10%

-The transfer rate starts at about 850MB/min and then goes down about 1MB every 3 seconds until it gets down to around 450/MB min

-Eventually the backup shows it has backed up the same amount of data as whats on the server, so almost like it has completed the job

So sounds good right?  Problem is that the job never completes in Backup exec and it just sits there, maxed out at 231GB (which is all my data).  The transfer rate continues to climb and climb and climb along with my memory usage until it eventually maxes out my memory.  I looked on my media and it looks like all the data is there so it seems like the problem is Backup Exec is having an issue with finishing/closing the job.  Does anyone have any idea what this might be from?


Viewing all articles
Browse latest Browse all 6307

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>