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. Have I told you lately…that backups are important?
0 kommentar(er)
