When you use an additional database folder and the database files in the additional folder use container fields that store files externally, you can specify a separate folder for the container data. By default, the container data folder is not backed up with the databases; however, you can select an option to include the container folder in backups.
You must create this folder on the master machine before specifying the path on the Configuration > Folders tab.
1. Click the Configuration > Folders tab.
2. Set up an addtional database folder. See Setting up an additional database folder.
3. Set Container Data Folder to Enabled.
4. Enter the full path to the location of the container data folder. The maximum length of the path is 255 characters.
•Windows: The path must start with filewin:/ and end with a slash (/).
For example, filewin:/driveLetter:/folderName/
If you are using a network volume, the path you enter must have the server name.
For example, filewin://serverName/shareName/folderName/
•macOS: The path must start with filemac:/ and end with a slash (/). If the folder is located on a remote volume, make sure the volume is mounted so that FileMaker Server can validate the path.
For example, filemac:/volumeName/folderName/
The container field objects for each database need to be in a folder identified by that database’s name:
RC_Data_FMS\<database_name>\Files\<database_name>\<table_name>\<container_field_name>See Uploading database files manually.
5. By default, the files in the container data folder are not backed up with the databases. To include the container data folder in backups, enable Back Up Container Data Folder. Selecting this setting can affect database performance. If you specify a container folder located on a network, it can affect the network’s performance.
See Understanding backup options.