Before, exporting was happening after a random time between midnight and 6am. This is a bad way to do, because backup may not happen every day exactly. From now, the time of backup is defined randomly thanks to the dcron recipe, but won't change once fixed. Still, it may create some delay during the import, but it's far better than before. Also, if a user defines a custom cron frequency, it will overwrite the default one set by the recipe on 1st run. Finally, a migration code has been embeeded, to migrate all the instances already deployed to a random time in the day, instead of keeping them all running at midnight.