Foreman Maintain

When you restore a backup, you need to restore "the same version", however, this is not as easy as it sounds as you might have a 2.5.2 backup, but restoring to a 2.5.3 as that's the latest release available.
This can result in certain upgrade steps not being run and thus diverge application and database.

To ease that scenario, f-m should run the installer after the config files and databases etc are in place and whatever else "upgrade" steps are defined (for foreman before 2.1 you'd run installer --upgrade and be done, in newer foremans you run installer and then foreman-rake upgrade:run if Katello is present)

To save time, we could look at the metadata of the backup, and only add the upgrade steps if the versions don't match.