At this moment we have two sides, Side-A and Side-B. Side-A has 5 Subscribers and one Publisher where Side-B has 3 Subscribers having clustering over the WAN. Now we want to separate the clusters and for this we need one Publsiher at Side-B. Can anybody suggest a safer way to do this in production environment without any loss of data?
If you are talking about splitting one CallManager into 2 clusters, then you will need to rebuild one of the subs as site B as a publisher, and the other subscribers to point to this new Pub.
Not sure what data loss are you referring to as all data is on the Publisher, so obviously you will need to configure the second cluster from start, by adding all entities, i.e. device pools, calling search spaces, paritions, etc.
You can add a new one or rebuilt one all together, however the new pub will have to be completely reconfigured. Not sure if you would be able to do a BARS backup of the current pub and try to restore it in the new pub, I doubt this would work.
You seem to know what you are talking about. If I were putting in a new cluster and I had (2) datacenters that were active/active. I know I can split the cluster if my roundtrip time is ok (40ms) (1) pub and (x) subs.
for example, I had (1) pub and (3) subs at the primary datacenter and (4) subs at the secondary datacenter. Im sure this would work, but Im wondering how it works with (2) Pubs, or does it not work this way? I thought you could setup a cluster with (2) Publishers config in larger clusters.
Two data center separation means two separtae clusters and for this one publisher for one cluster. Itold you guys before we have one publsiher already and going to install new one for another side which only have 3 subscribers at the moment and the question is how to point 3 subscribers to this new publisher and how to transfer all data to this new publsiher?
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...