Hi Arif, I'd like to add to Walt's response, which seems to be the standard method for keeping local backups.
I use a slightly different approach, which I prefer because it gives me immediate access to backup files without unzipping or unstuffing. When I copy a backup (we use FMPServer and have automated backups run at regular intervals during the day), I also rename the files. This can be done with a DOS batch file or with AppleScript on the Mac. I prefer to rename the extension. For example, "names.100" becomes "names.10B" or whatever. Since FileMaker locates files by name, they are safe, yet are very accessible when needed. I do development, so often need only one file rather than the entire set. This system makes it very easy. Gary > Subject: RE: a follow up to my "odd win2k question" > From: "Walt Daniels" <[EMAIL PROTECTED]> > Date: Mon, 24 Sep 2001 12:00:55 -0400 > X-Message-Number: 4 > > It is not safe to have any .10x files on any drive that is visible to the > machine that is going to serve the files to other machines. The easiest > solution is to never copy .10x files for backup but to zip them instead. > Running FMP Sever has fewer restrictions as it only opens files in a > certain > directory or one level down from that directory. Alternately you can put > backups on drives that are not network accessible, but that is highly > dependent on the details of your backup mechanism. Put them on a drive > that > is not normally shared. Then when you shutdown FM to do the backup, share > the backup drive, do the backup and unshare the drive. > > > -----Original Message----- > > From: Arif Mamdani [mailto:[EMAIL PROTECTED]] > > Sent: Sunday, September 23, 2001 3:15 AM > > To: TechRocks Support > > Subject: [support] a follow up to my "odd win2k question" > > > > > > Okay, so I figured out what was happening -- and this is weird! > > The Windows > > 2000 machine in question lives on a network. On this network is a > server > > that houses the organization's files. The Win2k box in question > > was opening > > Ebase, but not from cached copies, nor from local copies as I and > > others had > > suspected, but was instead being very precocious in that it was loading > > Ebase from a backup stored on the network drive! > > > > By manually redirecting Filemaker to look on the local drive, and _then_ > > hitting the hosts button, we can open Ebase correctly from the machine > > that's serving it. But every time we restart Filemaker, it's back to > > looking at the backup. Now the obvious solution is to remove the > back/do > > the backup elsewhere, but i'm reluctant to do that, as that to some > degree > > defeats the idea of having a server that's backed up. So, if > > anyone has any > > ideas on how to have this organization continue to use their network as > a > > place to park files till they're backed up onto some other media > > while also keeping this one Win2k machine from trying to open the > backups, > > I'd love to hear them. > > > > thanks, > > -arif > > -- > > Arif Mamdani > > Circuit Rider > > LINC Project -- Welfare Law Center > > www.lincproject.org www.welfarelaw.org > > p: 212.633.6967 > ------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
