Jump to content
Sign in to follow this  
Richy_Boy

Retrospect 7.7 (latest) crashing -1098

Recommended Posts

Well, I've taken a search through the forum and there seems to be a number of things which throw this error.

 

I came in this morning to find RS crashed (missing the weekend backup). Since then I launched it again and it kicked off all the missed backups as it should, yet after a while it crashed again.

 

Loaded it up again and it crashed within 2-3 minutes.

 

Here's a screen shot...

 

6719f797.png

 

I have rebooted the server now in the hope there's some memory leak which is causing this issue - it's a touch annoying when I have backups to get done!

 

Has anyone seen this and have any suggestions?

 

Rich

Edited by Guest

Share this post


Link to post
Share on other sites

More times than you can imagine - although not this time. I believe the problem is related to a corrupt config file, after initially thinking it was some of my catalog files.

 

Having rebuilt a couple of suspected catalog files (which took 4 hours) it's still doing it, although I have just found if I disable the Proactive backups from running everything is fine!

 

Looks like I'll be deleting these scripts and rebuilding them then!

 

EMC/RETROSPECT PLEASE stop your product from corrupting these config files... it's been happening for YEARS now.

 

Rich

Share this post


Link to post
Share on other sites

Could one of backup sets have backed up the corrupt file and thus after re-installing the problem returns because of that corrupt file. I would try a complete uninstall including catalogs and starting from scratch. I know it is a pain but it might solve the problem. I also suggest skipping the program files folders for backups and see if the problem returns.

Edited by Guest

Share this post


Link to post
Share on other sites

Hi Daniels, when Retrospect repeatedly crashes, in the vast majority of cases it's down to the configuration file getting corrupt. i.e config76.dat /.bak.

 

Having identified it was the proactive backups causing this crash I assumed that by removing the proactive scripts and then exiting Retrospect a new config file would be written (without the corrupt data).

 

As luck owuld have it, this is exactly what happened, and as proactive scripts are pretty straight forward here (i.e. all laptops, all desktop and a special PST scripts) then it probably took an hour or so to get back up and running.

 

Thanks for the help...

 

Rich

Share this post


Link to post
Share on other sites

It sounds like you have solved the problem but it sounds like something you want to report to Retrospect as a bug so they can fix it.

Share this post


Link to post
Share on other sites

Hi, they know about their configuraton file corrupting, which is why they changed the product to create a duplicate copy i.e. config76.bak.

 

If you machine crashes in a big way and corrupts config76.dat then you can rename config76.bak to .dat and launch Retrospect, which will then generate a new .bak file if it launches OK.

 

Most people who have been using Retrospect backup these files religiously as it saves you hours of rebuilding your configuration!

 

Rich

Share this post


Link to post
Share on other sites

If can just rename the .bak file to restore your preferences then I do not why I was told to delete both files when my .dat file gets corrupted. Knowing I only need to delete the .dat to restore is very useful information.

Is it possible for the .bak to get corrupt as well?

Edited by Guest

Share this post


Link to post
Share on other sites
If can just rename the .bak file to restore your preferences then I do not why I was told to delete both files when my .dat file gets corrupted. Knowing I only need to delete the .dat to restore is very useful information.

Is it possible for the .bak to get corrupt as well?

Yes. The .bak config file is just a renamed .dat config file. If the .dat file is corrupt and Retrospect creates a new .dat file, then the .bak file (renamed corrupt .dat file) will be corrupt.

 

Basically, you get one chance to figure out that the settings are corrupt.

 

There are two ways to recover.

 

(1) start over (new .dat and .bak file), re-enter license information, use that minimally-configured Retrospect to restore a good config file from your backups (from before it became corrupt); or

 

(2) if you are separately saving the config files, whether by copying them off, or whatever, then restore one of those.

 

This corruption of config files has been occurring for years and years on both the Mac and Windows version, and the programmers haven't seemed to be able to figure out the cause.

 

Long-time Retrospect users have learned to just periodically save away copies of the config file.

 

Russ

Share this post


Link to post
Share on other sites

Every morning I follow up my backups from the night before by backing up the whole folder where the config file is stored. Simple dupe over to another pc. I also dupe over all my catalog files to this pc, then backup that all up to a thumb drive. Has saved me several times when both the config.dat and config.bak have gotten corrupted at the same time.

Share this post


Link to post
Share on other sites

Yeah, I'm seeing it here as well (7.7.325 w/7.7.3.102). I called into TS, they had me use my 7.6 config file and re-serialize. Worked for a day or so..

 

I remember WAY back(and I said this to the TS agent) the fix was to start from scratch and recreate all your scripts. I had to do this once, never again..

 

-g

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×