Time Machine 108GB initial backup about 2.5 hours

I had a few issues getting Time Machine to do it's initial backup.
Here are some tips that might help you.
1) In System Preferences, Spotlight, Privacy, add the external drive so it will not be indexed (included in Spotlight searches). I would assume it's okay to remove that setting after the initial backup.
2) Before doing the first Time Machine backup, do a Shut Down... and then press the power button to boot up.
3) During the initial backup. Do not open the Finder. At least, don't open the Finder for the backup drive. When I did that, the drive would start thrashing and the data transfer would slow to a crawl. Not sure what the heck the drive was doing.
4) With a WD My Book Premium 320GB Drive, connected via FireWire, I got about 0.7 - 0.8GB copied per minute. When the backup was running too slow, it was about 30 - 40MB per minute (that would have taken forever.)
Here's the whole story:
I turned Time Machine on in the System Preferences and selected my Western Digital My Book Premium 320GB drive(connected via FireWire 400). I was already doing backups to this drive with ChronoSync, but there was enough room for it to do the backup of my system with room to spare. (I will free up more space by deleting that backup after I'm sure Time Machine is good.) Time Machine started doing it's initial backup and I noticed that it was going very slow... about 25GB after about 3 hours, which is pretty pathetic. I stopped it because the drive was thrashing like crazy and it didn't seem to make sense that it was doing that. It seemed like Spotlight might be trying to simultaneously index the drive, thus slowing things down. I added the drive to the Privacy setting on Spotlight, so it is now excluded. Then, I deleted the Backups.backupdb folder and emptied the Trash. After that, I rebooted. I then started the whole Time Machine initial backup again and it seemed to run much faster, so I let it go for a bit. I had about 25GB copied after about 30 minutes. Much faster. However, I decided to open up Finder and take a look at the Backups.backupdb folder to see what it looked like. After doing that and seeing the *.inprogress file, the drive started thrashing again and the copy slowed down. I stopped it again, deleted the folder again and rebooted. Started Time Machine initial copy again. Very slow this time. So, again, I stopped it, deleted the backup folder and this time, I shut the computer down. I let it sit for 10 seconds or so, then started it back up. Started the Time Machine initial copy again and it was going fast again. I think the shutdown cleared out something. ( a cache maybe?) Anyway, I made sure not to open Finder again during the initial backup and left it running. After about 2 - 2.5 hours, the initial backup of 108GB was complete. I just heard it do it's first hourly backup, which was basically nothing, because I haven't made any changes to anything yet.

Time Machine backups to AirDisks (e.g. USB HDD attached to Extreme) is unsupported, but has been successful by some. As well, once you decide to move any old TM backups (HDD connected directly to the Mac) to an AirDisk, you cannot continue backing up to your previous TM backup. The format it saves to vs. a local HDD is different. The folder structure you see becomes a sparsebundle/disk image via the AirDisk.
If you are interested in proceeding with your plan, check these links out:
http://discussions.apple.com/thread.jspa?messageID=8225748&#8225748
http://discussions.apple.com/thread.jspa?messageID=8650723&#8650723
http://jamesshore.com/Blog/How-to-Accelerate-Time-Machine.html

Similar Messages

  • How does time machine handle initial backup after upgrading to Yosemite?

    HI All,
    I'm wondering if Time machine will create a "new" full backup of the system after I upgrade to Yosemite.
    I'm trying to make sure I can backout (revert to previous backup of Mavericks) of the upgrade should I run into trouble.
    Thanks,
    Eddy817

    besides restoring just one file, that is what Time machine DOES. See this article:
    Time Machine - Frequently Asked Questions -- 14. How do I restore my entire system?
    If you are deeply concerned, you may want make a copy of your entire system before updating (Clone your old system) or Install onto a Blank drive and add your files to that.
    If you make NO preparation and do not have a Backup, the only way to install a previous versions is to do so onto a Blank drive. Also, you must have PURCHASED (even for $0) a copy of Mavericks, or it will not be available for re-download.

  • Time machine will not backup after maverick

    This is a major problem, not addressed in the installation instrucitons. The disk runs eternally "preparing backup", I mean all night.
    This happened to two machines on entirely separate backup disks. And if we are sacraficing the old data in reformating the drive, I would like to know about that before choosing to upgrade.

    Update: Finally...
    At least for the Promise Pegasus R4... but I noticed on other threads that WD drives are also acting up too so this might work with them too.
    I turned off Time Machine, and deleted that pesky .plist file, again. I unplugged the R4, power and thunderbolt, then played whack the gopher with the drives swapping them around randomly.  I reintalled Mavericks from a fresh download, yet again, then set Time Machine to backup on a fast USB 3TB drive (which it did in 6 hours or so).  Then I turned off Time Machine, deleleted that .plist file again, rebooted the iMac, plugged in the R4, reformatted it again with Disk Utility, then hooked it to Time Machine, said a few slightly heretic prayers to whatever demons came with Maverick, and 2 minutes later Time Machine started to backup and report 1 hour to complete... the hour isn't up yet, but I'm crossing everything I have 2 of...
    I've noticed a few other 'didn't copy over or mesh well' things with Maverick, but that's a different thread and 2 updates from now once we all suffer through this extended beta-test by Apple.
    John Galt posted this on another thread... to find and delete that pesky .plist file:
    or "error ... while creating the backup folder."
    and follow that to:
    http://pondini.org/TM/A4.html

  • Time machine won't backup, yet plenty of space & not much used on Mac HD

    Well, this is yet another "Time machine won't backup becuase there is not enough space" thread. I have searched Google and threads here but it's still a mystery why this error is occurring and it seems there is no clear solution. I also looked at the Apple Time Machine errors FAQ as well.
    Here are my specs and what I have tried so far.
    2010 Mac Pro Quad Core with 1 TB hard drive with 12 GB RAM. (137 GB used so far on internal Mac hard drive disk, so about 863 GB free space).
    - New external 1 TB hard drive initialized as Time Machine backup disk when inserted for the first time.
    The exact error I am getting is this: "This backup is too large for the backup disk. The backup requires 1.80 TB but only 999.20 GB are available."
    I have tried deleting the Time Machine system preference, reinitializing the external disk, clearing the system caches with Cocktail, restarting and letting Time machine ask me all over again if I wanted to use the external drive for Time Machine. Still the same error.
    My question is how on earth can 1.80 TB be required for the backup when I only have 137 GB of used space?

    danomatic12 wrote:
    My question is how on earth can 1.80 TB be required for the backup when I only have 137 GB of used space?
    Two possibilities:
    There's another disk (or disks) connected to your Mac. If they're formatted HFS+, Time Machine is trying to back it/them up as well. You can exclude them per #10 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum). The 1.8 TB includes 20% for temporary workspace on the TM drive, so TM is estimating the backup at about 1.5 TB.
    Something on your internal HD is corrupted, causing an incorrect calculation. Verify your internal HD, per #6 in [Formatting, Partitioning, Verifying, and Repairing Disks|http://web.me.com/pondini/AppleTips/DU.html] (or use the link in *User Tips* at the top of the +Using Snow Leopard+ forum).

  • Time Machine fails to backup HD and stalls computer when backing up to external HD (Western Digital WD5000MT) when using Firewire 800 but works fine using USB

    I have a mid 2012 MBP (MacbookPro9,1) running Mountain Lion 10.8.2.  When I start a Time Machine backup to an external Western Digital HD (WD5000MT) connected using a Firewire 800 cable, my open programs stop responding and in general my computer freezes up not allowing me to open activity monitor or the console utility.  I can't even shut down or restart my computer and must hard boot to reset.  Though removing the firewire cable that goes to the external HD can sometimes get my system working again.  However, the WD external HD also has a usb port and when I connect it to my computer via a USB cable, Time Machine seems to backup my system fine without stalling my computer.  This same external HD worked fine with Firewire 800 using my old late 2007 MBP running snow leopard.  I should note that my brother has the exact same model WD external HD and he also had issues with the firewire port on his MBP running mountain lion.  I have run the disk utility checking for disk/file permission errors and the drive itself seems fine.  I initially formatted that drive as ExFAT but while troubleshooting reformatted to HFS+ and still had the same issue.  I tested using a different firewire 800 cable but still had the same issue.  Can't think of anything else to do.  I don't have another firewire-compatible device to test if it is the HD vs the firewire port.   I would prefer to use the firewire port for quicker transfer speeds but I'm stuck with USB for now.  Any suggestions? 

    Maybe these will help:
    http://pondini.org/TM/Troubleshooting.html
    http://support.apple.com/kb/PH11194
    http://support.apple.com/kb/HT3275 (note - older article)
    Have you tried looking at the Western Digital web site to see if you can find anything?
    http://support.wdc.com

  • Time Machine fails on backup. Have verified and reformatted external. Have also run etrecheck and Time Machine Buddy.

    ETRECHECK:
    Problem description:
    time machine will not backup
    EtreCheck version: 2.1.8 (121)
    Report generated March 7, 2015 7:10:23 AM EST
    Download EtreCheck from http://etresoft.com/etrecheck
    Click the [Click for support] links for help with non-Apple products.
    Click the [Click for details] links for more information about that line.
    Hardware Information: ℹ️
        MacBook Pro (17-inch, Early 2011) (Technical Specifications)
        MacBook Pro - model: MacBookPro8,3
        1 2.3 GHz Intel Core i7 CPU: 4-core
        8 GB RAM
            BANK 0/DIMM0
                4 GB DDR3 1333 MHz ok
            BANK 1/DIMM0
                4 GB DDR3 1333 MHz ok
        Bluetooth: Old - Handoff/Airdrop2 not supported
        Wireless:  en1: 802.11 a/b/g/n
        Battery Health: Normal - Cycle count 680
    Video Information: ℹ️
        AMD Radeon HD 6750M - VRAM: 1024 MB
            Color LCD 1600 x 1000
        Intel HD Graphics 3000 - VRAM: 512 MB
    System Software: ℹ️
        Mac OS X 10.7.5 (11G63) - Time since boot: 8 days 7:40:9
    Disk Information: ℹ️
        TOSHIBA MK7559GSXF disk0 : (750.16 GB)
            disk0s1 (disk0s1) <not mounted> : 210 MB
            Seagate Backup Plus Drive (disk0s2) / : 749.30 GB (325.92 GB free) - 29 errors
            Recovery HD (disk0s3) <not mounted>  [Recovery]: 650 MB
        MATSHITADVD-R   UJ-898
    USB Information: ℹ️
        Seagate Backup+ Mac SL 1 TB
            disk1s1 (disk1s1) <not mounted> : 210 MB
            External Backup Time Machine (disk1s2) /Volumes/External Backup Time Machine : 999.86 GB (681.13 GB free)
        Apple Inc. BRCM2070 Hub
            Apple Inc. Bluetooth USB Host Controller
        Apple Inc. Apple Internal Keyboard / Trackpad
        Apple Inc. FaceTime HD Camera (Built-in)
        Apple Computer, Inc. IR Receiver
    Thunderbolt Information: ℹ️
        Apple, Inc. MacBook Pro
    Configuration files: ℹ️
        /etc/hosts - Count: 42
    Kernel Extensions: ℹ️
            /System/Library/Extensions
        [loaded]    com.sophos.kext.sav (9.2.0 - SDK 10.8) [Click for support]
        [loaded]    com.sophos.nke.swi (9.2.0 - SDK 10.8) [Click for support]
    Launch Agents: ℹ️
        [not loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
        [loaded]    com.adobe.CS5ServiceManager.plist [Click for support]
        [running]    com.brother.LOGINserver.plist [Click for support]
        [loaded]    com.divx.dms.agent.plist [Click for support]
        [loaded]    com.divx.update.agent.plist [Click for support]
        [running]    com.sophos.uiserver.plist [Click for support]
    Launch Daemons: ℹ️
        [loaded]    com.adobe.SwitchBoard.plist [Click for support]
        [loaded]    com.microsoft.office.licensing.helper.plist [Click for support]
        [running]    com.sophos.common.servicemanager.plist [Click for support]
    User Launch Agents: ℹ️
        [loaded]    com.adobe.AAM.Updater-1.0.plist [Click for support]
        [failed]    com.apple.CSConfigDotMacCert-[...]@me.com-SharedServices.Agent.plist
        [loaded]    com.google.keystone.agent.plist [Click for support]
    User Login Items: ℹ️
        iTunesHelper    UNKNOWN Hidden (missing value)
        Dropbox    Application  (/Applications/Dropbox.app)
        VerizonUpdateCenter    UNKNOWN  (missing value)
        Google Chrome    Application Hidden (/Applications/Google Chrome.app)
        K9-MacOptimizer    UNKNOWN  (missing value)
    Internet Plug-ins: ℹ️
        Flip4Mac WMV Plugin: Version: 3.2.0.16   - SDK 10.8 [Click for support]
        JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Check version
        DivX Web Player: Version: 3.2.1.977 - SDK 10.6 [Click for support]
        OVSHelper: Version: 1.1 [Click for support]
        LogMeIn: Version: 1.0.970 - SDK 10.7 [Click for support]
        QuickTime Plugin: Version: 7.7.1
        LogMeInSafari32: Version: 1.0.970 - SDK 10.7 [Click for support]
        Google Earth Web Plug-in: Version: 6.0 [Click for support]
        SharePointBrowserPlugin: Version: 14.2.3 - SDK 10.6 [Click for support]
        Silverlight: Version: 5.1.10411.0 - SDK 10.6 [Click for support]
        iPhotoPhotocast: Version: 7.0 - SDK 10.8
    Safari Extensions: ℹ️
        Twitter for Safari
        AllMyTube
        comicSansBeGone
        Better Facebook
    3rd Party Preference Panes: ℹ️
        Flip4Mac WMV  [Click for support]
        Growl  [Click for support]
    Time Machine: ℹ️
        Time Machine not configured!
    Top Processes by CPU: ℹ️
             3%    WindowServer
             1%    Activity Monitor
             1%    activitymonitord
             0%    ps
             0%    SophosUIServer
    Top Processes by Memory: ℹ️
        266 MB    mds
        180 MB    InterCheck
        120 MB    Finder
        94 MB    System Preferences
        77 MB    coreservicesd
    Virtual Memory Information: ℹ️
        4.98 GB    Free RAM
        1.81 GB    Active RAM
        572 MB    Inactive RAM
        1.22 GB    Wired RAM
        34.27 GB    Page-ins
        2.72 GB    Page-outs
    Diagnostics Information: ℹ️
        Mar 6, 2015, 08:16:26 PM    /Users/[redacted]/Library/Logs/DiagnosticReports/quicklookd_2015-03-06-201626_[ redacted].crash
        Mar 4, 2015, 11:56:25 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/quicklookd_2015-03-04-115625_[ redacted].crash
        Mar 4, 2015, 11:55:37 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/quicklookd_2015-03-04-115537_[ redacted].crash
        Mar 4, 2015, 11:53:07 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/quicklookd_2015-03-04-115307_[ redacted].crash
        Mar 4, 2015, 11:52:42 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/quicklookd_2015-03-04-115242_[ redacted].crash
        Mar 4, 2015, 11:52:41 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/quicklookd_2015-03-04-115241_[ redacted].crash
        Mar 4, 2015, 11:33:39 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/QuickLookUIHelper_2015-03-04-1 13339_[redacted].crash
        Mar 4, 2015, 11:16:53 AM    /Users/[redacted]/Library/Logs/DiagnosticReports/iPhoto_2015-03-04-111653_[reda cted].crash
    TIME MACHINE BUDDY
    Starting standard backup
    Backing up to: /Volumes/External Backup Time Machine/Backups.backupdb
    Ownership is disabled on the backup destination volume.  Enabling.
    Backup content size: 394.3 GB excluded items size: 14.0 GB for volume Seagate Backup Plus Drive
    456.36 GB required (including padding), 930.57 GB available
    Waiting for index to be ready (101)
    Error: (-36) SrcErr:YES Copying /Library/Internet Plug-Ins/Flip4Mac WMV Plugin.plugin/Contents/Resources/WmvPluginPrefix.pch.pth to (null)
    Copied 50.7 GB of 380.3 GB, 637488 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Dropbox/Airport Packages/-Presentation/PSD originals/A-2769 Guava and java.psd to (null)
    Copied 136.5 GB of 380.3 GB, 652973 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/iLifeAssetManagement/state/pub/227354896+3231309460012822759/queue.sqli te3 to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73a83ed2b6f5f3f74e690a2ae7b99ef7515e76ae/ec3f6fda8662 e542ac7c67f2ebcfa860d3d2e7b6 to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/59ac936d3c1e 548ac04dfc28cd80ee7e8375e71c to (null)
    Copied 211.8 GB of 380.3 GB, 703468 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/878f9a9e9e99 35f370ab2a09d62665cafa4f723f to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/8ca38b8456a3 80c835e4535b71a6322258f782c5 to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/9d43f27ba634 c956751fb66aadb06f955e74b3c8 to (null)
    Copied 273.7 GB of 380.3 GB, 794840 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2014/01/10/20140110-100023/IMG_8819.JPG to (null)
    Copied 345.8 GB of 380.3 GB, 880149 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2015/02/21/20150221-163320/IMG_0946.JPG to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2015/02/21/20150221-163652/IMG_0878.JPG to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2015/02/26/20150226-202057/IMG_0789.MOV to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Previews/2015/02/21/20150221-162736/aNrBUprVRiGN3Ul+Yph5Jw/IMG_1181.jpg to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Previews/2015/02/21/20150221-162736/DDfJ%BYeR1mC2WtxQXpLdw/IMG_1180.jpg to (null)
    E
    In making an attempt to copy my files to a different external hard drive, I ran into several issues with document files that were "read-only" so the copying stops. (they were just a couple of pdfs and photos). I deleted all of those files. I then ran back up again after verifying the external I have designated for Time Machine. (Ive also completely erased, repaired and verified this drive several times over the past few weeks) Backup failed, again.
    I feel like my next move is to start deleting the "files" that are causing the errors listed above in TM Buddy (they are mostly photos in iphoto)... but then I realized that some of those errors are associated with the backing up of my iphone.
    Just now, I pasted a portion of my system log into Textedit, and the application just hanged... for 2 hours. I finally force quit it. 

    Hi!  I did exactly as you said. I was able to backup with my home folder excluded, but was not able to do so after I removed the exclusion. It crapped out 5G before finishing.
    Here's the TIME MACHINE BUDDY LOG:
    Starting standard backup
    Backing up to: /Volumes/External Backup Time Machine/Backups.backupdb
    Ownership is disabled on the backup destination volume.  Enabling.
    Backup content size: 394.3 GB excluded items size: 14.0 GB for volume Seagate Backup Plus Drive
    456.36 GB required (including padding), 930.57 GB available
    Waiting for index to be ready (101)
    Error: (-36) SrcErr:YES Copying /Library/Internet Plug-Ins/Flip4Mac WMV Plugin.plugin/Contents/Resources/WmvPluginPrefix.pch.pth to (null)
    Copied 50.7 GB of 380.3 GB, 637488 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Dropbox/Airport Packages/-Presentation/PSD originals/A-2769 Guava and java.psd to (null)
    Copied 136.5 GB of 380.3 GB, 652973 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/iLifeAssetManagement/state/pub/227354896+3231309460012822759/queue.sqli te3 to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73a83ed2b6f5f3f74e690a2ae7b99ef7515e76ae/ec3f6fda8662 e542ac7c67f2ebcfa860d3d2e7b6 to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/59ac936d3c1e 548ac04dfc28cd80ee7e8375e71c to (null)
    Copied 211.8 GB of 380.3 GB, 703468 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/878f9a9e9e99 35f370ab2a09d62665cafa4f723f to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/8ca38b8456a3 80c835e4535b71a6322258f782c5 to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Library/Application Support/MobileSync/Backup/73f862553779c33821fe63b50ba4008f4ae89038/9d43f27ba634 c956751fb66aadb06f955e74b3c8 to (null)
    Copied 273.7 GB of 380.3 GB, 794840 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2014/01/10/20140110-100023/IMG_8819.JPG to (null)
    Copied 345.8 GB of 380.3 GB, 880149 of 970893 items
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2015/02/21/20150221-163320/IMG_0946.JPG to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2015/02/21/20150221-163652/IMG_0878.JPG to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Masters/2015/02/26/20150226-202057/IMG_0789.MOV to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Previews/2015/02/21/20150221-162736/aNrBUprVRiGN3Ul+Yph5Jw/IMG_1181.jpg to (null)
    Error: (-36) SrcErr:YES Copying /Users/sandi/Pictures/iPhoto Library/Previews/2015/02/21/20150221-162736/DDfJ%BYeR1mC2WtxQXpLdw/IMG_1180.jpg to (null)
    E

  • Time Machine deleted "expired" backups. Why?

    I want to know why Time Machine deleted some backups although the disk has plenty of free space available.
    02/05/15 09:46:39,191 com.apple.backupd[91015]: Starting automatic backup
    02/05/15 09:46:39,281 com.apple.backupd[91015]: Backing up to /dev/disk2s2: /Volumes/Backup2/Backups.backupdb
    02/05/15 09:46:42,900 com.apple.backupd[91015]: Will copy (429,3 MB) from SSD Boot
    02/05/15 09:46:42,968 com.apple.backupd[91015]: Will copy (1,45 GB) from USERS1
    02/05/15 09:46:42,969 com.apple.backupd[91015]: Found 1675 files (2,19 GB) needing backup
    02/05/15 09:46:42,980 com.apple.backupd[91015]: 8,51 GB required (including padding), 1,49 TB available
    02/05/15 09:47:21,437 com.apple.backupd[91015]: Copied 1665 items (440,8 MB) from volume SSD Boot. Linked 1991.
    02/05/15 09:50:03,429 com.apple.backupd[91015]: Copied 85 items (1,75 GB) from volume USERS1. Linked 2582.
    02/05/15 09:50:11,048 com.apple.backupd[91015]: Created new backup: 2015-05-02-095010
    02/05/15 09:50:11,753 com.apple.backupd[91015]: Starting post-backup thinning
    02/05/15 09:50:20,156 com.apple.backupd[91015]: Deleted /Volumes/Backup2/Backups.backupdb/iMac van Hans/2015-04-30-230300 (855,9 MB)
    02/05/15 09:50:22,363 com.apple.backupd[91015]: Deleted /Volumes/Backup2/Backups.backupdb/iMac van Hans/2015-04-30-215910 (308,4 MB)
    02/05/15 09:50:24,766 com.apple.backupd[91015]: Deleted /Volumes/Backup2/Backups.backupdb/iMac van Hans/2015-04-30-205523 (38,2 MB)
    02/05/15 09:50:25,756 com.apple.backupd[91015]: Deleted /Volumes/Backup2/Backups.backupdb/iMac van Hans/2015-04-30-195405 (36,8 MB)
    02/05/15 09:50:27,671 com.apple.backupd[91015]: Deleted /Volumes/Backup2/Backups.backupdb/iMac van Hans/2015-04-30-185319 (36,6 MB)
    02/05/15 09:50:27,672 com.apple.backupd[91015]: Post-backup thinning complete: 5 expired backups removed
    02/05/15 09:50:27,709 com.apple.backupd[91015]: Backup completed successfully.
    Backups are alright so it is not an important issue but I am wondering if something in my preferences set is wrong.
    Hans

    Time Machine keeps hourly backups for one day, then daily backups for a week, etc. What you are seeing is it deleting the daily backups form more than 24 hours ago. This is what it does, nothing to worry about.
    C.

  • Time machine makes 30 backups for the last two days, no backups for any earlier times: is there a way to control it?

    I've been running Time Machine in the background for as long as I've owned my current Mac--- a few months.  It is a completely generic set-up: it's a desktop (rarely shut off or asleep) connected to an external hard drive that is much larger (1 TB) than my internal hard drive (0.5 TB), and Time Machine is configured to save backups of my whole internal drive to the external drive.  The external is half-full, and the internal is a little more than half-full.  I often hear my external crunching away, working on something.
    I recently needed to access an old file, so I went into Time Machine mode on the folder where it had been deleted a few weeks ago.  While I'm not upset that it isn't available (it's my own fault for deleting it), I didn't expect the Time Machine to have such a bad distribution of saved backups.  There are 30 backup snapshots of the past two days, and nothing earlier.  I was expecting something more like a few from today, a few from this week, a few from this month, and a few going all the way back in time--- a broader distribution.
    I don't see any way to control this in the Time Machine Preferences (in fact, very little control at all).  Is there a secret way to control it, or some tip to ensure a more useful distribution of saved snapshots?
    Thanks,
    -- Jim

    Thanks, but it doesn't exactly address my question.  TimeMachineEditor allows me to set the intervals or times when backups occur, but it doesn't control the algorithm that decides which snapshots should be deleted.  My problem was that Time Machine chose to delete all of the old snapshots and keep only the most recent ones: I'd like it to keep more of the recent ones than the old ones, but still keep some old ones.
    In fact, the (unmodifyable) text on the Time Machine control panel says that it keeps:
    hourly backups for the past 24 hours
    daily backups for the past month
    weekly backups for all previous months
    That would be perfect if it were true.
    Perhaps the algorithm did the wrong thing because the size of my internal hard drive varied quite a lot a few days ago: a process got out of control and used up all of my internal disk space.  I killed the process and deleted its output (several times), so my internal disk eventually went back down to normal.  Perhaps in the intervening hours, Time Machine made a backup, once an hour, and used up all of the external drive space.  When it had to choose between keeping "weekly backups of previous months" and "hourly backups of the past 24 hours", it chose to keep hourly backups of the past 24 hours.  This was the wrong choice in my case (it was the unwanted output) and is probably the wrong choice in most cases.
    Is there a way to control the algorithm that decides which backups to keep and which to delete?  I would have it delete the hourly, daily, and weekly backups in a way that preserves their relative distribution.
    By the way, while I have made it sound like my problem was a runaway log file (something that would be easy to put in an excluded directory with Time Machine's "Options" button), it was a VirtualBox snapshot merge.  The data in question are precious, but were unnecessarily copied many times while VirtualBox failed to merge them properly.  I can't simply exclude a directory: I'm talking about a more general problem.
    Thanks!
    -- Jim

  • Time Machine: "Partially Deleted Backup"

    Last night, after Time Machine performed a backup and began its post-backup thinning, it got stalled on "Finishing backup... ." The system log showed that it was attempting to delete a previously partially deleted backup:
    Starting standard backup
    Starting post-backup thinning
    Found partially deleted backup - trying again to delete: 2009-09-30-110803
    The backup it was trying to delete was the last one on its list (i.e., the oldest one on that TM volume). And when I opened it up, it indeed appeared to be a partially deleted folder. So I let TM run. However, it never finished "Finishing backup... ," so after letting it run all night and all day, I simply told TM to stop. It did, and the system then added two more messages to the log, acknowledging my cancelation as well as TM's current success:
    Starting standard backup
    Starting post-backup thinning
    Found partially deleted backup - trying again to delete: 2009-09-30-110803
    Backup deletion was canceled by user
    Backup completed successfully.
    However, the next time TM ran, it began all over again:
    Starting standard backup
    Starting post-backup thinning
    Found partially deleted backup - trying again to delete: 2009-09-30-110803
    It's still sitting there in its "Finishing backup..." mode.
    I was thinking about entering Time Machine, selecting that backup, and telling Time Machine to delete that backup—and only that backup. But I'm (a) not sure that will address the actual problem, and (b) wondering if deleting that particular backup (i.e., the oldest one on the list) is advisable.
    Suggestions?

    Pondini wrote:
    Maxwell’s Demon wrote:
    I'm aware of the multilink nature of TM's backups. What I don't understand is how you immediately concluded that the backups were corrupted.
    TM finding partially deleted backups, trying repeatedly to deleted them, and failing to.
    (And yes, I though you meant that you'd tried to delete the backup yourself.)
    It took forever. I ran TechTool Pro, and it "choked" (i.e., ran out of memory) trying to rebuild the directory. When I asked Disk Warrior to graph the directory, it revealed that it was more than 40% fragmented!
    I'm not sure fragmentation is a problem, or even applies, given the structure of TM backups.
    So I ran Disk Warrior. It ran without incident. When I then looked inside the TM drive, I discovered that along with rebuilding the directory—which is what I understood its job to be—DW apparently removed/deleted the offending (partially deleted) backup. The next time Time Machine ran, everything went smoothly. It's been running fine ever since.
    Great! And yes, there are times it can repair/rebuild TM backups that nothing else can (I guess that's why it costs $100!).
    I'm obviously quite pleased with the results: Not only did DW perform an incredible directory rebuild (fragmentation went from more than 40% to less than 1% !!) but it cleared out the partially deleted backup that was causing TM to stumble. But I remain awfully curious: Had I simply gone into Time Machine and deleted the partially deleted backup myself, wouldn't that have fixed the problem? (Granted, DW not only got TM back on track, but it also rebuilt its directory, which is a definite plus in my mind...I'm just trying to understand.)
    It's possible you couldn't have deleted it completely, any more than TM was able to. Remember, a single backup folder has hard links to hundreds, thousands, or hundreds of thousands of other items. Just one of those being screwy can have a ripple effect through the whole structure.
    And if you could have, it might well have left some of the actual backup files "abandoned" -- some or all of the hard links to them deleted, but still somewhere in the disk directory, so still taking up space.
    I got the idea from
    http://www.macosxhints.com/article.php?story=20090515063602219
    which provided a link to the "solution" when partial backups remain that result in TM "error: 11" failures:
    http://www.bytebot.net/blog/archives/2008/08/13/fixing-time-machine-backup-faile d-with-error-11
    Admittedly, mine wasn't an "error: 11" problem, but it sure seemed similar. My hesitation/concern was due to the fact that the partially deleted backup was the last one (i.e., the "oldest") in my TM volume: I wasn't sure if deleting it would screw up all of the links used by the remaining backups. However, since DW removed it without causing any problems, it seems like I may have been able to accomplish the same result by removing it "manually" from within TM. If that is the case, then it suggests that there may not have been any actual "corruption."
    Again, I am very happy with the result, and likely will resort to DW again the next time I have similar problems. The only reason I'm harping on it is simply to try to gain a deeper understanding of how to determine when such problems are indeed due to corruption as opposed to simply an errant file that causes TM to stumble. (Had TM indicated that it stumbled and was unable to successfully perform the backup, then I would have little doubt that there was actual corruption.)

  • Time Machine Very Large Backup Space Requirements

    I'm having a bit of trouble with Time Machine.  I recently recreated a User Account.  The old User account's home library permissions had become corrupt.  Rather than try to sort through the permissions, I opted to just move all the personal data to another account (the primary admin), delete the old user account, recreate it, and move all the personal data to the new account.  This worked splendidly.  However, now Time Machine claims it needs about 2.1 TB to do it's next backup.  I find this odd because a full backup is estimated as only 384 GB, and the computer's hard drive is only 1 TB to begin with.  So, it needs a factor of 2 more space than is available on the computer.  So, there is something amiss.  I imagine Time Machine tracked the data being moved to the admin account and to the new account, and it wants to back all of this up.  I don't want it to do that.  Is there someway to cause Time Machine to forget the most recent changes?
    Clearly, I don't want Time Machine to not backup the new account's information.  However, I'm would like not to loose the previous backups.  Any solutions?

    Hello again:
    Erasing and then formatting the Time Machine volume and having Time Machine make a new backup would be the way I would do it.
    As an aside, I use two external hard drives.  I have Time Machine set to make alternating backups on the externals, and I also make a bootable clone (SuperDuper!) on one of the externals.  Short of a meltdown, I am reasonably well protected.
    Barry

  • Carbon Clone and Time Machine: developing a backup plan

    Howdy all!
    This is a second post that sort of flows on from another I have written today
    https://discussions.apple.com/thread/4649740
    I initally put them all together, but they were too rambling and disconnected, so it seemed better to seperate them. The question I have here is how best to organise my backup plan? I have a few ideas, but, basically, want to make sure I get the whole setup right the first time and would appreciate any advice from others that have been down the path before. As I am still waiting for some parts to arrive in the mail, I have a little time to think about how to go about setting up my Mac.
    Basically the setup is:
    Mac Mini 2012, boot drive is a Samsung 256GB 830 series SSD, seconday drive for data is a 1TB mechanical disk. I plan on having all my data on the seconday mechanical disk (photos, movies, music etc) and only the OS and Applications on the SSD. To this end, I understand I only have to move /Users to the mechanical disk to achieve this. I then also have 2x 2TB Western Digital MyBook Essential USB 3 disks for Time Machine backups. I plan on rotating them on a weekly basis (storing the disk not in use in a safe or offsite), and then, depending on costs a cloud backup service for some data (music, photos etc) which I might want to access when im not at home.
    So I have been thinking for a few days now on the benefit of having a Carbon Clone bootable recovery drive. The thinking goes along these lines. As my data is on a seperate drive, and is backed up to Time Machine, in the event of an OS disk failure, I can replace the disk and then point /Users to the new drive, and I can be up and running once I have reinstalled the apps i need. Now, I understand the idea of the Carbon Clone backup is such that it speeds up the time to rebuild the OS disk, but I have to question, how useful is this in reality?
    Consider, I can sit down now and write down all the apps I have needed in the past, install Mac OS, set it up (possibly with a generic admin password), install the apps I need from the App store and DVDs etc and then take a Carbon Clone at this point before any setup of Apps are done. If the apps configuration is backed up in the Time Machine backup (i.e.: the config files exist under /Users) then this is almost workable - in a recovery situation, the CC clone is used to rebuild the OS drive, the config files are pulled from the TM backups, and we're back up and running. Where this fails, is if I have installed (or removed) apps since the CC clone was made. At this point then, is it best to (a) make a new clone when a new app is added/removed or (b) make a note of apps added/removed, which will then have to be reinstalled if a recovery is required. I tend to think the (b) method is best here, as it preserves the integrity of the clone. If the machine has been compromised (malware etc) then remaking the clone, causes the clone to be compromised and hence the reinstalled machine as well. Though this method could be a pain if the machine state has changed somewhat over time. Also, it means that the reinstalled system will be missing updates etc which could be time consuming to apply anyway, so the usefulness of a clone is slightly reduced anyway.
    Does anyone have any thoughts on this? Some days I think having a clone will be useful esp. as most of my software was delivered on CD (Adobe Creative Suite, Office) or are large install bases (XCode), but other days I think, "its not a mission critical machine", i can survive a day without it while I rebuild the install, and so I dont achieve much by having a clone which is likely out-of-date by the time I go to use it.
    Also, in this backup plan, is it best to rely on TM for things like email backup or a dedicated mail backup utility? can a Carbon Clone exist on the same disk as Time Machine uses, or do I need to invest in a new disk or two for the CC clones?
    As I say, I want to make sure I have this machine setup right from the start, and would really appreciate any pointers, tips or advice.

    There is one big advantage of a clone.  You can immediately reboot
    to it and continue working and deal with the regular boot drive faiure,
    what ever it may be, later.  Especially since all your data and such
    is on another drive.  If you use your computer for work and time
    critical projects, this is a major plus!
    In the case of a hard drive failure/replacement, copying the clone
    to the drive is the fastest way to get the system and all your settings
    back.
    Time Machine and incremental backups have a place as well.  It is best
    suited for "incremental" problems.  Examples are installing an upgrade to
    software that doesn't work or just don't plain like.  With Time Machine it
    is easy to just restore back to the point before the install.
    Something else I do is backup current project files to USB memory sticks.
    If you are using your computer for business, you can never have too many
    backups.  Coralllary 456 of Murphy's Law is the "number of backups that
    you need will be one more than what you have!"

  • When time machine does a backup I get an error message

    Added a new Seagate 3T external as a backup drive Every time Time Machine does a backup I get an error message that the disk was not ejected properly, no bid deal just a pain. System 3.5GHz Intel Core i7... 16GB DDR# memory ... OSX 10.8.4.  How do I get rid of this error??

    Notes/Tips on OS X 10.8.5 External Drive Eject During Sleep:
    Updated the previous page on OS X 10.8.5 Problems/Notes and Tips with more info regarding external drive 'eject' in sleep and on drives going to sleep/spinning down despite ES settings. I ran some tests with drives I had but so far have not seen those problems with my setup/drives at least. Apparently many have based on the still growing number of threads on the subject in Apple's Mountain Lion forum.
    ... you posted inaccurate information about a Mac that I pointed out.
    Posts from and about Hackintosh do get removed.

  • Beware: Time Machine doesn't backup MySQL databases regularly!

    I have a Mac OS X Server which runs as a webserver. I had to replace the internal harddisk, which is backupped with TM too. So after replacement I restored the system from the TM backup and discovered that I lost some database content. The contents of the restored database content was several days old. This means that TM doesn't backup the database hourly.
    FYI I had backupped the database myself to be sure, so I didn't lost any data. But it took some extra work after restoring. All other files on the server were okay.

    I'm making an assumption here... but your post doesn't have a ton of detail about your setup so...
    It probably has more to do with the fact that you actually shouldn't be backing up a mysql database with time machine if the database is running/live (Of which Time machine has no idea about any of this).
    You can't backup open database just like that and it doesn't only apply to time machine. You need to first be doing a dump of the database either manually or with an automated script and then you could allow time machine to backup the dump. You're asking for trouble and behavior similar to what you noticed here if you backup a mysql (or any other open database) in this manner. This includes the LDAP database if this machine is an OD master and cyrus database if you run the OS X mail server (pre 10.6).
    Just an FYI that it is quite likely that time machine backed up the files in question but that the database was probably damaged or missing data for the reasons I mentioned above.
    There are tools out there that can automate this process (mysql website itself has a Mac GUI client that can do automated backups).

  • Time Machine says the backup is too large but it is not

    Time Machine says the backup is too large but it is not.
    While it is true my hard drive is very full (150 Gb used of the available 160Gb), this is way less than 42 Pb!!!!
    I have tried numerous time to reset it and still the same issue.
    Here is the reoccurring message:
    Advice?

    PB.. what the heck is a PB.. I kind of thought TB are still in fairly low digits.
    Do a disk verify.. something is seriously stupidly wrong.. Otherwise ring Apple support and give them an earful about nonsense popups.
    http://pondini.org/TM/Troubleshooting.html  A5

  • Time machine reports erroneous backup size

    I had my TM disk disconnected for about a week and now when I reconnect it, I get:
    Time Machine Error
    This backup is too large for the backup disk. The backup requires 499.48 GB but only 492.29 GB are available.
    However, my get info reports that only 223.73 GB are currently in use. Any ideas? I'm repairing permissions now and, if that doesn't work, I was thinking to try rebooting and repairing the disk, but if anyone has an alternative suggestion, I'd be grateful. I've actually just gone ahead and removed all my old backups, and emptied the trash, so the backup disk should be entirely open for anything.
    Any help would be much appreciated!

    That has nothing to do with the backup drive.   That's what Time Machine thinks is everything that's subject to being backed-up on your internal HD (and any others being backed-up).  
    For some reason, it's trying to do a full backup of that (and it adds 20% to the estimated size, for workspace, etc., so it gets the 499 GB in the message).
    Try the Verify Disk (not permissions) on your internal HD again, per #A5 in Time Machine - Troubleshooting.
    It's also possible the preferences file (where the exclusions, etc., are kept) is somehow corrupted.  Try a "full reset" of Time Machine, per #A4 in that same link.
    Also see #D3 there, for possible causes of a full backup.

Maybe you are looking for