haserden.blogg.se

1. #BACKUP EXEC 16 MIGRATION TO ANOTHER SERVER HOW TO#
2. #BACKUP EXEC 16 MIGRATION TO ANOTHER SERVER .EXE#

Uncheck the Overwite current IP and routing settings option to avoid any duplicate IP conflict with the old system. Go in System Settings > System Configuration > Backup You can find relevant information in the below KB for exporting devices: If you need to perform a hardware migration, this section may be skipped. The first thing to do is to prepare the new FortiAnalyzer with the same configuration as the old one by doing a config backup/restore process. Setting up automatic backup is recommended for each FortiAnalyzer unit, but it is not the subject of this KB.įortiAnalyzer hardware replacement must be done using the same kind of hardware and software. In case the FortiAnalyzer replacement is linked to hardware issues, backing up of the system configuration and logs should be done prior to the issue arising. Notice: This KB focuses only on operational FortiAnalyzer units that need to be migrated due to platform upgrade or other reasons. In any case the destination, FortiAnalyzer must have at least he same ADOM quota allocated as the source one (diag log device CLI command can be used for verification). (or use the same VM license within 24 hours grace period duplicate license detection period) In Case of FortiAnalyzer VM migration, two valid VM licensed instances are needed.

#BACKUP EXEC 16 MIGRATION TO ANOTHER SERVER .EXE#

This is a guide to migrate same type of FortiAnalyzer or same model, to transfer the config to a different HW or VM type, use (exe migrate all-settings) CLI command or contact CS. This is useful for FortiAnalyzer replacement or FortiAnalyzer platform upgrade or replacement.

#BACKUP EXEC 16 MIGRATION TO ANOTHER SERVER HOW TO#

This article explains how to migrate logs and config from one FortiAnalyzer to another.