Ever growing Backup File / Corrupted catalog backup.@db

Like many others in this forum I have the issue of an ever growing backup file, where only parts of the file are accessible (more files are in the backup file than are shown under the Norton interface) . I have discovered the issue coming from the following:

 

For some reasons - maybe when the automatic backup process is unexpectedly interrupted - the catalog file backup.@db gets emptied/corrupted and the whole backup starts all over again because Norton thinks there is nothing backuped up so far. While the previous backup up files are still there, they cannot be accessed and Norton is just adding the same files again.

 

This is a major issue of the software and makes the otherwise good functionality  useless since after a while the catalog files gets corrupted (this happens for some reason after a couple of days or weeks). Obviously this a software mistake and should not happen.

 

Is there a feasible solution to this and please not everytime using ARESTORE to recreate the catalog file which would take days.