Whether you are updating Concordance Desktop, or third-party products on the server that hosts the Concordance Desktop server, you need to back up your FYI.db files first.
Often administrators run patches on their servers and reboot without stopping and starting the Concordance Desktop services and backing up the FYI.db file. Doing so is a common cause for file corruption of the FYI.db file – the very file you do not want to rebuild. If you reboot the server while the Concordance Desktop services are still running, it appears as a server crash to the services.
Updating Guidelines:
•Back up the Concordance Desktop server FYI.db File - Always back up your FYI.db file before performing any updates to any products or services running on the server/computer that hosts the Concordance Desktop server.
For more information about backups, see About backups and data recovery.
•Concordance Desktop earlier versions - Due to the new simplified installation and the new database format, there is no upgrade process from a previous version of Concordance Desktop, Concordance Desktop Viewer and FYI server to Concordance Desktop. If you want to open existing databases in Concordance Desktop, you need to migrate those databases to the new format. Once migrated, the databases can no longer be opened in Concordance, they can only be opened in Concordance Desktop. Therefore, we recommend backing up your databases prior to migrating them to Concordance Desktop. Please see Migrating databases for more details.
•Tagging - Before migrating existing Concordance 10.x databases to Concordance Desktop, ensure that any legacy issues with tagging are resolved in the databases, or you will import those issues into Concordance Desktop. Once you migrate a database for use in Concordance Desktop, the database can no longer be opened in the previous version of Concordance, Concordance Desktop Viewer or Concordance Desktop server.
|
Always back up the Concordance Desktop server FYI.db file before performing updates to the server/computer, or updates to any third-party products on the server that hosts the Concordance Desktop server. You need to shut down services for Concordance Desktop while you perform updates, otherwise you risk corruption to the FYI.db file, as the Concordance Desktop server reads a server reboot as a system crash. |
Moving Existing Concordance Desktop Databases to Other Servers
If you need to move existing Concordance Desktop databases to another server, and need to ensure that all path information for those databases and imagebases are preserved, we recommend that you hire a consultant.
You can consider creating an alias in your host file on your server, such as \\myserver.1\. This would then redirect all paths to \\myserver.2\. See your local network administrator for more information concerning your host files.
Moving an Existing Concordance 10.x Database to Another Folder
If you plan to migrate an existing Concordance 10.x database to Concordance Desktop, but also want to move it to another folder, first move the database to its new location and open it in Concordance 10.x. Doing so ensures that the notes DCB is properly linked to the parent DCB. Once these two steps are done, you can migrate the Concordance 10.x database to Concordance Desktop.
Moving Imagebases
If you receive an error message stating that Concordance Desktop is unable to open the corresponding document, you need to edit your folder paths. The folder path listed in the message box is the path stored in the Concordance Desktop imagebase. That path points to where your files are located, so the viewer can open and display the document. You need to change the path to the directory location where your documents actually reside. See, Renaming file paths and folders.
|
Use caution when resetting folder paths as there is no undo function and changes are permanent. We recommend backing up the .cib file before performing this process or other imagebase management tasks. |