You probably want to create regular back-ups of your resources (projects, translation memories, term bases, settings, etc.) for disaster recovery. As memoQ stores resources as files, it is fairly easy to create backups by simply copying folders or files. The below instructions let you create backups that you can quickly restore if your resources become corrupted. The backups created this way are not meant for "long term" usage though: trying to restore a backup created in an older version might cause problems.
Before backing up or restoring any files, make sure that memoQ is not running. memoQ might hold some files open or may even be writing into one of them, which might prevent a successful backup or restore.
You need to back up the following folders:
For projects, translation memories, term bases, and filter configurations, the default storage paths can be changed in memoQ under Tools > Options > Appearance, Locations. If you have changed the default paths for any of the above, make a backup of your new paths.
If you are using a server solution, it is also advisable to regularly back up the SQL database that contains information about the users, groups, permissions and projects. By default, it is found in the following folder, which also contains the project folder and some configuration files that you may also want to back up:
The SQL database file and the transaction log are stored under the names memoQServer.mdf and memoQServer_log.ldf. Both are needed for a successful backup and restore. During the server installation you might have changed the path where the server database is stored. If you did change it, make sure that you back up the new path as well. The folder where server project documents are stored can also be changed from the Server Administrator, so if you are not using the default folder, back up the actual project folder as well.
Before the backup or restore operation, you will need to stop the memoQ Server service and the service of the SQL Server instance pertaining to the memoQ Server (in that order). Failure to do so may stop you from successfully finishing the operation, or might even leave the server in an unworkable state. After the backup or restore operation, start the SQL instance service and the memoQ Server service (in that order) again.
Never try to restore a database backup if you have upgraded your server to a newer version since the backup was taken. The database schema often gets modified between versions, and a database created by an older version might not work with the current version of the server. If you need to restore a database that was created in an older version of memoQ Server, you first need to uninstall you current version of memoQ Server, and install the version the database was created in. After this, you can restore the backup of the database, and install the current version. The installer will upgrade the restored database to the current version.
By following the above instructions, your backups might contain the license files of memoQ and/or memoQ Server. However, if there are frequent licensing related changes (e.g. you are using mobile licenses or have aquired new licenses recently), it might not be a good idea to restore earlier versions of your license files when you restore a backup. In this case, do not include the license files in your backup packages. (Or, if they are already backed up, do not restore them.) License files are named LicenseNN.dat (where N is a digit, e.g. License11.dat, License02.dat etc.). They can be found in the following folders:
memoQ:
memoQ Server:
If you have licensing problems after restoring a backup, update your licenses online first. To do this, click Activation (or Server Activation for the server) in the Help menu, and click Update licenses online. If this does not solve the problem, turn to Kilgray support.