On Mar 7, 2012, at 7:24 PM, Macs R We wrote:
> On Mar 7, 2012, at 10:07 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote:
>
>> On my Mac Pro at home, Time Machine runs for about 30 minutes of each hour,
>> even when I have not created any new files. I also have a Mac Pro at work
>> and it does NOT exhibit this behavior. Both are running the latest version
>> of Snow Leopard (10.6.8). Does anyone have an idea about why Time Machine
>> is running so much on one of these? I expect Time Machine to run for a
>> short period (maybe a minute or two), even without many files changing,
>> since I assume it still has to search for possible changes, but 25-30
>> minutes seems really excessive when nothing much has changed. Any thoughts?
>
> Do you have any large SQL databases (e.g., MailSteward)? I discovered that
> just SEARCHING an SQL database marks the entire dataset as "modified" and to
> be backed up.
If you are backing up running databases (of most any flavor) with
TimeMachine then you are almost certainly doing it wrong. There is a
not-small-enough chance that you will get a corrupt file out of your backup.
And bad backups are worse than no backups.
Internally I am sure that that database has timestamps telling when
each table or database (and in some cases records) were last modified, and have
methods/systems to back them up. Use those methods/systems. Yes it is probably
more work to setup, but it is the right thing to do.
--
Karl Kuehn
[email protected]
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk
