Jump to content

Auto Quit Problem


ricaruso

Recommended Posts

We are having a problem with Retrospect Quitting automatically after a scheduled Backup. It finishes the entire backup and then it stops with an error message “Execution Terminated Unexpectedly, possibly due to a power failure or system crash.”

 

It appears this happens when writing to the History Log, since it gets created, but nothing is logged (i.e. all 0’s).

 

OS = Win XP Pro

 

Below is the Content of the Session Log:

 

+ Retrospect version 6.5.336

Automatically launched at 1/11/2005 12:35 PM

+ Retrospect Driver Update, version 4.5.101

+ Recycle backup using Monday-Friday at 1/11/2005 12:35 PM

To Backup Set cd-rw set...

1/11/2005 12:35:08 PM: Recycle backup: The Backup Set was reset

 

- 1/11/2005 12:35:08 PM: Copying Archive on Drive C (C:)

1/11/2005 12:36:59 PM: Snapshot stored, 12 KB

1/11/2005 12:37:07 PM: Comparing Archive on Drive C (C:)

1/11/2005 12:37:13 PM: Execution completed successfully

Completed: 47 files, 311 KB

Performance: 1.6 MB/minute (1.0 copy, 4.5 compare)

Duration: 00:02:04 (00:01:41 idle/loading/preparing)

 

- 1/11/2005 12:37:13 PM: Copying Dbfs on Drive C (C:)

1/11/2005 12:38:05 PM: Snapshot stored, 33 KB

1/11/2005 12:38:13 PM: Comparing Dbfs on Drive C (C:)

1/11/2005 12:38:34 PM: Execution completed successfully

Completed: 177 files, 24.8 MB

Performance: 42.9 MB/minute (30.2 copy, 78.0 compare)

Duration: 00:01:20 (00:00:10 idle/loading/preparing)

 

- 1/11/2005 12:38:34 PM: Copying Intuit on Drive C (C:)

1/11/2005 12:47:07 PM: Snapshot stored, 711 KB

1/11/2005 12:47:17 PM: Comparing Intuit on Drive C (C:)

1/11/2005 12:50:19 PM: Execution completed successfully

Completed: 3209 files, 287.2 MB

Performance: 50.2 MB/minute (34.1 copy, 95.7 compare)

Duration: 00:11:44 (00:00:18 idle/loading/preparing)

 

- 1/11/2005 12:50:19 PM: Copying OldDocs on Drive C (C:)

1/11/2005 12:50:46 PM: Snapshot stored, 86 KB

1/11/2005 12:50:56 PM: Comparing OldDocs on Drive C (C:)

1/11/2005 12:51:09 PM: Execution completed successfully

Completed: 461 files, 6,318 KB

Performance: 20.5 MB/minute (15.4 copy, 33.6 compare)

Duration: 00:00:49 (00:00:12 idle/loading/preparing)

 

- 1/11/2005 12:51:09 PM: Copying Shared Docs on Drive C (C:)

1/11/2005 12:51:48 PM: Snapshot stored, 120 KB

1/11/2005 12:51:58 PM: Comparing Shared Docs on Drive C (C:)

1/11/2005 12:52:15 PM: Execution completed successfully

Completed: 284 files, 9,310 KB

Performance: 21.3 MB/minute (15.1 copy, 36.3 compare)

Duration: 00:01:06 (00:00:13 idle/loading/preparing)

 

- 1/11/2005 12:52:15 PM: Copying TI_QBac on Drive C (C:)

1/11/2005 12:53:05 PM: Snapshot stored, 32 KB

1/11/2005 12:53:15 PM: Comparing TI_QBac on Drive C (C:)

1/11/2005 12:53:36 PM: Execution completed successfully

Completed: 120 files, 20.6 MB

Performance: 37.2 MB/minute (26.1 copy, 64.7 compare)

Duration: 00:01:20 (00:00:13 idle/loading/preparing)

 

1/11/2005 12:53:36 PM: Execution completed successfully

Total performance: 44.7 MB/minute

Total duration: 00:18:27 (00:02:55 idle/loading/preparing)

Link to comment
Share on other sites

Thanks for the reply.

 

Yes, all the backups are created and it seems to “crash” when it is updating the History File. We are using a CD Burner factory installed from DELL (Dimension 2400) with CD-RW Disks.

 

Retrospect has been working fine for the past 3+ months. I’m not sure why it’s crashing now, but I’ll update it to 6.5.350 and see if that does the trick.

 

Could I have a corrupted Retrospect data file?

Link to comment
Share on other sites

Strange thing is I called my client and she said that Retrospect has worked fine the last two days and I have yet to install the update 6.5.350. Would a corrupt preference file cause it to fail each time?

 

Nate, you've been a big help. Thank you very much for your time.

Link to comment
Share on other sites

Hi

 

Preference files are written to and rewritten often. If one portion of the file becomes corrupt it may "fix itself" by rewriting correct data over the corrupt section. That is at least possible although I don't know how often it occurs.

 

Corrupt preferences can also cause unpredictable behavior in general. The update won't hurt and we'll need to apply it to keep working on this anyway.

 

Thanks

Nate

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...