Frequently Asked Questions (FAQ)
Breadcrumbs

Backup i-effect

If i-effect® is to be backed up completely, these instructions contain the processing steps necessary for this. Since the automated installation of i-effect also makes an automatic backup, the procedure described here is only to be used if another backup is to be made specifically.

i-effect® must be closed before the backup is started (Ending i-effect ).

Save the current status

With the help of the following script command, the current installation with all its components can be backed up. This includes all objects used by the product such as libraries and IFS directories, as well as environment variables and settings.

The backups are marked with a consecutive number. This backup is assigned the next available number.

The backups made can be viewed in the IEFFSAVE library. The version and date of the backup can be read from the object description.


Object

Type

Attribut

Text

Explanation

APP0

*FILE

SAVF

APP 2.9.0-RC100 2021-03-22 16:48:01

Backup of the application schema from version 2.9.0 from 22.3.2021, 16:48:01

APP1

*FILE

SAVF

APP 2.9.0-RC109 2021-03-22 17:12:55

Backup of application schema from version 2.9.0 from 22.3.2021, 17:12:55

DB0

*FILE

SAVF

DB 2.9.0-RC100 2021-03-22 16:48:01

Backup of database schema from version 2.9.0 from 22.3.2021, 16:48:01

DB1

*FILE

SAVF

DB 2.9.0-RC109 2021-03-22 17:12:55

Backup of database schema from version 2.9.0 from 22.3.2021, 17:12:55

ENV0

*FILE

PF-DTA

ENV 2.9.0-RC100 2021-03-22 16:48:01

Backup of environment variables from version 2.9.0 from 22.3.2021, 16:48:01

ENV1

*FILE

PF_DTA

ENV 2.9.0-RC109 2021-03-22 17:12:55

Backup of environment variables from version 2.9.0 from 22.3.2021, 17:12:55

IFS0

*FILE

SAVF

IFS 2.9.0-RC100 2021-03-22 16:48:01

Backup of IFS directories from version 2.9.0 from 22.3.2021, 16:48:01

IFS1

*FILE

SAVF

IFS 2.9.0-RC109 2021-03-22 17:12:55

Backup of IFS directories from version 2.9.0 from 22.3.2021, 17:12:55

LNG0

*FILE

SAVF

LNG 2.9.0-RC100 2021-03-22 16:48:01

Secondary language backup from version 2.9.0 from 22.3.2021, 16:48:01

LNG1

*FILE

SAVF

LNG 2.9.0-RC109 2021-03-22 17:12:55

Secondary language backup from version 2.9.0 from 22.3.2021, 17:12:55

LNGS0

*FILE

SAVF

LNGS 2.9.0-RC100 2021-03-22 16:48:01

Secondary language backup (SYSBAS) from version 2.9.0 from 22.3.2021, 16:48:01

LNGS1

*FILE

SAVF

LNGS 2.9.0-RC109 2021-03-22 17:12:55

Secondary language backup (SYSBAS) from version 2.9.0 from 22.3.2021, 17:12:55

SYS0

*FILE

SAVF

SYS 2.9.0-RC100 2021-03-22 16:48:01

Backup of SYSBAS schema from version 2.9.0 from 22.3.2021, 16:48:01

SYS1

*FILE

SAVF

SYS 2.9.0-RC109 2021-03-22 17:12:55

Backup of SYSBAS schema from version 2.9.0 from 22.3.2021, 17:12:55

VER0

*FILE

PF-DTA

VER 2.9.0-RC100 2021-03-22 16:48:01

Backup of version status from version 2.9.0 from 22.3.2021, 16:48:01

VER1

*FILE

PF-DTA

VER 2.9.0-RC109 2021-03-22 17:12:55

Backup of version status from version 2.9.0 from 22.3.2021, 17:12:55

Start backup

After entering the following command in a QSH session, the current state is saved

/i-effect/v2r9m0/base/tools/scripts/save2mebeff.sh -v v2r9m0

Protocol

The following messages appear on the console during a backup:

[17:34:47] *** Started at: Mon Mar 22 17:34:47 2021
[17:34:47] Check access rights...
[17:34:52] Check locks...
[17:35:26] Starting backup...
[17:35:26] Backup with unique identification: 13
[17:36:14] *** Ends at : Mon Mar 22 17:36:14 2021set
[17:36:14] *** Duration : 1 minutes and 30 seconds elapsed.
[17:36:14] Backup successfully completed.

Log file

The log file /tmp/JHJJMMTT-HHMMSS-ieffect-save.log contains the extended log for this backup.

Restore from this backup

The copy made with this backup can be saved back at any time as described in Restore