Jump to content

config65.dat file size


drugh

Recommended Posts

Running Retrospect 6.5 Multi-Server on Windows 2000, backing up a number of servers, we have seen the config65.dat/.bak files grow to 475MB each. Anybody have any ideas as to why these are so huge? They are causing us problems, since they consume nearly 1GB of space on the C drive, and backups are failing with disk full messages. I have moved the catalog files off of C, but why are these config files so large???

Link to comment
Share on other sites

Hi

 

This is definitely not normal. Can you tell if they are growing day by day? Did you do a clean install of Retrospect or did you import older versions of preference files? Do you have a lot of clients, volumes, selectors, scripts etc.?

 

Nate

Link to comment
Share on other sites

They are growing day-by-day, now up to 529MB, and increase of ~55MB since the last post 6 days ago. This was a new installation of 6.5.336. There are 10 clients, only "stock" selectors, 3 backup scripts.

 

It's been suggested that we just delete these files and start over, but we would like if at all possible to avoid having to reconfigure everything from scratch.

Link to comment
Share on other sites

I have found the answer. The History tab of the Activity Monitor holds the list of executed backup jobs. This list is stored as part of the config.dat file, along with the Operations Log for EACH of these jobs. Several jobs contained many errors, and that combined with nearly 4 months of history created the large config.dat file. I deleted some of the larger entries, and have now shrunk the file (and its .bak version) down to a much more manageable size.

 

Why the Dantz tech I spoke with couldn't tell me this is most disappointing......

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...