Backup Strategy for ZDO

This section deals with aspects of the data backup in the ZDO procedure.

During a ZDO update, the users continue to work until the end of the maintenance event. They have to log off from the system only for the time of the cutover.

During the uptime processing, database logging is kept active, and if scheduled, regular system backups are triggered in the background. Before the cutover is started, it is recommended to perform a full system backup that includes:

a synchronous state of the database
the SUM directory
the system and instance directories
the kernel directory

After a major problem occurs after a switch over to the new release, you can restore the system to the state of the full system backup. Then, a reset of the SUM procedure could be performed as described in Resetting the ZDO Procedure.

You are asked in a dialog in phase SUMASK_ZDO_CONFIGURATION of roadmap step Configuration whether you want to run a system backup during the transition from the bridge subsystem to the target subsystem.

If you choose this option, a further dialog in phase REQ_ZDO_SYSTEM_BACKUP of roadmap step Postprocessing prompts you to start the system backup. If you confirm, the bridge subsystem stops, and you can start to perform a full system backup.

To reset the update from this point in time, back up now the complete SUM directory including all subdirectories! In addition, the current state of the database, the system and instance directories, and the kernel directory must be backed up to be able to restore to a consistent state.