-
All replies
-
Helpful answers
-
Oct 15, 2015 7:28 PM in response to BruceLiby j-m-d,add me to the list of people bitten by this. I have an iMac hardwired to the TM, and have had no problems till tonight. It is about 18 months old.
lots of people complaining about this online/here
does anyone have actual answers to:
a) can I feel safe these problem is not my iMac, or something on it (can I trust separate CloneCopy BUs I make of it ?)
b) seems many people continue to get these after the first one ? why is this ?
c) is it HW fault on the TM ?
d) is this any way to make this stop ?
e) was the problem caused during the last BU ? I guess I'm asking if the Verification is performed after each BU, if not, when ?
f) is there a way to perform a manual Verification of the TM BU ? I can't find it, if there is.
thanks
why doesn't it just go back to the last valid BU, wouldn't that be the point ?
-
Oct 20, 2015 9:52 PM in response to adib1by matthew_sl,Adib1,
I ran tmdiagnose, but can't file a bug report at the URL you cited since you need to be a registered Apple Developer. I really appreciate the suggestion, but it will be pretty hard for 'lots' of users to follow this process if it's limited to registered devs.
I filled out the Apple "Product Feedback" form for Airport Time Capsule, but there is no ability to attach files to that form.
If you have any other suggestions, please let the world know! I'm not even backing up much data, and this just happened to me for the first time (OS X 10.10, top of the line Macbook Pro Retina 15", and a less than 1 year old Time Capsule).
Thank you
-
Nov 6, 2015 2:00 PM in response to July7Kiss1995by danfrommountida,Same problem, and cannot submit a tmdiagnostic.zip file because I'm not a developer.
Sheet!
I love the ability of Time Machine to create snapshots of backups on different days. I despise having to throw all of those snapshots away because of this defect.
There may be a way out. I have Time Machine configured to backup to more than just an Apple Time Machine disk. I also have it configured to backup to two other drives. If I ask Time Machine to create a new backup for me, will it only do so on the Apple Time Machine module, leaving my other snapshots intact, or will this cause all snapshots on all disks to be lost? Hope someone can definitively answer this. Thanks in advance.
(iMac 27 inch, mid 2011, running El Capitan Version 10.11.1)
-
Nov 6, 2015 2:33 PM in response to danfrommountidaby LaPastenague,If I ask Time Machine to create a new backup for me, will it only do so on the Apple Time Machine module, leaving my other snapshots intact, or will this cause all snapshots on all disks to be lost? Hope someone can definitively answer this. Thanks in advance.
Other backups are left intact.. you can start a new backup to a different disk at any time.. that is effectively all you are doing.. and TM will continue to work with all the previous snaphots on the other disks.
Someone recently posted a fix for their corrupted backup. How general a solution this is I don't know.
Fix corrupt TM backup.
https://discussions.apple.com/message/29263757#29263757
1) Disable Time Machine.
2) Stopping all Spotlight indexes (mdutil -d -a).
3) Destroying all Spotlight indexes (rm -rf /.Spotlight-V100) manually.
4) Repairing a file system permission issue with Spotlight (removed a bunch of folders owned by a non-existant user in a /private/var/folders subfolder that Spotlight created). No idea how they got there but they were there and the logs were complaining about them causing a fatal error.
5) Re-enabling Spotlight indexes and letting them build fully.
6) Re-running an initial Time Machine backup.
-
Nov 6, 2015 7:31 PM in response to danfrommountidaby adib1,If you can't login to https://bugreport.apple.com consider registering as a developer in https://developer.apple.com – it's free if you're not looking to publish apps to the App Store.
Otherwise maybe take it to the media as a last resort? Long ago I've written an article that explains the underlying issue in a non-technical way as much as possible. Maybe someone could highlight this long-standing problem so that Apple's higher management take notice?
Thanks.
-
Nov 14, 2015 2:33 PM in response to adib1by Ingmar Hemsen,I just got the same error message and reported a bug report on bugreport.apple.com: 23548218
The result from "sudo tmdiagnose" was a 5 Mb zip file and was attached to the report.
My setup:
Mac Mini with MacOS X 10.10.5 with cabled ethernet network to a TimeCapsule. TC version 7.6.4
The TC WiFi is switched off, but it is connected to a separate WiFi router.
The backup of the Mini started in September 2010. Last successful backup 30. October 2015.
I also back up a MacBookPro to the same TC over wifi. No problems there so far.
I'll report back any response form Apple. And I will wait before trying the suggested fixes.
-
Nov 16, 2015 5:56 PM in response to LaPastenagueby danfrommountida,With the knowledge that I'd be able to keep earlier backups on other devices (thank you!), I just pushed the "fix it for me" button and let it run a day and a half or so. All seems okay now. But, what a pain!
-
Nov 17, 2015 2:25 AM in response to danfrommountidaby LaPastenague,danfrommountida wrote:
With the knowledge that I'd be able to keep earlier backups on other devices (thank you!), I just pushed the "fix it for me" button and let it run a day and a half or so. All seems okay now. But, what a pain!
TM has become too unreliable..
I strongly advise people now to buy an alternative backup.. eg Carbon Copy Cloner or Chronosync. I use the former.. it is faster and more reliable than TM.. without doing all the incremental storing of file versions to be sure.
-
Jan 24, 2016 7:37 AM in response to LaPastenagueby rsterrill,I concur. After many wasted hours of research I've concluded the Time Machine is nothing more than a novelty. It may be different for other folks, but in my situation I have a Time Capsule, an Ethernet-connected NAS and a hard-wired USB drive. The USB drive is the only one of the three that it has never found reason to force me to discard all my legacy backup files with the phantom "unreliable backup" message. That drive is only periodically connected and stored offsite as a catastrophe mitigation measure so it misses many intermediate versions of files. I believe that Time Machine might work if you have two storage devices permanently installed inside your machine and connected 100% 24/7 to the main bus, but if you do anything novel like external storage, NAS or USB - well you are operating way outside the bounds of normal and are engaging in risky behavior with your data. I'm going to buy a commercial backup software package today and be done with this vexation.
-
Jan 30, 2016 12:08 PM in response to rsterrillby EdHans,Well, this is no good. I just got the same error. My TimeMachine is only a few months old. I just told it to create a new backup. I use CrashPlan as well, and all of my documents are on OneDrive, so not really worried. TM is my way to fully restore my entire machine in the event of disaster.
Will creating the new backup totally remove all of older stuff in the "corrupt backup" freeing space on the drive?
-
Feb 10, 2016 5:22 PM in response to Ingmar Hemsenby zmonteca,I did the same: 24600131
Bug report was submitted successfully.
-
Feb 15, 2016 2:01 PM in response to zmontecaby Ingmar Hemsen,Just checked the response from Apple on my report:
"Duplicate of 15971899 (Closed)"
I guess they need a few more cases before the issue is escalated.
The TM software and hardware (TimeCapsule) should handle power outages and network communications problems. That is more or less why we have them. I live in Oslo where we almost never experience power outages, but I noticed one suddenly one morning this autumn. If that was enough to ruin 5 years of backups, it is not good enough. Imagine having an unstable power supply as many (most?) people have. If a UPS is needed for reliable backups, Apple should either build a small on into TC to let it shut down gracefully or at least state the requirement clearly.
-
Feb 16, 2016 7:46 AM in response to Ingmar Hemsenby zmonteca,My Bug ID 24600131 is still open. They asked me for more information and to be able to replicate the issue. I have done this and resubmitted. Stay tuned.
-
Feb 16, 2016 7:51 AM in response to rsterrillby Csound1,rsterrill wrote:
I concur. After many wasted hours of research I've concluded the Time Machine is nothing more than a novelty. It may be different for other folks, but in my situation I have a Time Capsule, an Ethernet-connected NAS and a hard-wired USB drive. The USB drive is the only one of the three that it has never found reason to force me to discard all my legacy backup files with the phantom "unreliable backup" message. That drive is only periodically connected and stored offsite as a catastrophe mitigation measure so it misses many intermediate versions of files. I believe that Time Machine might work if you have two storage devices permanently installed inside your machine and connected 100% 24/7 to the main bus, but if you do anything novel like external storage, NAS or USB - well you are operating way outside the bounds of normal and are engaging in risky behavior with your data. I'm going to buy a commercial backup software package today and be done with this vexation.
Try using it in a supported manner. NAS is not a compatible destination and thus doesn't work correctly.
-
Feb 17, 2016 2:05 PM in response to Guillaume Maianoby foxmajik,It's 2016 and this problem still exists with no explanation.
This makes time machine backup unreliable and thus, worthless.