"Transfer Container Data" Off, But It's Doing It Anyway

OttoFMS
1

I’m trying to create a new dev file (a “Replace” operation), and JUST a dev file—I don’t want the 100+ GB external container data. In my deployment, the “Transfer Container Data” option is turned off.

My deployments are failing due to timeouts. When I watch the files on the server, I see the OttoFMS_Temp_Backups folder get created, and the files getting copied in… including the container data. This takes a rather long time, and in my latest test, only 36 GB of the 100+ GB of container data transfers over (keeping in mind that I would prefer none of it). Furthermore, the failed deployment does not delete these temp backup files, so I have to manually delete them (after a server restart 'cause the files are “open in another program”).

Windows Server 2022
FileMaker Server 22.0.1
OttoFMS 4.12.0 (this was also happening in the previous version)
FMS backup destination is on secondary disk.

Is OttoFMS relying on an FMS style backup where there is no option to exclude the container storage? At this rate the only way to get this done is to manually copy and rename files.

p.s. This was after a completely fresh restart as well.

2

Hey Matt,

OttoFMS is using an FMS backup that backs up the container data (OttoFMS can’t turn that off). If you have the option, I would toggle on the “Close Files during Build” option. If the files are closed we do not need to rely on an FMS backup to create a copy, we can just copy them directly and avoid the container data all together.

I’ll take a look at the issue with the container data folders not getting deleted that you’re seeing, but the “close files during build” option is what you’re looking for.

-Kyle

3

Makes sense. I am good for now but will keep this in mind for next time.

It’s a shame that FMS can’t give us options about what we want to back up.