Progressive backups that run after a set interval of time has elapsed (every x minutes). Each set is a point-in-time restore point. FileMaker Server will manage that by deleting an old backup after it created a new one to keep to your requested number of sets. The settings per schedule allow you to define how many backup sets you want to keep. These take a copy of all the hosted files and creates a date-time stamped folder. Backup schedules that run at a set time.Multiple Backup and Restore PointsįileMaker Server Pro has two basic built-in backup mechanisms: What if you want to go back to a backup from yesterday afternoon to retrieve a record that was accidentally deleted? For that, you’ll still need to run multiple backups. One thing that this construct did not provide, though: multiple restore points. This setup did not use FileMaker backups to achieve its goal and is obviously fairly expensive both in development time (to have robust audit logging) and in infrastructure (having two servers running at all times).īut it serves as an example of how thinking outside of the box can be the answer. That setup ticked a few boxes in the realm of high availability as a hot/warm standby since we could very quickly switch over from one server to another and do that with minimal data loss. A second server hosts a copy of the solution plus the audit log file from the first solution and uses a server-side schedule to read the audit log and roll all the changes into the standby copy. Leveraging High-Availability ConfigurationsĪt DevCon 2010, I presented a session on how to set up two FileMaker Servers in a high-availability configuration. But if the FileMaker Server machine is not operational anymore, then this may mean standing up a new server in the same location or in a different location. If the original machine with FileMaker Server is still available, then that is really just a matter of copying the backup to the proper location. The second question speaks to how quickly you can retrieve the relevant backup and host the files again. The thing to do then is to set up a backup frequency that guarantees that you will have a backup that is not older than your goal. And you will lose the data since that last backup was done. That means that you will always have to revert to your latest backup. The answer to the first question cannot be “None.” With the current state of the FileMaker platform, it is not possible to have a hot standby where every single data change is simultaneously written to two servers. What is the maximum amount of time you can live without you system?.Let’s start with the basic questions to answer: And we’re happy to help think through some alternatives. Sometimes, the team deploying the solution just has a flawed understanding of how FileMaker Server does backups, including non-standard options and how to make them work properly. Or, they set them to only happen once or twice a day or even just once a week. Running the backup interferes with the overall user experience to the point that most disable them. Not because the business owners don’t want them to happen but because the performance impact is just too much. Over the years, I’ve spent a lot of time writing and speaking about what it takes to set up a solid deployment and how a good backup strategy plays a crucial role in the overall plan.īut…all too often, we see deployments where backups do not happen. Snap! - Year-Long Mars Simulation, Open-Source Custom Chatbot, Smart Goggles Spiceworks Originalsįlashback: March 28, 2003: Microsoft Windows Server 2003 was released (Read more HERE.)īonus Flashback: March 28, 1935: First Gyroscope Controlled Rocket Launch (Read more HERE.Have I told you lately…that backups are important?.Hi,I like to RDP into my Windows 10 Pro desktops for maintenance or installing software manually. Normally, when I right-click on the Start Menu and point to 'Shutdown or sign out' I can see the full complement of options: Sign out, Sleep, Shutdown and R. Shutdown/Reboot options when RDP to desktop? Windows.When our server admin assigns the device a reserved DHCP IP, and we reboot the device, it works fine from then on. Greetings!In the last month we have started to have random IOS devices stop working on our enterprise network. Dear SpiceHeads,As far as I can tell my predecessor didn't document software purchases and the related licence.I've been asked to audit, and record the relevant details, but apart from going machine to machine I don't really have a clue where to start.I'd.
0 Comments
Leave a Reply. |