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.

Similar Messages

  • Unable to exclude VMware disk image from Time Machine backup

    In Time Machine Preferences, I elected to exclude home\Documents\Virtual Machines folder in my home directory. Whether I use the "+" button to add the exclusion or dragged it in from Finder, the exclusion list only shows [Virtual Machine]. Coming from a Windows world, I am concerned that I don't see the fully qualified path for the "Virtual Machine" folder name. Even the folder property doesn't show the full path information. Since I do not exclude Documents folder, it is included in all Time Machines backup. Unfortunately, so is my home\Documents\Virtual Machines folder.
    Question #1: What am I missing?
    This question is related to this next issue.
    Question #2: If I have a folder called "Users Guide" in addition to the built-in "Documents folder in my home directory, and they each contain the sub-directory "Preliminary", how do I tell Time Machine I want to exclude the folder \User Guide\Preliminary from TM backup?

    Thanks for the tip. Hovering does show the path. Now the mystery is a little worst than before, and I'm back to trying figure out how to exclude the home\Documents\Virtual Machines folder (where he VM disk images are stored) from Time Machine backups while it's allowed to backup home\Documents (as intended).
    When I get back home tonight, I'm going to try excluding some other sub-folders (which I created) of [Documents] from Time Machine while I allow [Documents] to be backed up. I'll post the results, and hopefully can ask a smarter questions.

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

  • Verify Disk failed for Time Machine backup disk

    Thread <http://discussions.apple.com/thread.jspa?messageID=7930301&#7930301> discussed a similar issue, but it was closed without an answer so I'm opening a new one.
    After a power failure I ran Disk Utility to Repair Permissions on my boot disk and Verify Disk on another that I use to store media files; neither had significant problems. Then I ran Verify Disk (verify, not repair; and disk, not permissions) on my Time Machine backup disk. It started spitting out the errors shown below. The time remaining counted up to 16 minutes, but wasn't coming down very fast so I left it running overnight. My machine is set to not sleep or spin down the disks. The next evening it was down to 12 minutes left, and was still spitting out the same errors. The second evening it was done, having failed out as shown in this log file excerpt:
    2009-06-20 22:25:48 -0400: Verifying volume “Backup”
    Starting verification tool: 2009-06-20 22:25:48 -0400
    2009-06-20 22:25:50 -0400: Checking Journaled HFS Plus volume.
    2009-06-20 22:25:50 -0400: Checking Extents Overflow file.
    2009-06-20 22:25:50 -0400: Checking Catalog file.
    2009-06-20 22:35:21 -0400: Checking multi-linked files.
    2009-06-20 23:08:17 -0400: Checking Catalog hierarchy.
    2009-06-20 23:16:59 -0400: Checking Extended Attributes file.
    2009-06-20 23:18:34 -0400: Checking multi-linked directories.
    2009-06-20 23:31:05 -0400: 2009-06-20 23:31:05 -0400: Incorrect owner flags for directory hard link (id = 3763501)
    2009-06-20 23:31:05 -0400: 2009-06-20 23:31:05 -0400: 2009-06-20 23:31:05 -0400: (It should be 0x2 instead of 0x0)
    2009-06-22 15:14:54 -0400: 2009-06-22 15:14:57 -0400: Incorrect owner flags for directory hard link (id = 7746623)
    2009-06-22 15:14:59 -0400: 2009-06-22 15:15:00 -0400: 2009-06-22 15:15:02 -0400: (It should be 0x2 instead of 0x0)
    2009-06-22 15:20:35 -0400: Checking volume bitmap.
    2009-06-22 15:20:37 -0400: Checking volume information.
    2009-06-22 15:20:39 -0400: 2009-06-22 15:20:41 -0400: The volume Backup needs to be repaired.
    2009-06-22 15:20:43 -0400: Error: Filesystem verify or repair failed.2009-06-22 15:20:44 -0400:
    2009-06-22 15:20:44 -0400: Disk Utility stopped verifying “Backup” because the following error was encountered:
    Filesystem verify or repair failed.
    At that point the whole system was extremely sluggish, and the access light on the backup disk was flashing steadily. The pmTool process seemed to be running away, but the system wasn't responsive enough for me to do much about it, so I held down the power button to shutdown. Upon the 2nd restart the system booted and seems to be OK, but I'm leery of running another Verify Disk.
    What's going on? Are those errors anything to worry about? Is it possible to run Verify Disk on a Time Machine backup disk? What about Repair Disk?

    John Seal wrote:
    2009-06-22 15:20:43 -0400: Error: Filesystem verify or repair failed.2009-06-22 15:20:44 -0400:
    2009-06-22 15:20:44 -0400: Disk Utility stopped verifying “Backup” because the following error was encountered:
    Filesystem verify or repair failed.
    At that point the whole system was extremely sluggish, and the access light on the backup disk was flashing steadily. The pmTool process seemed to be running away, but the system wasn't responsive enough for me to do much about it, so I held down the power button to shutdown.
    Any time Disk Utility says you need to repair a disk, you need to repair it. Period.
    So run it. If it fails to repair everything, run it again (and again) until it either repairs everything or can't repair any more. If it can't repair it, post back and we'll discuss options.
    There's no point in running +Verify Disk+ on an external drive; just run +Repair Disk.+ The only time +Verify Disk+ is needed is for your internal HD (because you can't repair the disk you're running from).
    And you need to do that again because of the forced power-down. Any time there's an abnormal shutdown, it's possible the file system on your internal HD can be damaged. Usually it isn't, but it's possible. If that says you need to repair it, you'll have to boot from your Leopard Install disc and use it's copy of DU. Post back if you need to do this but don't know how.

  • I want to use two separate Lion Time Machine backups and use them to create two separate profiles on one new computer

    This is something I need to do temporarily but I must do it. 
    I have an iMac 27 (end of year 2009) I5.  It has 1 TB internal and I want to replace it with a 2 TB internal.
    I have time machine backups on an external hard drive that has been connected via Firewire. 
    I have another iMac (my son's)Imac 24 Intel Core 2 Duo that has it's own separate Time machine backup to it's own separate firewire connected external drive.  Both machines are completely up to date with the latest version of Lion and all other necessary software updates.
    When the internal hardrive is replaced - I want to use my latest time machine backup to create one profile on the imac and then use my son's latest time machine back up for a second profile.  The end goal being to have everything from my current set up ie: apps, documents, itunes, etc existing in one profile and everything in my son's current set up existing in the other profile.   We can both be administrators for the time being as well.  I should note even though we both have some of the same apps, we both also have other apps that the other does not.
    My profile will be using about 900 gigs of total space.
    My son's profile will be using about 250 gigs of total space.
    This is temporary until the new iMac is released.  Then I will want to transfer my profile to that leaving my son's intact on the iMac 27 I5.
    I realize that during the temporary period that Time Machine will be making backups of this entire two profile setup, which I am now understanding as I write this will create a new issue for me when I want to transfer only my profile to the new computer as well.  But one bridge to cross at a time, I guess.
    I need to do this because we must bring his current computer to my father - as his iMac G5 is inoperable.  We have been doing this round robin hand me down in our family since IMac DV special edition :-)
    Any insight on this would be greatly appreciated.  And any other suggestions as well.
    Thanks very much.

    Hey Shootist000,  Thanks for the replies.  First off, I am actually okay if we both have each other applications so I am not concerned about that. It is still unclear from what you have said as to whether I can in fact, use these two separte time machine backup to create two separate profiles on the new hard drive.  If that in fact can be done, then - will it create two copies of the apps we both have in the ROOT of the drive as well as placing all the ones we each have separately?
    And reading your second reply, makes me think that maybe the partition is the way to go to begin with and then down the road - after I am in the new iMac, I could reformat the iMac 27 with only one partion and restore my son's latest back prior to the reformat thus giving him full access to the 2 TB of the drive.
    If this is still making sense, does this mean :
    replace the 1TB with a 2TB - but have it partitione - 1.5 TB & 500 GB.
    Install(Restore using Time Machine) my latest back up prior to the  1.5 partition
    Install (Restore using Time Machine) my son's latest back up prior to the 500 gig partition
    Lastly, in order for us both to be using the partioned computer - I am assuming Switch user can no longer be used - so would we need to restart and select our respective partions in order to use the computer?   And if so, how would we each be able to be using time machine to back up - two separte external hard drives - with each one dedicated to only one partition? Or ? 
    Thanks so much.
    Ironically, I am only trying to do this so that I don't need to manually install all his apps, setting, games, blah blah for this temporary period.  :-)

  • I have created a new partition on the Mac HD for Lion as I would like to dual boot. Do I need to install Snow Leopard on that partition before installing Lion? If so, can I use one of my Time Machine backups to do this?

    I have created a new partition on the Mac HD for Lion as I would like to dual boot. Do I need to install Snow Leopard on that partition before installing Lion? If so, can I use one of my Time Machine backups to do this?

    zoominnana wrote:
    Can I set up 2 different time capsule backups? one for the lion partition and one for the snow leopard partition?
    No, you can't partition a Time Capsule's internal HD.  Both partitions will back up to the same sparse bundle. keeping the backups for each partition separate.
    Time Machine will not take the two OSX partitions as two different computers, but for best results, exclude the Snow Leopard drive from backups on the Lion partition, and exclude the Lion partition from backups on the Snow Leopard partition.
    There may be some files on the Lion partition that Time Machine on Snow Leopard won't like, among other things.  See #10 in  Time Machine - Frequently Asked Questions for details.

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

  • Can the time capsule be used as both a time machine backup and NAS storage

    Can the time capsule be used as both a time machine backup and NAS storage?   I want to use the drive as external, wireless storage for all of my files so all my PCs, MACs and iOS devices can access the files.  Plus, I want to use the drive for backing up my iMac via time machine.  Can the time capsule device be used for both these purposes simultaneously?  If not, are the other suggestions on how I can do this?

    Can the time capsule device be used for both these purposes simultaneously? 
    It can, but is really not recommended. Sooner or later there will be a fight for space on the drive between Time Machine and the other files.
    If you have plenty of free space on the drive, you can do this......but.....have you thought about how you will back up the "other" files that are stored on the Time Capsule?

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

  • Using Automator to start Time Machine backup then eject?

    I've been fooling around with Automator because I want to create an application so when I mount my Time Machine disk and I run the application, the Time Machine backup with start and once it's finished it will automatically eject the volume.
    I used the following shell script to begin the TM backup:
    /System/Library/CoreServices/backupd.bundle/Contents/Resources/backupd-helper &
    I used the following Applescript to eject the volumes:
    tell application "Finder"
              eject (every disk)
    end tell
    The problem is, when I save it as an application and I run it, I can see TM backup starts but it immediately ejects the disk. What can I add so it will eject the disk AFTER the TM backup has completed?
    I have a MBP (late 2011) with OS X 10.7.4

    Two comments:
    1) Try removing the ampersand ("&") from the end of that command.  The ampersand causes the command to continue in the background while the script continues to the next step.  You want the script to wait until that command is complete.
    2) You posted your question in a section for Apple's Time Capsule Wi-Fi router.  Presumably you want support for the Time Machine backup hardware.  Such a question should be posted in the section for the OS X version you're running.

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

  • Use TC 2TB for Time Machine Backup and Storage simultaneously?

    Hi
    I am planning to buy a TC 2TB.
    I would like to know if the TC can be used as a Time Machine backup device and for storage simultaneously?
    for example:
    Can I use 1TB for Time Machine backups and 1TB for storage.
    Please let me know if this is possible?
    Thank you

    I tried for ages to seek a relatively easy way to do this.. i.e. partition it, it's a huge pain! You can, but i'm pretty savvy and got bored and confused! What I did do was switch the TM back-ups to manual so they don't end up filling the disk. Trust me it's the easiest and best option!

  • Using Ipod Classic for Time Machine backup

    If I use my Ipod Classic (60GB) as Time Machine Backup will it converted to a storage device only loosing my music and videos?.

    you can't use an ipod as a TM disk.
    http://docs.info.apple.com/article.html?path=Mac/10.5/en/11421.html

  • Iphoto images on time machine backup

    Hi All
    Can someone tell me where to fine my photos on my time machine backup, I import using iphoto and if I 'get info' on an image from within iphoto it shows, 'Users/MacBook/Pictures/iPhoto Library/Originals/2009/Centre Parcs April 2009', however if I try to find this on my backup it just shows the 'root folder'(iphoto) icon and I'm unable to open it any further into the sub directories, what am I doing wrong?

    See the pink box in #15 of [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
    Avoid using the Finder or Terminal on your TM backups; if you inadvertently change, move, or delete anything there, it can corrupt them, perhaps beyond repair.

  • Latest 3TB Time Capsule disk offline after Time Machine backup

    I just replaced my 3 year old 2TB Time Capsule with the latest 3TB Time Capsule.  I also replaced both of my wireless network extender Airport Extremes with the latest model.  The Time Capsule disk goes offline after a Time Machine backup.  I have to reboot my Mid 2010 Mac (Yosemite 10.10.1) to get the disk back online, only to have it go offline again after the next Time Machine backup.  I am not sure if the problem is with my new Time Capsule or if there is a problem with my iMac.

    The fact that it is the Mac you are rebooting indicates the issue is the OS.
    Are you using wireless or ethernet?
    As you can see with a quick glance down this page.. and the last few pages.. the introduction of Yosemite has not been without issues.. network in particular has been poor.
    I am keeping myself out of fray.. having introduced a test Yosemite machine which caused the network to go completely berserk I have left well alone.
    But I am tracking the issues.. so far nothing much is known.. so I can only suggest a few things to try.
    One user has just suggested turning off AFP in the system preferences.
    the simple method: System Preferences, Sharing, File Sharing, Options button, un-check AFP.
    SMB should still be checked.
    You should be able to manually mount the TC in finder.
    Use Go, Connect to Server.
    SMB://10.0.1.1
    (Thanks for the screenshot as that makes it much easier).
    Finder should locate the network resource and mount it.. asking you the password.. please save that in the keychain so it doesn't forget.
    Here is apple's list.
    OS X Yosemite: Time Machine problems
    It has not got anything close to locating the problem. But there are some things that may be important.. ie it can be several bugs in combo not just flick this switch and now everything works.

Maybe you are looking for