- Products
- Learn
- Local User Groups
- Partners
- More
Scaling Check Point Automation with Arodonata
7 October @ 5pm CET / 11am EDT
What's New in Check Point SASE
The State of Ransomware Q2 2026:
This Quarter's Trends, and Their Impact on Your Defenses
AI Security Masters
Implementing the AI Security Trifecta
CheckMates Go:
Half is Not Enough
Morning,
I will need some support to move my Policy Manager actually under a physical Appliance to a VM.
My trouble is :
For the moment my physical Appliances are used for Policy manager/log/endpoint server (HA), I would to keep under those Appliances LOG and Endpoint Server and keep the actual IP.
and move only Policy manager Role under a new VM with new IP.
My Understanding is :
Install new policy manager Under my vm
export/import database under new vm
link all the Gateways to the new Policy manager ip
probably need to change all licences as they have a new ip for the PM.
But
How can is say to the gateways that the log server is Under a different IP.
and most important part should I rebuild completly my pysical Appliances (log/enpoint)or can I just remove PM role?
Attached a drawing to explain probably better what I would like to do.
Many thanks for your support.
Ben.
Morning,
I will need some support to move my Policy Manager actually under a physical Appliance to a VM.
My trouble is :
For the moment my physical Appliances are used for Policy manager/log/endpoint server (HA), I would to keep under those Appliances LOG and Endpoint Server and keep the actual IP.
and move only Policy manager Role under a new VM with new IP.
My Understanding is :
Install new policy manager Under my vm
export/import database under new vm
link all the Gateways to the new Policy manager ip
probably need to change all licences as they have a new ip for the PM.
But
How can is say to the gateways that the log server is Under a different IP.
and most important part should I rebuild completly my pysical Appliances (log/enpoint)or can I just remove PM role?
Attached a drawing to explain probably better what I would like to do.
Many thanks for your support.
Ben.
Morning,
I will need some support to move my Policy Manager actually under a physical Appliance to a VM.
My trouble is :
For the moment my physical Appliances are used for Policy manager/log/endpoint server (HA), I would to keep under those Appliances LOG and Endpoint Server and keep the actual IP.
and move only Policy manager Role under a new VM with new IP.
My Understanding is :
Install new policy manager Under my vm
export/import database under new vm
link all the Gateways to the new Policy manager ip
probably need to change all licences as they have a new ip for the PM.
But
How can is say to the gateways that the log server is Under a different IP.
and most important part should I rebuild completly my pysical Appliances (log/enpoint)or can I just remove PM role?
Attached a drawing to explain probably better what I would like to do.
Many thanks for your support.
Ben.
Hi @GuilletB,
Old SMS R80.10 or R80.30?
Migration from old to new server (with update to R80.30) and use the same IP on the new SMS.
1) Download R80.30 migration tools.
2) Copy the tool via winscp to your old server.
3) Extract the migration tool to a folder:
# tar xzvf migration...
4) Start migrate export.
# ./migrate export /var/log/migrate_file
New SMS R80.30
5) Copy migrate_file.tgz via winscp to your new R80.30 server to folder /var/log/migrate_file.tgz
6) Now change to folder:
# cd $FWDIR/bin/upgrade_tools
7) Now start migrate import:
# ./migrate import /var/log/migrate_file.tgz
Hi @GuilletB,
Old SMS R80.10 or R80.30?
Migration from old to new server (with update to R80.30) and use the same IP on the new SMS.
1) Download R80.30 migration tools.
2) Copy the tool via winscp to your old server.
3) Extract the migration tool to a folder:
# tar xzvf migration...
4) Start migrate export.
# ./migrate export /var/log/migrate_file
New SMS R80.30
5) Copy migrate_file.tgz via winscp to your new R80.30 server to folder /var/log/migrate_file.tgz
6) Now change to folder:
# cd $FWDIR/bin/upgrade_tools
7) Now start migrate import:
# ./migrate import /var/log/migrate_file.tgz