Installation, Administration and Maintenance
Aastra
depl-0900/0.4
Page: 47 (104)
Before a database is accepted and replaced by automatic import process the
OMM performs the following checks:
-
The integrity of the file must be OK
-
To avoid the import of the same file multiple times, the checksum of
the new database file and the checksum of the last database import
file (stored in the flash) must be different
-
For authorization/authentication reasons:
The PARK of the new database file must be the same to the PARK of
the current configuration.
-
The admin/full access account of the new database file must be the
same to the one of the current configuration
Only if all of these checks are successful the database file is accepted.
If the database file is not accepted or wasn’t found, an error message is
displayed on the status page of OMM Web Service.
WARNING:
A manual or automatic import of a database leads to a reset of
the OMM to take effect.
The automatic OMM database import allows to change all configuration
settings but not the account settings and PARK. Only one exception:
changing the default user account and PARK for an initial configuration is
possible. After the initial configuration, the user account settings and PARK
can only be changed via the Web service on the target OMM itself.
3.3.2.5.4 Automatic Database Export
The automatic database export feature allows an automatic database backup
to an external server for each configuration modification.
If this feature is activated, the OMM transfers a backup file to a configured
external server any time configuration changes occur, e.g. handset
subscription. If there is no configuration change then no backup will be done.
A backup file will be overwritten during a day if there is more than one
modification. A new file will be created when this first change occurs at the
day.
