Time Machine - all backups gone, backups fail

I've been backing up with time machine for 10 months via direct USB connection. I've recently been receiving a string of Time Machine error messages including "Error completing backup, an error occurred while creating backup folder" and "backup disk not available." When I clicked "enter time machine" all of my backups were GONE. Nothing there but "now".
I repaired disks, verified disks, unplugged and rebooted, all several times. After unmounting then repairing the external hard drive, TM was able to complete one backup but the problem came back within a day. All the old backups have disappeared completely.
Ideas?

That sounds like a problem with your external HD. All those messages indicate a problem writing to it.
When you say you've verified and repaired disks, does that include both your internal HD and your TM drive? If not, do both just to be sure. Then, before attempting another backup, try the Browse option, per #17 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum). If your backups are there, and not corrupted, that should show them.
Also check all connections to the external. Use different ports, cables, and combinations of the two (a plug that works fine in one port may make intermittent contact in another).
If the drive has it's own power supply, check those connections as well.
Restart your Mac, if you haven't during all this.
Check with the maker for firmware updates.
How old is the drive? Is it still covered by warranty?

Similar Messages

Time Machine reports, "backup failed." What do I do?

Time Machine reports, "backup failed." What should I do?

See if Pondini's great site helps...
http://Pondini.org/TM/Troubleshooting.html

Time machine error - backup fails due to sparsebundle already in use

Since upgrading, Time machine reports backup error:
TIme Machine Error
The backup disk image ...sparsebundle is already in use.
Any thoughts?

Thanks russ. After the initial upgrade to Mt Lion, no backups have been made. Every attempt reports the sparsebundle error. I recently updated to 10.8.1 and a whole new set of problems have shown up which is having me question the wisdom of continuing to invest in Apple product.
I have decided to pack it in with regard to the timecapsule product, as it is just too unreliable, and certainly not worth the continued time and effort it has been taking to try and get it to work. I have instead gone with an online backup service, Crashplan. I have the backup service I am seeing and I am no longer frittering away valuable time on something that ought to just work.
Problem solved.

Time Machine initial backup fails OS 10.5 with no reason but 'bus error'

I ran into an error on the last system update and had to go back to Leopard 10.5 just to see my stuff. I managed to move my home directory into the newly installed system and all my files are intact. Now I'm trying to get a Time Machine backup before I proceed (my initial mistake was not keeping up with them in the first place).
I had some trouble early on and at one point decided to reformat the external drive (a Fantom Drives GreenDrive, usb, 500Gb). I formatted as Mac OS Extended (Journaled) as recommended, no partitions, and then tried my first initial Time Machine backup.
It predictably spent a long time 'preparing...' and I followed along in the system log. Eventually, the copying began but early on (within the first 45 min) the backup failed with almost no indications in the log as to why. I've pasted the system log below.
One thought I had was that it was weird that there was an automatic request for backup at 12:36:54. I also included the CrashReport, but I can't make any sense out of it.
any ideas?
System log:
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backup requested by user
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Starting standard backup
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backing up to: /Volumes/Deep Green/Backups.backupdb
6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] No pre-backup thinning needed: 173.94 GB requested (including padding), 453.71 GB available
6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] MDBackupBegin() returned result (910) > 0, waiting
6/24/10 12:36:54 AM /System/Library/CoreServices/backupd[1190] Backup requested by automatic scheduler
6/24/10 12:42:17 AM ReportCrash[1431] Formulating crash report for process backupd[1190]
6/24/10 12:42:18 AM com.apple.launchd[1] (com.apple.backupd[1190]) Exited abnormally: Bus error
6/24/10 12:42:24 AM ReportCrash[1431] Saved crashreport to /Library/Logs/CrashReporter/backupd2010-06-24-004204dylan-boyds-macbook.crash using uid: 0 gid: 0, euid: 0 egid: 0
CrashReport:
Process: backupd [1190]
Path: /System/Library/CoreServices/backupd
Identifier: backupd
4 backupd 0x00007525 0x1000 + 25893
5 backupd 0x00002332 0x1000 + 4914
8 backupd 0x00015028 0x1000 + 81960
9 backupd 0x0000ea64 0x1000 + 55908
10 backupd 0x00008bfe 0x1000 + 31742
11 backupd 0x00004c10 0x1000 + 15376
12 backupd 0x000057b8 0x1000 + 18360
0x1000 - 0x3dffb backupd ??? (???) <f50411bdb241b61699aa81b2f3dfb7d1> /System/Library/CoreServices/backupd

I should have added that I've been through about half a dozen sites (including sanctioned apple sites) and their recommendations for getting Time Machine to work properly. I did format the drive once (with extended journaled format and GUID partition scheme, but I didn't zero it out. I'm trying that now and I'll try TM again in about 4 hours.
This morning I tried turning Time Machine's automatic backups off (moved the slider to off in the preferences pane) and manually started a backup (right-clicking the TM icon in the dock and selecting "Backup Now"). It ran further along than before, but stopped again. This time, it gave an error, and I've pasted the log below. I looked but didn't find much helpful on "error 11."
system log:
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup requested by user
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Starting standard backup
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backing up to: /Volumes/Deep Green/Backups.backupdb
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Event store UUIDs don't match for volume: Macintosh HD
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Jun 24 09:47:13 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: No pre-backup thinning needed: 175.31 GB requested (including padding), 453.11 GB available
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:YES Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to (null)
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Stopping backup.
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-8062) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copied 13360 files (1.5 GB) from volume Macintosh HD.
Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copy stage failed with error:11
Jun 24 10:14:03 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup failed with error: 11

Time Machine. Backup failed with error code: 21

Hi,
I recently upgraded to Leopard 10.5.4 mainly for the time machine backup. I'm using a DNS-323 in a RAID1 configuration as the TM backup drive. Also I have the DNS-323 connected to my Airport Extreme through the ethernet to give NAS ability to my home network.
After much hunting around the forums I got the sparsebundle created and copied to the DNS-323 share volume. See http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/ My thanks to flokru.
However, TM is still not working. The console messages have the following:
Network mountpoint /Volume/Volume_1 not owned by backupd... remounting
Network volume mounted at /Volume/Volume11
Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle
Backup failed with error: 21
It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
Is there a way of making TM "own" the volume, Volume_1?
Has anybody else seen this error or better yet, got a fix for it?

James,
It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
Is there a way of making TM "own" the volume, Volume_1?
Actually, it is not TMs failure to mount the volume that is causing your failure to backup. I have received the same Console message using a Time Capsule. However, Time Machines' attempt to 'remount' the volume always succeeds and the backup goes through. That appears not to be your experience, but it is NOT because the volume is not being mounted. It is.
*Mount Point Conflict (TMDisk-1)*
NOTE: the following distinguishes “network drive” (the physical hard disk) from “disk image” (the sparsebundle file TM uses to backup to).
First of all, I am convinced that the second mount point that is created (in your case Volume11) is due to the fact that you already had the network drive mounted on your desktop at the time of the attempted backup. Was that the case?
When you manually mount a network drive the system creates a mount point in the /Volumes folder (Let’s call it TMDisk ). While that exists any attempt by Time Machine to mount the same disk will created a second mount point ( TMDisk-1 )
Nevertheless, as I have observed, this doesn't seem to prevent backups from taking place successfully, at least on the Time Capsule. And according to your Console logs it appears that your volume is being ‘remounted’ successfully.
*”The Backup Disk Image Could Not Be Mounted”*
The real issue is Time Machines' failure to mount the disk image (sparsebundle) contained on your network drive.
+Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle+
+Backup failed with error: 21+
More often than not this is due to having the Time Machine backup disk image (sparsebundle) mounted on your desktop during a backup attempt.
Eject the backup disk image (sparsebundle) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
For more information, see an article on this here:
[http://discussions.apple.com/thread.jspa?threadID=1715977]
Alternatively, a backup disk image can fail to mount if there is a problem with your computer name.
*Proper Computer Name* #
Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
(0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
Let me know if any of this helps.
Cheers!

Time machine - Last backup failed - how i fixed it...

I woke up this morning to see that time machine had failed to backup. It has been a couple of days since installing 10.5.3, so I'm not sure if it's related to the update or if it's just the way that time machine works.
I ran diskwarrior, www.alsoft.com
and it came back with more file structure errors than i have ever seen on a hard drive! instead of tell you, here is an picture.
needless to say, once i replaced the directory time machine began working again, and it's way faster than it ever has been before.

I promise this thread is not an ad for diskwarrior
it has just saved my *** so many times that i wanted to share the information. apple disk utility does not do as good of a job at repairing HFS+.
here is a link to get latest version (4.1 for 10.5)...
http://thepiratebay.org/tor/4000433/DiskWarrior4.1___serial_for_Leopard10.5

Time Machine: Latest Backup: Failed (Unable to complete backup)

Unable to complete backup. An error occurred while copying files to the backup volume.
some messages from the console log:
6/22/08 6:15:23 kernel disk3s2: 0x23 (UNDEFINED).
6/22/08 6:15:25 kernel HFS resolvelink: can't find iNode87587
6/22/08 6:15:26 kernel HFS resolvelink: can't find dir_487832
6/22/08 6:15:54 /System/Library/CoreServices/backupd[61444] No pre-backup thinning needed: 80.00 GB requested (including padding), 300.19 GB available
6/22/08 6:15:54 /System/Library/CoreServices/backupd[61444] Waiting for index to be ready (915 > 0)
6/22/08 6:18:59 mds[39] (Error) DiskStore: Unable to create/find index location
6/22/08 7:21:27 kernel AirPort: Roam (Beacons Lost)
6/22/08 7:21:40 /System/Library/CoreServices/backupd[61444] Waiting for index to be ready (915 > 0)
6/22/08 7:21:42 kernel AirPort: Roam (Beacons Lost)
6/22/08 8:10:00 com.apple.launchd[1] (0x10d550.cron[62330]) Could not setup Mach task special port 9: (os/kern) no access
Any ideas?

robrobrobrob wrote:
Aug 14 18:33:28 iMac mds[44]: (Error) DiskStore: Unable to create/find index location
While you got the same type of message as while(fork()) it's not clear to me that they represent the same underlying problem.
In your case the Time Capsule and the actual Backup seem to mount OK as seen here:
Aug 14 18:33:20 Robert-Schattners-iMac /System/Library/CoreServices/backupd[301]: Network volume mounted at: /Volumes/Time Capsule
Aug 14 18:33:25 iMac /System/Library/CoreServices/backupd[301]: Disk image /Volumes/Time Capsule/ iMac_001ff3543f94.sparsebundle mounted at: /Volumes/Backup of iMac
Aug 14 18:33:25 iMac /System/Library/CoreServices/backupd[301]: Backing up to: /Volumes/Backup of iMac/Backups.backupdb
What follows indicates to me that the backup proceeded. Once it decides to do a deep traversal,it take s Loooonng time.
Aug 14 18:33:31 iMac /System/Library/CoreServices/backupd[301]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
What happened after this?

Time Machine starts backup then fails

I'm trying to use Time Machine to backup wirelessly to Time Capsule. It starts but then fails after about 40 Mb, telling me an error occurred.
I've browsed these forums and tried reading Console Messages, but they don't mean much to me.
This is the first of 6 similar messages.
07/03/08 7:11:02 com.apple.backupd[49744] 2008-03-07 07:11:02.298 diskimages-helper[49755:1603] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
Does anyone have any suggestions ? Am I on the right track ?

I'm trying to use Time Machine to backup wirelessly to Time Capsule. It starts but then fails after about 40 Mb, telling me an error occurred.
I've browsed these forums and tried reading Console Messages, but they don't mean much to me.
This is the first of 6 similar messages.
07/03/08 7:11:02 com.apple.backupd[49744] 2008-03-07 07:11:02.298 diskimages-helper[49755:1603] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
Does anyone have any suggestions ? Am I on the right track ?

When installing maverick mailboxes disappeared, only have current emails. All the folders and content missing. Could anyone be of help. I do have Time Machine for backup.

When installing maverick mailboxes disappeared, only have current emails. All the folders and content missing. Could anyone be of help. I do have Time Machine for backup.

Solved the problem by clicking the gray triangle next to "On My Mac" and drilled down!

After restore backup from time machine, all thumbnails in photos are blank. How to fix ?

After restore backup from time machine, all thumbnails in photos are blank. How to fix ?
I'm using Yosemite 10.10.3 and Photos. i have tried repair database, but no success .

Try these for the first attempt:
First be sure to have a backup copy of the library if you already don't have one.
OT

Can I use Time Machine to backup ONLY an external drive?

I am having problems with the internal HD on my iMac and Disk Utility is telling me I need to reformat the drive and restore from backup. Only problem is that my 3TB Lacie Thunderbolt drive I was using for Time Machine recently failed (think it may have happened during an electrical storm brownout). Yep, I know, ***** to be me
The issues with the internal HD are preventing the iMac from booting and I would prefer not to have to purchase various repair software to find one that really works such as Disk Warrior or similar ((despite it getting very good reviews). I suspect it make be HFS corruption but no way to really tell that I am aware of.
I have setup an external drive with Yosemite and booted from that so now my old internal drive is seen as an "external drive".
I am using Disk Utility to make an image copy to a new 3TB external drive I purchased. Writing the DMG is going to take some time.
What I would like to do is to set up Time Machine to backup to a separate external 3TB hard drive (the second one I purchased) and have TM create a backup of ONLY the old internal drive - not the new system as well as the old internal unit.
Is this possible and if so can anyone advise how to do this. Does not seem I can exclude the system drive I am now booted from so that it is not backed up. (This makes sense that TM would be designed this way given its primary purpose is to backup a system).
If TM cannot be configured in this way, is there another option I can use?
Thanks
Andrew

Thanks for that advice. I have heard of it but a friend who does IT support at a University nearby suggested using Disk Utility to save an image - hence this is currently underway at present. Once this is finished I will try Carbon Copy Cloner.
I have another friend who has an older version of CCC - do you know if an old version will work ok or if only the latest supports Yosemite?
Also once I have the clone completed from CCC, is the process then to reformat the old internal drive and then clone from the CCC external drive back to the internal and then reboot and trust all is well?
Appreciate your help Csound1.
Regards
Andrew

Time Machine plural backups

In time past I lost my prime drive and Time Machine due to a bad Windows 7 backup drive. Don't ask how this could happen but I was working to install a Buffalo 3TB drive to act as a backup for Windows. It wasn't fun. I eliminated Windows all together as it is far to much trouble to maintain.
I have a 4 slot desktop which 2 were for Mac (prime and BU) and 2 were for Windows 7 and Windows BU. The Window drive problem scrambled the Macs and the Time Machine. I now have 4 for Mac with the other drives being BU.
My question is: Can I use my Time Machine and the other drives as Time Machines (TM 2, 3, 4) also?
One method I had been using is Disk Utility/Restore to make 2 of the extra drive like the original. This takes time and the drive ID needs to be watched. To much trouble. I can use a third party backup application. I use Intego for several other external drives but like the idea of the Time Machine does for search and recovery.
I didn't want to blindly experiment on creating extra Time Machines until I learned a bit more so if anyone can help, I would appreciate it.

Bud Willner wrote:
Thanks for responding.
From what I think you are saying is that it is safer to use a third party application to backup periodically.
No. That is emphatically not what I am stating. All backups fail. Sometimes at the most critical moment. I can and do use Time Machine. Heavily. I do recognize its limits, just as other approaches can and do have their own and often-unique limitations, and the occasional corruptions and failures can and do arise.
I have 4 internal drives and 4 external drives in my desktop but only one Time Machine. Three of the internal drives are for back as are all the external drives. I use Disk Utility restore process for direct copy from the main drive to two of the internal drives. This takes to long and ties up the computer.
To start with, obviously any backup is better than no backup. For time constrained environments, you'll end up with a controller-level backup (and I'm very skeptical around those), or an incremental backup, or you'll need faster I/O. USB 2 performance is glacial (if that's what you're using here), and many commodity hard disks are pretty slow devices, so... faster interconnects — Thunderbolt, USB 3 — and compatible and faster storage can help, here. There are also slow storage controllers.
What I had in mind is to protect the Time Machine and quicken the BU time for quicker computer recovery. If the Time Machine goes out, one needs to start all over.
As stated in my earlier reply, I tend to use multiple disparate Time Machine targets, particularly for higher-value data. Backing up a Time Machine backup device is going to be very slow. Others have tried that approach, and I've tried a few backups of the Time Machine disks over the years, and I've generally not found that approach to be particularly expedient, nor particularly efficient. The late Pondini had some comments on backing up a Time Machine volume that might interest you, too. But again, this is your call.
Of course, the counter argument is that with all the backup drives, extra Time Machine(s) would not be necessary.
Does that seem to be a reasonable conclusion, i.e., use the Intego BU process on a daily/weekly/monthly basis?
What you do depends on the value of your data and your time, your hardware and your software, and your risk aversion.
Just having backups is ahead of what some folks (don't) have available.
Whatever approach and whatever tools you pick, test the recovery path on occasion, just to make sure that works, that your backups are complete and are valid, and so that you have some idea of how long the recovery requires.
I'm not a huge fan of having all my backups in one box, for the reason mentioned earlier reply — not only does software fail, but so does hardware. Some hardware failures are obvious. Some just make the software flaky, or leave latent errors in the backup archives.
Backups are created because software and hardware can fail, and because the various creatures involved can cause problems for data longevity, too. These same sorts of failures can also cause problems for the backups, either directly or during the recovery.
Again: what you do here is entirely your call.

Confused about how Time Machine merges backups

Okay, I understand how TM works and that it merges many daily backups into one days worth by the next day. I've been doing some experimenting with creating a file on my desktop, backing up with TM, and then deleting it and emptying bin. I try to access this file the next day with Time Machine but it is if it never existed. Time machine shows no sign of it. It's there when I have access to the hour by hour updates. But by the next day, when everything from the previous day merged, it's gone. Am I missing the point of Time Machine? Wasn't it created for situations when you delete a file accidentally and want to bring it back sometime in the near future? What am I missing here? Thanks for your help!

mikemac22,
The last hourly backup in a given day is kept as the "daily" backup. The last daily backup in a given week is kept as the "weekly" backup, and these are kept as long as possible.
Time Machine is mainly intended to be a backup and recovery tool. Yes, if you mistakenly delete a file, it can be retrieved. However, the importance of a file is based on the length of time it remains on your "source." I doubt Apple set out to make it this way, but rather made the decision to go with this paradigm as opposed to the alternative.
You see, there is an inherent trade-off in any backup solution that works as Time Machine does. It probably would have been easy to make Time Machine "consolidate" backups, but then disk space would be consumed at a much faster rate. At some point, some decision must be made concerning the question, "when can a file be deleted from the backup?" In the case of Time Machine, as it is, a file becomes important enough to keep when it has remained on the "source" for at least one week. If it is kept for a shorter duration, and not restored, it will be deleted at some point.
On the other end of the spectrum, files that exist only in the backup will be deleted entirely when the oldest remaining backup that contains them is deleted. This "thinning" must be done in order to make room for new backups. If this action was not taken, Time Machine would just keep filling up drives, and quickly.
Time Machine is not an "archive" utility, in any sense of the term. It is not intended to maintain multiple versions of a given file for your convenience. What it is intended to do is to allow for the (almost) immediate recovery of your entire installation- user files, applications, and all- in the event you must format (erase) your source, replace your internal hard drive, or even swap computers completely. As a bonus, it will allow you to choose from several (perhaps many, depending on the size of the backup volume) backups going back in time when you do have to resort to a "Restore."
Another bonus, of course, is the ability to restore individual files that you might mistakenly delete.
Scott

On imac 10.6.8 using current version of Aperture. How can I access the Aperture Library on my external hard drive that I use with time machine for backup? I can only access the application but not the library..

On imac 10.6.8 using current version of Aperture. How can I access the Aperture Library on my external hard drive that I use with time machine for backup? I can only access the application but not the library..

Go into Time Machine (the program not the bundle on the extrnal disk) and using Time Machine's browser go to the Folder where the library lives. You could look in the library bundle in Time Machine but that won't really tell you much,
If you want to make sure it truely has backed up your library you will need to restore it and open the restored library with Aperture.
If all this still has you confused you need to read up on Time Machine in order to get a feel for how it works, for what it is doing and for how to restore files from it.

How do I use time machine to backup to an external hard drive plugged into my airport extreme

How do I use time machine to backup to an external hard drive plugged into my airport extreme? I used to be able to but now time machine will not recognize my hard drive to select as a backup when plugged into my airport extreme. I'm not sure what happened or changed. Any help is greatly appreciated. Thanks

First thing to do is go to the Pondini tips page, then follow the link to his full TM site for all the details.

Time Machine - all backups gone, backups fail

Similar Messages

Maybe you are looking for