FM Server Set Container Backup Within Schedules

Idea created by Andy Hibbs on Oct 6, 2016
    • Magnus Fransson
    • Andy Hibbs
    • Johan Hedman
    • GordonShewach
    • BeatriceBeaubien
    • Markus Schneider
    • kiwikaty

    When making backups of a database system for the purpose of creating a copy for further development we are having to wait for nearly 2 hours on some solutions, as we can't take a backup of the FileMaker files without backing up all the container folder files, which are Gbs in size.


    The database file backup alone would only take a minute or two, without this.


    We have requested this before, but the above is a better example as to why we believe the container backups should be set in each schedule and not in Database Server:Folders.


    The only option we currently have is to wait the 2 hours or so, wait for the overnight backup or make an overall decision to not backup the container data folders - all of which have productivity or risk implications.


    This problem is particularly acute when using data separation designs, where frequent small updates can be made by dropping in a revised UI file. However, if a tweak is made on the live system and then another development copy is required, then the inability to only backup the FileMaker files is a major hit on productivity.