Forum Discussion

Nhan_Tran's avatar
Nhan_Tran
Level 2
9 years ago

Backup Exec 15 FP4 and SQL server 2012 memory usage.

Dear support team,

In our company, we used Backup Exec 15 for backup our database MSSQL server 2012 std. But after the bakup was done, the file sqlservr.exe take alot of memory usage. And it never release memory until we restart the SQL service.

We try to restart SQL service for release memory usage, hold the bakup task and the sqlservr.exe file grow up to slow. So I think the backup task affect to the sqlservr.exe file to much.

We check everytime the backup task was done and realize that, the file sqlservr.exe take about over 65% after the incremental backup done, and it take about 98% memory usage after the full backup done.

Please let us know are there any abnormal in this situation? Or are there any misss config in both system, Backup Exec or SQL server machine?

Thank you so much for your support and i am so sorry about my bad English.

  • For what you are describing, this is normal (but not necessarily desired) behavior of SQL.  SQL will basically attempt to load as much of the database into RAM as it can at any given point with a default SQL configuration.  As data is read from SQL (which may can triggered from running a backup amongst other things), it is cached into RAM and will stay there.  There are several guides available for properly tuning SQL, but you may want to look at the SQL min/max memory setting in your SQL instance....This Technet artivlcle from Microsoft may help as well:

    https://technet.microsoft.com/en-us/library/ms191144(v=sql.105).aspx

     

    In our environment we have dedicated SQL servers.  We typically set the max memory to about 8 GB less than the memory in the server to allow for plenty of RAM for other things to happen (antivirus scan, etc), but that number is really environmentally-dependant.

     

    In other words, this really isn't caused by Backup Exec itself.  If you were to run a backup using any other application, you would see the same thing happen....

  • For what you are describing, this is normal (but not necessarily desired) behavior of SQL.  SQL will basically attempt to load as much of the database into RAM as it can at any given point with a default SQL configuration.  As data is read from SQL (which may can triggered from running a backup amongst other things), it is cached into RAM and will stay there.  There are several guides available for properly tuning SQL, but you may want to look at the SQL min/max memory setting in your SQL instance....This Technet artivlcle from Microsoft may help as well:

    https://technet.microsoft.com/en-us/library/ms191144(v=sql.105).aspx

     

    In our environment we have dedicated SQL servers.  We typically set the max memory to about 8 GB less than the memory in the server to allow for plenty of RAM for other things to happen (antivirus scan, etc), but that number is really environmentally-dependant.

     

    In other words, this really isn't caused by Backup Exec itself.  If you were to run a backup using any other application, you would see the same thing happen....

  • Thank you so much for your comment and support tape monkey.

    But I really need some more advice from others because I am a newbie with BE software. Please...

  • Can anyone give me some more advice pleaseeeeeeeeeeeeeeee..... Thanks

  • Tape monkey gave the advice already - if SQL Server processes are using memory during/after backups it is because of how SQL works and not Backup Exec

    If you cannot understand the information in the MS link provided by tape monkey then you may need to engage Microsoft (or a consultant that is specifically a specialist in SQL)