Moving Time Machine Drive from Direct Connect to Network Share

I have a 1 TB external USB 2 drive I use for my Time Machine backup. I'd like to move that drive to a file server and continue backing up to it. The problem appears to be that when backing up to the drive as a network volume, Time Machine wants to create a new sparsebundle for the backup and not use the existing TM backup folder on the drive.
Is it possible to migrate a Time Machine drive from direct connect to network while preserving the backed up data? Thanks!

Kenneth Kirksey wrote:
I have a 1 TB external USB 2 drive I use for my Time Machine backup. I'd like to move that drive to a file server and continue backing up to it.
Depending on what "file server" you're using, that may or may not work reliably. Here's the criteria they must meet: Disks that can be used with Time Machine. And be careful here: just because some 3rd-party hardware claims to support Time Machine doesn't necessarily mean that Apple supports it, or that it will work in all circumstances.
The problem appears to be that when backing up to the drive as a network volume, Time Machine wants to create a new sparsebundle for the backup and not use the existing TM backup folder on the drive.
That's correct.
Is it possible to migrate a Time Machine drive from direct connect to network while preserving the backed up data? Thanks!
See #18 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).

Similar Messages

Problems moving Time Machine drive from USB to Airport Extreme

Greetings compadres.
I'm using a WD external Mac hard drive for my Time Machine backups. I was using a USB hub and directly connecting my MacBook to the hub, thus a seamless connection to the external hard drive.
Now, I want to connect my external drive to my Airport Extreme for wireless back ups. I tried this before and I couldn't figure out a way for the system to recognize the drive to continue my previous back ups. Eventually, I just reformated the drive and started my back ups over.
Is there a way to switch to wireless and continue my old back ups?
Much obliged,
- robert

That's not supported by Apple, but Pondini has some advice on the matter here: http://pondini.org/TM/AEQ2.html

Moved Time Machine drive - can't see backup.

I was having trouble with my Time Machine drive, which was connected by USB to my Airport Extreme. I moved the drive to a USB connector on my MacBook Pro to improve the speed, and after formatting the drive, made a complete, new backup with Time Machine, which took about 8 hours.
Then I moved the drive back to the AirPort and told Time Machine to use it for backup. Time Machine doesn't see the earlier backup (I can verify that it's there using the Finder) and is now doing another complete backup of my MBP.
What's wrong here? How can I tell Time Machine to use the backup it made yesterday instead of starting over?
Walt

Actually, Tech Support told me that they support only Apple Time Capsules connected to the Air Port Extreme. They most certainly do NOT support using Seagate drives such the ones I have been using successfully for over three years, on two MBPs.
I firmly believe (but Apple does not want to hear this) that my problem originated with the erratic WIFI connections since I upgraded to Lion, which has been discussed at length in the forums. Time Machine reported backups failing when the WIFI connection could nto be restored after waking from sleep.
My wife's MBP, running Snow Leopard, is working just fine on the same hardware.
Walt
EDIT: I tried "Inheriting" the backup that was made via the direct USB connection, but it still doesn't show up in the TM history. The tmutil program is interesting - it does distinguish between the "machine_directory" - the backups.backupdb folder that was made by the direct USB backup, and the sparse_bundle file that was created by the AirPort backup.

Moving Time Machine backups from Time Capsule to External USB Drive

Hi all,
hoping someone out there can help I'm trying to move my time machine backups from my old Time Capsule to my external USB drive. I've already used the Airport Utility to "archive" my Time Capsule to a USB connected WD MyBook Elite.
Right now my WD MyBook Elite has both the archive, and recent (roughly 5 backups) of both my MacBook & MacMini. I've tried to follow the seemingly simple steps located in the FAQ's here [URL="http://web.me.com/pondini/Time_Machine/18.html#id22"]Copy NETWORK backups to be used LOCALLY[/URL] , but I cannot past step 1.
[Quote]Right-click the new volume on your desktop or Finder sidebar and select Get Info. If the Ignore ownership on this volume box is checked, click the padlock at the lower right and enter your Admin password at the prompt. Then remove the check mark from the box and close the window.[/Quote]
There is no option to "Ignore Ownership" in Snow Leopard for the Spars Bundle or when expanding it to see its folders.
Any advice?
I'm basically trying to combine my backups to unit them into one seemless backup each for:
Mac Mini & MacBook.
Thank you in advance.

Dark Heart wrote:
[Quote]Right-click the new volume on your desktop or Finder sidebar and select Get Info. If the Ignore ownership on this volume box is checked, click the padlock at the lower right and enter your Admin password at the prompt. Then remove the check mark from the box and close the window.[/Quote]
There is no option to "Ignore Ownership" in Snow Leopard for the Spars Bundle or when expanding it to see its folders.
That's not referring to the sparse bundle you're copying FROM, but the new volume you just formatted on the USB drive you're copying TO.
If you didn't just format the partition, that box may not be shown -- it not, there's no problem and you don't need to do anything in that step.
I'm basically trying to combine my backups to unit them into one seemless backup each for:
Mac Mini & MacBook.
I'm not sure what you mean by that: you cannot combine the backups of two different Macs. You can put them both on the same hard drive, either in two different partitions, or, if any are going to be backed-up over a network, in a sparse bundle.
If I've misunderstood, please clarify exactly what you're trying to do.

Can I move the time machine drive from being a usb drive

Hello
I am not sure whether this fits best in the time capsule or in the time machine forum. I try here as this a issue thar arises only to time capsule users.
I have a new USB drive that I want to use for time machine backups. Eventually I want it to be attached to the time capsule and make the time machine back up via wifi. However the first backup is 261 Gb and this is too long for the wi-fi. I am doing it right now via the USB and take 12 hours (estimated).
After the USB backup will be finished, can I move the drive to the time capsule and let time machine make the backups via wifi? I mean, is time machine going to find the backup done via USB or once started with USB I am stuck with that?
Thanks for answering and for reading
Roberto
PS
maybe was better on the time machine forum, still don't know.

Backup strategy
Backing up a client computer to Time Capsule hardware with Time Machine software via the network provides ample time for contemplation, and rumination as to why the backup is taking so long. An initial 200Gb backup has an estimated time of "3 days" even on a wired network. Incremental backups following the initial backup are also beset with delays, with various message which can be viewed with the programmer's delight, the "Console" app. Otherwise the System Preference Time Machine interface is mute. The glacial pace of the Time Capsule backup process is exhaustively documented on the internet, but with no solutions - at least that I have found any after too many hours searching.
The System Preferences->Time Machine interface is always used to start a backup, monitor, or stop a backup, whether the backup drive is present on the network via Time Capsule, or if the backup drive is directly connected to the client computer.
On the positive side, Time Machine performs quickly and provides hourly backup to external drives directly attached to the client computer. The delay appears in network backups via Time Capsule.
Another positive is that network backups to Time Capsule are reliable when the client computer is stable, always on, and never detached from the network. In this case, the mute interface offered by system preferences->Time Machine is welcome. For example, my Apple Mac Mini web server (always on) is reliably backed up to a Time Capsule.
The negative experience is encountered when backing up a laptop when, as laptops do, the laptop wanders from the network. As stopping a backup can take 15 minutes, backups are necessarily interrupted when dashing off to work with your laptop. In the network where I have experience, there are 5 laptops and 1 stationary (Mac Mini) clients living on an all-Apple network. Failing to complete a backup via network for days on end gives no feeling of security.
Reading from Podini's excellent website
http://pondini.org/TM/Works.html
and extracting a summary, files copied from a client computer using Time Machine are stored on the backup drive in one of two formats: sparse bundle (special file type) when backing up to Time Capsule (or to a drive attached to a Time Capsule), or a folder with the client computer name when the backup drive is Firewire attached to the client. A closer examination of the sparse bundle file on the network with the Finder shows that the same folder appears with the computer name.
So, Time Machine backups always go to a folder with the client computer name, and this folder is either inside a sparse bundle or not depending upon if the backup drive is mounted on the network via TC or directly attached to the client.
An external drive mounted on the network via Time Capsule will create a sparse bundle file for the client or add to it if it already exists. Even if backups are present of the same machine, but not in a sparse bundle, Time Capsule will create a sparse bundle if it does not exist for the current backup client computer, and start a new backup.
An external drive directly connected to the client has a different experience. No Time Capsule is involved. Upon turning on backups via Time Machine, the backups will go to a sparse bundle file with the client computer name, if it exists. If the sparse bundle file does not exist, a folder is created with the computer name.
A strategy of backing up to an external drive moved between various computers and the Time Capsule might resolve some of the many delays. The strategy is simple, if delays are encountered, directly attach the backup drive to the client computer. If a backup is to be manually deleted in order to begin anew, directly attach the backup drive to the client computer before deleting the sparse bundle file.
To begin a new backup with this strategy of "drive+TC", initiate (via TM) the backup on the network (via TC), then stop after 10 minutes (with TM), noting that a sparse bundle of zero size is created. Continue the first backup by directly connecting the external backup drive to the client then pointing Time Machine to the newly connected drive. The backups by way of direct connect will go to the existing sparse bundle. Wait three hours rather than three days for a 200Gb backup to complete. Subsequent backups will go to the sparse bundle file on the backup drive, whether the backup drive is on the network (via TC) or directly connected.
But what of the internal drive on the TC? In this strategy, it is not used for backups unless the client computer is always attached to the network.
With so little documentation from Apple, we are left to speculate as to the cause of TC largo. Normally, slight documentation means little to know for the user, and the user is spared the complex machinations under the hood, but when the operation is flawed the user is left without resources.
A secure backup strategy stores a backup offsite, just in case the house burns down, or buglers make a clean sweep of computers and backup drives. Unfortunately, this means doubling the equipment, including two Time Capsules and two external drives attached to the TCs. The offsite copy is rarely mentioned in the same paragraph as the Time Capsule, likely because of the cost. It's an uncomfortable fact that a sole TC is vulnerable to local hazards, along with the local client computers.
This is the strategy I'm testing now. I'll send an update in a few days.

Time Machine will no Longer connect to network drive.. Although the drive is visible and accessible by the system.

Time Machine was working fine, until one day back up was failing due to being unable to delete the old backup. now it will no longer connect to the network drive although the external drive is accessible through the system.. any ideas?

Time Machine is completely unrlable on any networked drive unless that drive is connected to one of the new Airport Extremes. I'm not surprised that you're encountering problems with it if you're using a networked drive. Can you plug the drive into your MacBook Pro and see if it will backup? The backups may - probably are - corrupt.
Clinton

Moving Time Machine Backup from Old Mac to New Mac

I had my old MacBook happily backing up via Time Machine to my Time Capsule. Then I bought a new MacBook and moved all my files etc across with the Apple Migration Assistant.
However, having problems with TM - tells me there is no room on my TC to complete my backup (not true, plenty of disk). However, I suspect this is because it views the backup data on my TC as "owned" by the old Mac and hence that chunk of disk is unavailable to the new Mac.
Is there a way to associate the old backup data with the new Mac?
Or do I need to wipe the TC clean and start all over again?
Thanks,
SM

Hello only:
I performed a similar migration a couple of months ago. In my case, I used a SuperDuper clone on an external firewire drive as the source, but what you describe (#1) should work fine. In any event, keep the G5 handy as you can firewire attach it to the new Mac if you wish.
If I were you, I would just delete the files you do not wish to move from the G5, run a backup now for Time Machine, and then proceed with your transfer.
Barry

How to setting up new (June 2011) TC to do wireless time machine backup but not connected to network?

Hello. Just got new (refurbished June 2011, 2TB) Time Capsule. My building has a shared wifi network, and I'm assuming it's hard to join the network with Time Capsule and still be satisfied with security/privacy/performance. (Of course, if I'm assuming wrong, please let me know!)
My understanding is that I can use Time Capsule wirelessly to do Time Machine backups by switching out of my wireless network to - I assume - a new Time Capsule generated network(?). It's an extra step, but that beats connecting cables to the computer everytime I need to do backup. Basically it's like an external wireless hard drive that I have to join everytime the backup is updated, right? (Again, if there is a better way to go about doing this, please let me know.)
So how do I go about doing this? The setup manual isn't helpful (not at all).
Here's more detail if necessary. I have 10.8 Macbook Air (which I plan to upgrade to 10.9 soon) and my spouse is running 10.9 Macbook Pro. I am also assuming I don't have to partition Time Capsule, and when the Time Machine backs up, it'll figure who's who.
Thanks in advance.

Hello. Just got new (refurbished June 2011, 2TB) Time Capsule. My building has a shared wifi network, and I'm assuming it's hard to join the network with Time Capsule and still be satisfied with security/privacy/performance. (Of course, if I'm assuming wrong, please let me know!)
Security is ok.. but performance is abominable.
The TC unfortunately has some design limitations that Apple imposed that makes it rather poor for anything but ethernet.
There is a couple of ways around the problem of sequential internet or backups.
1. Get a wireless bridge that is suited to your in-building system.. and plug that into the TC so it can take normal router settings .. This will give you double NAT but I doubt your in building system will be handing out public IP anyway. An airport extreme can do this. Although it is pricey for the same results as a $35 standard wireless bridge. All devices in your place will then get both internet and backup direct to the TC.
One flaw here could be the download limits.. if you have two connections do you get double the downloads.. ??
ie how many IP are allocated to you?? And is it divided between all of them or the more IP clients the more download bandwidth?
2. Use a USB wireless stick in the Mac.. these can be tiny little things now.. just buy Mac compatible ones.. use that for internet and use the internal (faster) wireless for local connections. there are some manual setup tricks needed here but nothing hard.

Lost the ability to Spotlight Index my Time Machine drive

I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
So I've run out of things to try.
Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
--Bob

Well unfortunately the command
sudo mdutil -E /Volumes/MyDiskName
didn't help.
The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
However, this time there were console messages and a crash report.
The Console shows (with personal information x'ed out):
12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
The Crash Report reads as follows (again with personal information x'ed out):
Process: mds [28]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2007-12-31 13:30:38.746 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
Crashed Thread: 15
Thread 0:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0000cfa0 0x1000 + 49056
5 mds 0x00005580 0x1000 + 17792
Thread 1:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 4:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 5:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 6:
0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
2 mds 0x00009648 0x1000 + 34376
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 7:
0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
1 mds 0x000091b4 0x1000 + 33204
Thread 8:
0 libSystem.B.dylib 0x92f15438 kevent + 12
1 mds 0x0007e584 0x1000 + 513412
Thread 9:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 10:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 11:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 12:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 13:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 14:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 Crashed:
0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
13 com.apple.spotlight.index 0x0016529c runLoop + 72
14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 crashed with PPC Thread State 32:
srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
vrsave: 0x00000000
Binary Images:
0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
Any suggestions before I just Erase the disk and start over with a new backup?
--Bob

Cannot delete Time Machine file from external hard drive

Hello,
I'd like to delete my original Time machine file from an external hard drive ( Lacie mini ). I move the file into the trash bin and it constantly "deletes". At one time I left it deleting overnight and the file still wasn't trashed.
I am going to hook up Time Machine to a different, dedicated external hard drive, but I'd like to gain space on the drive that Time Machine is currently on.
I currently have Time Machine turned off ( I do have everything backed up with my home folder on another external HD ). Should Time Machine be turned on for me to trash the file? Is there a better way to delete the file?
Much thanks in advance.

V.K. wrote:
... the best and the quickest way to delete it is to erase the TM hard drive....
But what if a person doesn't want to erase the TM drive? My MacPro came with tiger installed, but since tiger-intel-retail discs don't exist, my copy of tiger is what i have. I was all manner of foolish directing TM to that drive, but damage is done. What can someone in my position do?

How do I move time machine files from one external drive to another?

My original external drive isn't big enough. So I've bought a second larger one. How do I move the earlier Time Machine backups from Ext Drive #1 to Ext Drive #2 so I can access my full history, and leave Drive #1 for other backup items?
Ext Drive #1= SimpleTech 120 GB
Ext Drive #2= WEstern 500 GB

When you are ready to pass the 320GB drive on, I would format it. That will make the entire drive available to him to use as his TM. I would be sure that each drive has a unique name so that there will be no confusion for TM as to which computer goes with which drive. If you want to start fresh with the 500GB drive, I'd format it as mac-extended-journaled. When you connect it the first time to your computer, you will be asked if you want to use it as your TM. If you are not prompted to select it as your TM, you can configure TM by opening system preferences, click on TM, click on "change drive" and choose your new drive.
Another choice is to follow the steps in my previous response for restoring your current TM to the new drive by booting from a Leopard start up disk and accessing Disk Utilities from there so you can restore the drive. It is essential that the new hard drive is the exact name as the old TM hard drive. In this last scenario you would continue adding to your current set of backups.

Problems Moving Time Machine to New Hard Drive, Error -8062

I'm in 10.8.5, trying to copy my Backups.backupsb folder from my current 2TB ext drive to a new 4TB drive, following Apples instructions for changing the Time Machine drive. Both are Seagates, single partitioned (GUIDE) formatted Mac OS Extended (Journaled.)
The 2TB is nearly full, hence the move. This morning after 12 hours of the projected 14 to copy the backups file over, I got an alert that action could not be completed because of Error 8062    I've found pages with suggested fixes from simple restart to more elaborate measures. The one thing I've done so far is restart and check Disk Permissions for both drives, which read as okay.
But before trying again, since error occured 12 hours into the process (of course it did,) I would like to see if the portion of the file that shows in the folder, size 1.46TB out of the 1.93 total, could be "replaced" by the original folder and thus not have to copy everything again.
One apparent problem is that, after a similar attempt to do similar replacement after a problem 3 hours into copying, instead of asking if I wanted to replace it, it just started copying it with "(original)" added to the end of the folder name. That file tagged (original) is the 1.46TB partial copy. So I deleted the much smaller initial partial copy, but of course the *true* original folder from the active Time Machine will not replace the existing partial copy. I don't know if removing (original) from its name so it matches will help because I can't; the folder is greyed out and I can't alter the name. I've tried changing Permissions on it, and tried Terminal commands that will supposedly change the name of a hidden file - nothing works.   Of course, I don't even know if it would ask to "replace" the next time I try, since it didn't do so when the folder names matched on the first attempt.   And since *when* does Finder not ask to "replace" an identically named folder, anyway? This begs the question if it is simply not going behave like a normal folder with files no matter what I do to it.
Is there anything else I can try? Barring a solution, any other precautions I might take to try to avoid the joy of anohter "cannot complete" 12 hours in?   I've got multiple backups to make of loads of data, including a full extra backup to keep offsite, and would love to avoid such time wasters.
Thanks for you kind assistance!
Brian

This looks right on point and very thorough. I've started a new backup directly to the new drive. Since I don't necessarily need the old drive for storage of anything else for the time being, I will probably do as he recommends and keep the old backups ther, at least until I'm reasonably sure I'm never going to need anything dating back that far, and long enough to confirm the new configuration is stable, and everything is there and backed up off site.
I"m all for simple solutions right now! :^)

How can I "Put Back" a time machine backup from the trash to my external hard drive?

Basically what happened was I accidentally put an older time machine backup from my external hard drive into the trash on my macbook. Since then, time machine has made new backups onto my external hard drive. How can I either "Put Back" or replace the deleted backup back into my hard drive?
Whenever I try to move it it says "A newer item named “Backups.backupdb” already exists in this location. Do you want to replace it with the older one you’re moving?" I click replace and after a few minutes of loading, it says "Cannot replace. An item named "" already exists."

As long as you don't delete the trash, the files should be recoverable.
I suspect using the Put Back command could take a long time, so be patient.
If your Time Machine backups are mixed with your daughter's backups you might want to buy a larger drive and move the Time Machine files to the new drive.
Regarding missing photos in iPhoto...There might be options to rebuild/recover that data from iPhoto rather than trying to revert to a Time Machine backup.
Check out this third party app, iPhoto Library Manager. It has a demo.
http://www.fatcatsoftware.com/iplm/
Options for a larger drive.
I like the Seagate USB 3.0 Backup plus drives. Works on USB 2.0 ports. They come formatted for PC but easy to format in Disk Utility.
I don't recommend Western Digital because of the boot problem with some of their drives.
LaCie makes good drives.
All Mac formatted drives will cost more and it’s easy to reformat with Disk Utility. Do not use the software that comes with the drives. It’s recommended that you use Apple’s Disk Utility.
Prices vary but this gives you an idea of what you’ll find. As you notice the second and third TB is usually only $15 more per TB. Normally, you’ll find these prices but right now the 1T is more than the 2T
Seagate Backup Plus 1 TB USB 3.0 $85
Seagate Backup Plus 2 TB USB 3.0 $99
Seagate Backup Plus 3 TB USB 3.0 $115
I have seen the 3T on sale for $99.
Locally, Best Buy seems to have the best prices.

Can I transfer Time Machine Backup from WD Hard Drive to Time Capsule?

I have a Western Digital 500 Gb. Hard drive and recently purchased a 500 Gb.Time Capsule which, at the moment, am using only for the AirPort feature. I would like to use Time Capsule for my Time Machine backups and use the Western Digital drive as my Aperture Vault. Is there a way to move the Time Machine file from the WD drive to the Time Capsule drive so that I don't lose the old files? My Time Capsule is connected to my iMac via an Ethernet cable.

Unfortunately, no. Time Machine will backup to a local drive (e.g. via USB or FW HDD) using a folder structure. When backing up to a NAS (e.g. Time Capsule or USB HDD connected to a TC or Extreme), TM utilizes a sparsebundle. You cannot easily convert a folder structure to a sparsebundle. The best plan is to start a NEW backup to TC. Connecting via ethernet is highly recommended for the initial backup.
P.S. You can still access the old TM backups until such time that you want to reclaim the use of the HDD.

Is it possible to boot or Time Machine restore from an external Thunderbolt disk drive?

(There are several questions - search for "?".)
I purchased a Seagate Backup Plus for Mac Desktop Drive 3 TByte with default USB 3.0 interface, and also acquired the Seagate Thunderbolt Adapter for Backup Plus Desktop Drives and Thunderbolt cable.
I do a redundant backup to the Seagate Drive using both Carbon Copy Cloner (nightly) and Time Machine (hourly) using its Thunderbolt adapter. BTW: One never knows when Time Machine will choke - see discussion titled, "UPDATED: Serious Time Machine bug on Mountain Lion", which I had; Rest In Peace Pondini (James Lewis Pond).
Booting from the external Seagate Backup Plus via Thunderbolt inteface from System Preferences -> Startup Disk:
I select the Time Machine OS X, 10.8.5 Startup Disk (Thunderbolt attached drive), click Restart, confirm my choice, the computer reboots, however, it reboots from the internal Macintosh HD OS X, 10.8.5, NOT the selected external Thunderbolt drive. The SSD drive was used as the Startup Drive, not the selected external Time Machine volume as indicated by the display free disk space command (df(1)) and seeing that the Macintosh HD OS X, 10.8.5 volume is mounted as root. That is very deceptive in that both the internal and external drives will appear in the same manner from a GUI point of view! OS X doesn't even inform me that it did not boot off the selected volume. This is the first half of the problem, that is, Is it possible to boot from an external Thunderbolt disk drive? In my case, the answer is deceptively No. Can anybody else boot off a Thuderbolt attached disk drive? Note that if I remove the Thunderbolt adapter, and attach the drive via its USB 3.0 cable, the MBP boots off the external Seagate Backup Plus just fine, as is expected.
Booting from the external Seagate Backup Plus via Thunderbolt inteface from boot-time "Option - Select startup disk" method:
When I restart the MBP using the startup Option key to select the startup volume, the externally connected Seagate drive ONLY SHOWS UP if it is attached with the USB 3.0 cable, not when it is attached with via the Thunderbolt interface. Can anyone else boot off a Thunderbolt drive with the startup Option key sequence? At least the MBP doesn't deceive me in this case - I know right away that the external Thunderbolt drive is not an option when connected as such.
Time Machine restore from the external Seagate Backup plus via Thunderbolt interface from the "command-R - Recovery Parition" method:
After booting from the recovery partition, I attempt to perform a Time Machine restore from the Thunderbolt connected Seagate Backup drive. When Time Machine attempts to present me with a viable backup Time Machine volume, the external Thunderbolt drive is never offered as an option. So I switch the Time Machine volume to use its USB 3.0 interface, and then Time Machine displays that drive as an option, and the MBP proceeds with the restoration as expected. The interesting thing to note is that while booted in the recovery partition via the Thuderbolt cable, the MBP Disk Utility may be selected, and the Thunderbolt attached drive may be operated on just fine. Can anybody else restore their MBP using Time Machine and the Recovery Partition via the Thunderbolt interface?
This is also a big problem for me in that I am forced to restore my MBP via Carbon Copy Cloner using the USB 3.0 interface, because I cannot even boot off that volume's Thunderbolt interface. Of course, the option may be that I could use yet another eternal USB 3.0 drive, boot from it, and then use Carbon Copy Cloner to restore the Macintosh HD via the aforementioned drive connected by a Thunderbolt cable, but that is less than ideal and not elegant, so I'm not going there.
Another side issue is that the commercially available program, TechTool Pro 7's eDrive, which I installed on the Time Machine volume, will not boot off that eDrive as advertised, but I won't got through those steps here, because that would be beyond the scope of this issue, however, I must say, It does not work either when the Time Machine volume is connected via the Thunderbolt interface, but works just fine when connected via the USB 3.0 interface.

If this helps anybody else make a decision about whether to consider Apple because of Apple's superior customer service:
Apple sells this entire line of drives right in their store, from 1TB to 4TB. I spent 1 and 1/2 hours, yesterday, confirming that the 3TB model IS NOT 100% Thunderbolt compliant. A MBP cannot boot, nor can it Time Machine restore from this drive, though EVERYTHING about the drive is normal.
Apple's South Coast Plaza store management had at least two responses to me personally about how to proceed:
1. Buy a different drive from another drive manufacturer, and to attempt to return the drive to COSTCO. A lead genius suggested going with GTech drives, for instance.
2. Wait for Seagate to fix their problem.
I told Apple management in the store that the drive is advertised as Mac Compatible (see picture) and that it is advertised as being a Thunderbolt drive (see picture). I pressed management that my purchasing decsion to get the best possible MBP Retina was based on the availablity of Inexpensive Devises (raID), and that not having this complete compatibility is a show-stopper for my needs, and that I wanted a refund. Their response? They needed to talk with "Merchendising" to see if they are on or off the hook for these kind of 3rd party assertions, and would get back to me.
I am not holding my breath.
Note: I do not hold this against the Geniuses that helped me, nor against the management I've dealt with, nor the upper level engineers that I've corresponded with through Apple Care - their problem solving skills were helpful - although I could have arrived at similar conclusions given enough $$$. (For instance, try a Lacie TB drive and see if that works - we did, and it did not work. Or, we have a different TB cable and a different TB adapter, let's try those - we did, and it did not work.) I blame myself for not doing enough homework before going with Apple's solutions.

Moving Time Machine Drive from Direct Connect to Network Share

Similar Messages

Maybe you are looking for