Are you using FileMaker Server or planning to use FileMaker Pro's peer-to-peer hosting? If this is the real FileMaker Server then I would suggest not going with Windows 7 but ask for Windows 2008R2
In general: put the data files and backups on the RAID volume. FMS itself can be on the system drive.
Thanks for your reply. We are to use Filemaker 12 Server or Advanced. Not sure which one as of yet. Hoping to get some good feed back to aid us in the proper direction to go. I was understanding that Windows 7 Professional 64 bit would be fine. JM
1 of 1 people found this helpful
Windows 7 is not recommended for production use, mainly supported for development deployments. I would start off with a proper server OS.
Your projected load is fairly light so that's not too bad, but keep it in mind as your deployment grows more complex / busier.
In a planning section today we have cut the number of users to 3. With budget so near the end of the year upgrading the operating system will problem not happen due to money constants. Will it be a major issue to up grading at a later date. The work load should not be heavy for a while. New record loading per month should not be more than 200-250 records per month. The program was written to handle the inmate booking system for a 110 bed jail which stays full most of the time.
With the configuration listed in the original post, I still not sure if I should load the Filemaker Server 12 software on the system drive or the raid drive.
If anyone has a similar configuration please help with the pro's and con's, Thanks JM
I answered the question about where to install things in my earlier post: install FMS on the non RAID but keep the live files and all backups on the RAID system.
Best practices are rules-of-thumb and encapsulate a lot of lessons-learned from other deployments. Thay are not dogma's, it is OK to deviate from them as long as:
- the reasoning behind the best practice is understood
- the reasons for deviating from the best practice are discussed and documented. This is important because it will save a lot of potential finger-pointing when another developer / IT person evaluates the current deployment
I suggest you download the Server Configuration Guide from FileMaker and study it.