Re: using FSevents for backup - is it reliable enough?
Re: using FSevents for backup - is it reliable enough?
- Subject: Re: using FSevents for backup - is it reliable enough?
- From: James Bucanek <email@hidden>
- Date: Wed, 19 Jan 2011 09:37:11 -0700
Stanley Sieler <mailto:email@hidden> wrote (Wednesday, January
19, 2011 1:28 AM -0800):
Re:
These may have been excluded by the applications that created them. Can't say for sure.
/Users/sieler/Library/Icons/WebpageIcons.db
I'd have expected such exclusions to be via metadata files (like the ones
below :) ... I'm somewhat disappointed that there appears to be some other
mechanism to implement the TM exclusion. (In general, I prefer
exclusions/metadata to be 'near" an object (like via dot-underbar files)
instead of "away" from an object (like in a database) ... it's almost always a
safer/stronger approach than application-specific dbs tracking files.)
Stanley,
I don't think it matters. The two API functions for excluding
items from a backup (CSBackupIsItemExluded and
CSBackupSetItemExcluded) are both "near" in that operate on the
URL of the item. Whether the information for maintaining this
property is "near" (i.e. an extended attribute) or "far" (an OS
X database hidden on the volume) is an implementation detail--as
long as it's reliable, of course.
I should have clarified that I expected a "they're excluded" answer ... and that I'm mostly fine with that.
They're excluded. (feel better?)
Time Machine has specific folders that it always ignores (cache,
temporary, VM, ...) and you can programatically set any item to
be excluded using the Backup Core API. Xcode, for example, uses
CSBaeckupSetItemExcluded to exclude the build folder of its projects.
--
James Bucanek
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden