Thanks for getting in touch. I can see two potential ways of achieving this.
The first option would be to handle this externally from Octopus and focus on a solution using MS SQL tools. There are a few ways (example 1, example 2) to automate the backup and restore of an MS SQL database.
The main drawbacks of this would be security and speed. Octopus uses a master key to secure sensitive information; this key is unique per Octopus installation which means that to make this solution work you would need to configure your Pre Production Octopus instance to use the same master key.
This method would also be restoring the entire database, so if your instance is large, this could take some time.
The second option would be to make use of our migrator tool. This tool allows you to export and import the entire Octopus Server configuration without needing to touch the database. This method would likely be quicker as it will skip any items that already exist by default.
It is worth mentioning that both of these options will only move the configuration data; items such as task logs, artefacts, and packages wouldn’t move during this although task logs can be included in the migrator export.
I hope this helps point you in the right direction, please let me know if you have any further questions.