Backup and Restore - Revision history

Vmurrell: /* Creating a Backup */

2023-10-02T16:20:31Z

‎Creating a Backup

Vmurrell at 12:35, 18 July 2023

2023-07-18T12:35:53Z

Plazarou: /* Troubleshooting */

2023-03-27T15:09:58Z

‎Troubleshooting

Plazarou: /* Can not restore from backup - the database table must be empty */

2023-03-27T15:00:26Z

‎Can not restore from backup - the database table must be empty

Plazarou: /* Can not restore from backup - the 'XXX' database table must be empty */

2023-03-27T15:00:16Z

‎Can not restore from backup - the 'XXX' database table must be empty

Plazarou at 14:59, 27 March 2023

2023-03-27T14:59:20Z

Plazarou: /* Parameters */

2022-11-09T17:52:15Z

‎Parameters

Vmurrell at 09:15, 3 November 2022

2022-11-03T09:15:30Z

Mnelson: /* Overview */

2022-09-26T10:50:23Z

‎Overview

Mnelson: /* Overview */

2022-09-26T10:45:42Z

‎Overview

@@ Line 6: / Line 6: @@
 = Creating a Backup =
-The backup process requires the FMRCL Command Line Application, which can be downloaded from the tools page:
+The backup process requires the FMRCL Command Line Application, which can be downloaded from https://sdmxio.s3.eu-west-2.amazonaws.com/FMRCL/fmr-cl-1.0.0.zip. '''''Note:''''' clicking this link will download a zip file.
 The files should not be placed in the webapps folder of the Tomcat.

← Older revision		Revision as of 12:35, 18 July 2023
Line 1:		Line 1:
		+	[[Category:How_To V11]]
	@See [[Restore_Web_Service\|Restore Web Service]]		@See [[Restore_Web_Service\|Restore Web Service]]
	= Overview =		= Overview =

← Older revision		Revision as of 15:09, 27 March 2023
Line 62:		Line 62:
	== Can not restore from backup - the 'table name' database table must be empty ==		== Can not restore from backup - the 'table name' database table must be empty ==
	The above error is returned (where 'table name' wil be replaced with the specific name of a table e.g. sdmx_transaction ) if attempting to restore against a database that already has transactions (structural metadata) within it. Check that you have specified the correct database (on step 1 of the wizard) and if necessary, terminate the Registry, clear all tables from your database schema, and try again.		The above error is returned (where 'table name' wil be replaced with the specific name of a table e.g. sdmx_transaction ) if attempting to restore against a database that already has transactions (structural metadata) within it. Check that you have specified the correct database (on step 1 of the wizard) and if necessary, terminate the Registry, clear all tables from your database schema, and try again.
		+
		+	== Restore is either running, or failed part way. Please check the log files. A restore can not be re-run without first emptying the database tables ==
		+	If this error is displayed it is highly recommended to check your Registry log to see if you can determine what caused the backup to fail. If in doubt, please contact Metadata Technology, supplying the log file for further analysis. To restart the backup process, terminate the Tomcat and then clear out the tables from the database schema. Then restart Tomcat and go through the install process again.

@@ Line 60: / Line 60: @@
 = Troubleshooting =
-== Can not restore from backup - the <table name> database table must be empty ==
+== Can not restore from backup - the 'table name' database table must be empty ==
 The above error is returned (where 'table name' wil be replaced with the specific name of a table e.g. sdmx_transaction ) if attempting to restore against a database that already has transactions (structural metadata) within it.  Check that you have specified the correct database (on step 1 of the wizard) and if necessary, terminate the Registry, clear all tables from your database schema, and try again.

@@ Line 60: / Line 60: @@
 = Troubleshooting =
-== Can not restore from backup - the 'XXX' database table must be empty ==
+== Can not restore from backup - the <table name> database table must be empty ==
-The above error is returned if attempting to restore against a database that already has transactions (structural metadata) within it.  Check that you have specified the correct database (on step 1 of the wizard) and if necessary, terminate the Registry, clear all tables from your database schema, and try again.
+The above error is returned (where 'table name' wil be replaced with the specific name of a table e.g. sdmx_transaction ) if attempting to restore against a database that already has transactions (structural metadata) within it.  Check that you have specified the correct database (on step 1 of the wizard) and if necessary, terminate the Registry, clear all tables from your database schema, and try again.

← Older revision		Revision as of 14:59, 27 March 2023
Line 58:		Line 58:
	==Results==		==Results==
	It is strongly recommended to check the FMR tomcat log files after a restore is complete to ensure all transactions were successfully restored. It is possible for the restore to complete even if some transactions or audits could not be fully restored - the tomcat log files will contain details if this is the case.		It is strongly recommended to check the FMR tomcat log files after a restore is complete to ensure all transactions were successfully restored. It is possible for the restore to complete even if some transactions or audits could not be fully restored - the tomcat log files will contain details if this is the case.
		+
		+	= Troubleshooting =
		+	== Can not restore from backup - the 'XXX' database table must be empty ==
		+	The above error is returned if attempting to restore against a database that already has transactions (structural metadata) within it. Check that you have specified the correct database (on step 1 of the wizard) and if necessary, terminate the Registry, clear all tables from your database schema, and try again.

@@ Line 34: / Line 34: @@
 |-
 | url || URL of running FMR instance || -url http://localhost:8080/FMR
 |}

@@ Line 2: / Line 2: @@
 = Overview =
-From FMR 11.3.0 it is possible to restore the live structures and transaction history from another FMR.  The restore can only be run at install time.  In order to make use of this feature, a Command Line application ([[FMR-CL]]) is used to create a backup from a running FMR instance.  On installation of FMR 11.3.0 or later, the installation process will enable the FMR to load the backup to restore the state.
+From FMR '''11.3.0''' it is possible to restore the live structures and transaction history from another FMR.  The restore can only be run at install time.  In order to make use of this feature, a Command Line application ([[FMR-CL]]) is used to create a backup from a running FMR instance.  On installation of FMR 11.3.0 or later, the installation process will enable the FMR to load the backup to restore the state.
 = Creating a Backup =