Primary and DR Site Introduction Question
Hello All............When caught up in the situation where you are doing migration from 2010 to 2013 and some of the users are also moved into the new 2013 environment and you need to introduce DR Site as well, what would be best approach to test out the DR Site first before moving users or continue with the user migration to 2013 and once they are done, move other resources to 2013 as well and cut off from 2010 completely and then after all is ready at 2013 move with the DR Site pairing, configuration and testing?
September 14th, 2015 8:34am

Hi

As you have already got users on 2013 you cannot really test the pool pair without affecting them in some way. What you could do is move the 2013 users back to 2010 temporarily, build your pool pair and then perform failover between pools with some test users. The CMS will be (or should still be) on the 2010 server, so you cannot test CMS failover until you move the CMS over to 2013. But as the CMS move is the last thing you do it is not something you can test in a sterile environment. Having said that you do get 30 minutes grace period before users are placed into limited functionality mode so you can test on a live system with no effect on users as long as you've done it right.

thanks

Free Windows Admin Tool Kit Click here and download it now
September 14th, 2015 10:28am

Thanks for the reply; appreciate it.

So, basically you are suggesting that I should move the users back to 2010 and configure pairing, test it and then move ahead with the user migration.  This would be your recommended approach. Kindly, confirm.

On the other hand, as an option, you are suggesting that in order to fully test the failover capability along with CMS, we can go ahead with the user migration first, cut off 2010 then configure pairing and test complete failover capability with CMS failover as well?  Kindly, confirm.

That leaves me very confused.  I am more enticed by the second option because that would mean we would have tested completely rather than just user failover?  Please, confirm.  And also do you vote for number 1 or 2.  :)

thanks in advance.

September 14th, 2015 4:02pm

Hi,

As Lync Pool Pairing is for Lync Server 2013 but not for Lync Server 2010, so you need to deploy two Lync Server 2013 pools (or two Lync Server 2013 Standard Edition) and perform pool pairing. After this, you can test pool failover and failback function between Lync Server 2013 environment.

If there is no issue for Lync Server 2013 pool pairing, you can finally move CMS to Lync 2013 pool and then, you could test pool failover and failback including CMS. If all works as normal, then you can delete Lync Server 2010 pool.

Best R

Free Windows Admin Tool Kit Click here and download it now
September 15th, 2015 2:33am

Hello Eason,

                 Actually, what I am trying to get a recommendation for is about the introduction of the DR Site.  That what would be appropriate time.  I am at a certain point right now as well with Primary Site in place and users (some of them) moved.  So, I introduce it now or once all is done.

September 15th, 2015 3:13am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics