Replacing SFB 2015 SQL backend in pool pairing design
Hi All, Quick question: I am replacing SQL backend for a SFB Ent infrastructure in pool pairing design. First off, thinking of breaking the pool pairing, uninstalling the CMS replica in DR and then switching the SQL instance in the topology to new one and publishing it back. Post that, deploy the CMS replica back in to be able to move it from Prod to DR later. In order to replace SQL for Prod pool, I plan to free it up moving the following (in order listed) to DR pool. -Response Groups - Export/Import -Move Users -Dialin conf numbers -Meeting Rooms -Move Common Area Phones -Conferencing directories -ExUmContact -Move CMS Please advise if my approach is correct and if I am missing anything or moving something in this list that's not needed. Thanks, Az