 | |
Warning on shared directory
comp.databases.filemaker comp.databases.filemaker
 |
| | Thread Tools | Display Modes |
#41
 
| |||
| |||
|
Re: Warning on shared directory -
01-12-2011
, 06:19 PM
|
"Your Name" <your.name (AT) isp (DOT) com> writes: You've been told the "better way" numerous times, but choose not to do that ... there's little point in bothering to continue with this topic since you aren't going to listen and simply do whatver you want anyway. Helpful Harry  )The backup has nothing to do with the filemaker open remote thing... Am I wrong? I meant what is a better way to backup data safely. |
As I said before, store the database file locally and then use a shutdown
script to copy the closed file to the filesaerver for backup.
Helpful Harry
)
#42
| |||
| |||
|
|
The backup has nothing to do with the filemaker open remote thing... Am I wrong? I meant what is a better way to backup data safely. Yep, use FileMaker properly and then you can back it up properly. As I said before, store the database file locally and then use a shutdown script to copy the closed file to the filesaerver for backup. Helpful Harry ) |
could not backup my database?
That would be probably more stupid than doing a snapshot on the open
database, isn't there a way to freeze the database while it's open?
#43
| |||
| |||
|
|
your.name (AT) isp (DOT) com (Your Name) writes: The backup has nothing to do with the filemaker open remote thing... Am I wrong? I meant what is a better way to backup data safely. Yep, use FileMaker properly and then you can back it up properly. As I said before, store the database file locally and then use a shutdown script to copy the closed file to the filesaerver for backup. Helpful Harry )So you're saying that for the whole day (while the database is open) I could not backup my database? That would be probably more stupid than doing a snapshot on the open database, isn't there a way to freeze the database while it's open? |
You've been ignoring all the best advice here. If you want to properly
share FileMaker databases, than you will host them using FileMaker
Server, which also provides built-in backup schedules.
If you insist on sharing the databases peer-to-peer, you will need to
jerry-rig something. Harry's suggestion on scripting it on file close
was one good suggestion. If you want more frequent backups, then you
need to script it differently. One way would be to use the timed script
triggers in FM 10 and 11 to perform the save that Harry suggested on a
more frequent, timed basis. Another way would be to use a robot machine
to open the database on a schedule (Windows script scheduler, or Cron on
Mac) and to perform the same 'save as' that Harry suggests.
Even though you insist on doing things your way, there are still ways to
work around it. But, yes, they require a little extra work!
#44
| |||
| |||
|
|
Mac) and to perform the same 'save as' that Harry suggests. |
launchd on mac; Cron is deprecated
#45
| |||
| |||
|
|
Luckily I don't use it, I just administer that network. |
you are playing with their job.
PLEASE administer FMP as FMP tells you to do, not as you, very young and
irresponsible "sysadm" think it could be.
FMP has tens of years of experiment of data processing over all kinds of
systems, and they knows of thousands of catastrophes like the ones you
are preparing.
--
Philippe Manet
en fait, c'est manet avant @
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.