Just like its predecessors, FileMaker Server 10 allows you to specify your own preferred locations for Database Files and backups. That's in addition to the default ones that FileMaker Server itself uses. In the movie that discusses the Databases Area of the Server Admin Console, we've already touched on the subject. You'll find it here in the Database Server Default Folders Tab. The grayed out path on the Default Folder Tab shows us where FileMaker's Default Databases Folder is. Any FileMaker files you put there will automatically be hosted when FileMaker Server starts its database engine. Plus any files in immediate sub-folders. Let's have a look at that. This is our Windows Server running FileMaker Server. This is FileMaker Server's Databases Folder and you'll find it in this, in this path. Any FileMaker files we put in this Databases Folder will automatically be hosted when FileMaker Servers starts the database engine and so will any FileMaker Files in its immediate sub-folders. But not files in sub-folders of the Databases Folder sub-folder. If we want to specify an additional Database folder, we can go ahead and do that. Note that you can not browse to select a folder. You have to manually type the path. And as you can see, the syntax is not your standard operating system format either. FileMaker basically created their own syntax so that it would work the same on both platforms. Remember that you may be running the SAT Tool on the Mac and connecting to a FileMaker Server running on Windows, just like we're doing here. The FileMaker syntax looks like this. You have to use FileWin if the FileMaker Server is running on Windows and then basically the same path as on Windows but with forward slashes instead of backward slashes. So let's specify a folder named Live Data. Note the helpful hint here that is shown at the bottom of the dialog. It's different based on what operating system the Server is running on. We know that our FileMaker Server is running on Windows, so the example that it's giving here is specific for Windows. If the FileMaker Server was running on OS X, then the example shown here would be specific for OS X. After you type in a path, you can have it validated to make sure it's correct. And we see that our path is indeed valid. Once you have the correct path set, FileMaker Server will host all the files there and one folder down from this particular folder. If we now go to the Databases Section of our Admin Console and do a refresh, we see that our Live Data Folder shows up here and it automatically shows us the files that are in that folder and we can verify that by going to our Windows machine and go look in the Live Data Folder. This is the Live Data Folder that we've just specified and there is indeed a FileMaker file in it. And the Admin Console correctly picked that up. So we can now go ahead and open this file so that it'll be hosted for clients to connect to. FileMaker Server includes a default backup folder. If you don't want the backups to end up in here, you can specify another location in the same way that we did for the databases location. You type in a path, you validate it and that's it. Note that FileMaker Server will always create a date and time stamped sub-folder in the Backups Folder, even if you choose to keep just one backup set. If you configure FileMaker Server to keep more backup sets, then it will create as many dates and time stamped sub-folders as you've decided to keep. If you can later change the Backup Setting to store less backup sets, then FileMaker Server will immediately and silently delete as many existing backup sets as it has to to conform with the new settings. The changes that you make here are applied immediately, so we don't have to restart FileMaker Server for them to take hold.