Backup Evo-ERP
Evo-ERP and DBA Classic are designed to be self-contained meaning the application exists entirely in the EvoERP or DBAMFG directory. There are a couple caveats to this described below:
- ISTS directories that are stored either on workstations or another folder as part of an RDP environment.
- The named database references stored in the Zen/Pervasive Control Center. These can be recreated if necessary by running
ODBCDDFfrom UT-A.
Before Performing Backup
Before creating the backup we recommend checking the following to ensure files are not backed up in a partially written state:
- Stop the Actian Zen/Pervasive engine to ensure no data tables are in use during the backup process.
- Check that no files in the EvoERP or DBAMFG folder are open. This can be done with various tools such as Computer Management (for shared folders), Resource Monitor, or the Sysinternals Handle Utility.
- If you use Evo Service, stop the service while performing the backup.
Creating the Backup
Once you are confident that no components in the system are in use, you can simply copy or zip the folder to create the backup. If you are making the backup prior to installing an update, make sure you have the copy or zip file readily available in case of any errors during the update process.
Recovering the Backup
To recover your Evo-ERP installation from a backup, there are a few steps to perform to make sure the restoration is successful.
- If you can still run the license utility in the folder prior to reinstating the backup, run it and make sure your license is not installed. If you can’t run this tool, you may need to contact us to have the license deauthorized.
- Replace the existing
EVOERPorDBAMFGfolder with the folder from the backup. Make sure not to copy the contents on top of an existing folder, you must replace the entire folder. - If your backup is 2025.1 or newer, run the license utility to install your license on the recovered folder.