OttoFMS Deployment Checks for Disk Space

OttoFMS
1

Before OttoFMS starts a deployment it checks to see if there is enough space in the FileMaker Server Backup folder, which is the folder that Otto uses to perform most off it’s work.

If your deployment includes Data Migrations, we check to make sure that the 3x the total data being migrated is available. If it isn’t OttoFMS will abort the Deployment immediately before anything even gets going. This 3x cushion prevents OttoFMS from causing your server to run out of space during a Deployment with data migrations.

Here is what that looks like. 3 minute long video.

Thanks

Todd

2

Is that 3x the size of the whole migration

or

3x the size of the largest file and 2x the size of the whole migration? Or something not completely 3x the size of the whole migration. Is it possible to set that somewhere yourself?

3

It is the whole sub-deployment.

And it has to be since we do the entire migration with all the files before we replace the files in the production

It is not currently possible to change it.

We will work to lower it if we can.

Todd

1 Like
4

I’m having an issue where the available file size isn’t refreshing in OttoDeploy v. 2.2.0. The files are hosted with ottomatic.cloud, and the dashboard there shows that enough space is free after deleting backups, but in OttoDeploy, I still get the same error with same old free the file size from when I first tried it. I even tried opening OttoDeploy in another instance of FileMaker Pro, but no difference.

5

Hey @CamelCase ,

OttoDeploy isn’t actually doing the disk space check. The check happens on your server when OttoDeploy attempts to start the deployment. You can verify this by copying the deployment JSON and sending the request manually. You’ve ensured you have at least 3x the file size on your destination available?

-Kyle

6

Yes, I freed up space to make sure I had enough available. I had to use a workaround this time, but if it happens again, I’ll follow your advice to try to debug.

1 Like