Lot's of "Unchanged" items when importing from 3.7.10 to 3.7.10

I am trying to work on making sure that we are able to restore our Octopus Deploy backups to a new server in the event of needing to switch to a DR scenario.

However, when importing in order for it to ‘succeed’ I have to use the --force flag. When using the --force flag I am getting the following:

Unchanged…12963
Attachment…74
CommunityActionTemplate…218
DeploymentProcess…7317
ExtensionConfiguration…1
FeaturesConfiguration…1
LibraryVariableSet…1673
License…1
Lifecycle…1
MachinePolicy…1
NuGetFeed…1
ServerConfiguration…1
UserRole…2
VariableSet…3671
WebPortalConfiguration…1

On a new Server, with a new Instance and a CLEAN database - Why would I get these errors? If I look into the logs I am seeing this;

2017-02-13 10:29:39.5066 1 DEBUG Reader took 24ms (12ms until the first record): SELECT TOP 1 * FROM dbo.[CommunityActionTemplate] WHERE ([Id] = @id) ORDER BY [Id]
2017-02-13 10:29:39.5066 1 DEBUG Skipping CommunityActionTemplate “File System - Clean Directory” (CommunityActionTemplates-51 -> CommunityActionTemplates-56) unchanged
2017-02-13 10:29:39.5066 1 DEBUG Converting CommunityActionTemplate CommunityActionTemplates-52

Hope someone can help because I have no idea where this might be going on - or what it might relate to.

Thanks,

Hi Dan,

I agree, that isn’t what I would expect for importing in to a clean database.

Can I ask how you are invoking the import? Are you running it via the Octopus Manager, or using the Octopus.Migrator.exe command line?
Either way, would you be able to send the command that is being executed (if running via the Octopus Manager, you can get this using the “Show Script” button)?

The Import command runs against an Octopus instance, rather than directly against a database. Is it possible that your are either not running against the correct instance (i.e. your clean instance), or that the instance is not configured to point to the clean database?
You can check the database connection string in the Octopus.Storage.ExternalDatabaseConnectionString key of the Server.config file located in your Octopus home directory (located by default at C:\Octopus).

Regards,
Michael