Forum Discussion
Solved
MIP On-Prem Scanners Migration
Hi, We have around 33 On-prem scanners in clustered mode along with SQL DB clustering in on-premise environment deployed across multiple regions i.e. APAC, North America & Europe. We need to migrate...
Hey rajatwadhwa,
No worries at all! I hope you had a great vacation.
Regarding your question, it’s usually better to add the new on-prem scanners to the existing Purview cluster to minimize business impact and downtime during the cut-over. This way, you can maintain continuity without having to reconfigure everything. However, if the infrastructure in the new data center is significantly different or if you need a fresh start, creating a new Purview cluster might be a better option, though it could involve more planning.
I’d suggest considering the current cluster setup and whether it can handle the new scanners with minimal disruption.
Hope it helps!
Hi luchete,
Thanks for your response. Link you have shared is towards the fresh build of on-prem scanner. I would like to know migration approach from one data center to another? Also, would like to know if we need to migrate on-prem scanner clusters, shall we rebuild those in new data center & then restore configurations or do a move of those virtual machines retaining same configuration? What should be approach for SQL DB cluster migration as well? Is there any migration document for on-prem scanner architecture?
Gotcha, for migrating your on-prem scanner clusters to a new data center, you have two main options. You can either rebuild the scanners in the new data center and restore the configurations, or you can move the virtual machines (VMs) along with their existing configurations. If you choose to move the VMs, make sure the network settings and IP addresses are compatible with the new environment. If there are significant differences in infrastructure, rebuilding might be a more reliable option.
For the SQL DB cluster migration, you’ll need to ensure the new data center supports your SQL clustering setup. It's important to follow SQL Server clustering best practices to properly handle data and transaction log migration.
The general MIP scanner documentation should still help with the reconfiguration once the scanners are moved. Do you have the option to contact straight Microsoft support for more tailored guidance on your specific setup?
Hi luchete ,
Sorry for delayed response as I was away on vacation. Thanks for your response. I will check on Microsoft support if we can leverage that. By any chance, do you think once new on-prem scanners are build in new DC & sql db reconfigured in new data center, we should add on-prem scanner nodes to existing purview cluster or create a new purview cluster? which option would be better from cut-over perspective & to avoid minimal business outage or impact?
Hey rajatwadhwa,
No worries at all! I hope you had a great vacation.
Regarding your question, it’s usually better to add the new on-prem scanners to the existing Purview cluster to minimize business impact and downtime during the cut-over. This way, you can maintain continuity without having to reconfigure everything. However, if the infrastructure in the new data center is significantly different or if you need a fresh start, creating a new Purview cluster might be a better option, though it could involve more planning.
I’d suggest considering the current cluster setup and whether it can handle the new scanners with minimal disruption.
Hope it helps!
luchete, Thanks a lot for your response. Very useful indeed. Thanks again for giving time to reply back.
