External Data Back-Up

The administrator has the task of backing up files used and created by Innovator.

Storage Locations of Innovator Data

As the administrator, you are also responsible for backing up files used and created by Innovator.

Attention

This topic deals with the backup of data as security in case the data carrier (normally the hard drives on the server or local computer) fails.

During the installation of Innovator and during work with Innovator, various data is stored in the directories.

Table: Overview of Program Paths
Meaning	Directory Name	Description
Program Directory	%PROGRAMFILES%\Innovator\16.0	Directory path where the program files are located. These files can be restored at any time by means of a reinstallation or a repair in Windows Control Panel. This means that a backup is not necessary.
Resource and Parameter Directory	$INODIR1	Directory path where resources that cannot be changed are located. This includes icons, engineering action Java files, migration files, language-dependent message files, parameter files and Word templates. You can use a shared workgroup directory and, in doing so, use common settings.
License directory	$INOLIC2	Directory path where you will find or can store the license repository by default.
Project Directory	$INOPRJ3	Directory path where you will find or can store repositories as standard. The `Demo` repository is also located here. For model servers, the `/config` subdirectory contains the model templates (`/option`), add-on templates (`/addon`) and user configurations (`/user`) included within the scope of delivery.

Backup-Relevant Files

Aim of Backup

The data carriers which the Innovator data is stored on - normally the hard drives of servers or local computers - can fail due to defects, damage or other circumstances. Recovery might not be possible. To enable the recovery of the data on servers and local computers despite this, you need to store backup files on other data carriers.

You should include the data below in each data backup.

Files to be Backed Up from $INOPRJ Project Directory

$INOPRJ\<repository>

All subdirectories except for the config directory either contain the Demo repository with the demo model included within the scope of delivery or the model data created by your company.

To reduce the amount of data to back up, to prevent access conflicts and to include the saved model states in the data backup, it makes sense to shut down the model servers with the repositories before the data backup.

Attention

In all cases, you should back up your repositories regularly and should therefore make them part of an automated data backup process.

If you run the model servers on Windows, a special procedure is required.

If work has taken place in the demo model, then the Demo repository should also be backed-up.
$INOPRJ\config\*.*

The configurations included within scope of delivery are saved in the various subdirectories of this directory.

Attention

If you have created user configurations or profiles as base or add-on templates, you must back these up regularly.
$INOPRJ\ivm

Your managed models are stored in this directory; agent data is also stored in this directory under \logs.

The first directory level contains an entry with the model UUID for each managed model.

The versions of a managed model can be found in the second directory level. The name of such a repository directory for a version is show using the "br" prefix, followed by the version UUID ("-" replaced by "_").

Example: ivm\4bed4291-a5a8-4718-44eb-8bd9fd7d3bf2\br3e2748d2_7cb0_0d13_f52c_247b57ac8bb0
$INOPRJ\ivm\logs

Log files can provide important information about problems which may have occurred. They should also be taken into consideration when carrying out regular back-ups.

Files to be Backed Up from the $INODIR Resource and Parameter Directory

$INODIR\inolic.lr

This file contains your license authorizations, which you can retrieve from us again.

Attention

The license projects created by you (key words "project license server") and user management data (key words "user management on license server, LDAP connection") are also saved in this file.

For this reason, you should back up this file regularly. In all cases, it should be backed up after major changes to the configuration of licenses or users.
$INODIR\java\*.*

Scripts are normally saved in this directory. If you have created scripts and saved them here, you should back up the finished scripts or make sure that they can be recovered at any time from the development environment used.
$INODIR\logs\

Log files can provide important information about problems which may have occurred. They should also be taken into consideration when carrying out regular back-ups.