Server Migration - Revision history

Car031: /* Step 1: Unbind the license from the old system */

2025-09-19T06:33:15Z

Step 1: Unbind the license from the old system

← Older revision		Revision as of 06:33, 19 September 2025
Line 14:		Line 14:

	== Step 1: Unbind the license from the old system ==		== Step 1: Unbind the license from the old system ==
	In general your license is bound to a specific hardware, so you have to unbind it before being able to activate the same in another server.		In general, your license is bound to a specific hardware, so you have to unbind it before being able to activate the same in another server.
	Please follow the license unbinding guide here: https://docs.logicaldoc.com/en/license-management/license~~-unbind~~		Please follow the license unbinding guide here: https://docs.logicaldoc.com/en/license-management/hardware-bound-license

	== Step 2: Install a fresh LogicalDOC in the new server ==		== Step 2: Install a fresh LogicalDOC in the new server ==

Car031: /* Step 5: Migrate the full-text index */

2025-01-16T07:05:49Z

Step 5: Migrate the full-text index

← Older revision		Revision as of 07:05, 16 January 2025
Line 40:		Line 40:
	This repository can be big so the time to transfer all the contents to the new server may require a lot of time.		This repository can be big so the time to transfer all the contents to the new server may require a lot of time.

	== Step 5: Migrate the full-text index ==		== Step 5: Migrate the full-text index (optional, not strictly required) ==
	* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/OLDPATH'''		* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/OLDPATH'''
	* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/NEWPATH'''		* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/NEWPATH'''

Car031 at 08:00, 12 April 2021

2021-04-12T08:00:08Z

← Older revision		Revision as of 08:00, 12 April 2021
Line 24:		Line 24:
	*After the end of installation, stop LogicaDOC.		*After the end of installation, stop LogicaDOC.

	== Step 2: Migrate the configuration files ==		== Step 3: Migrate the configuration files ==
	* Copy all the files in '''/OLDLDOC'''/conf into '''/NEWLDOC'''/conf		* Copy all the files in '''/OLDLDOC'''/conf into '''/NEWLDOC'''/conf
	* Open the file '''/NEWLDOC'''/conf/build.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''		* Open the file '''/NEWLDOC'''/conf/build.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''
Line 33:		Line 33:
	** Locate the property '''jdbc.password''' and put the new database password		** Locate the property '''jdbc.password''' and put the new database password

	== Step 3: Migrate the documents repository ==		== Step 4: Migrate the documents repository ==
	* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''store.1.dir''', it references a path we could call '''/OLDPATH'''		* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''store.1.dir''', it references a path we could call '''/OLDPATH'''
	* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''store.1.dir''', it references a path we could call '''/NEWPATH'''		* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''store.1.dir''', it references a path we could call '''/NEWPATH'''
Line 40:		Line 40:
	This repository can be big so the time to transfer all the contents to the new server may require a lot of time.		This repository can be big so the time to transfer all the contents to the new server may require a lot of time.

	== Step 4: Migrate the full-text index ==		== Step 5: Migrate the full-text index ==
	* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/OLDPATH'''		* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/OLDPATH'''
	* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/NEWPATH'''		* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''index.dir''', it references a path we could call '''/NEWPATH'''
	* Copy all the contents of '''/OLDPATH''' to '''/NEWPATH'''		* Copy all the contents of '''/OLDPATH''' to '''/NEWPATH'''

	== Step 5: Migrate the plugins configurations ==		== Step 6: Migrate the plugins configurations ==
	* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''conf.plugindir''', it references a path we could call '''/OLDPATH'''		* Open the file '''/OLDLDOC'''/conf/context.properties and locate the property '''conf.plugindir''', it references a path we could call '''/OLDPATH'''
	* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''conf.plugindir''', it references a path we could call '''/NEWPATH'''		* Open the file '''/NEWLDOC'''/conf/context.properties and locate the property '''conf.plugindir''', it references a path we could call '''/NEWPATH'''
	* Copy all the contents of '''/OLDPATH''' to '''/NEWPATH'''		* Copy all the contents of '''/OLDPATH''' to '''/NEWPATH'''

	== Step 6: Migrate the database ==		== Step 7: Migrate the database ==
	* Make a dump file of the old database, if you are using MySQL, execute this command:		* Make a dump file of the old database, if you are using MySQL, execute this command:
	$ mysqldump -u '''username''' -p'''password''' --add-drop-database '''logicaldoc''' > logicaldoc.sql		$ mysqldump -u '''username''' -p'''password''' --add-drop-database '''logicaldoc''' > logicaldoc.sql
Line 56:		Line 56:
	$ mysql -u '''username''' -p'''password''' '''logicaldoc''' < logicaldoc.sql		$ mysql -u '''username''' -p'''password''' '''logicaldoc''' < logicaldoc.sql

	== Step 7: Start LogicalDOC ==		== Step 8: Start LogicalDOC ==
	* Start LogicalDOC in the new server and check that all is working properly		* Start LogicalDOC in the new server and check that all is working properly

	[[Category: Migration]]		[[Category: Migration]]

Car031: /* Step 1: Install a fresh LogicalDOC in the new server */

2021-04-12T07:59:07Z

Step 1: Install a fresh LogicalDOC in the new server

← Older revision		Revision as of 07:59, 12 April 2021
Line 13:		Line 13:
	*'''/NEWLDOC''': represents the installation path of the migrated installation		*'''/NEWLDOC''': represents the installation path of the migrated installation

	== Step 1: Install a fresh LogicalDOC in the new server ==		== Step 1: Unbind the license from the old system ==
			In general your license is bound to a specific hardware, so you have to unbind it before being able to activate the same in another server.
			Please follow the license unbinding guide here: https://docs.logicaldoc.com/en/license-management/license-unbind

			== Step 2: Install a fresh LogicalDOC in the new server ==
	Preparing this new installation, make sure to use the same database engine you used in the old system (eg: MySQL).<br/>		Preparing this new installation, make sure to use the same database engine you used in the old system (eg: MySQL).<br/>
	<u>It is really important to install the same version of LogicalDOC as the old system.</u>		<u>It is really important to install the same version of LogicalDOC as the old system.</u>

Car031: /* Step 7: Start LogicalDOC */

2021-01-26T07:20:20Z

Step 7: Start LogicalDOC

← Older revision		Revision as of 07:20, 26 January 2021
Line 53:		Line 53:

	== Step 7: Start LogicalDOC ==		== Step 7: Start LogicalDOC ==
	* Start LogicalDOC in the new server and ~~chack~~ that all is working properly		* Start LogicalDOC in the new server and check that all is working properly

	[[Category: Migration]]		[[Category: Migration]]

Car031: /* Step 2: Migrate the configuration files */

2021-01-26T07:19:50Z

Step 2: Migrate the configuration files

← Older revision		Revision as of 07:19, 26 January 2021
Line 24:		Line 24:
	* Open the file '''/NEWLDOC'''/conf/build.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''		* Open the file '''/NEWLDOC'''/conf/build.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''
	* Open the file '''/NEWLDOC'''/conf/context.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''		* Open the file '''/NEWLDOC'''/conf/context.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''
	* ~~Reconfigurethe~~ connection to the new database, open the file '''/NEWLDOC'''/conf/context.properties and follow these instrucions:		* Reconfigure the connection to the new database, open the file '''/NEWLDOC'''/conf/context.properties and follow these instrucions:
	** Locate the property '''jdbc.url''' and put the connection URL to your new database		** Locate the property '''jdbc.url''' and put the connection URL to your new database
	** Locate the property '''jdbc.username''' and put the new database username		** Locate the property '''jdbc.username''' and put the new database username

Car031: /* Step 2: Migrate the configuration files */

2017-09-28T14:16:29Z

Step 2: Migrate the configuration files

← Older revision		Revision as of 14:16, 28 September 2017
Line 22:		Line 22:
	== Step 2: Migrate the configuration files ==		== Step 2: Migrate the configuration files ==
	* Copy all the files in '''/OLDLDOC'''/conf into '''/NEWLDOC'''/conf		* Copy all the files in '''/OLDLDOC'''/conf into '''/NEWLDOC'''/conf
			* Open the file '''/NEWLDOC'''/conf/build.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''
	* Open the file '''/NEWLDOC'''/conf/context.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''		* Open the file '''/NEWLDOC'''/conf/context.properties and replace all the occurrencies of '''/OLDLDOC''' with '''/NEWLDOC'''
	* Reconfigurethe connection to the new database, open the file '''/NEWLDOC'''/conf/context.properties and follow these instrucions:		* Reconfigurethe connection to the new database, open the file '''/NEWLDOC'''/conf/context.properties and follow these instrucions:

Car031 at 16:18, 18 July 2017

2017-07-18T16:18:55Z

← Older revision		Revision as of 16:18, 18 July 2017
Line 3:		Line 3:
	Sometimes you want to migrate your running installation to another server. This How-To describe a plan to migrate a LogicalDOC installation o another machine, please note that this activity is delicate and may lead to data loss.		Sometimes you want to migrate your running installation to another server. This How-To describe a plan to migrate a LogicalDOC installation o another machine, please note that this activity is delicate and may lead to data loss.

	{{Advice\|This guide refers to a basic single-server deployment scenario. <b><u>Please be aware that this procedure is not coverded by the standard support contract</u>.</b> <u>In case something goes wrong during the migration process, the support team cannot offer any help</u>.<br/> In case you want this delicate matter to be handled professionally, please write to sales@logicaldoc.com for a quote.}}		{{Advice\|This guide refers to a basic single-server deployment scenario. <b><u>Please be aware that this procedure is not coverded by the standard support contract</u>.</b> <u>In case something goes wrong during the migration process, the support team cannot offer any help and LogicalDOC is not liable for any data loss</u>.<br/> In case you want this delicate matter to be handled professionally, please write to sales@logicaldoc.com for a quote.}}

	== Assumptions ==		== Assumptions ==

Car031 at 16:18, 18 July 2017

2017-07-18T16:18:00Z

← Older revision		Revision as of 16:18, 18 July 2017
Line 3:		Line 3:
	Sometimes you want to migrate your running installation to another server. This How-To describe a plan to migrate a LogicalDOC installation o another machine, please note that this activity is delicate and may lead to data loss.		Sometimes you want to migrate your running installation to another server. This How-To describe a plan to migrate a LogicalDOC installation o another machine, please note that this activity is delicate and may lead to data loss.

	{{Advice\|This guide refers to a basic single-server deployment scenario. <u><b>~~This~~ procedure is not coverded by the standard support contract.</b></u> <u>In case something goes wrong during the migration process, the support team cannot offer any help</u>.<br/> In case you want this delicate matter to be handled professionally, please write to sales@logicaldoc.com for a quote.}}		{{Advice\|This guide refers to a basic single-server deployment scenario. <b><u>Please be aware that this procedure is not coverded by the standard support contract</u>.</b> <u>In case something goes wrong during the migration process, the support team cannot offer any help</u>.<br/> In case you want this delicate matter to be handled professionally, please write to sales@logicaldoc.com for a quote.}}

	== Assumptions ==		== Assumptions ==

Car031 at 16:17, 18 July 2017

2017-07-18T16:17:11Z

← Older revision		Revision as of 16:17, 18 July 2017
Line 3:		Line 3:
	Sometimes you want to migrate your running installation to another server. This How-To describe a plan to migrate a LogicalDOC installation o another machine, please note that this activity is delicate and may lead to data loss.		Sometimes you want to migrate your running installation to another server. This How-To describe a plan to migrate a LogicalDOC installation o another machine, please note that this activity is delicate and may lead to data loss.

	{{Advice\|This guide refers to a basic single-server deployment scenario. This procedure is not coverded by the standard support contract. In case something goes wrong during the migration process, the support team cannot offer any help.<br/> In case you want this delicate matter to be handled professionally, please write to sales@logicaldoc.com for a quote.}}		{{Advice\|This guide refers to a basic single-server deployment scenario. <u><b>This procedure is not coverded by the standard support contract.</b></u> <u>In case something goes wrong during the migration process, the support team cannot offer any help</u>.<br/> In case you want this delicate matter to be handled professionally, please write to sales@logicaldoc.com for a quote.}}

	== Assumptions ==		== Assumptions ==