- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Re: Is it possible to migrate from D-series to E-s...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jump to solution
Is it possible to migrate from D-series to E-series SKU size on Azure?
We have deployed CheckPoint R80 on Azure with Standard D3 v2 (4 vcpus, 14 GB memory).
Now we have to migrate to E - series SKU. Is it possible to migrate to E - series?
Any information regarding such migration would be helpful?
- Tags:
- microsoft azure
1 Solution
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Usually you just shut down the VM, change the VM size, and reboot.
That assumes you are moving from PAYG > PAYG or BYOL > BYOL.
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The PAYG License Solution can contain either NGTP or NGTX, but the VM (with its ressources like CPN or RAM) is payed to MS.
CCSE CCTE CCSM SMB Specialist
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Usually you just shut down the VM, change the VM size, and reboot.
That assumes you are moving from PAYG > PAYG or BYOL > BYOL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. Moving from BYOL to BYOL.