Just upgraded from a much older version (Mac) and have a few questions
that don't seem to be covered in the docs:

1. Why does it install in the Library rather than Applications?

2. Old version, you put your Filemaker file in the same folder as the
server and it got served. Now, when you "upload" a database, it seems to
somehow be absorbed into the server: there's no file you can look at,
e.g. to make a change. Is a copy of the file still there somewhere, if
so where?

3. I want to send backups to a mounted volume, but everything I've put
in the "path" space is rejected, and there's no browse option. Is there
some special format for the path, or is it just not able to back up
external to the host machine?

On 3/8/2011 12:12 PM, Bill Steele wrote:
In the FileMaker program folder is a sub-folder labeled data or
databases. You will find them in there.


Be sure you have a fill path, beginning with FileMaker's path-type
protocol, and ending with a slash. For example, this is a path to an
external drive that is legal on a Windows server (sorry, I don't have
any Mac servers to refer to): filewin:/F:/Backups/

Did you check the Quickstart guide that is installed in the
Documentation subfolder of the FM Server program folder?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg
FM Professional Solutions, Inc. Los Angeles

FileMaker Certified Developer
Associate Member, FileMaker Business Alliance

On 9/03/11 6:42 AM, Bill Steele wrote:

server is a service, not an application. It also has a unique set of
(Unix) permissions on the directory and sub-directories



/Library/FileMaker Server/Data/Databases/

note FM have 'kindly' thought to (continue to) include a space in
'FileMaker Srever' directory name, so all paths in shell scripts etc
will need to be correctly escaped. Another one of those little FM things
good coding practice would tidied up years ago.


it has to be a directly connected volume, it can not be a LAN/WAN volume.
The path must be prefixed with filemac:
The path must end in a slash/

an easy way to get the full path is to drag the target onto an open
terminal or into an open Smultron window (Smultron is a free very handy
editor)
- neither will have the trailing slash
- you will need to remove /Volumes from the parsed path


If you want to push from the attached backup volume to a LAN volume, a
launchd scheduled shell script is one way to go; but more involved than
one may initially think.