I am using Backup Exec 2010 R2 on this SBS 2008 server, and it backs up 20Gbs of data. It take about an hour and half or even two hours to do so. I believe the slow down is backing up the System State. I also need to mention, this is clean install of the OS and Backup Exec 2010 only. I have all OS services pack and patches applied, and Backup Exec is all up-to-date too. I noticed the problem is the Windows Internal Database (MICOSOFT##SSEE) sqlservr.exe consumes 4Gbs+ of memory, and does not release the memory unless the Windows Internal Database service is restarted, or the server is rebooted, or if the sqlservr.exe (SQL Server Windows NT -64-bit) process is terminated.
I decided to implement the max amount of memory to 2147Mbs for both the MSSQL$MICROSOFT##SSEE and SBSMonitoring SQL instances as per the following article:
I have noticed the sqlservr.exe process now remains active witth a max memory allocation of 2.295,396K. I am not sure if this actually the best thing to do. Maybe what should be done is simply leave the default memory settings alone, and simply restart both the SBSMONITORING and MSSQL$MICROSOFT##SSEE services every morning at 5AM. A simply batch file with the following commands should do, but my concern is I do this will it possibly cause some sort of corruption or problems down the line.
net stop mssql$sbsmonitoring
net start mssql$sbsmonitoring
net stop mssql$microsoft##ssee
net start mssql$microsoft##ssee
This server installation was done using the defaults. I am not sure if I should leave the max memory settings as is, or restore the default setting back, or simply restart the services as described above, or even simply leave everything as is. I just want to new server to run smoothly, and have all the programs get along and place nice with each other.