ShoreTel 14.x Full Server Protection Using Double-Take Availability for Windows

Transcription

1 ST AppNote (AN 16076) December, 2016 ShoreTel 14.x Full Server Protection Using Double-Take Availability for Windows Description: This Application Note describes configuration of Double-Take for ShoreTel HQ Server redundancy. Environment: ShoreTel 14.x and Vision Solutions Double-Take Availability for Windows ShoreTel. Brilliantly simple business communications. Page 1 of 60

2 Contents Introduction... 4 Comparisons between Double-Take 6.0 or earlier versions and Double-Take Basic Operations... 6 Deployment Models... 9 Requirements General Recommendations Double-Take Availability Setup Configuring Network Interfaces Installation and Configuration of Double-Take Availability Installing Double-Take Server Installing Double-Take Console Configuring Double-Take Availability Installing the ShoreTel Server Software on the Servers Configuring the TARGET Server s Primary IP Address Configuring DHCP for IP Phones Configuring Distributed Voice Services Servers Configuring ShoreTel Mobility Router Configuring Distributed Database Enabling Distributed Database Viewing Database Status Configuring Physical Switches Server Updates ShoreTel Server Upgrades Limitations TroubleShooting Configuring Job Properties Managing Jobs Environment Evaluation Evaluating Environments Best Practices Failover ShoreTel. Brilliantly simple business communications. Page 2 of 60

3 Failback Appendix A: Failover Script Verifying Scripts Additional Resources Document and Software Copyrights Trademarks Company Information Document History ShoreTel. Brilliantly simple business communications. Page 3 of 60

4 Introduction Double-Take 8.0 Availability for Windows provides complete data protection and enables instant recovery from a server outage. It continuously captures byte-level changes and replicates them without a shared storage or geographic limitations. Double-Take Availability provides the following features: Continuous protection and workload recovery on physical or virtual servers. It offers application availability that allows recovery of the entire ShoreTel HQ server. Comprehensive high availability and disaster recovery. Real-time or periodic protection for applications and data. Support for dissimilar hardware. Multiple recovery points if logical data is corrupt or data has no distance limits between servers. Near-zero data loss. Double-Take monitors the ShoreTel HQ Server (SOURCE) for a failure, and if it fails, the backup server (the TARGET) stands in for the SOURCE by restarting and applying the SOURCE system state on the TARGET. After it restarts, the TARGET becomes the SOURCE. Note: If the servers are on different subnets, you must use FQDN instead of the IP address. ShoreTel. Brilliantly simple business communications. Page 4 of 60

5 Comparisons between Double-Take 6.0 or earlier versions and Double-Take 8.0 Double-Take 6.0 or earlier versions Double-Take 8.0 Same version of ShoreTel Server has to be installed on both SOURCE and TARGET. ShoreTel software upgradation and Windows updates are required for both SOURCE and TARGET. Failover is automatic by default and it results in an undesired failover. ShoreTel Server has to be installed only on SOURCE using Full Server Protection. ShoreTel software upgradation and Windows updates are required only for SOURCE. The default configuration of Failover is changed to Manual. To complete the Failover process, you need to perform the Failover and Reverse Failover. Failback process requires a maintenance window and a manual process of copying data from TARGET to SOURCE. Failback process is now a single mouse click. To complete the Failback process, you need to perform the Failover and Reverse Failover twice. No maintenance window is required for Failback when using Reverse Protection. You can check the on-going process on the Monitoring server. Double-Take 8.0 includes the following new capabilities for Windows-based servers: Improved the usability of Double-Take Console with simplified job creation workflow. Optimized the network usage in the areas of polling and mirroring. Upgraded to.net for Windows security updates. Included Port Address Translation (PAT) to accommodate more robust firewall configurations. Added RESTful interfaces to the SDK. Enhanced the operating system support o Client Double-Take Console is now supported on Windows 10. Removed support for Windows XP. o Server ShoreTel. Brilliantly simple business communications. Page 5 of 60

6 Removed support for Windows Server 2003 RTM, Windows Server 2003 R2, and Windows Server 2008 RTM, and all 32-bit Windows Server OS. Note: The previous versions of Double-Take still support 32-bit Windows Server Operating Systems, Windows XP, Windows Server 2003 RTM, Windows Server 2003 R2, and Windows Server 2008 RTM. Removed the following workflows or job types from DT 8.0: o o o o o Double-Take Availability for Hyper-V (DTHV) protection Double-Take Availability for vsphere (DTAV) protection Exchange protection V to Hyper-V protection V to ESX protection Note: The previous versions of Double-Take still support Double-Take Availability for Hyper-V, Double- Take Availability for vsphere, Exchange, V to Hyper-V, and V to ESX protection jobs. ShoreTel does not support Double-Take in the Hyper-V environment. Included general maintenance to address issues in FCS 1. Basic Operations Double-Take operation is summarized in the following three steps: Mirroring After a job is created, the job automatically starts copying source and system data from the SOURCE server to the TARGET Server. ShoreTel. Brilliantly simple business communications. Page 6 of 60

7 It takes several minutes to copy the necessary data from the SOURCE to the TARGET server for the first time. When the system is fully operational, the value in the Activity column is Protecting and the value in the Mirror Status column is Idle. When the two servers are hosted on the same subnet, the estimated time it takes to complete the mirroring process is as follows: For Windows server, 1 hour and 30 minutes For a server on which ShoreTel 14.x is installed, 2 hours Note: If the initial mirroring to TARGET fails without any warnings or errors, you cannot start a failover. Therefore, we recommend that you validate the data is mirrored to the TARGET. To validate, on the Double-Take Console, select the Report only option in the Verifications Options section of the job properties. If the verify operation has completed but the job freezes, clear the job s state by performing the following steps from the TARGET: Stop the Double-Take service first and then the Double-Take Management service. Click Start > Run, type regedit, and then click OK. The Registry Editor window appears. On the Registry Editor window, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\NSI Software\Double-Take\CurrentVersion\Connections\<Target_Connection>\TargetState and change the key State value from 1 to 0. ShoreTel. Brilliantly simple business communications. Page 7 of 60

8 Restart Double-Take service first and then Double-Take Management services. Note: Ensure that the Double-take system is always active. If the Double-Take system remains idle after the initial mirroring from SOURCE to TARGET, you might see the Writing to the target has been paused message and the job remains in a warning state for few minutes. Monitoring TARGET monitors the SOURCE server for a failure or any changes. Failover When the SOURCE fails, the TARGET server stands in for the SOURCE by restarting and applying the SOURCE system state on the TARGET. After it restarts, the TARGET becomes the SOURCE. Note: Manual failover is the default and the only supported option. You should perform a failover from physical to physical machines or from virtual to virtual machines. For more information about failover, refer the Failover section. The following figure shows the three basic operations of Double-Take. ShoreTel. Brilliantly simple business communications. Page 8 of 60

9 After the TARGET restarts, the TARGET becomes the SOURCE in both identity and with the source data. Deployment Models When you use Double-Take to set up ShoreTel servers, you must consider the type of redundancy. The three protection models are as follows: Full Server Protection Full Server with Reverse Protection Geographic Full Server with Reverse Protection Note: You must use the secondary NIC for all the three deployment models to avoid performance issues. ShoreTel. Brilliantly simple business communications. Page 9 of 60

10 Full Server Protection (SOURCE and TARGET are in the same Data Center) Full server protection provides high availability for an entire server, including the server's operating system and applications that are configured. The SOURCE and TARGET servers are on the same IP Subnet. Double-Take failover results in the TARGET server assuming the SOURCE s identity including the SOURCE s IP address. An IP address conflict prevents the SOURCE server from connecting to the network when the SOURCE server is repaired. The old SOURCE is configured such that it is the new TARGET server. When the ShoreTel software is uninstalled, the original TARGET IP address is used for the new TARGET (old SOURCE). The administrator has to manually configure Double-Take to set up monitoring and data replication after a failover. Full Server with Reverse Protection (SOURCE and TARGET are in the same Data Center) Reverse protection allows you to store a copy of the TARGET s system state on the SOURCE server in the staging-ssm folder, so that the TARGET server is not lost. The reverse process brings the TARGET s identity back on the SOURCE hardware and establish protection. After the reverse process, the TARGET (running on the original SOURCE hardware) protects the SOURCE (running on the original TARGET hardware). In a LAN environment, consider having two IP addresses on each server. This allows you to monitor and failover one or more IP addresses, while leaving an IP address that does not get failed over. The IP address that is not failed over is called a reserved IP address and is used for the reverse process. The reserved IP address remains with the server hardware. The reserved IP address is not used for the Voice VLAN. The reserved IP address can be on the same or different subnet from your production IP addresses. However, if the subnet is different, it should be on a different network adapter. The reserved IP address is also used to route Double-Take data. The SOURCE and TARGET servers are configured with two network interfaces. The primary NIC on both the ShoreTel. Brilliantly simple business communications. Page 10 of 60

11 servers is on the same IP Subnet/VLAN, and the secondary NIC has an IP Address for Double-Take to use for management. The secondary NIC can be on the same IP subnet/vlan as the primary or on a dedicated management IP Subnet/VLAN. The primary IP address is moved to the TARGET on failover but the secondary IP addresses never move. Double-Take uses the secondary addresses to track the SOURCE and the TARGET server. When the SOURCE server is repaired and is online, its primary IP address results in a conflict preventing any ShoreTel services from running properly. You can use the Double-Take Console to reconfigure the old SOURCE as the new TARGET and set up replication and monitoring using a single click. Geographic Full Server with Reverse Protection (SOURCE and TARGET are in separate Data Centers) The SOURCE and TARGET servers are in separate Data Centers. Each server has two NICs that are connected to separate IP Subnets or VLANs. You must configure the SOURCE s primary address as IP address and the TARGET s primary address as Secondary IP address for the HQ server in ShoreTel Director. A failover script (command line.exe) is used to update the ShoreTel registry values for the server s IP address that is run by Double-Take as part of the failover process. For more information about the failover script, see Appendix A. On failover, the primary IP Address does not move to the TARGET. Double-Take uses the secondary addresses to track the SOURCE and TARGET server. Double-Take uses the secondary addresses to track the SOURCE and TARGET server. When the SOURCE server is online, its primary IP Address does not result in a conflict. Therefore, the ShoreTel services start and attempt to manage the ShoreTel voice switches. The administrator has to restart ShoreTel. Brilliantly simple business communications. Page 11 of 60

12 the old SOURCE while it is disconnected from the network so that the ShoreTel services are disabled. You can now connect the server to the network. You can use the Double-Take Console to reconfigure the old SOURCE as the new TARGET and set up replication and monitoring using a single click. Recommendation If Double-Take Reverse protection is configured, we recommend that you install the Double-Take Management Console on a third computer that can access both the SOURCE and TARGET servers. Figure 1 shows an example of a complete deployment. ShoreTel. Brilliantly simple business communications. Page 12 of 60

13 Requirements Figure 1 While setting up Double-take Availability, you must consider the following requirements: The SOURCE and the TARGET server must have the same version of the operating system. For example, if Windows Server 2012 is installed on the SOURCE server, the TARGET must be on Windows Server The SOURCE and TARGET server can have different edition of Windows such as Standard, Enterprise, and so on. The SOURCE and the TARGET server must have the same architecture. For example, 32 bits on both or 64 bits on both. The SOURCE and TARGET server must have the NTFS file system format. FAT and FAT32 are not supported. ShoreTel. Brilliantly simple business communications. Page 13 of 60

14 The TARGET cannot be a domain controller and must not host any other functionality. The SOURCE and TARGET servers should have at least the same number of processors and similar processor speeds so that it does not impact the performance after the failover. If the TARGET has fewer processors or slower processors than the SOURCE, there will be performance issues after failover. In total, 4 GB of RAM is required to test Double-Take on a server where ShoreTel applications are installed (1 GB for Double-Take, 1 GB for the ShoreTel application, and 2 GB for other applications and system files). TARGET volumes (C: D: E: and so on) must match for every volume protected. The SOURCE and TARGET must have the same system path. The system path includes the location of the Windows files, Program Files, and Documents and Settings (for example, C:\Program Files\Vision Solutions). You must install Double-Take on the same path (volume and full directory path) on the SOURCE and TARGET. If you enable reverse protection with the full server job, SOURCE and TARGET must run the same version of Double-Take. You must map at least one NIC from the SOURCE to one NIC on the TARGET. Microsoft.NET Framework version is required on both the SOURCE and TARGET. The TARGET must have enough space to store the data from the SOURCE. The amount of disk space depends on the applications and data files you are protecting. The TARGET must also have enough space to store, process, and apply the source's system state data. If you enable reverse protection, the SOURCE must have enough space to store, process, and apply the target's system state data. In either case, the size of the system state depends on the operating system and architecture. A copy of the source system state data is stored on the TARGET boot volume in a folder called Staging- SSM. For reverse protection, the target system state is stored on the SOURCE boot volume in a folder called Staging-SSM. You can predict the amount of space you need in the staging folder by calculating the size of the following folders on your boot volume: o o o o o Documents and Settings Program Files Program Files (x86) Program Data Windows ShoreTel. Brilliantly simple business communications. Page 14 of 60

15 o o Users Any other folders you manually select for staging Note: If the TARGET s boot volume does not have enough space to accommodate the source data and the staging folder, the job will stall in the retrying state and will not be able to complete synchronization. You should have a minimum of 2 GB space on the TARGET boot volume to ensure enough space for failover processing. The following estimates are the minimum amount of free space that the SOURCE must have for a clean source installation: 10 GB for Windows 2008 R2 15 GB for Windows 2012 R2 Note: Operating system customizations, installed applications, and user data increases the disk space requirement. General Recommendations The Double-Take Availability for Windows User s Guide provides some general recommendations for configuration. (For link to the document, see the Additional Resources section.) Third machine to run Double-Take Console You should use a third machine to run the Double-Take Console, set up protection, and perform full and reverse failover. The third machine communicates with the reserved IP addresses. If you do not use a third machine, you may need to remove and add the servers into the console by using the reserved IP addresses. Single gateway Even if you are using multiple IP addresses on Windows server, use a single gateway instead of multiple gateways. NIC configuration To failover the IP address of the SOURCE, use a separate NIC and separate network for a Double-Take reserved IP address that is not failed over. If you use one NIC for both production and reserved IP addresses, disable DNS registration on the NIC. If the IP address of the SOURCE is not failed over, an additional NIC and address is not necessary. In this case, Double-Take blocks the DNS record for that address while it is failed over. Disabling DNS registration Disabling DNS registration for the reserved IP address ensures that a user is not communicating to the original SOURCE when it is failed over because two different DNS records point to two different servers. ShoreTel. Brilliantly simple business communications. Page 15 of 60

16 Double-Take Availability Setup Setting up Double-Take Availability includes the following tasks: Configuration of Network Interfaces Installation of Double-Take Server Installation of Double-Take Console Configuration of Double-Take Availability Installation of ShoreTel Server Software on the Servers Configuration of TARGET Server s Primary IP Address Configuration of DHCP for IP Phones Configuration of Distributed Voice Services Servers Configuration of Mobility Router Configuration of Distributed Database Configuration of Job Properties and Management of Jobs Configuring Network Interfaces Before you install the ShoreTel server software, you must add a second NIC to a virtualized ShoreTel server. Note: On a server with multiple NICs, the software always binds to the very last NIC that was added to the server. For more information, see Binding-Order-on-Microsoft-Server-2012 You can install Double-Take while the ShoreTel server is running; no maintenance window or system restart are required. However, you must configure the second NIC for managing the network. To ensure continued functioning of the ShoreTel system if reverse protection deployment is selected, configure the network interfaces for the SOURCE and TARGET servers such that each have static IP addresses appropriate for voice and network management. For example, NIC1 is Voice LAN and NIC 2 is Data VLAN. Only one default gateway is configured on the production voice NIC and not the management NIC. Therefore, you must use static routes or persistent routes on the server to ensure that the traffic that is destined for the management NIC of the other server is routed properly. Examples of the static routes required for the deployment topology shown in Figure 1 are as follows: Source: ShoreTel. Brilliantly simple business communications. Page 16 of 60

17 Target: route add mask p route add mask p route add mask p route add mask p Follow these steps to configure the network interfaces and prioritize the NICs: 1. From the Control Panel, open the Network and Sharing Center. The Network and Sharing Center window appears. 2. Click the Change adapter settings link. The Network Connections window appears. 3. Press the ALT+N keys on your keyboard to display the Advanced menu. 4. Select Advanced Settings. The Advanced Settings dialog box appears. ShoreTel. Brilliantly simple business communications. Page 17 of 60

18 5. Click the Adapters and Bindings tab, and then select the NIC that is connected to the voice network and use the up arrow next to the connections list to move the item such that it is listed first. Note: Changing the order of connections such that the Voice VLAN NIC is listed first presents the correct IP Address or NIC to applications that use Windows APIs. 6. Ensure that in the Bindings for Ethernet section, for each NIC, Internet Protocol Version 4 is listed first and Internet Protocol Version 6 is not selected. 7. Click the Provider Order tab and ensure that the Microsoft Windows Network is listed first. 8. Click OK and close the Advanced Settings dialog box. The Network Connections window displays the NICs. Note: You can run the route print command in the command prompt window to view the routing table to see the metric associated with the routes. 9. Right-click the Voice VLAN and select Properties. The Ethernet Properties dialog box appears. ShoreTel. Brilliantly simple business communications. Page 18 of 60

19 10. Select the Internet Protocol Version 4 option from the protocol list. The Internet protocol version 4 TCP/IP Properties dialog box appears. 11. Click the Advanced button. The Advanced TCP/IP Settings dialog box appears. ShoreTel. Brilliantly simple business communications. Page 19 of 60

20 12. Clear the Automatic metric check box, and enter 1 in the Interface metric field. 13. Click the DNS tab of the Advanced TCP/IP Settings dialog box. 14. Ensure that the Register this connection s addresses in DNS option is not selected for all the NICs. Note: You must ensure that DNS has manually created a record in the primary DNS zone for the HQ server that references only the primary Voice VLAN IP Address. ShoreTel. Brilliantly simple business communications. Page 20 of 60

21 15. Click OK to close each of the dialog boxes. 16. Perform the following tasks: Verify the settings are correct by typing route print in the command prompt. The metric associated with the Voice VLAN routes should have a lower value than the Data VLAN routes. In the following example, the Voice VLAN routes have a metric of 257 while the Data VLAN route has a value of 261. Verify the network connections and the associated IP addresses are correct by typing ipconfig /all in the command prompt. Verify that both the SOURCE and TARGET are properly configured. ShoreTel. Brilliantly simple business communications. Page 21 of 60

22 The SOURCE and TARGET servers are now ready for software installation Installation and Configuration of Double-Take Availability Double-Take Availability consists of Double-Take Console and Double-Take Server. You can install the software on the SOURCE and TARGET servers, but only the server components are required on the SOURCE and TARGET servers. If you are installing Double-Take Availability on an existing ShoreTel system that has ShoreTel distributed voice servers, you might need to edit the Windows Registry to change the HQServerAddress and LocalDBServerAddress values from IP Addresses to FQDNs. For Full Server protection, you need to install the ShoreTel server software only on the SOURCE server. Double-Take Availability replicates data, applications, and the state of the Windows server to the TARGET server as part of failover. There is no need to install ShoreTel software on the TARGET server. You should install Double-Take Console on a third computer to manage the system remotely. If Double-Take Console is installed on the server, you must ensure that it is installed on both the SOURCE and TARGET. You must use the default values while installing Double-Take server components on SOURCE and TARGET. The Installation chapter of the Double-Take Installation and Licensing Activation Guide provides detailed instructions about installation and licensing. To download the Double-Take Installation and Licensing Activation Guide, see the Additional Resources section. Installing Double-Take Server Follow these steps to install Double-Take server on a Windows machine: 1. Go to and download the Double-take executable file. 2. Close any open applications. 3. Double-click the downloaded file to start the installation. 4. Select the language for the software. When the installation begins, the Autorun appears that allows you to install software and view documentation and online resources. 5. Select any of the product installation links to install the server. Depending on the version of Windows, you must install the following components: One or more Visual C++ security updates Microsoft.NET Framework Note: Ensure that these components are installed on the server. 6. Select Yes to install or enable Microsoft.NET and click Continue. ShoreTel. Brilliantly simple business communications. Page 22 of 60

23 Note: Before installing Double-Take server, you must install or enable Microsoft.NET. 7. Click Yes to check for a later version. 8. Click Next to proceed. The installation program establishes an Internet connection from your server to the Vision Solutions website and lists the latest version. You can select the version that you want to download. 9. Review the Vision Solutions license agreement and accept the license agreement to continue with the installation. 10. Click Next. 11. Review the activation notice. For full product functionality, Double-Take licenses require activation after installation. If you fail to activate licenses, Double-Take jobs fail. 12. Click Next to continue. 13. Select either of the following options based on your requirements: Client and Server Components The client components do not require a license key. However, licenses are required to administer Double-Take servers throughout the organization. We recommend that you select this option. Server Components Only Does not allow you to use Double-Take Console. 14. Click Change and specify the location to install the Double-Take files, and then OK. 15. Click Next. 16. If Windows Firewall is enabled on the machines where you want to install Double-take Console, select one of the following options to open and reassign any firewall ports for Double-Take: Open only the ports that are not in use Opens any firewall ports that are not in use. The ports that are opened are assigned to Double-Take. Open all ports, reassigning the ports in use to Double-Take Opens all necessary firewall ports reassigning any to Double-Take as needed. Do not configure the Windows Firewall at this time Does not modify any firewall ports. If you select this option, you must manually modify the firewall settings for Double-Take to process. 17. Click Next. 18. Click Install to start copying the Double-Take files. 19. Click Finish when the installation is complete. ShoreTel. Brilliantly simple business communications. Page 23 of 60

24 Installing Double-Take Console Follow these steps to install Double-Take Console on a Windows machine: 1. Go to and download the Double-take executable file. 2. Close any open applications. 3. Double-click the downloaded file to start the installation. 4. Select the language for the software. When the installation begins, the Autorun appears that allows you to install the software and view documentation and online resources. 5. Select any of the product installation links to install the console. Depending on the version of Windows, you must install the following components: One or more Visual C++ security updates Microsoft.NET Framework Note: Ensure that these components are installed on the server. 6. Select Yes to install or enable Microsoft.NET and click Continue. Note: Before installing Double-Take server, you must install or enable Microsoft.NET. 7. Click Yes to check for a later version. 8. Click Next to proceed. The installation program establishes an Internet connection from your server to the Vision Solutions website and lists the latest version. You can select the version that you want to download. 9. Review the Vision Solutions license agreement and accept the license agreement to continue with the installation. 10. Click Next. 11. Review the activation notice. For full product functionality, Double-Take licenses require activation after installation. If you fail to activate licenses, Double-Take jobs fail. 12. Click Next to continue. 13. Select the Client Components Only installation option. The client components do not require a license key. However, licenses are required to administer Double-Take servers throughout the organization. ShoreTel. Brilliantly simple business communications. Page 24 of 60

25 14. Click Change and specify the location to install the Double-Take files, and then OK. 15. Click Next. 16. If Windows Firewall is enabled on the machines where you want to install Double-take Console, select one of the following options to open and reassign any firewall ports for Double-Take: Open only the ports that are not in use Opens any firewall ports that are not in use. The ports that are opened are assigned to Double-Take. Open all ports, reassigning the ports in use to Double-Take Opens all necessary firewall ports reassigning any to Double-Take as needed. Do not configure the Windows Firewall at this time Does not modify any firewall ports. If you select this option, you must manually modify your firewall settings for Double-Take to process. 17. Click Next. 18. Click Install to start copying the Double-Take files. 19. Click Finish when the installation is complete. Configuring Double-Take Availability Follow these steps to configure Double-Take Availability: Open the Double-Take Console. The Servers page appears. On the toolbar of the Servers page, click the Add Servers icon. The Add Servers page appears. ShoreTel. Brilliantly simple business communications. Page 25 of 60

26 Note: You can hover the mouse over icons on the toolbar to view the tooltip. Click the Manual Entry tab and enter the SOURCE server name, local administrator username, and password. Note: You can provide an IP address instead of the SOURCE server name. Click Add. Enter the TARGET server name, local administrator username, and password and click OK. Click Servers on the toolbar of the Double-Take Console to view the licensing status of the servers. The Servers page appears. ShoreTel. Brilliantly simple business communications. Page 26 of 60

27 Note: Double-Take Availability for Windows must have Activation Codes installed to license the software. Double-Take functions for 14 days without activation. For information on adding licenses to the Inventory and assigning them to the SOURCE and TARGET servers, see Double-Take Availability for Windows User s Guide. Installing the ShoreTel Server Software on the Servers For information about setting up the ShoreTel HQ server software on the SOURCE server, see the ShoreTel Server Installation chapter in the ShoreTel 14.2 Onsite Planning and Installation Guide. Configuring the TARGET Server s Primary IP Address After you install the ShoreTel server, you must configure the TARGET server s primary IP address in ShoreTel Director for the HQ Application Server. Follow these steps to configure the TARGET server s IP address in ShoreTel Director: Log on to ShoreTel Director, navigate to Administration > Application Servers > HQ / DVS. The HQ / DVS Servers page appears. ShoreTel. Brilliantly simple business communications. Page 27 of 60

28 Click the Headquarters server. The Edit Server page appears. Enter the TARGET server s primary IP Address in the Secondary IP Address field and click Save. Configuring DHCP for IP Phones After you configure the secondary IP Address in ShoreTel Director, you must update DHCP Option 156 for IP Phones to reflect both servers IP address. For a system that uses only ShoreTel IP400-Series and IP655 phones, you can use an FQDN instead of IP address values that are separated by comma. The format of Option 156 is as follows: vlan=<number>, layer2tagging=<0 1>, configservers=<ipaddress>, ftpservers=<ip address> ftpservers and configservers parameters should be configured to list both the SOURCE and TARGET servers IP addresses (or the single FQDN used by the SOURCE server for systems with only IP400-Series and IP655 phones). Examples: ftpservers= , , configservers= , , layer2tagging=1, vlanid=2 Configuring Distributed Voice Services Servers Installation of the ShoreTel Remote Server software requires the address of the ShoreTel HQ server. You must use the FQDN of the HQ server instead of the IP address when using Double-Take Availability for the main ShoreTel server, regardless of the deployment model. This ensures that no action is required for ShoreTel Distributed Voice Servers (DVSs) to continue operation in the event of a failover. ShoreTel. Brilliantly simple business communications. Page 28 of 60

29 The following figure shows an example using an FQDN instead of an IP address. For information about setting up a DVS, see the ShoreTel Server Installation chapter in the ShoreTel 14.2 Planning and Installation Guide. Note: If Distributed Database is enabled and the ShoreTel DVS has a local database configured, the LocalDBServerAddress points to the DVS and not to the ShoreTel HQ server. Configuring ShoreTel Mobility Router If the ShoreTel system has a ShoreTel Mobility Router, ensure that the configuration for ShoreTel Communicator uses the FQDN instead of the IP Address for the Server Address field as shown in the ShoreTel. Brilliantly simple business communications. Page 29 of 60

30 following figure. Configuring Distributed Database Distributed database (DDB) allows databases to run on the DVS servers for load distribution and survivability. You can use the MySQL replication technology to synchronize data between HQ and DVS. You must manually enable DDB on DVS. When DDB is enabled, the switches that are managed by the DVS read from the DVS DB. Enabling Distributed Database Follow these steps to create a local database: Log on to ShoreTel Director, navigate to Administration > Application Servers. The Application Servers page appears. Select the Local Database check box. A confirmation message appears. Click OK to create a local database. A snapshot of the HQ database is captured in.jpg format and uploaded to the FTP site of HQ, and then DVS server restarts. ShoreTel. Brilliantly simple business communications. Page 30 of 60

31 NOTE: To capture the snapshot successfully, the Virus Scan should exclude the Shoreline Data folder. After DVS restarts, it performs the following tasks: Accesses the FTP server using anonymous login. Downloads the DB snapshot from C:\inetpub\ftproot\Snapshot. Creates a read-only copy of the DB on the DVS server. Updates the LocalDBServerAddress and LocalDBServerID registry keys. Viewing Database Status To view the details of DB for the DVS servers: Log on to ShoreTel Director, navigate to Maintenance > Quick Look. The Quick Look page displays the DB status for the DVS server in the DB column. Click the DVS link. The Distributed Server Maintenance page appears and the Database Connection section displays the DB server IP address and the Local Database section displays the replication status and related parameters. ShoreTel. Brilliantly simple business communications. Page 31 of 60

32 Configuring Physical Switches Follow these steps to configure a physical switch: Log on to ShoreTel Director, navigate to Administration > Application Servers > HQ / DVS. The HQ / DVS Servers page appears. Click the switch link. ShoreTel. Brilliantly simple business communications. Page 32 of 60

33 From the Use Database on Server list, select the database. A message appears asking you to confirm the selection. Click OK to continue. On the HQ / DVS Servers page, click Save. The switch services restart and they update the registry settings on the switch. Note: When DVS switches restart, the configuration information is fetched from the DVS DB. ShoreTel. Brilliantly simple business communications. Page 33 of 60

34 Server Updates Applications subscribe the triggers from the same server as the database host. HQ delivers triggers to DVS through replication. Local updates are done on SIP expiry, CHM settings, and workgroup agent login/logout. When HQ fails, you can still change the settings on DVS. Later, you can synchronize the changes to HQ when it comes online. ShoreTel Server Upgrades While upgrading the DVS server, replication stops in HQ or DVS. After the upgrade, the server updates the my.ini file with DVS s id in the server_id field. After the upgrade of the DVS server, you must: Check the events in DVS to ensure that the replication is started. Change the CHM of the user from IP Phone or MGCP and verify if the change is updated in ShoreTel Director to ensure replication is in process. Comparison between HQ and DVS during an upgrade The following table describes the changes in HQ and DVS during an upgrade of HQ or DVS severs, respectively. HQ DVS Stops the Replication Stops the Replication Overwrites the files at C:\Shoreline Data\DB\MySQL Performs a DB backup and stores the files at C:\Shoreline Data\DB\MySQL. Updates the my.ini file at C:\Program files(x86)\shoreline Communications\Shoreware Server\MySql Config\MySql Server Updates the my.ini file at in C:\Program files(x86)\shoreline Communications\Shoreware Server\MySql Config\MySql Server Starts the MySql service Starts the MySql service Creates a Route password for MySql Creates a Route password for MySql Creates UDF for MySql Creates UDF for MySql ShoreTel. Brilliantly simple business communications. Page 34 of 60

35 HQ DVS Creates a Loopback account Creates a Loopback account Upgrades the database and creates mysql users Upgrades the database and creates mysql users Starts the KU at the end of the installation and the snapshot of DB is taken and is uploaded at ftp root and C:\Shoreline Data\Database\SnapShot Starts and resynchronizes the KU Limitations Distributed Database (DDB) and Distributed Workgroups are not supported on the same system. Replication may stop if you change the DVS server name. This is because the server name is used as a part of the log file name unless you specify a name for my.ini. To avoid the replication from stopping, delete relay-log.info from the C:\Shoreline Data\Database\ShoreTelConfig\Data location. This wipes out the old log file name, and resynchronizes again. For the DDB to function properly, you must disable DEP (Data Execution Prevention) on all servers. If you are a remote user and if the mailbox is on HQ, there are no local updates. It directly goes to HQ. So when HQ is down, there are no local updates because it uses CSIS which communicates to mail box server (in this case HQ server) which then writes to the HQ DB. However, the same behavior does not apply from IP phones because it follows a different path using TMS server. When HQ is down, do not access MCM from remote server for provisioning, changing CHM, and so on. This is because MCM always talks to HQ. The following table describes the local updates in the DVS DB when HQ is down and DVS is online and has local DB. Application or Device Change CHM Change WG Agent state IP Phone TUI YES YES Voice Mail YES YES PCM YES YES ShoreTel. Brilliantly simple business communications. Page 35 of 60

36 Application or Device Change CHM Change WG Agent state MCM no no WCM/WCM Options Yes Yes WonderPhone YES YES WebClient (Old) (deprecated in TB) no no TroubleShooting If the services are not running Check the Servers page to ensure the log detail is same on HQ and DVS servers. Check the registry settings on DVS. Check the registry settings on the switch. Use the SQL command "SHOW SLAVE STATUS;" and "SHOW MASTER STATUS;" to check the replication status. Verify the my.ini file on the DVS. The file is located at Program Files\Shoreline Communications\ShoreTel Remote Server\mySQLConfig\MySQL 5.0. Ensure that the server-id value is not set to 1. If DDB is enabled, the server-id value is same as the server-id of the DVS server. You must set this value to 1 only for the HQ server, which is the master. Check the error file that is created under Shoreline Data\Database\Data\MySQL 5.0 Use the UpdateLog table on the DVS DB for synchronization when HQ comes online after a failure because when HQ is down, the local updates are written to this table. Ensure that FTP service is running. The snapshot is sent to the DVS servers using FTP service. If replication has stopped Log on to ShoreTel Director and navigate to Maintenance. Select the DVS for which the replication stopped. Resynchronize DB on DVS. ShoreTel. Brilliantly simple business communications. Page 36 of 60

37 If the issue persists, get snapshot on HQ. Resynchronize DB on DVS again. If the issue persists, on the Application Servers page, disable and enable DDB. Configuring Job Properties Follow these steps to configure the job properties when reverse protection is required and two NICs are used: Open the Double-Take Console. On the toolbar of the Servers page, select the SOURCE server. Click the Create a New Job icon and click Protect. The Choose Data page appears. From the list of Workload types, select the Full Server option. From the Workload items list, select all the disks. Expand the Replication Rules section and in the Folders section, navigate to the Shoreline Data folder. Select the Logs folder. The Path field displays the navigation path of the Logs folder. ShoreTel. Brilliantly simple business communications. Page 37 of 60

38 To improve replication performance and save bandwidth, select Exclude from the list next to the path field to exclude the Logs folder and then click Add Rule. Click Next. The Choose Target Server page appears. From the list of servers, select the TARGET server and click Next. The Set Options window appears. Edit the necessary options. Double-Take automatically displays a job in the General section. You can enter a new name, if required. Expand the Failover Monitor section to adjust the settings for the following options: Total time to failure The time taken to restart the ShoreTel server without triggering a failover. ShoreTel. Brilliantly simple business communications. Page 38 of 60

39 The default time is too less. Instead, 10 minutes is an ideal time. For system upgrades, we recommend that you pause the TARGET server. To pause the TARGET server, on the toolbar of the Manage Jobs window, click the Pause button. Network Monitoring You must ensure that this option is selected. You must monitor only the SOURCE server s primary IP address. Therefore, select only the primary IP address from the list. Expand the Failover Options section and perform the following steps: i Ensure that the Wait for user to initiate failover option is selected. Note: If the Wait for user to initiate failover option is not selected, automatic failover is enabled, which can result in an undesired failover, if the failover monitor triggers a false positive. ii Download the FixIPAddress.exe utility from and copy it to the same folder path on both the SOURCE and TARGET server. The name of the folder on both the SOURCE and TARGET server must be the same. For more details on the Failover script, refer to Appendix A. After Failover is complete, FixIPAddress.exe runs and updates the registry values and the monitoring service INI file with the TARGET server s primary IP address. Expand the Failover Identity section and select the network configuration option that is appropriate for the deployment model: ShoreTel. Brilliantly simple business communications. Page 39 of 60

40 For the Full Server Protection option without Reverse Protection, select Apply source network configuration to the target (Recommended for LAN configuration). For both deployment models with Reverse Protection, select Retain target network configuration (Recommended for WAN configuration). We recommend that you enable the Update DNS server option. Enter credentials for a user account with administrator rights to update the DNS database along with a list of DNS servers. You must update only the primary DNS server that manages the forward lookup zone for the domain that is used for the ShoreTel servers. If there are multiple servers in your environment, the zone replication time varies based on configuration and technology. Enter the IP addresses of the SOURCE and TARGET servers in the Update these source DNS entries with the corresponding target IP address field. Note: If you do not configure Double-Take to automatically update DNS during failover, the administrator must update DNS manually to allow continued operation of the ShoreTel system. Expand the Reverse Protection section and perform the following steps: ShoreTel. Brilliantly simple business communications. Page 40 of 60

41 i ii Select Enable reverse protection or Disable reverse protection based on the deployment model type. Set the reserved IP addresses of the SOURCE and TARGET servers by selecting them from the drop-down lists. Note: You must select the secondary IP address configured for each server as the reserved IP address. Expand the Network Adapter Options section and perform the following steps: ShoreTel. Brilliantly simple business communications. Page 41 of 60

42 i ii Validate that the mappings of the SOURCE and TARGET Network Adapters are correct. Ensure that the primary NICs are matched between SOURCE and TARGET, as well as the secondary NICs. Expand the Mirror, Verify & Orphaned Files section and perform the following steps: i ii In the General Options section, select the Calculated size of protected data upon connection and Delete orphaned files. Select the Enable scheduled verification option for enhanced data security. For more information about the security, see Double-Take Availability for Windows User s Guide. Expand the Snapshots section and select Enable scheduled snapshots and set the desired interval. Double-Take takes snapshots of the SOURCE server s data that is replicated on the TARGET server. ShoreTel. Brilliantly simple business communications. Page 42 of 60

43 Note: You must consider the additional storage required on the servers when planning the SOURCE and TARGET servers disk sizes. If Enable scheduled snapshots is selected, Double-Take displays a list of snapshots that are used when failover is initiated. Expand the Compression section and perform the following step: Select Enable compression and select a compression level for data copied from SOURCE to TARGET. Expand the Bandwidth section to control WAN utilization and perform one of the following steps: To limit the bandwidth for the entire day, select Use a fixed limit (bytes per second). ShoreTel. Brilliantly simple business communications. Page 43 of 60

44 To restrict bandwidth that is used by Double-Take during business hours, select Use scheduled limits and set the days of the week and time of the day. Click Next. The Summary page appears. Double-Take validates the settings and reports any issues. Click Finish when all items appear with a green check mark. The job starts automatically. Managing Jobs Follow these steps to start the process of mirroring, replication, and monitoring: On the toolbar of the Double-Take Console, click Jobs. The Jobs page appears. ShoreTel. Brilliantly simple business communications. Page 44 of 60

45 On the toolbar, click the play button to start the process of mirroring, replication, and monitoring. It takes several minutes to copy the necessary data from the SOURCE to the TARGET server for the first time. When the system is operating, the value in the Activity column is Protecting and the value in the Mirror Status column is Idle. You can click the pause or stop button to pause or stop the job, respectively. Environment Evaluation It is critical to determine the amount of overall throughput available for Double-Take deployments where SOURCE and TARGET servers are set up across a WAN. Throughput, which is not the same as bandwidth, is a function of TCP Window Size and round-trip latency. Throughput is determined by the following calculation: TCP Window Size in bytes / round-trip latency The default TCP Window Size is 64 KB or 524,288 bytes. For example, on a WAN with a round-trip latency of 45 ms between the servers, then /.045 = 11,650,844 bps or 11.7 Mbps. This is the maximum throughput even if the available bandwidth is greater. Double-Take enables you to simulate protection in a simple way in order to generate statistics that are used to approximate the time and amount of bandwidth that a particular source and job type uses when it is established. This simulation uses the Throughput Diagnostics Utility (TDU), which is a built-in null (nonexistent) target that simulates a job. No data is actually transmitted across the network. The diagnostics utility helps you plan your implementation strategy because there is no true job. Before and after simulating a job, you should gather network and system information specific to Double-Take operations. To evaluate Double-Take log files, use the Double-Take Console to collect the following data: Double-Take and system settings Network configuration information such as IP, WINS and DNS addresses, and other data ShoreTel. Brilliantly simple business communications. Page 45 of 60

46 Evaluating Environments Follow these steps to evaluate an environment: In the Double-Take Console, right-click the source on the Servers page, and select Gather Support Diagnostics. Specify a location to store the zipped diagnostics information. It may take several minutes for the diagnostics to finish processing. After the process completes, a.zip file is created, which contains the gathered information. The file name is based on the machine name. Consider the following requirements to establish job protection: When selecting the target, select the Diagnostics job option instead of a TARGET server. The Set Options page does not display few options for the selected job type because they are not applicable. (For example, target-specific selections are not displayed because there is no actual target with the TDU.) Run the job for several days to gather accurate data for your network and source server usage. The simulation data is logged to the Double-Take statistics file. For more information about DTStat, see Double-Take Reference Guide. Repeat step 1 and 2 to gather diagnostics again after the simulation is complete. You can use the Diagnostics connection job type within the Double-Take Console to perform the following tasks: i Create a connection to monitor the amount of change that is generated over time. However, no data is actually transmitted. ShoreTel. Brilliantly simple business communications. Page 46 of 60

47 ii iii iv Most job options, such as compression and bandwidth limits, are available to view the behavior during production. Leave this job running for a few days or a week to get a good amount of data and then delete the job. The gathered data is stored in the connect.sts file on the SOURCE server in the Double-Take installation directory. Perform the following steps to convert the statistic.sts file to a CSV file: a b Enter the following command in the command prompt window: DTStat p f statistic.sts s statistic.csv Ensure you can write to the installation directory without a UAC prompt. This converts the file to something that is readable by Excel. Open the file in Microsoft Excel. The following figure shows an example of collected statistics showing the amount of data that are transmitted. For detailed descriptions of all columns in the file, see the Double-Take Availability for Windows User s Guide. The following figure shows statistics indicating that there is insufficient bandwidth where data is stored in the replication and disk queues. ShoreTel. Brilliantly simple business communications. Page 47 of 60

48 If protecting across a WAN environment, consider the following guidelines before enabling compression: The best compression setting is medium. Do not use another device, such as a WAN Accelerator, to compress data. If there is limited bandwidth or throughput, enable the bandwidth limits to minimize network impact while considering the following conditions: Bandwidth limits are per job and are not shared among multiple jobs. To limit bandwidth for all Double-Take jobs from one site to another, consider using QoS. The disk queue enables you to track the changes. You can use unlimited memory queue and you need to optimize it if queuing to disk is expected based on diagnostics testing. For slightly more efficient queuing, you can increase the queue file size from 5 MB to 50 MB by modifying a registry key. The key is called QJournalFileSize and the key value is in hexadecimal and is found in the Windows Registry at: HKEY_LOCAL_MACHINE\SOFTWARE\NSI Software\Double-Take\CurrentVersion You must not put the disk queue on the same physical devices that contain the data being replicated. For best results, put it on a dedicated array optimized for writing, if possible. A single dedicated disk is probably ShoreTel. Brilliantly simple business communications. Page 48 of 60

49 better than a shared RAID 5 array. Best Practices The following implementation tips can help you achieve the best performance from Double-Take: Anti-virus Disable real time scanning of the Double-Take queue directory on both servers. Exclude the Double-Take queue directory from any scheduled system scan on both servers. Disable real-time scanning of target data, if possible. Target Path Blocking Target Path Blocking prevents the modification of data on the target server until failover has occurred or protection is disabled. You can set up Target Path Blocking based on the connection or on the TARGET server for all the connections to that server. If the Send data only if Source is Newer than Target mirror type is used, we recommend that you enable Target Path Blocking. High Latency and/or Low Bandwidth Environments In high latency or low bandwidth environments, increase Mirror Packet Size to 128 K and MaxChecksumBlocks to 64. You can find the Mirror Packet Size option on the source tab in the properties of the SOURCE server. MaxChecksumBlocks is a registry key located in the following path: HKEY_LOCAL_MACHINE\SOFTWARE\NSI Software\Double-Take\CurrentVersion MTU Packet Size for Windows The Default MTU size for Windows is If the value is too high, packets are fragmented. Fragmented packets can slow down mirroring and replication and break the connection. These messages are displayed in the Double-Take logs. To check if the default MTU size is correct, ping between the SOURCE and TARGET server, using -f and -l. For example, if we consider the MTU size of Windows as 1500, use the following command to ping the SOURCE and TARGET servers: ping <ip_address> -f -l The following figures show a successful ping command and one that resulted in an error, respectively. ShoreTel. Brilliantly simple business communications. Page 49 of 60

50 If this error occurs, try using a smaller value, as in the following example: ping <ip_address> -f -l 1464 To view all the network interfaces along with the current MTU on each, use the following command: netsh interface ipv4 show interfaces To make the MTU 1464 persistent, use the Idx number of the interface in the quotes in the following command: netsh interface ipv4 set subinterface "10" mtu=1464 store=persistent Other Recommendations The hardware device drivers (especially NIC drivers) must be up to date. Reset the port speed and duplex on NICs and switches, if possible. If you are protecting from one workgroup server to another or from one domain to another, select the Replicate NTFS security attributes by name in the Source section of the Edit Server Properties ShoreTel. Brilliantly simple business communications. Page 50 of 60

51 window. This ensures that permissions that are associated with the account name are replicated and not the permission of the SID. The Move deleted files to this folder option enables you to recover the files that are accidentally deleted on the source as they are moved to a specified location on the target for a specified time. We recommend that you enable this option as an additional protection. Before you enable this option, you must ensure that there is sufficient space on the folder specified to store the deleted data. For example, if 100 GBof data is deleted from the source, 100 GB of data is written to the specified location on the TARGET. If you want to receive alerts through s about any issues with Double-Take, you can configure the notification in the Notification section of the Edit Server Properties window. You can exclude types of messages that you want to ignore. ShoreTel. Brilliantly simple business communications. Page 51 of 60

52 For information about the All Event IDs that trigger alerts, refer the Monitoring Tools chapter of the Double-Take Availability User s Guide. Failover A complete failover includes the following processes in the given order: Failover Reverse failover The following table describes the roles of the servers and their statuses during the failover process. ShoreTel. Brilliantly simple business communications. Page 52 of 60

53 When the SOURCE fails, the Activity column on the Jobs page displays Failover condition met or Protecting. Process 1: Failover When the SOURCE fails, the TARGET server stands in for the SOURCE by restarting and applying the SOURCE s system state on the TARGET. After it restarts, the TARGET becomes the SOURCE. Follow these steps to initiate the failover process: On the toolbar of Double-take Console, click Jobs. The Jobs page appears. On the toolbar, click the Failover or Cutover button. The Failover and Cutover dialog box appears. ShoreTel. Brilliantly simple business communications. Page 53 of 60

54 Select one of the following options based on the requirement: Failover to live data Select this option to initiate a full live failover using the current data on the target. The SOURCE automatically shuts down if it is running and then the TARGET stands in for the SOURCE by restarting and applying the SOURCE identity, including its system state on the TARGET. After the TARGET restarts, the TARGET becomes the SOURCE and the original TARGET no longer exists. Perform test failover Select this option if the TARGET is a virtual server. It is similar to live failover, except the SOURCE is not shutdown. Therefore, you should isolate the virtual server from the network during the restart process. Otherwise, you will receive error messages after the restart. If you do not isolate the virtual server, you can ignore the conflict messages. Before selecting this option, you should take a snapshot of the virtual server. After your test is complete, you must revert to the snapshot. Failover to a snapshot Select this option to initiate a full live failover without using the current data on the TARGET. Instead, select a snapshot and the data on the TARGET is reverted to that snapshot. This option is not available if there are no snapshots on the TARGET or if the TARGET does not support snapshots. This option is also not applicable to clustered environments. The following types of snapshots are displayed in the Type column. o o o Scheduled Part of periodic snapshot. Deferred Part of a periodic snapshot, although it did not occur at the specified interval because the job between the SOURCE and TARGET are not in a good state. Manual Click Failover. Snapshots that are manually taken by the user. The Jobs page displays the state of the failover process. ShoreTel. Brilliantly simple business communications. Page 54 of 60

55 The process takes several minutes to apply the replicated data to the TARGET, and then the TARGET restarts to complete the process. Actual time depends on the network and server performance. Post Failover Actions After failover, in some environments, Double-Take services may not start in their correct order following a server restart. If the "Could Not Determine Activation Status" or Target Management Service Cannot Communicate to Source message appears during a server maintenance, perform the following tasks on the TARGET: Before the TARGET restarts, perform the following on the TARGET: Stop the Double-Take service first, and then the management services. Change the startup type on both the servers to manual. Restart the TARGET. After all the Windows services are fully loaded, type services.msc in the Start Search field, and then press Enter. The Services window appears. Change Double-Take service startup type to Automatic and then start Double-Take service always first. Change Double-Take Management service startup type back to Automatic (Delayed Start) and then start the service. For Double-Take issues, refer to the Vision Solutions website. After failover, you may need to reactivate your Windows registration after failover because the Windows product activation is dependent on the hardware. When you are using Windows 2008 or 2012, the reactivation depends on several factors including service pack level, Windows edition, and the licensing type. If a TARGET that is Windows 2008 or 2012 is online after failover with an activation failure, the steps vary based on the license type. Double-Take automatically configures the job with the same settings as set initially and starts data mirroring and replication. Additionally, if you are using Windows 2012, you might have only 60 minutes to complete the reactivation process until Windows activation tampering automatically shuts down your server. For steps to reactivate Windows, see the Failing over full server jobs section of the Double-Take Availability for Windows User s Guide. ShoreTel licensing is based on a System License Key that is tied to the original SOURCE server. After failover, ShoreTel determines that the System License Key is not valid and starts the 45-day lockout timer. For information about how to request a new System License Key for the TARGET server post failover, see the Obtaining Licenses section of the ShoreTel 14.2 Planning and Installation Guide. To verify if the DNS is changed on the servers, run ping against the FQDN. To flush the local cache resolver in Windows if needed, you can run the ipconfig /flushdns from Command Prompt as an Administrator. ShoreTel. Brilliantly simple business communications. Page 55 of 60

56 Process 2: Reverse Failover Reverse failover is a process that reverses roles of the old SOURCE and TARGET server such that the old TARGET server becomes the new SOURCE as HQ runs on it and old SOURCE becomes the new TARGET server as no TARGET was present after the first failover. Follow these steps to reverse the roles: On the toolbar of the Jobs page, click the Reverse button. A message displays asking you to confirm if you want to perform the reverse operation. Click Yes to proceed. The process takes several minutes and results in the SOURCE and TARGET roles running on the servers. Actual time depends on the network and server performance. After this process, restore continues to replicate data between the new SOURCE and TARGET; it takes several hours to complete. Failback Failback is the process of bringing back the servers to their original roles such that the old SOURCE server and old TARGET server are the current SOURCE and TARGET servers, respectively. To perform a failback, you must perform another complete failover, which includes a failover and reverse failover. The complete failback includes the following processes in the given order: Failover Reverse failover Failover Reverse Failover The following table describes the roles of the servers and their statuses during the failback process. ShoreTel. Brilliantly simple business communications. Page 56 of 60

57 Appendix A: Failover Script Double-Take copies all registry settings from the SOURCE to the TARGET server as part of the failover process, which results in ShoreTel services not being able to bind to the correct IP address. This only applies to the deployment scenarios where two NICs are used for Reverse Protection. The FixIPAddress.exe utility was developed using Visual Studio 2010 with Visual Basic.NET using version 4.0 of the framework. The application finds the primary IP Address configured and updates two ShoreTel registry values that store the IP Address of the current server. You can download the utility from the following location: The failover process replicates all registry keys, sub-keys, and values from the SOURCE server. The ShoreTel server installation software creates HQServerAddress and LocalDBServerAddress values that store the primary IP address as shown in the following figure. During failover, Double-Take copies these values and data over to the TARGET. ShoreTel Diagnostics and Monitoring uses a separate MySQL database instance to store its data and the IP address for the host server and is stored in an.ini file. Double-Take replicates this file to the TARGET server. ShoreTel. Brilliantly simple business communications. Page 57 of 60

58 However, the file contains the SOURCE server s primary IP address as shown in the following figure. You must run FixIPAddress.exe prior to restarting the server. When you run FixIPAddress.exe, the registry values are updated and the TARGET server s primary IP address is updated to the ShoreTel Monitoring service.ini file. By default, scripts run on the Double-Take service account. If the SOURCE and TARGET servers are part of an Active Directory domain, the account needs permissions to run the script. Verifying Scripts Follow these steps to ensure that the scripts run: Open the Double-take Console. Right-click on each server, select View Server Details, and then select Edit Server Properties. The Edit Server Properties page appears. ShoreTel. Brilliantly simple business communications. Page 58 of 60

59 Expand the Script Credentials section and enter the credentials. Click the Test button to verify the credentials. After the test, the Password field becomes blank, but the password is saved. Click OK to save. Additional Resources ShoreTel 14.2 Planning and Installation Guide ShoreTel 14.2 System Administration Guide Vision Solutions Double-Take White Papers: Double-Take Availability for Windows documents are available in the CustomerCare section of Vision Solutions Support Central at You must have a Support Central account to access the documents. Document and Software Copyrights Copyright 2016 by ShoreTel, Inc., Sunnyvale, California, U.S.A. All rights reserved. Contents of this publication may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without prior written authorization of ShoreTel Communications, Inc. ShoreTel, Inc. reserves the right to make changes without notice to the specifications and materials contained herein and shall not be responsible for any damage (including consequential) caused by reliance on the materials presented, including, but not limited to typographical, arithmetic or listing errors. Trademarks ShoreTel, Inc., ShoreTel, ShoreWare, ShoreGear and ShorePhone are trademarks of ShoreTel, Inc.in the ShoreTel. Brilliantly simple business communications. Page 59 of 60