Fragile catalogs

[Steve3]

Retro 7.6 Multi Server, running on Windows XP.

 

One of my backup sets recently reported "Catalog File out of Sync", so I first took Retro's advice to use Tools>Repair Catalog>Update Existing to fix it.

 

This didn't work.

 

So I went with the Nuclear Option of Tools>Repair Catalog>Recreate from Disks. This ran for 14 hours, then says "Not enough application memory".

 

Twice.

 

How do I provide more application memory? This isn't OS 9, where you could just change memory allocations via Get Info.

 

Besides this damaged catalog, I also have another set which says it can't be groomed and needs to be rebuilt. This is a frequent problem, demanding that I rebuild catalogs. What can I do to make these stable? All the time I spend rebuilding them is time backups aren't happening.

 

Thanks,

Steve.

[Mayoff]

How much RAM do you have? How much free space on the C: disk?

 

You might have a corrupt .rdb file which is causing Retrospect to get false out of memory error.

[Steve3]

1 gig RAM, 25gigs open on C:

 

How can I keep .rdb files from being corrupted?

[Lennart_T]

How can I keep .rdb files from being corrupted?

Basically by letting Retrospect always "exit gracefully".

I.e. Use an UPS, never end the task in task manager etc

[Steve3]

This machine is dedicated to Retrospect- the only time it's turned off is to install Windows Updates. Any time the application is quit, it's been under proper controlled circumstances- except for when it throws an error and explodes on it's own.