Thanks for your patience here. I’ve passed your feedback and recent experience with the Octopus Migrator on to the team. I’m interested in knowing a few more details about your specific use case with the Octopus Migrator too if possible.
In your environment, would you typically use the exports of your Octopus Projects in source control to restore lost data in the event that your Octopus Server ever has a failure and needs to be restored?
Typically, what would happen to your source Octopus server once you’ve taken the migrator export? Does it get shutdown and destroyed once the export is taken, so that subsequent spawns of an Octopus Server can be built from your code in source control?
I’m asking these questions to get a feel for how you are using this feature because a lot of changes are happening with the Migrator. The good news is that we are planning to introduce some kind of early warning when you attempt to import a non-compatible export, we should expect to see that soon.
While using the Octopus Migrator export is a good way to provide an audit log in source control, we don’t recommend it as a way to provide backup/restore. For more information on this please feel free to check out our documentation on Unsuitable Scenarios for the Octopus data migration. The most recommended way to get a true backup/restore strategy with Octopus is to take Master Key, File Storage and SQL Database backups at regular intervals.
I look forward to hearing your thoughts comments and questions here.