Progressive backups are FileMaker's version of the waiter who maneuvers from table to table, topping off everyone's glass of water. ![]() ![]() You can review some important considerations to help you identify essential backup requirements for your custom apps. Now you're free to set up a custom backup strategy. If you want to turn off the default schedule, head over to your preferred command line tool and perform this command: "fmsadmin disable schedule 1." Enter your FileMaker Server admin credentials when prompted. Perhaps midnight isn't an optimal time to run backups or maybe some of us want to keep more than one week of backups. Nonetheless, many developers and advanced users want control over what data to back up and when to schedule them. One of the nice things about the default Backup Schedule is that the FileMaker Admin Console gives us the ability to preserve selected backups for posterity, as long as we have enough disk space, of course. ![]() The newest backup replaces the oldest backup. This default backup stores up to seven data copies at a time. So, a backup automatically runs every night and makes timestamp copies of all our hosted apps and places them in a default folder named Backups, which is located in the Data folder. Right out of the box, Claris equips their product with a default Backup Schedule tool. Default Backupsīefore we dive into the particulars of how to bend FileMaker Server to our will, let's review some of the product's built-in functionality. We'll outline the use of these tools and how they connect to the decisions we make based on the principles we discussed in the previous post. ![]() The on-premise Claris FileMaker Server product not only allows us to share our custom solutions with our coworkers and the world, but it also gives us a set of tools to protect our valuable data and workflows. We've discussed some backup principles for our FileMaker applications, specifically, the when, what and where to protect the data within up our custom apps.
0 Comments
Leave a Reply. |