Tools - Database Maintenance

If you receive an error message after you have run a backup that reads as "Error Writing to Local Configuration," you can fix this problem with the database maintenance options. 

The Backup Client keeps a cache copy of its backup history locally. This local copy of the backup history is used during the backup process to reduce line time and speed up the backup process. Should the local cache copy of your backup history become corrupt or lost you will receive the error message "Error Writing to Local Configuration."  Follow the steps below to fix this problem.

• STEP 1 - Download from the Backup Server Now
  Press the Download from the Backup Server Now button to instruct the Backup Client to pull a copy of your backup history from the Backup Server. The Backup Server maintains a duplicate copy of your backup history. This process resynchronizes the Backup Client data with the Backup Server. This process is very quick if you have a high speed connection to the Backup Server.
  
  When this process completes, run the backup set again. If the backup runs successfully, the resynchronization has fixed the problem. If the problem persists, go to Step 2.
   

• STEP 2 - Rebuild Database from Logs Now
  Press the Rebuild Database from Logs Now button to instruct the Backup Client to replay the logs and reconstruct your history. The Backup Client keeps logs that record information about the files that have been backed up and when you perform this type of database maintenance, all of the reconstruction is performed on the local Backup Client. These logs can be used to recreate the backup history. Normally this process is slow and may take hours. Since this method is slow, we normally recommend using the Download from the Backup Server option first.