<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Triad of Server</title>
	<atom:link href="http://fmcollective.com/2007/05/16/the-triad-of-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://fmcollective.com/2007/05/16/the-triad-of-server/</link>
	<description>Syndicating the best FileMaker blogs</description>
	<lastBuildDate>Sat, 29 Nov 2008 04:44:04 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Russell</title>
		<link>http://fmcollective.com/2007/05/16/the-triad-of-server/comment-page-1/#comment-40</link>
		<dc:creator>Rob Russell</dc:creator>
		<pubDate>Thu, 17 May 2007 19:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://fmcollective.proofgroup.com/?p=28#comment-40</guid>
		<description>SHB said:

&gt; For a deployment to be successful, three keys parts must be 
&gt; properly configured and designed as well as properly aligned 
&gt; with one another:

&gt; •The Server hardware and operating system,
&gt; •The FileMaker Server services/daemons, and,
&gt; •The developer designed FileMaker Pro solution.

May I venture that there is a fourth that is sort of implied by (and relies upon) the first two but should always be explicitly called out:

• A well designed back up and restore procedure.

I am constantly amazed by the number of Server installs I come across that do not have a decent (sometimes any) backup procedure.

First port of call is Wim&#039;s other paper &quot;Backups, Backups, More Backups&quot;. Read it, read it and apply it.

Rob
</description>
		<content:encoded><![CDATA[<p>SHB said:</p>
<p>> For a deployment to be successful, three keys parts must be<br />
> properly configured and designed as well as properly aligned<br />
> with one another:</p>
<p>> •The Server hardware and operating system,<br />
> •The FileMaker Server services/daemons, and,<br />
> •The developer designed FileMaker Pro solution.</p>
<p>May I venture that there is a fourth that is sort of implied by (and relies upon) the first two but should always be explicitly called out:</p>
<p>• A well designed back up and restore procedure.</p>
<p>I am constantly amazed by the number of Server installs I come across that do not have a decent (sometimes any) backup procedure.</p>
<p>First port of call is Wim&#8217;s other paper &#8220;Backups, Backups, More Backups&#8221;. Read it, read it and apply it.</p>
<p>Rob</p>
]]></content:encoded>
	</item>
</channel>
</rss>
