FileMaker Pro 6 back-up

[wiredbydufy]

Sorry if this topic has been covered, but I've spent too much time searching through the forum and have yet to find the answer.

Situation:

Running FileMaker Pro 6 (NOT SERVER) on PC (Windows 2000 server) and hosting files with Web Companion on a seperate web server. I need to back-up the FileMaker databases and ideally would like a timed script or executable to pause the databases and copy the databases to a directory that is backed-up by the PC's nightly back-up program

I followed advice from some forum entries that had me create a batch file to launch a database that shut down FileMaker, then copied the files, then launched database scripted to open the files up again... but the batch files do not work properly half the time (i.e. didn't always close the databases or succeed in starting the database to reopen the databases).

Ideally I do not want to shut down anything... pausing the databases to lock out use, and then saving a copy of the open databases to folder would be perfect. As long as it can be run unattended and unpause/start the databases when done.

Appreciate any help.

[Anatoli]

This will always work -- export all records with script and you do not have to shut anything, just trigger the script.

[wiredbydufy]

If I export records I don't think I'm creating a copy of the databases, i.e. relationships, scripts, etc..

Also the solution needs to save a copy of all the databases... typically about 12 are running 24/7.

Is there a standard method for unattended back-up of running Filemaker databases? Isn't there a something like a "pause" command (not pause script) that can pause all database running allowing the database files to be backed up?

[LiveOak]

Exporting records, even in FileMaker Pro format, does not create a copy of your file (layouts, scripts, etc.), only the data.

Unfortunately, the standard method is to use FileMaker Server which includes internal features to pause and backup files.

Practically, almost nothing REALLY needs to be up 24/7. Closing and reopening under programmed control is about your only option.

-bd

[Bob Minteer]

Before I started using Filemaker Server, I was sharing my solution using Filemaker Unlimited on an NT4 server. The tape backup was also on this machine.

I needed to do the same in shutting things down for a period while backing up the databases. The biggest problem I had was making sure that the users were disconnected by backup time. Most of that was handled via personal "social re-engineering" (read as: "I trained them" ;-)).

I used command scripts and Windows scheduler to terminate and restart Filemaker just as you described. Once I had my schedules where I needed them, no problems.

Have you nailed down "why" the scheduled scripts aren't consistent?

Are there other services that are interfering?

In my case, I wanted to minimize downtime as well. I shut down Filemaker, ran a command line WinZip to compress the files and send them to my "archives" folder. I renamed the Zip files for the current date using the 'namedate' command line utility (http://www.cmdtools.com/files/namedate.zip), and then restarted Filemaker. Depending on the number of files you are dealing with, determines how much time you should allocate between termination and re-launch of the solution.

This done, I had Filemaker back online and ready for the occasional midnight hour user before the backup was even ready to start.

I have since upgraded to Filemaker Server on Linux.

regards...

Bob Minteer

[Anatoli]

wiredbydufy said:

If I export records I don't think I'm creating a copy of the databases, i.e. relationships, scripts, etc..

Also the solution needs to save a copy of all the databases... typically about 12 are running 24/7.

Is there a standard method for unattended back-up of running Filemaker databases? Isn't there a something like a "pause" command (not pause script) that can pause all database running allowing the database files to be backed up?

If you created clone and don't tell me you don't have one secure and locked away, then you need just data, nothing more.

RE: unattended back-up

I think the cost of FM server can be justified because of that feature alone. Plus data are protected even when client machine crashes.

[wiredbydufy]

Didn't nail down why the scheduled batch file were inconsistant. If I manually ran each .bat file I had no problem, but when they executed via the scheduler I found that about half the time the databases were not shutting down.... and the rest of the batch commands continued, so I was copying the databases while they were running.

I just took it to be an unreliable method and at that time I made what now seems to be an incorrect assumption that there was a more elegant way to do this.

Other issue is that I found that when I shut down the databases for maintenance reasons then started them again, web companion had a problem connecting, which added to my concern about this method of shutting down the databases then starting them again.

With FileMaker 3 I remember YEARS ago writing a DOS command to PAUSE the database... can't do that in DOS now cause the FileMaker Pro 6 executable has a space in the name.

--Bob

[Anatoli]

RE: PAUSE the database

You can Pause the databases on FM server and I am doing that and starting and closing, anything.

RE: I found that about half the time the databases were not shutting down.

With BAT file you should just open another FM file which will autoexec script with Exit Application.

Then do anything you need.

Then call FM file with autostart script, which will open all files.

We are using that for 4 years without problem.