Backup fails in Messaging Gateway when using the SCP transfer protocol. The logs reference failure of FIPS integrity verification.
Mar 26 2017 01:03:09 [BrightmailScheduler_Worker-8] [ScriptHelper] ERROR - Cannot backup the database. Mar 26 2017 01:03:09 [BrightmailScheduler_Worker-8] [ScriptHelper] ERROR - Failed to transmit the file: Problem performing scp: FIPS integrity verification test failed.lost connection. ERROR: Unable to send to the specified URL. Mar 26 2017 01:03:09 [BrightmailScheduler_Worker-8] [ScheduledBackupTask] ERROR - Error occurred while attempting to execute scheduled backup. com.symantec.smg.controlcenter.BrightmailException at com.symantec.smg.controlcenter.agent.ScriptHelper.generateError(ScriptHelper.java:2486) at com.symantec.smg.controlcenter.disasterrecovery.backup.BackupManager.backupNow(BackupManager.java:321) at com.symantec.smg.controlcenter.disasterrecovery.backup.scheduled.ScheduledBackupTask.executeTask(ScheduledBackupTask.java:123) at com.symantec.smg.controlcenter.internal.scheduledtask.ScheduledTask.execute(ScheduledTask.java:133) at org.quartz.core.JobRunShell.run(JobRunShell.java:195) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
This issue is a security feature of SSH and occurs when the Messaging Gateway SCP function (an SSH function) determines the host key of the receiving system has changed.
More information on the host key can be found at https://www.ssh.com/ssh/host-key.
To correct this issue, first make sure that Messaging Gateway is not connecting to an unexpected system and there is no man-in-the-middle intercepting the transfer.
Then, if the connection is as expected, clear the previous key from the Messaging Gateway so it can be recreated:
Note: Use the "rsa-key test" command to add the host key of any necessary hosts that the Messaging Gateway may make scp connections to.