Time Machine full backup started... why!?

Installed Mavericks, played around a bit, time machine was behaving normally until today.
I thought the usual backup was starting, not so many changes since last one, maybe a couple of giga of new photos to add but Time Machine decided instead to delete the whole content and start from scratch.
My time machine disk is 1.5TB my full backup will be under 1.20TB, and again Mavericks was already backing up normally since I installed that... so what caused this absurd behaviour?
If this is not a bug, what else? Because of this at the moment I have no backup, time machine is working and if I am lucky it'll take one full day or two to have a backup again.

troyboy65 wrote:
I dont understand why when the total of the 2 machines only totals 500gb
Time Machine keeps copies of everything currently on your Mac, plus copies of things you've changed or deleted. It varies widely depending on how you use your Mac, but Time Machine generally needs 2-3 times the space of the data it's backing-up, to be able to keep a reasonable "depth" of backups for you.
Is there some settings i need to change or is something wrong?
Probably neither.
If both Macs are running Snow Leopard, you may be getting notices like the one in the blue box in #C4 of Time Machine - Troubleshooting. You can stop those notices if you want.
If either is on Leopard, it's a different story. When Time Machine on a Mac running Leopard runs out of room, and the +Warn when old backups are deleted+ option is checked, it fails with a message like the one in the tan box in #C4. Remove the check from the box, and it will start deleting old backups.
But if you're getting the message in the pink box, something is likely wrong. See the suggestions and explanations there.

Similar Messages

  • Time Machine nuking backups, starting from scratch!

    ok, i just received this warning:
    and now i't doing a backup that is slated to take more than "several hours."
    is this common? how often can i expect this?

    Hello,
    Should you click “Start New Backup”? Not yet! If you see the dialog above, your existing Time Machine backup is corrupt, and you might not be able to recover data from it. But you can save a copy of the corrupt bundle and, perhaps, extract some data from it if needed.
    Ask yourself if Time Machine has saved data you might need before deciding what to do next:
    If you are sure you won’t need anything backed up before today, click “Start New Backup” and let Time Machine do its thing.
    Otherwise, click “Back Up Later” and save a copy before letting Time Machine start a new backup. Just look for a file called “computername.sparsebundle” (for network backups) or “Backups.backupdb” (for local ones) and create a copy with a different name. You can open sparsebundle files with DiskImageMounter and browse them like any other disk. More information is available here.
    There you go. If you click “Start New Backup” when you see this dialog box, Time Machine will erase all of your old backup data and start a new bundle. It won’t be corrupt, but it will be empty.
    Note that you can manually initiate a Time Machine backup integrity check by option-clicking the “Time Machine” icon in the menu bar and selecting “Verify Backups.”
    http://blog.fosketts.net/2010/08/11/time-machine-completed-verification-backups- improve-reliability-time-machine-create-backup/
    According to This Time Machine resource   “This appears only on Snow Leopard, and started with the Time Capsule Backup Update 1.0 in mid-May of 2010.  It also seems to have been included in the 10.6.3 v1.1 update and 10.6.4.”
    So, what can you do about it?  Grin and bear it, it seems, until Apple fixes it.
    One thing you can do to make the backup take less time is to connect your machine to your Time Capsule or other backup drive via Ethernet for the duration of the initial backup.
    http://www.theinternetpatrol.com/the-dreaded-time-machine-has-completed-a-verifi cation-of-your-backups-to-improve-reliability-time-machine-must-create-a-new-bac kup-for-you-message-and-why-you-are-seeing-it/
    Time Machine: About "Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you."...
    http://support.apple.com/kb/HT4076

  • Time machine full backup after disk and disk permissions repair

    my macbook would not boot so i inserted the snow leopard DVD and did a disk repair and disk permissions repair, after that it booted perfectly but when it went to do a backup it did a full backup of 149GB , i am unsure why it has done this and would like to know how to stop it as i am trying to save space on my time capsule.
    thank you in advance

    Brycycle wrote:
    i do not wish to let it do a full backup so as to save space on my time capsule but this is the log up till when it started transferring data.
    I'm afraid you don't have much choice. You do have lot of space available, though.
    Node requires deep traversal:/ reason:must scan subdirs|new event db|
    No pre-backup thinning needed: 165.92 GB requested (including padding), 507.60 GB available
    The "deep traversal" means TM compared everything on your system to the backups, and estimates that about 138 GB is new/changed (it adds 20% for workspace on the TM disk - the "padding" in the message).
    If there's about 138 GB on your system, see #D3 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum), for some common reasons for TM to do a new full backup.
    If there's more, #D4 there has some common reasons for large backups.
    If all you did was repair disk and permissions, neither should have resulted.
    the reason i did a permission repair and disk repair while running from the install disk was because my laptop would not boot from the internal disk so i did both just to be safe.
    That's fine; just do the Permissions Repair again, while running normally.

  • Time Machine Full backup after disk move

    I have followed the instructions for moving my Time Machine backup to a new disk as per instructions here.  However, once I have completed the copy to the new disk, the first time that time machine runs, it seems to be do a full new backup and therefore there is not enough room on the new disk. 
    I get the following error: Time Machine could not complete the backup.  This backup is too large for the backup disk.
    Please help, this is driving me nuts.
    Thanks,
    Ian.

    Peeps, I am so sorry, I am such an idiot, I have just realise what I have done wrong!!!
    Whilst trying to build my new drive (part of which is to be my new Time Machine backup) I created a 500gb backup in my local Documents folder - this is why my initial Time Machine backup was so large, not because Time Machine was trying to do a full backup!!!
    Thanks for looking,
    Ian.

  • Force Time Machine Full Backup

    I wanted to update my Macbook Pro with a new Hard Disk, after preparing & installing the new HD and then chossing to restore from the Time Machine, i was surpised that the Time Machine showed me only some Backups(Full Backups), and the last full backup was 6 Months old, although i did a TM Backup just before installing the new HD, but apprently it is an incremntal backup, therfore it was not shown in the list.
    So my question is how to force a TM Full Backup so that i can just restore it on the new HD. I know i can do it if i deleted all the old Backups, but i want to keep them, is it possible?

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
              <key>sourcePaths</key>
              <array>
                        <string>/</string>
              </array>
              <key>standardExclusionPaths</key>
              <array>
                        <string>/.MobileBackups</string>
                        <string>/MobileBackups.trash</string>
                        <string>/.MobileBackups.trash</string>
                        <string>/.Spotlight-V100</string>
                        <string>/.TemporaryItems</string>
                        <string>/.Trashes</string>
                        <string>/.com.apple.backupd.mvlist.plist</string>
                        <string>/.fseventsd</string>
                        <string>/.hotfiles.btree</string>
                        <string>/Backups.backupdb</string>
                        <string>/Desktop DB</string>
                        <string>/Desktop DF</string>
                        <string>/Network/Servers</string>
                        <string>/Library/Updates</string>
                        <string>/Previous Systems</string>
                        <string>/Users/Shared/SC Info</string>
                        <string>/Users/Guest</string>
                        <string>/dev</string>
                        <string>/home</string>
                        <string>/net</string>
                        <string>/private/var/db/com.apple.backupd.backupVerification</string>
                        <string>/private/var/db/efw_cache</string>
                        <string>/private/var/db/Spotlight</string>
                        <string>/private/var/db/Spotlight-V100</string>
                        <string>/private/var/lib/postfix/greylist.db</string>
                        <string>/Volumes</string>
                        <string>/Network</string>
                        <string>/automount</string>
                        <string>/.vol</string>
                        <string>/tmp</string>
                        <string>/cores</string>
                        <string>/private/tmp</string>
                        <string>/private/Network</string>
                        <string>/private/tftpboot</string>
                        <string>/private/var/automount</string>
                        <string>/private/var/folders</string>
                        <string>/private/var/run</string>
                        <string>/private/var/tmp</string>
                        <string>/private/var/vm</string>
                        <string>/private/var/db/dhcpclient</string>
                        <string>/private/var/db/fseventsd</string>
                        <string>/Library/Caches</string>
                        <string>/Library/Logs</string>
                        <string>/System/Library/Caches</string>
                        <string>/System/Library/Extensions/Caches</string>
                        <string>/private/var/log</string>
                        <string>/private/var/spool/cups</string>
                        <string>/private/var/spool/fax</string>
                        <string>/private/var/spool/uucp</string>
              </array>
              <key>systemFilesExcluded</key>
              <false/>
              <key>userExclusionPaths</key>
              <array/>
    </dict>
    </plist>

  • Time machine full backup

    Why does my computer start a new backup series every week / 10 days now? Never used to with Lion.

    It backs up every hour which is OK but the frequency of starting a new backup has increased dramatically since I switched to Mountain Lion.
    It now wants to start a new backup every week to 10 days and it takes forever to do a new full backup.

  • Restore Time Machine Full Backup After Catastrophic Failure

    I am new to the Mac and using Time Machine as my primary backup utility. My concern is the way it creates one full backup at the beginning and only incremental ones after that. If the full backup gets overwritten due to the program needing hard drive space, does it know to create another full backup, even if it needs to delete some older incremental backups?
    I am concerned I will need to complete a full restore at some point, and will not be able to do so because there will not be a full backup present on the Time Machine disk.
    Also, who has had to restore from a catastrophic disk failure using an external time machine disk? Is this easy? Does it work properly?

    you concerns are unfounded. due to the way TM keeps data organized every backup is full and independent of any other backups.
    when TM makes a backup it only backs up afresh new and changed files. everything else is _*hard linked*_ to existing backup copies.
    deleting an earlier backup to save space as TM does sometimes has zero effect on the remaining backups. they remain full and complete. doing a full system restore from TM is very easy. you boot from the SL install DVD and select "restore system from backup" from Utilities menu.
    However, it should be noted that TM is still very buggy and doing a full restore can not be tested until you actually do it. therefore, it's advisable to have a double backup using a different backup tool. bootable clones are the best for doing a full restore. CCCloner and Superduper are excellent cloning backup programs.

  • FYI: No Sleep during Time Machine initial backup

    Just an FYI - I noticed that during the first Time Machine full backup, the computer does not go to sleep.
    I would also assume that if you computer is asleep, it will not wake for each hourly backup.

    Hi, and welcome to the forums.
    You need to know that backing-up that way is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).
    Kernel panics are usually caused by hardware problems, but can be software.
    Disconnect all peripherals, except keyboard and mouse. Reconnect one at a time to see if you can find the culprit.
    If that's no help, run the Apple Hardware Test: http://support.apple.com/kb/HT1509
    And perhaps a heavy-duty memory test, such as the free Rember: http://www.kelleycomputing.com/
    More kernel panic info:
    Apple Support - About kernel panic messages
    Mac OS X Kernel Panic FAQ
    The X Lab - Resolving Kernel Panics
    Apple Developer - Technical Note TN2063: Understanding and Debugging Kernel Panics
    Tutorial: Avoiding and eliminating Kernel panics
    |
    If you still want to back up via the Airport, the first backup will be much faster if you connect via Ethernet.

  • HT1175 Time Machine wants to start with a new, full backup instead of using the existing one

    Hi, my Time Machine wants to start a new, full backup, instead of continuing with the existing one on the time Capsule.
    Looking a the Troubleshooting guide, I've found the following piece of info, which is, as 99% of the times with the troubleshooting guides, totally useless to resolve my problem...
    Message: Time Machine starts a new, full backup instead of a smaller incremental backup
    There are three reasons why this may occur:
    You performed a full restore.
    Your Computer Name (in Sharing preferences) was changed--when this happens, Time Machine will perform a full backup on its next scheduled backup time.
    If you have had a hardware repair recently, contact the Apple Authorized Service Provider or Apple Retail Store that performed your repair. In the meantime, you can still browse and recover previous backups by right-clicking or Control-clicking the Time Machine Dock icon, and choosing "Browse Other Time Machine disks" from the contextual menu.
    It should be noted (hence the uselessness of the guide) that:
    -I haven't performed ANY full restore
    - I havent changed my computer name
    - My computer has not had ANY repair, much less a hardware repair. Neither recently, nor in the 9 months I've owned it.
    Which puts me back to square one, with the marginal improvement that now I have a way of browsing my old backups.
    In the event I decide to start all over again, will there be a way for me to "sew" the two backup files?
    Or will I always have to go the silly way around?
    Anybody has any idea?
    Thank you for your time (machine/capsule, your choice;-)

    Hi John,
    no, that doesn't have anything to do with my problem.
    Just look at the image below.
    Time Machine thinks that the disk I've always used to do my backups has none of them.
    If I open the disk with Finder, obviously they are where they should be.
    It is even possible to navigate them as per the instruction reported above, but even following Pondini's advice #s B5 and B6 (which are more applicable to my problem) didn't solve the problem.
    Actually, not being a coder, I'm always scared of doing more damage than good when I have a Terminal window open.
    My question is: how is it possible that Apple hasn't thought of some kind of user command to tell the idiotic Time Machine software that a hard disk backup is a hard disk backup, no matter what?
    Estremely frustrating and annoying: I'm wasting HOURS in trying to find a solution to a problem that should not have arisen in the first place...
    Have a nice weekend
    Antonio

  • I recently did a full reinstall from my time machine and now my MacBook pro won't back up to the time machine. It starts a full backup ignoring the original back up, can anyone help?

    I recently did a full reinstall from my time machine and now my MacBook pro won't back up to the time machine. It starts a full backup ignoring the original back up, can anyone help?

    Did you follow the instructions on the page linked below?
    OS X Yosemite: Recover your entire system

  • HT3275 What do i do when, having reconnected my Time-Machine Backup disk, i'm told that there is not sufficient space to do a backup ? it seems somehow that my previous backup was "closed" and i cannot continue using it, so Time machine appears to start a

    I use an external 500 GB WD hard drive for my Time-Machine backup.
    Sometimes - several times - after i've disconnected the drive to go travelling, when i reconnect the external drive, Time Machine tries to resume but tells me there is not enough space on the drive, and to chose a bigger disk.
    It is as if the previous backup file is "closed' and cannot be written to again.
    The only fix i can find is to erase, start again from scratch and do a full backup from scratch - which totally defeats the purpose of Time Machine.
    I've tried repairing the disk, nothing appears to allow the previous backup to be continued.
    Suggestions please ??
    Jean-Noel Cozon

    Hi Linc,
    Thanks for getting back - if i understood correctly, the info you suggested i collect is hereunder ...
    Jan 22 06:08:09 MBP-15 com.apple.backupd[4353]: Starting standard backup
    Jan 22 06:08:10 MBP-15 com.apple.backupd[4353]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
    Jan 22 06:10:54 MBP-15 com.apple.backupd[4353]: No pre-backup thinning needed: 3.12 GB requested (including padding), 234.07 GB available
    Jan 22 06:18:20 MBP-15 com.apple.backupd[4353]: Copied 28083 files (2.2 GB) from volume MBP-15.
    Jan 22 06:21:57 MBP-15 com.apple.backupd[4353]: No pre-backup thinning needed: 3.13 GB requested (including padding), 231.88 GB available
    Jan 22 06:29:10 MBP-15 com.apple.backupd[4353]: Copied 23509 files (2.2 GB) from volume MBP-15.
    Jan 22 06:32:01 MBP-15 com.apple.backupd[4353]: Starting post-backup thinning
    Jan 22 06:32:01 MBP-15 com.apple.backupd[4353]: No post-back up thinning needed: no expired backups exist
    Jan 22 06:32:02 MBP-15 com.apple.backupd[4353]: Backup completed successfully.
    Jan 22 07:08:09 MBP-15 com.apple.backupd[4474]: Starting standard backup
    Jan 22 07:08:10 MBP-15 com.apple.backupd[4474]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
    Jan 22 07:10:52 MBP-15 com.apple.backupd[4474]: No pre-backup thinning needed: 3.13 GB requested (including padding), 231.88 GB available
    Jan 22 07:18:26 MBP-15 com.apple.backupd[4474]: Copied 28091 files (2.2 GB) from volume MBP-15.
    Jan 22 07:22:02 MBP-15 com.apple.backupd[4474]: No pre-backup thinning needed: 3.13 GB requested (including padding), 229.69 GB available
    Jan 22 07:29:22 MBP-15 com.apple.backupd[4474]: Copied 23517 files (2.2 GB) from volume MBP-15.
    Jan 22 07:32:14 MBP-15 com.apple.backupd[4474]: Starting post-backup thinning
    Jan 22 07:32:14 MBP-15 com.apple.backupd[4474]: No post-back up thinning needed: no expired backups exist
    Jan 22 07:32:15 MBP-15 com.apple.backupd[4474]: Backup completed successfully.
    Jan 22 08:08:10 MBP-15 com.apple.backupd[4595]: Starting standard backup
    Jan 22 08:08:10 MBP-15 com.apple.backupd[4595]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
    Jan 22 08:10:56 MBP-15 com.apple.backupd[4595]: No pre-backup thinning needed: 3.13 GB requested (including padding), 229.68 GB available
    Jan 22 08:18:19 MBP-15 com.apple.backupd[4595]: Copied 28099 files (2.2 GB) from volume MBP-15.
    Jan 22 08:21:50 MBP-15 com.apple.backupd[4595]: No pre-backup thinning needed: 3.14 GB requested (including padding), 227.49 GB available
    Jan 22 08:29:18 MBP-15 com.apple.backupd[4595]: Copied 23525 files (2.2 GB) from volume MBP-15.
    Jan 22 08:32:09 MBP-15 com.apple.backupd[4595]: Starting post-backup thinning
    Jan 22 08:32:09 MBP-15 com.apple.backupd[4595]: No post-back up thinning needed: no expired backups exist
    Jan 22 08:32:10 MBP-15 com.apple.backupd[4595]: Backup completed successfully.
    Jan 22 09:08:09 MBP-15 com.apple.backupd[4716]: Starting standard backup
    Jan 22 09:08:10 MBP-15 com.apple.backupd[4716]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
    Jan 22 09:10:55 MBP-15 com.apple.backupd[4716]: No pre-backup thinning needed: 3.13 GB requested (including padding), 227.49 GB available
    Jan 22 09:18:48 MBP-15 com.apple.backupd[4716]: Copied 28107 files (2.2 GB) from volume MBP-15.
    Jan 22 09:22:40 MBP-15 com.apple.backupd[4716]: No pre-backup thinning needed: 3.27 GB requested (including padding), 225.30 GB available
    Jan 22 09:32:35 MBP-15 com.apple.backupd[4716]: Copied 23533 files (2.3 GB) from volume MBP-15.
    Jan 22 09:35:25 MBP-15 com.apple.backupd[4716]: Starting post-backup thinning
    Jan 22 09:35:25 MBP-15 com.apple.backupd[4716]: No post-back up thinning needed: no expired backups exist
    Jan 22 09:35:26 MBP-15 com.apple.backupd[4716]: Backup completed successfully.
    Jan 22 10:08:09 MBP-15 com.apple.backupd[4840]: Starting standard backup
    Jan 22 10:08:10 MBP-15 com.apple.backupd[4840]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
    Jan 22 10:10:51 MBP-15 com.apple.backupd[4840]: No pre-backup thinning needed: 3.14 GB requested (including padding), 225.18 GB available
    Jan 22 10:18:12 MBP-15 com.apple.backupd[4840]: Copied 28115 files (2.2 GB) from volume MBP-15.
    Jan 22 10:21:49 MBP-15 com.apple.backupd[4840]: No pre-backup thinning needed: 3.14 GB requested (including padding), 222.99 GB available
    Jan 22 10:29:05 MBP-15 com.apple.backupd[4840]: Copied 23541 files (2.2 GB) from volume MBP-15.
    Jan 22 10:32:00 MBP-15 com.apple.backupd[4840]: Starting post-backup thinning
    Jan 22 10:32:00 MBP-15 com.apple.backupd[4840]: No post-back up thinning needed: no expired backups exist
    Jan 22 10:32:01 MBP-15 com.apple.backupd[4840]: Backup completed successfully.
    Jan 22 11:08:09 MBP-15 com.apple.backupd[4963]: Starting standard backup
    Jan 22 11:08:10 MBP-15 com.apple.backupd[4963]: Backing up to: /Volumes/Time-Machine MBP15 Backup/Backups.backupdb
    Jan 22 11:10:53 MBP-15 com.apple.backupd[4963]: No pre-backup thinning needed: 3.14 GB requested (including padding), 222.82 GB available
    Jan 22 11:18:10 MBP-15 com.apple.backupd[4963]: Copied 28123 files (2.2 GB) from volume MBP-15.
    Jan 22 11:21:46 MBP-15 com.apple.backupd[4963]: No pre-backup thinning needed: 3.14 GB requested (including padding), 220.63 GB available
    Jan 22 11:30:13 MBP-15 com.apple.backupd[4963]: Copied 23553 files (2.2 GB) from volume MBP-15.
    Jan 22 11:33:03 MBP-15 com.apple.backupd[4963]: Starting post-backup thinning
    Jan 22 11:33:03 MBP-15 com.apple.backupd[4963]: No post-back up thinning needed: no expired backups exist
    Jan 22 11:33:04 MBP-15 com.apple.backupd[4963]: Backup completed successfully.
    Currently, having once again yesterday flattened and restarted my T-M from scratch i probably overwrote all the backups since the last time i had to do that - and as long as i don't disconnect my external backup drive it seems OK now.
    I'm a bit paranoid as i use my MBP both as my Mac, but also as my Virtual PC so i have a lot of technical and commercial data which i need to keep properly backed up.
    Is it possible when i've ejected my TM backup disck, gone travelling, and then reconnected it some days later - that i am causing a new backup to start by hitting the 'Backup Now' command on the menu bar.... should i let TM pickup by itself automaticvally without porvoking a Backup Now command ?
    Thanks in advance for any futher advice

  • Time Machine thinks backup disk is full but its not

    I just purchased a new 1 Terabyte hard drive for backup. In the past I backed up both my internal Mac harddrive (250 Gb with 8gb free) and an external iOmega archive drive (DRIVE H 320Gb with 41Gb free) to a 500Gb Lacie drive. I purchased an iOmega 1 Terabyte drive (DRIVE G) because the Lacie drive was full. I went into Time Machine and changed the backup drive to the G one terabyte drive and did a full backup of my internal hard drive. When I did this I did not have the external H archive drive attached so Time Machine didn't back that up. I did it that way because I wanted to first backup the internal drive then do some work and then go backup the external archive drive over night. I plugged the H archive drive in, so it show up in the finder and then told Time Machine to Backup Now. It started the back up but right after doing the initial computations when it actually started backing up I got the standard error message that "the backup disk ran out of space unexpectedly..."  I've double checked that the backup disk is set correctly in Time Machine to the 1Tb G drive and when I do a Get Info on the G drive it shows Capacity: 1TB, Available: 713.54 GB.
    Is it possible something is wrong with the new drive? Can I test that?

    Its funny how sometimes asking a question can prompt  your thinking. As soon as I finished posting this I thought "of course Disk Utility".  I ran a check disk and got the following error message:
    Unused node is not erased (node = 107)
    I did a restore which corrected the error. Turned Time Machine back on and its backing up the rest of my data now.

  • 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.

  • Time Machine everytime backups everyting!

    My main system disk "Macintosh HD", 500 GB
    Media disk is exernal disk named "Media", 1000 GB.
    My Time Machine disk is named "DeLorean" and its external 1,500 GB.
    I have about 340 GB more free space in the Time Machine disk than my data currently uses up.
    My problem is that the Time Machine VERY often starts its backup FROM THE SCRATCH!
    Doing FULL BACKUP! Deleting over 800 GB of data. If you see my logs, you will see it doesnt like something about the external "Media" disk.
    It does this thing called "Deep event scan at path:/Volumes/Media reason:must scan subdirs|"... * see logs later.
    Funny thing is, if i delete/erase the backup, or let it do the FULL backup when it wants, it usually after that does the normal smaller backup just fine.
    BUT if I unmount the Media disk even once and do one incremental backup(which it does fine), then after i mount the Media back, next time it does this FULL backup and says in the logs about the Deep even scan.
    All my disks are encrypted via FileVault2. Shouldnt time machine still work or is this setup fine?
    Here are the logs. Yesterday i even shuffled all my disks and erased the Media and the time machine disk and encrypted them again.
    You can see the first full backup starting at 2 am, then ONE succesfull incremental backup while both disk were still mounted. When i woke up at (13:20 pm) I did one incremental backup without the Media (ummounted it) and then again new one with media mounted (13:29 pm) and BAM ! It started FULL backup (deleting 800+ GB of data). Nothing has been changed on the media disk during that time. Weird !
    Logs showing fresh first new backup stuff:
    Dec 18 01:03:48 imac com.apple.backupd[95130]: Copied 81.9 GB of 1047.6 GB, 1469 of 1156879 items
    Dec 18 02:03:49 imac com.apple.backupd[95130]: Copied 172.8 GB of 1047.6 GB, 1516 of 1156879 items
    Dec 18 03:03:50 imac com.apple.backupd[95130]: Copied 264.8 GB of 1047.6 GB, 1563 of 1156879 items
    Dec 18 04:03:50 imac com.apple.backupd[95130]: Copied 357.1 GB of 1047.6 GB, 1615 of 1156879 items
    Dec 18 05:03:51 imac com.apple.backupd[95130]: Copied 449.1 GB of 1047.6 GB, 1666 of 1156879 items
    Dec 18 06:03:51 imac com.apple.backupd[95130]: Copied 541.5 GB of 1047.6 GB, 1696 of 1156879 items
    Dec 18 07:03:52 imac com.apple.backupd[95130]: Copied 633.6 GB of 1047.6 GB, 1741 of 1156879 items
    Dec 18 08:03:52 imac com.apple.backupd[95130]: Copied 725.6 GB of 1047.6 GB, 1786 of 1156879 items
    Dec 18 08:10:55 imac com.apple.backupd[95130]: Copied 1796 files (736.3 GB) from volume Media.
    Dec 18 09:03:53 imac com.apple.backupd[95130]: Copied 773.9 GB of 1047.6 GB, 621723 of 1156879 items
    Dec 18 10:03:54 imac com.apple.backupd[95130]: Copied 803.6 GB of 1047.6 GB, 936589 of 1156879 items
    Dec 18 11:03:54 imac com.apple.backupd[95130]: Copied 878.4 GB of 1047.6 GB, 1019840 of 1156879 items
    Dec 18 12:03:54 imac com.apple.backupd[95130]: Copied 951.6 GB of 1047.6 GB, 1107382 of 1156879 items
    Dec 18 13:03:54 imac com.apple.backupd[95130]: Copied 1034.6 GB of 1047.6 GB, 1110125 of 1156879 items
    Dec 18 13:13:49 imac com.apple.backupd[95130]: Copied 1140722 files (1041.4 GB) from volume Macintosh HD.
    Dec 18 13:13:58 imac com.apple.backupd[95130]: 1.72 GB required (including padding), 341.53 GB available
    Dec 18 13:13:58 imac com.apple.backupd[95130]: Copied 6 files (0 bytes) from volume Media.
    Dec 18 13:14:15 imac com.apple.backupd[95130]: Copied 6665 files (1.7 MB) from volume Macintosh HD.
    Dec 18 13:14:17 imac com.apple.backupd[95130]: Copying Lion Recovery set
    Dec 18 13:14:42 imac com.apple.backupd[95130]: Backed up Lion Recovery to /Volumes/DeLorean/Backups.backupdb
    Dec 18 13:14:45 imac com.apple.backupd[95130]: Starting post-backup thinning
    Dec 18 13:14:45 imac com.apple.backupd[95130]: No post-back up thinning needed: no expired backups exist
    Dec 18 13:14:45 imac com.apple.backupd[95130]: Backup completed successfully.
    Ends.
    This backup i Initiated after i woke up, with both system disk and external "media" mounted:
    Dec 18 13:22:02 imac com.apple.backupd[5781]: Starting standard backup
    Dec 18 13:22:02 imac com.apple.backupd[5781]: Backing up to: /Volumes/DeLorean/Backups.backupdb
    Dec 18 13:22:05 imac com.apple.backupd[5781]: 1.70 GB required (including padding), 340.96 GB available
    Dec 18 13:22:05 imac com.apple.backupd[5781]: Waiting for index to be ready (100)
    Dec 18 13:23:05 imac com.apple.backupd[5781]: Waiting for index to be ready (100)
    Dec 18 13:23:48 imac com.apple.backupd[5781]: Copied 6 files (0 bytes) from volume Media.
    Dec 18 13:23:55 imac com.apple.backupd[5781]: Copied 1780 files (8.6 MB) from volume Macintosh HD.
    Dec 18 13:23:56 imac com.apple.backupd[5781]: 1.37 GB required (including padding), 341.39 GB available
    Dec 18 13:23:56 imac com.apple.backupd[5781]: Copied 6 files (0 bytes) from volume Media.
    Dec 18 13:23:59 imac com.apple.backupd[5781]: Copied 1596 files (268 bytes) from volume Macintosh HD.
    Dec 18 13:24:00 imac com.apple.backupd[5781]: Starting post-backup thinning
    Dec 18 13:24:00 imac com.apple.backupd[5781]: No post-back up thinning needed: no expired backups exist
    Dec 18 13:24:00 imac com.apple.backupd[5781]: Backup completed successfully.
    Ends.. This seems to work like it should.
    Now, see the time stamps, i just toke some coffee and came back....
    This next backup is done while "Media" drive has been umounted:
    Dec 18 13:28:00 imac com.apple.backupd[5962]: Starting standard backup
    Dec 18 13:28:00 imac com.apple.backupd[5962]: Backing up to: /Volumes/DeLorean/Backups.backupdb
    Dec 18 13:28:01 imac com.apple.backupd[5962]: 1.37 GB required (including padding), 341.39 GB available
    Dec 18 13:28:04 imac com.apple.backupd[5962]: Copied 1455 files (78 KB) from volume Macintosh HD.
    Dec 18 13:28:04 imac com.apple.backupd[5962]: 1.37 GB required (including padding), 341.39 GB available
    Dec 18 13:28:05 imac com.apple.backupd[5962]: Copied 115 files (93 bytes) from volume Macintosh HD.
    Dec 18 13:28:05 imac com.apple.backupd[5962]: Starting post-backup thinning
    Dec 18 13:28:05 imac com.apple.backupd[5962]: No post-back up thinning needed: no expired backups exist
    Dec 18 13:28:05 imac com.apple.backupd[5962]: Backup completed successfully.
    Incremental backup seems to finnish ok, without the "Media" drive.
    This backup is the third one done just after couple minutes after i mounted the "Media" drive back on:
    Dec 18 13:31:49 imac com.apple.backupd[6025]: Starting standard backup
    Dec 18 13:31:49 imac com.apple.backupd[6025]: Backing up to: /Volumes/DeLorean/Backups.backupdb
    Dec 18 13:31:49 imac com.apple.backupd[6025]: Deep event scan at path:/Volumes/Media reason:must scan subdirs|
    Dec 18 13:31:49 imac com.apple.backupd[6025]: Finished scan
    Dec 18 13:31:51 imac com.apple.backupd[6025]: 884.92 GB required (including padding), 341.39 GB available
    Dec 18 13:31:51 imac com.apple.backupd[6025]: No expired backups exist - deleting oldest backups to make room
    Dec 18 13:31:52 imac com.apple.backupd[6025]: Deleted backup /Volumes/DeLorean/Backups.backupdb/imac/2011-12-18-131415 containing 8.7 MB; 341.40 GB now available, 884.92 GB required
    Dec 18 13:31:52 imac com.apple.backupd[6025]: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    Dec 18 13:32:02 imac com.apple.backupd[6025]: Deleted backup /Volumes/DeLorean/Backups.backupdb/imac/2011-12-18-132359 containing 736.30 GB; 1.05 TB now available, 884.92 GB required
    Dec 18 13:32:02 imac com.apple.backupd[6025]: Deleted 2 backups containing 736.31 GB total; 1.05 TB now available, 884.92 GB required
    Dec 18 13:32:02 imac com.apple.backupd[6025]: Backup date range was shortened: oldest backup is now Dec 18, 2011
    Dec 18 13:35:02 imac com.apple.backupd[6025]: Copied 526 files (4.3 GB) from volume Media.
    Dec 18 13:35:03 imac com.apple.backupd[6025]: Backup canceled.
    I canceled that scan(it would take about 12 hours again
    OK. Couple questions:
    - Why time machine does this deep scan? What does it actually mean?
    - Why time machine thinks that it needs to do a 800GB worth of new backup. Those data have not changed a bit (they are movies).
    - How its related to the unmount/mounting the Media drive?
    I would really hope some answers from somebody. I have strugled with this issue almost a month now.
    Thanks!

    ECONOMAN wrote:
    Time Machine Incremental Backups S...L...O...W and seem to bog down things so as to make the machine unusable. Why doesn't it simply backup changes, not the entire drive (less exclusions)?
    Normally, that's exactly what it does. So start by calming down.
    And, it gobbles processing power so I can't even check mail.
    Can you schedule the frigging thing or do I just stop it all the time in order to get anything done?
    It's cute, but kind of worthless.
    First, are these backups larger than you think they ought to be? If so, that's likely at least part of your problem. See #D4 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum, for some possible causes and a way to find out just what's going on.
    If that's no help, or they're still slow, try all the things in #D2 of the Troubleshooting Tip.
    If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.

  • Can I set Time Machine to backup both my hard drive and an external hard drive?

    Hi. I've been working with a lot of family video lately and my internal hard drive has filled up significantly. iMovie doesn't seem to have a good archiving facility like Adobe InDesign which I use at work were all the relevant files are gathered together into one folder. Apple advised me to relocate my movie files to an external hard drive and herein lies my query.
    Is there a way for me to set Time Machine to backup both my iMac's internal drive and the external hard drive that would contain my movie files? I've been using Time Machine for my backups for a few years now, but backing up the external as well has me stumped. If Time Machine could be used then all the necessary file accociations etc would be safely backed up as well - that's why I don't want to have to manually backup the external.
    Anyone have any ideas? Thanks!

    7string48 wrote:
    Thanks so much Pondini!!  You just quickly answered a question that none of the Mac people in 3 stores or Apple Care have been able to answer.If you can format it HFS+ (any variation of Mac OS Extended), it will work.  If not, it won't.  
    I'm not too surprised about the Apple Stores, as they don't get much training on Time Machine.  But AppleCare sure ought to know. 
    Oh...what about if the external drive is an array...like a Drobo with it's own proprietary formatting...I guess that would not work...??
    I've never used a Drobo.  A number of folks here have used them as their Time Machine drives, but I don't recall seeing anyone try to back one up with TM, so can't say for sure.  But if you can format it as HFS+ (any variation of Mac OS Extended), it will work.  If not, it won't.
    At least part of the reason is, Time Machine uses the File System Event Store, a hidden log of changes that OSX keeps on each Mac-formatted disk/partition, to figure out what's changed and needs to be backed-up.  See How Time Machine works its Magic for details.
    See Time Machine - Frequently Asked Question #32 for details and considerations of backing-up multiple volumes with Time Machine.
    However, even if it will work, that may not be your best strategy, depending on your circumstances:
    Since Time Machine keeps copies of things you've changed or deleted, the destination needs to be considerably larger than the data being backed-up.  How much larger varies widely depending on how you use your Mac, but a general "rule of thumb" is, it needs at least twice the space to be able to keep a reasonable "depth" of backups for you.
    If you have a large internal HD, fairly full, plus a large external HD, and the files on the external don't change frequently, you might want to use Time Machine for the internal, and a different app to a different disk or partition, on a different schedule, for the external.  Especially if space is a consideration, you might not need to keep previous versions of files on the externals.  See Time Machine - Frequently Asked Question #27 for some alternatives.

Maybe you are looking for

  • GUI_DOWNLOAD field names problem

    Hi, I have a problem with the haederline with the column names in the downloaded file. I'm using the function GUI_DOWNLOAD in the following way: DATA: ls_fieldnames  TYPE it_fieldnames,         lt_fieldnames  TYPE STANDARD TABLE OF it_fieldnames. ls_

  • HT4859 every time I try to restore my ipod it does not work...how come?

    every time I try to restore my ipod it does not work...how come?

  • Outer join not returning missing records.

    Hi All, Can you please look at the query and see why I don't get any record. There is no item '0141884' for cust_id '1259' in the nfpc_gpm_expense table. Thank you in advance. A/A    SELECT DISTINCT rctla.customer_trx_id, msi.segment1 item_number,   

  • Essbase Copy App Issue

    Hi, We are facing a problem, doing a very simple step of Copy Application. In backend I can see the application is copied properly, however in EAS console its not appearing and the copy application sessions is till going on. Moreover nothing is there

  • Finder dies when opening Applications

    Whenever I open Applications, regardless of which user account I'm logged in as, the Finder dies. Starting apps from the doc does this too. Some of them will actually start up, some won't, but in any event the finder dies and restarts. Help! Thanks,