I’m looking for some advice. I have a parent dataset called configs with multiple child datasets—one per application—which I believe is a fairly common setup.
As I understand it, when configuring periodic replication tasks, I need to create a corresponding destination dataset for each application. These destination datasets must have the same properties as their respective source datasets.
I’m aware that there is an option to replicate child datasets recursively, but this only applies to child datasets and does not cover the main application dataset itself. Because of this limitation, the main application dataset still requires its own corresponding destination dataset.
What is the easiest and most reliable way to create destination datasets that exactly match the properties of the source datasets?
You simply replicate “configs” recursively. That will replicate the entire hierarchy in exactly the state as the source. You can set a different retention period and you can pick specific snapshots by pattern.
E.g.
- snapshot “configs” recursively every hour, keep for 2 weeks
- replicate only the midnight (00:00) snapshots and keep at the destination for 6 months
All of that works seamlessly for the entire hierarchy below “configs”. Or any other dataset you might want to start at.
Thanks for your reply. I’m aware of the option to replicate configs recursively, but unfortunately this does not create the root dataset itself.
For example, as shown in my screenshot, the source dataset immich is not created on the destination. If I were to replicate multiple applications this way, the destination would not be properly divided into their respective application datasets.
You can simply tell it to use Private_media/media/immich as a target. If it doesn’t exist yet it will be created automatically and properly set/inherit it’s properties.
Then when you include more datasets in the source for this single replication task like this: Private_media/configs/immich,Private_media/configs/whatever you change the destination back to Private_media/media and since there’s now multiple sources it’ll use the last section of each source as a target.
So immich still goes to Private_media/media/immich and whatever would target Private_media/media/whatever.
Or if you want multiple independent jobs just set the Private_media/configs/whatelse → Private_media/media/whatelse source/destination on each of them. The location you specify will be created automatically.
@Momi_V , thank you very much for your clear explantion. This was exactly what I was looking for.