Category: System Configuration Issue
One or more scripts found in the /etc/firemon/postbackup.d directory could not be migrated to the FMOS Post-Backup Actions framework. These scripts will continue to function, but should be reviewed.
FMOS v9.7 introduced a new mechanism for configuring actions to take following a backup. Administrators are no longer required to write scripts to integrate with other systems or copy backup files to remote locations. FMOS provides native support for copying backup files using several remote file transfer protocols and sending e-mail notifications.
Machines that were upgraded from an earlier version of FMOS to version 9.7.0 or later may have already had post-backup scripts in place. During the upgrade process, FMOS attempts to parse any post-backup scripts it finds and determine if they can be migrated to the new configuration system. Scripts that were based on the remote-sftp.sh.example script can be migrated directly to the new framework. No other scripts can be migrated directly; for theses a Run Command action is configured and the script itself will be executed.
Post-backup scripts that were migrated to run command actions will still work as they originally did. This warning exists to inform administrators that it may be possible to eliminate existing post-backup scripts by manually configuring an equivalent post-backup action. For example, if an administrator had written a post-backup script to copy a backup file to Amazon S3, this script would no longer be necessary as FMOS now natively supports copying to S3. This administrator may choose to use the native functionality and remove the script.
Only scripts that were derived from the remote-sftp.sh.example script are migrated to Post-Backup Action configuration directly. FMOS has special support for these scripts and is able to determine the correct configuration for copying a file to a remote SFTP server based on the contents of the script. It cannot identify or parse any other type of action from post-backup scripts. If any scripts were present in /etc/firemon/postbacup.d that were not derived from the example, they will be migrated as-is, which triggers this warning.
Resolution 1: Manual Migration
If any of the legacy post-backup scripts perform an action that is now supported natively by the FMOS Post-Backup Actions framework, administrators can manually configure these actions. After configuring the new actions, the migrated script action can be removed, which will clear this warning.
Resolution 2: Relocate the Script
This warning only appears when there are Run Command actions configured that execute scripts in the /etc/firemon/postbackup.d directory. Administrators who wish to continue using a custom script as a Post-Backup Action can move the script to another directory and update the action configuration accordingly.