New- need to migrate from datacenter Management server on Azure cloud on same version R81.10

[Bucktips34]

Hi Experts,

need your guidence on documents and steps to migrate checkpoint management  server from datacenter to Azure cloud. we have almost 20 gateways managed by existing single management server and currently SIC is established via global rule.
As per plan we are using migrate export & import and changing only Ip address on new ip management address. Will they be distruption while import database file. Kindly guide me the steps for smoother migration. 

[Nir_Shamir]

Hi,

Exporting the DB might take the services of the Management Server to DOWN state, but this won't affect your GW's traffic.

the import of course won't cause any disruptions.

After the DB migration , you just need to make sure the GW's can communicate with the new Management Server , SIC will not be affected between the GW's and the Old and New Management Server (no need to Reset SIC).

I don't know how the current Management Server is configured but you will need to configure the GW's to work with a Management Server behind NAT. See these SK's for more information:

https://support.checkpoint.com/results/sk/sk66381

https://support.checkpoint.com/results/sk/sk100583

[Bucktips34]

Thanks for your response, 

Question: SIC will establish before importing database or after importing the database file on new management server?

Currently, Existing mangement server object is using Hide NAT for all the gateways and SIC is establish with NATED IP . we have some remote VPN side with Public IP it is establish with public IP ( not with NATED IP ) of old Management server , as per logs they are using implied rules.

the new we are planning migrate on azure (new management ) we would like to establish sic with private IP with gateways and for remote VPN side with public IP (we can use Hide NAT to communicate) you suggestion is much appreciated

Note: we can't us static NAT as we have CP gateways in VMSS on azure.

Thanks

[along5664]

We did this a few years back and now are moving back to onprem .

I am in process of moving back from cloud to onprem now for sms.

Here is how we do it.

We create a new SMS and make it HA with the existing one. Make sure the new one has access to all the gateways.

Once confirmed you can promote the new ha to become the primary. 

[Bucktips34]

To create a HA both Management Server should have unique name and IP address (in same subnet). we are using same object name but different subnets/IP address.

[along5664]

We have done this with HA and ours are not on same subnet, but they do have different names.

I have gone from on prem say 172.27.144.x to AWS 10.63.27.x without issues. We then moved from AWS to Azure and I went from 10.63.27.x to 10.250.27.x. Names changed as did the ip, and it worked just fine.

[PhoneBoy]

Management HA does not require nodes to be in the same subnet UNLESS it's a Full HA configuration (then the ClusterXL requirement for this applies).
See: https://support.checkpoint.com/results/sk/sk39345