Hello.
I've been receiving a high number of backup failures due to the database catalog being locked.
Error EC8F1C50: Cannot create file backup for job: File Backup. Error E4BC0012: An interaction with the catalog's database layer failed unexpectedly: sqlite3_step--5: database is locked.
Details: 0xE4BC0012
Source: Norton Ghost
Once I delete the catalog, it might go a whole day before I have to delete the catalog again.
Is this a permissions issue?
Is this a conflict with some other service possibly running in the background? (I noticed that the program is using some of the VSS services included in Windows.)
If I close all of my programs (inconvenient) when I'm done for the day, (prior to the back-ups running at 3,4,5,& 6am) that sometimes the backup service still fails. I run a few apps that are Java based, and quite a few that are (unfortunately) C++ based using the Microsoft engines.
Is it possibly one of the Microsoft services is not releasing something the database needs?
There is 10gb available on the operating system drive, so there is plenty of room to write the catalog file. I also run defrag every 1-2 weeks (depending on the drive).
I've been following the instructions here:
http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080428103004EN&ln=en_US
Is there a limit to the number of files the sqlite catalog can hold? Just curious because it says "lite" in the name.
The backups work for the moment when I've followed those instructions, but it's becoming more and more difficult to successfully create a back-up job unattended. I'm sure the short corporate answer is to upgrade, but I've been a Ghost user (corporate and private) for a long time and have experienced this particular issue in versions of Ghost prior, so I have no faith in an upgrade at this point in time unless I can be assured the system works in a different way rather than a simple product renaming and reskinning.
I'm trying to determine if there is a habit I can change, or if there is an application I can disable, or something? I typically work 20 hour days, and do not have "time in the day" for leaving the machine alone unattended so it can run a manual backup on important data because a scheduled backup was missed.
Sometimes I have to cancel a job if I'm working really late, then I'll reschedule that backup for the morning. Sometimes it works, sometimes it doesn't. Is cancelling a single job what's corrupting the database?
Thank you for any feedback.
-Chris