When "Save configuration data in local flash" is activated, a backup
file is created on the local flash at the set time of the day (default
03:00).
When "Save configuration data in local flash" is activated, a backup
file is created on the local flash whenever data is saved in the WBM.
This means that virtually no data is lost any more when loadware is updated
via HDLC.
This backup file is only used in the event of a loadware upgrade which
is performed per HDLC (with an STMI) or FTP (with an NCUI). If such as
upgrade is initialized, the restore is executed using the existing backup
file when the new loadware version is started (still in startup - before
the gateway status "system ready"). Then a check is made whether the
OpenScape 4000 Assistant "Backup and Restore" is reachable or whether
a more up-to-date backup is available. This is the case if between 3:00
and the current time a manual or an automatic backup of the board was
created. If there is a more up-to-date backup available on the OpenScape
4000 Assistant "Backup and Restore" and the backup server can be reached,
a second restore is carried out.
If the loadware upgrade is done via the loadware manager of the assistant,
then the backup file in the local flash (03:00) is not used. In this
case a current backup is created in the local flash before the new software
is activated with the old load. Then the new loadware version is loaded
and started. During startup the backup created shortly before is imported.
This ensures that this upgrade with the local backup/restore always contains
the latest configuration data. The OpenScape 4000 Assistant "Backup and
Restore" must still be contacted to check the backup file. This is important
in the case of HFA : Here there is a backup on the OpenScape 4000 Assistant
backup server with the same IP address but old MAC address which then
must be imported.
Notes on rebooting
- If the backup is created from the OpenScape 4000 Assistant "Backup and
Restore" before the "system ready" status of the board, then there is
no additional reboot. If the backup is created after the "system ready"
status because the OpenScape 4000 Assistant backup server is not reachable
immediately, then the board is automatically rebooted in the case of
SPE (because of certificates and MEK).
- The local backup is restored during the startup phase (before the
board is operational) and therefore an additional automatic gateway reboot
is only necessary in exceptional cases (e.g. SPE certificates available).
- If additionally a OpenScape 4000 Assistant "Backup and Restore" server
is configured/present, the currentness of the backup determines applying
board data, i.e. restore from the local backup or the OpenScape 4000
Assistant "Backup and Restore" backup. If the OpenScape 4000 Assistant
"Backup and Restore" backup is more up-to-date, this can possibly lead
to an additional reboot.