Resizing Time Machine Backup Volume

As a recent iMac purchaser, I started using Time Machine with an external 1TB FW400 drive about a week ago. All is working well (as far as I know) but I now wish that I had partitioned the external drive e.g., 800GB for Time Machine and 200GB for another volume.
1) Is there a way for me to resize (make smaller) the TM partition such that I don't lose the TM backup files already on it? Current backupdb is 90GB, free space is roughly 900GB (part of which I'd like to use to create a small partition). If so, how?
2) Alternatively, if the creation of a second partition from some of the unused space on the existing TM partition will result in loss of data on the TM volume, is there a way for me to first copy the TM data into a folder on my iMac internal hard drive (250GB free)? And, if so, how should I restore the backupdb from the folder back into the TM volume when I'm done repartitioning the external drive?
I've tried copying the backupdb two ways, with no success. 1) After turning off Time Machine, a "copy" of the database seemed to be working okay but eventually failed with message "The operation can't be completed because the selection contains both backup items and non-backup items." 2) I had also tried a sudo find . -print | cpio -pdmv /Users/somedir in the hope that I force a total copy using Unix utilities, but received plenty of error messages. (I guess there's more to the backupdb than just a collection of files.)
Since I only recently started using TM, I'm okay with scratching what I have and starting over, but I'd like to determine if there's a way I can solve this problem the hard way... .
Thanks.
P.S. If I need to scratch the existing TM volume and start over (after creating two partitions on my external drive), are there any gotchas I need to be aware of before (re)starting TM on the new partition?

Yes, you can do what you want. I would make a backup of your TM backup as a precaution, but it isn't a necessity. To backup the TM volume you will need another drive large enough for the space used by the TM backup. You must use the Restore option of Disk Utility to essentially clone the volume to another drive.
To resize the drive do the following:
1. Open Disk Utility and select the drive entry (mfgr.'s ID and size) from the left side list.
2. Click on the Partition tab in the DU main window. You should see the graphical sizing window showing the existing partition. A portion will appear as a blue rectangle representing the used space on the drive.
3. In the lower right corner of the sizing window is a resizing gadget. Select it with the mouse and move the bottom of the rectangle upwards until you have reduced the existing partition enough to create the desired new volume's size. The bottom of the sizing window will appear gray. Click on the Apply button and wait until the process has completed.
4. Click on the [+] button below the sizing window to add a new partition in the gray space you freed up. Give the new volume a name, if you wish, then click on the Apply button. Wait for the process has completed.
You should now have a second volume on the drive.

Similar Messages

  • "No such file or directory" errors on Time Machine backup volume

    I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I "cd" into some folders (but not all) and do a "ls -la" command, I get a lot of "No such file or directory" errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do "ls -a" everything appears normal on both systems (no error messages anyway).
    It appears to be the case that the folders that have the problem are folders that Time Machine has created as "hard links" to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.
    I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK - so basically by switching the volume the problem switches also on who shows the "no such file or directory" errors.
    Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these "hard links" to folders.
    There is utility program written by Amit Singh, the fella who wrote the "Mac OS X Internals" book, called hfsdebug (you can get it from his website if you want - just do a web search for "Mac OS X Internals hfsdebug" if you want to find it ). If you use it to get a little bit more info on what's going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:
    mac1:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac1:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac1:xxx me$ ls -lai
    total 48
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 .
    282780 drwxr-xr-x 12 me staff 442 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 Documents
    729750 drwx------ 104 me staff 7378 Jan 15 14:17 D2
    728506 drwx------ 19 me staff 850 Jan 14 09:19 D3
    mac1:xxx me$ hfsdebug Documents/ | head
    <Catalog B-Tree node = 12589 (sector 0x18837)>
    path = MyBackups:/yyy/xxx/Documents
    # Catalog File Record
    type = file (alias, directory hard link)
    indirect folder = MyBackups:/.HFS+ Private Directory Data%000d/dir_135
    file ID = 728505
    flags = 0000000000100010
    . File has a thread record in the catalog.
    . File has hardlink chain.
    reserved1 = 0 (first link ID)
    mac1:xxx me$ cd Documents
    mac1:xxx me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac1:Documents me$ ls -lai | head
    total 17720
    135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 .
    280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    146 drwxr-xr-x 2 me staff 68 Feb 17 2009 .parallels-vm-directory
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    148 drwxr-xr-x 2 me staff 136 Aug 28 2009 ACPI
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    So you can see from the first few lines of the "ls -a" command, it shows some file/folders but you can't tell which yet. The next "ls -la" command shows which names are files and folders - that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the "hfsdebug" info shows some details of what is really happening in the "Documents" folder, but more about that in a bit.
    And here are what a "ls -a" and "ls -al" look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:
    mac2:xxx me$ pwd
    /Volumes/MyBackups/yyy/xxx
    mac2:xxx me$ ls -a
    . .DS_Store D2
    .. Documents D3
    mac2:xxx me$ ls -lai
    total 56
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 .
    282780 drwxr-xr-x 13 me staff 398 Jan 17 14:03 ..
    286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 Documents
    729750 drwx------ 217 me staff 7334 Jan 15 14:17 D2
    728506 drwx------ 25 me staff 806 Jan 14 09:19 D3
    mac2:xxx me$ cd Documents
    mac2:Documents me$ ls -a | head
    .DS_Store
    .localized
    .parallels-vm-directory
    .promptCache
    ACPI
    ActivityMonitor2010-12-1710p32.txt
    ActivityMonitor2010-12-179pxx.txt
    mac2:Documents me$ ls -lai | head
    ls: .parallels-vm-directory: No such file or directory
    ls: ACPI: No such file or directory
    ... many more "ls: ddd: No such file or directory" error messages appear - there is a one-to-one
    correspondence between the "ddd" folders and the "no such file or directory" error messages
    total 17912
    728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 .
    280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 ..
    144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
    145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
    147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
    151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
    152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
    If you look very close a hint as to what is going on is obvious - the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it's 728505 in the remote mounted case for mac2. So it appears that these "hard links" to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the "hfsdebug" shows even better as you can clearly see the REAL location of the Documents folder is in something called "/.HFS+ Private Directory Data%000d/dir_135" that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the "cd Documents" I don't go into the inode 135, but into the inode 728505 (look close at the "." entry for the "ls -la" commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.
    Anyone have any ideas how to fix this so that "ls -l" commands don't generate these "no such file or folder" messages?
    I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call - do a "man 2 link" if you are curious how it works.
    I'm well aware of the issues and the conditions when they can and can't be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.
    Do not try these hard links to folders on your own without knowing what they're for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don't say I didn't warn you first.
    Thanks ...
    -Bob

    The problem is Mac to Mac - the volume that I'm having the issue with is not related in any way to Time Machine or to TimeCapsule. The reference to TIme Machine is just to illustrate the problem exists outside of my own personal work with hard links to folders on HFS Extended volumes (case-sensitive in this particular case in case that matters).
    I'm not too excited about the idea of snooping AFP protocol to discover anything that might be learned there.
    The most significant clue that I've seen so far has to do with the inode numbers for the two folders shown in the Terminal window snippets in the original post. The local mounted case uses the inode=728505 of the problematic folder which is in turn linked to the hidden original inode of 135 via the super-secret /.HFS+... folder that you can't see unless using something like the "hfsdebug" program I mentioned.
    The remote mounted case uses the inode=728505 but does not make the additional jump to the inode=135 which is where lower level folders appear to be physically stored.
    Hence the behavior that is seen - the local mounted case is happy and shows what would be expected and the remote mounted case shows only files contained in the problem folder but not lower-level folders or their contents.
    From my little knowledge of how these inode entries really work, I think that they are some sort of linked list chain of values, so that you have to follow the entire chain to get at what you're looking for. If the chain is broken somewhere along the line or not followed correctly, things like this can happen. I think this is a case of things not being followed correctly, as if it were a broken chain problem then the local mounted case would have problems also.
    But the information for this link in the chain is there (from 728505 to the magic-135) but for some reason AFP doesn't make this extra jump.
    Yesterday I heard back from Apple tech support and they have confirmed this problem and say that it is a "implementation limitation" with the AFP client. I think it's a bug, but that will have to be up to Apple to decide now that it's been reported. I just finished reporting this as a bug via the Apple Bug Reporter web site -- it's bug id 8926401 if you want to keep track it.
    Thanks for the insights...
    -Bob

  • Finder "Open With..." Menus Seeing Time Machine Backup Volumes

    The "Open With..." context menu that is available if you right-click a file in the Finder has gone crazy on my Mac. The list is about a mile long and includes literally dozens of versions of each app.
    One clue is that a similar "Open Page With..." menu that is available under Safari's Debug menu includes paths, and each redundant version of the applications that appear there are all located in the Time Machine backup volume.
    It's hard to imagine that Time Machine doesn't auto-configure this, but my question to the group is if there's a way to make the Finder (and Safari) ignore the Time Machine backup database? Clearly, I would never, ever want to open a file with an app located in the Time Machine database.
    Thanks,
    Steve

    I have excluded my external USB drive where Time Machine backups reside, and I still get a context menu full of backed up applications.
    It's not just plain wrong, it makes the context menu very slow.
    MacOS must look for this information elsewhere.

  • Unable to restore from Time Machine after an erase and reinstall - MacbookPro cannot access my old Time Machine backup volume. Desperate for help please?

    My MacbookPro would not move past the Apple logo and spinning wheel for a number of hours.  After trying the numerous suggestions to solve the issue I eventually opted to erase and reinstall feeling confident my Time Machine backups would come to the rescue.  After a successful erase and reinstall I tried to restore all my data from my TIme Capsule using Command-R during start up and by using the Migration Assistant.  Neither worked and I have received messages to the effect that the backup volumes on my Time Capsule cannot be access because I have entered a wrong password or because the backup volume is damaged.
    When I open my Time Capsule in Finder and click on my sparsebundle I get an eror message saying that the disk image could not be opened and that the resource is temporarily unavailable.
    Desperate for some help and comfort that many years of personal data have not been lost.
    Thank you.
    M

    When I try to Verify option it says Unable to Verify - Resource temporarily unavailable.
    Here is the past of the log screen:
    2013-06-09 15:00:00 -0500: Disk Utility started.
    2013-06-09 15:09:01 -0500: Disk Utility started.
    2013-06-09 15:19:53 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:19:53 -0500:
    2013-06-09 15:20:00 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:20:00 -0500:
    2013-06-09 15:20:05 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 15:20:05 -0500:
    2013-06-09 15:20:13 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 15:20:14 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:20:14 -0500:
    2013-06-09 15:25:21 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 15:25:23 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:25:23 -0500:
    2013-06-09 15:25:27 -0500: Attach Image “Macajee’s MacBook Pro”
    2013-06-09 15:25:27 -0500: Initializing…
    2013-06-09 15:25:31 -0500: Attaching…
    2013-06-09 15:25:31 -0500: Finishing…
    2013-06-09 15:25:32 -0500: Unable to attach “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 15:25:32 -0500:
    2013-06-09 20:02:06 -0500: Disk Utility started.
    2013-06-09 20:05:22 -0500: Disk Utility started.
    2013-06-09 20:07:11 -0500: Disk Utility started.
    2013-06-09 20:18:34 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:18:34 -0500:
    2013-06-09 20:19:34 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:19:34 -0500:
    2013-06-09 20:19:36 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:19:36 -0500:
    2013-06-09 20:22:29 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:22:29 -0500:
    2013-06-09 20:22:33 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:22:33 -0500:
    2013-06-09 20:22:45 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 20:22:45 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 20:22:45 -0500:
    2013-06-09 20:34:53 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:34:53 -0500:
    2013-06-09 20:34:56 -0500: [DUDiskController viewablePartitions] expecting DUDisk, but got nil
    2013-06-09 20:34:56 -0500:
    2013-06-09 20:38:17 -0500: Verifying Image “Macajee’s MacBook Pro”
    2013-06-09 20:38:17 -0500: Unable to verify “Macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 20:38:17 -0500:
    2013-06-09 20:47:35 -0500: Disk Utility started.
    2013-06-09 20:53:06 -0500: Disk Utility started.
    2013-06-09 20:55:30 -0500: Disk Utility started.
    2013-06-09 20:56:40 -0500: Disk Utility started.
    2013-06-09 21:06:32 -0500: Verifying Image “macajee’s MacBook Pro”
    2013-06-09 21:06:32 -0500: Unable to verify “macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 21:06:32 -0500:
    2013-06-09 21:07:08 -0500: Verifying Image “macajee’s MacBook Pro”
    2013-06-09 21:07:08 -0500: Unable to verify “macajee’s MacBook Pro.” (Resource temporarily unavailable)
    2013-06-09 21:07:08 -0500:

  • Time Machine backup volume will not mount

    Once I goy Time Machine up and running over almost two years ago, I have had little cause for concern. A few lengthy backups here and there but I have been able to restore without any problems whatsoever. It has been extremely useful many times.
    A couple of days ago, I noticed that the backup volume was not mounted (I backup to one of my four internal drives) and launched Time Machine. I got the error:
    The storage location for Time Machine backups can't be found.
    When I run Disk Utility the generic disk icon is in the left hand pane but not the volume. None of the tasks are available except Erase and Partition - there is no option to Verify Disk, Repair Disk, Verify Disk Permissions or Repair Disk Permissions.
    According to my logs, the last backup at 18:12 on 20th November was successful. I didn't notice that the volume had not mounted the until the next day.
    I'm very concerned that I have lost almost two years of data security. Is there any way I can repair the disk or recover the backups?
    Thanks.

    If Disk Utility can't see any partitions, it's not good.
    First, turn TM off.
    Then try ejecting, disconnecting and powering the drive off for a few minutes, then reattaching it. Then try again with Disk Utility. If still no help, the drive is likely dead.
    There's a very small chance that +Disk Warrior+ (version 4.1.1 or 4.2 only), or another heavy-duty disk repair app can fix it, if you already have one. But I wouldn't suggest spending the $$ for one unless you think you'll need it in the future -- DW is about $100.
    Most likely, your disk is dead. There's a small chance that a +Data Recovery+ app such as +Data Rescue+ can recover some of the data. Check via Google, VersionTracker.com, or MacUpdate.com for +Data Recovery.+ There are services and apps, none cheap. Some of the apps have a free demo or test mode that will tell you if there's anything that can be recovered, and perhaps actually recover a single file; then you pay for it and recover whatever else can be recovered. You'll need another external disk to receive the recovered items.
    You won't get the normal Time Machine folder structure, though, just "raw" files. Even if you do recover files, you'll most likely have to figure out what goes where and copy them to the right places manually.
    So I'd suggest immediately getting a new drive and doing a new TM backup to it, so you have something. Put a second partition on it that you can use for the recovered files if and when you do that.
    If those are your only backups, I'd recommend getting a second external, perhaps a portable one, and using CarbonCopyCloner or SuperDuper to make a full "bootable clone" to it, then take it to your safe deposit box, workplace, relative's house, or other secure location. And/or, you might want to look at Mozy, Carbonite, or other online backup services.

  • Time Machine: Backup Volume Could not be Found

    I recently upgraded to Leopard. I have a brand new Lacie external hard drive.
    I have tried to use Time Machine with the Lacie HD, but it fails and gives me this message, "Backup volume could not be found."
    I did some troubleshooting. I tried to reformat the HD, but that gave me errors as well, stating "Could not unmount disk"
    The HD is currently formatted to Mac OS Extended.
    I am not certain if this is a problem with the HD, or just user error! I also had problems with iTunes when I tried to move the Library to the HD. I got and error message stating "you don't have sufficient privileges"
    I only have 2.5G left on my internal HD, so I am a bit concerned. Any guidance would be much appreciated!!

    when you select the TM hard drive in disk utility (the model, not the name) look at the bottom of the DU window. Do you see the line
    Partition Map Scheme : GUID Partition Table?
    Also, I looked at your first post again and it says that you only have 2.5GB of space available on your main drive. I don't know how big your hard drive is but that's a tiny amount. You need to offload part of your data to a different drive ASAP. when free space gets that low, disk fragmentation becomes a very serious issue. system slows done and start behaving in unpredictable fashion. This can lead to all sorts of problems including directory damage. Run "verify disk" on your main drive and see if any errors are reported. I don't know for sure if this is related to your TM problems but it very well might be.

  • Use disk image as time machine backup volume

    I have a large RAID array attached directly to my Mac via firewire (so it is not a NAS). Can I create a disk image file within that larger array, then mount that image as a disk, then use that as my Time Machine target? I see lots of discussion of doing this for NAS, but I cannot get TM to recognize a mounted disk image file as a TM backup volume. FYI, the reason for this is that I want to create a sparse image that limits the amount of space that TM will take, without eating up my entire RAID array, which is huge. Also, by tricking it into thinking it is another volume, TM will still let me back up other stuff on the RAID array to TM.

    Thank you,
    It's interesting to me that it will work if mounted as an SMB volume (at least according to many other posts). While I agree with you that it won't work, as I have verified that, I wonder if it could work if enabled (similar to the ability to enable unsupported network volumes).
    A follow-on question: I would really like to have TM back up FROM a mounted network share to my TM database. I have a network SMB share with a lot of my data on it. I currently have to rsync it to an external drive in order to get TM to back it up. TM is set to ignore network volumes volumes. Interestingly, the SMB shares appear to get mounted on /Volumes instead of /Network, but that is aside, as both directories are set to be ignored by default. Anyhow, is there a way to turn that feature off and allow certain network shares to be backed up (and similarly blocked from back-up in the same manner that I do everything else)? Again, lots of posts out there about backing up TO a network share, but none tell me how to back up from a mounted network share to TM.

  • Time machine backups to remote volumes

    Hi all,
    Been having trouble with backing up a Lion system onto a remote (network) volume.  The idea is basically to back up a (client) Mac onto a disk hosted by another Mac (the backup server).
    I can get the initial backup to work:
    1. share the disk to back up to on the backup server via File Sharing, and ensure to use an administrator account at the client Mac to log onto in order for it to see the backup disk.
    2. mount the backup disk over the network onto the client Mac.
    3. get Time Machine to select that network disk as a backup disk.
    4. start the backup.
    All this works, and I am left with a good initial backup.  However, subsequent backups fail with the following message after the client Mac is next rebooted:
    The syslog shows some rather perculiar difficulty in managing its backup disks:
    15/12/11 11:44:31.309 PM com.apple.backupd: Starting standard backup
    15/12/11 11:44:31.436 PM com.apple.backupd: Attempting to mount network destination URL: afp://Tony%20Kavadias@L%C3%B3rien._afpovertcp._tcp.local/Rivendell
    15/12/11 11:44:31.792 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Rivendell-1 using URL: afp://Tony%20Kavadias@L%C3%B3rien._afpovertcp._tcp.local/Rivendell
    15/12/11 11:45:10.045 PM com.apple.backupd: Failed to eject volume /Volumes/Rivendell-1 (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)
    15/12/11 11:45:10.046 PM com.apple.backupd: Waiting 60 seconds and trying again.
    15/12/11 11:46:10.108 PM com.apple.backupd: Network destination already mounted at: /Volumes/Rivendell-1
    15/12/11 11:46:46.912 PM com.apple.backupd: Failed to eject volume /Volumes/Rivendell-1 (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)
    15/12/11 11:46:46.913 PM com.apple.backupd: Waiting 60 seconds and trying again.
    15/12/11 11:47:46.967 PM com.apple.backupd: Network destination already mounted at: /Volumes/Rivendell-1
    15/12/11 11:48:23.618 PM com.apple.backupd: Failed to eject volume /Volumes/Rivendell-1 (FSVolumeRefNum: -104; status: -47; dissenting pid: 0)
    15/12/11 11:48:23.618 PM com.apple.backupd: Giving up after 3 retries.
    15/12/11 11:48:33.630 PM com.apple.backupd: Backup failed with error: 21
    More digging around leads to the observation that /Volumes/Rivendell-1 (the filesystem that Time Machine mounts from the backup server) is now stuck and cannot be unmounted—to get rid of it, I have to reboot the client Mac.  And that the sparse disk image file Annuminas.sparsebundle is mounted read-only when Time Machine attempts to mount it for writing subsequent backups to!
    The only way I can recover is to erase the backup and start another initial one, but that defeats the purpose of having a continuously running Time Machine backup.
    The client Mac is running Mac OS X 10.7.2 Lion, while the backup server is running Mac OS X 10.6.8 Snow Leopard.  The latter is really just using AFP services to export a disk to the network, whereas Lion is using Time Machine to make backups on the network disk.
    Any help or ideas would be greatly appreciated.  Many thanks,
    —tonza

    Oh... discovered something odd... the Time Machine Backups volume (that is the volume that is mounted from the Annuminas.sparseimage file on the fileserver) is being mounted read-only!
    /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local, nobrowse)
    map -hosts on /net (autofs, nosuid, automounted, nobrowse)
    map auto_home on /home (autofs, automounted, nobrowse)
    afp_000000004oMw0oYHtK1bbUQr-1.2d000004 on /Volumes/Rivendell (afpfs, nobrowse)
    /dev/disk1s2 on /Volumes/Time Machine Backups (hfs, local, nodev, nosuid, read-only)
    How is Time Machine going to write to a read-only volume?!  This is not making any sense!
    If there is one thing I do know about the BSD kernel is that filesystems are mounted read-only if it has been detected by the filesystem driver that a volume is marked dirty or corrupt.  Another thing I'll do is check via Disk Utility that Time Machine Backups needs to be fixed.  If Time Machine is indeed making faulty sparse images, it may be due to Snow Leopard's AFP server after all.
    —tonza

  • Time Machine Backups disk image displays the wrong capacity

    I have a USB hard drive partitioned and connected as an airdisk on a time capsule. The drive "TIME" is partitioned for 300 GB and serves both my MacBook (MB) and MacBook Pro (MBP).
    If I connect to TIME from Finder, it shows 155.68 GB free of 300 GB total.
    When MB runs Time Machine, the Time Machine Backups volume mounts and shows 155.68 GB free of 300 GB total.
    Here is what is weird - When MBP runs Time Machine, the Time Machine Backups volume mounts and shows 155.68 GB free of 429.5 GB total.
    Why does the MBP show a different and inaccurate total?
    I tried reconfiguring Time Machine to point to a different backup drive and then back to TIME hoping it would just 'reset' but that did not work.
    Something I just thought of - I did move that sparse from a different volume that was larger. I bet the total size is saved in the information in the sparse.
    Can anyone confirm this?
    Will this cause me any problems in the long run?

    redemily wrote:
    Something I just thought of - I did move that sparse from a different volume that was larger. I bet the total size is saved in the information in the sparse.
    That's possible, depending on how you moved the sparse bundle. If it had a smaller maximum size than the volume it's on, Time Machine would automatically resize it to the size of the volume it's on, making it larger (effective with 10.6.3).
    I don't know if it will make a larger one smaller, though.
    Will this cause me any problems in the long run?
    No. Time Machine will figure out how much space there really is anyway. But if you want to change the size, see #A8 in Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).

  • Time Machine Backups of Pages file cannot be opened by Pages

    I just restird a backup of a Pages file from my Time Machine backup volume.  It's not a Pages file!  Finder jusy says it's a document and if I double click it, a folder is created with the same name as the file with a number appended.  There are sevarla files in the folder - none of them can be opened by Pages.
    I'm aware of the Preference to save a backup copy but that saves just one copy, not a tru backup.
    Is there some way round this?  I'm not inclined to use a product if I can't back up it's files safely.
    Pete

    It's what I assumed.
    An iWork document created with the format introduced by iWork '09 is in fact a folder packed with a specific tool.
    If we remove the name extension, the system can't guess that it's an iWork document.
    According to the structure of the file, it recognize it as an archive and it unpack it.
    It's a variant of what I do when I want to study the contents of the index.xml file describing a document.
    In my scheme, I rename wxyz.pages as wxyz.pages.zip
    When I unpack it, I get a document wxyz.pages which is a Pages document in the old structure.
    When Time Machine give you a document entitled wxyz, it's important to add the extension name by yourself.
    If you forget and expand the beast as a folder, nothing is lost. Just rename the folder waxy as waxy.pages and Pages will open it.
    From my point of view, the fact that Time Machine return a document without its name extension is a bug in Time Machine.
    Yvan KOENIG (VALLAURIS, France) lundi 2 mai 2011 22:30:54
    Please :
    Search for questions similar to your own before submitting them to the community
    To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

  • Time Machine: Backup Disk Not Available

    I realize there are a few topics floating around about this issue, but I'm still not finding a solution. Not sure if my situation is different than the others but figured I'd take a shot a describing my scenario in a new thread and seeing if it generates any new ideas.
    I have a 2TB Seagate external expansion drive connected to a MacMini on my home network. The drive is formatted as Mac OS Extended (Journaled) and is not partitioned.
    I have mounted the drive on my MacBook Pro 2.66/i7 running 10.6.6. I then go to the TM Preference pane and select the drive, enter the username and password for my admin account on the Mini. It indicates that it's preparing and then comes back a minute later with a Time Machine error indicating that the backup drive is not available.
    I have an older MacBook Pro, my sons MacBook, and my wife's Macbook also on the network. Each of these Macs can mount the backup drive, select it in the TM Preference pane and successfully begin and maintain the TM backup.
    I have created a second "test" account on my MacBook Pro. I have followed the same steps and have had no problems with time machine preparing and successfully beginning the back up account.
    So - with those facts - I have had to conclude that there is something amiss with my main account.
    Other steps I have taken on my MBP with my main account include:
    * Deleting the com.timemachine.plist file from /Library/Preferences - restarting and trying again. No luck.
    * Restarting into applejack and performing an "applejack auto restart". No luck
    * Removing all timemachine related entries in the Keychain, running Keychain FirstAid. No luck.
    * Reformatting the external drive on the Mini, repairing permissions and running a disk repair and starting all over again. No luck.
    In each case above a restart was done before attempting to reinitiate the TM process.
    So - with out blabbering on with any more details, I think it's clear that I'm at a bit of a loss as to what else I should try. I'm WIDE open to suggestions.

    I resolved this issue just this morning (see below). This may not (or may) apply to your situation because yours magically corrected itself, but hopefully it will help somebody.
    Environment Architecture: We appear to have a very similar system architecture to the one you describe. In my case, we have 4 macs all relying on Time Machine and a networked 1TB Time Capsule for backups. Each of 3 workstation macs share data from the 4th, which we use as a primary server. I ran into my problem when the Time Capsule filled up and stopped backing up our primary server due to lack of available space. All recommended solutions for freeing up space appeared time consuming, and because we do daily off-site backups through MOZY (we use Time Machine for simplicity of recovery for hourly backups) I could take the "easier" path of just reformatting the Time Capsule's data drive and start again fresh.
    Problem identified: Per instructions, I used Airport Utility to erase my Time Capsule data drive, but thought I'd check my existing settings while I was there. Seeing the password prompt, and not remembering for sure what my password was, I thought I'd just reset it to what I wanted. Seemed benign at the time. When I started my 1st system's backup, I was prompted for the Time Capsule's password, and entered the new password. It accepted it as it should have, but then rejected the backup with a message indicating that I had provided the incorrect network account and password. The odd part was that it had originally accepted it, and even flashed the available space on the Time Machine preferences window. After much searching through these topics, I discovered that the password is stored multiple times -- some correctly and some not. Correcting the passwords fixed the problems.
    Where to look:
    http://support.apple.com/kb/TS2048
    Mac OS X 10.5.3 or later: Time Machine - "Backup volume could not be mounted" after changing network volume's password
    * Last Modified: October 14, 2008
    * Article: TS2048
    As it turns out, Apple stores that password in multiple places in your Keychain (don't ask me why!), even using the identical Keychain entry name. All I can presume is that one piece of the software looked in one Keychain entry, and another looked in a different Keychain entry. The passwords were different (one was my original password, and one was my new password). Once I changed them to the same thing on each of my satellite stations, they all worked again and Time Machine is happily chugging along on all workstations.

  • Cannot access old time machine backups

    Hi,
    I recently had some issues regarding my MacBook Pro and decided the best course of action would be to ensure it was completely backed up; reinstall OS X Yosemite and pick the old backup for useful files.
    Unfortunately, when it came to resetting up Time Machine, it asked me if I wanted to use the existing backup.  I imagined the safe answer would've been "Yes" and that it would've been smart enough to create a clean backup at the date of restore.
    It seems that this is not the case...
    Any backup, despite being listed on the Time Machine interface, prior to the date of restore was "greyed out" and could not be accessible.  Unfortunately, the "Browse other Backup Disks" option didn't work (are there issues with this option for NAS backups?), and unfortunately, a repair disk doesn't seem to either.
    I have only managed to get the .sparsebundle (encrypted) drive to mount once by using a repair disk; every other time I attempt to remount using repair disk, the button is greyed out. :/
    The time I did get into the "Time Machine Backups" volume; only once backup was listed for ".inProgress" – a 70GB file (the sparsebundle is ~500GB+).
    Any ideas on steps I can try to find these phantom files?
    At present, Disk Utility doesn't have the "Repair Disk" option available and DiskWarrior 4.4 is throwing up error 2154; low memory; on a 16GB RAM rMBP.
    Any help would be appreciated.
    Regards,
    Jamie

    I am having a similar problem and do not understand the solution. I have a new Macbook and transferred my data from my Powerbook G4. However, I cannot access anything! There is a no entry sign on the folders and if I click them I get this message: 'The folder “Pictures” can’t be opened because you don’t have permission to see its contents.'
    Help - but please, in simple language
    Thanks

  • Every other time machine backup to timecapsule is too large

    Hello,
    I have a strange thing going on here. I am running 10.8.2 on a MBP early 2011. I backup with time machine to my timecapsule via WiFi and to an external drive connected to USB. Both backups are encrypted.
    Everything worked great for a year. A couple of weeks ago I had to reset my MBP from a backup. Worked fine as well. After that time mashine did a new complete backup.
    Since then, sometimes my incremental backups get as large as 37GB even though not much has changed. I have excluded my downloadfolder and also my Virtual machine (Windows XP via parallels). The backup begins and is being calculated to be lets say 3MB large but during the backup the size grows up to 37GB.
    This happens maybe once a day. Eight backups or so just work as always and then all of a sudden 37GB again. And the funny thing, this does NOT happen at all backing up to the external HD, ONLY when backing up to my timecapsule.
    What I have tried so far:
    - I reset my timecapsule i.e. I deletd all backups and did a fresh complete backup
    - I reset timemachine as described here    http://pondini.org/TM/A4.html
    This did not help. I found out comparing the backups that when it comes to a 37GB backup the following folders are backed up to an great extend if not completely:
    - Machintosh HD / System, Library and Applications
    This is really frustrating as it takes so long for large backups...

    OK, it looks like it IS supported to have a Time Machine backup to an external drive hanging off a Time Capsule:
    http://support.apple.com/kb/HT2038?viewlocale=en_US
    "...but you cannot choose AirPort Extreme's AirPort Disk as a Time Machine backup volume.
    However, you can choose Time Capsule AirPort Disks or internal disks as a Time Machine backup volume."

  • Retrieving work files/data from a time machine backup off another computer

    If I create a time machine backup on one imac (imac 1) onto an external drive, I want to know if I can use this backup on another mac (imac 2) and restore or retrieve the old work files as and when required work from the external drive (time machine backup)? onto imac 2?

    You can't use Time Machine for Restoring on iMac 2 (if you made an TM Backup with iMac 1), but you can easily drag files from the "Time-machine-Backup-volume" in Finder on your iMac 2!

  • Time machine backup illegal name

    Hi there, I've just finished setting up a new time machine backup and moving other files to my external hard drive but today i plugged it in and it wouldn't mount. I opened Disk Utility and tried to mount and repair disk but nothing has happened, all i get is errors saying illegal name and that it is unable to be repaired. I've seen that this can sometimes be caused by some adobe software but I have none installed or on that disk. I have also tried repairing it with DiskWarrior but all the options are greyed out. Here is the error by Disk Utility i get now:
    Verify and Repair volume “Time Machine Backups”
    Volume repair complete.
    Updating boot support partitions for the volume as required.
    Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    The first time i tried repairing i got two illegal name errors. The disk still mounts in under Windows 7 but i don't want to use that.
    Any suggestions?
    I am running Snow Leopard 10.6.8 on my MacBook

    DiskWarrior ended up working and I rebuilt the directory

Maybe you are looking for