Specifications

ShoreWare Server Release Notes Disaster Recovery Enhancements
ShoreTel 9.1 Page 83
When the primary and secondary servers are in different subnets, their IP addresses must
be static.
The DNS server accessed by a ShoreTel system must associate the same server name to the
primary and secondary servers if
• The primary and secondary servers are configured with static IP addresses.
and
• The HQ server supports MCM clients or clients on Citrix or Windows Terminal
Servers.
The primary and secondary servers cannot be running and connected to the network at the
same time.
System Failover Requirements
The following sections describe required administrator tasks after the failover operation.
License Compliance
After a failover operation transfers Headquarters server control to the secondary server,
license status on the secondary server is non compliant. To restore the system to
compliance, reinstall all licenses that were originally purchased for the secondary server.
MCM Failover Requirements
To assure proper MCM client operation and performance after a Failover or a Failback, the
browser cache must be cleared. The system administrator should send messages to all
MCM clients after a failover operation advising them to clear the browser cache on their
devices.
System Failback Requirements
The following sections describe required administrator tasks after the failback operation.
Figure 33 Designating Primary and Secondary IP Addresses