1 Reply Latest reply on Jan 20, 2015 10:09 AM by wimdecorte

    Yesterday's data for accounting

    siplus

      Hi all,

       

      Our solution - about 5 GB for this particular client - is used 6 days out of 7 by people that input, modify and consult the data. Think at a clinic/hospital as a close example.

      Their interaction with the system must be as smooth and fast as possible.

       

      On the other hand, we have the accounting people; their primary hobby is to run statistics and reports on the system, all the time.

       

      These people's interaction with the data (they are situated at a remote location via Citrix, just to make the whole sweeter) should have the minimal impact on the work of the main team. From experience, I know that some reports they are entitled to start will run for 6-10 minutes before delivering the results. As of now, during this time, the team 1 experiences spinning beach balls and text input that only appears in the fields after 3- 10 seconds, completely unacceptable.

       

      In order to achieve this (minimal impact from team 2 on team 1's work), what I would like is: create a configuration in which there are 2 servers.

       

      Server 1 hosts the live data and is only accessed by team 1. In the evening, all the data gets copied to Server 2. Team 2 (accounting) will only have access to "yesterday's data". They can massacrate the Server 2 with all their weird requests, with no impact on Team 1, fully knowing that what they see is one day late over the real thing. They can accept that.

       

      So 2 servers, 2 different IP addresses, 2 Filemaker Pro servers. But how would you implement this, concretely ?

      (data copy, start stop servers etc).

        • 1. Re: Yesterday's data for accounting
          wimdecorte

          FMS can be fully scripted.  Are the servers Windows or Mac?

           

          On the main server:

          - an OS-level script would find the most recent backup (no need to close any files on the main server)

          - copy that over to a network share

           

          On the other server:

          - an OS-level to grab the files from the network share

          - runs a last backup on the existing files

          - close the existing FM files

          - replace the existing files with the backup from the main server