Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Follow-up from https://discussions.apple.com/message/13337119#13337119

Follow-up from https://discussions.apple.com/thread/2805056?answerId=13337119022#13337119022

(question about Time Machine in Snow Leopard's time).


15 months later, here I am, back again with yet another horror story.


Mac OS X 10.7.4. Since the last problem, I kept using both the disk utility and Time Machine. The process for using Time Machine is still the same as described in April 2011. That is, the Mac's two users are encrypted using the old Filevault (which is, as far as function goes, a better solution than the new one that encrypts the whole system disk - if only because it allows to encrypt the users' data while having a non encrypted admin account from which maintenance can be done by a person that does not need to access confidential data). Time Machine saves are done manually from this admin non encrypted account while the two users are logged out and the modem is powered off.


Recently, because the Time-Machine Firewire disk was becoming a bit full, I erased it (after doing two separate full disk backups using disk utility and testing that I could reboot from each of these two backups). I then did a full Time Machine save of the disk. Since then, only two incremental Time Machine saves were done, using the above process.


Then a minor disaster struck. An erroneous command deleted a very big lot of important user files (and the wastebasket was emptied before it was realised that these files had been lost). OK. That's why backups are done, and the last of the two incremental Time Machine saves had been done in the morning. So, no reason to panic.


I powered up the Firewire disk and opened the encrypted user directory saved that very morning on the Time Machine disk. The whole directory structure was present and visible. Only, ABOUT EIGHTY PERCENT OF THE USER DATA FILES WERE CORRUPT ONE WAY OR ANOTHER AND UNUSABLE!!!!!


Given this, the surprising thing is that the remaining twenty percent of the data files were OK...


I had to use one of the backups done with the disk utility to recover the other lost files. Meaning a little over a week worth of data files were lost...


Since I started using Time Machine, I did two sets of tests, which were OK and produced bootable and usable restore but did not include incremental saves. And in the two occasions where I had to use the incremental backups to recover lost data, I was presented with corrupted files or disks!!! Good record, isn't it?


I previously wrote that Time Machine was NOT a backup utility but, at best, a fancy copy utility, because it did not check the integrity of the saved data. Today I must reckon that it isn't even a copy utility, but a death trap!


BACKUPS INTEGRITY IS THE SINGLE MOST IMPORTANT FEATURE ON A COMPUTER. That Apple is advertising such a trash as Time Machine as a backup utility is simply criminal! And it may cause unlimited damage to whoever is mad or gullible enough to trust her/his data to it...

iMac, Mac OS X (10.7.4), 4 GB memory

Posted on Jul 1, 2012 12:15 PM

Reply
18 replies

Jul 3, 2012 9:12 PM in response to DenisMaillard


DenisMaillard wrote:


OK. I give up.

Right back atycha!


ABOUT EIGHTY PERCENT OF THE USER DATA FILES WERE CORRUPT ONE WAY OR ANOTHER AND UNUSABLE!!!!! ... I was presented with corrupted files or disks!!! ... as demonstrated in my case, in restoring corrupted files ... This first attempt had resulted in about 80% of corrupt files ... And I did NOT corrupt anything ... my previous answers should have made it plain that NO corruption took place


Either I am not clear, or you have a comprehension problem. Or both.

Either way, I'm outta here. Adieu, mon ami.

Jul 4, 2012 10:04 AM in response to petermac87

petermac87:


Here is the note that originally misled me.

https://discussions.apple.com/thread/1688318

The reference is indirect, but this is what led me to try the restore the way I first did.



etresoft:


I first had trouble believing my eyes when I read your last note. A bunch of concatenated extracts that:

- Are out of sequence

- Are out of context

- Conveniently ignore the topic evolution

- Also ignore the demonstrated and several times stated fact that no corruption of the backup occurred, but (originally) a corruption of the restore.


Unprejudiced readers who have read all the topic from beginning to end will appreciate...


So, before dropping the issue, I'll write one last reply to sum up what I did.


I entered the original note to complain of corrupted files when restoring a backup.


My first reply was just an acknowledgement of the recommendation (that I was already following anyway) to have several backups.


My second reply denied that my way of saving data could have corrupted them (this was later established by what followed), did not accept that the use of FileVault 1 (a still supported feature, as of V10.7.4) could be an acceptable cause for corruption and acknowledged as a possibility the one proposed explanation that eventually turned out to be the correct one. This explanation was the non-supported way I did the restore. I also pointed out that, in my first bad experience with Time Machine, 15 months earlier, the non bootable disk I obtained from my backup had been restored in the supported way.


My third reply, after I redid the restore, acknowledged again the cause of the problem. I also mentioned a problem that showed up in the supported way of restoring files and a second problem (the fact that Time Machine allowed users to do unsupported manipulations). I also answered to the replies that hinted again that my way of doing the backups caused corruptions (which was proved false by the successful restore).


Then, the reply by etresoft that followed affirmed so many things that were not conform to the stated reality that my fourth reply was merely a new explanation of the events trying to put things straight and restating the real problems that I had met in the process. Said problems having nothing to do with my way of saving data.


When etresoft again twisted reality in his next reply to have it fit his own ideas, I entered my fifth reply to try and make things clear.


I'll now no longer restate the evidence. Readers will have to judge.

Jul 6, 2012 4:50 PM in response to DenisMaillard

DenisMaillard wrote:


petermac87:


Here is the note that originally misled me.

https://discussions.apple.com/thread/1688318

The reference is indirect, but this is what led me to try the restore the way I first did.




That is not a direct link! It is a link within another person's thread which points to a possible solution to their individual issue. It does not relate at all to an official Time Machine link.You need to be more careful before bandying around solutions and advice meant for others. I presumed you had at least gone to an official Apple Time Machine Site!


Good Luck


Pete

Follow-up from https://discussions.apple.com/message/13337119#13337119

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.