Offsite Backups

Offsite Backup to S3 Services

Otto version 2.0 and greater can be configured for offsite backups to any S3 (Simple Storage Service) compatible storage provider such as Amazon, DigitalOcean, Wasabi, or others.

Please note these warnings. Careful attention to details here can save hours of headaches!


Otto's Offsite Backups are configured in three easy steps: First, create an account with an S3 service provider. Then, create a FileMaker Server schedule to backup the selected files. Finally, configure Otto to perform the transfer.


  1. S3 Account Setup
    If you are unfamiliar with the process, here are some guides for S3 configuration with a few S3 Storage Providers.
    1. Verify Access to your S3 Storage Provider 
      Before you begin, you need a working connection to an S3 Compatible Service. While it is similar to FTP and many FTP clients can access S3, there are a few key differences. The connection information includes the following information:
      • Bucket Name
      • Region
      • Access Key
      • Secret Access Key
    2. If you do not have a working connection that you can test with a program like Cyberduck, Transmit, or others, then Otto will not be able to make the connection.
    3. When you have successfully connected to your S3 provider, we highly suggest that you create a new directory there for your backups. This is especially important if you are backing up multiple servers. You will use this later in the Otto configuration
    4. Please note that the S3 directory name is case sensitive, so "FilemakerServerBackups" is not the same as "FileMakerServerBackups".

  2. FileMaker Server Admin Console – Create a Backup specifically for Otto
    1. Create a backup schedule that copies all required files into the Offsite directory that Otto created during installation.
      • filemac:/Macintosh HD/Library/FileMaker Server/Data/Backups/_Otto_/Offsite/
      • filewin:/C:/Program Files/FileMaker/FileMaker Server/Data/Backups/_Otto_/Offsite/
    2. Schedule Notes
      • Do not use spaces in the name of the Schedule. For example, use "My_Offsite_Backup", not "My Offsite Backup". (For clarity, we suggest including "Offsite" in the Schedule Name.)
      • Set this backup to run at a time that is appropriate for your server. Make a note of this time to use when setting Otto's schedule in later steps.
      • When configuring Otto in Step 3, you want to schedule the backup to S3 for at least 2 hours later than this FileMaker Server backup. Doing so allows ample time for FileMaker Server to complete the backups and Otto to .zip the files before the transfer.

        Example  In this example, we are keeping four local backup copies. Set it to a value that makes sense for your system.
      • Run the schedule manually to verify that it works as intended.
  3. Otto Offsite Configuration
    Otto is configured for Offsite backups in just two easy steps. First, we'll edit the server configuration, then we will set the schedule for the backups.

    Otto Configuration Page
    1. Enter Connection Details
      • Under S3 Compatible Settings, click the Edit button to enter the information for your connection.
      • S3 Settings Window

      • Enter the same information that you used in Step 1 - Setup Your S3 Account, plus the unique Server Folder name for the server you previously created.
      • A unique Server Folder lets you use one S3 Bucket to backup all your FileMaker servers into its own subfolder within your bucket.
      • Remember! The server folder name is CaseSensitive

      • The Auto Delete setting determines if you want files that are removed from the FileMaker server to also be deleted from the S3 Bucket. Leaving this set to "Off" lets you keep just few backups locally while maintaining a full archive of the backups in your S3 storage.
      • Once you have entered the required information, Save Settings, then click the Test button. You should be warned if your connection settings don't work. If you receive a success message, then your connection to S3 is working.
      • Please note that this does not test for the presence of the Server Folder and it will not create it if it does not exist.

    2. Create a Schedule
      • Next, create the Schedule by clicking the Edit button.
      • Set the time to at least two hours after your FileMaker Server backup.
        We recommend setting the schedule to Zip backups and keep three backups locally.
    3. Click Save Schedule
    4. When you are done editing, click the "Run Now" Button. That will kick off your offsite transfer. Since this process could take a long time, we do not provide feedback here when it is complete. You must use your connection tool (Cyberduck, Transmit, etc.) or the AWS Console to check for your new backup.
    5. When complete, your Otto Offsite Backups configuration should look something like this:

That’s it!

Please reach out to us via the link at the bottom of the page if you have any questions.

Still need help? Contact Us Contact Us