This is getting offtopic for Yojimbo so I won't continue past this
email. I appreciate your comments Jan and I do understand the issue of
data of data consistency.  The only way to completely avoid that is to
take the system completely down for backup and either run the backup
in single user mode or better yet, run the backup in target disk mode
without even the OS running.  But I won't do that because of
convenience nor will most other users. I don't ever close applications
or log off my machine unless a software update forces me to and I
suspect there are many more like me. Most people don't backup because
it's inconvenient which is one of the main things that Apple was
trying to address with Time Machine. Time Machine also has the added
advantage of provided checkpoints throughout the day that you can
roll-back to (at least for specific files).  I'd much rather take the
very small chance of data inconsistency than accept the inconvenience
of offline backups.

Now to get it back to Yojimbo so we're not completely off topic ;-) If
Yojimbo stored records as separate files and kept metadata and/or
index data in smaller DBs then the backup regime would only have to
backup those files that had changed instead of the entire xxxMB
sqllite file that Yojimbo uses now. I believe that would decrease the
risk of inconsistency as opposed to the case now, where Yojimbo could
write the the large database file while the backup is trying to copy
it.

And finally, once users get used to the power of Time Machine's
rollback capability, they'll demand it.  There are several times I
wish I could have rolled back a Yojimbo record (this is exacerbated by
Yojimbo's lack of read-only records which has allowed me to
accidentally edit Yojimbo data that I didn't intend to).

Cheers,
Rhet

On 2/15/08, Jan Erik Moström <[EMAIL PROTECTED]> wrote:
> Rhet Turnbull <[EMAIL PROTECTED]> 08-02-14 15.58
>
>
>  >I would never use a backup solution that didn't run on live data.
>  >Thankfully the days of "they system is down for backup" are long gone.
>  >Whether I use Time Machine or I use Super Duper or Chronosync or
>  >something else, I'm certainly not about to take my machine offline or
>  >logout to do the backup.
>
>
> Your misunderstanding me, if you run a backup on a programs data
>  file (without the applications talking to each other) you always
>  run the risk of inconsistent data (unless you have a filesystem
>  that does some fancy stuff). For example, if you have an
>  application with several files that in some way depend on each
>  other - for example a database that store data as individual
>  files and then have an index file to keep track of them - there
>  is always the chance that the backup is done between the
>  modification of the individual files which would make the data
>  in the backup inconsistent.
>
>  So while I'm running TM for my whole disk, I'm also running a
>  second program for applications that is constantly running like
>  my email program.
>
>
>
>                              jem
>  --
>  Jan Erik Moström, www.mostrom.pp.se
>
>
>  --
>  ------------------------------------------------------------------
>
> This message is sent to you because you are subscribed to
>   the mailing list <yojimbo-talk@barebones.com>.
>  To unsubscribe, send mail to: <[EMAIL PROTECTED]>
>  List archives:  <http://www.listsearch.com/yojimbotalk.lasso>
>  Have a feature request, or not sure if the software's working
>  correctly? Please send mail to: <[EMAIL PROTECTED]>
>

--
------------------------------------------------------------------
This message is sent to you because you are subscribed to
  the mailing list <yojimbo-talk@barebones.com>.
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
List archives:  <http://www.listsearch.com/yojimbotalk.lasso>
Have a feature request, or not sure if the software's working
correctly? Please send mail to: <[EMAIL PROTECTED]>

Reply via email to