[FX.php List] one machine intallation

[Bob Patin]

I listened to an interesting webcast from FMI last night, about best  
practices with FileMaker Server & Server Advanced.

The tech talked a lot about using RAIDs, backups, and other things,  
but the interesting thing that he said was that it's "best practice  
NOT to change layouts or field definitions on a database that's  
hosted on FM Server. Instead, he said that FMI considers it best  
practice to use an offline copy of the database, make all changes,  
then put it on FM Server.

While I can understand that a loss of connection might damage a  
database that's being edited when the connection fails, I've edited  
hosted database a hundred times, and can't imagine trying to work any  
other way...

He also talked about backing up to network drives, and from the way  
that he talked, he didn't seem to know that FM Server on OS X doesn't  
allow backing up to external drives or drives other than the system  
drive...

Bob Patin
Longterm Solutions
bob at longtermsolutions.com
615-333-6858
http://www.longtermsolutions.com

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: tech at longtermsolutions.com
      ICQ: 159333060



On Apr 25, 2007, at 5:51 PM, Kevin Futter wrote:

> On 25/4/07 1:15 AM, "Jonathan Schwartz" <jonathan at exit445.com> wrote:
>
>> Thank you!  Now *this* makes sense.
>>
>> Jonathan
>>
>>
>> At 9:48 AM -0500 4/24/07, Bob Patin wrote:
>>>
>>>
>>> 2) I asked about web servers; as I suspected, he confirmed that the
>>> speed bottleneck with FMSA and a web application is in WPE, where
>>> the PHP code is interpolated (not sure if that would be the correct
>>> term) into XML. So logically, the machine running WPE needs to be as
>>> fast as possible.
>>>
>>> He also opined that the best place to put WPE is on the web server.
>>> This makes sense, since it leaves the FMSA machine free to deal
>>> solely with FileMaker tasks; since FMSA does all the
>>> number-crunching, as opposed to earlier versions of FM Server, it
>>> makes sense to leave it by itself to handle FileMaker-related tasks.
>>>
>
> It's more-or-less the same as what we do - FMSA on one Xserve and  
> WPE on the
> webserver (another Xserve). If you have the infrastructure to  
> support it,
> it's definitely the most efficacious solution.
>
> -- 
> Kevin Futter
> Webmaster, St. Bernard's College
> http://www.sbc.melb.catholic.edu.au/
>
>
>
> ###################################################################### 
> ###############
> This e-mail message has been scanned for Viruses and Content and  
> cleared
> by MailMarshal
> ###################################################################### 
> ###############
>
> This e-mail and any attachments may be confidential. You must not  
> disclose or use the information in this e-mail if you are not the  
> intended recipient. If you have received this e-mail in error,  
> please notify us immediately and delete the e-mail and all copies.  
> The College does not guarantee that this e-mail is virus or error  
> free.  The attached files are provided and may only be used on the  
> basis that the user assumes all responsibility for any loss, damage  
> or consequence resulting directly or indirectly from the use of the  
> attached files, whether caused by the negligence of the sender or  
> not. The content and opinions in this e-mail are not necessarily  
> those of the College.
>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list