Error Message

The following errors may be seen in the console windows when running option 1: Backup Appliance in the Clearwell Utility.  This is an example from version 10.1.0.

backup-db:
     [echo] Backing up esadb databases to //EDP-CS/Clw_emea/eDP-App3/MyBackup
    [mkdir] Created dir: \\\\\
[dbbackuprestoreprop] Checking fragmentation of 7 cases
     [echo] Caught error in backup-db-ft-internal
 [cwdelete] Deleting: \\\\\
 [cwdelete]   counts: 51 bytes in 1 dir(s) and 1 file(s)

BUILD FAILED
D:\CW\V101\build.xml:2228: The following error occurred while executing this line:
D:\CW\V101\build\build-schema.xml:1153: The following error occurred while executing this line:
D:\CW\V101\build\build-schema.xml:1205: The following error occurred while executing this line:
D:\CW\V101\build\build-schema.xml:1404: cannot set db catalog:esadb_lds_case_adaoczzjg6

OR

D:\CW\V101\build\build-schema.xml:1376: unable to determine version number for esa_lds_case_adaoczzjg6

Total Time: ## seconds

ANT COMMAND DONE

Error "cannot set db catalog":   

On the MySQL server there is a database called "mysql".  In the "mysql" database is a table called "db".  The term 'db catalog' references the 'db' table in the 'mysql' database. Which catalogs all databases within your MySql environment.  The error means the backup process is  trying to access a database that has no record in this db catalog table. 

Error "unable to determine version number":  

At the beginning of the Appliance Backup process, eDiscovery enumerates all database folders in the MySQLData\data folder as input for the backup process.  This error indicates that a database folder may be present in MySQLData\data, but incomplete.

1.  From File Explorer, go to D:\MySQLData\data and list out all the files/folders in that location to a file.  
     A command can be run from that folder via the command prompt. Example: 
    D:\MySQLData\data:\>dir /b > DirectoryContents.txt
2.  Login to MySQL using: mysql -uroot -p********     --Replace ******** with the actual password.
3. Get the list of databases using the command: show databases;
4. Copy the list to a notepad and save the list as MySQL_Databases.txt, then compare it to the DirectoryContents.txt to identify the missing databases.
5. From the example above, the database in question is esa_lds_case_adaoczzjg6
6. Run query: use esa_lds_case_adaoczzjg6;
7. Run query:show tables;     Note: If there are only 1-2 tables listed, it means the case is not valid and can be deleted from eDiscovery/Clearwell system.
8. If there are many tables listed, please contact Support for more troubleshooting.

To delete the database:
1. Stop CW services using the CW Utility #3.
2. From MySQL, run the command to the list of databases again: show databases; 
3. Run query: drop database [database_name];     --Replace the database_name with the actual database name. In this example, the database is called esa_lds_case_adaoczzjg6
4. Confirm the database has been deleted by running the query: show databases;
5. Confirm the database folder also has been deleted from File Explorer as well (typically in the D:\MySQLData\data).
6. Restart CW services using the CW Utility #4.
7. Run the Appliance Backup again.
8. If another database reports the same error, the same process needs to be taken to delete the next database until all databases in question have been deleted.