Steps to reproduce:

1. Unzip new Enterprise bundle (tested with 4.4.1), bring up Magnolia.
2. Activate some content to create versions.
3. Set up scheduled backup. Wait for backup to run.
4. Shut down Magnolia after backups run.
5. Delete repositories. (rm -rf webapps/magnoliaAuthor/repositories/magnolia/)
6. Restore backup files using restore CLI tool. (./bin/restore -backup <backupDir> -webapp <webappDir>)
7. Restart Magnolia. (Might need to delete the indices and restart again.)
8. Modify some of the previously versioned content, activate it.

Expected result:

• Content activates successfully.

Actual result:

• Activation fails. (See attached log.)

Also:

9. Choose "Versions" from page popup.

Expected result:

• List of versions displayed.

Actual result:

• List of versions is empty.

The workaround is to add parameter backupVersions to the generated task and set its value to true