terryj Posted April 6, 2006 Report Share Posted April 6, 2006 Running Retrospect Express 9.21 on a G4 533, with 1.25GB of Ram, and Quantum Ultra SCSI DLT tape Drive. This error occurs on one particular backup set, and has begun to spread. I have six backup sets, each with double backupsets, named -a and -b, so I have been able to limp along and only do my backup-a, and not backup-b for a particular backup because after initial launch, and it goes through the steps of checking for the device ( SCSI) and then matching the backup set, when it prepares to execute, it gives the "elem-817c" error, and fails. Things I have been noticing: *On Recycles or New Media, doesn't happen, only on new ( incremental) *At boot up of the mac, I get a weird "File Sharing could not be enabled" message, even though all CP/EXT for filesharing are off. On the ones that do work, I get about 50% of the time an error for "date and time may not be synced, Retrospect has unexpectedly quit" at the END when it it trying to update its catalogs on some -a backup sets, but I can ususally run it again ( after a reboot) and it works fine. Any help would be appreciated! Quote Link to comment Share on other sites More sharing options...
terryj Posted April 7, 2006 Author Report Share Posted April 7, 2006 Ok, further testing.... I created a brand new BackupSet and script, named Backupset3 ( storageset named same). I set it to backup as normal an attached 160GB FW drive. I also unchecked the following: *Set time of volume storageset *stop on errors So far, it has been running trying to scan the fw drive, and create its catalog (matching) in ths normal backup, but it has stalled once. Quote Link to comment Share on other sites More sharing options...
terryj Posted April 10, 2006 Author Report Share Posted April 10, 2006 Ok, further testing... at the point of updating the catalog, with 40 items left to go, (having updted 173GB of items) the elemc error occurs, and retrospect can only be quit via forced reboot. I will investigate if this is because the storage set is too large for it to handle updating the catlog, and if making a smaller catalog and storage set will fix the problem.... Quote Link to comment Share on other sites More sharing options...
terryj Posted April 11, 2006 Author Report Share Posted April 11, 2006 ok, further testing still... on the two smaller catalogs I created, the first at 30Gb of data went fine, the second catalog at 150Gb of data didn't succeed and hung up at the updating catalog stage. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 17, 2006 Report Share Posted April 17, 2006 what is your version of Retrospect? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.