Jump to content

Catalog rebuild - three questions:


Recommended Posts

During backup to a file (Workstations A) my HD run out of space:

 

Quote:

+ Normal backup using Default PC BKUP Nightly at 7/7/2003 11:52 AM

To Backup Set Workstations A...

 

- 7/7/2003 11:52:50 AM: Copying Drive C (C:) on X205

7/7/2003 11:52:50 AM: Connected to X205

7/7/2003 11:52:50 AM: No files need to be copied

Catalog File out of sync with Backup Set "Workstations A".

To repair it, use Tools>Repair Catalog>Update existing Catalog File.

Can't save Catalog File, error -1115 (disk full)

7/9/2003 9:58:44 AM: Execution incomplete

Duration: 1 22:05:48 (00:00:51 idle/loading/preparing)

 


 

...and Retrospect froze up...After killing the process and restarting I went on to rebuilding the catalog:

 

 

Quote:

+ Retrospect version 6.0.206

Launched at 7/9/2003 10:04 AM

+ Retrospect Driver Update, version 3.7.105

 

+ Executing Recatalog at 7/9/2003 10:08 AM

To Backup Set Workstations A...

Bad Backup Set header found (0x64685654 at 43,837,015)

7/9/2003 12:24:06 PM: 1 execution errors

Completed: 4 files, 513.8 MB

Performance: 3.7 MB/minute

Duration: 02:15:25

 

 


 

1) What does "bad backup set header found" error mean. How to fix it?

2) Log mentions that it completed 4 files??? 4 files in two hours? Or, perhaps it means something else?

3) Performance is 3.7MB a minute. Is that normal?

 

thanks,

 

Mikee

[Retrospect 6.0 multiserver]

Link to comment
Share on other sites

Bad Backup Set header found (0x64685654 at 43,837,015) means that Retrospect is having trouble reading data from the media, which results in a very slow and incomplete rebuild.

 

If each rebuild attempt shows the error as and identical number (0x64685654 at 43,837,015), that indicates a bad spot on the media.

 

Of the numbers are different then you have a drive or device communicaton problem.

 

http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27863

Link to comment
Share on other sites

Thanks for the link. I doubt that this is the media issue (This HD is used for backup jobs with verification and I'm sure I would see verify errors if there was an issue). Considering that backup job run out of space and froze up could it be that the file on the server is corrupted?

 

Mikee

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...