the storage location is tied to the drive where the database is hosted.
move the db to that drive and the container data will be stored there.
Container data is actually still part of the database file system, even when using external storage options, so it all has to remain on the same disk.
Yes this was my understanding on filemaker 12 but let me quote a paragraph from Filemakers Container field enhancements located @ http://help.filemaker.com/app/answers/detail/a_id/11888
"When using FileMaker Server, you can now configure / store container data on a separate drive. For example, you can use a fast solid state drive (SSD) for your database and a large, slower drive for your container field data.".
1 of 1 people found this helpful
Make sure the other drive has the permissions set correctly. FMS runs as user "fmserver" of group "fmsadmin".
Generally mimic the permissions as set inside the FMS folder structure
I have manged to make it work on my development server. All be it a mac mini with the second disk an SD card. I didnt do anything with the manage containers dialogue. Storage is open. I have confirmed a file uploaded goes to the correct location. I used BatchMod to make sure the permissions are just so.
I created a new location (additional location 1) (at the root of my hard drive). I tweaked permissions and it validated. I then created a folder on the SD card, erffectively a second disk, and set the permissions. The in the admin console added that location so the paths I am using are:
filemac:/Macintosh HD/Filemaker/ for the FMP12 file
filemac:/Disk1/Filemaker/ for the containers
So the good news is it does work :-)
Thats using FMS 13 on OS X 10.8.5. Client is FileMaker 13 on OS X 10.8.5.
You did somewhat make me panic, as I have a server on order with the suggested SSD and HDD drives. All in all about £10k's worth based on the recommendation in FileMakers documentation. I am still a little worried; my server is Windows. If it doesnt work as advertised there might be an animated call to Filemaker.....
Many Thanks Damian the simple bit I was missing was hosting the database outside the default Library location, was screen shots were a great help a picture is worth a thousand words.