capn.freako

Q: Time Machine requesting to create new backup, but backups seem to be working fine

Time Machine is telling me that it wants to wipe out my backup history and create a new backup volume, but it seems to be backing up files just fine. I use an Apple AirPort, via WiFi. Should I just keep ignoring Time Machine's request to start a new backup volume? I really don't want to lose my backup history.

MacBook Air (13-inch, Early 2014), iOS 10

Posted on Sep 13, 2016 12:08 PM

Close

Q: Time Machine requesting to create new backup, but backups seem to be working fine

  • All replies
  • Helpful answers

  • by LaPastenague,Helpful

    LaPastenague LaPastenague Sep 13, 2016 6:14 PM in response to capn.freako
    Level 9 (52,596 points)
    Wireless
    Sep 13, 2016 6:14 PM in response to capn.freako

    Something doesn't add up here.

     

    When Time Machine say that the backup is corrupt and needs wiping .. then it can no longer backup to it.

     

    What TM is probably doing is using your local hard disk to make a backup snapshot since the Network version on your Time Capsule (or AE plus USB drive) is now corrupted.

     

    Sorry but your Time Machine history is now dead and lost.. and just needs burying. There is seldom any great point in doing a backup of the sparsebundle.. but if you are adamant then for sure just copy the sparsebundle to a different location.. then wipe the disk and start over.. You have no choice.

  • by capn.freako,

    capn.freako capn.freako Sep 13, 2016 5:59 PM in response to LaPastenague
    Level 1 (4 points)
    Wireless
    Sep 13, 2016 5:59 PM in response to LaPastenague

    How can I determine where my backups are going?

  • by LaPastenague,Helpful

    LaPastenague LaPastenague Sep 13, 2016 6:25 PM in response to capn.freako
    Level 9 (52,596 points)
    Wireless
    Sep 13, 2016 6:25 PM in response to capn.freako

    Look at the date of the backup file..

     

    The backup sparsebundle on the Network drive.. I am confused what it is but that will give you the last time it was backed up.

     

    Then look at the files on your local hard disk .. I suspect it is hidden so you will need to turn on view hidden files.. just google it.

  • by capn.freako,

    capn.freako capn.freako Sep 14, 2016 6:13 AM in response to LaPastenague
    Level 1 (4 points)
    Wireless
    Sep 14, 2016 6:13 AM in response to LaPastenague

    Hmmm, the *.sparsebundle file, on my AirPort, says it was modified today at 5:55AM.

     

    However, as a test I just tried to restore a much older version of my ~/.bashrc file. And, after "Waiting..." for about a minute, Time Machine offered me only versions of this file going back to 9/12/16 at 7:44PM. So, I think you're right about me only having local snapshots available. Darn!

     

    Have you heard of anyone being able to restore a *.sparsebundle file, once it gets horked?

     

    I know Apple disavows any responsibility for these issues, when third party backup drives are being used, but I'm using one of their own AirPorts. Do they have any solution, for that scenario?

     

    Thanks for your time and help! I appreciate it.

  • by LaPastenague,

    LaPastenague LaPastenague Sep 14, 2016 2:57 PM in response to capn.freako
    Level 9 (52,596 points)
    Wireless
    Sep 14, 2016 2:57 PM in response to capn.freako

    I know Apple disavows any responsibility for these issues, when third party backup drives are being used, but I'm using one of their own AirPorts. Do they have any solution, for that scenario?

    The solution is built into Time Machine.. on discovery of a corrupt backup it is wiped and a new one begun. Apple will certainly NOT help you extract files from a corrupt backup.

     

    Have you heard of anyone being able to restore a *.sparsebundle file, once it gets horked?

    Sure.. there is lots of angst in these columns over corrupted sparsebundles. LOADS and LOADS of bad feelings.

     

    In general our advice is .. do not waste your time.

     

    Here is one method I saw a while ago.

     

    Fix corrupt TM backup.

     

    https://discussions.apple.com/message/29263757#29263757

     

    1) Disable Time Machine.

    2) Stopping all Spotlight indexes (mdutil -d -a).

    3) Destroying all Spotlight indexes (rm -rf /.Spotlight-V100) manually.

    4) Repairing a file system permission issue with Spotlight (removed a bunch of folders owned by a non-existant user in a /private/var/folders subfolder that Spotlight created). No idea how they got there but they were there and the logs were complaining about them causing a fatal error.

    5) Re-enabling Spotlight indexes and letting them build fully.

    6) Re-running an initial Time Machine backup.


    The problem is, this is NOT a universal fix. Only one of many problems.


    IMHO if you are concerned to keep historical backups.. you need a totally different approach.

    Time Machine is less and less reliable as time goes on.. related more I think to network issues than TM itself.

    My advice is

    1. Do not use TM to network targets without ethernet. (wireless is not now and not in the immediate future at least a reliable network infrastructure no matter how much Apple hates wires).

    2. TM backup to local disk (USB, Thunderbolt, Firewire) are much faster, much more reliable and much cheaper (well USB 3 at least) than Network targets including ethernet.

    3. Using a second backup software is highly recommended. I use Carbon Copy Cloner. People have good results with Chronosync. There are others.

    4. If you want to keep historical backups and still run a Time Capsule.. buy lots of USB drives and archive the TC on a monthly rotation. Unfortunately this is slow and as the TC fills up with take longer and longer to accomplish. Maybe the next one (if there is a next one) will have a USB3 port.