Jump to content

Internal Consistency


Recommended Posts

Quote:

Using 6.1.x Retrospect Workgroup on my Mac OS X server 10.3.9

 


 

The "x" matters.

 

So does the version of the RDU that's loading with the program.

 

So does the model of Macintosh that's running Mac OS X Server.

 

So does the Type of Backup Set you're using.

 

So does the backup media you're writing to.

 

No one can make (helpful) suggestions without having enough information to go on.

 

Dave

Link to comment
Share on other sites

Thanks Dave I wasn't sure what all to offer. (Bruce) Backups were running fine and the error occured so I updated the RDU to the latest and it still persists. The exact error is elem-c.923 which I can't find in the online resources. I found elem-c but not 923.

 

The "x" matters.

 

So does the version of the RDU that's loading with the program.

6.1.126 Workgroup with RDU 6.1.4.103

 

 

So does the model of Macintosh that's running Mac OS X Server.

Dual G5 1.8 Ghz 768 MB RAM running OS X 10.3.9 Unlimited

 

So does the Type of Backup Set you're using.

Daily Rotation all data to external FW Drives

 

So does the backup media you're writing to.

Lacie External FireWire drives

 

No one can make (helpful) suggestions without having enough information to go on.

 

Dave

Link to comment
Share on other sites

This thread seems a goot place to post my similar issue:

 

800 MHz PowerMac G4 / 768MB Ram / 2 internal drives - one boot, one data

2 external LaCie 500GB (Non-Raid) drives - A and B backups, only one connected at a time

Mac OS X Server 10.4.2

Retrospect 6.1.126

Driver Access 1.0.107

Driver Update 6.1.4.103

 

Backup type: File, not secure

There are 2 backup scripts and 2 backup sets - A and B - each one runs for a week, recycling at the beginning of the week and then "Normal" for the remainder of the week. The backups are set to backup both drives, with compression. Users quit retrospect, unmount backup drive, mount alternate backup drive and relaunch retrospect once a week.

 

When manually executing a backup or manually running the backup script, the backup completes successfully. When the scripts run from the schedule, Restrospect throws the error:

Internal Consistency Check Failed: Assertion check at "elem.c-928"

during backup. It will throw the error sometimes when it's backing up the first volume in the list and sometimes the second. Re-ordering the volumes in the list does not change the behavior.

 

I have completely re-done the backup sets and the scripts, replacing the old ones and running a fresh backup to the new set with the new script.

 

I'm looking for suggestions. Any help would be appreciated.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...