Hi Matt, I was worried about a hardware problem. As you say, either the TM disk or the system disk could be failing. Both are very new (3-TB Seagates).
I have not yet looked for information in the Console app, but unless it's very obvious, I probably won't recognize a problem even if it's there. Thanks, Gregg On 7 Mar 2012, at 1:03 PM, Matt Penna wrote: > Greg, > > Is it possible you have a hardware problem? Perhaps the TM disk or the source > disk is failing, and the backup is taking so long because of difficulties > reading or writing files. > > Is there any useful information in the Console app? > > The only time I've seen TM consistently take this long is on PPC hardware > running 10.5. > > -Matt > > On Mar 7, 2012, at 12:46 PM, "Dinse, Gregg (NIH/NIEHS) [E]" > <di...@niehs.nih.gov> wrote: > >> Both machines use an internal hard drive for the TM backups. Both TM backup >> drives still have a lot of empty space, though the TM drive at home is >> larger than the TM drive at work. >> >> I certainly have a few files at home that are larger than those at work, >> such as videos, but I exclude the Movies, Music, and Pictures directories >> from my TM backups, so that should not be the problem. >> >> Any other thoughts? >> >> Gregg >> >> On 7 Mar 2012, at 12:36 PM, objectwerks inc wrote: >> >>> How big are your data sets (how full with how much data are your disks)? >>> Is the one at home using a local TM disk or a TM disk on your network? Is >>> the data set composed of LOTS of little files? >>> >>> On Mar 7, 2012, at 10:07 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote: >>> >>>> Hi, >>>> >>>> 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? >>>> >>>> Thanks, >>>> >>>> Gregg _______________________________________________ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
