I have FMS 10 on a Windows Server 2003. 3-5 users, all of them on XP
machines, small DBs.

The servers gets rebooted once a week. Every now and then, FMS does
not work afterwards, says its running, can't be stopped or restarted.
Works fine after a second reboot of the server machine.

This server machine is the only server in the network and does
everything. I like FMS 10 to have its own machine.

Can I use a Mac Mini with 2GHz and 4GB RAM with OS 10.6 (no server
software) for FMS here? Known issues? And can someone put me on the
right path regarding moving the backups to the Windows Server machine
where they get taped?
--
Christoph Kaufmann
http://clk.ch

Hi Christoph


On 11/07/10 4:59 PM, Christoph L. Kaufmann wrote:
Which people do, but FM recommends against.




I like FMS 10 to have its own machine.

Which apparently you currently don't? Which may well be the source of
the problem; the FM documentation will indicate the requirements,
suggested and mandatory.

OS File Sharing on?



People have different positions on the suitability of mm as a fmsrv, it
is after all just a computer, and much older/lower spec mac's have and
continue to be used.

The real issue, may be considered the hard drive, it is after all a
laptop drive, so the speed and quality is not what a server drive would
normally employ, and with heavy loads, mttf is reduced; it will
possibly/probably/INEVITABLY mechanically fail. The solution , if this
is an issue, is as I understand it, to run the dbs from an external
server grade attached hard drive (currently investigating this).

I have one project employing a mm srv (X.6.4) in a heavy access
situation, and have had one hard drive fail in the last 10 months. I
also use a mm with X.6.2 Server as a development fmsrv.




And can someone put me on the

Shell script executed by a launchd



Chris

On 12/07/10 12:05 PM, 105 wrote:

which of course you already know :-)

On 2010-07-11 20:05:01 -0700, 105 <cortical (AT) internode (DOT) on.net> said:

I wonder if when those servers get rebooted, anyone bothers to shut
down the FM server properly, or if they just reboot the server, kaBAM!

Shutting down the FM server involves flushing the entire cache to disk,
and cleaning up the scraps and tucking in the folds.

If this is not done, and with sufficient time to complete the operation
before the server shutdown, then on reopening, the FM Server has to
perform consistency checks on all hosted files. This alone I've seen
cause all sorts of delays and/or problems with FMServer. Large files
can take hours to finish those checks, people think Server isn't
working, and they do all sorts of things they shouldn't.

This is why FM Server should be on its own machine. Well, one reason.
That way reboots on all your other servers don't impact FM Server.
Rebooting an FM Server for routine maintenance is generally not
necessary. With proper configuration, an FM Server machine can have
uptime in years, not days.

--
Lynn Allen
--
www.semiotics.com
Member FBA
FM 10 Certified Developer

Lynn Allen <lynn (AT) NOT-semiotics (DOT) com> schrub am Mon, 12 Jul 2010
12:45:30 -0700 in comp.databases.filemaker:

Stop wondering, it's the latter.

If I want to include shutting down FMS before rebooting the Windows
2003 Server, could I write a batch file that

- shuts down fms properly
- waits until this is finished
- and then reboots?

I gather from the FTS that the first step line looks like this:

“C:\Program Files\FileMaker\FileMaker Server\Database Server\
fmsadmin” close –t 30 –y

I'm not into servers and networks; can anyone point me to a source
where I get the commands for step 2 and 3?
--
Christoph Kaufmann
http://clk.ch

Christoph L. Kaufmann <clk (AT) tele2 (DOT) ch> wrote:

yes you can !

but consider the disk issue.
You will better have to use an external cabinet with a firewire link and
a self repairing hotswap pair of RAID 0 disks (cost : 250 euros).

With that, you'll have years of uptime and a good security (anyway, have
to do external sécurity copies)
--
Philippe Manet
en fait, c'est manet avant @