This site uses tracking cookies. By using this site, you agree to our Privacy Policy. If you don't opt in, some parts of the site might not function.
Blog
Home / Blog / FileMaker / FileMaker Cloud and Manual Backup Restore
27Sep 2016

FileMaker Cloud and Manual Backup Restore

About the Author

Mike Duncan Mike Duncan

Mike is an AWS Certified Solutions Architect as well as a certified FileMaker Developer. In addition to his work, Mike also enjoys pursuing his art, freelance writing, traveling, and spending time with his family.

Comments (6)

Green Wood - February 16, 2018

File maker automatic take the backup, if you are connected with Internet. A week’s worth of snapshots is stored at any given time, which will result in 504 snapshots (3 snapshots per hour * 24 hrs * 7 days) over time.

Reply
    Mike Duncan
    Mike Duncan - February 16, 2018

    Correct, with AWS Snapshots storing only the diff from the previous snapshot, so the actual size needed is only what changed on the volume.

Rodolfo Marra - May 11, 2018

Hi Mike, I know that we can create a new volume based on snapshot (as you shown).

But:
Could we create a new FMC instance on AWS (using FileMaker template as we did to create the first instance), stop it, dettach the dev/sdf volume (that is fresh with no data), attach the volume created using a snapshot from my old instance (that has all config and data) and start the new instance?

Do you know if in this case my FMC application (deployed in my new instance) will be up and running without problems?

I’m trying to design a Disaster Recovery Plan to restore our FMC application in new EC2 instance using AWS ressources. So, if the FMC server goes down (I dont know, if we patched and after reboot the server stopped), I’m wondering if we could create a new EC2 instance but use the old volume with all configuration and databases.

Thanks!

Reply
    Mike Duncan
    Mike Duncan - May 29, 2018

    I would not count on this working, especially through automated maintenance on FMC. My fear would be that the instance logs the volume ID of the data volume it was built with, and changing that would result in the wrong volume getting attached later, when it builds a new instance as part of maintenance that it can do sometimes.

Leave a Reply