Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About sungoddt

  • Rank
    Occasional Forum Poster
  1. same here, several full backups, to different devices, all completed without assert errors
  2. given that dantz has admitted, finally, what was instantly apparent to many users posting on this forum, that the initial tiger update has bugs resulting in the assert errors, 'tardy' seems generous as of now, dantz has yet to ship any update that *reliably* carries out backups under tiger, let alone one that supports the extra filesystem features
  3. according to dantz's updates page retrospect 6.0.212 is for tiger only for panther you should be running 6.0.204 http://www.dantz.com/en/support/updates.dtml#mac
  4. hmmmm, after a week or so of successful backups, retrospect has reverted to failing with the elem.c821 error as it did when first installed, the apparent trigger was installing adobe creative suite 2 (backup succeeded immediately before this, failed immediately after, and 8 hours later still fails) dantz have tech notes/postings acknowledging that there is a problem with retrospect and offering possible workarounds, such as excluding spotlight files, and starting/logging-in in safe mode i've tried both of these but still get the elem.c821 error, so still looking for a real resolution when retrospect aborts and shuts down, if i restart it and do a recycle backup then it will just fail again at exactly the same point, however restarting it and doing a normal (incremental) backup on the partial backup set from the failure results in a 'successful' backup i haven't had time to run a verify yet, this is burning a lot of time, any guesses about whether this backup set is safe to rely on?
  5. Quote: I hope you're not putting forth a theory that the replacement of the Retrospect application is what made this work... The only way to identify the cause of a software bug is to regress your test; go back to the configuration where it works/fails and see if it works/fails again. i'm not putting forth a theory, i'm making a statement of fact there is sufficient evidence to suggest that the new release of retrospect is unreliable on some systems running tiger on my system the other backup utilities i've tried are ok, all disk/filesystem checks pass, no other applications are crashing or giving weird results, only retrospect seems to have an issue having finally managed one full backup out of 6-7 attempts certainly hasn't made me think the problem is resolved, enough people have had the same error that i want to know *why*, and as only dantz has access to the code generating the messages only dantz can do this dantz doesn't give people support unless they pay i'll happily offer dantz the same deal: if dantz pays me my standard day rates then i'm available to help track down the problem dantz has my contact details, i await their purchase order
  6. hmmmm, interesting, ok, i tried again, downloaded from scratch (third or fourth time), deleted/reinstalled (third time), this time my backup to a new backup set worked so after several days of failing every time, it suddenly is "ok", but aside from emptying trash and deleting some video workfiles i haven't changed anything on the mac except for the multiple deletes/re-installs of retrospect which leaves my confidence level at zero backup software must be 100% reliable, not subject to unexplained success/failure until dantz issues a fix or explains what external problem was/is causing these errors i obviously can't rely on retrospect
  7. if i move some files before starting the backup i can get the tree.c-3444 error (instead of a different error) presumably it is due to the same underlying problem as the elem.c-821 error (which i get otherwise) reported here... http://forums.dantz.com/ubbthreads/showflat.php?Cat=0&Number=55501&page=0&view=collapsed&sb=5&o=&fpart=2&vc=1 let's face it, this release of retrospect is borked
  8. to be honest my patience with dantz has expired at present i'm testing alternative backup software, the prospective vendor has responded inside an hour with the *resolution* of a technical issue with their software dantz no longer gives that level of service
  9. same error here I have just installed the updated version of Retrospect on a latest model powerbook 17" running tiger immediately before the powerbook being upgraded with tiger the earlier version of Retrospect performed a successful backup attempting to perform a backup from tiger with 6.0.212 results in an internal Retrospect error, repeating the process results in exactly the same failure the backup was to an external lacie d2 firewire drive, with latest firmware, which passes disk test (as does the internal drive being backed up creating a *new* backup set on a *different* external disk (lacie, latest firmware) and attempting a backup results in *exactly* the same failure so at present I cannot perform backups, sigh reported to Dantz support yesterday, no acknowledgement so far extract from the Retrospect log showing the failures... ∆ Retrospect version 6.0.212 launched at 5/5/2005 22:37 + Retrospect Driver Update, version 6.3.102 + Executing Immediate Backup at 5/5/2005 22:44 To backup set Backup Set A… 5/5/2005 22:44:36: Recycle backup: The backup set was reset - 5/5/2005 22:44:36: Copying osx100… Internal consistency check failed: Assertion check at "elem.c-821" 5/5/2005 22:50:51: Execution incomplete. Remaining: 297048 files, 58.9 GB Completed: 21550 files, 1.6 GB Performance: 257.2 MB/minute Duration: 00:06:15 (00:00:15 idle/loading/preparing) Quit at 5/5/2005 22:50 ∆ Retrospect version 6.0.212 launched at 5/5/2005 22:51 + Retrospect Driver Update, version 6.3.102 + Executing Immediate Backup at 5/5/2005 22:57 To backup set Backup Set A… 5/5/2005 22:57:37: Recycle backup: The backup set was reset - 5/5/2005 22:57:37: Copying osx100… Internal consistency check failed: Assertion check at "elem.c-821" 5/5/2005 23:03:43: Execution incomplete. Remaining: 297050 files, 58.9 GB Completed: 21550 files, 1.6 GB Performance: 263.8 MB/minute Duration: 00:06:06 (00:00:15 idle/loading/preparing) Quit at 5/5/2005 23:03