subject: Configure ShoreTel For Redundancy, Resiliency Or Business Continuity [print this page] Configure ShoreTel For Redundancy, Resiliency Or Business Continuity
Of late we've got seen an evergrowing curiosity about building "disaster recovery" solutions for both the data along with the voice applications so crucial for business operation. First, discovered ensure we understand the visible difference between redundancy, resiliency and various configuration choices to assure business continuity. Many more installations now include the usage of an online "collocation" facility for an key component from the installation plan. What is the fastest way to configure a ShoreTel HQ server, for example to offer for continued operation with a wide variety of options.
The subject of redundancy is sort of amusing occasionally. The amount redundancy is reasonable and appropriate? You will get the many redundancy your financial budget can fund, but by the end during the day can you continue this business operation in case of a catastrophic event. Clearly, two power supplies are better than one. Should they be both connected to a similar commercial power outlet however, it truly will likely not matter the number of power supplies you have when you lose commercial power! Again, we must target the definition of we wanting to protect?
By way of example, there is absolutely no law that says you cannot put in a ShoreTel Distributed Voice Mail server on the same level as the ShoreTel HQ server. Actually this works properly! Install the servers at the same physical location, or squeeze HQ server within the remote "collocation" facility. Should they be installed on the same "logical" level (i.e. be visible on precisely the same level inside the Shoreware Director, either server are equipped for the stress. Generally, you will invest from the users and switches for the site under the DVM and employ the HQ as the "fail up" and proxy solution. Nothing wrong using this configuration, it truly is economical as well as simple to administer. Every now and then you could hear ShoreTel say "please wait while I connect you to the correct server" but even which might be managed.
ShoreTel HQ has three services that are not distributed: Route Points; Account Codes and Workgroups. Should you lose th HQ server, you may lose these services, but generally it really is a small investment in this volume of resiliency! ShoreTel Version 10 promises to distribute these facilities, so there's no reason to never configure that way and achieve full survivability given your building remains to be standing.
You won't need to think al all long in terms of a Katrina or Haiti, notably if you have a home in California! It is simply prudent to never only policy for some level of "redundancy", but to cover the way the business would operation if you can easliy not start our building! If we put the HQ server at the "collocation" facility and then we give to Trunk Lines and "dial tone", we could balance this possibility. The thing is, that if your building housing individuals becomes unavailable, users can nevertheless sign in and route their phones to phones or utilize RDP to reach their Call Managers.
The "collocation" option often takes an upside between band width and trunk lines. You may invest your trunk lines in the colo, in that case every call produced from services, will traverse a WAN. So moving the trunk lines towards the colo increases resiliency but additionally drives your WAN cost. By the end through the day it is most likely some mixture of bandwidth and trunk lines spread between your facilities. In any case, you are going to talk with your carrier allow lines being repointed in the event of an outage. This is a little more challenging should you be in The big apple and your collocation facility is due to Phoenix, but it surely can be performed.
