We recommend backing up your database regularly.
Stop the Firebird service and the Markvision Enterprise service.
Open the Run dialog box, and then type .
Right-click Firebird Guardian - DefaultInstance, and then click Stop.
Right-click Markvision Enterprise, and then click Stop.
Browse to the folder where Markvision Enterprise is installed.
For example,
Back up the application and database files.
Copy the following files to a safe repository:
Lexmark\mve_encryption.jceks
Lexmark\mve_truststore.p12
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\encryption.properties
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\platform.properties
Lexmark\Markvision Enterprise\apps\library
Lexmark\Markvision Enterprise\apps\mve-data-service\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\mve-data-service\WEB-INF\classes\encryption.properties
Lexmark\Markvision Enterprise\jre\lib\security\cacerts
Lexmark\Markvision Enterprise\tomcat\conf\server.xml
Do either of the following:
If you are using a Firebird database, then copy the following files to a safe repository. These files must be backed up regularly to avoid data loss.
Lexmark\Markvision Enterprise\firebird\security2.fdb
If you are using custom database names, then update the following:
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\mve-data-service\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\mve-data-service/WEB-INF\classes\application.yml
Lexmark\Markvision Enterprise\firebird\aliases.conf
Lexmark\Markvision Enterprise\firebird\data\QUARTZ.FDB
Lexmark\Markvision Enterprise\firebird\data\MONITOR.FDB
Lexmark\Markvision Enterprise\firebird\data\FRAMEWORK.FDB
If you are using Microsoft SQL Server, then create a backup for FRAMEWORK, MONITOR, and QUARTZ.
For more information, contact your Microsoft SQL Server administrator.
Restart the Firebird service and the Markvision Enterprise service.
Open the Run dialog box, and then type .
Right-click Firebird Guardian - DefaultInstance, and then click Restart.
Right-click Markvision Enterprise, and then click Restart.
Stop the Markvision Enterprise service.
For more information, see step 1 of Backing up the database and application files.
Browse to the folder where Markvision Enterprise is installed.
For example,
Restore the application files.
Replace the following files with the files that you saved during the backup process:
Lexmark\mve_encryption.jceks
Lexmark\mve_truststore.p12
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\encryption.properties
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\platform.properties
Lexmark\Markvision Enterprise\apps\library
Lexmark\Markvision Enterprise\apps\mve-data-service\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\mve-data-service\WEB-INF\classes\encryption.properties
Lexmark\Markvision Enterprise\jre\lib\security\cacerts
Lexmark\Markvision Enterprise\tomcat\conf\server.xml
Restore the database files.
Do either of the following:
If you are using a Firebird database, then replace the following files that you saved during the backup process:
Lexmark\Markvision Enterprise\firebird\security2.fdb
If you are using custom database names, then the following files are also restored:
Lexmark\Markvision Enterprise\apps\dm-mve\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\mve-data-service\WEB-INF\classes\database.properties
Lexmark\Markvision Enterprise\apps\mve-data-service/WEB-INF\classes\application.yml
Lexmark\Markvision Enterprise\firebird\aliases.conf
Lexmark\Markvision Enterprise\firebird\data\QUARTZ.FDB
Lexmark\Markvision Enterprise\firebird\data\MONITOR.FDB
Lexmark\Markvision Enterprise\firebird\data\FRAMEWORK.FDB
If you are using Microsoft SQL Server, then contact your Microsoft SQL Server administrator.
Restart the Markvision Enterprise service.
For more information, see step 4 of Backing up the database and application files.