1 Reply Latest reply on Nov 7, 2013 12:00 PM by disabled_ntaylor

    RAM increases to 99% every time backup jobs run

    KevinSimmons
    KevinSimmons Nov 4, 2013 1:05 PM

      Summary

      RAM increases to 99% every time backup jobs run

      Product

      FileMaker Server

      Version

      12.0.1.178

      Operating system version

      Windows Server 2008 R2 Standard 64 bit

      Description of the issue

      Every time the backup runs the Used Physical Memory gradually increases to 99% and maintains that level until the job is finished. And then it immediately goes back down to the 20 to 29% range.

      Steps to reproduce the problem

      Problem occurs every time the backup runs at 6:00am, 12 noon and 6:00pm.

      Configuration information

      We have cleared space on the C drive so that at least 50% is available. The physical RAM has been increased from 4 GB's to 12 GB's. Virtual Memory has been increased to 18 GB's. And just today, the Database cache was increased from 128 MB's to 3072 MB's. All of these efforts have been fruitless, unfortunately. Besides Symantec Endpoint Protection Manager, there really is no significant applications running on this server. Not really sure where else to turn now.

      • 54 Views
      • Tags:
        • 1. Re: RAM increases to 99% every time backup jobs run
          disabled_ntaylor Nov 7, 2013 12:00 PM (in response to KevinSimmons)

          Kevin Simmons:

               Thank you for the post.

                

               Does the issue occur with FileMaker Server 12 (Advanced) updated to the latest version?

                

          Software Update: FileMaker Server 12.0v4 and FileMaker Server 12.0v4 Advanced release notes

                

               Backing up a file of any significant size is an intensive memory process and will utilize any and all available resources provided by the CPU and RAM. For a computer program to be suffering from a "memory leak" the RAM is both used during processing and then not returned to the operating system once the processing completes. 

                

               Please report back with the tests results after updating to FileMaker Server 12.0v4 (Advanced).

                

               PhilModJunk is correct that best practice is to schedule backups during downtime when nobody is using the database file.

                

               Since you mentioned Symantec Endpoint Protection Manager, please note that best practice is to exclude the hosted databases from scans by third party security or antivirus software as this may lead to file corruption.

                

          Antivirus Software May Cause File Corruption

          Is it safe for antivirus software to scan FileMaker files?

                

               "If scanning of the files is necessary, please schedule the antivirus software so that it does NOT scan during the time FileMaker Server is backing up the database files.  It is preferable to scan the database files after the files have been backed up completely."

                

               TSFalcon

               FileMaker, Inc.