Time Machine not making hourly backups since Mavericks upgrade

Recently upgraded to Mavericks from Lion 10.7.5 (took 14 hr.). Since then, when I enter Time Machine (without being connected to my external backup drive) I get a notification "your time machine backup disc can not be found". The only options given are to "set up time machine" (which I have done) or "cancel". My previous backups to my external hard drive are shown in the back ground but can not be opened and there are no hourly or weekly backups shown.

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Click the Clear Display icon in the toolbar. Then try the action that you're having trouble with again. Select any messages that appear in the Console window. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Similar Messages

  • Time machine not consolidating hourly backups

    For some reason my time machine isn't consolidating backups at the end of the day/week/month. On my time machine drive, I currently have hourly backups going back over 2 months.
    As you may imagine, this eats up a lot of storage.
    Does anyone have any ideas what might be causing this?

    That's odd. Mine go away after 24 hours like clockwork.
    As VA2020 says, it's probably not a significant space problem, but worth investigating, especially after that long a time.
    I'd suggest downloading the Time Machine Buddy widget, which extracts TM's messages from your logs and displays them in a little window. Check your last few backups, especially for messages about "thinning".
    As an example, here's my most recent set, showing routine deletion of an hourly:
    *Starting standard backup*
    *Backing up to: /Volumes/TmBackups/Backups.backupdb*
    *No pre-backup thinning needed: 133.2 MB requested (including padding), 175.83 GB available*
    *Copied 492 files (2.7 MB) from volume Macintosh HD.*
    *Starting post-backup thinning*
    *Deleted backup /Volumes/TmBackups/Backups.backupdb/JPs.G5.iMac/2009-01-19-191145: 175.83 GB now available*
    *Post-back up thinning complete: 1 expired backups removed*
    *Backup completed successfully.*
    If yours look hinky (pardon the technical term), especially any sort of failure message, or not being able to delete old backups, copy and post them here (be careful to get all the messages, as they often overflow the little window).
    One question: have you used any of the 3rd part apps or postings about modifying TM's preference file to alter the backup schedule?

  • HT201250 Time Machine not keeping hourly backups.

    My Time Machine backups don't seem to be working correctly.  It doesn't appear to be keeping hourly backups.  When I enter Time Machine and look at the backup from just one hour ago, the newest file is from several weeks ago, not one hour ago.
    Same thing with monthly backups.  At a certain point, the backup history skips several months.
    I've scoured the internet but can't seem to find anyone else with this problem or a solution.

    That's odd. Mine go away after 24 hours like clockwork.
    As VA2020 says, it's probably not a significant space problem, but worth investigating, especially after that long a time.
    I'd suggest downloading the Time Machine Buddy widget, which extracts TM's messages from your logs and displays them in a little window. Check your last few backups, especially for messages about "thinning".
    As an example, here's my most recent set, showing routine deletion of an hourly:
    *Starting standard backup*
    *Backing up to: /Volumes/TmBackups/Backups.backupdb*
    *No pre-backup thinning needed: 133.2 MB requested (including padding), 175.83 GB available*
    *Copied 492 files (2.7 MB) from volume Macintosh HD.*
    *Starting post-backup thinning*
    *Deleted backup /Volumes/TmBackups/Backups.backupdb/JPs.G5.iMac/2009-01-19-191145: 175.83 GB now available*
    *Post-back up thinning complete: 1 expired backups removed*
    *Backup completed successfully.*
    If yours look hinky (pardon the technical term), especially any sort of failure message, or not being able to delete old backups, copy and post them here (be careful to get all the messages, as they often overflow the little window).
    One question: have you used any of the 3rd part apps or postings about modifying TM's preference file to alter the backup schedule?

  • Time Machine not making restorable backups

    I've been having a few problems with Time Machine - this began when I un-installed Boot Camp, having reluctantly had to invest in a full Windows PC - and discovered that both the utility and recovery system were unable to repartition the Hard Drive in my MBP back to full size. Currently, OSX effectively uses 380GB of a 500GB HD (less space taken by partitioning, recovery partition, etc...) I was particularly perturbed by the error thrown up by Disk Utility in OSX recovery that it was unable to dismount the HD for repartitioning, irrelevent the size I attempted to make the new OSX partition.
    Having exausted options I was aware of then, I decided the safe option was to re-install OSX to the entire HD, restoring it from the Time Machine backup, but (checking that this was feasible before starting) I found that the last restorable backup Time Machine claimed to have was from 2011, about the time I moved from my previous MBP to this one. I reformatted the drive Time Machine was installed on, and setup the programme from scratch again to try and create a useable backup, but in spite of this it refuses to work properly - Time Machine claims to have backed up, but upon trying to use the backup the restore programme states it isn't there. For reference, I'm using a 1TB, FireWire 800 external HD for the backups.
    At this point, I've run out of knowledge of how OSX works, and would really like some help getting things back on an even keel. Obviously, my major concern is that I'm not getting proper backups anymore, but I would also like to recover the space on my HD that's otherwise lost. Googling the problem led me to an issue which sometimes occurs that Time Machine can get flagged to ignore system files, but checking through Terminal it appears that that isn't the case (all it's set to ignore is my Steam folder, as that's all available online anyway.) Might anyone be able to help with this?
    Many thanks in advance.

    This simple procedure will clear your Time Machine settings, including exclusions. The backups won't be affected. If you have a long exclusion list that can't be recreated easily, you may prefer a more complicated procedure that preserves the exclusion list. In that case, ask for instructions. Otherwise, do as follows.
    Triple-click anywhere in the line below on this page to select it:
    /Library/Preferences/com.apple.TimeMachine.plist  
    Right-click or control-click the highlighted line and select
    Services ▹ Reveal
    from the contextual menu.* A Finder window should open with a file selected. Copy the file to the Desktop. Then move it (the original, not the copy) to the Trash. You'll be prompted for your administrator password. Reboot and recreate your settings in the Time Machine preference pane. It will show that you have no backups. Don't worry; that's expected. Run a backup to test. The backup may take much longer than usual. If TM now performs as expected, delete the file you copied to the Desktop.
    *If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination  command-C. In the Finder, select
    Go ▹ Go to Folder...
    from the menu bar, paste into the box that opens (command-V). You won't see what you pasted because a line break is included. Press return.

  • I have been using a WD Passport with Time Machine on my iMac.  Since I upgraded to Mavericks, the backup no longer works.  What do I need to do?

    I have been using a WD Passport with Time Machine on my iMac.  Since I upgraded to Mavericks, the backup no longer works.  What do I need to do?
    I assume that upgrading the WD SmartWare is irrelevant as it is not being used.  Should I upgrade just as a precaution?
    One complication is that I have renamed my user since the last time I backed up.

    the problem is with the WD Passport drives.   I also have one, and since upgrading to 10.9 I can no longer use mine either.  See if this solution works for you: https://discussions.apple.com/message/23943103#23943103

  • Time Machine not thinning older backups (Hourly= Daily= Weekly)

    Ever since upgrading to Snow Leopard, Time machine has kept hourly backups of my computer.
    In the past under 10.5, after about 24 hours, TM would delete all but the last hourly backup of the day and keep daily backups for 30 days, then after about 30 days delete the daily backups except for 1 per week and keep weekly backups thereafter.
    Now, TM does it's hourly backups like normal, but I have hourly backups from today all they way back to 29 August (about 24 hours prior to when I upgraded to 10.6) and then weekly backups from that date until 30 July (i.e. about 30 days prior to the upgrade).
    Called AppleCare and talked to 2 different people. Both questioned whether TM really was even supposed to thin old backups like this (um, it's written in the da^^ preference pane, guys) and one admitted that he doesn't even use a Mac at home and that in the support office they don't have TM on their macs, so he's never used it!
    Needless to say, not sure how to a) get TM to start thinning the backups like it should and b) also thin out all the previous backups so I don't have a 2 month glut of frequent backups.
    I've looked all over and found nothing. Anyone with some advice? I'd like to avoid killing all my backups and starting over.

    Forensic
    I suggest you follow the advice posted above by V.K., once installed it will provide a log of what TM is doing.
    Once you have that info, post back here and someone far wiser than I will help you to resolve the issue.

  • HT3275 Time Machine not deleting oldest backups when the disk is full

    Time Machine not deleting oldest backups when the disk is full

    Unfortunately, when this happens, Time Machine cannot erase enough space to create room for the new backup. Your options now are:
    1) Add a new Time Capsule or a hard drive to the USB port on the existing Time Capsule and continue with backups
    2) Manually delete backups from Time Machine....which is a long and tedious process.  After a few hours, not much space will be reclaimed and it will not be long before the Time Capsule is full again
    3) Erase the Time Capsule....if you really do not need all the old backups from months ago....and start over with a new Time Machine backup and move forward again

  • I am using 10.9.1 on a 21.5" iMac. I am backing up using Time Machine. The hourly backups are over kill. How do get TM to backup daily?

    I am using 10.9.1 on a 21.5" iMac. I am backing up using Time Machine. The hourly backups are over kill. How do get TM to backup daily, only?

    See Pondini's TM FAQs, for details.

  • Time Machine Not Overwriting Older Backups

    Time Machine is telling me that the 1TB backup disk is full, albeit there is 62GB of available space (why is TM stating it's full?). In any event, TM is not overwriting the older backups. How can this be enabled?
    Thank you!

    About TM "Backup Drive is Full"
    Alert TM only deletes older files if they have been deleted from the source and when TM needs space on the backup drive for a new incremental backup. Time Machine "thins" it's backups; hourly backups over 24 hours old, except the first of the day; those "daily" backups over 30 days old, except the first of the week. The weeklies are kept as long as there's room.
    So, how long a backup file remains depends on how long it was on your Mac before being deleted, assuming you do at least one backup per day. If it was there for at least 24 hours, it will be kept for at least a month. If it was there for at least a week, it will be kept as long as there's room.
    Note, that on a Time Capsule the sparsebundle grows in size as needed, but doesn't shrink. Thus, from the user's view of the TC it appears that no space has been freed, although there may be space in the sparsebundle.
    Once TM has found it cannot free up enough space for a new backup it reports the disk is full. You can either erase the backup drive and start your backups anew or replace the drive with a larger drive.

  • Time machine not making backup

    My time machine has been having troubles lately. Then it seemed to work, but now it hasn't done a backup for 2 days. I just saw it going and it was totally up a bunch of items (on the order of 60,000 items). But it didn't go. The buddy reported this:
    Starting standard backup
    Attempting to mount network destination using URL: afp://[email protected]/Data
    Mounted network destination using URL: afp://[email protected]/Data
    Disk image /Volumes/Data/Rothrock’s iMac_001ec215e6e6.sparsebundle mounted at: /Volumes/Backup of Rothrock’s iMac
    Backing up to: /Volumes/Backup of Rothrock’s iMac/Backups.backupdb
    Error: Flushing index to disk returned an error: 0
    Backup canceled.
    Ejected Time Machine disk image.
    Ejected Time Machine network volume.

    It just occurred to me that the "Error: Flushing index to disk returned an error: 0" was pretty vague. So I went into the console and found these entries:
    Apr 11 12:25:14 Rothrock mds[38]: (/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16)(Erro r) IndexSDB in dbflushdatastore:/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16/store .db : dbsyncdatastore: !WARNING! prior write-errors invalidate sync.
    Apr 11 12:25:14 Rothrock mds[38]: (/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16)(Erro r) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
    Apr 11 12:25:14 Rothrock com.apple.backupd[29095]: Error: Flushing index to disk returned an error: 0
    Apr 11 12:25:14 Rothrock mds[38]: (/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16)(Erro r) IndexSDB in dbflushdatastore:/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16/store .db : dbsyncdatastore: !WARNING! prior write-errors invalidate sync.
    Apr 11 12:25:14 Rothrock mds[38]: (/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16)(Erro r) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
    Apr 11 12:25:17 Rothrock com.apple.backupd[29095]: Backup canceled.
    Apr 11 12:25:17 Rothrock mds[38]: (/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16)(Erro r) IndexSDB in dbflushdatastore:/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16/store .db : dbsyncdatastore: !WARNING! prior write-errors invalidate sync.
    Apr 11 12:25:17 Rothrock mds[38]: (/Volumes/Backup of Rothrock’s iMac/.Spotlight-V100/Store-V1/Stores/77013B24-21EF-4E45-A447-88425C215C16)(Erro r) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 0
    Does that mean that spotlight is trying to index the sparsebundle? Is there a way to fix that?

  • Time machine stuck in 'preparing backup' in mavericks

    I have just upgraded to Mavericks on my macbook pro 13" 2009.  I have a 2TB time capsule which has run perfectly for years under several OS X.  I also have an external HDD to which I copy an image of my internal HD once a week using Carbon Copy Cloner.
    Since upgrading to Mavericks the whole 'backing up' has become a total nightmare.  Backing up using CCC is fine.  Backing up to the time capsule using Time machine has now become completely unusable.
    I have verified both my internal HDD and the time capsule.  I have repaired permissions.  I have disconnected my HDD as I now realise that this is a problem under Mavericks but I do feel let down by Apple.  Its their software, their hardware and their time capsule and it is clearly failing. Even a USB memory key (essential for me) throws everything off!!!
    Has anybody any bright ideas?  I am not a guru by any means but have a working knowledge of the various bits of kit.....sort of.
    Thanks in advance.  First time poster so looking forward to some help here.......
    R

    This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve your problem.
    If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    Below are instructions to run a UNIX shell script, a type of program. All it does is to gather information about the state of your computer. That information goes nowhere unless you choose to share it on this page. However, you should be cautious about running a program at the instance of a stranger on a public message board. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them.
    Here's a summary of what you need to do: Copy a line of text from this web page into the window of another application. Wait about a minute. Then paste some other text, which will have been copied automatically, back into a reply on this page. The sequence is: copy, paste, wait, paste again. Details follow.
    You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
    If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
    The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking  anywhere in the line. The whole line will highlight, though you may not see all of it in your browser, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
    Triple-click anywhere in the line of text below on this page to select it:
    clear; shopt -s extglob; Fb='%s\n\t(%s)\n'; Fm='\n%s:\n\n%s\n'; Fs='\n%s: %s\n'; Fu='User %s%%\t\tSystem %s%%'; PB="/usr/libexec/PlistBuddy -c Print"; A () { [[ a -eq 0 ]]; }; R () { o=; [[ r -eq 0 ]]; }; Pm () { [[ "$o" ]] && o=`sed 's/^ */   /' <<< "$o"` && printf "$Fm" "$1" "$o"; }; Pc () { o=`egrep -v '^[[:blank:]]*($|#)' "$2"`; Pm "$1"; }; Pp () { o=`$PB "$2" | awk -F'= ' \/$3'/{print $2}'`; Pm "$1"; }; Ps () { o="${o##+( )}"; [[ ! "$o" =~ ^0?$ ]] && printf "$Fs" "$1" "$o"; }; id | grep -qw '80(admin)'; a=$?; A && sudo true; r=$?; t=`date +%s`; clear; { A || echo $'No admin access\n'; A && ! R && echo $'No root access\n'; system_profiler SPSoftwareDataType | sed '8!d;s/^ *//'; o=`system_profiler SPDiagnosticsDataType | sed '5,6!d'`; [[ "$o" =~ Pass ]] || Pm "POST"; o=`pmset -g therm | sed 's/^.*CP/CP/'`; egrep -q 'No th|pms' <<< "$o" && o=; Pm "Thermal conditions"; o=`pmset -g sysload | grep -v :`; grep -q '= [^GO]' <<< "$o" || o=; Pm "System load advisory"; o=`nvram boot-args | awk '{$1=""; print}'`; Ps "boot-args"; d=(/ ""); D=(System User); for i in 0 1; do o=`cd ${d[$i]}L*/L*/Dia* && ls *.{crash,hang,panic} | tail | awk -F_ '{$NF=a[split($NF,a,".")]; print}'`; Pm "${D[$i]} diagnostics"; done; o=`syslog -F bsd -k Sender kernel -k Message CReq 'GPU |hfs: Ru|I/O e|n Cause: -|NVDA\(|pagin|SATA W|timed? ?o' | tail -n25 | awk '/:/{$4=""; $5=""; print}'`; Pm "Kernel messages"; o=`df -m / | awk 'NR==2 {print $4}'`; [[ o -lt 5120 ]] && Ps "Free space (MiB)"; o=$(($(vm_stat | awk '/eo/{sub("\\.",""); print $2}')/256)); o=$((o>=1024?o:0)); Ps "Pageouts (MiB)"; s=( `sar -u 1 10 | sed '$!d'` ); [[ s[4] -lt 90 ]] && o=`printf "$Fu" ${s[1]} ${s[3]}` || o=; Pm "Total CPU usage" && { s=(`ps acrx -o comm,ruid,%cpu | sed '2!d'`); o=${s[2]}%; Ps "CPU usage by process $s of user ${s[1]}"; }; s=(`top -R -l1 -n1 -o prt -stats command,uid,prt | sed '$!d'`); s[2]=${s[2]%[+-]}; o=$((s[2]>=25000?s[2]:0)); Ps "Mach ports used by process $s of user ${s[1]}"; o=`kextstat -kl | grep -v com\\.apple | cut -c53- | cut -d\< -f1`; Pm "Loaded extrinsic kernel extensions"; R && o=`sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|calendarse|cups|dove|isc|ntp|post[fg]|x)/{print $3}'`; Pm "Extrinsic system jobs"; o=`launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)|\.[0-9]+$/{print $3}'`; Pm "Extrinsic agents"; for d in {/,}L*/{La,Priv,Sta}*; do o=`ls -A "$d" | egrep -v '^(\.DS_Store$|com\.apple\.)'`; Pm "$d"; done; o=`find -L /S*/L*/E* {/,}L*/{A*d,Compon,Ex,In,Keyb,Mail,P*P,Qu,Scripti,Servi,Spo}* -type d -name Contents -prune | while read d; do ID=$($PB\ :CFBundleIdentifier "$d/Info.plist") || ID="No bundle ID"; egrep -qv "^com\.apple\.[^x]|Accusys|ArcMSR|ATTO|HDPro|HighPoint|driver\.stex|hp-fax|\.hpio|JMicron|microsoft\.MDI|print|SoftRAID" <<< $ID && printf "$Fb" "${d%/Contents}" "$ID"; done`; Pm "Extrinsic loadable bundles"; o=`find /u*/{,*/}lib -type f -exec sh -c 'file -b "$1" | grep -qw shared && ! codesign -v "$1"' {} {} \; -print`; Pm "Unsigned shared libraries"; o=`launchctl getenv DYLD_INSERT_LIBRARIES`; Pm "Inserted libraries"; o=`find {,/u*/lo*}/e*/periodic -type f -mtime -10d`; Pm "Modified periodic scripts"; o=`scutil --proxy | grep Prox`; Pm "Proxies"; o=`scutil --dns | awk '/r\[0\] /{if ($NF !~ /^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./) print $NF; exit}'`; Ps "DNS"; R && o=`sudo profiles -P | grep :`; Pm "Profiles"; for f in fstab sysctl.conf crontab launchd.conf; do Pc $f /etc/$f; done; Pc "hosts" <(grep -v 'host *$' /etc/hosts); Pc "User launchd" ~/.launchd; R && Pc "Root crontab" <(sudo crontab -l); Pc "User crontab" <(crontab -l); R && o=`sudo defaults read com.apple.loginwindow LoginHook`; Pm "Login hook"; Pp "Global login items" /L*/P*/loginw* Path; Pp "User login items" L*/P*/*loginit* Name; Pp "Safari extensions" L*/Saf*/*/E*.plist Bundle | sed 's/\..*$//;s/-[1-9]$//'; o=`find ~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \) | wc -l`; Ps "Restricted user files"; cd; o=`system_profiler SPFontsDataType | egrep "Valid: N|Duplicate: Y" | wc -l`; Ps "Font problems"; o=`find L*/{Con,Pref}* -type f ! -size 0 -name *.plist ! -exec sh -c 'plutil -s "$1" >&-' {} {} \; -print`; Pm "Bad plists"; d=(Desktop L*/Keyc*); n=(20 7); for i in 0 1; do o=`find "${d[$i]}" -type f -maxdepth 1 | wc -l`; o=$((o<=n[$i]?0:o)); Ps "${d[$i]##*/} files"; done; o=$((`date +%s`-t)); Ps "Elapsed time (s)"; } 2>/dev/null | pbcopy; exit 2>&-
    Copy the selected text to the Clipboard by pressing the key combination command-C.
    Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign ($) or a percent sign (%). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
    Click anywhere in the Terminal window and paste (command-V). The text you pasted should vanish immediately. If it doesn't, press the return key.
    If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important.
    If you're not logged in as an administrator, you won't be prompted for your password. The test will still run. It just won't do anything that requires administrator rights.
    The test may take up to a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. There is no indication of progress until it's done. Wait for the line "[Process completed]" to appear in the Terminal window. If you don't see that line within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report your results. No harm will be done.
    When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
    If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
    When you post the results, you might see the message, "You have included content in your post that is not permitted." That's because the forum software falsely identifies something in the post as a violation of the terms of use. If that happens, please post the results on Pastebin, then post a link here to the page you created.
    Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
    Copyright © 2014 Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Terms of Use of Apple Support Communities ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

  • Time Machine doing HUGE hourly backups

    TM seems to be doing gigantic backups every hour -- copying 2-4 GB worth of data each time. Now clearly I'm not modifying that much data on an hourly basis. Is there any way I can monitor which files are being copied?
    My naive expectation is that in TM Preferences, under the progress bar, there would be a little disclosure triangle that, when clicked, tells you the name of the file currently being copied. Of course no such thing exists. Is there any way of knowing what the heck is going on?

    Time Machine will back up data if anything has changed. Even the slightest change to permissions will force a new backup. For example: I defragged my hard drive recently. Since I optimized the metadata table and moved the files around, TM thought I had new versions and prompted doubled my sparsebundle size overnight. It did not bother to compare filenames or sizes (and I do not think iDefrag changes the "modified" date), but some some puny little flag somewhere had been changed so it backed the file up again. I really do like TM, but the more I use it, the more I can see that it really is not "smart" with respect to incremental backups.
    Anyway, that might be something for you to investigate. I'm willing to bet tat even if you change the name of a directory then change it right back, TM will backup it up fresh. Time Machine has a ways to go yet. Hopefully Apple will release a "2.0" version in the near future that will address many of the irregularities that seem to plague the program.

  • Time Machine not performing routine backups

    Hi all,
    I noticed recently that Time Machine has not been completing my scheduled backups. A full backup has not been completed since December of 2011. The backups start but never progress past "Preparing Backup", today I let it sit with no other applications open or processes running for 4 hours and nothing occured.
    I have reviewed many discussions here and so far nothing seems to be working. I deleted the preference file and have powered the Time Machine off and on to no avail.
    Here is a snippet of the log from my latest attempt at running a backup. I'm sure I need to give more information but I'm not sure what that is. I would appreciate any help.
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Data-1/Jen Bradshaw’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Capsule
    Backing up to: /Volumes/Time Capsule/Backups.backupdb
    Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device
    Event store UUIDs don't match for volume: Macintosh HD
    Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device
    Exception writing exclusions cache.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device
    Unable to create exclusions cache data.
    Failed to write exclusions cache. Continuing anyway.
    Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)
    Waiting for index to be ready (101)

    volley15 wrote:
    Error writing to backup log.  NSFileHandleOperationException:*** -[NSConcreteFileHandle writeData:]: No space left on device
    That's a problem writing to the (hidden) log Time Machine keeps on the Time Capsule, not your internal drive.  (As Linc says, you also need free space on your internal).
    Do you have other data there, besides Time Machine backups?  Usually that's how this condition happens -- Time Machine always leaves a bit of space, so the next backup can get started, see if there's enough room for the backup and if necessary start deleting old backups to make room. But if the very last of the free space gets used, it can't get started.
    First, connect via Ethernet cable if at all possible.  What you have to do, and the next backup, will take a while, but be 2-3 times faster than via WIFI.
    If you have other data there, copy some of it elsewhere and delete it (50 MB should be enough), and copy it back after the next backup completes.
    If there isn't any other data there, delete your oldest backup, per Time Machine - Frequently Asked Question #12, and "compact" the sparse bundle per the pink box there.
    The next backup will take quite a while -- TM has to do a "deep scan" first, to see what needs to be backed-up (since the previous backup failed), then "compact" the sparse bundle, then start deleting backups to make room.
    Once you get this sorted out, if you have other data on the TC, see #Q3 in Using Time Machine with a Time Capsule for some workarounds to keep this from happening again.
    Message was edited by: Pondini

  • Time machine not deleting old backups...

    I am on Mavericks 10.9.1 and get the following error:
    "The backup disk needs48.93 GB for the backup but only 30.99 are available.  Select a larger backup disk or make the backup smalled by excluding files."
    I recently had to unplug my external HD which I use for time machine back-ups, this error started when I plugged it back in just a few days ago.  I have exlcuded some files from the back up and still get the error.  My internal HD has 475.62GB of data on it, and I am trying to back up to a 500GB external HD, the total size of my backup is roughly 465GB. 
    Seems like I should have enough space for a back-up and TM should delete the old back-ups.  I have been through a search of the forum and online and have not found a solution.  Has anyone ran into this?
    Thanks for the help!

    I believe I was told that If you had older backups like ML and your disk is getting full it will not delete these because you are now backing up a new OS (Mavericks).  It only deletes older backups of the same OS you are now using.

  • Time machine not deleting old backups of recovery partition

    I have a Mac Mini running Lion Server. I have an external disk partitioned with a space for network backups and a smaller partition for backing up the server itself. The server has a 160GB disk, it is only using 29.27GB, the partition for backing up the server is 152GB (it's what was left over after creating the partition for the network backups). I figured since I'm only using about 30GB, 152GB should be plenty of space. However after 3 months of use I get the error "the backup is too large for the backup disk". In the past I have formatted the partition and restarted the backups, however it always fills up after 3 months. This time I decided to dig into it a bit more. I looked to see what was available in my backup, it only has one previous restore point. I browsed the disk and opened the backups.backupdb folder, checked the size of the folder with the computer name, it is only 9.44GB. I was wondering where all of the space went so I enabled hidden files, I found the .RecoverySets folder and found it was taking up 141.95GB. I looked at the recovery sets, there are 295 copies of com.apple.recovery.boot which all seem to contain the following files:
    .disk_label                         749b
    BaseSystem.chunklist       2KB
    BaseSystem.dmg              454.6MB
    boot.efi                              864KB
    com.apple.Boot.plist          431b
    kernelcache                       24.1MB
    PlatformSupport.plist         2KB
    SystemVersion.plist           478b
    Of those files, the only file not dated Aug 11, Oct 6 or 12, 2011 is com.apple.Boot.plist which has a date that corresponds to when the backup was performed. These backups go all the way back to Jan 30, the last time I formatted the partition, but the user data backups only go back to the 27th and it hasn't been able to complete a backup since.
    I thought Time Machine was supposed to only backup data that had changed since the last backup, and delete old revisions when space is running low, it seems that it is copying more than just the data that changed since the last backup and only deleting old revisions of user data, not system data. Is there a way to fix this permanently?

    See C18 in the first linked article. Also, your backup drive should be 2-4 times your hard drive capacity.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

Maybe you are looking for