Backup iFIX Files Manually and Restore Them to A New iFIX Machine

Description

iFIX only

iFIX Backup and Restore Utility is designed for performing a full or partial backup of iFIX files which are to be restored to theSAME iFIX machine, or to another machine with the same nodename and directory structure.

In order to restore existing iFIX files to a different iFIX system, it is recommended thatthe working files from an existing iFIX system be backed up manually on the source machine, and subsequently restored to the alternate/target iFIX system.

Below is a list of the Dynamics\FIX32 directories and file types to be manually backed up on an existing system and subsequently restored to another iFIX\FIX32 system:

Step by Step Instructions

Source Machine:

Security Files -If security is enabled on the source machine, disable it and run a security report before you backup any of the other files:

  • Open the System Configuration Utility (SCU) file and click Configure then select Security;
  • Click File,then selectExport and click OK. This will create a Security.Rpt file in the Dynamics\Local directory. This is a report of the current security configuration (without the user passwords);
  • Click on the Key icon in the Toolbox to launch the Configuration. Disable the User Based Security by clicking the "Disabled" radio button and click OK;
  • Save your changes and close the Security Configurator.

Dynamics\HTR directory - This folder contains historical configurations files which may include .CSV files, .CFG, and .DAT files. All files should bebacked up.

Dynamics\HTRDATA directory - This folder contains the .HTC file for each node collected from as well as subfolder for each node collected from containing historical data files, which may include .H04, .H08, or .H24 files. If you want to view old historical data on the new machines, these files should be backed up.

Dynamics\LOCALdirectory - This folder contains a number of configuration and initialization files. Any .INI files, .SCU files, and theSecurity.Rpt file (if applicable) should be backed up.

Note, if you are upgrading the version if iFIX, then the .ini files shouldnot be copied to the new machine. It is also recommended that a new SCU file be created manually for each new node and not to backup existing *.SCU files on one machine/restore to another machine due to potential issues with iFIX security; path configuration; etc.

Dynamics\PIC directory - This folder contains files relevant to pictures. Files to be backed up are .GRF, .TGD, and all of the *.fxg files. If you have created custom color tables (.FTB) or custom dynamos (.FDS) these should be copied as well.

Dynamics\PDB directory ?This folder contains files relevant to the database, alarming and driver communication. Files to be backed up are: Driver configuration file, AlarmAreas.AAD and the database file NOTE: The database and driver config file should be saved or exported out as a *.csv file to limit file corruption.

Dynamics\RCC directory - All files (as applicable) are to be backed up

Dynamics\RCM directory - All files (as applicable) are to be backed up

Finally, if security is enabled, then re-enable User Based Security on the source machine by opening the SCU and clicking on Configure - Security then the Key icon in the Toolbox to launch the Configuration then click the Enabled radio button and OK and Click on the "X" to close the Security Configuration and then click the "Yes" button when prompted with the message "Configuration has changed. Save new changes?"

Target Machine:

  • Restore the backed up directories/files to the target machine;
  • Create a new SCU file and/or open the restored SCU file and change the node name (as required);
  • If security is to be enabled on the target machine, open the Security Configuration in the SCU and click File then Import and import the restored Security.Rpt file;
  • Recreate all user passwords for each of the Users prior to enabling security (as failure to do so will lock all users out of the iFIX system);
  • Finally, once the security information has been imported, and the user passwords have been recreated then reenable User Based Security:

(a)Click the Key icon in the Toolbox to launch the Configuration

(b) Enable the User Based Security by clicking the "Enabled" radio button and click OK

(c) Click on the "X" to close the Security Configuration and then click the "Yes" button when prompted with the message "Configuration has changed. Save new changes"