System Maintenance, Backups, and Migration - EcoSys - Administration - Hexagon PPM

EcoSys System Administration

PPMProduct
EcoSys
PPMCategory_custom
Administration & Configuration
Version_EcoSys
8.6

Considerations for system maintenance, backups, and migration of an existing EcoSys installation.

System Maintenance

The primary data repository for EcoSys is the ESFM database. Normal maintenance for the related database platform (Oracle or SQL Server) is all that is required. Please consult with your database administrators.

Backups

  1. Database: All live data in the EcoSys system is stored in the ESFM database. Your database administrator should configure backups of this database in accordance with your site’s backup policies. It is recommended to take at least nightly snapshots of the data, and verify that they can be restored in the case of hardware failure or user error.

  2. Configuration Files: The configuration files under the ESFM_HOME folder on the application server should also be backed up whenever they are modified. This will facilitate reconstructing an installation if ever needed.

Migration

When migrating an existing EcoSys installation to another environment, the following considerations may be useful:

  1. Database: A database-level backup and restore can be used to move EcoSys data from one instance to another. Alternatively, you can use the Database XML Utility (see section above) for this purpose.

  2. Configuration Files: Copying the contents of the ESFM_HOME folder to the target environment will save time in a migration. Make sure your system administrator reviews the contents and settings in FMServerSettings.properties to adjust them for the target environment. Some of the settings reference specific database row id values which must be updated to match the new database.

  3. License Files: Note that you must adhere to the contractual terms of the sale if you are redeploying an existing license file.

  4. Primavera Integration API: It is recommended that you run the Primavera Integration API’s configuration tool after ghosting or cloning an existing server, so that the new server properly connects to the target Primavera database.

Purging Batch Job Logs

In order to purge historical batch job logs from the database, a utility script is provided in the utils folder. Refer to the comments within this script for how to use it and execute it against your database as needed.

For Oracle Databases:

database/oracle/utils/fm_or_delete_batchjob_records.sql

For SQLServer Databases:

database/sqlserver/utils/fm_ss_delete_batchjob_records.sql