FileMaker Extra: Best Practices Checklist

 <  Day Day Up  >  

Much of the work of server maintenance and administration consists of diligently following a routine. For each server or service you maintain, there should be a checklist of necessary tasks. Some of these you need to do only once, when you set things up. Others are recurring tasks that should be attended to carefully . In this section, we present a series of considerations for setting up and maintaining a FileMaker Server installation.

If you're working with network staff or administrators who don't have previous experience with FileMaker, offer them this list as a handy overview of the essentials of maintaining a FileMaker Server.

Determine Network Infrastructure

You'll want to run FileMaker traffic over the fastest network possible. Before doing anything about a server machine proper, make sure you have a handle on prevailing networking conditions. What's the topology of the network over which FileMaker will run? Is it fully switched, or are hubs involved? What's the minimum speed of links within the network? With what other services will FileMaker traffic be competing? Knowing the answers to all these questions can help you make the right hardware choices, and will give you a leg up on diagnosing any later problems that appear to be network- related .

Purchase Hardware

We discussed ideal hardware characteristics earlier in the chapter. Simply put, buy the best machine you can afford. Get a machine with one or more fast processors ( ideally , 2GHz and up), a healthy dose of RAM (1GB and up), fast disk storage (SCSI or Serial ATA, and consider a hardware RAID configuration), and a networking capability that matches the prevailing speed of your network. Expandability is also a good idea: Additional drive bays, external hard drive connectivity, and multiple slots (for additional or upgraded networking capability, for example) are all desirable.

All this might sound expensive, but hardware power these days is reasonably priced. For example, at the present time (mid-2004), $2750 will get you a PowerMac G5 with dual 1.8GHz processors, 1GB of RAM, and a 160GB Serial ATA drive. And $2600 will get you a Dell PowerEdge 1600SC with dual 2.4GHz Xeon processors, 1GB RAM, and a 73GB SCSI hard drive. If you want to spend less, you could reduce the amount of available hard drive space, use a bit less RAM (but not much less!) or drop back to a single processor.

Install Software

Use the latest version of an approved operating system, with all relevant patches and updates. Avoid enabling any other services on the machine except for those strictly necessary for system administration. In particular, avoid file sharing as much as possible. If it can't be avoided, make sure you do not enable file sharing for those areas that contain the hosted database files ” otherwise you run the risk of file corruption.

Install FileMaker Server and make sure all appropriate updates are applied. Make sure your version of FileMaker Server is compatible with both the operating system and, if applicable , the service pack level of the operating system.

Configure FileMaker Server

Configure FileMaker Server to a level appropriate for your expected usage (see the detailed notes earlier in the chapter). Bear in mind that it's worthwhile to try to use only those resource levels (for example, maximum numbers of connected clients and hosted files) that you think you'll need.

Deploy Databases and Schedule Backups

Decide on your database directory structure ”that is, how you'll group databases into directories on the server. Decide whether to use an alternate database directory. Regardless of your choice, establish backup schedules that provide you and your organization with an appropriate level of security. How much data can you afford to lose? Decide on the answer and back up accordingly . Remember that local backups by themselves are not sufficient security: You should make provisions to transfer this data to offline storage such as a tape backup.

Monitor Usage Statistics

Keep a careful eye on usage statistics, especially early on when usage patterns are being established. Be alert for signs of inappropriate configuration, such as a low cache hit percentage or a high amount of unsaved data in the cache. Make sure that your network bandwidth continues to be adequate.

Monitor Event Logs

Check the application event logs periodically to make sure things are operating smoothly. If you want to be especially proactive, and have some facility with operating system scripting, write a batch script that scans the event log for errors and emails you if errors appear in the log.

Perform Regular File Maintenance

It's probably a wise idea to run the File Maintenance tool, available in FileMaker Developer, periodically. How often to run it depends on how heavily used your files are. A good rule of thumb is probably to perform file maintenance once per month. If your databases experience thousands or tens of thousands of transactions a month, you may wish to optimize your files as often as every couple of weeks.

Keep Current with Software Updates

It should go without saying, but you'll want to keep current with all updates and patches to your operating system, and to all software packages installed on the server, including, of course, FileMaker Server itself.

 <  Day Day Up  >  


QUE CORPORATION - Using Filemaker pro X
QUE CORPORATION - Using Filemaker pro X
ISBN: N/A
EAN: N/A
Year: 2003
Pages: 494

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net