Issues with Time Machine File Restore Permissions and Interface

Hi All,I bought a Time Capsule in January 2010, and i've had backups since then.
Time Machine's interface has pretty much always been laggy as ****, but I've always put that down to using it over wifi, perhaps that was a wrong assumption.
Anyway, I went to open a folder in a virtual machine which resides in my mac's documents folder, and it wasn't there. Sure enough this folder wasn't in my documents folder, so I thought i'd restore it from time machine. Time machine shows every segment as a pink fully coloured one (signalling theres a backup there) for a few secs, before most of them turn into a pale pink. Looking into the issue further, it seems as though I don't have permission to access the documents folder on a lot of backups, by looking at the users/brett/ folders on them (which i do have access to), right clicking on the restricted folder shows that everyone has no access, and it's fetching the other user. Trying to add myself to it doesn't work.
I have gone through two MBPs with the same backup set, and a number of hard drives (the latest being a SSD I put in yesterday, and the migration assistant restore from time machine worked without skipping a beat - never had a problem doing full restores or migrations, just using the interface)
Obviously the easiest thing to do would be to start afresh, but I'd rather not as I'd lose 2 years worth of backups, and who's to say this wouldn't just happen again in the future? Could this be why the interface is so slow too?
Thanks guys

studentguy wrote:
Time Machine's interface has pretty much always been laggy as ****, but I've always put that down to using it over wifi, perhaps that was a wrong assumption.
Yes, there is a lot going on to "populate" the display -- it can be sluggish even to a FireWire 800 drive.
Looking into the issue further, it seems as though I don't have permission to access the documents folder on a lot of backups, by looking at the users/brett/ folders on them (which i do have access to), right clicking on the restricted folder shows that everyone has no access, and it's fetching the other user. Trying to add myself to it doesn't work.
I don't do Windoze, so am not familiar with the structure of the VM files, or how the permissions on them work. Many folks exclude them from Time Machine, and back them up separately.
I have gone through two MBPs with the same backup set, and a number of hard drives (the latest being a SSD I put in yesterday, and the migration assistant restore from time machine worked without skipping a beat
Yes, because it simply copies whatever permissions are there. It doesn't need to (and shouldn't) check whether the logged-on user has permission to anything.
Could this be why the interface is so slow too?
It could be a contributor.
Can you set the permissions on the VM files on your Mac so everyone has read rights? That should at least allow you to restore their backups.

Similar Messages

Clean Install around Boot Camp partition with time machine file restore

Currently at 10.5.8 on MacBook with a bootcamp partition. I am wondering if I can:
Make a timemachine backup
Wipe the mac partition, leave bootcamp partition alone
Install clean 10.6 OS
Use Time Machine to restore non-OS docs, apps, and other files
Just asking...

Yes, you can. Perform the erase and install normally and then either use Time Machine or the Migration Assistant to restore the backup.
(46800)

I try to backup my Macbook with Time machine, it goes fine and at the end it says that it could not be completed because "/Volumes/Data-2/ MacBook.sparsebundle is already in use".. What is that?!

I try to backup my Macbook with Time machine, it goes fine and at the end it says that it could not be completed because "/Volumes/Data-2/ MacBook.sparsebundle is already in use".. What is that?!

See #C12 in Time Machine - Troubleshooting

Recently upgraded to a Canon Mark 3 and now having issues with my RAW files in Bridge and Photoshop. I am operating with CS4. Photoshop produces an error " Could not complete your request because photoshop does not recognize this type of file"

Recently upgraded to a Canon Mark 3 and now having issues with my RAW files in Bridge and Photoshop. I have operating with CS4. Photoshop produces and error " Could not complete your request because photoshop does not recognize this type of file"

Assuming you mean 5D Mark III, Photoshop CS4 cannot directly open raw files from your camera.
Generally speaking, Adobe stopped updating older versions to be able to read raw files from newer cameras when they released a new major version of Photoshop. Photoshop CS4 is no longer receiving Camera Raw updates.
You can double check this yourself:
First you need to determine whether Adobe has released support for your new camera in your version of Photoshop. To do that, look at these two pages. You'll want to find out the earliest version of Camera Raw that can support your camera, then what version of Photoshop can run that version of Camera Raw.
Camera Raw plug-in | Supported cameras
Camera Raw-compatible Adobe applications
If you find your camera is supported by your version of Photoshop, you need to download the latest update for Camera Raw. There's more information on how to do that here:
Keeping Photoshop Up-To-Date
If your version of Photoshop cannot support your camera, you can download and install the latest version of the free Adobe DNG Converter, which can take your raw files as input and put out DNG format files, which your version of Photoshop can open.
Photoshop Help | Digital Negative (DNG)
The DNG converter DOES work, but if you want maximal quality from your raw files (not to mention the convenience and ease of use of directly opening your raw files) you'll want the latest version of Photoshop. Adobe has made substantial improvements in raw conversion quality in recent years.
-Noel

Macbook won't recognize external Hard Drive and issues with Time Machine

Hello everyone,
I have just bought a new Macbook Pro with Mountain Lion and I am currently having problems with Time Machine.
The issue begun in Snow Leopard: Time Machine was taking too long to backup, and would often not finish the backup because the external hard drive would be unwillingly ejected.
Now with Mountain Lion I have reformated the drive (Mac OS Journaled) and about a third of the way through had the same issue: the drive was ejected before the backup could be finished. I restarted the machine and it happened again. However, now the computer won't even recognize the external drive when I plug it in. I have also tried to power off/on the drive itself to no progress.
I have tested the USB port with another drive and the port is fine. I have also tested the usb cable and it is fine. And Disk Utility does not recognize the drive (even when I try the >diskutil list command in terminal).
Now, I can hear the drive humming normally when I turn it on, and it is not usb-powered (my electricity current does fluctuate).
Could the interrupted backup procedures have damaged the drive? And if so, wouldn't the computer recognize it anyway?
It is a 4 year old WD 1 TB that is used exclusively for TM and has never left the house.
Thank you for your time reading this and let me know if you need any more information that could help out.
Cheers!

From your description, I'd suspect a failing drive. Maybe time for a new external, especially as you've already re-formatted and it's still playing up.
I had a similar problem with one of my clone backups a few weeks ago - it failed, I erased it, re-cloned, worked a couple of times and then it failed again. Disk Utility didn't throw up any errors after re-formatting. I guess all disks die at some point.

Issue with Time Machine and WD Elements external drive

I am experiencing continuous problems with Time Machine set to back up to a WD Elements 1TByte external disk; appears to backup files perfectly but I'm plagued by recurring message 'The disk was not ejected properly...'. Dealer assures me that the disk is fine. No problem if Time Machine is disabled. But then I have no back up...

christopherfromadelaide wrote:
In fact, when I turn off Time Machine, I still get the ... message, which flashes up every 30 secs or so, and only goes away when I unplug the external drive.
That indicates that the problem may not involve Time Machine at all.
To be sure everything else is ok, verify your internal HD and repair the WD drive, per #A5 in Time Machine - Troubleshooting
If the problems persist, try different port(s), cables, and combinations of the two (a plug that works fine in one port may only make marginal/intermittent contact in another). Also make sure the WD's power cable is snug and secure, and it's plugged-in to a good power source.

Errors with Time Machine (not completing backup, and needing to erase the ".inProgress" package)

I have in a previous discussion been talking about errors with my Time Machine backup. The errors were with a problem with Indexing a file, it fails and stops the whole backup. Each time it attemps another backup, it fills my ".inProgress" package with a (nearly) whole backup, filling my Time Machine hard drive, and thus errasing my previous good backups. The error occurs after about 95% completion.
In my last post of a similar disscussion, the problem was indexing the Preference Pane files and this caused the whole backup to fail. This was my last post there: (below in some additional info of my situation)
I did exclude the MobileMe.prefPane. And I got:
12/16/11 9:24:50.468 PM com.apple.backupd: Starting standard backup
12/16/11 9:24:50.556 PM com.apple.backupd: Backing up to: /Volumes/3 TB GoFlex Drive/Backups.backupdb
12/16/11 9:25:14.418 PM com.apple.backupd: Waiting for index to be ready (101)
12/16/11 9:27:02.366 PM com.apple.backupd: Deep event scan at path:/ reason:must scan subdirs|
12/16/11 9:27:02.366 PM com.apple.backupd: Finished scan
12/16/11 9:33:37.119 PM com.apple.backupd: Deep event scan at path:/Volumes/Mac OS Lion GM reason:must scan subdirs|
12/16/11 9:33:37.119 PM com.apple.backupd: Finished scan
12/16/11 9:36:15.650 PM com.apple.backupd: 758.92 GB required (including padding), 830.32 GB available
12/16/11 10:25:14.873 PM com.apple.backupd: Copied 22.8 GB of 630.5 GB, 782749 of 2357620 items
12/16/11 11:25:15.335 PM com.apple.backupd: Copied 86.6 GB of 630.5 GB, 1167675 of 2357620 items
12/17/11 12:25:16.227 AM com.apple.backupd: Copied 152.2 GB of 630.5 GB, 1393795 of 2357620 items
Dec 17 01:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 305.2 GB of 630.5 GB, 1413946 of 2357620 items
Dec 17 02:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 457.1 GB of 630.5 GB, 1419190 of 2357620 items
Dec 17 03:19:07 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 1736865 files (568.3 GB) from volume Macintosh HD.
Dec 17 03:25:16 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 572.1 GB of 630.5 GB, 1848939 of 2357620 items
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Indexing a file failed. Returned 200 for: /Volumes/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane, /Volumes/3 TB GoFlex Drive/Backups.backupdb/Tom iMac/2011-12-14-171406.inProgress/7DB524DD-EFB9-42A6-8A21-0A2A312EDA6D/Mac OS Lion GM/System/Library/PreferencePanes/Mouse.prefPane
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Aborting backup because indexing a file failed.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Stopping backup.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copied 2164998 files (581.1 GB) from volume Mac OS Lion GM.
Dec 17 03:40:33 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Copy stage failed with error:11
Dec 17 03:40:50 Thomas-P-Kellys-iMac com.apple.backupd[99858]: Backup failed with error: 11
This time it was the Mouse.prefPane that caused the error. I'd like to exclude the entire PreferencePanes directory.
This was my error message this time:
I just realized this was on my small Developers partition. Perhaps there is an error with the build, OR an error with the initial restore. I'd like to perhaps exclude the entire /Volumes/Mac OS Lion GM. I expect that Time Machine is working fine with my main partition and the error happens when it's almost done with the Mac OS Lion GM partition.
The problem now is that I only have 265 GB of 3 TB available on my Time Machine HDD. If attempt another backup, it'll surely erase about 410 GB of my past saved backups. I've already lost 6 months, and I only have two months left of backups. I need to erase the ".inProgress" package again. That'll take time, and it's impossible to do from this main partition, even at root access. This ".inProgress" has a total of two (nearly) full backups; it didn't cleanup the first full backup attempt while starting the second,perhaps it would have had it finished. But I fear even if I exclude the whole "Mac OS Lion GM" partition, It'll create a third full backup before cleanup and erase ~400 GB of previous good backups. Then, I'll have a total of 4 (nearly) full backups! 3 TB is just enough without any past backups.
Maybe I'll just copy my documentations of my 'errasing the ".inProgress" package' last time (from the Mac OS Lion GM partition) and do a full restore of just that partition. Thus erasing the errors all together. If it doesn't fix the errors then this could be a bug in the build that doesn't allow Time Machine to work. I've always included this partition in Time Machine before, even with other Lion builds, so I suspect that it was an error in the initial restore. (I may be answering my own questions, and that the inital restore (of the small partition) is the problem, and I just need to re-restore the small partition)
Again, I'm going to have to erase the ".inProgress" file to regain 1.53 TB of space before proceeding.
Also, I gave myself permission to read the ".Backup.345781513.887697.log", the log that was created last night when I first started Time Machine this last time. It was interesting, but didn't show the error I could see from the console.
Right now, mds and mdworker appear to be going crazy even after I just now turned off Time Machine. I think I'll let it go for the rest of the night. Then I'll work on erasing the ".inProgress" package from the other partition boot up.
That was my entire last post. To add some information, I have two OS X partitons, both Mac OS X Lion. One is my large main partition, the other is one I don't mind testing with. I recently replaced my internal hard drive in my iMac and restored from Time Machine both partitions. This appeared to go smoothly. But I have yet to create a single successful Time Machine backup since. At first it was doing a Full Backup, which I didn't like, but now it just aborts around 95% completion. Each, time, it tries it fills the Time Machine hard drive with duplicate (nearly) full backups errasing my older good backups. I would like to erase the ".inProgress" file to save space.
My main question in this new discussion is does anyone know of a good way of erasing the ".inProgress" file? This is so I can preseerve my previous backups. ACLs and other permissions seem to make it impossible to erase from this startup partition, the one I'm running Time Machine from. Even at root level, if I give myself permission to change permissions or delete a file, it'll say Operation not Permitted instead of Permission Denied. I have been able to delete this ".inProgress" package before when booting from the other partition, but with great difficulty. I have had much help from another Member in this Support Community when it comes to solving my Time Machine problems. I think I have found the problem (indexing files in my small OS X partition), as stated in my copy& pasted post above, but I really need to delete this inProgress package first to save space before continuing!

Pondini wrote:
Gator TPK wrote:
Now I'll have to fix the small partition? How's the best way to do this? There could be thousands of files that won't index fine.
See if there's anything you haven't done, that applies, in the pink box of #C3 in Time Machine - Troubleshooting
Otherwise, since most (or all?) of the indexing errors are in OSX, you might want to just reinstall it. Something may have gone wrong sometime, that damaged those files.
I reviewed #C3 in Time Machine - Troubleshooting and I have already done most of those things. I have just learned something new though:
When I included my Main OS X partition again, I got an indexing error for the first time for that partition. I might be interesting to note that the _spotlight process was running, and it's running again (the magnifying glass has a dot and it generically says "Indexing Tom's iMac"). mdworker, mds and backupd processes really are working hard, one moment they used over 500% of my CPU. It's nice to know for once quad core is good for something other than video encoding. (Now if they could just get the Finder to do more than 100.1%, only 1 thread is doing 100%, I'd like to see file size calculations 8 times quicker!)
I never got an indexing error once in the past 2 weeks for that large Mac OS X v10.7.2 main volume, and it had appeared to finish that partition backup before running into problems with my smaller test partition. Also, I had just updated the smaller test partition with a later build of Mac OS X. But It appears that the beta builds are clearly not the problem. I thought I could just restore again (from the December 4th backup) the small partition and both would be fine.
I'll finish reviewing all the suggestions on Time Machine - Troubleshooting and go from there. Hopefully, the _spotlight indexing simutaniously was the only problem. It's strange that the indexing hasn't happened since the original restore last week untill I finally got a good clean complete partial Time Machine backup. Why would the first Time Machine backup trigger indexing again?
For now, I'm going to exclude the Main Partition again, and let another good backup run. And try your suggestions. (And wait till mds, mdworker, etc. to finish!)
I have the logs of the first two sucsessful backups and the last two failed backups from the last 3 hours, if that would help.?

Mountain Lion Server App - Issue with Time Machine Volume Selection

Besides my gripes that 10.7 Server or the 10.8 Server app are radically dumbed down versions of what 10.6 Server was capable of, the upgrade to 10.8 from 10.7 unexpectably broke my home time machine backup.
Am quite familiar with the prior server versions as we are still using 10.6 Server on a dozen or so Xserve's, plugging along nicely
This is for our house setup using a Mac Mini with an attached 8TB RAID managing media serving and time machine backups. For simplicity, the array is partitioned as a single volume and simply configuring a file sharing sharepoint as a Time Machine Volume. Simple and easy!
When upgrading to 10.8 and then installing the server app, the upgrade conveniently didn't migrate any file sharing settings, forcing me to set them up again. Easy enough, just took a couple of minutes, except that the share point I used for time machine backups has no more setting to turn it into a Time Machine volume.
As such, under the Time Machine tab, which shows only logical volumes, I simply can't back up to our existing backups.
I suppose I can re-partition the array to create a logical volume for TM backups, but I can't believe that there is no provision to change a sharepoint into a TM volume anymore.
Am trying to stay away from CLI settings as well as that defeats the purpose of the app.
Any thoughts or suggestions?
Wolfman

I have asked the hosts to move your post to the OS X Server forum.

I have an issue with time machine, it doesn't find the Lacie external driver it use to use. it is the same drive that I usaly use for time machine back ups. It is corectly plugged. What can I do ?

Hi,
I'm trying to back up my macbook with time machine on the Lacie external driver I usualy use for this, but today my computer doesn't find the driver. I haven't done back up in 6 month.
Today, the Lacie driver is pluged and running, but the computer just does'nt find it.
what shall I do ?

Some things to consider:
Is the drive mounted, i.e., visible via Finder and/or on the Desktop?
Is the drive still selected in System Preferences, Time Machine? If not, use the "Select Disk" button.
Is Time Machine still turned on (System Preferences, Time Machine)?
Can you see the drive (and mount it) using Disk Utility (in your Utilities folder)?
charlie

Permissions issue with Time Machine backup store

I am struggling with a Time Machine permissions issue on an iMac running OS X 10.10.2 + OS X Server 4.0.3, and backing itself up to an external USB disk.
Backups complete successfully, but I am unable to carry out any user-level operations such as accessing the "time travel" interface via Enter Time Machine from the menu bar. Invoking Enter Time Machine fails with the error Can't connect to a current Time Machine backup disk. Likewise, although tmutil will correctly list the backup destination, tmutil listbackups produces an error:
$ tmutil listbackups
2015-02-05 16:53:19.413 tmutil[29181:2324148] Error enumerating (null): The file “Backups.backupdb” couldn’t be opened because you don’t have permission to view it.
No machine directory found for host.
My system logs are full of similar error messages from Finder.
On the back volume, the permisisons to the store are set to owner root and group wheel, and there is an access control list applied to the directory and Backups.backupdb:
$ ls -lae
total 2688
drwxrwxr-x 12 root wheel      476 Feb 4 22:29 .
drwxrwxrwt@ 9 root admin      306 Feb 4 11:57 ..
0: group:everyone deny add_file,add_subdirectory,directory_inherit,only_inherit
drwxrwx---+ 6 root wheel      204 Jan 30 13:49 Backups.backupdb
0: group:everyone deny add_file,delete,add_subdirectory,delete_child,writeattr,writeextattr,chown
-rwxr-xr-x@ 1 root wheel   115716 Nov 13 02:43 tmbootpicker.ef
The problem is clearly the drwxrwx--- permissions applied to the store. I can temporarily revert these with chmod, after which all the user-level operations described above work correctly. But on the next backup, backupd will revert the permissions to give wheel write access and remove rx privileges for everyone else. It doesn't leave anything in the system log to suggest why it is making this change.
I have a MacBook also running OS X 10.10.2, without the Server pack. This also backs up to a (different) external volume. On this volume the owner, group and access control list for the store are set as above, but the permissions are (and remain) what I would have expected, drwxr-xr-x.
Is there any obvious reason why backupd should be modifying the permissions in this way — and is there any way to stop it?

Thanks - I was seeing exact same problem on one of my client's machines (10.10.2 with OS X Server). I could see wrong group of "wheel" but wasn't certain that just changing to "staff" would be enough - but seems to have sorted things out

Time machine file restore fails "you don't have permissions to access.."

Frequently I work my macbook (10.7.3) in the terminal as root. I seems like files that owned by root are not eligable for restore via time machine by the system administrator. Is there a way to operate time machine as root? Or is there a way to grant root rights to the user account designated as administrator?
Specifically, the time machine copy dialog reports "The operation can't be completed because you don't have permission to access [filename]. For example, in one case case, it is .gitignore.

In post https://discussions.apple.com/message/9945786#9945786 Scott T. states that "time machine always runs as root.", I take that to mean that time machine will have rights to copy all files, regardless of the owner.
That's great. So I can restate the question: how do I restore a file that is owned by root?

HT3275 I encrypted my WD elements SE external hard drive with Time Machine and now everytime i enter my password it shuts downs my mac book pro. I contacted WD and they say its an issue with Time Machine?

Any advice?

Hi, I tried your advice and it tells me the external drive is ok, and the ERASE section is grey, probably because I encrypted the disk!?!
Still the same issue: every time I enter my password to access the external hard drive, it restarts the macbook and I get a screen that says: the computer restarted because of a problem... so frustrating!
Any other ideas?

Yosemite time machine file restore problem

I'm trying to restore some files (iPhone backups) in OS X Yosemite, but am encountering a problem.
I can locate the files I need in Time Machine. When I hit restore the 'Star Wars' UI exits as I would expect, and the 'preparing to copy files' dialogue box appears.
At this point, it goes no further. I also get the following message in the console:
15/11/2014 6:00:30.406 am Finder[236]: setting error: Error Domain=NSCocoaErrorDomain Code=3840 "The data couldn’t be read because it isn’t in the correct format." (Unexpected character at line 1) UserInfo=0x60800067d7c0 {NSDebugDescription=Unexpected character at line 1, kCFPropertyListOldStyleParsingError=The data couldn’t be read because it isn’t in the correct format.}
Any advice on how to address this will be greatly appreciated. I'm currently verifying the backup in Time Machine, but other than that I'm out of ideas.

Jimbo, have you looked in the system’s Trash? Just see if it needs to be emptied to free up space. As Eric mentioned, I’ve only done a complete restore by wiping the disk, reinstalling the OS, etc. so I’m just guessing in your situation something is still lying around.
You could also look in Spotlight for a folder (whose full name I can’t recall now) that begins with the name “Previous System” or something like that in your boot drive; it is created to archive your previous system in case you want to revery to an earlier version. If your system is fine now, it is safe to delete that folder - just remember to empty the Trash.

Issues with time machine software to view tm backups

this is both a question and comment on this issue.
I started to noticed that on entering 'time machine' on my imac all the 'backed up' folder screens that are stacked up behind each other had a black screen instead of the 'finder desktop window'. Worse still this problem was intermittant - sometimes I could view backed up data.
I use a late 2013 IMAC (latest update of OSX) connected wirelessly to a 6 month old 2gb time capsule (TC).
I spoke to Apple (April 2014) and they are unaware of any similar problems
The guy who was trying to help suggested it was a wireless interference problem and I agreed to try a number of things before just deleting the backup and starting all over again (not for the first time). I note that 6 months ago I replaced a WD NAS as I was having repeated problems using it with TM.
Digging around a little more what seems clear to me is that the issue maybe with how TM communicates with the TC, rather than any wireless interference.
If I open finder and select TC > data > 'computer name' sparse bundle.
Clicking on the sparse bundle file loads the 'time machine' server in the DEVICES list.
From there you will see all the backups taken since day1 - date/time folder name.
Selecting one of these reveals the actual folders from your computer that were backed up and clicking through the folders you can open any file that was backed up.
The point is here; using finder over the same wireless network I can view any file that TM has backed up to the TC, however at the same time (having ejected the time machine device) I am unable to view the same files through the TM software as the stacked windows are all black.
I have to assume that TM is using a different method to access the TC commpared to finder, otherwise I would have the same issues in finder.

this is both a question and comment on this issue.
I started to noticed that on entering 'time machine' on my imac all the 'backed up' folder screens that are stacked up behind each other had a black screen instead of the 'finder desktop window'. Worse still this problem was intermittant - sometimes I could view backed up data.
I use a late 2013 IMAC (latest update of OSX) connected wirelessly to a 6 month old 2gb time capsule (TC).
I spoke to Apple (April 2014) and they are unaware of any similar problems
The guy who was trying to help suggested it was a wireless interference problem and I agreed to try a number of things before just deleting the backup and starting all over again (not for the first time). I note that 6 months ago I replaced a WD NAS as I was having repeated problems using it with TM.
Digging around a little more what seems clear to me is that the issue maybe with how TM communicates with the TC, rather than any wireless interference.
If I open finder and select TC > data > 'computer name' sparse bundle.
Clicking on the sparse bundle file loads the 'time machine' server in the DEVICES list.
From there you will see all the backups taken since day1 - date/time folder name.
Selecting one of these reveals the actual folders from your computer that were backed up and clicking through the folders you can open any file that was backed up.
The point is here; using finder over the same wireless network I can view any file that TM has backed up to the TC, however at the same time (having ejected the time machine device) I am unable to view the same files through the TM software as the stacked windows are all black.
I have to assume that TM is using a different method to access the TC commpared to finder, otherwise I would have the same issues in finder.

Anyone got Issue with Time Machine on Mac OS 10.9.5 on External Hard Drive?

Mac Book Air June 2012, Mac OS 10.9.5 (fully updated) external Hard Drive, USB 3
Dear all,
Just realized that my regular Time Machine back-ups don’t work anymore: despite several back-ups, Time Machine tells me that I did not back-up for 10 days but I did not get any error message.
Suspected an issue with my external Hard Drive, so took a brand new one 1TB, labelled Mac OS, USB 3, sold at Apple Corner.
Registered this new drive in Time Machine, started a full back-up of about 350 Gb, and it is hanging up, 13Kb copied in one hour.....
This become very critical as I don’t have back-up since a few days....
Your help will be upmost appreciated.
Best regards to all,
Bernard

Temporarily turn Time Machine "off". Make sure a backup is not in progress, then rebuild the Spotlight database according to the following instructions: Spotlight: How to re-index folders or volumes
(summary: drag the entire source volume to the exclusions list, click OK, then remove it by clicking the minus ("–") button.)
This will have no effect on any existing backups.
Let Spotlight finish reindexing and then turn Time Machine back "on". Select "Back Up Now".

Issues with Time Machine File Restore Permissions and Interface

Similar Messages

Maybe you are looking for