Dave Graham Posted September 13, 2017 Share Posted September 13, 2017 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 1 Link to comment Share on other sites More sharing options...
Newbies Joe Patterson Posted February 19, 2019 Newbies Share Posted February 19, 2019 I would also like to know the answer to this Link to comment Share on other sites More sharing options...
ryan360Works Posted February 19, 2019 Share Posted February 19, 2019 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. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 1892 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now