On 09/03/2012, at 11:41 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote:
> Why does it make 2 passes?
I believe TM makes two passes because it is trying to capture a snapshot of the
files, but some of the files may have changed, been open, or not been created
since the backup started. So TM assumes if
As suggested, I looked at the console logs (searching on "backupd"). No wonder
it seems like TimeMachine is always running. It took 41 minutes to backup
about 40 MB. It does this every hour, so it's running for 41 minutes and
resting for 19 minutes. It sure seems to backup a lot of files, co
Thanks for the suggestion. I will try this when I get home.
I tried this at work, just to see what it looked like. I was surprised to see
that it claimed to backup 43,000 files, though it only took 2-MB of space.
That's an order of magnitude more than the 4,500 files in your output. Also,
i
On Mar 7, 2012, at 8:46 PM, Karl Kuehn 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.
>> Do you have any large SQL databases (e.g., MailSteward)? I discovered that
>> just SEARCHING an SQL database marks
On 07 Mar 2012, at 21:08 , Dinse, Gregg (NIH/NIEHS) [E] wrote:
> I am not knowingly running any databases. Is there an easy way to tell?
I think you need to open up console and in the search field type 'backupd'
You should see blocks like this about every hour:
07-Mar-12 11:06:23.090 PM com.app
I am not knowingly running any databases. Is there an easy way to tell?
How much of my system drive should I exclude from TimeMachine? I certainly
want to backup my home directory, but should I exclude /Applications,
/Developer, /Library, or /System?
Gregg
On Mar 7, 2012, at 10:46 PM, Karl K
Did you ever play with this thing?
http://smartcardservices.macosforge.org/trac/wiki/smartcardccid
On Mar 7, 2012, at 8:36 PM, Dinse, Gregg (NIH/NIEHS) [E] wrote:
> Hi,
>
> I do not know of any large (or small) SQL databases.
>
> I just opened the Console app and found one message repeating i
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 exhib
Hi,
I do not know of any large (or small) SQL databases.
I just opened the Console app and found one message repeating itself every
second. There were thousands of copies of the same message, but I have no idea
if it's related to the TM problem. The messages said:
3/7/12 10:30:40 PM com
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 versi
Hi Chad,
Both the TM drive and the source drive are 3-TB. I am not at home right now,
but I'm pretty sure that both have more than 2-TB of free space. Even if the
source drive has 1-TB of files, I bet that more than 500-GB are excluded (due
to not backing up Movies, Music, Pictures), so my gu
On Mar 7, 2012, at 10:46 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote:
> Both machines use an internal hard drive for the TM backups.
Ok. I do TM to a network server over both Wifi and a wired ethernet. The wired
ethernet is much faster to back up the same amount of data. So it was one area
to exp
Thanks for confirming that you had the same problem, and that it was a disk
failure in progress. I think the first thing I'll try is to replace the TM
drive and see if this all clears up. Thanks,
Gregg
On 7 Mar 2012, at 2:49 PM, Nathan Sims wrote:
> Check your system and console logs. This h
Check your system and console logs. This happened to me, too, where TM would
run and run and run. It turned out to be a disk failure in progress (on the TM
drive). Unfortunately for me, it was too late to save any of the data on the
drive.
On Mar 7, 2012, at 11:06 AM, Dinse, Gregg (NIH/NIEHS)
Hi Mike,
I looked at the Activity Monitor and I forget the name of the process, but it
looked like one that I thought was associated with backups, so I did not notice
anything unusual.
I'm pretty sure the CPU is not overloaded and that the memory is not used up.
Both the TM disk and the system
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 the
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 Mar 7, 2012, at 11:46 AM, Dinse, Gregg (NIH/NIEHS) [E] wrote:
> Any other thoughts?
I would fire up Activity Monitor and see what's going on. Is it actually doing
much reading/writing to the drives? Is the CPU overloaded (unlikely)? Is all of
your memory being used so it has to keep hitting
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
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,
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 Ti
21 matches
Mail list logo
