There are a couple of options for backing up your Concordance Desktop databases. Before backing up your Concordance Desktop database, you need to determine how long the backup process may take, given the size of the database files. The backup process could take many hours, so having a solid estimate helps you plan backup maintenance schedules.
Research the network’s automatic server backups and how it may impact Concordance Desktop database files. Database files automatically backed up in this manner often take longer to restore, therefore, they are probably not a practical method to rely on as your sole source for database copies.
|
Do not perform live backups if you are using backup software that locks files, even briefly. This has been known to cause read/write functions to the database files to fail, and can cause file synchronization or corruption issues. Check with your IT group and/or backup solution provider to verify that no file locking occurs before scheduling any backups on Concordance Desktop files that are in use. Be aware that anti-virus, firewall, and backup software can often interfere with network traffic and the locking of files, and in effect, could cause Concordance Desktop, Concordance Desktop Image, and Concordance Desktop server software to crash. |
It is best practice to use the following methods for routine backup procedures:
•Verify that you are not backing up your databases while they are in use either by tape or by manually making a copy. Any locking of files while users are updating those same files can produce erroneous results. Using snapshots on your data storage devices can reduce these effects because they do not lock the files.
•To create a backup of a Concordance Desktop database, use the Export Wizard provided in Concordance Desktop. Exported databases do not include tag history, redlines, or the imagebase. To retain this data in your back up, you should replicate the database. To include tag history, run the TagSaver.cpl and TagHistoryandStoreIt.cpl. Either way, you are storing a backup of your database files in the event they need to be restored later. To save your redlines and imagebase, backup the .CIB file separately. In lieu of using the wizard, you can backup the whole database folder by copying and pasting the whole folder to another location.
When backing up databases, you should also consider the following:
•If user management is applied at the database level, back up the .sec files
•Back up tags using the TagSaver.cpl and TagHistoryandStoreIt.cpl
•Back up redlines and imagebase by using another backup method to backup the .CIB file.
•Do not forget to copy over your list files, queries, exported user management, and .gat files, etc.
•Verify that your anti-virus does not scan any of the following file types: .trk, .key, .dct, .dir, .fzy, .layout, .sec, .cib
|
Backing up tags may take days for some databases, and loss of tagging information can jeopardize a case review. Please make time to research and test this process so you understand how to best schedule this task regularly. |
