For many clients I use a different container data folder so that the FMS backup schedule only backs up the FileMaker database files, and I use CrashPlan for backing up the container folder.

Unfortunately, 360Deploy expects the folder RC_Data_FMS to exist only in the database folder and fails with a 500 error if that path doesn't exist.

Is a fix for this on the radar? Some of my solutions have many GBs worth of container data and I'd rather not have FMP back up all of this data every time a backup schedule runs. 

Dave

I would also like to know the answer to this

Hello,

360Deploy doesn't do anything with external container data, and ultimately just swaps out the prod file with another file. If the prod file name doesn't change, the containers should resolve correctly, even if they are in a custom location.