Time machine Deleted old computer backups

Hey,
I have been using a mac pro for about a year and a half now and as all computers get it has become slow and full of garbage. So i used my time machine back up and successfully backed up all my files. I put in the OS disk and wiped the computer clean and reinstalled the OS. I plugged the time machine back up in and began to copy over only the files that i wanted. A few days later I had not yet copied over all of the files that I needed, i was prompted me to set up this computer with a time machine back up. I began the process thinking that it would create the backups in a new file on the drive or append it to the current list of back up images. It stopped half way though saying there was not enough free disk space. on the 1 TB HD there was only 5 GB remaining. So I just canceled it and was going to finish copying over all of the files i wanted and they delete the old backups. However when I went to get my old backup files, they had all been deleted.
I was using this hard drive to store other media files as well as time machine backups. taking the HD into the local computer shop i was informed that that is a terrible thing to do and perhaps the reason that my backups have been lost. the tech said there was nothing to be done but reformat the drive and start again. I am hoping this is not the case. the drive still says there is only 5GB of free space however I can only fine 300GB of files on the drive. so i believe that the files are still there. Does anyone know a solution to this issue. There are many valuable things on this hard drive that i would hate to loose.
I have tried holding the option key and clicking on the icon to view other backups, but my original backups are not there.
Thanks in advance.

Before I make any reply, note that you are responding to a topic that has been inactive for more than two years, on a system two versions out of date. In the future, you would do better to start your own topic in an appropriate forum, specifying what system you're running and what hardware you're running it on, among other things.
this exact thing happened to me as well and I must say that I find it totally unacceptable...
Well, without more information, it's impossible to say what might have happened or how you can recover. You may find some answers on Pondini's excellent site:
http://pondini.org
However, it's important to understand that this may or may not have anything to do with Time Machine. Perhaps your backup drive is dying, perhaps its directory structure became badly corrupt, perhaps one of any number of other things could have happened. Because there is no such thing as storage that is completely stable, it's important to keep more than one backup, as noted previously on this topic.
Carbon Copy Cloner seems like a much better solution at this time.
Carbon Copy Cloner is an excellent solution. Is it better? No. It is simply different, and that makes it better in some aspects and worse in others than Time Machine. The best backup strategy will involve two different backup programs. I frequently recommend using both Time Machine and CCC. I use TM with a Time Capsule for one backup, which has certain advantages over CCC. I use CCC for a couple other backups, one of which is in a safe deposit box at all times, and that has some advantages over TM. Using both, with multiple backups, means that I'm extremely unlikely to lose much data, if any at all... unless a meteor hits and destroys both my home and my bank, in which case I've got bigger problems!
Anyway, with regard to recovery, take a look at Pondini's site. If that doesn't help, or you need assistance with something, start your own topic in the appropriate forum for your system and provide additional details that may help us better assist you.

Similar Messages

  • Doesn't Time Machine delete old backups when it needs more space?

    I've had time machine running for a long time now. It worked flawlessly for quite some time.
    Today it gave me the error that there was not enough free space on the disk to complete the backup (the error message says something like there is 360 GB of data on the Time Machine drive already, 140 GB of free space and it would require more than that to complete my backup). I have a 500 GB Time Machine disk and my Mac has a 500 GB hard drive, so I should technically never run out of space.
    The Time Machine almost acts like this is the first time I've ever backed up, which is not true. Shouldn't Time Machine delete old backups to make space for the new? What's even weirder is that if I open the "Star Wars" window of Time Machine I only see one backup from March 31, 2011, but I have been running Time Machine for well over a year now. I'm totally confused as to what happened. Any advice on how to get my Time Machine back up and running (without buying a new drive) would help!

    You see only one backup in the Time Machine window because Time Machine has deleted the older backups to make space to do the current backup.
    Time machine needs some working space to do its backups, and so backing up a 500GB drive onto a 500GB time machine volume is not ideal.
    However, I do essentially the same thing, and what I do, when I have this problem, is exclude things from the backup.
    First off, figure out what you changed. If you moved things from one partition to another, then that will cause a backup of the size of the thing that was moved. This may be why you have a large backup.
    When I have this problem, I exclude large things that have changed recently from the backup. This makes the backup smaller, and means that there is less working space needed. I do this until I get a successful backup. Then I remove things, one by one, from the exclusion list, and back up after each one.
    So, for instance if you just put 4 new folders on your drive, each of which s 20GB of data and they are named A, B, C and D, add all four to the exclusion list, do a backup, then remove A from the exclusion list (leaving B, C & D on it) and do a backup, and continue like this, adding 20GB of backup data each time until none of the new data is on the exclusion list and you get a completed backup.
    Another possible issue, if you use multiple partitions, is that Time Machine may be keeping an obsolete backup of a partition that you previously reformatted. To see if this is the case, go into time machine (The universe interface) and go back to the most recent backup it shows. Click on your computer and see what partitions show up-- are any of them old ones that have been reformatted and renamed? You may be storing a duplicate backup because Time Machine does not realize that the disk that went away isn't coming back (because it has been reformatted as a different partition)
    You can right-click on these items and remove them from your backup by sleecting "Delete all backups of...." This will free up space as well.

  • Time Machine deleted 4-5 backups...

    Time Machine deleted 4-5 backups that were from a different computer to make room for the an update. How can I get back 1 or more of those backups?

    Unfortunately, you can't, since they have been permanently deleted and the drive space has been overwritten with new data.

  • HT3275 My Time Machine deletes ALL previous backups

    Every so often, Time Machine deletes ALL previous backups and starts over from scratch. It has done this several times in the last year.  I have not changed any hardware or the name of the computer. Why is this happening?  Makes me very concerned that I now have NO backups while it chugs away rebuilding a 210 GB backup. 
    Just got an error message:
    Time Machine couldn’t complete the backup. Time machine could not delete the backup disk image "/Volumes/Joe's iMac.purgeable"
    HELP!
    iMac 27: 8GB, 2.9 GHz Intel Core I5
    OS X Yosemite 10.10.1
    Backup volume is Western Digital MyBookLiveDuo with 2TB and 1.8TB available

    Hi Joe,
    Have you Repaired both drives first, then Repaired Permissions on both?
    Have you looked through Pondini's extensive TM help site?
    http://Pondini.org/TM/FAQ.html
    http://pondini.org/TM/Troubleshooting.html
    Can't imagine something not being covered there.

  • Time Machine deleted my first backup to make space for a new one, is there anyway to recover it?!?!

    So I had all my stuff backed up to December 23 on an external hard drive with Time Machine, then I deleted it all so that the next automatic backup didn't have any of these older files. Today Time Machine deleted my original backup to make space for a new one and so I lost Decemer 23, now I am screwed..HELP?? I accidently let it delete or something, I don't really know, I know this was just a series of mistakes and now I'm desparate ):

    Have a look at this article http://support.apple.com/kb/HT1427 and section "backup drive fills up".
    It's a normal behavior that Time Machine is deleting oldest backups when drive is filling up.

  • Help! Time Machine Deleted My Oldest Backup!

    So, time machine deleted my oldest backup (because it ran out of room)
    I know it's supposed to do this -- but I didn't want it to.
    On my oldest backup, I had a folder with lots of pictures and documents. Does time machine delete files that can't be found anywhere else?
    I don't know what to do! Those pictures meant a lot to me!

    Time Machine isn't meant to be used as an archiving utility, as you've now noticed.
    If a file isn't on your internal hard drive, eventually TM will delete the copy in its backups.
    If you wanted an archiving utility, you needed to look elsewhere
    You may be able to use a data recovery software to get the files back--I suggest you turn off TM until you get this sorted.
    Take a look at Data Rescue II here:
    http://www.prosofteng.com/
    ~Lyssa

  • Time Machine deleted old backups as disk filled up. Now I'm confused

    Hi guys,
         My backup disk was full, and hence Time Machine deleted my old backup. The most important data on my Mac (for me) is my iPhoto library. As I know it, Time Machine deletes backups for files which are used less frequently. In my iPhoto library, there are some photos which I haven't opened for years. So has Time Machine deleted them?
    Thank you

    As I know it, Time Machine deletes backups for files which are used less frequently. In my iPhoto library, there are some photos which I haven't opened for years. So has Time Machine deleted them?
    Time Machine won't delete files that are still on your Mac, regardless of how long since you view them.
    What it trashes are files that have been removed from your Mac. So, it's not an archive app. For instance, if you backed up with TM and then deleted the pics from iPhoto on your Mac (to save space or whatever) then eventually they will be deleted from TM.
    Regards
    TD

  • Time Machine Deleting Old Backups!!

    Good morning,
    I recently installed a new hard drive and a clean OS X 10.6.3 in my MacBook Pro (2008).
    I plugged in my Time Machine back-up drive, and TM started getting rid of my old back-ups!
    Can anyone advise me on what is happening and how to prevent this? Is this a malfunction or, more likely, something I don't understand about TM?
    Thanks for your help.
    Cheers,
    Burntmonkey

    BurntMonkey wrote:
    Currently my new 500Gb hard drive has 210Gb of data.
    My back-up drive is a 500Gb drive. Previously it had 180Gb free space, but all (98%) of the data on the drive is what I rebuilt my new drive with so it's the same data.
    Does Time Machine need to 're-backup' this data?
    Yes; it's a different drive, so is treated as never having been backed-up.
    Time Machine erased about 60Gb of old backups so now the capacity of the back-up drive is at about 240Gb.
    Yes, it would have deleted a lot of old backups to make room. In addition, it adds 20% to the estimated size of the backup, for workspace on the backup drive, so it would need roughly 250 GB to back up the 210 GB on your drive.

  • Time Machine Deleting old backups after full restore

    So I'm wondering if anyone else came up with this issue:
    My computer crashed and so I restored my MacBook from Time machine. I've never done this before, but figured it would put everything back to how it was.
    It did on my hard drive, but my Time machine external drive's backups all got wiped! I had about 1.5 years of backups and they are all gone!
    I realize that hopefully the backup that I restored to should have everything I need, but I never thought to backup my backup drive before using it to restore.
    Seems like a really dumb glitch in the software.

    harryhewitt wrote:
    Exactly what happened with me. I was using Snow Leopard, my macbook pro died, I bought a new one and restored from my HD which I had used with TimeMachine to back up to for the past 18 months. it restored brilliantly and I was impressed - passwords etc were all there.
    However, I now see that I have no backups other than the last one before my old mac died. As has been said, that is a serious glitch in the software. At the very least there should be a warning that it is going to do that. And why does it need to do that?
    It's a different Mac. Time Machine backs up each Mac (and each drive) separately (all other full system backup apps I've ever seen do, too); if it didn't, those who back up 2 or more to the same place would have a complete and unreliable mess.
    I'd agree that the "Would you like to reuse the backup" prompt you saw on the first backup of the new Mac could be worded better, but it is explained in #B5 of Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).

  • Time machine deletes old backups with new system drive

    So I decided it was time to get a larger system drive. After I finished migrating to the new drive, I plugged in my Time Machine backup drive, and now it's deleting all my old backups! What gives? Shouldn't Time Machine keep doing incremental backups the way it always has? Nothing has changed except the drive -- the files are still the same. I had backups going back to 2011, so it's a bit unsettling to see this happen.

    Digijohn wrote:
    So I decided it was time to get a larger system drive. After I finished migrating to the new drive,
    On Snow Leopard, that's what usually happens. 
    On Lion and later, depending on exactly how you put your data back, it usually doesn't -- TM changes the backups so they look like they were made from the new drive. And there's a way to do that manually.
    But on Snow Leopard, there's nothing you can do.  Note that you can still see and restore from the remaining old backups, via the procedure in #E3 of Time Machine - Troubleshooting.

  • Time Machine : Deleting all local backups of one of several computers leaves files behind

    Hi,
    I'm in the process of transitioning my Time Machine setup. For the moment, I have a local Time Machine volume backing up three Macs to the same Backups.bakupdb folder (I had set that up two years ago before reading Pondini's Time Machine FAQ).
    Basically what I want to achieve is have a partition per computer that I'm backing up. So what I did was I partitioned a second external drive into 3 partitions, and I copied my TM partition to each of these 3 temporary partitions. I did that using Disk Utility's Restore tab. My plan was then to delete the backups of two computers off each temporary partition (per question 12 of Pondini's FAQ), to get 1 computer per partition on the temporary drive, then partition my main external drive in 3 and copy back each temporary partition to the main drive.
    (The second external drive is lent, I can't just switch to using it.)
    From what I read on question 12 of Pondini's FAQ and this reply by Pondini to a similar thread, I thought that deleting all backups of one computer via the Time Machine interface would leave me with an empty folder for that computer under Backups.backupdb, and that I could just delete this folder via the Finder. This is * not * what happened.
    After all backups for the first computer I wanted to delete off the first temporary partition are deleted, the folder for this Mac is not empty ; it still contains all the 15 dates folder of the individual backups. What's more, these date folders aren't empty either. The first 12 of them I deleted (the most recent ones) each contains a Macintosh HD folder, under which remains a System/Library/CoreServices hierarchy. The (locked) boot.efi file is alone in the CoreServices folder. The last 3 dates I deleted (the oldest backups), however, still contain an even bigger hierarchy. Applications, Library, System and Users exists in all three, with a lot of subfolders and lots of files, totalizing around 2 GB of data. Most of the files are locked, even logged into root (very diverse files : plists, dylibs, rtf files, fonts, etc) but some are not (apps, and other diverse files : colorsync profiles, dashboard widgets, bundles...). Seems like Time Machine could not delete everything. (Why ?)
    Note that I deleted the backups for one computer using that same computer, first using an Admin account for the first 3 or 4 dates and then using the root account to avoid having to always authenticate. (I didn't think it would create a problem... maybe it has?)
    When I go back into Time Machine for this computer, no backups remains. It's like if Time Machine doesn't see the data that it could't delete... This is all very strange.
    My question is : can I delete these leftover files and folders bia the Finder without fear it's going to break the backups for the other computers on the same partition ? If not, what should I do ?
    Sorry for the long post, but I hope I was clear...

    Phil_6379 wrote:
    After all backups for the first computer I wanted to delete off the first temporary partition are deleted, the folder for this Mac is not empty ; it still contains all the 15 dates folder of the individual backups.
    It shouldn't; when you delete a backup, the date-stamped backup folder and all it's contents should be deleted.
    Most likely, there was some sort of corruption, either on the original or the copies, that left some pieces.  On occasion, that will happen even when Time Machine is doing it's normal "thinning:" there will be a message in the log about finding a "partially-deleted" backup, and trying again.  Sometimes the second try will do it, sometimes not.  In that case, you might be able to delete it after running Repair Disk;  if not, sometimes you can delete it via the Finder.
    Under Lion only, deleting backups via the Finder is supported by Apple;  you'll get a message about how it can't be undone.  But it doesn't always work, so is recommended only as a last resort.  Holding the Option key while deleting may help with the locked files.
    If you can't get rid of the detritus, however, I'd recommend erasing the affected partition(s) and starting over.  I'd not continue backing-up to a set of suspect backups -- the way they're all linked together, there's just no telling whether you could do a full system restore successfully.
    In addition, as Linc says, even if you have some things off-site, I'd strongly recommend getting another external HD for "secondary" onsite backups.  Externals are getting much less expensive all the time, and if there's a problem with the old one (either the drive itself or the backups on it), you'll be in a large pickle.  Plus, of course, drives don't last forever.  See #27 in Time Machine - Frequently Asked Questions for some suggestions.

  • Time machine deleted all my backups instead of the one selected

    I have a one year old Macbook Pro with 16 GB of RAM, running OSX v10.9.5 (Mavericks).  I use a LaCie 2TB external hard drive for my time machine backups, and I needed to delete some of the old TM backups to make space.
    Following the instructions at pontini.org (http://pondini.org/TM/12.html ), I opened TM, navigated to the external HD and selected the oldest folder in backups.backupdb, right clicked it and selected 'Delete all backups in [the oldest folder's name]'.  Then I went home for the weekend, and when I got in this morning, Voila!  ALL files in the backups.backupdb folder were gone!  Not only that, but there was nothing in the trash to restore!
    Has anyone else had this wonderful experience?
    Thanks,
    Casey

    Wow -- thanks for all the comments, folks, I must have struck a nerve!  I'll try to respond to all of them here, in sequence:
    John Galt: I loved your comment about "no user serviceable parts inside"!  It was echoed by etresoft, too, later in the chain; sounds like good advice if this ever happens again.  You mentioned that Yosemite incorporated a lot of changes to TM, but I'm not using Yosemite (have been avoiding this upgrade, as it sounds too buggy).  But apparently your advice holds with Mavericks, too. 
    Etresoft (3:17am): very good point -- I think that's exactly what I did.  What I'm still not clear on is: are the backup files themselves (ie the actual data being backed up, as opposed to hard links) stored in the backup folder that TM creates, or are they kept in a separate file or folder?  It sounds like it's the former, as I had originally thought.  But pondini led me to believe that, if the data WAS stored in the folder, it would not be deleted if there were any links to it in future backup folders.  From what you said, I'm thinking that's probably true IF you are dealing with a backup that's INSIDE TM, but not if its a folder OUTSIDE TM.  Is that right?  If so, this really is a pit that's ripe for idiots like me to fall into.
    Lex Schellings (3:52am): I don't think I understand your comment -- you said "All these instructions are to delete a specific file... You should never deleted a dated FOLDER".  But instruction #2 says "One or more individual backups -- it's best to use Time Machine, per the green box below" --  then, in the green box, it says " Locate the backup or item you want to delete via the Timeline or "cascade" of Finder windows".  Since I was trying to delete a "backup", what was I supposed to select, if not a folder?
    Etresoft (4:15am): that's an interesting thought, but I don't think I used the sidebar to navigate to the backup I deleted.  When I opened TM, it showed me a sequence of Finder windows with the Star Wars background, but the external hard drive in the Finder window was grayed out and inaccessible.  So I checked pondini again, and it said I could get to it by right-clicking on the TM icon in the task bar (after exiting TM), selecting 'Browse other TM Disks', and selecting the one I wanted.  After I did that, I could see the external hard drive in TM was not gray anymore, and I navigated to the first backup folder.  Apparently, that's what took me "outside" of TM, even though I thought I was inside it.  I will definitely follow up on your suggestion to go to Apple's bug report site and file a report; thanks!
    Lex Schellings (4:39am; do you guys ever sleep?): I didn't hear that pondini had died -- I hope you folks weren't close to him; sounds like he was very thorough, and trying to do the right thing.  He just didn't realize there were people like me out there.   
    I'm surprised at your comment that "the behaviour of deleting one of the TimeMachine dated folders in Finder has always been the wrong way, leading to unhappiness."  That is exactly what our tech support department (which is run by Lockheed Martin; they're supposed to know what they're doing -- at least they certainly charge JPL enough for their service) said was the approved way to delete old TM backups, and in several cases in the past, it has worked for me.  In any event, I didn't think I was deleting the TM dated folder through Finder -- I thought I was doing it through TM, as pondini recommended.  Silly me.
    Etresoft (5:24am): It's a little scary that you said "I don't know of anyone who knows Time Machine well enough to actually update it."  Were you joking?  I definitely agree with your (and John Galt's) advice that "I wouldn't recommend any kind of interference with Time Machine, especially with the Finder".  In the future, I think I will just set up a separate partition on my external drive for TM backups, and let TM figure out how to thin itself out.
    Lex Schellings (5:43am): "a magic black box" -- that's a very good take-away from this misadventure. Thanks for your advice.

  • When Time Machine deletes old backups......

    My Time Machine disk is about to be full. I realize that when the disk becomes full, Time Machine will delete old backups.
    I am not clear, however, exactly what this means.
    Is what are deleted:
    1. older disk pseudo-images?
    2. files which no longer are on the computer?
    Or is Time Machine actually deleting files which are still on the computer (but were in the old now-being-deleted backup)?
    I suspect it is #1 and #2. So if you had a computer where files are added over time (without meaningful deletions), this strategy will not help a lot---you just need to get a new disk.
    Is another option to just make a complete new full Time Machine backup (losing all the intermediate backups)? How is this done?

    Jeffrey Folinus1 wrote:
    Is what are deleted:
    1. older disk pseudo-images?
    I have no idea what that is.
    2. files which no longer are on the computer?
    Yes. More to the point, files that were changed or deleted long ago.
    Or is Time Machine actually deleting files which are still on the computer (but were in the old now-being-deleted backup)?
    No.
    When Time Machine does it's first, Full backup, it of course copies every file and folder on your system. It also makes a folder in your backups, named with the date and time of the backup. This folder appears to contain all those copied items.
    But it doesn't. It contains "hard links" to the backup copies. Think of these as extra-fancy aliases.
    Thereafter, TM does "incremental" backups. It copies only the files and folders that were added or changed, and makes another dated folder for that backup. In that folder are links to the new items, plus links to the items that didn't change: so they're cleverly named "multi-links." This is how TM appears to have many full, complete backups of your system when it obviously doesn't.
    When TM deletes a backup, all that's really deleted are the folder and the links.
    Consider what happens when you do a normal (not secure) deletion of a normal file: OSX basically "forgets" where it was, so the space can be re-used. TM is a little fancier: as long as there's even one link to a file, it isn't forgotten, so it's available to be recovered from any backup that has a link to it, and the space isn't re-used. When the last link is deleted, the copied file is forgotten.
    Thus, when you delete a backup, the only actual backup copies that are deleted are the ones that have links in no other backup. So, for example, once you've done a Full backup and a single Incremental, you (or TM) can delete the Full without losing it's copy of anything current.
    Another way to look at it is, *each backup is, in effect, a full, complete copy of your entire system the way it was at the time of that backup.*
    So much for "fancy." The "extra" fancy part is, TM doesn't necessarily make another link for every single file and folder that didn't change. Instead, if a folder wasn't changed, and nothing in it was changed, TM makes only a single link, to the folder. When you consider that your System folder, for example, contains many tens of thousands of sub-folders and files that rarely change, you see how efficient this is.
    For more details: http://www.appleinsider.com/articles/07/10/12/roadto_mac_os_x_leopard_timemachine.html
    and: http://arstechnica.com/apple/reviews/2007/10/mac-os-x-10-5.ars/14

  • Time Machine delete old backups

    My wife has a MacBook Pro and uses Time Machine on a 500 GB external drive. She is using about 160 GB on her MacBook Pro, but the Time Machine drive is now full and is not backing up current files. The Time Machine backups go back to 2010 and two or three versions of the operating system. I would like to delete old backups from Time Machine, as I understand that only files no longer needed in other backups will be deleted. Is there any reason this approach should be avoided? Are there instructions on the best way to do this? Thanks.

    tomarm wrote:as I understand that only files no longer needed in other backups will be deleted. Is there any reason this approach should be avoided? Are there instructions on the best way to do this? Thanks.
    yes, your wife ..
    A: needs a MINIMUM of a second HD to archive data on
    B: Yes, time machine "throws data out the window" when full
    C: HD clones are more important.
    https://discussions.apple.com/docs/DOC-6031
    Methodology to protect your data. Backups vs. Archives. Long-term data protection
    Time Machine / Time Capsule
    Drawbacks:
    1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
    2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
    3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
    4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
    5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
    6. Restoring from TM is quite time intensive.
    7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
    8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
    9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
    10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
    11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
    12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
    13. *Level-1 security of your vital data.
    Advantages:
    1. TM is very easy to use either in automatic mode or in 1-click backups.
    2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
    3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
    HD clones (see below for full advantages / drawbacks)
    Drawbacks:
    1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
    2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
    Advantages:
    1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
    2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
    3. HD clones are unconnected and isolated from recent corruption.
    4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
    5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
    6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
    7. *Level-2 security of your vital data.
    HD cloning software options:
    1. SuperDuper HD cloning software APP (free)
    2. Carbon Copy Cloner APP (will copy the recovery partition as well)
    3. Disk utility HD bootable clone.

  • Any way to restore Time Machine deleted old backups?

    Hi,
    I've just discovered that Time Machine has successfully deleted my very first backup and all my files tediously archived from 2002 has disappeared. TM has failed to warn me that my disc was full.
    My only question is there any way at all i can recover these files? I have unfortunately dumped all my old cdrs.<proceed to wail uncontrollably>
    Help.

    V.K. wrote:
    nerowolfe wrote:
    I am beginning to suspect that when TM informs the user that backups are being deleted, it is not with a popup on the desktop, but rather via the console only.
    No. that would be totally absurd.
    Absurd, perhaps, yet possibly true. From reading these boards, many people have never gotten that message, but the logs do show that old backups are being removed.
    I was also being sarcastic but I suppose unless you know me, it does not show
    No user is reasonably expected to monitor console for a message like that.
    I agree but the facts show that very few have ever gotten this warning. Again, I was being sarcastic.
    I did get a regular desktop popup warning me about this when my TM drive filled up. but as I understand this particular feature is quite buggy and many people don't get those popups.
    If it is buggy as you note, then what I wrote is not so absurd after all, IMO.
    TM is not quite ready for Prime Time. It is a useful tool, much like a hammer or tire wrench, but it is only a tool.

Maybe you are looking for

  • Trying to sync apps in itunes after a complete computer reboot-

    I recently cleaned out and rebooted my Macbook Pro from scratch and am now trying to organize my apps which exist on my iPhone 4S with my iTunes library. We have several Apple products using the same iTunes library, but we manually select which apps

  • Moving music from my ipod to my new i phone

    Is ther an easy way to move my itunes purchased music from my ipod to my i-phone

  • Search function (Spotlight) not working in Mail

    Hi, This just started happening today on my PowerBook G4. The search function in Mail is not working. No matter which mailbox I go into to search for a term it shows 0 results when I know for a fact there should be multiple results. If I search for a

  • WES8.1 IP install problem.

    I created something using SIM, much like my existing WES7 image in style (disk partitions, bits and bobs, user etc) Fire up the installer with the autounattend.xml on a USB and it gets all the way to: Windows could not apply unattend settings during

  • Static import of member of class in same unnamed package fails

    I think I found a bug in the JDK 1.5 (Tiger) javac compiler. It involves static import and unnamed packages. Consider the following compilation unit: import static D.x; class C {     int foo() { return x; } class D {     static final int x = 1; }Runn