dbTalk Databases Forums  

Backing up open files

comp.databases.filemaker comp.databases.filemaker


Discuss Backing up open files in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
bilbod
 
Posts: n/a

Default Backing up open files - 11-09-2009 , 10:14 PM






Hello,
I've got users running an automated backup that makes one zip file of
the solution. It's in FM5 on current windows platforms, mostly XP &
Vista. Until now, I've been reluctant to have the zip backup routine
run automatically because I thought it was important the files be
closed, so the system wouldn't get confused between open and closed
files to archive. Now I'm wondering if that is necessary best
practice. Any thoughts?
Thanks,
Bill

Reply With Quote
  #2  
Old   
105
 
Posts: n/a

Default Re: Backing up open files - 11-10-2009 , 12:05 AM






bilbod wrote:
Quote:
Hello,
I've got users running an automated backup that makes one zip file of
the solution. It's in FM5 on current windows platforms, mostly XP &
Vista. Until now, I've been reluctant to have the zip backup routine
run automatically because I thought it was important the files be
closed,
it is; re flushing cache...
maintain your reluctance.

Reply With Quote
  #3  
Old   
Howard Schlossberg
 
Posts: n/a

Default Re: Backing up open files - 11-10-2009 , 11:06 AM



bilbod wrote:
Quote:
Hello,
I've got users running an automated backup that makes one zip file of
the solution. It's in FM5 on current windows platforms, mostly XP &
Vista. Until now, I've been reluctant to have the zip backup routine
run automatically because I thought it was important the files be
closed, so the system wouldn't get confused between open and closed
files to archive. Now I'm wondering if that is necessary best
practice. Any thoughts?
You should absolutely, positively not copy, zip, virus scan, or
otherwise apply external influence to any live, open database files.

If you have more than, say, three users, you should probably be hosting
the files from FileMaker Server, which includes scheduled backups of
live files (it pauses the data service while the files are backing up).

If you don't have FM Server, then whichever machine is acting as host
should run a "save files as...copy" script step and then the zip files
can be made from those copies. Guests of a multi-user file are not able
to use the "save as" command; only the host can.

Reply With Quote
  #4  
Old   
bilbod
 
Posts: n/a

Default Re: Backing up open files - 11-10-2009 , 01:55 PM



Thanks everyone,
I'd have to have a pretty thick skull to miss the intent of the
responses!
Bill
On Nov 10, 10:06*am, Howard Schlossberg
<how... (AT) nospam (DOT) fmprosolutions.com> wrote:
Quote:
bilbod wrote:
Hello,
I've got users running an automated backup that makes one zip file of
the solution. It's in FM5 on current windows platforms, mostly XP &
Vista. Until now, I've been reluctant to have the zip backup routine
run automatically because I thought it was important the files be
closed, so the system wouldn't get confused between open and closed
files to archive. Now I'm wondering if that is necessary best
practice. Any thoughts?

You should absolutely, positively not copy, zip, virus scan, or
otherwise apply external influence to any live, open database files.

If you have more than, say, three users, you should probably be hosting
the files from FileMaker Server, which includes scheduled backups of
live files (it pauses the data service while the files are backing up).

If you don't have FM Server, then whichever machine is acting as host
should run a "save files as...copy" script step and then the zip files
can be made from those copies. *Guests of a multi-user file are not able
to use the "save as" command; only the host can.

Reply With Quote
  #5  
Old   
105
 
Posts: n/a

Default Re: Backing up open files - 11-10-2009 , 03:57 PM



Howard Schlossberg wrote:
Quote:
bilbod wrote:
Hello,
I've got users running an automated backup that makes one zip file of
the solution. It's in FM5 on current windows platforms, mostly XP &
Vista. Until now, I've been reluctant to have the zip backup routine
run automatically because I thought it was important the files be
closed, so the system wouldn't get confused between open and closed
files to archive. Now I'm wondering if that is necessary best
practice. Any thoughts?

You should absolutely, positively not copy, zip, virus scan, or
otherwise apply external influence to any live, open database files.

If you have more than, say, three users, you should probably be hosting
the files from FileMaker Server, which includes scheduled backups of
live files (it pauses the data service while the files are backing up).

If you don't have FM Server, then whichever machine is acting as host
should run a "save files as...copy" script step and then the zip files
can be made from those copies. Guests of a multi-user file are not able
to use the "save as" command; only the host can.
Hi Howard

re save as copy
there was discussion of this in another forum some months ago, and the
strongly expressed position was that this was a very bad idea, was a
source of potential corruption, and that even FM had subsequently
advised against it (no reference). In short, never use save as copy.
This from a well known FM dev. Which is very inconvenient if true.

Having to quit FM in order to do a 'safe' copy is tedious. Thoughts?

Reply With Quote
  #6  
Old   
bilbod
 
Posts: n/a

Default Re: Backing up open files - 11-10-2009 , 06:33 PM



I've been using a Save as Copy routine for a long time. Whenever I've
needed to restore a user's file
I've just renamed the copy to the correct name for the fileset in use.
It's never given me a problem.
I'm having that run when they close the solution, but, they don't
always close each day. That's why
I turned to the free Cobian Backup. And finally, one important file
wouldn't Save as Copy.
Bill
Quote:
Hi Howard

re save as copy
there was discussion of this in another forum some months ago, and the
strongly expressed *position was that this was a very bad idea, was a
source of potential corruption, and that *even FM had subsequently
advised against it (no reference). In short, never use save as copy.
This from a well known FM dev. Which is very inconvenient if true.

Having to quit FM in order to do a 'safe' copy is tedious. Thoughts?

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.