Archived - Retrospect: Error Messages (1 of 2)
This article list the following Retrospect error messages and possible solutions.
1) Catalog out of sync
2) Bad StorageSet header
3) Content Unknown
4) Content Damaged
5) Compare Error
6) Error 34 (volume full)
7) Errors 35 and 53 (volume doesn't exist, volume off-line)
8) Error 36 (I/O error)
For more information on Retrospect error messages, see article 13002: "Retrospect: Error Messages (2 of 2)"
1) Catalog out of sync
2) Bad StorageSet header
3) Content Unknown
4) Content Damaged
5) Compare Error
6) Error 34 (volume full)
7) Errors 35 and 53 (volume doesn't exist, volume off-line)
8) Error 36 (I/O error)
For more information on Retrospect error messages, see article 13002: "Retrospect: Error Messages (2 of 2)"
1) Catalog out of sync Error
Each time Retrospect performs a backup to a StorageSet, it updates the information in the Catalog.
* A "Catalog out of sync" error indicates that Retrospect was unable to update the Catalog the last time it copied data to this StorageSet -- possibly because of equipment failure or power failure.
* This error may also be caused by a full disk error (error -34) or by an out of memory error (error -108). (Both of these errors are explained in separate articles in the Tech Info Library.)
What to do:
Repair the Catalog. For instructions, see "Updating a Catalog" on pageā©162 of the Retrospect User's Guide. If updating the Catalog does not eliminate the "Catalog out of sync" error, the Catalog cannot be repaired.
You have three options:
* Perform a Full Backup, resetting the Catalog and erasing the tape.
* Select Catalogs from the Configure icon. Choose the StorageSet and select Media Control. Click Skip, forcing Retrospect to use a new piece of media for the next backup.
* Create a new StorageSet and begin a new backup.
2) Bad StorageSet header Error
Each file in your StorageSet is preceded by a header that contains information such as its name and size. A bad StorageSet header error will appear if Retrospect reads a header that is obviously damaged or invalid.
What to do:
If the error appears immediately while you are recreating a Catalog file, it means you forgot to tell Retrospect that the StorageSet was encrypted. If the error appears during backup or retrieving, it can indicate SCSI communication issues. See "SCSI problems" on page 180 of the Retrospect User's Guide for details.
3) Content Unknown Error
A "Content Unknown" error means that Retrospect can see data on your media, but the data is not recognized as Retrospect-formatted data. For tapes, this usually means that the tape was damaged or used by a different backup program.
4) Content Damaged Error
The "Content Damaged" error message appears if you change the name of a disk or cartridge that is part of a Disk StorageSet.
What to do:
If you want to preserve this data, rename the disk to the original name it was given by Retrospect. The original disk uses the format "1-The StorageSet." If you do not want to save the data and want to use the disk for other purposes, erase the disk using the Erase Disk command from the Special menu in the Finder.
5) Compare Error
A compare error appears if a backup file does not match the file from which it was copied. Retrospect will try to back up the file again during the next backup session.
The following messages in Retrospect Log indicate a compare error:
* File "Home": different modify date/time
* File "My File": didn't compare at data offset 263,078
* File "My File": didn't compare at resource offset 731,429
What to do:
If you know the file was in use at the time the backup occurred, a compare error is usually nothing to worry about. It simply means the file changed between backup and verification. Compare Errors that mention data or resource offsets usually indicate SCSI communication issues. See "SCSI problems" on page 180 of the Retrospect User's Guide for details.
6) Error 34 (volume full)
Error 34 (volume full) means that a volume has run out of free storage space. You will see this error in the following situations:
* If you are restoring more files to a volume than will fit.
Solution: Try restoring fewer files, or restore to a larger volume.
* When Retrospect is updating a StorageSet Catalog during a backup and the volume where the Catalog is located runs out of room.
Solution: Check your hard disk to see if it is full, or close to full.
* If you are backing up to a Macintosh File StorageSet and the destination volume runs out of free space.
Solution: Check the hard disk containing the Catalog file, to see if it is full.
7) Errors 35 and 53 (volume doesn't exist, volume off-line)
The Errors 35 and 53 (volume doesn't exist, volume off-line) mean that Retrospect cannot find a volume when it is time to perform a backup.
What to do:
Make sure the volume is actually connected to the Macintosh and that it is mounted on the Desktop. If it is, click the Immediate icon in the Retrospect Directory, then click View to scan the volume and display the Browser.
8) Error 36 (I/O error)
When an Error 36 (I/O error) is reported by Retrospect, a media issue has occurred on a source volume.
What to do:
Try verifying the media on your source disk using a disk utility or the formatting program that came with your hard drive. If you are using an Apple hard disk, try using the Test command in the Apple HD SC Setup utility or MacCheck (MacCheck is included with Macintosh computers after July 1993, and on the Macintosh Software Utility Update 1.0 disk).
If you have a Power Macintosh with the native version of Retrospect 2.1i installed, and while Retrospect displays a dialog that says "Scanning...." you encounter this error, contact Dantz.
Note: For further information on working with Retrospect and Retrospect A/UX, search the Tech Info Library by "Retrospect" or "Remote."
Each time Retrospect performs a backup to a StorageSet, it updates the information in the Catalog.
* A "Catalog out of sync" error indicates that Retrospect was unable to update the Catalog the last time it copied data to this StorageSet -- possibly because of equipment failure or power failure.
* This error may also be caused by a full disk error (error -34) or by an out of memory error (error -108). (Both of these errors are explained in separate articles in the Tech Info Library.)
What to do:
Repair the Catalog. For instructions, see "Updating a Catalog" on pageā©162 of the Retrospect User's Guide. If updating the Catalog does not eliminate the "Catalog out of sync" error, the Catalog cannot be repaired.
You have three options:
* Perform a Full Backup, resetting the Catalog and erasing the tape.
* Select Catalogs from the Configure icon. Choose the StorageSet and select Media Control. Click Skip, forcing Retrospect to use a new piece of media for the next backup.
* Create a new StorageSet and begin a new backup.
2) Bad StorageSet header Error
Each file in your StorageSet is preceded by a header that contains information such as its name and size. A bad StorageSet header error will appear if Retrospect reads a header that is obviously damaged or invalid.
What to do:
If the error appears immediately while you are recreating a Catalog file, it means you forgot to tell Retrospect that the StorageSet was encrypted. If the error appears during backup or retrieving, it can indicate SCSI communication issues. See "SCSI problems" on page 180 of the Retrospect User's Guide for details.
3) Content Unknown Error
A "Content Unknown" error means that Retrospect can see data on your media, but the data is not recognized as Retrospect-formatted data. For tapes, this usually means that the tape was damaged or used by a different backup program.
4) Content Damaged Error
The "Content Damaged" error message appears if you change the name of a disk or cartridge that is part of a Disk StorageSet.
What to do:
If you want to preserve this data, rename the disk to the original name it was given by Retrospect. The original disk uses the format "1-The StorageSet." If you do not want to save the data and want to use the disk for other purposes, erase the disk using the Erase Disk command from the Special menu in the Finder.
5) Compare Error
A compare error appears if a backup file does not match the file from which it was copied. Retrospect will try to back up the file again during the next backup session.
The following messages in Retrospect Log indicate a compare error:
* File "Home": different modify date/time
* File "My File": didn't compare at data offset 263,078
* File "My File": didn't compare at resource offset 731,429
What to do:
If you know the file was in use at the time the backup occurred, a compare error is usually nothing to worry about. It simply means the file changed between backup and verification. Compare Errors that mention data or resource offsets usually indicate SCSI communication issues. See "SCSI problems" on page 180 of the Retrospect User's Guide for details.
6) Error 34 (volume full)
Error 34 (volume full) means that a volume has run out of free storage space. You will see this error in the following situations:
* If you are restoring more files to a volume than will fit.
Solution: Try restoring fewer files, or restore to a larger volume.
* When Retrospect is updating a StorageSet Catalog during a backup and the volume where the Catalog is located runs out of room.
Solution: Check your hard disk to see if it is full, or close to full.
* If you are backing up to a Macintosh File StorageSet and the destination volume runs out of free space.
Solution: Check the hard disk containing the Catalog file, to see if it is full.
7) Errors 35 and 53 (volume doesn't exist, volume off-line)
The Errors 35 and 53 (volume doesn't exist, volume off-line) mean that Retrospect cannot find a volume when it is time to perform a backup.
What to do:
Make sure the volume is actually connected to the Macintosh and that it is mounted on the Desktop. If it is, click the Immediate icon in the Retrospect Directory, then click View to scan the volume and display the Browser.
8) Error 36 (I/O error)
When an Error 36 (I/O error) is reported by Retrospect, a media issue has occurred on a source volume.
What to do:
Try verifying the media on your source disk using a disk utility or the formatting program that came with your hard drive. If you are using an Apple hard disk, try using the Test command in the Apple HD SC Setup utility or MacCheck (MacCheck is included with Macintosh computers after July 1993, and on the Macintosh Software Utility Update 1.0 disk).
If you have a Power Macintosh with the native version of Retrospect 2.1i installed, and while Retrospect displays a dialog that says "Scanning...." you encounter this error, contact Dantz.
Note: For further information on working with Retrospect and Retrospect A/UX, search the Tech Info Library by "Retrospect" or "Remote."