07-20-2012 05:45 AM
07-20-2012 09:32 AM
That error means one of the files the backup needs to run is not located on the backend. Generally its the result of a prior failed backup. The @DB files are catalog files that contain the roadmap of what is being backed up.
How long has that error been surfacing?
07-20-2012 09:53 AM
Thanks for the reply! It started occuring towards the end of June, and every day since. I have tried uninstalling and re-installing the software but the error continues. Is there some temp files I need to remove so the software will make a new version?
07-20-2012 10:52 AM
Don't remove anything at the moment. Send me a private message containing the email address you use to login to the service. Also include a link to this forum discussion so I have a point of reference.
What I'm going to do is have the set purged server side instead and then have you initiate a backup. It's likely removing it from your side is not properly completing. This will effectively act the same as if you went through the steps to remove the computer without the headache of having to set everything up again.