Saving Translations - Avaya ESS User Manual

ESS Installation
Figure 40: status ess port-networks

Saving translations

Translations are saved on the Main server by executing the save translations command.
You cannot save translations on an ESS server. When logging into an ESS server you receive a
message stating that this server is an ESS server and translations cannot be saved.
The Main server keeps one complete copy of translations plus the differences between that
copy and one previous copy. Each copy has an associated day and time (timestamp). If the
ESS server's translation timestamp matches the timestamp of the Main server's current
translations, no translation download occurs. If the ESS server's timestamp matches the
timestamp of the Main server's previous copy, the Main server sends only the differences to the
ESS server. If the ESS server's timestamp does not match either of the Main server's copies,
then the Main server sends the entire translation download to the ESS server.
Translations are distributed from the Main server to the ESS server by executing the save
translations ess or save translations all command. Executing the save
translations ess or save translations all command requires network resources
and should be performed when impact to the network is minimal. After the ESS server receives
the translation download, it resets. The ESS server's registration to the Main server drops until
the reset completes.
Saving translations, including sending the translations to the ESS servers, can be performed
during routine Communication Manager maintenance. Communication Manager scheduled
maintenance is administered on the system-parameters maintenance form. See
Figure 41 for an example of the system-parameters maintenance form.
130 Avaya Enterprise Survivable Servers (ESS) Users Guide