- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Migrate Fortimanager to new appliance
I'm moving FortiManger (and Analzyer) from hyper-v to KVM. Is it as simple as spinning up the new appliance and restoring the config or are there steps to do after that?
I've setup the new appliance and restored the config but I don't see any of my policies/objects/scripts. Is there a separate step for this? All I can find for documentation is this: https://help.fortinet.com/fmgr/50hlp/56/5-6-2/FMG-FAZ/2400_System_Settings/0200_Dashboard/0430_Migra...
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A restore won't work because the model is changing. Use migrate. See Technical Note: Using 'exec migrate' to migrate to a new FortiAnalyzer / FortiManager model
Fortinet Technical Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A restore won't work because the model is changing. Use migrate. See Technical Note: Using 'exec migrate' to migrate to a new FortiAnalyzer / FortiManager model
Fortinet Technical Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
chall wrote:A restore won't work because the model is changing. Use migrate. See Technical Note: Using 'exec migrate' to migrate to a new FortiAnalyzer / FortiManager model
So export backup the config from the current FortiManager, then use exec migrate to import the config to the new appliance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes. As outlined in the link I provided.
https://kb.fortinet.com/k...amp;externalId=FD41305
Fortinet Technical Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just had to migrate from one hardware FortiAnalyzer to another one. I posted some comments on it at https://forum.fortinet.com/tm.aspx?m=183032. One of the gotchas is making sure you have ADOMs enabled/disabled to match the original device before starting the migration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good point, tanr. I have added a note about the multi-ADOM scenario in the KB article.
Fortinet Technical Support