Since installing Lion why does Time Machine shows backup was delayed?

Ever since we stalled Lion after we backup with Time Machine the display quickly changes to the alert symbol that backup was delayed how can I change this. I have backed up four times.

It's a 'new feature' .. check out this post here https://discussions.apple.com/message/16148789#16148789 .. if you don't agree with this new feature, please join us in raising it as a bug for Apple to fix.

Similar Messages

Why does time machine show the backup failed

The time machine icon in the menu bar keeps showing up with a "!" in the middle of it, which is suppose to mean the back up failed.
Yet when I go to System Preference, it shows the backup succeeded.
The menu bar shows the last successful back up was on Sept 13.
System Preferences shows the last successful backup was an hour ago. (15 Sept.)
How do I get these two to agree with each other?
Rebooting the computer doesn't seem to help.
I'm running 10.9.4 now.

LonerT:
Thanks for looking at the HomeSharing problem
I have three discussions open that are related. The first one shows that the ATV appears to open the extra DAAP connections, which in turn appears to be related to Homesharing problem.
Airport opens multiple DAAP connections
Numerous ATV DAAP ports to MacBook Pro
Cannot turn off Homesharing to AppleTV: IPv6 connections remain
This one (not mine) points at the Bonjour Sleep Proxy Service as being involved in the DAAP problem.
DHCP conflicts between AppleTV and Airport Extreme repeater
And this is the "other side" of the problem, which I have also experienced
Apple TV homesharing keeps dropping out ...
I note that my AppleTV started out with a DHCP address of 10.0.1.16, it jumped to 10.0.1.20 and then migrated up, one address at a time, to 10.0.1.25.
Given the number of systems I have on my subnet, if they are handed out in order, and given that I just moved from 192.168.1.0/24 private space, the highest address should be around 12.
I have two Apple TVs. One on Wireless remote from the ATX and connected to an Airport Express and one connected via ethernet directly to the AEX. I don't use the remote one. It should not have been turned on (activated) for at least two weeks, yet the AEX is still sending out ARP requests for the last IP address that it had and my laptop still associates the AEX MAC with the last address assigned to the remote ATV.

Since installing mavericks my WD time machine doesn't work, it keeps insisting it needs more space? This wasn't an issue an hour earlier?

Since installing mavericks my WD time machine doesn't work, it keeps insisting it needs more space? This wasn't an issue an hour earlier?
Id also like to know if Powerpc software will be supported? I have C&C Generals on disc but it doesnt run now mavericks is installed?!
Annoying!

Regarding time machine, it probably took a full backup after you put mavericks on. To investigate, open Console, select "All Messages" and type "backup" (without the quotes). It will then only show you backup-related messages. If you're not sure how to read those, copy them and paste them into a reply here; we can investigate the situation.
I don't know anything about your PPC software issue, sorry.

Why is Time machine saying backup disk disconnected? Using MBP 17" Lion 10.7

Why is Time machine saying backup disk disconnected? Using MBP 17" Lion 10.7

Do you have an external drive connected?
If you do has it gone into sleep mode? There is a setting in the OS to put drives to sleep if they aren't being used. Energy Saver "Put the hard disk to sleep when possible".
Also most external drives have a built in sleep function that if they aren't being accessed for a period of time they go to sleep by themselves.

Why does Time Machine disappear?

Why does Time Machine disappear each restart?

Suggest that you power cycle the entire network, as things are likely out of sequence
Power every device off on the network, order is not important
Wait a few moments, then start the modem first and let it run by itself for 2-3 minutes
Start the Time Capsule the same way
Start each network device one at a time about a minute apart
Check for proper operation

Why does time machine make a second/different backup after new installing a hard drive?

Hi all,
Long time reader, first time poster...
after having to install a new hard drive on my MacBook Pro, the new Time Machine backups are not recognising the original/older backups on the external hard drive connected via network router and has created a new/second backup caller 'xxx Mac Book Pro 1' instead of updating/reading the orginal 'xxx Mac Book Pro backup'?
Does anyone know why it did this? and more importantly how do i make it recgonise the original and stop making the secondary copy?
Thanks!

Hi gb69,
If you are having issues with Time Machine backups after a recent hardware change, you may find the following article helpful:
Time Machine: Troubleshooting backup issues
http://support.apple.com/kb/ht3275
Regards,
- Brenden

Why does Time Machine Hang OSX when a USB drive does not respond?

I use USB drives to store photo data. When I back up the drives using Time Machine to a Time Capsule, If I have added a large amount of data to the USB drive, the backup will consistently fail with the drive hung. I can see the drive in finder, but I cannot see the directory structure. Often OSX hangs too and I cannot even get to finder, just the whirling colored wheel. Sometimes the system has entered sleep mode and it will not wake up. I if I am using the monitor, I can open the MAC Book Pro cover and the screen there shows alternately, a blue screen and the screen wallpaper, flipping back and forth but otherwise unresponsive. If I turn the USB drive off the OS recovers and Time Machine completes, usually indicating a backup failure (but not always). The drive is always very hot under these circumstances, indicating that the system is issuing repetitive operations to the drive. I should emphasize that I am not writing to the USB drives during backup, Time Machine is just reading the drive. So several questions:
1) How in the world can a non system drive hang the Operating System? This is a big no-no for a supposedly multi-tasking Operating System.
2) I use Aperture 2.1 to store data on the USB drives with no problems (at least so far). Why would Time Machine drive the USB drive so hard that it fails? I had the same problem using a USB drive with iTunes. It completely fried the drive by writing to it too intensively during one of the frequent software updates. Is there no throttle mechanism in OSX that limits the disc activity so that the throttle mechanism is not the failure of the drive itself?
3) Does Apple have a list of USB drives that it has validated to be able to work with it's system reliably?

Are the USB drives powered from the computer or do they have their own power supplies.
There is a limit to how much power can be drawn from each USB port and also a total limit. If you exceed this, unexpected things can happen.

Why does Time Machine run continually?

I moved from Snow Leopard to Lion last week, and also converted my MobileMe account to iCloud. It has now been seven days and Time Machine appears to have never stopped backing up. To be more precise, it appears that as soon as it completes one back up, it immediately starts on a new one. My Time Machine drive is an external 750 GB connected by FW800. Time Machine estimates the size of a full backup at 132.66 GB. The Bootcamp partition on my 320 GB internal drive and the external Time Machine drive are excluded from the backups. Looking at the Star Wars screen in Time Machine shows that it has made two backups per day since the move, so I don't think it is still making the initial full back up due to the OS upgrade.
Is this normal? If not, what may be causing Time Machine to run continually? It did not behave in this way with Snow Leopard and previous versions of OS X.
Thanks for any advice.

Hi, and welcome to the forums.
It sounds like you may have either or both of the following:
Your backups are too large. Something is being backed-up often, or every time, that is taking a lot of time and disk space. See #D4 in the Time Machine - Troubleshooting *User Tip* at the top of this forum.
Your backups are running too slowly, for one or more reasons. See #D2 in the Troubleshooting Tip.

Does Time Machine fully backup iPhoto 09 photos, events, faces, etc.? Mtn Lion

I'm going to the Apple store this afternoon. I believe I'll end up reinstalling the system and need to be sure everything is backed up.
Problem is iPhoto 09 (yep, I have an OLD version). It's going nuts - making sounds like a fast, loud, constant drumbeat, flashing, won't let me do anything except force quit.
I backup to Time Machine /external drive automatically and it seems to be backing up iPhoto. I don't want to open the iPhoto program from Time Machine to check since I'm afraid it might be something in the computer that could screw it up. I have thousands of phtoos in iPhoto and don't want to lose them.
Since the external drive I'm using wth Time Machine shows a backup today including iPhoto, should I feel comfortable that iPhoto is backed up appropriately, or do I need to back it up in some other way?

Besides Time Machine, you could use a cloning program.
Clone - Carbon Copy Cloner
Clone - SuperDuper

Why does Time Machine folder sizes exceed physical capacity?

I have a MAC G3 Server Serving multiple MACs as a Storage, Media Server, and Time Machine storage. These other external MACs are all running Version 10.8.3. Only the Storage server is running 10.5.8.
All of the extenal Macs use Time Machine to backup to the served Storage media volume called "Time Machine".
The physical size of the "Time Machine" volume is 2.0 TB.
Yet when I am on the G3 Server, and perform a "Get Info" on the "Time Machine" volume, and also the folder that contains the Server's backups, the stored capacities exceed the physical capacity of the drive to which the volume resides.
The single physical drive is 2.0 GB and only has one partition called "Time Machine". In the root directory of this volume there is the one folder called Backups.backupdb, and a .sparsebundle DMG file for each of the remote systems that are bing backed up by Time Machine.
Each of the sparsebundles are well below the dirve's physical capacity, but both the local server's backup folder (Backups.backupdb) and the G3 server's local volume "Time Machine" show a used capcity that well exceeds the physical capacity of the drive on which it resides.
For example, here is the information from "Get Info" on the Backups.backupdb folder on the "Time Machine" volume when viewed from all systems:
Kind: Folder
Size: 3,456,930,478,415 bytes (3.46 TB on disk) for 122,254 items
But the Physical Volume "Get Info" shows this:
Kind: Volume
Capacity: 2.0 TB
Available: 169.92 GB
Used: 3,456,930,478,415 bytes (3.46 TB on disk) for 122,254 items
(NOTE: this is identical to the size
My guess is that there is some sort of deduplication involved.
If so, I would like to know the type of deduplication is performed?
Is it File Level deduplication, Block Level, or Content Level?
Also, is the deduplication inhererant on the volume (File System) level, or only specifically for Time Machine, via symbolic links?
Thank you in advance.
Jeff Cameron

This is due to the way Time Machine stores files. While there is only one copy of each version of each file stored, there are multple links to that file, and each link is reported in Get Info at its restored size.
How Time Machine Works its Magic

Why does time machine close open applications? eg firefox, mail ...

since the latest update of time machine, a few days/weeks ago (sorry i can't be more precise), it seems that open applications close themselves. i've tried disabling time machine, and then all stay open, for hours ... so i'm blaming time machine.
i don't think this used to happen! applications close normally - at least i don't get error messages when i reopen them.
am i confused?

Hello tim:
Welcome to Apple discussions.
As far as I know, the regular TM backups do not close anything. TM runs in the background.
Barry

Why does time machine say my wireless hard drive doesn't have enough space when it clearly does?

I have a 2 TB western digital hard drive connected via USB to my airport extreme (Y2012) that i've been using the past 2 years to connect to wirelessly. The hard drive has 2 partitions, ~1 TB each. 1 partition for backing up, the other for storing media. Recently I deleted my macbook pro backup. My macbook pro has a 500GB hard drive, of which about 120 GB is free.
Since I deleted the old time machine backup disk image and told time machine to start a new backup, I am now receiving an error. It's telling me there isn't enough room on the drive, when the 1TB partition i'm trying to use (as i've sucessfully done in the past) has nothing on it. 1 full TB free, and my macbook pro can't backup a 500 GB hard drive, which isn't even full itself.
PLEASE HELP!! I have a macbook pro early 2011, and I never know when the board is going to go koput again and I don't currently have a backup of my stuff while this problem persists.
Thanks!

Start with Section C in the 1st linked article.
Time Machine Troubleshooting
Time Machine Troubleshooting Problems

HT201250 How does Time Machine allocate backup data.

I have over 150GB to back up with time machine and only 256GB HD to use, does Time Machine back up all files each time or only files updated after the last backup?

Time Machine first makes a full backup, and then, it makes incremental backups backing up only the files that have changed since the last backup. When the Time Machine drive gets full, Time Machine will start deleting old backups in order to be able to make new backups. If you want more information about Time Machine, see > http://pondini.org

Does Time Machine bundle backup sets when it deletes a month's daily sets?

I'm asking this question to find out if I can delete the all but the last week in a month, each month, in order to extend the useful capacity of my backup drive.
In some backup systems, a periodic "bundle" is made when previous sets are deleted, so for instance, the last backup of the month has the cumulative hourly changes of that month. In this way, transient files which appear and disappear within the month are retained in the monthly backup.
Is this true of Time Machine? Exactly what does Time Machine do? Does it simply wipe out the daily sets and chose the last one to be the "weekly backup?" Or something more sophisticated and useful?
Thanks for any insight!

I've devised a little experiment to discover Time Machine's behavior in this regard:
On my Time Machine's backup schedule, August 27 corresponds with the end of a week. So, on August 26 at 9:15AM, I created the following [folder]/file structure:
[Time Machine Test -Transient Roll-up]
   [Time Machine Test - 1. Hourly Transience
      A one hour lifetime file.rtf
   [Time Machine Test - 2. Daily Transience
      A one day lifetime file.rtf
   [Time Machine Test - 3. Weekly Transience
      A one week lifetime file.rtf
At 10:10AM of that day I removed
[Time Machine Test - 1. Hourly Transience
      A one hour lifetime file.rtf
At 10:10 the next day, August 27, I removed
   [Time Machine Test - 2. Daily Transience
      A one day lifetime file.rtf
On August 28 at 10:30AM, acheck today of the earliest backup of this structure reveals only the following:
[Time Machine Test -Transient Roll-up]
   [Time Machine Test - 3. Weekly Transience
      A one week lifetime file.rtf
I draw the conclusion that transient files within a time period are not subject to a "roll-up" mechanism that displays all changes after out-of-date files are deleted by Time Machine. Thus, for instance, any file that appeared and disappears during an hour will be lost in Time Machine's daily history. Similarly, files that only persist for a day will be lost in the weekly history. And, presumably, if one wanted to choose a week which represented an accumulation of transient changes during the month it would be impossible to do so.
Even so, if one wants to manage only one backup volume, rather than accumulating a stack of them over the years, one might well think about selectively deleting all but one week per month in the earliest backups available, as the projected remaining time approaches less than a few weeks. BackupLoupe's Statistics gives an estimate of remaining time left for backups on a volume, and I would suggest using that as a forecast, unless others have experience to the contrary.
Hope this is useful. It certainly is to me.

Why does Time Machine forget "everything" after Mountain Lion update?

After updating to Mountain Lion (from Snow Leopard), I fired up my trusty external hard drive which contains my Time Machine backups (and nothing else) - of course I had run a backup right before upgrading to be sure. Two things are deeply disturbing: 1) The drive keeps on "rattling" as if a process is constantly reading or writing to it - even with Time Machine "OFF". Why? I (tried to) explicitly disable(d) Spotlight searching that drive, and nothing else should be accessing it! (I wish there was a way to simply turn Spotlight OFF for a while - I suspect it of a lot of crashes I experience).
Anyway, even more disturbing: Opening the System Preference Panel and sliding Time Machine to "On", it claims there is NO backup at all! Oldest backup: "NONE". Latest backup: "NONE". This is B.S.! BTW, opening the "Time Machine" app proper shows all the recent backups, so they are still there. So why doesn't the Time Machine Preference Panel not recognize them? Under these circumstances, is it safe to enable backups??? I am very afraid that if I let Time Machine proceed, it will try to create a full new backup, perhaps overriding all the snapshots from the past that are still stored on that disk. For one, even at 1 TB, my disk is not big enough to take another full backup on top of what's already stored on there. Any advice (other than "buy another hard disk just to be safe")?
O.k., I admit, so far I'm more upset with Mountain Lion than impressed.

Dear Pondini,
I am grateful for your advice and encouraging words, but I am (and remain) at my wit's ends as far as Time Machine is concerned. While I'm sure 99.99% of Mac users have no problem, there must be SOMETHING idiosyncratic about my own setup that has consistently crashed TM in the past, and now (after upgrading to Mountain Lion), it simply refuses to work EVER. Mind you, I'm NOT a "hacker" who installs non-standard software or likes to poke around in the Kernel.
Below is a shortened version of the Console output during my latest attempt - after 3 tries (after running disk utility to repair my permissions and check the hard drive), it never makes it beyond about 4 Gb before crashing. (And, what's worse, if I don't immediately react, TM very often crashes the whole computer to the point where NOTHING works anymore - requiring a restart. Even with Mountain Lion).
Thanks for any offer of help from anyone... SK
THIS WAS RIGHT BEFORE I TRIED TO START THE BACKUP
7/30/12 12:42:46.697 PM WindowServer[73]: [cps/setfront] Failed setting the front application to Finder, psn 0x0-0xc00c, securitySessionID=0x186a4, err=-13066 _
7/30/12 12:46:53.815 PM UserEventAgent[180]: com.apple.TMLaunchAgent disabled
NONE OF THE ABOVE WAS IN RESPONSE TO ANYTHING I DID! BUT MAYBE A CLUE?
ANYWAY, HERE GOES (with many repetitive lines removed - indicated by gaps):
7/30/12 12:48:52.885 PM com.apple.backupd[320]: Starting manual backup
7/30/12 12:48:53.475 PM com.apple.backupd[320]: Backing up to: /Volumes/TimeShare/Backups.backupdb
7/30/12 12:48:55.101 PM com.apple.backupd[320]: Event store UUIDs don't match for volume: Macintosh HD
7/30/12 12:48:55.799 PM com.apple.backupd[320]: Deep event scan at path:/ reason:must scan subdirs|new event db|
7/30/12 12:49:20.607 PM com.apple.launchd.peruser.501[156]: (com.apple.KerberosHelper.LKDCHelper[212]) Exited with code: 1
7/30/12 12:54:19.579 PM com.apple.backupd[320]: Finished scan
7/30/12 12:59:57.836 PM com.apple.backupd[320]: Found 470214 files (18.15 GB) needing backup
7/30/12 12:59:58.422 PM com.apple.backupd[320]: 24.03 GB required (including padding), 312.52 GB available
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:28.000 PM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x5
7/30/12 1:05:28.000 PM kernel[0]: jnl: disk1s2: write_journal_header: error writing the journal header!
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:28.693 PM com.apple.backupd[320]: Error (256): fetching properties: Error Domain=NSCocoaErrorDomain Code=256 "The file “Credits.rtf” couldn’t be opened." UserInfo=0x7f8b749355c0 {NSURL=file://localhost/Volumes/TimeShare/Backups.backupdb/kuhn%E2%80%99s%20Mac Book%20Pro/2012-07-26-114729/Macintosh%20HD/Applications/Preview.app/Contents/Re sources/zh_TW.lproj/Credits.rtf, NSFilePath=/Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-26-114729/Macintosh HD/Applications/Preview.app/Contents/Resources/zh_TW.lproj/Credits.rtf, NSUnderlyingError=0x7f8b7493fff0 "The operation couldn’t be completed. Input/output error"}
7/30/12 1:05:28.694 PM com.apple.backupd[320]: Error: (-50) SrcErr:NO Copying /Applications/Preview.app/Contents/Resources/zh_TW.lproj/Credits.rtf to /Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-30-124855.inProgress/A9556B25-47FE-4D1F-A2C9-BF18EEF78898/Macintosh HD/Applications/Preview.app/Contents/Resources/zh_TW.lproj
7/30/12 1:05:28.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:30.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error: (-50) SrcErr:NO Copying /Applications/Preview.app/Contents/version.plist to /Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-30-124855.inProgress/A9556B25-47FE-4D1F-A2C9-BF18EEF78898/Macintosh HD/Applications/Preview.app/Contents
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.341 PM com.apple.backupd[320]: Error: (-50) SrcErr:NO Copying /Applications/Preview.app/Contents/XPCServices to /Volumes/TimeShare/Backups.backupdb/kuhn’s MacBook Pro/2012-07-30-124855.inProgress/A9556B25-47FE-4D1F-A2C9-BF18EEF78898/Macintosh HD/Applications/Preview.app/Contents
7/30/12 1:05:30.381 PM com.apple.backupd[320]: Stopping backup.
7/30/12 1:05:30.381 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.381 PM com.apple.backupd[320]: Error: (-8062) SrcErr:NO Copying /Applications/Preview.app/Contents/XPCServices/com.apple.Preview.TrustedBookmar ksService.xpc/Contents/_CodeSignature/CodeResources to (null)
7/30/12 1:05:30.385 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.386 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.386 PM com.apple.backupd[320]: Copied 96604 files (2.26 GB) from volume Macintosh HD.
7/30/12 1:05:30.386 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.387 PM com.apple.backupd[320]: Copy stage failed with error:11
7/30/12 1:05:30.389 PM com.apple.backupd[320]: Error writing to backup log. NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: Invalid argument
7/30/12 1:05:30.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:30.464 PM com.apple.backupd[320]: Error: (5) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/TimeShare/Backups.backupdb/kuhn‚Äôs MacBook Pro/2011-06-14-140802
7/30/12 1:05:30.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:31.178 PM com.apple.backupd[320]: Error: (5) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/TimeShare/Backups.backupdb/kuhn‚Äôs MacBook Pro/2012-07-26-114729
7/30/12 1:05:31.000 PM kernel[0]: disk1s2: I/O error.
7/30/12 1:05:31.248 PM com.apple.backupd[320]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TimeShare/Backups.backupdb/kuhn‚Äôs MacBook Pro size:37
7/30/12 1:05:41.526 PM com.apple.backupd[320]: Backup failed with error: 11
7/30/12 1:09:42.396 PM mtmfs[37]: filesystem unmount attempted from stopFS
7/30/12 1:09:42.557 PM mtmfs[37]: unmount failed for /Volumes/MobileBackups
NOTE THE FAILURE TO UNMOUNT
7/30/12 1:10:02.499 PM fseventsd[48]: disk logger: failed to open output file /Volumes/TimeShare/.fseventsd/636573369d318daf (Invalid argument). mount point /Volumes/TimeShare/.fseventsd
7/30/12 1:10:04.000 PM kernel[0]: disk1s2: I/O error.
HERE I USED "FORCE EJECT"
7/30/12 1:10:04.799 PM fseventsd[48]: disk logger: failed to open output file /Volumes/TimeShare/.fseventsd/636573369d318daf (Invalid argument). mount point /Volumes/TimeShare/.fseventsd
7/30/12 1:10:05.000 PM kernel[0]: jnl: disk1s2: close: journal 0xffffff8042d1bcc0, is invalid. aborting outstanding transactions

Since installing Lion why does Time Machine shows backup was delayed?

Similar Messages

Maybe you are looking for