VDN call profile administration changes are specific to a CMS server, so any changes made on the primary CMS server must be duplicated on the secondary. Within the interval in which VDN call profile administration changes are made, all data from the time of the profile change and extending back to the beginning of that archive interval are lost. Therefore, it is highly recommended that:

• VDN call profile changes be performed at the beginning of an archive interval.

• the changes be performed sequentially on both the primary and secondary server as quickly as possible.

Also, when the system restore ACD-specific administration data from the primary server to the secondary server, data in the archive interval in which the restore is performed is lost on the secondary server. Therefore, if minimization of data loss is of critical importance, after VDN call profile changes are made on the primary server, do a backup of both ACD-specific administration data and historical data on the primary and restore it onto the secondary server.

To update VDN call profile administration items: