![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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, |
#3
| |||
| |||
|
|
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? |
#4
| |||
| |||
|
|
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. |
#5
| |||
| |||
|
|
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. |
#6
| |||
| |||
|
|
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? |
![]() |
| Thread Tools | |
| Display Modes | |
| |