Previous 1 2 3 4 5 Next 64 Replies Latest reply: Mar 14, 2013 1:18 PM by geedubya Go to original post
  • Pondini Level 8 Level 8 (38,720 points)

    geedubya wrote:

     

    I did notice my Library 2 HD doesn't show up in Spotlight either

    See if it's excluded from Spotlight, per System Prefs > Spotlight > Privacy.

     

     

    I can't figure out what's up with Library HD 1, though.  We must be missing something, but I can't think what.

     

    It's a long shot, but try running Repair Disk on the backup drive.

  • geedubya Level 1 Level 1 (0 points)

    Library 2 HD not excluded from Spotlight.

     

    Repair Disk (you did mean Repair Disk and not Repair Permissions?) showed a message saying 'Incorrect permissions for private directory' after 'Checking multi-linked directories'.  It then went through the volume again and said 'Repair complete'.  Library 1 HD still showed under 'Latest'.  I am doing another backup to see if that changes anything.

  • Pondini Level 8 Level 8 (38,720 points)

    geedubya wrote:

     

    Library 2 HD not excluded from Spotlight.

    Very odd. 

     

     

    Repair Disk (you did mean Repair Disk and not Repair Permissions?)

    Yup.

     

    showed a message saying 'Incorrect permissions for private directory' after 'Checking multi-linked directories'.  It then went through the volume again and said 'Repair complete'.

    Good.  I hadn't really expected a problem, but we need to rule that out.

     

     

    Library 1 HD still showed under 'Latest'.  I am doing another backup to see if that changes anything.

    It shouldn't matter, but don't necessarily look at Latest.  Try the actual date-stamped backup folders.

  • geedubya Level 1 Level 1 (0 points)

    Library 1 HD still gets backed up - it appears in the last 3 backups.

     

    I have another new drive at my disposal, so is it worth trying again to restore Library HD using a different approach?  I could do the restore from my second TM drive which I have not backed up since the drive failure, if that's a good idea.  I have repaired permissions on Mac HD recently though - not sure if that would affect anything.

     

    Also, should I update to Lion and would it possibly help to do so at this point?

  • Pondini Level 8 Level 8 (38,720 points)

    geedubya wrote:

     

    Library 1 HD still gets backed up - it appears in the last 3 backups.

    Bizarre.  We must be missing something, but I can't imagine what.

     

     

    I have another new drive at my disposal, so is it worth trying again to restore Library HD using a different approach?  I could do the restore from my second TM drive which I have not backed up since the drive failure, if that's a good idea.

    You have recovered all the data, right?  I don't think the results will be any different, but it might be worth a try. Before you do that, though, see if the "phantom" Library HD 1 is on those backups.

     

    If/when you try it, check whether "Owners Enabled" is yes or no via Disk Utility.  (No is the default when you format a drive, and might let the restore work properly.)

     

     

    I have repaired permissions on Mac HD recently though - not sure if that would affect anything.

    No, that only handles permissions on files & folders installed by OSX, or by the OSX installer;  not files you've created in your home folder or on external HDs.   See About Disk Utility's Repair Disk Permissions feature.

     

     

    Also, should I update to Lion and would it possibly help to do so at this point?

    That likely won't help with the restore problem. 

     

    There are many differences between Snow Leopard and Lion, but being able to "associate" the new drive with the old backups is the only one that should affect anything we've been discussing.   Apple's "what's new" announcement and sales-pitch-type article has been deleted, but you might want to review Changes in Lion from Snow Leopard

  • baltwo Level 9 Level 9 (61,945 points)

    Launch the Terminal app in /Utilities, copy & paste in this command into the window that pops up, hit the return key, and post the results:

     

    df -H

  • geedubya Level 1 Level 1 (0 points)

    OK here you go.

     

    Screen shot 2013-03-12 at 19.00.52.jpg

  • Pondini Level 8 Level 8 (38,720 points)

    geedubya wrote:

     

    Library 1 HD still gets backed up - it appears in the last 3 backups.

    This is really bizarro, especially since it doesn't appear with the command Baltwo recommended (btw, thanks for staying tuned, Baltwo).

     

    A clue may be lurking in your logs.  Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs.  Locate the most recent backup where Library HD 1 appears to have been backed-up, then copy and post all the messages here.

     

    Message was edited by: Pondini

  • geedubya Level 1 Level 1 (0 points)

    OK - latest backup below.  Seems to have done it twice or am I misreading it?  Oh, and the TM drive lost its TM icon after 'Repair Disk' by the way.

     

    Starting standard backup

    Backing up to: /Volumes/My Book/Backups.backupdb

    No pre-backup thinning needed: 2.37 GB requested (including padding), 130.25 GB available

    Copied 209 files (0 bytes) from volume Project HD.

    Copied 1809 files (0 bytes) from volume Library 2 HD.

    Waiting for index to be ready (100)

    Copied 26275 files (12.6 MB) from volume Mac HD.

    Copied 440731 files (12.6 MB) from volume Library HD.

    No pre-backup thinning needed: 2.36 GB requested (including padding), 130.19 GB available

    Copied 209 files (0 bytes) from volume Project HD.

    Copied 1809 files (0 bytes) from volume Library 2 HD.

    Copied 24711 files (168 KB) from volume Mac HD.

    Copied 439167 files (168 KB) from volume Library HD.

    Starting post-backup thinning

    No post-back up thinning needed: no expired backups exist

    Backup completed successfully.

  • Pondini Level 8 Level 8 (38,720 points)

    geedubya wrote:

     

    OK - latest backup below.  Seems to have it twice or am I misreading it?

    That's correct -- it made one "pass," then found changes since it started, so it made a second pass.  That makes sense on a large, long-running backup (so the backup timestamp is accurate);  not so much on little ones.

     

    (And the screwy messages showing the exact same amount of data from two different disks -- that's a known problem Apple hasn't fixed.)

     

    But no mention of copying anything from Library HD 1.

     

    So it just seems to be some weird display anomaly, not something actually wrong.

     

     

    I don't know why it appears on the backup per the Finder.  That's why I suggested running Repair Disk on the backup disk.

     

    I'll experiment with a couple of things . . .

  • Pondini Level 8 Level 8 (38,720 points)

    Aack!  I owe you an apology. 

     

    I'd forgotten how Time Machine handles a disconnected/unavailable drive -- it will continue to appear in the backups, and on the TM browser ("Star Wars" display), until the last backup of it is deleted, just as you're seeing.

     

    That's different from the way I usually test multiple drives -- since I actually use multiple partitions on the same drive, I include it on one backup, then exclude it via the TM prefs panel.  In that scenario, it won't appear on subsequent backups.

     

     

    How and why the name changed, I can't answer.  It looks like you did that, but I can't swear that TM (or OSX) didn't do it, if at some point it thought it had two drives with the same name.  You can have two drives with the same name connected to your Mac, and OSX won't get confused, because it keeps track of them by UUID (Universally Unique IDentification), but TM won't let you back up two with the same name -- it puts up a message asking you to rename one of them.

     

    Bottom line -- nothing's wrong. 

     

    Sorry for the confusion -- this is a quite unusual situation.

  • geedubya Level 1 Level 1 (0 points)

    OK, so TM/OSX has kept the orginal backup but renamed it so it's not the same as the name I used for the new drive (which is the same as the original).  It definitely wasn't me that used that name.  But presumably that means TM now has a duplicate backup, as it were, so is storing around 650GB of data that's not required.  Are you saying I have to leave it until it 'falls off the end'?

     

    I may give restoring to the other new drive a go when I have a spare moment and see what happens.  I'll start by giving it a unique name and make sure to 'Ignore Ownership'.  I'll keep you posted if you would like to know what happens?

     

    Many thanks for your help, much appreciated

  • geedubya Level 1 Level 1 (0 points)

    In case I need to try this, and in case you didn't spot my previous reply ...

    Linc Davis wrote:

     

    Inside the snapshot folder is a folder hierarchy like the one on the source disk. Find one of the items you can't restore and select it. Open the Info dialog for the selected item. In the Sharing & Permissions section, you may see an entry in the access list that shows "Fetching…" in the Name column. If so, click the lock icon in the lower right corner of the dialog and authenticate. Then delete the "Fetching…" item from the icon list. Click the gear icon below the list and select Apply to enclosed items from the popup menu.

     

    Now you should be able either to copy the item in the Finder or to restore it in the time-travel view. If you use the time-travel view, be sure to select the snapshot you just modified. If successful, repeat the operation with the other items you were unable to restore. You can select multiple items in the Finder and open a single Info dialog for all of them by pressing the key combination option-command-I.

     

     

    I don't see any as 'fetching' but there are lots that say ' _unknown' or 'admin' as well as my username and 'everyone'.  I'm wondering if deleting the '_unknown' entry will work in the same way as you describe, or is that something else entirely?

  • Pondini Level 8 Level 8 (38,720 points)

    geedubya wrote:

     

    OK, so TM/OSX has kept the orginal backup but renamed it so it's not the same as the name I used for the new drive (which is the same as the original).  It definitely wasn't me that used that name.  But presumably that means TM now has a duplicate backup, as it were, so is storing around 650GB of data that's not required.  Are you saying I have to leave it until it 'falls off the end'?

    No.  You may delete all backups of it, per Time Machine - Frequently Asked Question #12, as I posted earlier. 

     

    But you may want to wait a while, to be sure you don't need any of the old backups.    Be very careful to select the old backups (navigate in the TM display to one of the old backups, then select the old drive, click the "gear" icon, and select the Delete All Backups of ... option).  When it's done, immediately check to be sure you still have the backups of the new drive . . . just in case.

     

    If I can get some time, I'll do some more experimenting, and try to duplicate your scenario. 

     

     

    I may give restoring to the other new drive a go when I have a spare moment and see what happens.  I'll start by giving it a unique name and make sure to 'Ignore Ownership'.  I'll keep you posted if you would like to know what happens?

    Yup.  Keep us posted.

  • geedubya Level 1 Level 1 (0 points)

    OK, I'll hang on to them for a while.  Thanks again.