| Our product is constantly improving so each new version has a number of feature enhancements as well as issues resolved.
For additional information, read the Purchasing and Licensing Frequently Asked Questions. This page covers the most frequently asked questions related to the licensing and purchasing of LogicalDOC products
We spend a lot of time making sure that upgrades are painless however because of the large variety of configurations and environments, issues may occur. We recommend that you comply with the following best practice guidelines to minimize the risk of data loss and interruption of service. |
|
Best Practice Guidelines when Upgrading |
|
- Always read the release notes
- Do not upgrade your production system without first testing the upgrade on a non-production copy. This copy should preferably be on a separate server. If you don’t have a separate server available, make a copy of the system on the same server using different database and http ports
- Always keep a backup copy to roll back to if the upgrade runs into problems. Read instructions on how to backup and restore LogicalDOC
|
Recommended Upgrade Process |
|
- Set up test environment
- Perform a fresh installation of the current version of LogicalDOC
- Delete the default installed database
- Dump your current production database onto the test environment's new database server
- Copy your repository directory to the test environment
- Check that the test environment works
- Download the update package
- Go to http://update.logicaldoc.com and download the proper update package that applies to your version
- Read the files README.txt and INSTALL.txt contained in the archive, that will give you all informations about the upgrade
- Place the update package archive in the updates/ folder of the test environment
- Run upgrade on test environment
- Run the update command in the bin/ directory of the test environment
- Verify that the upgrade completes successfully and that you are able to login
- If the test upgrade fails, please take note of any error messages and contact the LogicalDOC Team for assistance.
- Run upgrade on production environment
- Close off user access to the production environment
- Backup the production environment – make a copy of the LogicalDOC folder and call it *_BAK
- Copy the update package in the production system
- Run the update command of the production environment
- Verify that the upgrade has completed successfully and that you are able to login
- If the upgrade fails for whatever reason, revert back to the *_BAK version and set up another test environment
|
|
|
|
|
|
|
